< draft-ietf-6lo-use-cases-10.txt   draft-ietf-6lo-use-cases-11.txt >
6Lo Working Group Y-G. Hong 6Lo Working Group Y-G. Hong
Internet-Draft Internet-Draft Daejeon University
Intended status: Informational C. Gomez Intended status: Informational C. Gomez
Expires: August 25, 2021 UPC Expires: January 13, 2022 UPC
Y-H. Choi Y-H. Choi
ETRI ETRI
AR. Sangi AR. Sangi
Huaiyin Institute of Technology Huaiyin Institute of Technology
S. Chakrabarti S. Chakrabarti
February 21, 2021 July 12, 2021
IPv6 over Constrained Node Networks (6lo) Applicability & Use cases IPv6 over Constrained Node Networks (6lo) Applicability & Use cases
draft-ietf-6lo-use-cases-10 draft-ietf-6lo-use-cases-11
Abstract Abstract
This document describes the applicability of IPv6 over constrained This document describes the applicability of IPv6 over constrained
node networks (6lo) and provides practical deployment examples. In node networks (6lo) and provides practical deployment examples. In
addition to IEEE 802.15.4, various link layer technologies such as addition to IEEE Std 802.15.4, various link layer technologies such
ITU-T G.9959 (Z-Wave), Bluetooth Low Energy, DECT-ULE, MS/TP, NFC, as ITU-T G.9959 (Z-Wave), Bluetooth Low Energy, DECT-ULE, MS/TP, NFC,
and PLC are used as examples. The document targets an audience who and PLC are used as examples. The document targets an audience who
would like to understand and evaluate running end-to-end IPv6 over would like to understand and evaluate running end-to-end IPv6 over
the constrained node networks for local or Internet connectivity. the constrained node networks for local or Internet connectivity.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 August 25, 2021. This Internet-Draft will expire on January 13, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 29 skipping to change at page 2, line 29
2.1. ITU-T G.9959 . . . . . . . . . . . . . . . . . . . . . . 4 2.1. ITU-T G.9959 . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Bluetooth LE . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Bluetooth LE . . . . . . . . . . . . . . . . . . . . . . 4
2.3. DECT-ULE . . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. DECT-ULE . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4. MS/TP . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.4. MS/TP . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5. NFC . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.5. NFC . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.6. PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.6. PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.7. Comparison between 6lo link layer technologies . . . . . 8 2.7. Comparison between 6lo link layer technologies . . . . . 8
3. Guidelines for adopting IPv6 stack (6lo) . . . . . . . . . . 9 3. Guidelines for adopting IPv6 stack (6lo) . . . . . . . . . . 9
4. 6lo Deployment Scenarios . . . . . . . . . . . . . . . . . . 11 4. 6lo Deployment Scenarios . . . . . . . . . . . . . . . . . . 11
4.1. Wi-SUN usage of 6lo in network layer . . . . . . . . . . 11 4.1. Wi-SUN usage of 6lo in network layer . . . . . . . . . . 11
4.2. Thread usage of 6lo in network layer . . . . . . . . . . 13 4.2. Thread usage of 6lo in network layer . . . . . . . . . . 12
4.3. G3-PLC usage of 6lo in network layer . . . . . . . . . . 13 4.3. G3-PLC usage of 6lo in network layer . . . . . . . . . . 13
4.4. Netricity usage of 6lo in network layer . . . . . . . . . 14 4.4. Netricity usage of 6lo in network layer . . . . . . . . . 14
5. 6lo Use Case Examples . . . . . . . . . . . . . . . . . . . . 15 5. 6lo Use Case Examples . . . . . . . . . . . . . . . . . . . . 15
5.1. Use case of ITU-T G.9959: Smart Home . . . . . . . . . . 15 5.1. Use case of ITU-T G.9959: Smart Home . . . . . . . . . . 15
5.2. Use case of Bluetooth LE: Smartphone-based Interaction . 16 5.2. Use case of Bluetooth LE: Smartphone-based Interaction . 16
5.3. Use case of DECT-ULE: Smart Home . . . . . . . . . . . . 16 5.3. Use case of DECT-ULE: Smart Home . . . . . . . . . . . . 16
5.4. Use case of MS/TP: Building Automation Networks . . . . . 17 5.4. Use case of MS/TP: Building Automation Networks . . . . . 17
5.5. Use case of NFC: Alternative Secure Transfer . . . . . . 18 5.5. Use case of NFC: Alternative Secure Transfer . . . . . . 18
5.6. Use case of PLC: Smart Grid . . . . . . . . . . . . . . . 18 5.6. Use case of PLC: Smart Grid . . . . . . . . . . . . . . . 18
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
9. Informative References . . . . . . . . . . . . . . . . . . . 20 9. Informative References . . . . . . . . . . . . . . . . . . . 20
Appendix A. Design Space Dimensions for 6lo Deployment . . . . . 25 Appendix A. Design Space Dimensions for 6lo Deployment . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
Running IPv6 on constrained node networks presents challenges, due to Running IPv6 on constrained node networks presents challenges, due to
the characteristics of these networks such as small packet size, low the characteristics of these networks such as small packet size, low
power, low bandwidth, low cost, and large number of devices, among power, low bandwidth, low cost, and large number of devices, among
others [RFC4919][RFC7228]. For example, many IEEE 802.15.4 variants others [RFC4919][RFC7228]. For example, many IEEE Std 802.15.4
[IEEE802154] exhibit a frame size of 127 octets, whereas IPv6 variants [IEEE802154] exhibit a frame size of 127 octets, whereas
requires its underlying layer to support an MTU of 1280 bytes. IPv6 requires its underlying layer to support an MTU of 1280 bytes.
Furthermore, those IEEE 802.15.4 variants do not offer fragmentation Furthermore, those IEEE Std 802.15.4 variants do not offer
and reassembly functionality. Therefore, an appropriate adaptation fragmentation and reassembly functionality. (It is noted that IEEE
layer supporting fragmentation and reassembly must be provided below Std 802.15.9-2016 provides multiplexing and fragmentation layer for
IPv6. Also, the limited IEEE 802.15.4 frame size and low energy the IEEE Std 802.15.4[IEEE802159].) Therefore, an appropriate
consumption requirements motivate the need for packet header adaptation layer supporting fragmentation and reassembly must be
compression. The IETF IPv6 over Low-Power WPAN (6LoWPAN) working provided below IPv6. Also, the limited IEEE Std 802.15.4 frame size
group published a suite of specification that provide an adaptation and low energy consumption requirements motivate the need for packet
layer to support IPv6 over IEEE 802.15.4 comprising the following header compression. The IETF IPv6 over Low-Power WPAN (6LoWPAN)
functionality: working group published a suite of specification that provide an
adaptation layer to support IPv6 over IEEE Std 802.15.4 comprising
the following functionality:
o Fragmentation and reassembly, address autoconfiguration, and a o Fragmentation and reassembly, address autoconfiguration, and a
frame format [RFC4944], frame format [RFC4944],
o IPv6 (and UDP) header compression [RFC6282], o IPv6 (and UDP) header compression [RFC6282],
o Neighbor Discovery Optimization for 6LoWPAN [RFC6775][RFC8505]. o Neighbor Discovery Optimization for 6LoWPAN [RFC6775][RFC8505].
As Internet of Things (IoT) services become more popular, the IETF As Internet of Things (IoT) services become more popular, the IETF
6lo working group [IETF_6lo] has defined adaptation layer 6lo working group [IETF_6lo] has defined adaptation layer
functionality to support IPv6 over various link layer technologies functionality to support IPv6 over various link layer technologies
other than IEEE 802.15.4, such as Bluetooth Low Energy (Bluetooth other than IEEE Std 802.15.4, such as Bluetooth Low Energy (Bluetooth
LE), ITU-T G.9959 (Z-Wave), Digital Enhanced Cordless LE), ITU-T G.9959 (Z-Wave), Digital Enhanced Cordless
Telecommunications - Ultra Low Energy (DECT-ULE), Master-Slave/Token Telecommunications - Ultra Low Energy (DECT-ULE), Master-Slave/Token
Passing (MS/TP), Near Field Communication (NFC), and Power Line Passing (MS/TP), Near Field Communication (NFC), and Power Line
Communication (PLC). The 6lo adaptation layers use a variation of Communication (PLC). The 6lo adaptation layers use a variation of
the 6LoWPAN stack applied to each particular link layer technology. the 6LoWPAN stack applied to each particular link layer technology.
The 6LoWPAN working group produced the document entitled "Design and The 6LoWPAN working group produced the document entitled "Design and
Application Spaces for 6LoWPANs" [RFC6568], which describes potential Application Spaces for 6LoWPANs" [RFC6568], which describes potential
application scenarios and use cases for low-power wireless personal application scenarios and use cases for low-power wireless personal
area networks. The present document aims to provide guidance to an area networks. The present document aims to provide guidance to an
skipping to change at page 7, line 19 skipping to change at page 7, line 19
| | | | | | | | | | | |
| IEEE1901.1 | <12MHz | PLC-IoT | 10Mbps | 2000m | | IEEE1901.1 | <12MHz | PLC-IoT | 10Mbps | 2000m |
| | | | | | | | | | | |
| IEEE1901.2 | <500kHz | Narrowband | 200kbps | 3000m | | IEEE1901.2 | <500kHz | Narrowband | 200kbps | 3000m |
| | | | | | | | | | | |
| G3-PLC | <500kHz | Narrowband | 234kbps | 3000m | | G3-PLC | <500kHz | Narrowband | 234kbps | 3000m |
+-------------+-----------------+------------+-----------+----------+ +-------------+-----------------+------------+-----------+----------+
Table 1: Some Available Open Standards in PLC Table 1: Some Available Open Standards in PLC
IEEE 1901 [IEEE1901] defines a broadband variant of PLC but is IEEE Std 1901 [IEEE1901] defines a broadband variant of PLC but is
effective within short range. This standard addresses the effective within short range. This standard addresses the
requirements of applications with high data rate such as: Internet, requirements of applications with high data rate such as: Internet,
HDTV, Audio, Gaming etc. Broadband operates on Orthogonal Frequency HDTV, Audio, Gaming etc. Broadband operates on Orthogonal Frequency
Division Multiplexing (OFDM) modulation. Division Multiplexing (OFDM) modulation.
IEEE 1902.1 [IEEE1901.1] defines a medium frequency band (less than IEEE Std 1901.1 [IEEE1901.1] defines a medium frequency band (less
12 MHz) broadband PLC technology for smart grid applications based on than 12 MHz) broadband PLC technology for smart grid applications
OFDM. By achieving an extended communication range with medium based on OFDM. By achieving an extended communication range with
speeds, this standard can be applied both in indoor and outdoor medium speeds, this standard can be applied both in indoor and
scenarios, such as Advanced Metering Infrastructure (AMI), street outdoor scenarios, such as Advanced Metering Infrastructure (AMI),
lighting, electric vehicle charging, smart city etc. street lighting, electric vehicle charging, smart city etc.
IEEE 1902.2 [IEEE1901.2] defines a narrowband variant of PLC with IEEE Std 1901.2 [IEEE1901.2] defines a narrowband variant of PLC with
less data rate but significantly higher transmission range that could less data rate but significantly higher transmission range that could
be used in an indoor or even an outdoor environment. It is be used in an indoor or even an outdoor environment. It is
applicable to typical IoT applications such as: Building Automation, applicable to typical IoT applications such as: Building Automation,
Renewable Energy, Advanced Metering, Street Lighting, Electric Renewable Energy, Advanced Metering, Street Lighting, Electric
Vehicle, Smart Grid etc. Moreover, IEEE 1901.2 standard is based on Vehicle, Smart Grid etc. Moreover, IEEE Std 1901.2 standard is based
the 802.15.4 MAC sub-layer and fully endorses the security scheme on the 802.15.4 MAC sub-layer and fully endorses the security scheme
defined in 802.15.4 [RFC8036]. A typical use case of PLC is smart defined in 802.15.4 [RFC8036]. A typical use case of PLC is smart
grid. grid.
G3-PLC [G3-PLC] is a narrowband PLC technology that is based on the G3-PLC [G3-PLC] is a narrowband PLC technology that is based on the
ITU-T G.9903 Recommendation [G.9903]. The ITU-T G.9903 ITU-T G.9903 Recommendation [G.9903]. The ITU-T G.9903
Recommendation contains the physical layer and data link layer Recommendation contains the physical layer and data link layer
specification for the G3-PLC narrowband OFDM power line communication specification for the G3-PLC narrowband OFDM power line communication
transceivers, for communications via alternating current and direct transceivers, for communications via alternating current and direct
current electric power lines over frequencies below 500 kHz. current electric power lines over frequencies below 500 kHz.
skipping to change at page 10, line 7 skipping to change at page 10, line 7
with a 6LoWPAN stack. with a 6LoWPAN stack.
o Address Assignment: 6LoWPAN developed a new version of IPv6 o Address Assignment: 6LoWPAN developed a new version of IPv6
Neighbor Discovery [RFC4861][RFC4862]. 6LoWPAN Neighbor Discovery Neighbor Discovery [RFC4861][RFC4862]. 6LoWPAN Neighbor Discovery
[RFC6775][RFC8505] inherits from IPv6 Neighbor Discovery for [RFC6775][RFC8505] inherits from IPv6 Neighbor Discovery for
mechanisms such as Stateless Address Autoconfiguration (SLAAC) and mechanisms such as Stateless Address Autoconfiguration (SLAAC) and
Neighbor Unreachability Detection (NUD). A 6LoWPAN node is also Neighbor Unreachability Detection (NUD). A 6LoWPAN node is also
expected to be an IPv6 host per [RFC8200] which means it should expected to be an IPv6 host per [RFC8200] which means it should
ignore consumed routing headers and Hop-by-Hop options; when ignore consumed routing headers and Hop-by-Hop options; when
operating in a RPL network [RFC6550], it is also beneficial to operating in a RPL network [RFC6550], it is also beneficial to
support IP-in-IP encapsulation [I-D.ietf-roll-useofrplinfo]. The support IP-in-IP encapsulation [RFC9008]. The 6LoWPAN node should
6LoWPAN node should also support [RFC8505] and use it as the also support [RFC8505] and use it as the default Neighbor
default Neighbor Discovery method. It is the responsibility of Discovery method. It is the responsibility of the deployment to
the deployment to ensure unique global IPv6 addresses for Internet ensure unique global IPv6 addresses for Internet connectivity.
connectivity. For local-only connectivity IPv6 Unique Local For local-only connectivity IPv6 Unique Local Address (ULA) may be
Address (ULA) may be used. [RFC6775][RFC8505] specifies the used. [RFC6775][RFC8505] specifies the 6LoWPAN border router
6LoWPAN border router (6LBR), which is responsible for prefix (6LBR), which is responsible for prefix assignment to the 6LoWPAN
assignment to the 6LoWPAN network. A 6LBR can be connected to the network. A 6LBR can be connected to the Internet or to an
Internet or to an enterprise network via one of the interfaces. enterprise network via one of the interfaces. Please refer to
Please refer to [RFC7668] and [RFC8105] for examples of address [RFC7668] and [RFC8105] for examples of address assignment
assignment considerations. In addition, privacy considerations considerations. In addition, privacy considerations [RFC8065]
[RFC8065] must be consulted for applicability. In certain must be consulted for applicability. In certain scenarios, the
scenarios, the deployment may not support IPv6 address deployment may not support IPv6 address autoconfiguration due to
autoconfiguration due to regulatory and business reasons and may regulatory and business reasons and may choose to offer a separate
choose to offer a separate address assignment service. Address address assignment service. Address Protection for 6LoWPAN
Protection for 6LoWPAN Neighbor Discovery (AP-ND) [RFC8928] Neighbor Discovery (AP-ND) [RFC8928] enables Source Address
enables Source Address Validation [RFC6620] and protects the Validation [RFC6620] and protects the address ownership against
address ownership against impersonation attacks. impersonation attacks.
o Broadcast Avoidance: 6LoWPAN Neighbor Discovery aims at reducing o Broadcast Avoidance: 6LoWPAN Neighbor Discovery aims at reducing
the amount of multicast traffic of classical Neighbor Discovery, the amount of multicast traffic of classical Neighbor Discovery,
since IP-level multicast translates into L2 broadcast in many L2 since IP-level multicast translates into L2 broadcast in many L2
technologies. 6LoWPAN Neighbor Discovery relies on a proactive technologies. 6LoWPAN Neighbor Discovery relies on a proactive
registration to avoid the use of multicast for address resolution. registration to avoid the use of multicast for address resolution.
It also uses a unicast method for Duplicate Address Detection It also uses a unicast method for Duplicate Address Detection
(DAD), and avoids multicast lookups from all nodes by using non- (DAD), and avoids multicast lookups from all nodes by using non-
onlink prefixes. Router Advertisements (RAs) are also sent in onlink prefixes. Router Advertisements (RAs) are also sent in
unicast, in response to Router Solicitations (RSs) unicast, in response to Router Solicitations (RSs)
o Host-to-Router interface: 6lo has defined registration extensions o Host-to-Router interface: 6lo has defined registration extensions
for 6LoWPAN Neighbor Discovery [RFC8505]. This effort provides a for 6LoWPAN Neighbor Discovery [RFC8505]. This effort provides a
host-to-router interface by which a host can request its router to host-to-router interface by which a host can request its router to
ensure reachability for the address registered with the router. ensure reachability for the address registered with the router.
Note that functionality has been developed to ensure that such a Note that functionality has been developed to ensure that such a
host can benefit from routing services in a RPL network host can benefit from routing services in a RPL network [RFC9010]
[I-D.ietf-roll-unaware-leaves]
o Proxy Neighbor Discovery: Further functionality also allows a o Proxy Neighbor Discovery: Further functionality also allows a
device (e.g. an energy-constrained device that needs to sleep most device (e.g. an energy-constrained device that needs to sleep most
of the time) to request proxy Neighbor Discovery services from a of the time) to request proxy Neighbor Discovery services from a
6LoWPAN Backbone Router (6BBR) [RFC8505][RFC8929]. The latter 6LoWPAN Backbone Router (6BBR) [RFC8505][RFC8929]. The latter
federates a number of links into a multilink subnet. federates a number of links into a multilink subnet.
o Header Compression: IPv6 header compression [RFC6282] is a vital o Header Compression: IPv6 header compression [RFC6282] is a vital
part of IPv6 over low power communication. Examples of header part of IPv6 over low power communication. Examples of header
compression over different link-layer specifications are found in compression over different link-layer specifications are found in
skipping to change at page 11, line 5 skipping to change at page 11, line 4
o Proxy Neighbor Discovery: Further functionality also allows a o Proxy Neighbor Discovery: Further functionality also allows a
device (e.g. an energy-constrained device that needs to sleep most device (e.g. an energy-constrained device that needs to sleep most
of the time) to request proxy Neighbor Discovery services from a of the time) to request proxy Neighbor Discovery services from a
6LoWPAN Backbone Router (6BBR) [RFC8505][RFC8929]. The latter 6LoWPAN Backbone Router (6BBR) [RFC8505][RFC8929]. The latter
federates a number of links into a multilink subnet. federates a number of links into a multilink subnet.
o Header Compression: IPv6 header compression [RFC6282] is a vital o Header Compression: IPv6 header compression [RFC6282] is a vital
part of IPv6 over low power communication. Examples of header part of IPv6 over low power communication. Examples of header
compression over different link-layer specifications are found in compression over different link-layer specifications are found in
[RFC7668], [RFC8163], [RFC8105]. A generic header compression [RFC7668], [RFC8163], [RFC8105]. A generic header compression
technique is specified in [RFC7400]. For 6LoWPAN networks where technique is specified in [RFC7400]. For 6LoWPAN networks where
RPL is the routing protocol, there exist 6LoWPAN header RPL is the routing protocol, there exist 6LoWPAN header
compression extensions which allow to compress also the RPL compression extensions which allow to compress also the RPL
artifacts used when forwarding packets in the route-over mesh artifacts used when forwarding packets in the route-over mesh
[RFC8138] [I-D.ietf-roll-turnon-rfc8138] [RFC8138] [RFC9035]
o Security and Encryption: Though 6LoWPAN basic specifications do o Security and Encryption: Though 6LoWPAN basic specifications do
not address security at the network layer, the assumption is that not address security at the network layer, the assumption is that
L2 security must be present. In addition, application-level L2 security must be present. In addition, application-level
security is highly desirable. The working groups [IETF_ace] and security is highly desirable. The working groups [IETF_ace] and
[IETF_core] should be consulted for application and transport [IETF_core] should be consulted for application and transport
level security. 6lo working group is working on address level security. 6lo working group is working on address
authentication [RFC8928] and secure bootstrapping is also being authentication [RFC8928] and secure bootstrapping is also being
discussed at IETF. However, there may be different levels of discussed at IETF. However, there may be different levels of
security available in a deployment through other standards such as security available in a deployment through other standards such as
skipping to change at page 11, line 35 skipping to change at page 11, line 35
o Additional processing: [RFC8066] defines guidelines for ESC o Additional processing: [RFC8066] defines guidelines for ESC
dispatch octets use in the 6LoWPAN header. An implementation may dispatch octets use in the 6LoWPAN header. An implementation may
take advantage of ESC header to offer a deployment specific take advantage of ESC header to offer a deployment specific
processing of 6LoWPAN packets. processing of 6LoWPAN packets.
4. 6lo Deployment Scenarios 4. 6lo Deployment Scenarios
4.1. Wi-SUN usage of 6lo in network layer 4.1. Wi-SUN usage of 6lo in network layer
Wireless Smart Ubiquitous Network (Wi-SUN)[Wi-SUN] is a technology Wireless Smart Ubiquitous Network (Wi-SUN)[Wi-SUN] is a technology
based on the IEEE 802.15.4g standard. Wi-SUN networks support star based on the IEEE Std 802.15.4g standard. Wi-SUN networks support
and mesh topologies, as well as hybrid star/mesh deployments, but star and mesh topologies, as well as hybrid star/mesh deployments,
these are typically laid out in a mesh topology where each node but these are typically laid out in a mesh topology where each node
relays data for the network to provide network connectivity. Wi-SUN relays data for the network to provide network connectivity. Wi-SUN
networks are deployed on both powered and battery-operated devices networks are deployed on both powered and battery-operated devices
[RFC8376]. [RFC8376].
The main application domains targeted by Wi-SUN are smart utility and The main application domains targeted by Wi-SUN are smart utility and
smart city networks. This includes, but is not limited to the smart city networks. This includes, but is not limited to the
following applications: following applications:
o Advanced Metering Infrastructure o Advanced Metering Infrastructure
o Distribution Automation o Distribution Automation
o Home Energy Management o Home Energy Management
o Infrastructure Management
o Infrastructure Management
o Intelligent Transportation Systems o Intelligent Transportation Systems
o Smart Street Lighting o Smart Street Lighting
o Agriculture o Agriculture
o Structural health (bridges, buildings) o Structural health (bridges, buildings)
o Monitoring and Asset Management o Monitoring and Asset Management
skipping to change at page 13, line 9 skipping to change at page 12, line 50
operation of network nodes operation of network nodes
The Wi-SUN FAN specification defines an IPv6-based protocol suite The Wi-SUN FAN specification defines an IPv6-based protocol suite
including TCP/UDP, IPv6, 6lo adaptation layer, DHCPv6 for IPv6 including TCP/UDP, IPv6, 6lo adaptation layer, DHCPv6 for IPv6
address management, RPL, and ICMPv6. address management, RPL, and ICMPv6.
4.2. Thread usage of 6lo in network layer 4.2. Thread usage of 6lo in network layer
Thread is an IPv6-based networking protocol stack built on open Thread is an IPv6-based networking protocol stack built on open
standards, designed for smart home environments, and based on low- standards, designed for smart home environments, and based on low-
power IEEE 802.15.4 mesh networks. Because of its IPv6 foundation, power IEEE Std 802.15.4 mesh networks. Because of its IPv6
Thread can support existing popular application layers and IoT foundation, Thread can support existing popular application layers
platforms, provide end-to-end security, ease development and enable and IoT platforms, provide end-to-end security, ease development and
flexible and future-proof designs [Thread]. enable flexible and future-proof designs [Thread].
The Thread specification uses the IEEE 802.15.4 [IEEE802154] physical The Thread specification uses the IEEE Std 802.15.4 [IEEE802154]
and MAC layers operating at 250 kbps in the 2.4 GHz band. The IEEE physical and MAC layers operating at 250 kbps in the 2.4 GHz band.
802.15.4-2006 and IEEE 802.15.4-2015 versions of the specification
are used by Thread.
Thread devices use 6LoWPAN, as defined in [RFC4944][RFC6282], for Thread devices use 6LoWPAN, as defined in [RFC4944][RFC6282], for
transmission of IPv6 Packets over IEEE 802.15.4 networks. Header transmission of IPv6 Packets over IEEE Std 802.15.4 networks. Header
compression is used within the Thread network and devices compression is used within the Thread network and devices
transmitting messages compress the IPv6 header to minimize the size transmitting messages compress the IPv6 header to minimize the size
of the transmitted packet. The mesh header is supported for link- of the transmitted packet. The mesh header is supported for link-
layer (i.e., mesh under) forwarding. The mesh header as used in layer (i.e., mesh under) forwarding. The mesh header as used in
Thread also allows efficient end-to-end fragmentation of messages Thread also allows efficient end-to-end fragmentation of messages
rather than the hop-by-hop fragmentation specified in [RFC4944]. rather than the hop-by-hop fragmentation specified in [RFC4944].
Mesh under routing in Thread is based on a distance vector protocol Mesh under routing in Thread is based on a distance vector protocol
in a full mesh topology. in a full mesh topology.
4.3. G3-PLC usage of 6lo in network layer 4.3. G3-PLC usage of 6lo in network layer
skipping to change at page 14, line 4 skipping to change at page 13, line 44
o Smart Metering o Smart Metering
o Vehicle-to-Grid Communication o Vehicle-to-Grid Communication
o Demand Response o Demand Response
o Distribution Automation o Distribution Automation
o Home/Building Energy Management Systems o Home/Building Energy Management Systems
o Smart Street Lighting o Smart Street Lighting
o Advanced Metering Infrastructure (AMI) backbone network o Advanced Metering Infrastructure (AMI) backbone network
o Wind/Solar Farm Monitoring o Wind/Solar Farm Monitoring
In the G3-PLC specification, the 6lo adaption layer utilizes the In the G3-PLC specification, the 6lo adaption layer utilizes the
6LoWPAN functions (e.g. header compression, fragmentation and 6LoWPAN functions (e.g. header compression, fragmentation and
reassembly). However, due to the different characteristics of the reassembly). However, due to the different characteristics of the
PLC media, the 6LoWPAN adaptation layer cannot perfectly fulfill the PLC media, the 6LoWPAN adaptation layer cannot perfectly fulfill the
requirements [I-D.ietf-6lo-plc]. The ESC dispatch type is used in requirements [I-D.ietf-6lo-plc]. The ESC dispatch type is used in
the G3-PLC to provide native mesh routing and bootstrapping the G3-PLC to provide native mesh routing and bootstrapping
functionalities [RFC8066]. functionalities [RFC8066].
4.4. Netricity usage of 6lo in network layer 4.4. Netricity usage of 6lo in network layer
The Netricity program in HomePlug Powerline Alliance [NETRICITY] The Netricity program in HomePlug Powerline Alliance [NETRICITY]
promotes the adoption of products built on the IEEE 1901.2 low- promotes the adoption of products built on the IEEE Std 1901.2 low-
frequency narrowband PLC standard, which provides for urban and long frequency narrowband PLC standard, which provides for urban and long
distance communications and propagation through transformers of the distance communications and propagation through transformers of the
distribution network using frequencies below 500 kHz. The technology distribution network using frequencies below 500 kHz. The technology
also addresses requirements that assure communication privacy and also addresses requirements that assure communication privacy and
secure networks. secure networks.
The main application domains targeted by Netricity are smart grid and The main application domains targeted by Netricity are smart grid and
smart cities. This includes, but is not limited to the following smart cities. This includes, but is not limited to the following
applications: applications:
skipping to change at page 15, line 4 skipping to change at page 14, line 45
o Load control o Load control
o Demand response o Demand response
o Net metering o Net metering
o Street Lighting control o Street Lighting control
o Photovoltaic panel monitoring o Photovoltaic panel monitoring
Netricity system architecture is based on the physical and MAC layers Netricity system architecture is based on the physical and MAC layers
of IEEE 1901.2 PLC standard. Regarding the 6lo adaptation layer and of IEEE Std 1901.2 PLC standard. Regarding the 6lo adaptation layer
IPv6 network layer, Netricity utilizes IPv6 protocol suite including and IPv6 network layer, Netricity utilizes IPv6 protocol suite
6lo/6LoWPAN header compression, DHCPv6 for IP address management, RPL including 6lo/6LoWPAN header compression, DHCPv6 for IP address
routing protocol, ICMPv6, and unicast/multicast forwarding. Note management, RPL routing protocol, ICMPv6, and unicast/multicast
that the L3 routing in Netricity uses RPL in non-storing mode with forwarding. Note that the L3 routing in Netricity uses RPL in non-
the MRHOF objective function based on the own defined Estimated storing mode with the MRHOF objective function based on the own
Transmission Time (ETT) metric. defined Estimated Transmission Time (ETT) metric.
5. 6lo Use Case Examples 5. 6lo Use Case Examples
As IPv6 stacks for constrained node networks use a variation of the As IPv6 stacks for constrained node networks use a variation of the
6LoWPAN stack applied to each particular link layer technology, 6LoWPAN stack applied to each particular link layer technology,
various 6lo use cases can be provided. In this section, various 6lo various 6lo use cases can be provided. In this section, various 6lo
use cases which are based on different link layer technologies are use cases which are based on different link layer technologies are
described. described.
5.1. Use case of ITU-T G.9959: Smart Home 5.1. Use case of ITU-T G.9959: Smart Home
skipping to change at page 19, line 28 skipping to change at page 19, line 25
actions like notification of electricity charges according to the actions like notification of electricity charges according to the
commands from the utility company. commands from the utility company.
With the existing power line infrastructure as communication medium, With the existing power line infrastructure as communication medium,
cost on building up the PLC network is naturally saved, and more cost on building up the PLC network is naturally saved, and more
importantly, labor operational costs can be minimized from a long- importantly, labor operational costs can be minimized from a long-
term perspective. Furthermore, this AMI application speeds up term perspective. Furthermore, this AMI application speeds up
electricity charge, reduces losses by restraining power theft and electricity charge, reduces losses by restraining power theft and
helps to manage the health of the grid based on line loss analysis. helps to manage the health of the grid based on line loss analysis.
Example: Use of PLC (IEEE1901.1) for WASA in Smart Grid Example: Use of PLC (IEEE Std 1901.1) for WASA in Smart Grid
Many sub-systems of Smart Grid require low data rate and narrowband Many sub-systems of Smart Grid require low data rate and narrowband
variants (e.g., IEEE1901.1) of PLC fulfill such requirements. variants (e.g., IEEE Std 1901.1) of PLC fulfill such requirements.
Recently, more complex scenarios are emerging that require higher Recently, more complex scenarios are emerging that require higher
data rates. data rates.
WASA sub-system is an appropriate example that collects large amount WASA sub-system is an appropriate example that collects large amount
of information about the current state of the grid over wide area of information about the current state of the grid over wide area
from electric substations as well as power transmission lines. The from electric substations as well as power transmission lines. The
collected feedback is used for monitoring, controlling and protecting collected feedback is used for monitoring, controlling and protecting
all the sub-systems. all the sub-systems.
6. IANA Considerations 6. IANA Considerations
skipping to change at page 21, line 6 skipping to change at page 21, line 6
Recommendation", August 2017. Recommendation", August 2017.
[G.9959] "International Telecommunication Union, "Short range [G.9959] "International Telecommunication Union, "Short range
narrow-band digital radiocommunication transceivers - PHY narrow-band digital radiocommunication transceivers - PHY
and MAC layer specifications", ITU-T Recommendation", and MAC layer specifications", ITU-T Recommendation",
January 2015. January 2015.
[G3-PLC] "G3-PLC Alliance", <http://www.g3-plc.com/home/>. [G3-PLC] "G3-PLC Alliance", <http://www.g3-plc.com/home/>.
[IEEE1901] [IEEE1901]
"IEEE Standard, IEEE Std. 1901-2010 - IEEE Standard for "IEEE Standard, IEEE Std 1901-2010 - IEEE Standard for
Broadband over Power Line Networks: Medium Access Control Broadband over Power Line Networks: Medium Access Control
and Physical Layer Specifications", 2010, and Physical Layer Specifications", 2010,
<https://standards.ieee.org/findstds/ <https://standards.ieee.org/findstds/
standard/1901-2010.html>. standard/1901-2010.html>.
[IEEE1901.1] [IEEE1901.1]
"IEEE Standard, IEEE Std. 1901.1-2018 - IEEE Standard for "IEEE Standard, IEEE Std 1901.1-2018 - IEEE Standard for
Medium Frequency (less than 12 MHz) Power Line Medium Frequency (less than 12 MHz) Power Line
Communications for Smart Grid Applications", 2018, Communications for Smart Grid Applications", 2018,
<https://ieeexplore.ieee.org/document/8360785>. <https://ieeexplore.ieee.org/document/8360785>.
[IEEE1901.2] [IEEE1901.2]
"IEEE Standard, IEEE Std. 1901.2-2013 - IEEE Standard for "IEEE Standard, IEEE Std 1901.2-2013 - IEEE Standard for
Low-Frequency (less than 500 kHz) Narrowband Power Line Low-Frequency (less than 500 kHz) Narrowband Power Line
Communications for Smart Grid Applications", 2013, Communications for Smart Grid Applications", 2013,
<https://standards.ieee.org/findstds/ <https://standards.ieee.org/findstds/
standard/1901.2-2013.html>. standard/1901.2-2013.html>.
[IEEE802154] [IEEE802154]
IEEE standard for Information Technology, "IEEE Std. IEEE standard for Information Technology, "IEEE Standard
802.15.4, Part. 15.4: Wireless Medium Access Control (MAC) for Low-Rate Wireless Networks".
and Physical Layer (PHY) Specifications for Low-Rate
Wireless Personal Area Networks". [IEEE802159]
IEEE standard for Information Technology, "IEEE Std
802.15.9-2016 - IEEE Recommended Practice for Transport of
Key Management Protocol (KMP) Datagrams".
[I-D.ietf-6lo-blemesh] [I-D.ietf-6lo-blemesh]
Gomez, C., Darroudi, S., Savolainen, T., and M. Spoerk, Gomez, C., Darroudi, S., Savolainen, T., and M. Spoerk,
"IPv6 Mesh over BLUETOOTH(R) Low Energy using IPSP", "IPv6 Mesh over BLUETOOTH(R) Low Energy using IPSP",
draft-ietf-6lo-blemesh-09 (work in progress), December draft-ietf-6lo-blemesh-10 (work in progress), April 2021.
2020.
[I-D.ietf-6lo-nfc] [I-D.ietf-6lo-nfc]
Choi, Y., Hong, Y., Youn, J., Kim, D., and J. Choi, Choi, Y., Hong, Y., Youn, J., Kim, D., and J. Choi,
"Transmission of IPv6 Packets over Near Field "Transmission of IPv6 Packets over Near Field
Communication", draft-ietf-6lo-nfc-17 (work in progress), Communication", draft-ietf-6lo-nfc-17 (work in progress),
August 2020. August 2020.
[I-D.ietf-6lo-plc] [I-D.ietf-6lo-plc]
Hou, J., Liu, B., Hong, Y., Tang, X., and C. Perkins, Hou, J., Liu, B., Hong, Y., Tang, X., and C. Perkins,
"Transmission of IPv6 Packets over PLC Networks", draft- "Transmission of IPv6 Packets over PLC Networks", draft-
ietf-6lo-plc-05 (work in progress), October 2020. ietf-6lo-plc-06 (work in progress), April 2021.
[I-D.ietf-roll-useofrplinfo]
Robles, I., Richardson, M., and P. Thubert, "Using RPI
Option Type, Routing Header for Source Routes and IPv6-in-
IPv6 encapsulation in the RPL Data Plane", draft-ietf-
roll-useofrplinfo-44 (work in progress), January 2021.
[I-D.ietf-roll-unaware-leaves]
Thubert, P. and M. Richardson, "Routing for RPL Leaves",
draft-ietf-roll-unaware-leaves-30 (work in progress),
January 2021.
[I-D.ietf-roll-turnon-rfc8138]
Thubert, P. and L. Zhao, "A RPL DODAG Configuration Option
for the 6LoWPAN Routing Header", draft-ietf-roll-turnon-
rfc8138-18 (work in progress), December 2020.
[IETF_6lo] [IETF_6lo]
"IETF IPv6 over Networks of Resource-constrained Nodes "IETF IPv6 over Networks of Resource-constrained Nodes
(6lo) working group", (6lo) working group",
<https://datatracker.ietf.org/wg/6lo/charter/>. <https://datatracker.ietf.org/wg/6lo/charter/>.
[IETF_ace] [IETF_ace]
"IETF Authentication and Authorization for Constrained "IETF Authentication and Authorization for Constrained
Environments (ace) working group", Environments (ace) working group",
<https://datatracker.ietf.org/wg/ace/charter/>. <https://datatracker.ietf.org/wg/ace/charter/>.
skipping to change at page 25, line 39 skipping to change at page 25, line 29
[RFC8928] Thubert, P., Ed., Sarikaya, B., Sethi, M., and R. Struik, [RFC8928] Thubert, P., Ed., Sarikaya, B., Sethi, M., and R. Struik,
"Address-Protected Neighbor Discovery for Low-Power and "Address-Protected Neighbor Discovery for Low-Power and
Lossy Networks", RFC 8928, DOI 10.17487/RFC8928, November Lossy Networks", RFC 8928, DOI 10.17487/RFC8928, November
2020, <https://www.rfc-editor.org/info/rfc8928>. 2020, <https://www.rfc-editor.org/info/rfc8928>.
[RFC8929] Thubert, P., Ed., Perkins, C., and E. Levy-Abegnoli, "IPv6 [RFC8929] Thubert, P., Ed., Perkins, C., and E. Levy-Abegnoli, "IPv6
Backbone Router", RFC 8929, DOI 10.17487/RFC8929, November Backbone Router", RFC 8929, DOI 10.17487/RFC8929, November
2020, <https://www.rfc-editor.org/info/rfc8929>. 2020, <https://www.rfc-editor.org/info/rfc8929>.
[RFC9008] Robles, M., Richardson, M., and P. Thubert, "Using RPI
Option Type, Routing Header for Source Routes, and IPv6-
in-IPv6 Encapsulation in the RPL Data Plane", RFC 9008,
DOI 10.17487/RFC9008, April 2021,
<https://www.rfc-editor.org/info/rfc9008>.
[RFC9010] Thubert, P., Ed. and M. Richardson, "Routing for RPL
(Routing Protocol for Low-Power and Lossy Networks)
Leaves", RFC 9010, DOI 10.17487/RFC9010, April 2021,
<https://www.rfc-editor.org/info/rfc9010>.
[RFC9035] Thubert, P., Ed. and L. Zhao, "A Routing Protocol for Low-
Power and Lossy Networks (RPL) Destination-Oriented
Directed Acyclic Graph (DODAG) Configuration Option for
the 6LoWPAN Routing Header", RFC 9035,
DOI 10.17487/RFC9035, April 2021,
<https://www.rfc-editor.org/info/rfc9035>.
[TIA-485-A] [TIA-485-A]
"TIA, "Electrical Characteristics of Generators and "TIA, "Electrical Characteristics of Generators and
Receivers for Use in Balanced Digital Multipoint Systems", Receivers for Use in Balanced Digital Multipoint Systems",
TIA-485-A (Revision of TIA-485)", March 2003, TIA-485-A (Revision of TIA-485)", March 2003,
<https://global.ihs.com/ <https://global.ihs.com/
doc_detail.cfm?item_s_key=00032964>. doc_detail.cfm?item_s_key=00032964>.
Appendix A. Design Space Dimensions for 6lo Deployment Appendix A. Design Space Dimensions for 6lo Deployment
The [RFC6568] lists the dimensions used to describe the design space The [RFC6568] lists the dimensions used to describe the design space
skipping to change at page 27, line 36 skipping to change at page 27, line 41
wireless, except MS/TP and PLC. The selection of wired or wireless, except MS/TP and PLC. The selection of wired or
wireless link layer technology is mainly dependent on the wireless link layer technology is mainly dependent on the
requirement of 6lo use cases and the characteristics of wired/ requirement of 6lo use cases and the characteristics of wired/
wireless technologies. For example, some 6lo use cases may wireless technologies. For example, some 6lo use cases may
require easy and quick deployment, whereas others may need a require easy and quick deployment, whereas others may need a
continuous source of power. continuous source of power.
Authors' Addresses Authors' Addresses
Yong-Geun Hong Yong-Geun Hong
Daejeon Daejeon University
62 Daehak-ro, Dong-gu
Daejeon 34520
Korea Korea
Phone: +82 42 280 4841
Email: yonggeun.hong@gmail.com Email: yonggeun.hong@gmail.com
Carles Gomez Carles Gomez
Universitat Politecnica de Catalunya/Fundacio i2cat Universitat Politecnica de Catalunya/Fundacio i2cat
C/Esteve Terradas, 7 C/Esteve Terradas, 7
Castelldefels 08860 Castelldefels 08860
Spain Spain
Email: carlesgo@entel.upc.edu Email: carlesgo@entel.upc.edu
Younghwan Choi Younghwan Choi
ETRI ETRI
218 Gajeongno, Yuseong 218 Gajeongno, Yuseong
Daejeon 34129 Daejeon 34129
Korea Korea
Phone: +82 42 860 1429 Phone: +82 42 860 1429
Email: yhc@etri.re.kr Email: yhc@etri.re.kr
Abdur Rashid Sangi Abdur Rashid Sangi
 End of changes. 42 change blocks. 
105 lines changed or deleted 113 lines changed or added

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