draft-ietf-opsawg-coman-probstate-reqs-03.txt		draft-ietf-opsawg-coman-probstate-reqs-04.txt
	Internet Engineering Task Force M. Ersue, Ed.		Internet Engineering Task Force M. Ersue, Ed.
	Internet-Draft Nokia Networks		Internet-Draft Nokia Networks
	Intended status: Informational D. Romascanu		Intended status: Informational D. Romascanu
	Expires: April 30, 2015 Avaya		Expires: July 22, 2015 Avaya
	J. Schoenwaelder		J. Schoenwaelder
	Jacobs University Bremen		Jacobs University Bremen
	U. Herberg		U. Herberg
	October 27, 2014		January 18, 2015
	Management of Networks with Constrained Devices: Problem Statement and		Management of Networks with Constrained Devices: Problem Statement and
	Requirements		Requirements
	draft-ietf-opsawg-coman-probstate-reqs-03		draft-ietf-opsawg-coman-probstate-reqs-04
	Abstract		Abstract
	This document provides a problem statement, deployment and management		This document provides a problem statement, deployment and management
	topology options as well as potential requirements for the management		topology options as well as potential requirements for the management
	of networks where constrained devices are involved.		of networks where constrained devices are involved.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	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 April 30, 2015.		This Internet-Draft will expire on July 22, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2015 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
	skipping to change at page 2, line 38		skipping to change at page 2, line 38
	3.7. Energy Management . . . . . . . . . . . . . . . . . . . . 34		3.7. Energy Management . . . . . . . . . . . . . . . . . . . . 34
	3.8. Software Distribution . . . . . . . . . . . . . . . . . . 36		3.8. Software Distribution . . . . . . . . . . . . . . . . . . 36
	3.9. Traffic Management . . . . . . . . . . . . . . . . . . . 36		3.9. Traffic Management . . . . . . . . . . . . . . . . . . . 36
	3.10. Transport Layer . . . . . . . . . . . . . . . . . . . . . 37		3.10. Transport Layer . . . . . . . . . . . . . . . . . . . . . 37
	3.11. Implementation Requirements . . . . . . . . . . . . . . . 39		3.11. Implementation Requirements . . . . . . . . . . . . . . . 39
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 40		5. Security Considerations . . . . . . . . . . . . . . . . . . . 40
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 41		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 41
	7. Informative References . . . . . . . . . . . . . . . . . . . 41		7. Informative References . . . . . . . . . . . . . . . . . . . 41
	Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 42		Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 42
	A.1. draft-ietf-opsawg-coman-probstate-reqs-02 - draft-ietf-		A.1. draft-ietf-opsawg-coman-probstate-reqs-03 - draft-ietf-
			opsawg-coman-probstate-reqs-04 . . . . . . . . . . . . . 42
			A.2. draft-ietf-opsawg-coman-probstate-reqs-02 - draft-ietf-
	opsawg-coman-probstate-reqs-03 . . . . . . . . . . . . . 42		opsawg-coman-probstate-reqs-03 . . . . . . . . . . . . . 42
	A.2. draft-ietf-opsawg-coman-probstate-reqs-01 - draft-ietf-		A.3. draft-ietf-opsawg-coman-probstate-reqs-01 - draft-ietf-
	opsawg-coman-probstate-reqs-02 . . . . . . . . . . . . . 42		opsawg-coman-probstate-reqs-02 . . . . . . . . . . . . . 43
	A.3. draft-ietf-opsawg-coman-probstate-reqs-00 - draft-ietf-		A.4. draft-ietf-opsawg-coman-probstate-reqs-00 - draft-ietf-
	opsawg-coman-probstate-reqs-01 . . . . . . . . . . . . . 43		opsawg-coman-probstate-reqs-01 . . . . . . . . . . . . . 43
	A.4. draft-ersue-constrained-mgmt-03 - draft-ietf-opsawg-		A.5. draft-ersue-constrained-mgmt-03 - draft-ietf-opsawg-
	coman-probstate-reqs-00 . . . . . . . . . . . . . . . . . 43		coman-probstate-reqs-00 . . . . . . . . . . . . . . . . . 44
	A.5. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 44		A.6. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 44
	A.6. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 45		A.7. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 45
	A.7. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 46		A.8. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 46
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46
	1. Introduction		1. Introduction
	1.1. Overview		1.1. Overview
	Constrained devices, aka. sensor, smart object, or smart device, with		Constrained devices, aka. sensor, smart object, or smart device, with
	limited CPU, memory, and power resources, can constitute a network.		limited CPU, memory, and power resources, can constitute a network.
	Such a network of constrained devices itself may be constrained or		Such a network of constrained devices itself may be constrained or
	challenged, e.g., with unreliable or lossy channels, wireless		challenged, e.g., with unreliable or lossy channels, wireless
	skipping to change at page 9, line 9		skipping to change at page 9, line 9
	Networks without bandwidth limitation (e.g., Ethernet) are in-scope		Networks without bandwidth limitation (e.g., Ethernet) are in-scope
	of this document if they are used with constrained devices (see the		of this document if they are used with constrained devices (see the
	use case "Building Automation" in [COM-USE]).		use case "Building Automation" in [COM-USE]).
	Loss rate:		Loss rate:
	The loss rate (or bit error rate) is the number of bit errors divided		The loss rate (or bit error rate) is the number of bit errors divided
	by the total number of bits transmitted. For wired networks, loss		by the total number of bits transmitted. For wired networks, loss
	rates are typically extremely low, e.g., around 10^-12 or 10^-13 for		rates are typically extremely low, e.g., around 10^-12 or 10^-13 for
	the latest 10Gbit Ethernet. For wireless networks, such as 802.15.4,		the latest 10Gbit Ethernet. For wireless networks, such as 802.15.4,
	the bit error rate can be as high as 10^-1 to 10^-0 in case of		the bit error rate can be as high as 10^-1 to 1 in case of
	interferences. Even when using a reliable transport protocol,		interferences. Even when using a reliable transport protocol,
	management operations can fail if the loss rate is too high, unless		management operations can fail if the loss rate is too high, unless
	they are specifically designed to cope with these situations.		they are specifically designed to cope with these situations.
	1.4. Constrained Device Deployment Options		1.4. Constrained Device Deployment Options
	We differentiate following deployment options for the constrained		We differentiate following deployment options for the constrained
	devices:		devices:
	o A network of constrained devices that communicate with each other,		o A network of constrained devices that communicate with each other,
	skipping to change at page 16, line 41		skipping to change at page 16, line 41
	requirements. As such this document avoids selecting any of the		requirements. As such this document avoids selecting any of the
	requirements as mandatory to implement. A device might be able to		requirements as mandatory to implement. A device might be able to
	provide only a particular selected set of requirements and might not		provide only a particular selected set of requirements and might not
	be capable to provide all requirements in this document. On the		be capable to provide all requirements in this document. On the
	other hand a device vendor might select a specific relevant subset of		other hand a device vendor might select a specific relevant subset of
	the requirements to implement.		the requirements to implement.
	The following template is used for the definition of the		The following template is used for the definition of the
	requirements.		requirements.
	Req-ID: An ID uniquely identified by a three-digit number		Req-ID: An ID composed by two numbers: section number indicating the
			topic area and a unique three-digit number per section
	Title: The title of the requirement.		Title: The title of the requirement.
	Description: The rational and description of the requirement.		Description: The rational and description of the requirement.
	Source: The origin of the requirement and the matching use case or		Source: The origin of the requirement and the matching use case or
	application. For the discussion of referred use cases for		application. For the discussion of referred use cases for
	constrained management please see [COM-USE].		constrained management please see [COM-USE].
	Requirement Type: Functional Requirement, Non-Functional		Requirement Type: Functional Requirement, Non-Functional
	skipping to change at page 41, line 31		skipping to change at page 41, line 31
	network may not be sufficient and methods should be investigated that		network may not be sufficient and methods should be investigated that
	provide protection of data while it is cached or stored (e.g., when		provide protection of data while it is cached or stored (e.g., when
	using a store-and-forward transport mechanism).		using a store-and-forward transport mechanism).
	6. Acknowledgments		6. Acknowledgments
	Following persons reviewed and provided valuable comments to		Following persons reviewed and provided valuable comments to
	different versions of this document:		different versions of this document:
	Dominique Barthel, Andy Bierman, Carsten Bormann, Zhen Cao, Benoit		Dominique Barthel, Andy Bierman, Carsten Bormann, Zhen Cao, Benoit
	Claise, Hui Deng, Bert Greevenbosch, Ulrich Herberg, James Nguyen,		Claise, Hui Deng, Bert Greevenbosch, Joel M. Halpern, Ulrich
	Anuj Sehgal, Zach Shelby, Peter van der Stok, Thomas Watteyne, and		Herberg, James Nguyen, Anuj Sehgal, Zach Shelby, Peter van der Stok,
	Bert Wijnen.		Thomas Watteyne, and Bert Wijnen.
	The editors would like to thank the reviewers and the participants on		The editors would like to thank the reviewers and the participants on
	the Coman and OPSAWG mailing lists for their valuable contributions		the Coman and OPSAWG mailing lists for their valuable contributions
	and comments.		and comments.
	7. Informative References		7. Informative References
	[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC		[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC
	2914, September 2000.		2914, September 2000.
	skipping to change at page 42, line 30		skipping to change at page 42, line 30
	Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.		Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.
	Alexander, "RPL: IPv6 Routing Protocol for Low-Power and		Alexander, "RPL: IPv6 Routing Protocol for Low-Power and
	Lossy Networks", RFC 6550, March 2012.		Lossy Networks", RFC 6550, March 2012.
	[COM-USE] Ersue, M., Romascanu, D., and J. Schoenwaelder,		[COM-USE] Ersue, M., Romascanu, D., and J. Schoenwaelder,
	"Constrained Management: Use Cases", draft-ietf-opsawg-		"Constrained Management: Use Cases", draft-ietf-opsawg-
	coman-use-cases (work in progress), July 2014.		coman-use-cases (work in progress), July 2014.
	Appendix A. Change Log		Appendix A. Change Log
	A.1. draft-ietf-opsawg-coman-probstate-reqs-02 - draft-ietf-opsawg-		A.1. draft-ietf-opsawg-coman-probstate-reqs-03 - draft-ietf-opsawg-
			coman-probstate-reqs-04
			o Changed in section 1.3 "10^-0" to "1".
			o Clarified in section 3 how the Requirements ID is composed.
			A.2. draft-ietf-opsawg-coman-probstate-reqs-02 - draft-ietf-opsawg-
	coman-probstate-reqs-03		coman-probstate-reqs-03
	o General bug fixing.		o General bug fixing.
	o Stated in the abstract and introduction section that the		o Stated in the abstract and introduction section that the
	requirements listed in the document are potential requirements.		requirements listed in the document are potential requirements.
	o Added text in section 1.3 to highlight that with the usage of		o Added text in section 1.3 to highlight that with the usage of
	6LowPAN and RPL multi-hop connectivity and dynamic routing can be		6LowPAN and RPL multi-hop connectivity and dynamic routing can be
	achieved.		achieved.
	A.2. draft-ietf-opsawg-coman-probstate-reqs-01 - draft-ietf-opsawg-		A.3. draft-ietf-opsawg-coman-probstate-reqs-01 - draft-ietf-opsawg-
	coman-probstate-reqs-02		coman-probstate-reqs-02
	o General bug fixing.		o General bug fixing.
	o Resolved the use of the term profile of requirements.		o Resolved the use of the term profile of requirements.
	o Changed requirement title from Redirect traffic to Reroute traffic		o Changed requirement title from Redirect traffic to Reroute traffic
	and the description accordingly.		and the description accordingly.
	o Changed requirement title from Traffic delay schemes to Traffic		o Changed requirement title from Traffic delay schemes to Traffic
	Shaping and the description accordingly.		Shaping and the description accordingly.
	o Extended Security Considerations section.		o Extended Security Considerations section.
	o Deleted empty section on Normative References.		o Deleted empty section on Normative References.
	A.3. draft-ietf-opsawg-coman-probstate-reqs-00 - draft-ietf-opsawg-		A.4. draft-ietf-opsawg-coman-probstate-reqs-00 - draft-ietf-opsawg-
	coman-probstate-reqs-01		coman-probstate-reqs-01
	o General bug fixing.		o General bug fixing.
	o Added Section 1.7. on Configuration and Monitoring Functionality		o Added Section 1.7. on Configuration and Monitoring Functionality
	Levels.		Levels.
	o Changed diverse occurences of "networks" to "networks with/of		o Changed diverse occurences of "networks" to "networks with/of
	constrained devices".		constrained devices".
	skipping to change at page 43, line 39		skipping to change at page 44, line 5
	o Introduced notes for parts of the requirements text if it is		o Introduced notes for parts of the requirements text if it is
	focusing on implementation or solution.		focusing on implementation or solution.
	o Extended Security Considerations section.		o Extended Security Considerations section.
	o Deleted Appendix A and B on other SDO's work and related projects		o Deleted Appendix A and B on other SDO's work and related projects
	as they provided dynamic information and couldn't be kept up-to-		as they provided dynamic information and couldn't be kept up-to-
	date.		date.
	A.4. draft-ersue-constrained-mgmt-03 - draft-ietf-opsawg-coman-		A.5. draft-ersue-constrained-mgmt-03 - draft-ietf-opsawg-coman-
	probstate-reqs-00		probstate-reqs-00
	o Reduced the terminology section for terminology addressed in the		o Reduced the terminology section for terminology addressed in the
	LWIG terminology draft. Referenced the LWIG terminology draft.		LWIG terminology draft. Referenced the LWIG terminology draft.
	o Checked and aligned all terminology against the LWIG terminology		o Checked and aligned all terminology against the LWIG terminology
	draft.		draft.
	o Moved section 1.4. Constrained Device Deployment Options and		o Moved section 1.4. Constrained Device Deployment Options and
	section 3. Use Cases to the companion document [COM-USE].		section 3. Use Cases to the companion document [COM-USE].
	skipping to change at page 44, line 16		skipping to change at page 44, line 28
	in Focus" and removed abbreviations C0, C1 and C2 for network		in Focus" and removed abbreviations C0, C1 and C2 for network
	classes as they have not been used.		classes as they have not been used.
	o Changed requirement priority classes to be High, Medium and Low.		o Changed requirement priority classes to be High, Medium and Low.
	o Changed requirement types to be Functional and Non-Functional and		o Changed requirement types to be Functional and Non-Functional and
	added text to explain the requirement types.		added text to explain the requirement types.
	o Reformulation of some text parts for more clarity.		o Reformulation of some text parts for more clarity.
	A.5. draft-ersue-constrained-mgmt-02-03		A.6. draft-ersue-constrained-mgmt-02-03
	o Extended the terminology section and removed some of the		o Extended the terminology section and removed some of the
	terminology addressed in the new LWIG terminology draft.		terminology addressed in the new LWIG terminology draft.
	Referenced the LWIG terminology draft.		Referenced the LWIG terminology draft.
	o Moved Section 1.3. on Constrained Device Classes to the new LWIG		o Moved Section 1.3. on Constrained Device Classes to the new LWIG
	terminology draft.		terminology draft.
	o Class of networks considering the different type of radio and		o Class of networks considering the different type of radio and
	communication technologies in use and dimensions extended.		communication technologies in use and dimensions extended.
	skipping to change at page 45, line 15		skipping to change at page 45, line 26
	* Software distribution (group-based firmware update) and Group-		* Software distribution (group-based firmware update) and Group-
	based provisioning.		based provisioning.
	o Deleted the empty section on the gaps in network management		o Deleted the empty section on the gaps in network management
	standards, as it will be written in a separate draft.		standards, as it will be written in a separate draft.
	o Added links to mentioned external pages.		o Added links to mentioned external pages.
	o Added text on OMA M2M Device Classification in appendix.		o Added text on OMA M2M Device Classification in appendix.
	A.6. draft-ersue-constrained-mgmt-01-02		A.7. draft-ersue-constrained-mgmt-01-02
	o Extended the terminology section.		o Extended the terminology section.
	o Added additional text for the use cases concerning deployment		o Added additional text for the use cases concerning deployment
	type, network topology in use, network size, network capabilities,		type, network topology in use, network size, network capabilities,
	radio technology, etc.		radio technology, etc.
	o Added examples for device classes in a use case.		o Added examples for device classes in a use case.
	o Added additional text provided by Cao Zhen (China Mobile) for		o Added additional text provided by Cao Zhen (China Mobile) for
	skipping to change at page 46, line 5		skipping to change at page 46, line 13
	management matched to management tasks like fault, monitoring,		management matched to management tasks like fault, monitoring,
	configuration management, Security and Access Control, Energy		configuration management, Security and Access Control, Energy
	Management, etc.		Management, etc.
	o Solved nits and added references.		o Solved nits and added references.
	o Added Appendix A on the related development in other bodies.		o Added Appendix A on the related development in other bodies.
	o Added Appendix B on the work in related research projects.		o Added Appendix B on the work in related research projects.
	A.7. draft-ersue-constrained-mgmt-00-01		A.8. draft-ersue-constrained-mgmt-00-01
	o Splitted the section on 'Networks of Constrained Devices' into the		o Splitted the section on 'Networks of Constrained Devices' into the
	sections 'Network Topology Options' and 'Management Topology		sections 'Network Topology Options' and 'Management Topology
	Options'.		Options'.
	o Added the use case 'Community Network Applications' and 'Mobile		o Added the use case 'Community Network Applications' and 'Mobile
	Applications'.		Applications'.
	o Provided a Contributors section.		o Provided a Contributors section.
End of changes. 18 change blocks.
	26 lines changed or deleted		36 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/