< draft-greevenbosch-coman-candidate-tech-02.txt		draft-greevenbosch-coman-candidate-tech-03.txt >
	coman B. Greevenbosch		coman B. Greevenbosch
	Internet-Draft K. Li		Internet-Draft K. Li
	Intended status: Informational Huawei Technologies		Intended status: Informational Huawei Technologies
	Expires: November 25, 2013 P. van der Stok		Expires: January 04, 2014 P. van der Stok
	vanderstok consultancy		vanderstok consultancy
	May 24, 2013		July 03, 2013
	Candidate Technologies for COMAN		Candidate Technologies for COMAN
	draft-greevenbosch-coman-candidate-tech-02		draft-greevenbosch-coman-candidate-tech-03
	Abstract		Abstract
	This draft identifies candidate technologies and considerations for		This draft identifies candidate technologies and considerations for
	the COMAN use cases and requirements.		the COMAN use cases and requirements.
	Note		Note
	Discussion and suggestions for improvement are requested, and should		Discussion and suggestions for improvement are requested, and should
	be sent to coman@ietf.org.		be sent to coman@ietf.org.
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on November 25, 2013.		This Internet-Draft will expire on January 04, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Requirements notation . . . . . . . . . . . . . . . . . . . . 2		1. Requirements notation . . . . . . . . . . . . . . . . . . . . 2
	2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Identified candidate technologies for the requirements . . . 3		3. Identified candidate technologies for the requirements . . . 3
	3.1. OMA-LwM2M . . . . . . . . . . . . . . . . . . . . . . . . 3		3.1. OMA-LwM2M . . . . . . . . . . . . . . . . . . . . . . . . 3
	3.2. OMA Device Management . . . . . . . . . . . . . . . . . . 3		3.2. OMA Device Management . . . . . . . . . . . . . . . . . . 4
	3.2.1. OMA-DM Management Objects . . . . . . . . . . . . . . 4		3.2.1. OMA-DM Management Objects . . . . . . . . . . . . . . 4
	3.2.2. ACL mechanism in OMA-DM . . . . . . . . . . . . . . . 5		3.2.2. ACL mechanism in OMA-DM . . . . . . . . . . . . . . . 5
	3.3. CoAP . . . . . . . . . . . . . . . . . . . . . . . . . . 5		3.3. CoAP . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3.3.1. CoAP main specification . . . . . . . . . . . . . . . 6		3.3.1. CoAP main specification . . . . . . . . . . . . . . . 6
	3.3.2. CoAP capability discovery specifications . . . . . . 6		3.3.2. CoAP capability discovery specifications . . . . . . 6
	3.3.3. CoAP group communication . . . . . . . . . . . . . . 7		3.3.3. CoAP group communication . . . . . . . . . . . . . . 7
	3.3.4. CoAP energy saving technology . . . . . . . . . . . . 7		3.3.4. CoAP energy saving technology . . . . . . . . . . . . 7
	3.3.5. Congestion avoidance in CoAP . . . . . . . . . . . . 7		3.3.5. Congestion avoidance in CoAP . . . . . . . . . . . . 8
	3.4. Cryptography considerations . . . . . . . . . . . . . . . 8		3.4. Cryptography considerations . . . . . . . . . . . . . . . 8
	3.5. MANET . . . . . . . . . . . . . . . . . . . . . . . . . . 9		3.5. MANET . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	3.6. BACnet . . . . . . . . . . . . . . . . . . . . . . . . . 9		3.6. BACnet . . . . . . . . . . . . . . . . . . . . . . . . . 9
	3.7. Other requirements and candidate technologies . . . . . . 12		3.7. SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	4. High level requirements that need to be observed continuously 13		3.8. NETCONF . . . . . . . . . . . . . . . . . . . . . . . . . 15
	5. Table of requirements and related technologies . . . . . . . 14		3.9. Other requirements and candidate technologies . . . . . . 15
	6. Conclusion and recommendations . . . . . . . . . . . . . . . 19		4. High level requirements that need to be observed continuously 16
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 19		5. Table of requirements and related technologies . . . . . . . 16
	8. IANA considerations . . . . . . . . . . . . . . . . . . . . . 19		6. Conclusion and recommendations . . . . . . . . . . . . . . . 21
	9. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 19		7. Security Considerations . . . . . . . . . . . . . . . . . . . 21
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 19		8. IANA considerations . . . . . . . . . . . . . . . . . . . . . 21
	10.1. Normative References . . . . . . . . . . . . . . . . . . 19		9. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 21
	10.2. Informative References . . . . . . . . . . . . . . . . . 19		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22		10.1. Normative References . . . . . . . . . . . . . . . . . . 22
			10.2. Informative References . . . . . . . . . . . . . . . . . 22
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
	1. Requirements notation		1. Requirements notation
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. Introduction		2. Introduction
	In [I-D.ersue-constrained-mgmt], several use cases and associated		In [I-D.ersue-constrained-mgmt], several use cases and associated
	skipping to change at page 9, line 19 ¶		skipping to change at page 9, line 25 ¶
	Keysize TBD.		Keysize TBD.
	o Candidates for hashing:		o Candidates for hashing:
	* SHA-1		* SHA-1
	* SHA-256		* SHA-256
	* SHA-512		* SHA-512
			o For CoAP [I-D.ietf-core-coap], the following choices have been
			made:
			* Cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 specified in
			[I-D.mcgrew-tls-aes-ccm-ecc], [RFC5246], [RFC4492]
			* Hash: SHA-256
			* ECC with curve secp256r1 (equivalent to NIST P-256) [RFC4492]
			* AES-128 in CCM mode [RFC5116], [CCM]
	4.6.008 Select cryptographic algorithms that are to be supported in		4.6.008 Select cryptographic algorithms that are to be supported in
	hardware		hardware
	o TBD		o TBD
	3.5. MANET		3.5. MANET
	TBD.		TBD.
	3.6. BACnet		3.6. BACnet
	skipping to change at page 11, line 26 ¶		skipping to change at page 11, line 41 ¶
	o 4.4.001 Device status monitoring - BACnet provides extensive tools		o 4.4.001 Device status monitoring - BACnet provides extensive tools
	for network and device status monitoring, specified in the Alarm		for network and device status monitoring, specified in the Alarm
	and Event services section. BACnet supports a very flexible event		and Event services section. BACnet supports a very flexible event
	and alarm reporting. Clients can subscribe to generators of		and alarm reporting. Clients can subscribe to generators of
	events and alarms, which can be changes of values in objects or		events and alarms, which can be changes of values in objects or
	status changes. Classes of events can be specified with		status changes. Classes of events can be specified with
	appropriate handling by the clients.		appropriate handling by the clients.
	o 4.4.002 Energy status monitoring - This can be provided in BACnet		o 4.4.002 Energy status monitoring - This can be provided in BACnet
	by creating a binary value object type connected to the energy		by creating a binary value object type connected to the energy
	c.q. power attributes to monitor and specify a change of state		c.q. power attributes to monitor and specify a change of state
	with an appropriate client.		with an appropriate client.
	o 4.4.003 Monitoring of current and estimated device availability -		o 4.4.003 Monitoring of current and estimated device availability -
	See text in 4.4.002.		See text in 4.4.002.
	o 4.4.004 Network status monitoring - BACnet provides facilities to		o 4.4.004 Network status monitoring - BACnet provides facilities to
	configure and install routers on the BACnet network. BACnet		configure and install routers on the BACnet network. BACnet
	specifies the MS/TP and PTP link protocols with the possibility to		specifies the MS/TP and PTP link protocols with the possibility to
	monitor link status.		monitor link status.
	skipping to change at page 12, line 30 ¶		skipping to change at page 12, line 45 ¶
	configuration purposes.		configuration purposes.
	o 4.11.001 Avoid complex application layer transactions requiring		o 4.11.001 Avoid complex application layer transactions requiring
	large application messages - BACnet has a finite set of		large application messages - BACnet has a finite set of
	application message constructs in which application messages		application message constructs in which application messages
	should fit.		should fit.
	o 4.11.002 Avoid reassembly of messages at multiple layers in the		o 4.11.002 Avoid reassembly of messages at multiple layers in the
	protocol stack - BACnet avoids reassembly by contruction.		protocol stack - BACnet avoids reassembly by contruction.
	3.7. Other requirements and candidate technologies		3.7. SNMP
			The Simple Network Management Protocol (SNMP) can be used to monitor
			and manage various network entities. It is the most popular network
			management protocol today based on IETF standards. In [RFC3410] an
			introduction and overview of SNMP is presented. The architecture of
			the Internet Standard management framework consists of:
			o A data definition language, referred to as Structure of Management
			Information (SMI), is defined in [RFC2578], [RFC2579], [RFC2580].
			o The Management Information Base (MIB) which contains the
			information to be managed and is defined for each specific
			function to be managed [RFC3418].
			o A protocol definition referred to as Simple Network Management
			Protocol. Version 3 (SNMPv3) is defined in [RFC3411], [RFC3412],
			[RFC3413], [RFC3416], and [RFC3417].
			o Security and administration that provides SNMP message based
			security on the basis of the user-based security model, discussed
			in [RFC3414] and [RFC3415].
			Separation in modules was motivated by the wish to respond to the
			evolution of Internet. The protocol part (SNMP) and data definition
			part (MIB) are independent of each other. The separation has enabled
			the progressive passage from SNMPv1 via SNMPv2 to SNMPv3. The SNMP
			protocol supports seven types of access supported by as many Protocol
			Data Unit (PDU) types. Two types of message exchange are used:
			o The SNMP client sends out a request message after which the SNMP
			server returns a Response message.
			o The SNMP server sends a confirmed or unconfirmed notification
			message with a list of (OBJECT-IDENTIFIERs, value) pairs to a
			notification requesting end-point.
			The MIB objects are defined in ASN.1, for various protocols, at
			different layers. For example, [RFC4113] defines a MIB for UDP,
			whereas the draft [I-D.schoenw-6lowpan-mib] defines a MIB module for
			6LoWPAN [RFC4944].
			The interesting part of SNMP is that it provides a framework that
			enables request/response and notification type message exchanges.
			The purpose of the message exchange is defined by the contents of the
			MIBs which are declared independently for many different purposes.
			Related requirements are:
			o 4.1.001 Multiple device classes, SNMP and MIB are class
			independent.
			o 4.1.002 Management scalability, SNMP can be the basis for extended
			management functionality.
			o 4.2.001 Modular implementation, Separation between MIB and SNMP
			provides basic modularity. Separation in MIBs and SNMP entities
			provides a second level of modularity.
			o 4.2.005 Consistency between data and information model, Encouraged
			by separation of MIBs.
			o 4.2.007 Protocol Extensibility, Supported by design, but lacks in
			message PDU type extensibility.
			o 4.3.004 Network reconfiguration, Several MIBs support network
			configuration but not in an automatic network state driven
			fashion.
			o 4.4.001 Device status monitoring, Appropriate MIB is specified.
			o 4.4.002 Energy state monitoring, MIB specified by Eman.
			o 4.4.004 Network status monitoring, Appropriate MIB is specified
			o 4.4.006 Performance monitoring, Appropriate MIBs may be specified
			outside IETF
			o 4.4.007 Fault detection monitoring, Appropriate MIBs are
			specified.
			o 4.4.011 Notifications, Basic SNMP function.
			o 4.6.001 Authentication of management system and devices, supported
			by SNMPv3.
			o 4.6.003 Access control on management system and devices, supported
			by SNMPv3.
			o 4.7.001 Management of Energy Resources, supported by Eman MIBs.
			o 4.11.001 Avoid large messages, SNMP supports progessive transport
			of data in self contained chunks.
			o 4.11.002 Avoid reassembly at multiple layers, SNMP request
			specifies data size per message.
			Since much MIB creation effort can be done offline through macros,
			and BER encoding is not extremely complex, it is feasible to
			implement SNMP in constrained environments. Sharing the security
			code between SNMP and DTLS/CoAP makes the inclusion of SNMP even more
			attractive.
			3.8. NETCONF
			Cover at least:
			o The NETCONF protocol is defined in [RFC6241]
			o The YANG module is defined in [RFC6022]
			o NETCONF is based on XML
			3.9. Other requirements and candidate technologies
	4.1.005 Automatic re-synchronisation with eventual consistency		4.1.005 Automatic re-synchronisation with eventual consistency
	4.1.006 Support for lossy links and unreachable devices		4.1.006 Support for lossy links and unreachable devices
	o Mechanisms for devices that are not sleepy, but have unstable		o Mechanisms for devices that are not sleepy, but have unstable
	network connections (e.g. mobile devices) are needed.		network connections (e.g. mobile devices) are needed.
	4.1.008 Distributed management		4.1.008 Distributed management
	4.2.006 Loss-less mapping of management data models		4.2.006 Loss-less mapping of management data models
	4.3.002 Capability discovery		4.3.002 Capability discovery
	4.3.004 Network reconfiguration		4.3.004 Network reconfiguration
	4.4.009 Recovery		4.4.009 Recovery
	skipping to change at page 14, line 4 ¶		skipping to change at page 16, line 35 ¶
	o A binary format would be most compact.		o A binary format would be most compact.
	o TLV could be considered.		o TLV could be considered.
	o XML would be counter productive.		o XML would be counter productive.
	o JSON may be counter productive.		o JSON may be counter productive.
	4.2.003 Compression of management data or complete messages		4.2.003 Compression of management data or complete messages
	o When the messages are designed compact enough, compression will be		o When the messages are designed compact enough, compression will be
	unnecessary.		unnecessary.
	4.2.007 Protocol extensibility		4.2.007 Protocol extensibility
	5. Table of requirements and related technologies		5. Table of requirements and related technologies
	The Table 1 summarises the requirements and related or possible		The Table 1 summarises the requirements and related or possible
	candidate technologies.		candidate technologies.
	+-----------+----------------+--------------------------------------+		+-----------+----------------+--------------------------------------+
	| Requireme | Name | Associated technology |		| Requireme | Name | Associated technology |
	| nt number | | |		| nt number | | |
	+-----------+----------------+--------------------------------------+		+-----------+----------------+--------------------------------------+
	| 4.1.001 | Support | [I-D.ietf-core-coap], [ISO16484-5] |		| 4.1.001 | Support | [I-D.ietf-core-coap], [ISO16484-5], |
	| | multiple | |		| | multiple | [RFC3410] |
	| | device classes | |		| | device classes | |
	| | within a | |		| | within a | |
	| | single network | |		| | single network | |
	| | | |		| | | |
	| 4.1.002 | Management | [ISO16484-5] |		| 4.1.002 | Management | [ISO16484-5], [RFC3410] |
	| | scalability | |		| | scalability | |
	| | | |		| | | |
	| 4.1.003 | Hierarchical | [ISO16484-5] |		| 4.1.003 | Hierarchical | [ISO16484-5] |
	| | management | |		| | management | |
	| | | |		| | | |
	| 4.1.004 | Minimise state | [I-D.ietf-core-coap], [ISO16484-5] |		| 4.1.004 | Minimise state | [I-D.ietf-core-coap], [ISO16484-5] |
	| | maintained on | |		| | maintained on | |
	| | constrained | |		| | constrained | |
	| | devices | |		| | devices | |
	| | | |		| | | |
	skipping to change at page 15, line 4 ¶		skipping to change at page 17, line 36 ¶
	| | and | resource-directory], [I-D.ietf-core- |		| | and | resource-directory], [I-D.ietf-core- |
	| | unreachable | observe] |		| | unreachable | observe] |
	| | devices | |		| | devices | |
	| | | |		| | | |
	| 4.1.007 | Network-wide | [OMA-DM], [ISO16484-5] |		| 4.1.007 | Network-wide | [OMA-DM], [ISO16484-5] |
	| | configuration | |		| | configuration | |
	| | | |		| | | |
	| 4.1.008 | Distributed | [ISO16484-5] |		| 4.1.008 | Distributed | [ISO16484-5] |
	| | management | |		| | management | |
	| | | |		| | | |
	| 4.2.001 | Modular | [ISO16484-5] |		| 4.2.001 | Modular | [ISO16484-5], [RFC3410] |
	| | implementation | |		| | implementation | |
	| | of management | |		| | of management | |
	| | protocols | |		| | protocols | |
	| | | |		| | | |
	| 4.2.002 | Compact | [OMA-LwM2M-TS], [ISO16484-5] |		| 4.2.002 | Compact | [OMA-LwM2M-TS], [ISO16484-5] |
	| | encoding of | |		| | encoding of | |
	| | management | |		| | management | |
	| | data | |		| | data | |
	| | | |		| | | |
	| 4.2.003 | Compression of | |		| 4.2.003 | Compression of | |
	| | management | |		| | management | |
	| | data or | |		| | data or | |
	| | complete | |		| | complete | |
	| | messages | |		| | messages | |
	| | | |		| | | |
	| 4.2.004 | Mapping of | [I-D.ietf-core-coap] |		| 4.2.004 | Mapping of | [I-D.ietf-core-coap] |
	| | management | |		| | management | |
	| | protocol | |		| | protocol | |
	| | interactions | |		| | interactions | |
	| | | |		| | | |
	| 4.2.005 | Consistency of | [ISO16484-5] |		| 4.2.005 | Consistency of | [ISO16484-5], [RFC3410] |
	| | data models | |		| | data models | |
	| | with the | |		| | with the | |
	| | underlying | |		| | underlying | |
	| | information | |		| | information | |
	| | model | |		| | model | |
	| | | |		| | | |
	| 4.2.006 | Loss-less | |		| 4.2.006 | Loss-less | |
	| | mapping of | |		| | mapping of | |
	| | management | |		| | management | |
	| | data models | |		| | data models | |
	| | | |		| | | |
	| 4.2.007 | Protocol | [I-D.ietf-core-coap], [ISO16484-5] |		| 4.2.007 | Protocol | [I-D.ietf-core-coap], [ISO16484-5], |
	| | extensibility | |		| | extensibility | [RFC3410] |
	| | | |		| | | |
	| 4.3.001 | Self- | [ISO16484-5] |		| 4.3.001 | Self- | [ISO16484-5] |
	| | configuration | |		| | configuration | |
	| | capability | |		| | capability | |
	| | | |		| | | |
	| 4.3.002 | Capability | [RFC6690], [I-D.greevenbosch-core- |		| 4.3.002 | Capability | [RFC6690], [I-D.greevenbosch-core- |
	| | discovery | profile-description], [I-D.shelby- |		| | discovery | profile-description], [I-D.shelby- |
	| | | core-resource-directory], [I-D.lynn- |		| | | core-resource-directory], [I-D.lynn- |
	| | | core-discovery-mapping], [I-D |		| | | core-discovery-mapping], [I-D |
	| | | .vanderstok-core-dna], [ISO16484-5] |		| | | .vanderstok-core-dna], [ISO16484-5] |
	| | | |		| | | |
	| 4.3.003 | Asynchronous | [I-D.ietf-core-coap] |		| 4.3.003 | Asynchronous | [I-D.ietf-core-coap] |
	| | transaction | |		| | transaction | |
	| | support | |		| | support | |
	| | | |		| | | |
	| 4.3.004 | Network reconf | [ISO16484-5] |		| 4.3.004 | Network reconf | [ISO16484-5], [RFC3410] |
	| | iguration | |		| | iguration | |
	| | | |		| | | |
	| 4.4.001 | Device status | [OMA-LwM2M-TS], [ISO16484-5] |		| 4.4.001 | Device status | [OMA-LwM2M-TS], [ISO16484-5], |
	| | monitoring | |		| | monitoring | [RFC3410] |
	| | | |		| | | |
	| 4.4.002 | Energy status | [OMA-LwM2M-TS], [ISO16484-5] |		| 4.4.002 | Energy status | [OMA-LwM2M-TS], [ISO16484-5], |
	| | monitoring | |		| | monitoring | [RFC3410] |
	| | | |		| | | |
	| 4.4.003 | Monitoring of | [OMA-DiagMon-MO], [ISO16484-5] |		| 4.4.003 | Monitoring of | [OMA-DiagMon-MO], [ISO16484-5] |
	| | current and | |		| | current and | |
	| | estimated | |		| | estimated | |
	| | device | |		| | device | |
	| | availability | |		| | availability | |
	| | | |		| | | |
	| 4.4.004 | Network status | [OMA-DiagMon-MO], [ISO16484-5] |		| 4.4.004 | Network status | [OMA-DiagMon-MO], [ISO16484-5], |
	| | monitoring | |		| | monitoring | [RFC3410] |
	| | | |		| | | |
	| 4.4.005 | Self- | [OMA-DiagMon-MO], [ISO16484-5] |		| 4.4.005 | Self- | [OMA-DiagMon-MO], [ISO16484-5] |
	| | monitoring | |		| | monitoring | |
	| | | |		| | | |
	| 4.4.006 | Performance | [OMA-DiagMon-MO], [ISO16484-5] |		| 4.4.006 | Performance | [OMA-DiagMon-MO], [ISO16484-5], |
	| | monitoring | |		| | monitoring | [RFC3410] |
	| | | |		| | | |
	| 4.4.007 | Fault | [I-D.ietf-core-coap], [OMA-DiagMon- |		| 4.4.007 | Fault | [I-D.ietf-core-coap], [OMA-DiagMon- |
	| | detection | MO], [ISO16484-5] |		| | detection | MO], [ISO16484-5], [RFC3410] |
	| | monitoring | |		| | monitoring | |
	| | | |		| | | |
	| 4.4.008 | Passive and | [OMA-DiagMon-MO] |		| 4.4.008 | Passive and | [OMA-DiagMon-MO] |
	| | reactive | |		| | reactive | |
	| | monitoring | |		| | monitoring | |
	| | | |		| | | |
	| 4.4.009 | Recovery | [ISO16484-5] |		| 4.4.009 | Recovery | [ISO16484-5] |
	| | | |		| | | |
	| 4.4.010 | Network | [ISO16484-5] |		| 4.4.010 | Network | [ISO16484-5] |
	| | topology | |		| | topology | |
	| | discovery | |		| | discovery | |
	| | | |		| | | |
	| 4.4.011 | Notifications | [OMA-DiagMon-MO], [ISO16484-5] |		| 4.4.011 | Notifications | [OMA-DiagMon-MO], [ISO16484-5], |
			| | | [RFC3410] |
	| | | |		| | | |
	| 4.4.012 | Logging | [OMA-LwM2M-TS], [ISO16484-5] |		| 4.4.012 | Logging | [OMA-LwM2M-TS], [ISO16484-5] |
	| | | |		| | | |
	| 4.5.001 | Self- | [OMA-DiagMon-MO], [OMA-Scheduling- |		| 4.5.001 | Self- | [OMA-DiagMon-MO], [OMA-Scheduling- |
	| | management - | MO] |		| | management - | MO] |
	| | Self-healing | |		| | Self-healing | |
	| | | |		| | | |
	| 4.6.001 | Authentication | [OMA-LwM2M-TS], [I-D.ietf-tls-oob- |		| 4.6.001 | Authentication | [OMA-LwM2M-TS], [I-D.ietf-tls-oob- |
	| | of management | pubkey], [I-D.greevenbosch-tls-ocsp- |		| | of management | pubkey], [I-D.greevenbosch-tls-ocsp- |
	| | system and | lite], [ISO16484-5] |		| | system and | lite], [ISO16484-5], [RFC3410] |
	| | devices | |		| | devices | |
	| | | |		| | | |
	| 4.6.002 | Support | [OMA-LwM2M-TS], [OMA-DM], [I-D |		| 4.6.002 | Support | [OMA-LwM2M-TS], [OMA-DM], [I-D |
	| | suitable | .jennings-core-transitive-trust- |		| | suitable | .jennings-core-transitive-trust- |
	| | security | enrollment] |		| | security | enrollment] |
	| | bootstrapping | |		| | bootstrapping | |
	| | mechanisms | |		| | mechanisms | |
	| | | |		| | | |
	| 4.6.003 | Access control | [OMA-LwM2M-TS], [OMA-DM] |		| 4.6.003 | Access control | [OMA-LwM2M-TS], [OMA-DM], [RFC3410] |
	| | on management | |		| | on management | |
	| | system and | |		| | system and | |
	| | devices | |		| | devices | |
	| | | |		| | | |
	| 4.6.004 | Select | |		| 4.6.004 | Select | |
	| | cryptographic | |		| | cryptographic | |
	| | algorithms | |		| | algorithms | |
	| | that are | |		| | that are | |
	| | efficient in | |		| | efficient in | |
	| | both code | |		| | both code | |
	| | space and | |		| | space and | |
	| | execution time | |		| | execution time | |
	| | | |		| | | |
	| 4.7.001 | Management of | [IEEE-802.15.4], [I-D.rahman-core- |		| 4.7.001 | Management of | [IEEE-802.15.4], [I-D.rahman-core- |
	| | energy | sleepy], |		| | energy | sleepy], [RFC3410] |
	| | resources | |		| | resources | |
	| | | |		| | | |
	| 4.7.002 | Support of | [I-D.ietf-core-coap], [RFC4944], |		| 4.7.002 | Support of | [I-D.ietf-core-coap], [RFC4944], |
	| | energy- | [I-D.rahman-core-sleepy], [I-D.ietf- |		| | energy- | [I-D.rahman-core-sleepy], [I-D.ietf- |
	| | optimized | core-observe], [I-D.shelby-core- |		| | optimized | core-observe], [I-D.shelby-core- |
	| | communication | resource-directory] |		| | communication | resource-directory] |
	| | protocols | |		| | protocols | |
	| | | |		| | | |
	| 4.7.003 | Support for | [IEEE-802.15.4] |		| 4.7.003 | Support for | [IEEE-802.15.4] |
	| | layer 2 | |		| | layer 2 | |
	skipping to change at page 18, line 28 ¶		skipping to change at page 21, line 13 ¶
	| 4.10.002 | Reliable | |		| 4.10.002 | Reliable | |
	| | unicast | |		| | unicast | |
	| | transport | |		| | transport | |
	| | | |		| | | |
	| 4.10.003 | Best-effort | [ISO16484-5] |		| 4.10.003 | Best-effort | [ISO16484-5] |
	| | multicast | |		| | multicast | |
	| | | |		| | | |
	| 4.10.004 | Secure message | |		| 4.10.004 | Secure message | |
	| | transport | |		| | transport | |
	| | | |		| | | |
	| 4.11.001 | Avoid complex | |		| 4.11.001 | Avoid complex | [RFC3410] |
	| | application | |		| | application | |
	| | layer | |		| | layer | |
	| | transactions | |		| | transactions | |
	| | requiring | |		| | requiring | |
	| | large | |		| | large | |
	| | application | |		| | application | |
	| | layer messages | |		| | layer messages | |
	| | | |		| | | |
	| 4.11.002 | Avoid | [ISO16484-5] |		| 4.11.002 | Avoid | [ISO16484-5], [RFC3410] |
	| | reassembly of | |		| | reassembly of | |
	| | messages at | |		| | messages at | |
	| | multiple | |		| | multiple | |
	| | layers in the | |		| | layers in the | |
	| | protocol stack | |		| | protocol stack | |
	+-----------+----------------+--------------------------------------+		+-----------+----------------+--------------------------------------+
	Table 1: Requirements and technologies		Table 1: Requirements and technologies
	6. Conclusion and recommendations		6. Conclusion and recommendations
	skipping to change at page 19, line 24 ¶		skipping to change at page 22, line 4 ¶
	7. Security Considerations		7. Security Considerations
	TBD		TBD
	8. IANA considerations		8. IANA considerations
	TBD		TBD
	9. Change Log		9. Change Log
	v00 -> v01:		v00 -> v01:
	o Added text about BACnet.		o Added text about BACnet.
	v01 -> v02:		v01 -> v02:
	o Updated text about BACnet.		o Updated text about BACnet.
	o Updated to match new requirements numbering in I-D.ersue-		o Updated to match new requirements numbering in I-D.ersue-
	constrained-mgmt v04.		constrained-mgmt v04.
			v02 -> v03:
			o Added text about SNMP.
			o Added bullets about security choices in CoAP.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	10.2. Informative References		10.2. Informative References
			[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
			Schoenwaelder, Ed., "Structure of Management Information
			Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
			[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
			Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
			58, RFC 2579, April 1999.
			[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
			"Conformance Statements for SMIv2", STD 58, RFC 2580,
			April 1999.
			[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
			"Introduction and Applicability Statements for Internet-
			Standard Management Framework", RFC 3410, December 2002.
			[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
			Architecture for Describing Simple Network Management
			Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
			December 2002.
			[RFC3412] Case, J., Harrington, D., Presuhn, R., and B. Wijnen,
			"Message Processing and Dispatching for the Simple Network
			Management Protocol (SNMP)", STD 62, RFC 3412, December
			2002.
			[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network
			Management Protocol (SNMP) Applications", STD 62, RFC
			3413, December 2002.
			[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
			(USM) for version 3 of the Simple Network Management
			Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
			[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
			Access Control Model (VACM) for the Simple Network
			Management Protocol (SNMP)", STD 62, RFC 3415, December
			2002.
			[RFC3416] Presuhn, R., "Version 2 of the Protocol Operations for the
			Simple Network Management Protocol (SNMP)", STD 62, RFC
			3416, December 2002.
			[RFC3417] Presuhn, R., "Transport Mappings for the Simple Network
			Management Protocol (SNMP)", STD 62, RFC 3417, December
			2002.
			[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
			Simple Network Management Protocol (SNMP)", STD 62, RFC
			3418, December 2002.
			[RFC4113] Fenner, B. and J. Flick, "Management Information Base for
			the User Datagram Protocol (UDP)", RFC 4113, June 2005.
			[RFC4492] Blake-Wilson, S., Bolyard, N., Gupta, V., Hawk, C., and B.
			Moeller, "Elliptic Curve Cryptography (ECC) Cipher Suites
			for Transport Layer Security (TLS)", RFC 4492, May 2006.
	[RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet		[RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet
	Group Management Protocol Version 3 (IGMPv3) and Multicast		Group Management Protocol Version 3 (IGMPv3) and Multicast
	Listener Discovery Protocol Version 2 (MLDv2) for Source-		Listener Discovery Protocol Version 2 (MLDv2) for Source-
	Specific Multicast", RFC 4604, August 2006.		Specific Multicast", RFC 4604, August 2006.
	[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,		[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
	"Transmission of IPv6 Packets over IEEE 802.15.4		"Transmission of IPv6 Packets over IEEE 802.15.4
	Networks", RFC 4944, September 2007.		Networks", RFC 4944, September 2007.
			[RFC5116] McGrew, D., "An Interface and Algorithms for Authenticated
			Encryption", RFC 5116, January 2008.
			[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
			(TLS) Protocol Version 1.2", RFC 5246, August 2008.
			[RFC6022] Scott, M. and M. Bjorklund, "YANG Module for NETCONF
			Monitoring", RFC 6022, October 2010.
	[RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc		[RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc
	Network (MANET) Neighborhood Discovery Protocol (NHDP)",		Network (MANET) Neighborhood Discovery Protocol (NHDP)",
	RFC 6130, April 2011.		RFC 6130, April 2011.
			[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
			Bierman, "Network Configuration Protocol (NETCONF)", RFC
			6241, June 2011.
	[RFC6690] Shelby, Z., "Constrained RESTful Environments (CoRE) Link		[RFC6690] Shelby, Z., "Constrained RESTful Environments (CoRE) Link
	Format", RFC 6690, August 2012.		Format", RFC 6690, August 2012.
	[I-D.ietf-core-coap]		[I-D.ietf-core-coap]
	Shelby, Z., Hartke, K., and C. Bormann, "Constrained		Shelby, Z., Hartke, K., and C. Bormann, "Constrained
	Application Protocol (CoAP)", draft-ietf-core-coap-16		Application Protocol (CoAP)", draft-ietf-core-coap-18
	(work in progress), May 2013.		(work in progress), June 2013.
	[I-D.ietf-core-groupcomm]		[I-D.ietf-core-groupcomm]
	Rahman, A. and E. Dijk, "Group Communication for CoAP",		Rahman, A. and E. Dijk, "Group Communication for CoAP",
	draft-ietf-core-groupcomm-07 (work in progress), May 2013.		draft-ietf-core-groupcomm-09 (work in progress), May 2013.
	[I-D.ietf-core-observe]		[I-D.ietf-core-observe]
	Hartke, K., "Observing Resources in CoAP", draft-ietf-		Hartke, K., "Observing Resources in CoAP", draft-ietf-
	core-observe-08 (work in progress), February 2013.		core-observe-08 (work in progress), February 2013.
	[I-D.ietf-tls-oob-pubkey]		[I-D.ietf-tls-oob-pubkey]
	Wouters, P., Tschofenig, H., Gilmore, J., Weiler, S., and		Wouters, P., Tschofenig, H., Gilmore, J., Weiler, S., and
	T. Kivinen, "Out-of-Band Public Key Validation for		T. Kivinen, "Out-of-Band Public Key Validation for
	Transport Layer Security (TLS)", draft-ietf-tls-oob-		Transport Layer Security (TLS)", draft-ietf-tls-oob-
	pubkey-07 (work in progress), February 2013.		pubkey-07 (work in progress), February 2013.
	skipping to change at page 20, line 48 ¶		skipping to change at page 25, line 9 ¶
	"Management of Networks with Constrained Devices: Problem		"Management of Networks with Constrained Devices: Problem
	Statement, Use Cases and Requirements", draft-ersue-		Statement, Use Cases and Requirements", draft-ersue-
	constrained-mgmt-03 (work in progress), February 2013.		constrained-mgmt-03 (work in progress), February 2013.
	[I-D.greevenbosch-core-minimum-request-interval]		[I-D.greevenbosch-core-minimum-request-interval]
	Greevenbosch, B., "CoAP Minimum Request Interval", draft-		Greevenbosch, B., "CoAP Minimum Request Interval", draft-
	greevenbosch-core-minimum-request-interval-01 (work in		greevenbosch-core-minimum-request-interval-01 (work in
	progress), April 2013.		progress), April 2013.
	[I-D.greevenbosch-core-profile-description]		[I-D.greevenbosch-core-profile-description]
	Greevenbosch, B., Hoebeke, J., and I. Ishaq, "CoAP Profile		Greevenbosch, B., Hoebeke, J., Ishaq, I., and F. Abeele,
	Description Format", draft-greevenbosch-core-profile-		"CoAP Profile Description Format", draft-greevenbosch-
	description-01 (work in progress), October 2012.		core-profile-description-02 (work in progress), June 2013.
	[I-D.greevenbosch-tls-ocsp-lite]		[I-D.greevenbosch-tls-ocsp-lite]
	Greevenbosch, B., "OCSP-lite - Revocation of raw public		Greevenbosch, B., "OCSP-lite - Revocation of raw public
	keys", draft-greevenbosch-tls-ocsp-lite-00 (work in		keys", draft-greevenbosch-tls-ocsp-lite-01 (work in
	progress), December 2012.		progress), June 2013.
	[I-D.jennings-core-transitive-trust-enrollment]		[I-D.jennings-core-transitive-trust-enrollment]
	Jennings, C., "Transitive Trust Enrollment for Constrained		Jennings, C., "Transitive Trust Enrollment for Constrained
	Devices", draft-jennings-core-transitive-trust-		Devices", draft-jennings-core-transitive-trust-
	enrollment-01 (work in progress), October 2012.		enrollment-01 (work in progress), October 2012.
	[I-D.li-core-conditional-observe]		[I-D.li-core-conditional-observe]
	Li, S., Hoebeke, J., and A. Jara, "Conditional observe in		Li, S., Hoebeke, J., Abeele, F., and A. Jara, "Conditional
	CoAP", draft-li-core-conditional-observe-03 (work in		observe in CoAP", draft-li-core-conditional-observe-04
	progress), October 2012.		(work in progress), June 2013.
	[I-D.lynn-core-discovery-mapping]		[I-D.lynn-core-discovery-mapping]
	Lynn, K. and Z. Shelby, "CoRE Link-Format to DNS-Based		Lynn, K. and Z. Shelby, "CoRE Link-Format to DNS-Based
	Service Discovery Mapping", draft-lynn-core-discovery-		Service Discovery Mapping", draft-lynn-core-discovery-
	mapping-02 (work in progress), October 2012.		mapping-02 (work in progress), October 2012.
			[I-D.mcgrew-tls-aes-ccm-ecc]
			McGrew, D., Bailey, D., Campagna, M., and R. Dugal, "AES-
			CCM ECC Cipher Suites for TLS", draft-mcgrew-tls-aes-ccm-
			ecc-06 (work in progress), February 2013.
	[I-D.rahman-core-sleepy]		[I-D.rahman-core-sleepy]
	Rahman, A., "Enhanced Sleepy Node Support for CoAP",		Rahman, A., "Enhanced Sleepy Node Support for CoAP",
	draft-rahman-core-sleepy-02 (work in progress), February		draft-rahman-core-sleepy-02 (work in progress), February
	2013.		2013.
			[I-D.schoenw-6lowpan-mib]
			Schoenwaelder, J., Sehgal, A., Tsou, T., and C. Zhou,
			"Definition of Managed Objects for IPv6 over Low-Power
			Wireless Personal Area Networks (6LoWPANs)", draft-
			schoenw-6lowpan-mib-03 (work in progress), February 2013.
	[I-D.shelby-core-resource-directory]		[I-D.shelby-core-resource-directory]
	Shelby, Z., Krco, S., and C. Bormann, "CoRE Resource		Shelby, Z., Krco, S., and C. Bormann, "CoRE Resource
	Directory", draft-shelby-core-resource-directory-05 (work		Directory", draft-shelby-core-resource-directory-05 (work
	in progress), February 2013.		in progress), February 2013.
	[I-D.vanderstok-core-dna]		[I-D.vanderstok-core-dna]
	Stok, P., Lynn, K., and A. Brandt, "CoRE Discovery,		Stok, P., Lynn, K., and A. Brandt, "CoRE Discovery,
	Naming, and Addressing", draft-vanderstok-core-dna-02		Naming, and Addressing", draft-vanderstok-core-dna-02
	(work in progress), July 2012.		(work in progress), July 2012.
			[CCM] , "Recommendation for Block Cipher Modes of Operation: The
			CCM Mode for Authentication and Confidentiality ",
			National Institute of Standards and Technology SP 800-38C,
			May 2004.
	[IEEE-802.15.4]		[IEEE-802.15.4]
	IEEE Computer Society, , "IEEE std. 802.15.4-2003",		IEEE Computer Society, ., "IEEE std. 802.15.4-2003",
	October 2003.		October 2003.
	[ISO16484-5]		[ISO16484-5]
	, "Building automation and control systems -- Part 5: Data		, "Building automation and control systems -- Part 5: Data
	communication protocol", ISO 16484-5, 2012.		communication protocol", ISO 16484-5, 2012.
	[OMA-DM] , "OMA Device Management 1.3", OMA-ERP-DM-V1_3-20121213-C		[OMA-DM] , "OMA Device Management 1.3", OMA-ERP-DM-V1_3-20121213-C
	, December 2012.		, December 2012.
	[OMA-DiagMon-MO]		[OMA-DiagMon-MO]
	skipping to change at page 22, line 18 ¶		skipping to change at page 27, line 4 ¶
	[OMA-Scheduling-MO]		[OMA-Scheduling-MO]
	, "OMA DM Scheduling Management Object", OMA-ERP-		, "OMA DM Scheduling Management Object", OMA-ERP-
	DM_Scheduling-V1_0-20110614-C , June 2011.		DM_Scheduling-V1_0-20110614-C , June 2011.
	[OMA-LwM2M-TS]		[OMA-LwM2M-TS]
	, "OMA Lightweight M2M", OMA-TS-LightweightM2M-		, "OMA Lightweight M2M", OMA-TS-LightweightM2M-
	V1_0-20130123-D (work in progress), January 2013.		V1_0-20130123-D (work in progress), January 2013.
	Authors' Addresses		Authors' Addresses
	Bert Greevenbosch		Bert Greevenbosch
	Huawei Technologies Co., Ltd.		Huawei Technologies Co., Ltd.
	Huawei Industrial Base		Huawei Industrial Base
	Bantian, Longgang District		Bantian, Longgang District
	Shenzhen 518129		Shenzhen 518129
	P.R. China		P.R. China
	Phone: +86-755-28979133
	Email: bert.greevenbosch@huawei.com		Email: bert.greevenbosch@huawei.com
	Kepeng Li		Kepeng Li
	Huawei Technologies Co., Ltd.		Huawei Technologies Co., Ltd.
	Huawei Industrial Base		Huawei Industrial Base
	Bantian, Longgang District		Bantian, Longgang District
	Shenzhen 518129		Shenzhen 518129
	P.R. China		P.R. China
	Phone: +86-755-28971807		Phone: +86-755-28971807
End of changes. 47 change blocks.
	60 lines changed or deleted		278 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/