draft-ietf-opsawg-coman-probstate-reqs-04.txt   draft-ietf-opsawg-coman-probstate-reqs-05.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: July 22, 2015 Avaya Expires: September 2, 2015 Avaya
J. Schoenwaelder J. Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
U. Herberg U. Herberg
March 1, 2015
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-04 draft-ietf-opsawg-coman-probstate-reqs-05
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 requirements addressing the different use
of networks where constrained devices are involved. cases of the management 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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 July 22, 2015. This Internet-Draft will expire on September 2, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
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-03 - draft-ietf- A.1. draft-ietf-opsawg-coman-probstate-reqs-04 - draft-ietf-
opsawg-coman-probstate-reqs-05 . . . . . . . . . . . . . 42
A.2. draft-ietf-opsawg-coman-probstate-reqs-03 - draft-ietf-
opsawg-coman-probstate-reqs-04 . . . . . . . . . . . . . 42 opsawg-coman-probstate-reqs-04 . . . . . . . . . . . . . 42
A.2. draft-ietf-opsawg-coman-probstate-reqs-02 - draft-ietf- A.3. draft-ietf-opsawg-coman-probstate-reqs-02 - draft-ietf-
opsawg-coman-probstate-reqs-03 . . . . . . . . . . . . . 42 opsawg-coman-probstate-reqs-03 . . . . . . . . . . . . . 42
A.3. draft-ietf-opsawg-coman-probstate-reqs-01 - draft-ietf- A.4. draft-ietf-opsawg-coman-probstate-reqs-01 - draft-ietf-
opsawg-coman-probstate-reqs-02 . . . . . . . . . . . . . 43 opsawg-coman-probstate-reqs-02 . . . . . . . . . . . . . 43
A.4. draft-ietf-opsawg-coman-probstate-reqs-00 - draft-ietf- A.5. draft-ietf-opsawg-coman-probstate-reqs-00 - draft-ietf-
opsawg-coman-probstate-reqs-01 . . . . . . . . . . . . . 43 opsawg-coman-probstate-reqs-01 . . . . . . . . . . . . . 43
A.5. draft-ersue-constrained-mgmt-03 - draft-ietf-opsawg- A.6. draft-ersue-constrained-mgmt-03 - draft-ietf-opsawg-
coman-probstate-reqs-00 . . . . . . . . . . . . . . . . . 44 coman-probstate-reqs-00 . . . . . . . . . . . . . . . . . 44
A.6. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 44 A.7. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 44
A.7. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 45 A.8. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 45
A.8. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 46 A.9. 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 4, line 15 skipping to change at page 4, line 18
The IETF has already done substantial standardization work to enable The IETF has already done substantial standardization work to enable
the communication in IP networks and to manage such networks as well the communication in IP networks and to manage such networks as well
as the manifold type of nodes in these networks [RFC6632]. However, as the manifold type of nodes in these networks [RFC6632]. However,
the IETF so far has not developed any specific technologies for the the IETF so far has not developed any specific technologies for the
management of constrained devices and the networks comprised by management of constrained devices and the networks comprised by
constrained devices. IP-based sensors or constrained devices in such constrained devices. IP-based sensors or constrained devices in such
an environment, i.e., devices with very limited memory, CPU, and an environment, i.e., devices with very limited memory, CPU, and
energy resources, use nowadays application-layer protocols in an ad- energy resources, use nowadays application-layer protocols in an ad-
hoc manner to do simple resource management and monitoring. hoc manner to do simple resource management and monitoring.
This document provides a problem statement and lists potential This document provides a problem statement and lists requirements for
requirements for the management of a network with constrained the different use cases of management of a network with constrained
devices. Section 1.3 and Section 1.5 describe different topology devices. Section 1.3 and Section 1.5 describe different topology
options for the networking and management of constrained devices. options for the networking and management of constrained devices.
Section 2 provides a problem statement on the issue of the management Section 2 provides a problem statement on the issue of the management
of networked constrained devices. Section 3 lists requirements on of networked constrained devices. Section 3 lists requirements on
the management of applications and networks with constrained devices. the management of applications and networks with constrained devices.
Note that the requirements listed in Section 3 have been separated Note that the requirements listed in Section 3 have been separated
from the context in which they may appear. Depending on the concrete from the context in which they may appear. Depending on the concrete
circumstances, an implementer may decide to address a certain circumstances, an implementer may decide to address a certain
relevant subset of the requirements. relevant subset of the requirements.
The use cases in the context of networks with constrained devices can The use cases in the context of networks with constrained devices can
be found in the companion document [COM-USE]. be found in the companion document [COM-USE]. This informational
document provides a list of objectives for discussions and does not
aim to be a strict requirements document for all use cases. In fact,
there likely is not a single solution that works equally well for all
the use cases.
1.2. Terminology 1.2. Terminology
Concerning constrained devices and networks this document generally Concerning constrained devices and networks this document generally
builds on the terminology defined in [RFC7228], where the terms builds on the terminology defined in [RFC7228], where the terms
Constrained Device, Constrained Network, etc. are defined. Constrained Device, Constrained Network, etc. are defined.
The following terms are additionally used throughout this The following terms are additionally used throughout this
documentation: documentation:
skipping to change at page 40, line 49 skipping to change at page 40, line 49
5. Security Considerations 5. Security Considerations
This document discusses the problem statement and requirements on This document discusses the problem statement and requirements on
networks of constrained devices. Section 1.6 mentions a number of networks of constrained devices. Section 1.6 mentions a number of
limitations that could prevent the implementation of strong limitations that could prevent the implementation of strong
cryptographic algorithms. Requirements for security and access cryptographic algorithms. Requirements for security and access
control are listed in Section 3.6. control are listed in Section 3.6.
Constrained devices might be deployed often in unsafe environments, Constrained devices might be deployed often in unsafe environments,
where attackers can gain physical access to the devices. As a where attackers can gain physical access to the devices. As a
consequence, it is crucial to properly protect any security consequence, it is crucial that devices are robust and tamper
resistant, have no backdoors, do not provide services that are not
essential for the primary function, and properly protect any security
credentials that may be stored on the device (e.g., by using hardware credentials that may be stored on the device (e.g., by using hardware
protection mechanisms). Furthermore, it is important that any protection mechanisms). Furthermore, it is important that any
credentials leaking from a single device do not simplify the attack credentials leaking from a single device do not simplify the attack
on other (similar) devices. In particular, security credentials on other (similar) devices. In particular, security credentials
should never be shared. should never be shared.
Since constrained devices often have limited computational resources, Since constrained devices often have limited computational resources,
care should be taken in choosing efficient but cryptographically care should be taken in choosing efficient but cryptographically
strong cryptographic algorithms. Designers of constrained devices strong cryptographic algorithms. Designers of constrained devices
that have a long expected lifetime need to ensure that cryptographic that have a long expected lifetime need to ensure that cryptographic
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-03 - draft-ietf-opsawg- A.1. draft-ietf-opsawg-coman-probstate-reqs-04 - draft-ietf-opsawg-
coman-probstate-reqs-05
o Extended Abstract and Overview sections to clarify the type of
requirements the draft describes.
o Extended security highlighting the devices should make sure
credentials are properly protected.
A.2. draft-ietf-opsawg-coman-probstate-reqs-03 - draft-ietf-opsawg-
coman-probstate-reqs-04 coman-probstate-reqs-04
o Changed in section 1.3 "10^-0" to "1". o Changed in section 1.3 "10^-0" to "1".
o Clarified in section 3 how the Requirements ID is composed. o Clarified in section 3 how the Requirements ID is composed.
A.2. draft-ietf-opsawg-coman-probstate-reqs-02 - draft-ietf-opsawg- A.3. 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.3. draft-ietf-opsawg-coman-probstate-reqs-01 - draft-ietf-opsawg- A.4. 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.4. draft-ietf-opsawg-coman-probstate-reqs-00 - draft-ietf-opsawg- A.5. 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 44, line 5 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.5. draft-ersue-constrained-mgmt-03 - draft-ietf-opsawg-coman- A.6. 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 28 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.6. draft-ersue-constrained-mgmt-02-03 A.7. 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 26 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.7. draft-ersue-constrained-mgmt-01-02 A.8. 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 13 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.8. draft-ersue-constrained-mgmt-00-01 A.9. 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. 22 change blocks. 
27 lines changed or deleted 44 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/