--- 1/draft-ietf-opsawg-coman-use-cases-03.txt 2015-01-19 02:15:11.123225222 -0800 +++ 2/draft-ietf-opsawg-coman-use-cases-04.txt 2015-01-19 02:15:11.191226871 -0800 @@ -1,22 +1,22 @@ Internet Engineering Task Force M. Ersue, Ed. Internet-Draft Nokia Networks Intended status: Informational D. Romascanu -Expires: April 30, 2015 Avaya +Expires: July 23, 2015 Avaya J. Schoenwaelder A. Sehgal Jacobs University Bremen - October 27, 2014 + January 19, 2015 Management of Networks with Constrained Devices: Use Cases - draft-ietf-opsawg-coman-use-cases-03 + draft-ietf-opsawg-coman-use-cases-04 Abstract This document discusses use cases concerning the management of networks, where constrained devices are involved. A problem statement, deployment options and the requirements on the networks with constrained devices can be found in the companion document on "Management of Networks with Constrained Devices: Problem Statement and Requirements". @@ -28,25 +28,25 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (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. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -73,31 +73,33 @@ 4.7. Home Automation . . . . . . . . . . . . . . . . . . . . . 16 4.8. Transport Applications . . . . . . . . . . . . . . . . . 17 4.9. Community Network Applications . . . . . . . . . . . . . 19 4.10. Field Operations . . . . . . . . . . . . . . . . . . . . 21 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 6. Security Considerations . . . . . . . . . . . . . . . . . . . 22 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 9. Informative References . . . . . . . . . . . . . . . . . . . 23 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 - 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 - 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 - 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 - A.5. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 27 - A.6. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 28 - A.7. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 28 + A.6. draft-ersue-constrained-mgmt-02-03 . . . . . . . . . . . 27 + A.7. draft-ersue-constrained-mgmt-01-02 . . . . . . . . . . . 28 + A.8. draft-ersue-constrained-mgmt-00-01 . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 1. Introduction Small devices with limited CPU, memory, and power resources, so called constrained devices (aka. sensor, smart object, or smart device) can be connected to a network. Such a network of constrained devices itself may be constrained or challenged, e.g., with unreliable or lossy channels, wireless technologies with limited bandwidth and a dynamic topology, needing the service of a gateway or @@ -517,49 +519,49 @@ 4.4. Energy Management The EMAN working group developed an energy management framework [RFC7326] for devices and device components within or connected to communication networks. This document observes that one of the challenges of energy management is that a power distribution network is responsible for the supply of energy to various devices and components, while a separate communication network is typically used to monitor and control the power distribution network. Devices in 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. Energy devices differ in complexity and may include basic sensors or switches, specialized electrical meters, or power distribution units (PDU), and subsystems inside the network devices (routers, network switches) or home or industrial appliances. The operators of an Energy Management System are either the utility providers or customers that aim to control and reduce the energy consumption and the associated costs. The topology in use differs and the deployment can cover areas from small surfaces (individual homes) to large geographical areas. The EMAN requirements document [RFC6988] discusses the requirements for energy management concerning 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 monitoring like battery utilization and availability may be specific to devices with lower physical resources (device classes C0 or C1 [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 act on energy and power-related information in an automated fashion with the goal to improve the efficiency, reliability, economics, and sustainability of the production and distribution of electricity. - Smart Metering is a good example of Smart Grid based Energy - Management applications. Different types of possibly wireless small + Smart Metering is a good example of Smart Grid based energy + management applications. Different types of possibly wireless small meters produce all together a large amount of data, which is 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 data-center. The communication infrastructure can be provided by a mobile network operator as the meters in urban areas will have most likely a cellular or WiMAX radio. In case the application server is located within the residence, such meters are more likely to use Wi- Fi protocols to interconnect with an existing network. An Advanced Metering Infrastructure (AMI) network is another example @@ -712,21 +714,21 @@ devices, there might be a need to certify components and subsystems operating in such constrained conditions based on specific requirements. Also in some environments, the malfunctioning of a control system (like temperature control) needs to be reported in the shortest possible time. Complex control systems can misbehave, and their critical status reporting and safety algorithms need to be basic and robust and perform even in critical conditions. Providing this monitoring, configuration and notification service is an 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 infrastructures. In the first case, there is a broader range of possible solutions, which can be planned for the infrastructure of the building. In the second case the solution needs to be deployed over an existing infrastructure taking into account factors like existing wiring, distance limitations, the propagation of radio signals over walls and floors, thereby making deployment difficult. 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 sensitive environments and in cases where link failures happen often, @@ -779,21 +781,21 @@ The management responsibility lies either with the residents or it may be outsourced to electricians and/or third parties providing management of home automation solutions as a service. A varying combination of electricians, service providers or the residents may be responsible for different aspects of managing the infrastructure. The time scale for failure detection and resolution is in many cases likely counted in hours to days. 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 a transportation system. Transport telematics or vehicle telematics are used as a term for the group of technologies that support transportation systems. Transport applications running on such a transportation system cover all modes of the transport and consider all elements of the transportation system, i.e. the vehicle, the infrastructure, and the driver or user, interacting together dynamically. Examples for transport applications are inter and intra vehicular communication, smart traffic control, smart parking, electronic toll collection systems, logistic and fleet management, @@ -1031,51 +1033,51 @@ 5. IANA Considerations This document does not introduce any new code-points or namespaces for registration with IANA. Note to RFC Editor: this section may be removed on publication as an RFC. 6. Security Considerations - This document discusses use cases for Management of Networks with - Constrained Devices. The security considerations described + This document discusses use cases for management of networks with + constrained devices. The security considerations described throughout the companion document [COM-REQ] apply here as well. 7. Contributors Following persons made significant contributions to and reviewed this document: - o Ulrich Herberg (Fujitsu Laboratories of America) contributed the - Section 4.9 on Community Network Applications. + o Ulrich Herberg contributed the Section 4.9 on Community Network + Applications. o Peter van der Stok contributed to Section 4.6 on Building Automation. o Zhen Cao contributed to Section 2.2 Cellular Access Technologies. o Gilman Tolle contributed the Section 4.4 on Automated Metering Infrastructure. o James Nguyen and Ulrich Herberg contributed to Section 4.10 on Military operations. 8. Acknowledgments Following persons reviewed and provided valuable comments to different versions of this document: Dominique Barthel, Carsten Bormann, Zhen Cao, Benoit Claise, Bert - Greevenbosch, Ulrich Herberg, James Nguyen, Zach Shelby, and Peter - van der Stok. + Greevenbosch, Ulrich Herberg, James Nguyen, Zach Shelby, Peter van + der Stok, and Martin Thomson. The editors would like to thank the reviewers and the participants on the Coman maillist for their valuable contributions and comments. 9. Informative References [RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)", RFC 6130, April 2011. @@ -1106,21 +1108,30 @@ Statement and Requirements", draft-ietf-opsawg-coman- probstate-reqs (work in progress), February 2014. [IOT-SEC] Garcia-Morchon, O., Kumar, S., Keoh, S., Hummen, R., and R. Struik, "Security Considerations in the IP-based Internet of Things", draft-garcia-core-security-06 (work in progress), September 2013. 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 o Updated references to take into account RFCs that have now been published o Added text to the access technologies section explaining why fixed line technologies (e.g., powerline communications) have not been discussed. o Created a new section, Device Lifecycle, discussing the impact of @@ -1137,21 +1148,21 @@ o Clarified the meaning of unreliability in context of constrained devices and networks. o Added information regarding the configuration and operation of factory automation use case, based on the type of information provided in the building automation use case. 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 o Renamed Mobile Access Technologies section to Cellular Access Technologies o Changed references to mobile access technologies to now read cellular access technologies. 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 @@ -1205,50 +1216,50 @@ * Expanded proprietary systems to "systems relying on a specific Management Topology Option, as described in [COM-REQ]." within Vehicular Networks section. * Added text regarding mobility patterns to Vehicular Networks. o Changed the Military Operations use case to Field Operations and 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 o Reordered some use cases to improve the flow. o Added "Vehicular Networks". o Shortened the Military Operations use case. 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 o Reduced the terminology section for terminology addressed in the LWIG and Coman Requirements drafts. Referenced the other drafts. o Checked and aligned all terminology against the LWIG terminology draft. o Spent some effort to resolve the intersection between the Industrial Application, Home Automation and Building Automation use cases. o Moved section section 3. Use Cases from the companion document [COM-REQ] to this draft. 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 terminology addressed in the new LWIG terminology draft. Referenced the LWIG terminology draft. o Moved Section 1.3. on Constrained Device Classes to the new LWIG terminology draft. o Class of networks considering the different type of radio and communication technologies in use and dimensions extended. @@ -1280,21 +1291,21 @@ * Software distribution (group-based firmware update) and Group- based provisioning. o Deleted the empty section on the gaps in network management standards, as it will be written in a separate draft. o Added links to mentioned external pages. 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 Added additional text for the use cases concerning deployment type, network topology in use, network size, network capabilities, radio technology, etc. o Added examples for device classes in a use case. o Added additional text provided by Cao Zhen (China Mobile) for @@ -1315,21 +1326,21 @@ constrained management matched to management tasks like fault, monitoring, configuration management, Security and Access Control, Energy Management, etc. o Solved nits and added references. o Added Appendix A on the related development in other bodies. 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 sections 'Network Topology Options' and 'Management Topology Options'. o Added the use case 'Community Network Applications' and 'Mobile Applications'. o Provided a Contributors section.