draft-ietf-opsawg-coman-use-cases-03.txt   draft-ietf-opsawg-coman-use-cases-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 23, 2015 Avaya
J. Schoenwaelder J. Schoenwaelder
A. Sehgal A. Sehgal
Jacobs University Bremen Jacobs University Bremen
October 27, 2014 January 19, 2015
Management of Networks with Constrained Devices: Use Cases Management of Networks with Constrained Devices: Use Cases
draft-ietf-opsawg-coman-use-cases-03 draft-ietf-opsawg-coman-use-cases-04
Abstract Abstract
This document discusses use cases concerning the management of This document discusses use cases concerning the management of
networks, where constrained devices are involved. A problem networks, where constrained devices are involved. A problem
statement, deployment options and the requirements on the networks statement, deployment options and the requirements on the networks
with constrained devices can be found in the companion document on with constrained devices can be found in the companion document on
"Management of Networks with Constrained Devices: Problem Statement "Management of Networks with Constrained Devices: Problem Statement
and Requirements". and Requirements".
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 23, 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
4.7. Home Automation . . . . . . . . . . . . . . . . . . . . . 16 4.7. Home Automation . . . . . . . . . . . . . . . . . . . . . 16
4.8. Transport Applications . . . . . . . . . . . . . . . . . 17 4.8. Transport Applications . . . . . . . . . . . . . . . . . 17
4.9. Community Network Applications . . . . . . . . . . . . . 19 4.9. Community Network Applications . . . . . . . . . . . . . 19
4.10. Field Operations . . . . . . . . . . . . . . . . . . . . 21 4.10. Field Operations . . . . . . . . . . . . . . . . . . . . 21
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
6. Security Considerations . . . . . . . . . . . . . . . . . . . 22 6. Security Considerations . . . . . . . . . . . . . . . . . . . 22
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
9. Informative References . . . . . . . . . . . . . . . . . . . 23 9. Informative References . . . . . . . . . . . . . . . . . . . 23
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 24 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 24
A.1. draft-ietf-opsawg-coman-use-cases-02 - draft-ietf-opsawg- A.1. draft-ietf-opsawg-coman-use-cases-03 - draft-ietf-opsawg-
coman-use-cases-04 . . . . . . . . . . . . . . . . . . . 24
A.2. draft-ietf-opsawg-coman-use-cases-02 - draft-ietf-opsawg-
coman-use-cases-03 . . . . . . . . . . . . . . . . . . . 24 coman-use-cases-03 . . . . . . . . . . . . . . . . . . . 24
A.2. draft-ietf-opsawg-coman-use-cases-01 - draft-ietf-opsawg- A.3. draft-ietf-opsawg-coman-use-cases-01 - draft-ietf-opsawg-
coman-use-cases-02 . . . . . . . . . . . . . . . . . . . 25 coman-use-cases-02 . . . . . . . . . . . . . . . . . . . 25
A.3. draft-ietf-opsawg-coman-use-cases-00 - draft-ietf-opsawg- A.4. draft-ietf-opsawg-coman-use-cases-00 - draft-ietf-opsawg-
coman-use-cases-01 . . . . . . . . . . . . . . . . . . . 26 coman-use-cases-01 . . . . . . . . . . . . . . . . . . . 26
A.4. draft-ersue-constrained-mgmt-03 - draft-ersue-opsawg- A.5. draft-ersue-constrained-mgmt-03 - draft-ersue-opsawg-
coman-use-cases-00 . . . . . . . . . . . . . . . . . . . 26 coman-use-cases-00 . . . . . . . . . . . . . . . . . . . 26
A.5. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 27 A.6. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 27
A.6. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 28 A.7. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 28
A.7. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 28 A.8. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
Small devices with limited CPU, memory, and power resources, so Small devices with limited CPU, memory, and power resources, so
called constrained devices (aka. sensor, smart object, or smart called constrained devices (aka. sensor, smart object, or smart
device) can be connected to a network. Such a network of constrained device) can be connected to a network. Such a network of constrained
devices itself may be constrained or challenged, e.g., with devices itself may be constrained or challenged, e.g., with
unreliable or lossy channels, wireless technologies with limited unreliable or lossy channels, wireless technologies with limited
bandwidth and a dynamic topology, needing the service of a gateway or bandwidth and a dynamic topology, needing the service of a gateway or
skipping to change at page 12, line 4 skipping to change at page 12, line 4
4.4. Energy Management 4.4. Energy Management
The EMAN working group developed an energy management framework The EMAN working group developed an energy management framework
[RFC7326] for devices and device components within or connected to [RFC7326] for devices and device components within or connected to
communication networks. This document observes that one of the communication networks. This document observes that one of the
challenges of energy management is that a power distribution network challenges of energy management is that a power distribution network
is responsible for the supply of energy to various devices and is responsible for the supply of energy to various devices and
components, while a separate communication network is typically used components, while a separate communication network is typically used
to monitor and control the power distribution network. Devices in to monitor and control the power distribution network. Devices in
the context of energy management can be monitored for parameters like the context of energy management can be monitored for parameters like
Power, Energy, Demand and Power Quality. If a device contains power, energy, demand and power quality. If a device contains
batteries, they can be also monitored and managed. batteries, they can be also monitored and managed.
Energy devices differ in complexity and may include basic sensors or Energy devices differ in complexity and may include basic sensors or
switches, specialized electrical meters, or power distribution units switches, specialized electrical meters, or power distribution units
(PDU), and subsystems inside the network devices (routers, network (PDU), and subsystems inside the network devices (routers, network
switches) or home or industrial appliances. The operators of an switches) or home or industrial appliances. The operators of an
Energy Management System are either the utility providers or Energy Management System are either the utility providers or
customers that aim to control and reduce the energy consumption and customers that aim to control and reduce the energy consumption and
the associated costs. The topology in use differs and the deployment the associated costs. The topology in use differs and the deployment
can cover areas from small surfaces (individual homes) to large can cover areas from small surfaces (individual homes) to large
geographical areas. The EMAN requirements document [RFC6988] geographical areas. The EMAN requirements document [RFC6988]
discusses the requirements for energy management concerning discusses the requirements for energy management concerning
monitoring and control functions. monitoring and control functions.
It is assumed that Energy Management will apply to a large range of It is assumed that energy management will apply to a large range of
devices of all classes and networks topologies. Specific resource devices of all classes and networks topologies. Specific resource
monitoring like battery utilization and availability may be specific monitoring like battery utilization and availability may be specific
to devices with lower physical resources (device classes C0 or C1 to devices with lower physical resources (device classes C0 or C1
[RFC7228]). [RFC7228]).
Energy Management is especially relevant to the Smart Grid. A Smart Energy management is especially relevant to the Smart Grid. A Smart
Grid is an electrical grid that uses data networks to gather and to Grid is an electrical grid that uses data networks to gather and to
act on energy and power-related information in an automated fashion act on energy and power-related information in an automated fashion
with the goal to improve the efficiency, reliability, economics, and with the goal to improve the efficiency, reliability, economics, and
sustainability of the production and distribution of electricity. sustainability of the production and distribution of electricity.
Smart Metering is a good example of Smart Grid based Energy Smart Metering is a good example of Smart Grid based energy
Management applications. Different types of possibly wireless small management applications. Different types of possibly wireless small
meters produce all together a large amount of data, which is meters produce all together a large amount of data, which is
collected by a central entity and processed by an application server, collected by a central entity and processed by an application server,
which may be located within the customer's residence or off-site in a which may be located within the customer's residence or off-site in a
data-center. The communication infrastructure can be provided by a data-center. The communication infrastructure can be provided by a
mobile network operator as the meters in urban areas will have most mobile network operator as the meters in urban areas will have most
likely a cellular or WiMAX radio. In case the application server is likely a cellular or WiMAX radio. In case the application server is
located within the residence, such meters are more likely to use Wi- located within the residence, such meters are more likely to use Wi-
Fi protocols to interconnect with an existing network. Fi protocols to interconnect with an existing network.
An Advanced Metering Infrastructure (AMI) network is another example An Advanced Metering Infrastructure (AMI) network is another example
skipping to change at page 16, line 8 skipping to change at page 16, line 8
devices, there might be a need to certify components and subsystems devices, there might be a need to certify components and subsystems
operating in such constrained conditions based on specific operating in such constrained conditions based on specific
requirements. Also in some environments, the malfunctioning of a requirements. Also in some environments, the malfunctioning of a
control system (like temperature control) needs to be reported in the control system (like temperature control) needs to be reported in the
shortest possible time. Complex control systems can misbehave, and shortest possible time. Complex control systems can misbehave, and
their critical status reporting and safety algorithms need to be their critical status reporting and safety algorithms need to be
basic and robust and perform even in critical conditions. Providing basic and robust and perform even in critical conditions. Providing
this monitoring, configuration and notification service is an this monitoring, configuration and notification service is an
important task of the management system used in building automation. important task of the management system used in building automation.
Building Automation solutions are deployed in some cases in newly Building automation solutions are deployed in some cases in newly
designed buildings, in other cases it might be over existing designed buildings, in other cases it might be over existing
infrastructures. In the first case, there is a broader range of infrastructures. In the first case, there is a broader range of
possible solutions, which can be planned for the infrastructure of possible solutions, which can be planned for the infrastructure of
the building. In the second case the solution needs to be deployed the building. In the second case the solution needs to be deployed
over an existing infrastructure taking into account factors like over an existing infrastructure taking into account factors like
existing wiring, distance limitations, the propagation of radio existing wiring, distance limitations, the propagation of radio
signals over walls and floors, thereby making deployment difficult. signals over walls and floors, thereby making deployment difficult.
As a result, some of the existing WLAN solutions (e.g., IEEE 802.11 As a result, some of the existing WLAN solutions (e.g., IEEE 802.11
or IEEE 802.15) may be deployed. In mission-critical or security or IEEE 802.15) may be deployed. In mission-critical or security
sensitive environments and in cases where link failures happen often, sensitive environments and in cases where link failures happen often,
skipping to change at page 17, line 27 skipping to change at page 17, line 27
The management responsibility lies either with the residents or it The management responsibility lies either with the residents or it
may be outsourced to electricians and/or third parties providing may be outsourced to electricians and/or third parties providing
management of home automation solutions as a service. A varying management of home automation solutions as a service. A varying
combination of electricians, service providers or the residents may combination of electricians, service providers or the residents may
be responsible for different aspects of managing the infrastructure. be responsible for different aspects of managing the infrastructure.
The time scale for failure detection and resolution is in many cases The time scale for failure detection and resolution is in many cases
likely counted in hours to days. likely counted in hours to days.
4.8. Transport Applications 4.8. Transport Applications
Transport Application is a generic term for the integrated Transport application is a generic term for the integrated
application of communications, control, and information processing in application of communications, control, and information processing in
a transportation system. Transport telematics or vehicle telematics a transportation system. Transport telematics or vehicle telematics
are used as a term for the group of technologies that support are used as a term for the group of technologies that support
transportation systems. Transport applications running on such a transportation systems. Transport applications running on such a
transportation system cover all modes of the transport and consider transportation system cover all modes of the transport and consider
all elements of the transportation system, i.e. the vehicle, the all elements of the transportation system, i.e. the vehicle, the
infrastructure, and the driver or user, interacting together infrastructure, and the driver or user, interacting together
dynamically. Examples for transport applications are inter and intra dynamically. Examples for transport applications are inter and intra
vehicular communication, smart traffic control, smart parking, vehicular communication, smart traffic control, smart parking,
electronic toll collection systems, logistic and fleet management, electronic toll collection systems, logistic and fleet management,
skipping to change at page 22, line 38 skipping to change at page 22, line 38
5. IANA Considerations 5. IANA Considerations
This document does not introduce any new code-points or namespaces This document does not introduce any new code-points or namespaces
for registration with IANA. for registration with IANA.
Note to RFC Editor: this section may be removed on publication as an Note to RFC Editor: this section may be removed on publication as an
RFC. RFC.
6. Security Considerations 6. Security Considerations
This document discusses use cases for Management of Networks with This document discusses use cases for management of networks with
Constrained Devices. The security considerations described constrained devices. The security considerations described
throughout the companion document [COM-REQ] apply here as well. throughout the companion document [COM-REQ] apply here as well.
7. Contributors 7. Contributors
Following persons made significant contributions to and reviewed this Following persons made significant contributions to and reviewed this
document: document:
o Ulrich Herberg (Fujitsu Laboratories of America) contributed the o Ulrich Herberg contributed the Section 4.9 on Community Network
Section 4.9 on Community Network Applications. Applications.
o Peter van der Stok contributed to Section 4.6 on Building o Peter van der Stok contributed to Section 4.6 on Building
Automation. Automation.
o Zhen Cao contributed to Section 2.2 Cellular Access Technologies. o Zhen Cao contributed to Section 2.2 Cellular Access Technologies.
o Gilman Tolle contributed the Section 4.4 on Automated Metering o Gilman Tolle contributed the Section 4.4 on Automated Metering
Infrastructure. Infrastructure.
o James Nguyen and Ulrich Herberg contributed to Section 4.10 on o James Nguyen and Ulrich Herberg contributed to Section 4.10 on
Military operations. Military operations.
8. Acknowledgments 8. 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, Carsten Bormann, Zhen Cao, Benoit Claise, Bert Dominique Barthel, Carsten Bormann, Zhen Cao, Benoit Claise, Bert
Greevenbosch, Ulrich Herberg, James Nguyen, Zach Shelby, and Peter Greevenbosch, Ulrich Herberg, James Nguyen, Zach Shelby, Peter van
van der Stok. der Stok, and Martin Thomson.
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 maillist for their valuable contributions and comments. the Coman maillist for their valuable contributions and comments.
9. Informative References 9. Informative References
[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.
skipping to change at page 24, line 17 skipping to change at page 24, line 17
Statement and Requirements", draft-ietf-opsawg-coman- Statement and Requirements", draft-ietf-opsawg-coman-
probstate-reqs (work in progress), February 2014. probstate-reqs (work in progress), February 2014.
[IOT-SEC] Garcia-Morchon, O., Kumar, S., Keoh, S., Hummen, R., and [IOT-SEC] Garcia-Morchon, O., Kumar, S., Keoh, S., Hummen, R., and
R. Struik, "Security Considerations in the IP-based R. Struik, "Security Considerations in the IP-based
Internet of Things", draft-garcia-core-security-06 (work Internet of Things", draft-garcia-core-security-06 (work
in progress), September 2013. in progress), September 2013.
Appendix A. Change Log Appendix A. Change Log
A.1. draft-ietf-opsawg-coman-use-cases-02 - draft-ietf-opsawg-coman- A.1. draft-ietf-opsawg-coman-use-cases-03 - draft-ietf-opsawg-coman-
use-cases-04
o Resolved Gen-ART review comments received from Martin Thomson.
o Deleted company name for the list of contributors.
o Added Martin Thomson to Acknowledgments section.
A.2. draft-ietf-opsawg-coman-use-cases-02 - draft-ietf-opsawg-coman-
use-cases-03 use-cases-03
o Updated references to take into account RFCs that have now been o Updated references to take into account RFCs that have now been
published published
o Added text to the access technologies section explaining why fixed o Added text to the access technologies section explaining why fixed
line technologies (e.g., powerline communications) have not been line technologies (e.g., powerline communications) have not been
discussed. discussed.
o Created a new section, Device Lifecycle, discussing the impact of o Created a new section, Device Lifecycle, discussing the impact of
skipping to change at page 25, line 5 skipping to change at page 25, line 11
o Clarified the meaning of unreliability in context of constrained o Clarified the meaning of unreliability in context of constrained
devices and networks. devices and networks.
o Added information regarding the configuration and operation of o Added information regarding the configuration and operation of
factory automation use case, based on the type of information factory automation use case, based on the type of information
provided in the building automation use case. provided in the building automation use case.
o Fixed editorial issues discovered by reviewers. o Fixed editorial issues discovered by reviewers.
A.2. draft-ietf-opsawg-coman-use-cases-01 - draft-ietf-opsawg-coman- A.3. draft-ietf-opsawg-coman-use-cases-01 - draft-ietf-opsawg-coman-
use-cases-02 use-cases-02
o Renamed Mobile Access Technologies section to Cellular Access o Renamed Mobile Access Technologies section to Cellular Access
Technologies Technologies
o Changed references to mobile access technologies to now read o Changed references to mobile access technologies to now read
cellular access technologies. cellular access technologies.
o Added text to the introduction to point out that the list of use o Added text to the introduction to point out that the list of use
cases is not exhaustive since others unknown to the authors might cases is not exhaustive since others unknown to the authors might
skipping to change at page 26, line 25 skipping to change at page 26, line 31
* Expanded proprietary systems to "systems relying on a specific * Expanded proprietary systems to "systems relying on a specific
Management Topology Option, as described in [COM-REQ]." within Management Topology Option, as described in [COM-REQ]." within
Vehicular Networks section. Vehicular Networks section.
* Added text regarding mobility patterns to Vehicular Networks. * Added text regarding mobility patterns to Vehicular Networks.
o Changed the Military Operations use case to Field Operations and o Changed the Military Operations use case to Field Operations and
edited the text to be suitable to such scenarios. edited the text to be suitable to such scenarios.
A.3. draft-ietf-opsawg-coman-use-cases-00 - draft-ietf-opsawg-coman- A.4. draft-ietf-opsawg-coman-use-cases-00 - draft-ietf-opsawg-coman-
use-cases-01 use-cases-01
o Reordered some use cases to improve the flow. o Reordered some use cases to improve the flow.
o Added "Vehicular Networks". o Added "Vehicular Networks".
o Shortened the Military Operations use case. o Shortened the Military Operations use case.
o Started adding substance to the security considerations section. o Started adding substance to the security considerations section.
A.4. draft-ersue-constrained-mgmt-03 - draft-ersue-opsawg-coman-use- A.5. draft-ersue-constrained-mgmt-03 - draft-ersue-opsawg-coman-use-
cases-00 cases-00
o Reduced the terminology section for terminology addressed in the o Reduced the terminology section for terminology addressed in the
LWIG and Coman Requirements drafts. Referenced the other drafts. LWIG and Coman Requirements drafts. Referenced the other drafts.
o Checked and aligned all terminology against the LWIG terminology o Checked and aligned all terminology against the LWIG terminology
draft. draft.
o Spent some effort to resolve the intersection between the o Spent some effort to resolve the intersection between the
Industrial Application, Home Automation and Building Automation Industrial Application, Home Automation and Building Automation
use cases. use cases.
o Moved section section 3. Use Cases from the companion document o Moved section section 3. Use Cases from the companion document
[COM-REQ] to this draft. [COM-REQ] to this draft.
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 28, line 5 skipping to change at page 28, line 12
* 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 28, line 40 skipping to change at page 28, line 47
constrained management matched to management tasks like fault, constrained management matched to management tasks like fault,
monitoring, configuration management, Security and Access Control, monitoring, configuration management, Security and Access Control,
Energy Management, etc. Energy 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. 26 change blocks. 
32 lines changed or deleted 43 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/