idnits 2.17.1 draft-fu-lwig-iot-usecase-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (October 19, 2014) is 3474 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Q. Fu, Ed. 3 Internet-Draft China Mobile 4 Intended status: Informational October 19, 2014 5 Expires: April 22, 2015 7 Deployment of the Low Weight IETF protocols In Internet of Things(IOT) 8 draft-fu-lwig-iot-usecase-00 10 Abstract 12 This draft analyze the development and deployment of the existing 13 IETF Low weight IPv6 protocols in the IOT (Internet Of Things) 14 industry. Taking consideration on the constrained resource nature of 15 devices, the IETF low weight IPv6 protocols, including 6LowPan, RPC 16 and COAP, fit perfectly in the IOT scenarios. Recent development and 17 promotion of Zigbee IP and IPSO also extend the use of these low 18 weight IPv6 protocols. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on April 22, 2015. 37 Copyright Notice 39 Copyright (c) 2014 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 56 3. ZigBee IP . . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 4. IPSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 5. Usecases for Operators . . . . . . . . . . . . . . . . . . . 4 59 6. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 7. Informative References . . . . . . . . . . . . . . . . . . . 4 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 With the fast development of wireless sensor technology and IC 66 technology, the concept of IOT (Internet Of Things) has been realized 67 and promoted in the Information Industry. IOT intends to build a 68 network to connect all devices, systems and services, which claims a 69 vast need of IP addresses.Due to its inherent advantage of huge 70 address pool, IPv6 has been chosen as the fundamental Internet 71 protocol by IETF ever since the research of IOT. 73 Due to the constrained resource nature of devices in IOT, working 74 groups in IETF mainly focus on low weight IPv6 protocols, which 75 include 6LowPan working group, RoLL working group, and CoRE working 76 group. Other standardization organizations, such as IPSO, Zigbee, 77 ISA and etc., are dedicated in promoting the deployment of these 78 protocols. With years of research and development, a number of 79 application cases and solutions for IOT based on IPv6 have been 80 proposed and deployed. In this draft, we will summarize the latest 81 deployments and usecases of protocols about IPv6 in IETF. 83 2. Terminology 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 87 document are to be interpreted as described in [RFC2119]. 89 3. ZigBee IP 91 ZigBee is the industry alliance based on IEEE 802.15.4. It mainly 92 focuses on standarization of network laryer and application layer in 93 short range wireless communication.The PHY and MAC layer of ZigBee is 94 IEEE 802.15.4. 96 ZigBee IP is the first open standard for an IPv6-based full wireless 97 mesh networking solution and provides seamless Internet connections 98 to control low-power, low-cost devices. It connects dozens of the 99 different devices into a single control network. 101 ZigBee IP was designed to support the ZigBee Smart Energy version 2 102 standard, published in 2013, which offers a global standard for IP- 103 based control,both wired and wireless, for energy management in Home 104 Area Networks(HANs).Such standard is expected to be used in Smart 105 Grid applications. 107 Zigbee IP has been recently updated to include 920IP, published in 108 July, 2014,which provides specific support for ECHONET Lite and the 109 requirements of Japanese Home Energy Management systems. 920IP was 110 developed in response to Japan's Ministry of Internal Affairs and 111 Communications (MIC) designation of 920 MHz for use in HEMS and 112 Ministry of Economy, Trade, and Industry(METI) endorsement of ECHONET 113 Lite as a smart home standard. 920IP is the only standard referenced 114 by the Telecommunications Technology Committee (TTC) which supports 115 multi-hop mesh networking. 117 The ZigBee IP specification enriches the IEEE 802.15.4 standard by 118 adding network and security layers and an application framework. 119 ZigBee IP offers a scalable architecture with end-to-end IPv6 120 networking, laying the foundation for an Internet of Things without 121 the need for intermediate gateways. It offers cost-effective and 122 energy-efficient wireless mesh network based on standard Internet 123 protocols, such as 6LoWPAN, IPv6, PANA, RPL, TCP, TLS and UDP. It 124 also features proven, end-to-end security using TLS1.2 protocol, link 125 layer frame security based on AES-128-CCM algorithm and support for 126 public key infrastructure using standard X.509 v3 certificates and 127 ECC-256 cipher suite. ZigBee IP enables low-power devices to 128 participate natively with other IPv6-enabled Ethernet, Wi-Fi and, 129 HomePlug devices. 131 ZigBee IP has been paid great attention once it was published in 132 2013. Several chip companies, including Exegin, Silicon Labs, TI and 133 etc., have developed chips that support ZigBee IP. 135 4. IPSO 137 The IPSO Alliance performs interoperability tests, documents the use 138 of new IP-based technologies, conducts marketing activities and 139 serves as an information repository for users seeking to understand 140 the role of IP in networks of physical objects. Its role complements 141 the work of entities such as the Internet Engineering Task Force 142 (IETF), Institute of Electrical and Electronics Engineers (IEEE) or 143 the ISA which develop and ratify technical standards in the Internet 144 community. 146 The ultimate goal of IPSO is to promote the use of IP in the IOT. 147 Considering the constraint nature of the IOT devices, several 148 technologies, including Lightweight OS, 6LowPan, COAP, and RPL, are 149 promoted in IPSO. Members of IPSO have developed large number of 150 commercial devices that support IP-communication. For example, 151 Toshiba has developed a IPv6-capable TV. Axis provides IPv6-capable 152 camera for surveillance use. 154 5. Usecases for Operators 156 The broad IOT market brings opportunities for operators world wide. 157 Interesting deployments of IOT or M2M (Machine to Machine) cases 158 based on IPv6 have emerged over the years.For example, the French 159 Telecom deploys IPv6 based M2M network in Smart Metering, Intelegent 160 Health Monitering, and Smart City. Considering the constraint nature 161 of the devices, low weight IPv6 protocols, including 6LowPan, RPL, 162 and COAP are utilized. 164 6. Conclusion 166 This draft introduces the recent development and deployments of low 167 weight IPv6 protocols studied in IETF. Taking careful consideration 168 on the constrained resource nature of the devices in IOT, these low 169 weight IPv6 protocols,including 6LowPan, RPL, and COAP, are proved to 170 be quite a success in the IOT scenarios. Generation and improvements 171 of industrial standards, such as Zigbee IP, also accelerate the 172 deployment of the low weight IPv6 protocols. We can predice that IOT 173 might be a "killer scenario" of the extensive deployment of IPv6 174 world wide in the near future. 176 7. Informative References 178 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 179 Requirement Levels", BCP 14, RFC 2119, March 1997. 181 Author's Address 183 Qiao Fu (editor) 184 China Mobile 185 Xuanwumenxi Ave. No.32 186 Beijing 187 China 189 Email: fuqiao1@outlook.com