draft-ietf-opsawg-coman-use-cases-04.txt   draft-ietf-opsawg-coman-use-cases-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 23, 2015 Avaya Expires: September 2, 2015 Avaya
J. Schoenwaelder J. Schoenwaelder
A. Sehgal A. Sehgal
Jacobs University Bremen Jacobs University Bremen
January 19, 2015 March 1, 2015
Management of Networks with Constrained Devices: Use Cases Management of Networks with Constrained Devices: Use Cases
draft-ietf-opsawg-coman-use-cases-04 draft-ietf-opsawg-coman-use-cases-05
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 July 23, 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 23 skipping to change at page 2, line 23
2. Access Technologies . . . . . . . . . . . . . . . . . . . . . 4 2. Access Technologies . . . . . . . . . . . . . . . . . . . . . 4
2.1. Constrained Access Technologies . . . . . . . . . . . . . 4 2.1. Constrained Access Technologies . . . . . . . . . . . . . 4
2.2. Cellular Access Technologies . . . . . . . . . . . . . . 5 2.2. Cellular Access Technologies . . . . . . . . . . . . . . 5
3. Device Lifecycle . . . . . . . . . . . . . . . . . . . . . . 6 3. Device Lifecycle . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Manufacturing and Initial Testing . . . . . . . . . . . . 6 3.1. Manufacturing and Initial Testing . . . . . . . . . . . . 6
3.2. Installation and Configuration . . . . . . . . . . . . . 6 3.2. Installation and Configuration . . . . . . . . . . . . . 6
3.3. Operation and Maintenance . . . . . . . . . . . . . . . . 7 3.3. Operation and Maintenance . . . . . . . . . . . . . . . . 7
3.4. Recommissioning and Decommissioning . . . . . . . . . . . 7 3.4. Recommissioning and Decommissioning . . . . . . . . . . . 7
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Environmental Monitoring . . . . . . . . . . . . . . . . 8 4.1. Environmental Monitoring . . . . . . . . . . . . . . . . 8
4.2. Infrastructure Monitoring . . . . . . . . . . . . . . . . 8 4.2. Infrastructure Monitoring . . . . . . . . . . . . . . . . 9
4.3. Industrial Applications . . . . . . . . . . . . . . . . . 9 4.3. Industrial Applications . . . . . . . . . . . . . . . . . 10
4.4. Energy Management . . . . . . . . . . . . . . . . . . . . 11 4.4. Energy Management . . . . . . . . . . . . . . . . . . . . 12
4.5. Medical Applications . . . . . . . . . . . . . . . . . . 13 4.5. Medical Applications . . . . . . . . . . . . . . . . . . 14
4.6. Building Automation . . . . . . . . . . . . . . . . . . . 14 4.6. Building Automation . . . . . . . . . . . . . . . . . . . 15
4.7. Home Automation . . . . . . . . . . . . . . . . . . . . . 16 4.7. Home Automation . . . . . . . . . . . . . . . . . . . . . 17
4.8. Transport Applications . . . . . . . . . . . . . . . . . 17 4.8. Transport Applications . . . . . . . . . . . . . . . . . 18
4.9. Community Network Applications . . . . . . . . . . . . . 19 4.9. Community Network Applications . . . . . . . . . . . . . 20
4.10. Field Operations . . . . . . . . . . . . . . . . . . . . 21 4.10. Field Operations . . . . . . . . . . . . . . . . . . . . 22
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
6. Security Considerations . . . . . . . . . . . . . . . . . . . 22 6. Security Considerations . . . . . . . . . . . . . . . . . . . 24
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 24
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 24
9. Informative References . . . . . . . . . . . . . . . . . . . 23 9. Informative References . . . . . . . . . . . . . . . . . . . 24
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 24 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 25
A.1. draft-ietf-opsawg-coman-use-cases-03 - draft-ietf-opsawg- A.1. draft-ietf-opsawg-coman-use-cases-04 - draft-ietf-opsawg-
coman-use-cases-04 . . . . . . . . . . . . . . . . . . . 24 coman-use-cases-05 . . . . . . . . . . . . . . . . . . . 25
A.2. draft-ietf-opsawg-coman-use-cases-02 - draft-ietf-opsawg- A.2. draft-ietf-opsawg-coman-use-cases-03 - draft-ietf-opsawg-
coman-use-cases-03 . . . . . . . . . . . . . . . . . . . 24 coman-use-cases-04 . . . . . . . . . . . . . . . . . . . 26
A.3. draft-ietf-opsawg-coman-use-cases-01 - draft-ietf-opsawg- A.3. draft-ietf-opsawg-coman-use-cases-02 - draft-ietf-opsawg-
coman-use-cases-02 . . . . . . . . . . . . . . . . . . . 25 coman-use-cases-03 . . . . . . . . . . . . . . . . . . . 26
A.4. draft-ietf-opsawg-coman-use-cases-00 - draft-ietf-opsawg- A.4. draft-ietf-opsawg-coman-use-cases-01 - draft-ietf-opsawg-
coman-use-cases-01 . . . . . . . . . . . . . . . . . . . 26 coman-use-cases-02 . . . . . . . . . . . . . . . . . . . 26
A.5. draft-ersue-constrained-mgmt-03 - draft-ersue-opsawg- A.5. draft-ietf-opsawg-coman-use-cases-00 - draft-ietf-opsawg-
coman-use-cases-00 . . . . . . . . . . . . . . . . . . . 26 coman-use-cases-01 . . . . . . . . . . . . . . . . . . . 28
A.6. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 27 A.6. draft-ersue-constrained-mgmt-03 - draft-ersue-opsawg-
A.7. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 28 coman-use-cases-00 . . . . . . . . . . . . . . . . . . . 28
A.8. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 28 A.7. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 A.8. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 29
A.9. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
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
proxy to connect to the Internet. In other scenarios, the proxy to connect to the Internet. In other scenarios, the
skipping to change at page 8, line 47 skipping to change at page 8, line 47
running the environmental monitoring application. Since these running the environmental monitoring application. Since these
monitoring applications must be designed to tolerate a number of monitoring applications must be designed to tolerate a number of
failures, the time scale for detecting and recording failures is for failures, the time scale for detecting and recording failures is for
some of these applications likely measured in hours and repairs might some of these applications likely measured in hours and repairs might
easily take days. In fact, in some scenarios it might be more cost- easily take days. In fact, in some scenarios it might be more cost-
and time-effective to not repair such devices at all. However, for and time-effective to not repair such devices at all. However, for
certain environmental monitoring applications, much tighter time certain environmental monitoring applications, much tighter time
scales may exist and might be enforced by regulations (e.g., scales may exist and might be enforced by regulations (e.g.,
monitoring of nuclear radiation). monitoring of nuclear radiation).
Since many applications of environmental monitoring sensors are
likely to be in areas that are important to safety (flood monitoring,
nuclear radiation monitoring, etc.) it is important for management
protocols and network management systems (NMS) to ensure appropriate
security protections. These protections include not only access
control, integrity and availability of data, but also provide
appropriate mechanisms that can deal with situations that might be
categorized as emergencies or when tampering with sensors/data might
be detected.
4.2. Infrastructure Monitoring 4.2. Infrastructure Monitoring
Infrastructure monitoring is concerned with the monitoring of Infrastructure monitoring is concerned with the monitoring of
infrastructures such as bridges, railway tracks, or (offshore) infrastructures such as bridges, railway tracks, or (offshore)
windmills. The primary goal is usually to detect any events or windmills. The primary goal is usually to detect any events or
changes of the structural conditions that can impact the risk and changes of the structural conditions that can impact the risk and
safety of the infrastructure being monitored. Another secondary goal safety of the infrastructure being monitored. Another secondary goal
is to schedule repair and maintenance activities in a cost effective is to schedule repair and maintenance activities in a cost effective
manner. manner.
skipping to change at page 9, line 38 skipping to change at page 9, line 48
modified. modified.
Management responsibility typically rests with the organization Management responsibility typically rests with the organization
owning the infrastructure or responsible for its operation. The time owning the infrastructure or responsible for its operation. The time
scale for detecting and recording failures is likely measured in scale for detecting and recording failures is likely measured in
hours and repairs might easily take days. However, certain events hours and repairs might easily take days. However, certain events
(e.g., natural disasters) may require that status information be (e.g., natural disasters) may require that status information be
obtained much more quickly and that replacements of failed sensors obtained much more quickly and that replacements of failed sensors
can be rolled out quickly (or redundant sensors are activated can be rolled out quickly (or redundant sensors are activated
quickly). In case the devices are difficult to access, a self- quickly). In case the devices are difficult to access, a self-
healing feature on the device might become necessary. healing feature on the device might become necessary. Since
infrastructure monitoring is closely related to ensuring safety,
management protocols and systems must provide appropriate security
protections to ensure confidentiality, integrity and availability of
data.
4.3. Industrial Applications 4.3. Industrial Applications
Industrial Applications and smart manufacturing refer to tasks such Industrial Applications and smart manufacturing refer to tasks such
as networked control and monitoring of manufacturing equipment, asset as networked control and monitoring of manufacturing equipment, asset
and situation management, or manufacturing process control. For the and situation management, or manufacturing process control. For the
management of a factory it is becoming essential to implement smart management of a factory it is becoming essential to implement smart
capabilities. From an engineering standpoint, industrial capabilities. From an engineering standpoint, industrial
applications are intelligent systems enabling rapid manufacturing of applications are intelligent systems enabling rapid manufacturing of
new products, dynamic response to product demands, and real-time new products, dynamic response to product demands, and real-time
skipping to change at page 11, line 41 skipping to change at page 12, line 9
are connected to a common backbone so that they may retrieve control are connected to a common backbone so that they may retrieve control
information from and send commands to appropriate devices. information from and send commands to appropriate devices.
Management responsibility is typically owned by the organization Management responsibility is typically owned by the organization
running the industrial application. Since the monitoring running the industrial application. Since the monitoring
applications must handle a potentially large number of failures, the applications must handle a potentially large number of failures, the
time scale for detecting and recording failures is for some of these time scale for detecting and recording failures is for some of these
applications likely measured in minutes. However, for certain applications likely measured in minutes. However, for certain
industrial applications, much tighter time scales may exist, e.g. in industrial applications, much tighter time scales may exist, e.g. in
real-time, which might be enforced by the manufacturing process or real-time, which might be enforced by the manufacturing process or
the use of critical material. the use of critical material. Management protocols and NMSs must
ensure appropriate access control since different users of industrial
control systems will have varying levels of permissions. E.g., while
supervisors might be allowed to change production parameters, they
should not be allowed to modify the functional configuration of
devices like a technician should. It is also important to ensure
integrity and availability of data since malfunctions can potentially
become safety issues. This also implies that management systems must
be able to react to situations that may pose dangers to worker
safety.
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
skipping to change at page 14, line 20 skipping to change at page 14, line 47
Different applications use Bluetooth, Wi-Fi or ZigBee connections to Different applications use Bluetooth, Wi-Fi or ZigBee connections to
access the patient's smartphone or home cellular connection to access access the patient's smartphone or home cellular connection to access
the Internet. the Internet.
Constrained devices that are part of medical applications are managed Constrained devices that are part of medical applications are managed
either by the users of those devices or by an organization providing either by the users of those devices or by an organization providing
medical (monitoring) services for physicians. In the first case, medical (monitoring) services for physicians. In the first case,
management must be automatic and/or easy to install and setup by management must be automatic and/or easy to install and setup by
average people. In the second case, it can be expected that devices average people. In the second case, it can be expected that devices
be controlled by specially trained people. In both cases, however, be controlled by specially trained people. In both cases, however,
it is crucial to protect the privacy of the people to which medical it is crucial to protect the safety and privacy of the people to
devices are attached. Even though the data collected by a heart beat which medical devices are attached. Security precautions to protect
access (authentication, encryption, integrity protections, etc.) to
such devices may be critical to safeguarding the individual. The
level of access granted to different users also may need to be
regulated. For example, an authorized surgeon or doctor must be
allowed to configure all necessary options on the devices, however, a
nurse or technician may only be allowed to retrieve data that can
assist in diagnosis. Even though the data collected by a heart beat
monitor might be protected, the pure fact that someone carries such a monitor might be protected, the pure fact that someone carries such a
device may need protection. As such, certain medical appliances may device may need protection. As such, certain medical appliances may
not want to participate in discovery and self-configuration protocols not want to participate in discovery and self-configuration protocols
in order to remain invisible. in order to remain invisible.
Many medical devices are likely to be used (and relied upon) to Many medical devices are likely to be used (and relied upon) to
provide data to physicians in critical situations since the biggest provide data to physicians in critical situations since the biggest
market is likely elderly and handicapped people. Timely delivery of market is likely elderly and handicapped people. Timely delivery of
data can be quite important in certain applications like patient data can be quite important in certain applications like patient
mobility monitoring in old-age homes. Data must reach the physician mobility monitoring in old-age homes. Data must reach the physician
skipping to change at page 16, line 40 skipping to change at page 17, line 25
identified with a network identifier related to their physical identified with a network identifier related to their physical
location. Devices are accessed from an installation tool to connect location. Devices are accessed from an installation tool to connect
them to the network in a secure fashion. During installation, the them to the network in a secure fashion. During installation, the
setting of parameters of common values to enable interoperability may setting of parameters of common values to enable interoperability may
be required. During operation, the networks are connected to the be required. During operation, the networks are connected to the
backbone while maintaining the network identifier to physical backbone while maintaining the network identifier to physical
location relation. Network parameters like address and name are location relation. Network parameters like address and name are
stored in DNS. The names can assist in determining the physical stored in DNS. The names can assist in determining the physical
location of the device. location of the device.
It is also important for a building automation NMS to take safety and
security into account. Ensuring privacy and confidentiality of data,
such that unauthorized parties do not get access to it, is likely to
be important since users' individual behaviors could be potentially
understood via their settings. Appropriate security considerations
for authorization and access control to the NMS is also important
since different users are likely to have varied levels of operational
permissions in the system. E.g., while end users should be able to
control lighting systems, HVACs, etc., only qualified technicians
should be able to configure parameters that change the fundamental
operation of a device. It is also important for devices and the NMS
to be able to detect and report any tampering they might detect,
since these could lead to potential user safety concerns, e.g., if
sensors controlling air quality are tampered with such that the
levels of Carbon Monoxide become life threatening. This implies that
a NMS should also be able to deal with and appropriately prioritize
situations that might potentially lead to safety concerns.
4.7. Home Automation 4.7. Home Automation
Home automation includes the control of lighting, heating, Home automation includes the control of lighting, heating,
ventilation, air conditioning, appliances, entertainment and home ventilation, air conditioning, appliances, entertainment and home
security devices to improve convenience, comfort, energy efficiency, security devices to improve convenience, comfort, energy efficiency,
and safety. It can be seen as a residential extension of building and safety. It can be seen as a residential extension of building
automation. However, unlike a building automation system, the automation. However, unlike a building automation system, the
infrastructure in a home is operated in a considerably more ad-hoc infrastructure in a home is operated in a considerably more ad-hoc
manner. While in some installations it is likely that there is no manner. While in some installations it is likely that there is no
centralized management system, akin to a Building Automation System centralized management system, akin to a Building Automation System
skipping to change at page 19, line 29 skipping to change at page 20, line 33
necessarily need to be wireless. The time scale for detecting and necessarily need to be wireless. The time scale for detecting and
recording failures in a moving transport network is likely measured recording failures in a moving transport network is likely measured
in hours and repairs might easily take days. It is likely that a in hours and repairs might easily take days. It is likely that a
self-healing feature would be used locally. On the other hand, self-healing feature would be used locally. On the other hand,
failures in fixed transport application infrastructure (e.g., failures in fixed transport application infrastructure (e.g.,
traffic-lights, digital signage displays) is likely to be measured in traffic-lights, digital signage displays) is likely to be measured in
minutes so as to avoid untoward traffic incidents. As such, the NMS minutes so as to avoid untoward traffic incidents. As such, the NMS
must be able to deal with differing timeliness requirements based on must be able to deal with differing timeliness requirements based on
the type of devices. the type of devices.
Since transport applications of the constrained devices and networks
deal with automotive vehicles, malfunctions and misuse can
potentially lead to safety concerns as well. As such, besides access
control, privacy of user data and timeliness management systems
should also be able to detect situations that are potentially
hazardous to safety. Some of these situations could be automatically
mitigated, e.g., traffic lights with incorrect timing, but others
might require human intervention, e.g., failed traffic lights. The
management system should take appropriate actions in these
situations. Maintaining data confidentiality and integrity is also
an important security aspect of a management system since tampering
(or malfunction) can also lead to potentially dangerous situations.
4.9. Community Network Applications 4.9. Community Network Applications
Community networks are comprised of constrained routers in a multi- Community networks are comprised of constrained routers in a multi-
hop mesh topology, communicating over a lossy, and often wireless hop mesh topology, communicating over a lossy, and often wireless
channels. While the routers are mostly non-mobile, the topology may channels. While the routers are mostly non-mobile, the topology may
be very dynamic because of fluctuations in link quality of the be very dynamic because of fluctuations in link quality of the
(wireless) channel caused by, e.g., obstacles, or other nearby radio (wireless) channel caused by, e.g., obstacles, or other nearby radio
transmissions. Depending on the routers that are used in the transmissions. Depending on the routers that are used in the
community network, the resources of the routers (memory, CPU) may be community network, the resources of the routers (memory, CPU) may be
more or less constrained - available resources may range from only a more or less constrained - available resources may range from only a
skipping to change at page 23, line 19 skipping to change at page 24, line 36
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, Peter van Greevenbosch, Ulrich Herberg, Ted Lemon, Kathleen Moriarty, James
der Stok, and Martin Thomson. Nguyen, Zach Shelby, Peter van 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 25, line 35
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-03 - draft-ietf-opsawg-coman- A.1. draft-ietf-opsawg-coman-use-cases-04 - draft-ietf-opsawg-coman-
use-cases-05
o Added text regarding security and safety considerations to the
Environmental Monitoring, Infrastructure Monitoring, Industrial
Applications, Medical Applications, Building Automation and
Transport Applications section.
o Adopted text as per comments received from Kathleen Moriarty
during IESG review.
o Added security related text to use cases for addressing concerns
raised by Ted Lemon during the IESG review.
A.2. draft-ietf-opsawg-coman-use-cases-03 - draft-ietf-opsawg-coman-
use-cases-04 use-cases-04
o Resolved Gen-ART review comments received from Martin Thomson. o Resolved Gen-ART review comments received from Martin Thomson.
o Deleted company name for the list of contributors. o Deleted company name for the list of contributors.
o Added Martin Thomson to Acknowledgments section. o Added Martin Thomson to Acknowledgments section.
A.2. draft-ietf-opsawg-coman-use-cases-02 - draft-ietf-opsawg-coman- A.3. 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 11 skipping to change at page 26, line 45
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.3. draft-ietf-opsawg-coman-use-cases-01 - draft-ietf-opsawg-coman- A.4. 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 31 skipping to change at page 28, line 16
* 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.4. draft-ietf-opsawg-coman-use-cases-00 - draft-ietf-opsawg-coman- A.5. 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.5. draft-ersue-constrained-mgmt-03 - draft-ersue-opsawg-coman-use- A.6. 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.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 28, line 12 skipping to change at page 29, line 45
* 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 28, line 47 skipping to change at page 30, line 32
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.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. 20 change blocks. 
47 lines changed or deleted 124 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/