< draft-ietf-6lo-use-cases-06.txt   draft-ietf-6lo-use-cases-07.txt >
6Lo Working Group Y-G. Hong 6Lo Working Group Y-G. Hong
Internet-Draft ETRI Internet-Draft ETRI
Intended status: Informational C. Gomez Intended status: Informational C. Gomez
Expires: September 12, 2019 UPC Expires: March 13, 2020 UPC
Y-H. Choi Y-H. Choi
ETRI ETRI
AR. Sangi AR. Sangi
Huaiyin Institute of Technology Huaiyin Institute of Technology
T. Aanstoot T. Aanstoot
Modio AB Modio AB
S. Chakrabarti S. Chakrabarti
March 11, 2019 September 10, 2019
IPv6 over Constrained Node Networks (6lo) Applicability & Use cases IPv6 over Constrained Node Networks (6lo) Applicability & Use cases
draft-ietf-6lo-use-cases-06 draft-ietf-6lo-use-cases-07
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 802.15.4, various link layer technologies such as
ITU-T G.9959 (Z-Wave), BLE, DECT-ULE, MS/TP, NFC, PLC (IEEE 1901.2), ITU-T G.9959 (Z-Wave), BLE, DECT-ULE, MS/TP, NFC, and PLC (IEEE
and IEEE 802.15.4e (6tisch) are used as examples. The document 1901.2) are used as examples. The document targets an audience who
targets an audience who like to understand and evaluate running end- like to understand and evaluate running end-to-end IPv6 over the
to-end IPv6 over the constrained node networks connecting devices to constrained node networks connecting devices to each other or to
each other or to other devices on the Internet (e.g. cloud other devices on the Internet (e.g. cloud infrastructure).
infrastructure).
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 September 12, 2019. This Internet-Draft will expire on March 13, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4
3. 6lo Link layer technologies and possible candidates . . . . . 4 3. 6lo Link layer technologies . . . . . . . . . . . . . . . . . 4
3.1. ITU-T G.9959 (specified) . . . . . . . . . . . . . . . . 4 3.1. ITU-T G.9959 . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Bluetooth LE (specified) . . . . . . . . . . . . . . . . 4 3.2. Bluetooth LE . . . . . . . . . . . . . . . . . . . . . . 4
3.3. DECT-ULE (specified) . . . . . . . . . . . . . . . . . . 5 3.3. DECT-ULE . . . . . . . . . . . . . . . . . . . . . . . . 5
3.4. MS/TP (specified) . . . . . . . . . . . . . . . . . . . . 5 3.4. MS/TP . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.5. NFC (specified) . . . . . . . . . . . . . . . . . . . . . 6 3.5. NFC . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.6. PLC (specified) . . . . . . . . . . . . . . . . . . . . . 7 3.6. PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.7. IEEE 802.15.4e (specified) . . . . . . . . . . . . . . . 7 3.7. Comparison between 6lo Link layer technologies . . . . . 7
3.8. Comparison between 6lo Link layer technologies . . . . . 8 4. 6lo Deployment Scenarios . . . . . . . . . . . . . . . . . . 8
4. 6lo Deployment Scenarios . . . . . . . . . . . . . . . . . . 9 4.1. G3-PLC usage of 6lo in network layer . . . . . . . . . . 8
4.1. jupitermesh in Smart Grid using 6lo in network layer . . 9 4.2. Netricity usage of 6lo in network layer . . . . . . . . . 9
4.2. Wi-SUN usage of 6lo stacks . . . . . . . . . . . . . . . 11 5. Guidelines for adopting IPv6 stack (6lo/6LoWPAN) . . . . . . 10
4.3. G3-PLC usage of 6lo in network layer . . . . . . . . . . 12 6. 6lo Use Case Examples . . . . . . . . . . . . . . . . . . . . 12
4.4. Netricity usage of 6lo in network layer . . . . . . . . . 13 6.1. Use case of ITU-T G.9959: Smart Home . . . . . . . . . . 12
5. Design Space and Guidelines for 6lo Deployment . . . . . . . 14 6.2. Use case of Bluetooth LE: Smartphone-based Interaction . 13
5.1. Design Space Dimensions for 6lo Deployment . . . . . . . 14 6.3. Use case of DECT-ULE: Smart Home . . . . . . . . . . . . 13
5.2. Guidelines for adopting IPv6 stack (6lo/6LoWPAN) . . . . 16 6.4. Use case of MS/TP: Building Automation Networks . . . . . 14
6. 6lo Use Case Examples . . . . . . . . . . . . . . . . . . . . 17 6.5. Use case of NFC: Alternative Secure Transfer . . . . . . 15
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 6.6. Use case of PLC: Smart Grid . . . . . . . . . . . . . . . 15
8. Security Considerations . . . . . . . . . . . . . . . . . . . 18 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 8. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16
10.1. Normative References . . . . . . . . . . . . . . . . . . 19 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.2. Informative References . . . . . . . . . . . . . . . . . 21 10.1. Normative References . . . . . . . . . . . . . . . . . . 17
Appendix A. Other 6lo Use Case Examples . . . . . . . . . . . . 23 10.2. Informative References . . . . . . . . . . . . . . . . . 19
A.1. Use case of ITU-T G.9959: Smart Home . . . . . . . . . . 23 Appendix A. Design Space Dimensions for 6lo Deployment . . . . . 20
A.2. Use case of DECT-ULE: Smart Home . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
A.3. Use case of MS/TP: Building Automation Networks . . . . . 25
A.4. Use case of NFC: Alternative Secure Transfer . . . . . . 25
A.5. Use case of PLC: Smart Grid . . . . . . . . . . . . . . . 26
A.6. Use case of IEEE 802.15.4e: Industrial Automation . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
Running IPv6 on constrained node networks has different features from Running IPv6 on constrained node networks has different features from
general node networks due to the characteristics of constrained node general node networks due to the characteristics of constrained node
networks such as small packet size, short link-layer address, low networks such as small packet size, short link-layer address, low
bandwidth, network topology, low power, low cost, and large number of bandwidth, network topology, low power, low cost, and large number of
devices [RFC4919][RFC7228]. For example, some IEEE 802.15.4 link devices [RFC4919][RFC7228]. For example, some IEEE 802.15.4 link
layers have a frame size of 127 octets and IPv6 requires the layer layers have a frame size of 127 octets and IPv6 requires the layer
below to support an MTU of 1280 bytes, therefore an appropriate below to support an MTU of 1280 bytes, therefore an appropriate
skipping to change at page 3, line 30 skipping to change at page 3, line 27
compression. The IETF 6LoPWAN (IPv6 over Low powerWPAN) working compression. The IETF 6LoPWAN (IPv6 over Low powerWPAN) working
group published an adaptation layer for sending IPv6 packets over group published an adaptation layer for sending IPv6 packets over
IEEE 802.15.4 [RFC4944], which includes a compression format for IPv6 IEEE 802.15.4 [RFC4944], which includes a compression format for IPv6
datagrams over IEEE 802.15.4-based networks [RFC6282], and Neighbor datagrams over IEEE 802.15.4-based networks [RFC6282], and Neighbor
Discovery Optimization for 6LoPWAN [RFC6775]. Discovery Optimization for 6LoPWAN [RFC6775].
As IoT (Internet of Things) services become more popular, IPv6 over As IoT (Internet of Things) services become more popular, IPv6 over
various link layer technologies such as Bluetooth Low Energy various link layer technologies such as Bluetooth Low Energy
(Bluetooth LE), ITU-T G.9959 (Z-Wave), Digital Enhanced Cordless (Bluetooth 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), Power Line Passing (MS/TP), Near Field Communication (NFC), and Power Line
Communication (PLC), and IEEE 802.15.4e (TSCH), have been defined at Communication (PLC) have been defined at [IETF_6lo] working group.
[IETF_6lo] working group. IPv6 stacks for constrained node networks IPv6 stacks for constrained node networks use a variation of the
use a variation of the 6LoWPAN stack applied to each particular link 6LoWPAN stack applied to each particular link layer technology.
layer technology.
In the 6LoPWAN working group, the [RFC6568], "Design and Application In the 6LoPWAN working group, the [RFC6568], "Design and Application
Spaces for 6LoWPANs" was published and it describes potential Spaces for 6LoWPANs" was published and it describes potential
application scenarios and use cases for low-power wireless personal application scenarios and use cases for low-power wireless personal
area networks. Hence, this 6lo applicability document aims to area networks. Hence, this 6lo applicability document aims to
provide guidance to an audience who are new to IPv6-over-low-power provide guidance to an audience who are new to IPv6-over-low-power
networks concept and want to assess if variance of 6LoWPAN stack networks concept and want to assess if variance of 6LoWPAN stack
[6lo] can be applied to the constrained layer two (L2) network of [6lo] can be applied to the constrained layer two (L2) network of
their interest. This 6lo applicability document puts together their interest. This 6lo applicability document puts together
various design space dimensions such as deployment, network size, various design space dimensions such as deployment, network size,
skipping to change at page 4, line 22 skipping to change at page 4, line 19
given L2 technology. given L2 technology.
o Example use cases and practical deployment examples. o Example use cases and practical deployment examples.
2. Conventions and Terminology 2. Conventions and Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. 6lo Link layer technologies and possible candidates 3. 6lo Link layer technologies
3.1. ITU-T G.9959 (specified) 3.1. ITU-T G.9959
The ITU-T G.9959 Recommendation [G.9959] targets low-power Personal The ITU-T G.9959 Recommendation [G.9959] targets low-power Personal
Area Networks (PANs), and defines physical layer and link layer Area Networks (PANs), and defines physical layer and link layer
functionality. Physical layers of 9.6 kbit/s, 40 kbit/s and 100 functionality. Physical layers of 9.6 kbit/s, 40 kbit/s and 100
kbit/s are supported. G.9959 defines how a unique 32-bit HomeID kbit/s are supported. G.9959 defines how a unique 32-bit HomeID
network identifier is assigned by a network controller and how an network identifier is assigned by a network controller and how an
8-bit NodeID host identifier is allocated to each node. NodeIDs are 8-bit NodeID host identifier is allocated to each node. NodeIDs are
unique within the network identified by the HomeID. The G.9959 unique within the network identified by the HomeID. The G.9959
HomeID represents an IPv6 subnet that is identified by one or more HomeID represents an IPv6 subnet that is identified by one or more
IPv6 prefixes [RFC7428]. The ITU-T G.9959 can be used for smart home IPv6 prefixes [RFC7428]. The ITU-T G.9959 can be used for smart home
applications. applications.
3.2. Bluetooth LE (specified) 3.2. Bluetooth LE
Bluetooth LE was introduced in Bluetooth 4.0, enhanced in Bluetooth Bluetooth LE was introduced in Bluetooth 4.0, enhanced in Bluetooth
4.1, and developed even further in successive versions. Bluetooth 4.1, and developed even further in successive versions. Bluetooth
SIG has also published Internet Protocol Support Profile (IPSP). The SIG has also published Internet Protocol Support Profile (IPSP). The
IPSP enables discovery of IP-enabled devices and establishment of IPSP enables discovery of IP-enabled devices and establishment of
link-layer connection for transporting IPv6 packets. IPv6 over link-layer connection for transporting IPv6 packets. IPv6 over
Bluetooth LE is dependent on both Bluetooth 4.1 and IPSP 1.0 or Bluetooth LE is dependent on both Bluetooth 4.1 and IPSP 1.0 or
newer. newer.
Many Devices such as mobile phones, notebooks, tablets and other Many Devices such as mobile phones, notebooks, tablets and other
skipping to change at page 5, line 12 skipping to change at page 5, line 9
collaborate with mobile devices such as phones, tablets and notebook collaborate with mobile devices such as phones, tablets and notebook
computers. An example of a use case for a Bluetooth LE accessory is computers. An example of a use case for a Bluetooth LE accessory is
a heart rate monitor that sends data via the mobile phone to a server a heart rate monitor that sends data via the mobile phone to a server
on the Internet [RFC7668]. A typical usage of Bluetooth LE is on the Internet [RFC7668]. A typical usage of Bluetooth LE is
smartphone-based interaction with constrained devices. Bluetooth LE smartphone-based interaction with constrained devices. Bluetooth LE
was originally designed to enable star topology networks. However, was originally designed to enable star topology networks. However,
recent Bluetooth versions support the formation of extended recent Bluetooth versions support the formation of extended
topologies, and IPv6 support for mesh networks of Bluetooth LE topologies, and IPv6 support for mesh networks of Bluetooth LE
devices is being developed [I-D.ietf-6lo-blemesh] devices is being developed [I-D.ietf-6lo-blemesh]
3.3. DECT-ULE (specified) 3.3. DECT-ULE
DECT ULE is a low power air interface technology that is designed to DECT ULE is a low power air interface technology that is designed to
support both circuit switched services, such as voice communication, support both circuit switched services, such as voice communication,
and packet mode data services at modest data rate. and packet mode data services at modest data rate.
The DECT ULE protocol stack consists of the PHY layer operating at The DECT ULE protocol stack consists of the PHY layer operating at
frequencies in the 1880 - 1920 MHz frequency band depending on the frequencies in the 1880 - 1920 MHz frequency band depending on the
region and uses a symbol rate of 1.152 Mbps. Radio bearers are region and uses a symbol rate of 1.152 Mbps. Radio bearers are
allocated by use of FDMA/TDMA/TDD techniques. allocated by use of FDMA/TDMA/TDD techniques.
skipping to change at page 5, line 44 skipping to change at page 5, line 41
assembly for larger packets from layers above. The DECT ULE layer assembly for larger packets from layers above. The DECT ULE layer
also implements per-message authentication and encryption. The DLC also implements per-message authentication and encryption. The DLC
layer ensures packet integrity and preserves packet order, but layer ensures packet integrity and preserves packet order, but
delivery is based on best effort. delivery is based on best effort.
The current DECT ULE MAC layer standard supports low bandwidth data The current DECT ULE MAC layer standard supports low bandwidth data
broadcast. However the usage of this broadcast service has not yet broadcast. However the usage of this broadcast service has not yet
been standardized for higher layers [RFC8105]. DECT-ULE can be used been standardized for higher layers [RFC8105]. DECT-ULE can be used
for smart metering in a home. for smart metering in a home.
3.4. MS/TP (specified) 3.4. MS/TP
Master-Slave/Token-Passing (MS/TP) is a Medium Access Control (MAC) Master-Slave/Token-Passing (MS/TP) is a Medium Access Control (MAC)
protocol for the RS-485 [TIA-485-A] physical layer and is used protocol for the RS-485 [TIA-485-A] physical layer and is used
primarily in building automation networks. primarily in building automation networks.
An MS/TP device is typically based on a low-cost microcontroller with An MS/TP device is typically based on a low-cost microcontroller with
limited processing power and memory. These constraints, together limited processing power and memory. These constraints, together
with low data rates and a small MAC address space, are similar to with low data rates and a small MAC address space, are similar to
those faced in 6LoWPAN networks. MS/TP differs significantly from those faced in 6LoWPAN networks. MS/TP differs significantly from
6LoWPAN in at least three respects: a) MS/TP devices are typically 6LoWPAN in at least three respects: a) MS/TP devices are typically
skipping to change at page 6, line 26 skipping to change at page 6, line 23
UART, an RS-485 [TIA-485-A] transceiver with a driver that can be UART, an RS-485 [TIA-485-A] transceiver with a driver that can be
disabled, and a 5 ms resolution timer. The MS/TP MAC is typically disabled, and a 5 ms resolution timer. The MS/TP MAC is typically
implemented in software. implemented in software.
Because of its superior "range" (~1 km) compared to many low power Because of its superior "range" (~1 km) compared to many low power
wireless data links, MS/TP may be suitable to connect remote devices wireless data links, MS/TP may be suitable to connect remote devices
(such as district heating controllers) to the nearest building (such as district heating controllers) to the nearest building
control infrastructure over a single link [RFC8163]. MS/TP can be control infrastructure over a single link [RFC8163]. MS/TP can be
used for building automation networks. used for building automation networks.
3.5. NFC (specified) 3.5. NFC
NFC technology enables simple and safe two-way interactions between NFC technology enables simple and safe two-way interactions between
electronic devices, allowing consumers to perform contactless electronic devices, allowing consumers to perform contactless
transactions, access digital content, and connect electronic devices transactions, access digital content, and connect electronic devices
with a single touch. NFC complements many popular consumer level with a single touch. NFC complements many popular consumer level
wireless technologies, by utilizing the key elements in existing wireless technologies, by utilizing the key elements in existing
standards for contactless card technology (ISO/IEC 14443 A&B and standards for contactless card technology (ISO/IEC 14443 A&B and
JIS-X 6319-4). NFC can be compatible with existing contactless card JIS-X 6319-4). NFC can be compatible with existing contactless card
infrastructure and it enables a consumer to utilize one device across infrastructure and it enables a consumer to utilize one device across
different systems. different systems.
skipping to change at page 7, line 5 skipping to change at page 7, line 5
share business cards, make transactions, access information from a share business cards, make transactions, access information from a
smart poster or provide credentials for access control systems with a smart poster or provide credentials for access control systems with a
simple touch. simple touch.
NFC's bidirectional communication ability is ideal for establishing NFC's bidirectional communication ability is ideal for establishing
connections with other technologies by the simplicity of touch. In connections with other technologies by the simplicity of touch. In
addition to the easy connection and quick transactions, simple data addition to the easy connection and quick transactions, simple data
sharing is also available [I-D.ietf-6lo-nfc]. NFC can be used for sharing is also available [I-D.ietf-6lo-nfc]. NFC can be used for
secure transfer in healthcare services. secure transfer in healthcare services.
3.6. PLC (specified) 3.6. PLC
PLC is a data transmission technique that utilizes power conductors PLC is a data transmission technique that utilizes power conductors
as medium. Unlike other dedicated communication infrastructure, as medium. Unlike other dedicated communication infrastructure,
power conductors are widely available indoors and outdoors. power conductors are widely available indoors and outdoors.
Moreover, wired technologies are more susceptible to cause Moreover, wired technologies are more susceptible to cause
interference but are more reliable than their wireless counterparts. interference but are more reliable than their wireless counterparts.
PLC is a data transmission technique that utilizes power conductors PLC is a data transmission technique that utilizes power conductors
as medium[I-D.ietf-6lo-plc]. as medium[I-D.ietf-6lo-plc].
The below table shows some available open standards defining PLC. The below table shows some available open standards defining PLC.
skipping to change at page 7, line 44 skipping to change at page 7, line 44
[IEEE1901.2] defines a narrowband variant of PLC with less data rate [IEEE1901.2] defines a narrowband variant of PLC with less data rate
but significantly higher transmission range that could be used in an but significantly higher transmission range that could be used in an
indoor or even an outdoor environment. It is applicable to typical indoor or even an outdoor environment. It is applicable to typical
IoT applications such as: Building Automation, Renewable Energy, IoT applications such as: Building Automation, Renewable Energy,
Advanced Metering, Street Lighting, Electric Vehicle, Smart Grid etc. Advanced Metering, Street Lighting, Electric Vehicle, Smart Grid etc.
Moreover, IEEE 1901.2 standard is based on the 802.15.4 MAC sub-layer Moreover, IEEE 1901.2 standard is based on the 802.15.4 MAC sub-layer
and fully endorses the security scheme defined in 802.15.4 [RFC8036]. and fully endorses the security scheme defined in 802.15.4 [RFC8036].
A typical use case of PLC is smart grid. A typical use case of PLC is smart grid.
3.7. IEEE 802.15.4e (specified) 3.7. Comparison between 6lo Link layer technologies
The Time Slotted Channel Hopping (TSCH) mode was introduced in the
IEEE 802.15.4-2015 standard. In a TSCH network, all nodes are
synchronized. Time is sliced up into timeslots. The duration of a
timeslot, typically 10ms, is large enough for a node to send a full-
sized frame to its neighbor, and for that neighbor to send back an
acknowledgment to indicate successful reception. Timeslots are
grouped into one of more slotframes, which repeat over time.
All the communication in the network is orchestrated by a
communication schedule which indicates to each node what to do in
each of the timeslots of a slotframe: transmit, listen or sleep. The
communication schedule can be built so that the right amount of link-
layer resources (the cells in the schedule) are scheduled to satisfy
the communication needs of the applications running on the network,
while keeping the energy consumption of the nodes very low. Cells
can be scheduled in a collision-free way, introducing a high level of
determinism to the network.
A TSCH network exploits channel hopping: subsequent packet exchanges
between neighbor nodes are done on a different frequency. This means
that, if a frame isn't received, the transmitter node will re-
transmitt the frame on a different frequency. The resulting "channel
hopping" efficiently combats external interference and multi-path
fading.
The main benefits of IEEE 802.15.4 TSCH are:
- ultra high reliability. Off-the-shelf commercial products offer
over 99.999% end-to-end reliability.
- ultra low-power consumption. Off-the-shelf commercial products
offer over a decade of battery lifetime.
- 6TiSCH at IETF defines communications of TSCH network and it
uses 6LoWPAN stack [RFC7554].
IEEE 802.15.4e can be used for industrial automation.
3.8. Comparison between 6lo Link layer technologies
In above clauses, various 6lo Link layer technologies and a possible In above clauses, various 6lo Link layer technologies and a possible
candidate are described. The following table shows that dominant candidate are described. The following table shows that dominant
paramters of each use case corresponding to the 6lo link layer paramters of each use case corresponding to the 6lo link layer
technology. technology.
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| | Z-Wave | BLE |DECT-ULE| MS/TP | NFC | PLC | TSCH | | | Z-Wave | BLE | DECT-ULE| MS/TP | NFC | PLC |
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| | Home |Interact| |Building| Health-| |Industr-| | | Home | Interact| | Building| Health- | |
| Usage | Auto- |w/ Smart| Meter | Auto- | care | Smart |ial Aut-| | Usage | Auto- | w/ Smart| Meter | Auto- | care | Smart |
| | mation | Phone | Reading| mation | Service| Grid | mation | | | mation | Phone | Reading | mation | Service | Grid |
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| Topology | L2-mesh| Star | Star | MS/TP | P2P | Star | | | Topology | L2-mesh | Star | Star | MS/TP | P2P | Star |
| & | or | & | | | | Tree | Mesh | | & | or | & | | | | Tree |
| Subnet | L3-mesh| Mesh | No mesh| No mesh| L2-mesh| Mesh | | | Subnet | L3-mesh | Mesh | No mesh | No mesh | L2-mesh | Mesh |
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| | | | | | | | | | | | | | | | |
| Mobility | No | Low | No | No |Moderate| No | No | | Mobility | No | Low | No | No | Moderate| No |
| Reqmt | | | | | | | | | Requirement | | | | | | |
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| | High + | | High + | High + | | High + | High + | | | High + | | High + | High + | | High + |
| Security | Privacy| Parti- | Privacy| Authen.| High |Encrypt.| Privacy| | Security | Privacy |Partially| Privacy | Authen. | High | Encrypt.|
| Reqmt |required| ally |required|required| |required|required| | Requirement | required| | required| required| | required|
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| | | | | | | | | | | | | | | | |
| Buffering | Low | Low | Low | Low | Low | Low | Low | | Buffering | Low | Low | Low | Low | Low | Low |
| Reqmt | | | | | | | | | Requirement | | | | | | |
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| Latency, | | | | | | | | | Latency, | | | | | | |
| QoS | High | Low | Low | High | High | Low | High | | QoS | High | Low | Low | High | High | Low |
| Reqmt | | | | | | | | | Requirement | | | | | | |
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| | | | | | | | | | | | | | | | |
| Data |Infrequ-|Infrequ-|Infrequ-|Frequent| Small |Infrequ-|Infrequ-| | Data | Infrequ-| Infrequ-| Infrequ-| Frequent| Small | Infrequ-|
| Rate | ent | ent | ent | | | ent | ent | | Rate | ent | ent | ent | | | ent |
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
| RFC # | | | | | draft- | draft- | | | RFC # | | | | | draft- | draft- |
| or | RFC7428| RFC7668| RFC8105| RFC8163|ietf-6lo|ietf-6lo| RFC7554| | or | RFC7428 | RFC7668 | RFC8105 | RFC8163 | ietf-6lo| ietf-6lo|
| Draft | | | | | -nfc | -plc | | | Draft | | | | | -nfc | -plc |
+-----------+--------+--------+--------+--------+--------+--------+--------+ +--------------+---------+---------+---------+---------+---------+---------+
Table 2: Comparison between 6lo Link layer technologies Table 2: Comparison between 6lo Link layer technologies
4. 6lo Deployment Scenarios 4. 6lo Deployment Scenarios
4.1. jupitermesh in Smart Grid using 6lo in network layer 4.1. G3-PLC usage of 6lo in network layer
jupiterMesh is a multi-hop wireless mesh network specification
designed mainly for deployment in large geographical areas. Each
subnet in jupiterMesh is able to cover an entire neighborhood with
thousands of nodes consisting of IPv6-enabled routers and end-points
(e.g. hosts). Automated network joining and load balancing allows a
seamless deployment of a large number of subnets.
The main application domains targeted by jupiterMesh are smart grid
and smart cities. This includes, but is not limited to the following
applications:
o Automated meter reading
o Distribution Automation (DA)
o Demand-side management (DSM)
o Demand-side response (DSR)
o Power outage reporting
o Street light monitoring and control
o Transformer load management
o EV charging coordination
o Energy theft
o Parking space locator
jupiterMesh specification is based on the following technologies:
o The PHY layer is based on IEEE 802.15.4 SUN specification [IEEE
802.15.4-2015], supporting multiple operating modes for deployment
in different regulatory domains and deployment scenarios in terms
of density and bandwidth requirements. jupiterMesh supports bit
rates from 50 kbps to 800 kbps, frame size up to 2048 bytes, up to
11 different RF bands and 3 modulation types (i.e., FSK, OQPSK and
OFDM).
o The MAC layer is based on IEEE 802.15.4 TSCH specification [IEEE
802.15.4-2015]. With frequency hopping capability, TSCH MAC
supports scheduling of dedicated timeslot enabling bandwidth
management and QoS.
o The security layer consists of a certificate-based (i.e. X.509)
network access authentication using EAP-TLS, with IEEE
802.15.9-based KMP (Key Management Protocol) transport, and PANA
and link layer encryption using AES-128 CCM as specified in IEEE
802.15.4-2015 [IEEE 802.15.4-2015].
o Address assignment and network configuration are specified using
DHCPv6 [RFC3315]. Neighbor Discovery (ND) [RFC6775] and stateless
address auto-configuration (SLAAC) are not supported.
o The network layer consists of IPv6, ICMPv6 and 6lo/6LoPWAN header
compression [RFC6282]. Multicast is supported using MPL. Two
domains are supported, a delay sensitive MPL domain for low
latency applications (e.g. DSM, DSR) and a delay insensitive one
for less stringent applications (e.g. OTA file transfers).
o The routing layer uses RPL [RFC6550] in non-storing mode with the
MRHOF objective function based on the ETX metric.
4.2. Wi-SUN usage of 6lo stacks
Wireless Smart Ubiquitous Network (Wi-SUN) is a technology based on
the IEEE 802.15.4g standard. Wi-SUN networks support star and mesh
topologies, as well as hybrid star/mesh deployments, but are
typically laid out in a mesh topology where each node relays data for
the network to provide network connectivity. Wi-SUN networks are
deployed on both powered and battery-operated devices.
The main application domains targeted by Wi-SUN are smart utility and
smart city networks. This includes, but is not limited to the
following applications:
o Advanced Metering Infrastructure (AMI)
o Distribution Automation
o Home Energy Management
o Infrastructure Management
o Intelligent Transportation Systems
o Smart Street Lighting
o Agriculture
o Structural health (bridges, buildings etc)
o Monitoring and Asset Management
o Smart Thermostats, Air Conditioning and Heat Controls
o Energy Usage Information Displays
The Wi-SUN Alliance Field Area Network (FAN) covers primarily outdoor
networks, and its specification is oriented towards meeting the more
rigorous challenges of these environments. Examples include from
meter to outdoor access point/router for AMI and DR, or between
switches for DA. However, nothing in the profile restricts it to
outdoor use. It has the following features;
o Open standards based on IEEE802, IETF, TIA, ETSI
o Architecture is an IPv6 frequency hopping wireless mesh network
with enterprise level security
o Simple infrastructure which is low cost, low complexity
o Enhanced network robustness, reliability, and resilience to
interference, due to high redundancy and frequency hopping
o Enhaced scalability, long range, and energy friendliness
o Supports multiple global license-exempt sub GHz bands
o Multi-vendor interoperability
o Very low power modes in development permitting long term battery
operation of network nodes
In the Wi-SUN FAN specification, adaptation layer based on 6lo and
IPv6 network layer are described. So, IPv6 protocol suite including
TCP/UDP, 6lo Adaptation, Header Compression, DHCPv6 for IP address
management, Routing using RPL, ICMPv6, and Unicast/Multicast
forwarding is utilized.
4.3. G3-PLC usage of 6lo in network layer
G3-PLC [G3-PLC] is a narrow-band PLC technology that is based on G3-PLC [G3-PLC] is a narrow-band PLC technology that is based on
ITU-T G.9903 Recommendation [G.9903]. G3-PLC supports multi-hop mesh ITU-T G.9903 Recommendation [G.9903]. G3-PLC supports multi-hop mesh
network, and facilitates highly-reliable, long-range communication. network, and facilitates highly-reliable, long-range communication.
With the abilities to support IPv6 and to cross transformers, G3-PLC With the abilities to support IPv6 and to cross transformers, G3-PLC
is regarded as one of the next-generation NB-PLC technologies. is regarded as one of the next-generation NB-PLC technologies.
G3-PLC has got massive deployments over several countries, e.g. G3-PLC has got massive deployments over several countries, e.g.
Japan and France. Japan and France.
The main application domains targeted by G3-PLC are smart grid and The main application domains targeted by G3-PLC 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:
o Smart Metering o Smart Metering
o Vehicle-to-Grid Communication o Vehicle-to-Grid Communication
o Demand Response (DR) o Demand Response (DR)
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
skipping to change at page 13, line 27 skipping to change at page 9, line 37
In the G3-PLC specification, the 6lo adaptation layer utilizes the In the G3-PLC specification, the 6lo adaptation layer utilizes the
6LoWPAN functions (e.g. header compression, fragmentation and 6LoWPAN functions (e.g. header compression, fragmentation and
reassembly) so as to enable IPv6 packet transmission. LOADng, which reassembly) so as to enable IPv6 packet transmission. LOADng, which
is a lightweight variant of AODV, is applied as the mesh-under is a lightweight variant of AODV, is applied as the mesh-under
routing protocol in G3-PLC networks. Address assignment and network routing protocol in G3-PLC networks. Address assignment and network
configuration are based on the bootstrapping protocol specified in configuration are based on the bootstrapping protocol specified in
ITU-T G.9903. The network layer consists of IPv6 and ICMPv6 while ITU-T G.9903. The network layer consists of IPv6 and ICMPv6 while
the transport protocol UDP is used for data transmission. the transport protocol UDP is used for data transmission.
4.4. Netricity usage of 6lo in network layer 4.2. 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 1901.2 Low-
Frequency Narrow-Band PLC standard, which provides for urban and long Frequency Narrow-Band 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
skipping to change at page 13, line 42 skipping to change at page 10, line 4
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:
o Utility grid modernization o Utility grid modernization
o Distribution automation o Distribution automation
o Meter-to-Grid connectivity o Meter-to-Grid connectivity
o Micro-grids o Micro-grids
o Grid sensor communications o Grid sensor communications
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 PHY and MAC layers of Netricity system architecture is based on the PHY and MAC layers of
IEEE 1901.2 PLC standard. Regarding the 6lo adaptation layer and IEEE 1901.2 PLC standard. Regarding the 6lo adaptation layer and
IPv6 network layer, Netricity utilizes IPv6 protocol suite including IPv6 network layer, Netricity utilizes IPv6 protocol suite including
6lo/6LoWPAN header compression, DHCPv6 for IP address management, RPL 6lo/6LoWPAN header compression, DHCPv6 for IP address management, RPL
routing protocol, ICMPv6, and unicast/multicast forwarding. Note routing protocol, ICMPv6, and unicast/multicast forwarding. Note
that the layer 3 routing in Netricity uses RPL in non-storing mode that the layer 3 routing in Netricity uses RPL in non-storing mode
with the MRHOF objective function based on the own defined Estimated with the MRHOF objective function based on the own defined Estimated
Transmission Time (ETT) metric. Transmission Time (ETT) metric.
5. Design Space and Guidelines for 6lo Deployment 5. Guidelines for adopting IPv6 stack (6lo/6LoWPAN)
5.1. Design Space Dimensions for 6lo Deployment
The [RFC6568] lists the dimensions used to describe the design space
of wireless sensor networks in the context of the 6LoWPAN working
group. The design space is already limited by the unique
characteristics of a LoWPAN (e.g. low power, short range, low bit
rate). In [RFC6568], the following design space dimensions are
described: Deployment, Network size, Power source, Connectivity,
Multi-hop communication, Traffic pattern, Mobility, Quality of
Service (QoS). However, in this document, the following design space
dimensions are considered:
o Deployment/Bootstrapping: 6lo nodes can be connected randomly, or
in an organized manner. The bootstrapping has different
characteristics for each link layer technology.
o Topology: Topology of 6lo networks may inherently follow the
characteristics of each link layer technology. Point-to-point,
star, tree or mesh topologies can be configured, depending on the
link layer technology considered.
o L2-Mesh or L3-Mesh: L2-mesh and L3-mesh may inherently follow the
characteristics of each link layer technology. Some link layer
technologies may support L2-mesh and some may not support.
o Multi-link subnet, single subnet: The selection of multi-link
subnet and single subnet depends on connectivity and the number of
6lo nodes.
o Data rate: Typically, the link layer technologies of 6lo have low
rate of data transmission. But, by adjusting the MTU, it can
deliver higher upper layer data rate.
o Buffering requirements: Some 6lo use case may require more data
rate than the link layer technology support. In this case, a
buffering mechanism to manage the data is required.
o Security and Privacy Requirements: Some 6lo use case can involve
transferring some important and personal data between 6lo nodes.
In this case, high-level security support is required.
o Mobility across 6lo networks and subnets: The movement of 6lo
nodes depends on the 6lo use case. If the 6lo nodes can move or
moved around, a mobility management mechanism is required.
o Time synchronization requirements: The requirement of time
synchronization of the upper layer service is dependent on the 6lo
use case. For some 6lo use case related to health service, the
measured data must be recorded with exact time and must be
transferred with time synchronization.
o Reliability and QoS: Some 6lo use case requires high reliability,
for example real-time service or health-related services.
o Traffic patterns: 6lo use cases may involve various traffic
patterns. For example, some 6lo use case may require short data
length and random transmission. Some 6lo use case may require
continuous data and periodic data transmission.
o Security Bootstrapping: Without the external operations, 6lo nodes
must have the security bootstrapping mechanism.
o Power use strategy: to enable certain use cases, there may be
requirements on the class of energy availability and the strategy
followed for using power for communication [RFC7228]. Each link
layer technology defines a particular power use strategy which may
be tuned [RFC8352]. Readers are expected to be familiar with
[RFC7228] terminology.
o Update firmware requirements: Most 6lo use cases will need a
mechanism for updating firmware. In these cases support for over
the air updates are required, probably in a broadcast mode when
bandwith is low and the number of identical devices is high.
o Wired vs. Wireless: Plenty of 6lo link layer technologies are
wireless, except MS/TP and PLC. The selection of wired or
wireless link layer technology is mainly dependent on the
requirement of 6lo use cases and the characteristics of wired/
wireless technologies. For example, some 6lo use cases may
require easy and quick deployment, whereas others may need a
continuous source of power.
5.2. Guidelines for adopting IPv6 stack (6lo/6LoWPAN)
The following guideline targets new candidate constrained L2 The following guideline targets new candidate constrained L2
technologies that may be considered for running modified 6LoWPAN technologies that may be considered for running modified 6LoWPAN
stack on top. The modification of 6LoWPAN stack should be based on stack on top. The modification of 6LoWPAN stack should be based on
the following: the following:
o Addressing Model: Addressing model determines whether the device o Addressing Model: Addressing model determines whether the device
is capable of forming IPv6 Link-local and global addresses and is capable of forming IPv6 Link-local and global addresses and
what is the best way to derive the IPv6 addresses for the what is the best way to derive the IPv6 addresses for the
constrained L2 devices. Whether the device is capable of forming constrained L2 devices. Whether the device is capable of forming
skipping to change at page 17, line 31 skipping to change at page 12, line 4
[RFC7668], [RFC8163], [RFC8105]. A generic header compression [RFC7668], [RFC8163], [RFC8105]. A generic header compression
technique is specified in [RFC7400]. technique is specified in [RFC7400].
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 [ace] and [core] security is highly desirable. The working groups [ace] and [core]
should be consulted for application and transport level security. should be consulted for application and transport level security.
6lo working group is working on address authentication [6lo-ap-nd] 6lo working group is working on address authentication [6lo-ap-nd]
and secure bootstrapping is also being discussed at IETF. and secure bootstrapping is also being discussed at IETF.
However, there may be different levels of security available in a However, there may be different levels of security available in a
deployment through other standards such as hardware level security deployment through other standards such as hardware level security
or certificates for initial booting process. Encryption is or certificates for initial booting process. Encryption is
important if the implementation can afford it. important if the implementation can afford it.
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.
6. 6lo Use Case Examples 6. 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 clause, one 6lo use various 6lo use cases can be provided. In this clause, various 6lo
case example of Bluetooth LE (Smartphone-Based Interaction with use cases which are based on each particular link layer technology
Constrained Devices) is described. Other 6lo use case examples are are described.
described in Appendix.
6.1. Use case of ITU-T G.9959: Smart Home
Z-Wave is one of the main technologies that may be used to enable
smart home applications. Born as a proprietary technology, Z-Wave
was specifically designed for this particular use case. Recently,
the Z-Wave radio interface (physical and MAC layers) has been
standardized as the ITU-T G.9959 specification.
Example: Use of ITU-T G.9959 for Home Automation
Variety of home devices (e.g. light dimmers/switches, plugs,
thermostats, blinds/curtains and remote controls) are augmented with
ITU-T G.9959 interfaces. A user may turn on/off or may control home
appliances by pressing a wall switch or by pressing a button in a
remote control. Scenes may be programmed, so that after a given
event, the home devices adopt a specific configuration. Sensors may
also periodically send measurements of several parameters (e.g. gas
presence, light, temperature, humidity, etc.) which are collected at
a sink device, or may generate commands for actuators (e.g. a smoke
sensor may send an alarm message to a safety system).
The devices involved in the described scenario are nodes of a network
that follows the mesh topology, which is suitable for path diversity
to face indoor multipath propagation issues. The multihop paradigm
allows end-to-end connectivity when direct range communication is not
possible. Security support is required, specially for safety-related
communication. When a user interaction (e.g. a button press)
triggers a message that encapsulates a command, if the message is
lost, the user may have to perform further interactions to achieve
the desired effect (e.g. a light is turned off). A reaction to a
user interaction will be perceived by the user as immediate as long
as the reaction takes place within 0.5 seconds [RFC5826].
6.2. Use case of Bluetooth LE: Smartphone-based Interaction
The key feature behind the current high Bluetooth LE momentum is its The key feature behind the current high Bluetooth LE momentum is its
support in a large majority of smartphones in the market. Bluetooth support in a large majority of smartphones in the market. Bluetooth
LE can be used to allow the interaction between the smartphone and LE can be used to allow the interaction between the smartphone and
surrounding sensors or actuators. Furthermore, Bluetooth LE is also surrounding sensors or actuators. Furthermore, Bluetooth LE is also
the main radio interface currently available in wearables. Since a the main radio interface currently available in wearables. Since a
smartphone typically has several radio interfaces that provide smartphone typically has several radio interfaces that provide
Internet access, such as Wi-Fi or 4G, the smartphone can act as a Internet access, such as Wi-Fi or 4G, the smartphone can act as a
gateway for nearby devices such as sensors, actuators or wearables. gateway for nearby devices such as sensors, actuators or wearables.
Bluetooth LE may be used in several domains, including healthcare, Bluetooth LE may be used in several domains, including healthcare,
skipping to change at page 18, line 34 skipping to change at page 13, line 41
the other hand, the smartphone may locally generate messages for the the other hand, the smartphone may locally generate messages for the
smartwatch, such as e-mail reception or calendar notifications. smartwatch, such as e-mail reception or calendar notifications.
The functionality supported by the smartwatch may be complemented by The functionality supported by the smartwatch may be complemented by
other devices such as other on-body sensors, wireless headsets or other devices such as other on-body sensors, wireless headsets or
head-mounted displays. All such devices may connect to the head-mounted displays. All such devices may connect to the
smartphone creating a star topology network whereby the smartphone is smartphone creating a star topology network whereby the smartphone is
the central component. Support for extended network topologies (e.g. the central component. Support for extended network topologies (e.g.
mesh networks) is being developed as of the writing. mesh networks) is being developed as of the writing.
6.3. Use case of DECT-ULE: Smart Home
DECT is a technology widely used for wireless telephone
communications in residential scenarios. Since DECT-ULE is a low-
power variant of DECT, DECT-ULE can be used to connect constrained
devices such as sensors and actuators to a Fixed Part, a device that
typically acts as a base station for wireless telephones. Therefore,
DECT-ULE is specially suitable for the connected home space in
application areas such as home automation, smart metering, safety,
healthcare, etc.
Example: Use of DECT-ULE for Smart Metering
The smart electricity meter of a home is equipped with a DECT-ULE
transceiver. This device is in the coverage range of the Fixed Part
of the home. The Fixed Part can act as a router connected to the
Internet. This way, the smart meter can transmit electricity
consumption readings through the DECT-ULE link with the Fixed Part,
and the latter can forward such readings to the utility company using
Wide Area Network (WAN) links. The meter can also receive queries
from the utility company or from an advanced energy control system
controlled by the user, which may also be connected to the Fixed Part
via DECT-ULE.
6.4. Use case of MS/TP: Building Automation Networks
The primary use case for IPv6 over MS/TP (6LoBAC) is in building
automation networks. [BACnet] is the open international standard
protocol for building automation, and MS/TP is defined in [BACnet]
Clause 9. MS/TP was designed to be a low cost multi-drop field bus
to inter-connect the most numerous elements (sensors and actuators)
of a building automation network to their controllers. A key aspect
of 6LoBAC is that it is designed to co-exist with BACnet MS/TP on the
same link, easing the ultimate transition of some BACnet networks to
native end-to-end IPv6 transport protocols. New applications for
6LoBAC may be found in other domains where low cost, long distance,
and low latency are required.
Example: Use of 6LoBAC in Building Automation Networks
The majority of installations for MS/TP are for "terminal" or
"unitary" controllers, i.e. single zone or room controllers that may
connect to HVAC or other controls such as lighting or blinds. The
economics of daisy-chaining a single twisted-pair between multiple
devices is often preferred over home-run Cat-5 style wiring.
A multi-zone controller might be implemented as an IP router between
a traditional Ethernet link and several 6LoBAC links, fanning out to
multiple terminal controllers.
The superior distance capabilities of MS/TP (~1 km) compared to other
6lo media may suggest its use in applications to connect remote
devices to the nearest building infrastructure. for example, remote
pumping or measuring stations with moderate bandwidth requirements
can benefit from the low cost and robust capabilities of MS/TP over
other wired technologies such as DSL, and without the line-of-site
restrictions or hop-by-hop latency of many low cost wireless
solutions.
6.5. Use case of NFC: Alternative Secure Transfer
According to applications, various secured data can be handled and
transferred. Depending on security level of the data, methods for
transfer can be alternatively selected.
Example: Use of NFC for Secure Transfer in Healthcare Services with
Tele-Assistance
A senior citizen who lives alone wears one to several wearable 6lo
devices to measure heartbeat, pulse rate, etc. The 6lo devices are
densely installed at home for movement detection. An LoWPAN Border
Router (LBR) at home will send the sensed information to a connected
healthcare center. Portable base stations with LCDs may be used to
check the data at home, as well. Data is gathered in both periodic
and event-driven fashion. In this application, event-driven data can
be very time-critical. In addition, privacy also becomes a serious
issue in this case, as the sensed data is very personal.
While the senior citizen is provided audio and video healthcare
services by a tele-assistance based on LTE connections, the senior
citizen can alternatively use NFC connections to transfer the
personal sensed data to the tele-assistance. At this moment, hidden
hackers can overhear the data based on the LTE connection, but they
cannot gather the personal data over the NFC connection.
6.6. Use case of PLC: Smart Grid
Smart grid concept is based on numerous operational and energy
measuring sub-systems of an electric grid. It comprises of multiple
administrative levels/segments to provide connectivity among these
numerous components. Last mile connectivity is established over LV
segment, whereas connectivity over electricity distribution takes
place in HV segment.
Although other wired and wireless technologies are also used in Smart
Grid (Advance Metering Infrastructure - AMI, Demand Response - DR,
Home Energy Management System - HEMS, Wide Area Situational Awareness
- WASA etc), PLC enjoys the advantage of existing (power conductor)
medium and better reliable data communication. PLC is a promising
wired communication technology in that the electrical power lines are
already there and the deployment cost can be comparable to wireless
technologies. The 6lo related scenarios lie in the low voltage PLC
networks with most applications in the area of Advanced Metering
Infrastructure, Vehicle-to-Grid communications, in-home energy
management and smart street lighting.
Example: Use of PLC for Advanced Metering Infrastructure
Household electricity meters transmit time-based data of electric
power consumption through PLC. Data concentrators receive all the
meter data in their corresponding living districts and send them to
the Meter Data Management System (MDMS) through WAN network (e.g.
Medium-Voltage PLC, Ethernet or GPRS) for storage and analysis. Two-
way communications are enabled which means smart meters can do
actions like notification of electricity charges according to the
commands from the utility company.
With the existing power line infrastructure as communication medium,
cost on building up the PLC network is naturally saved, and more
importantly, labor operational costs can be minimized from a long-
term perspective. Furthermore, this AMI application speeds up
electricity charge, reduces losses by restraining power theft and
helps to manage the health of the grid based on line loss analysis.
Example: Use of PLC (IEEE1901.1) for WASA in Smart Grid
Many sub-systems of Smart Grid require low data rate and narrowband
variant (IEEE1901.2) of PLC fulfils such requirements. Recently,
more complex scenarios are emerging that require higher data rates.
WASA sub-system is an appropriate example that collects large amount
of information about the current state of the grid over wide area
from electric substations as well as power transmission lines. The
collected feedback is used for monitoring, controlling and protecting
all the sub-systems.
7. IANA Considerations 7. IANA Considerations
There are no IANA considerations related to this document. There are no IANA considerations related to this document.
8. Security Considerations 8. Security Considerations
Security considerations are not directly applicable to this document. Security considerations are not directly applicable to this document.
The use cases will use the security requirements described in the The use cases will use the security requirements described in the
protocol specifications. protocol specifications.
skipping to change at page 20, line 39 skipping to change at page 18, line 32
[RFC7400] Bormann, C., "6LoWPAN-GHC: Generic Header Compression for [RFC7400] Bormann, C., "6LoWPAN-GHC: Generic Header Compression for
IPv6 over Low-Power Wireless Personal Area Networks IPv6 over Low-Power Wireless Personal Area Networks
(6LoWPANs)", RFC 7400, DOI 10.17487/RFC7400, November (6LoWPANs)", RFC 7400, DOI 10.17487/RFC7400, November
2014, <https://www.rfc-editor.org/info/rfc7400>. 2014, <https://www.rfc-editor.org/info/rfc7400>.
[RFC7428] Brandt, A. and J. Buron, "Transmission of IPv6 Packets [RFC7428] Brandt, A. and J. Buron, "Transmission of IPv6 Packets
over ITU-T G.9959 Networks", RFC 7428, over ITU-T G.9959 Networks", RFC 7428,
DOI 10.17487/RFC7428, February 2015, DOI 10.17487/RFC7428, February 2015,
<https://www.rfc-editor.org/info/rfc7428>. <https://www.rfc-editor.org/info/rfc7428>.
[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using
IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the
Internet of Things (IoT): Problem Statement", RFC 7554,
DOI 10.17487/RFC7554, May 2015,
<https://www.rfc-editor.org/info/rfc7554>.
[RFC7668] Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., [RFC7668] Nieminen, J., Savolainen, T., Isomaki, M., Patil, B.,
Shelby, Z., and C. Gomez, "IPv6 over BLUETOOTH(R) Low Shelby, Z., and C. Gomez, "IPv6 over BLUETOOTH(R) Low
Energy", RFC 7668, DOI 10.17487/RFC7668, October 2015, Energy", RFC 7668, DOI 10.17487/RFC7668, October 2015,
<https://www.rfc-editor.org/info/rfc7668>. <https://www.rfc-editor.org/info/rfc7668>.
[RFC8036] Cam-Winget, N., Ed., Hui, J., and D. Popa, "Applicability [RFC8036] Cam-Winget, N., Ed., Hui, J., and D. Popa, "Applicability
Statement for the Routing Protocol for Low-Power and Lossy Statement for the Routing Protocol for Low-Power and Lossy
Networks (RPL) in Advanced Metering Infrastructure (AMI) Networks (RPL) in Advanced Metering Infrastructure (AMI)
Networks", RFC 8036, DOI 10.17487/RFC8036, January 2017, Networks", RFC 8036, DOI 10.17487/RFC8036, January 2017,
<https://www.rfc-editor.org/info/rfc8036>. <https://www.rfc-editor.org/info/rfc8036>.
skipping to change at page 21, line 39 skipping to change at page 19, line 23
Passing (MS/TP) Networks", RFC 8163, DOI 10.17487/RFC8163, Passing (MS/TP) Networks", RFC 8163, DOI 10.17487/RFC8163,
May 2017, <https://www.rfc-editor.org/info/rfc8163>. May 2017, <https://www.rfc-editor.org/info/rfc8163>.
[RFC8352] Gomez, C., Kovatsch, M., Tian, H., and Z. Cao, Ed., [RFC8352] Gomez, C., Kovatsch, M., Tian, H., and Z. Cao, Ed.,
"Energy-Efficient Features of Internet of Things "Energy-Efficient Features of Internet of Things
Protocols", RFC 8352, DOI 10.17487/RFC8352, April 2018, Protocols", RFC 8352, DOI 10.17487/RFC8352, April 2018,
<https://www.rfc-editor.org/info/rfc8352>. <https://www.rfc-editor.org/info/rfc8352>.
10.2. Informative References 10.2. Informative References
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
C., and M. Carney, "Dynamic Host Configuration Protocol
for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <https://www.rfc-editor.org/info/rfc3315>.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
DOI 10.17487/RFC4861, September 2007, DOI 10.17487/RFC4861, September 2007,
<https://www.rfc-editor.org/info/rfc4861>. <https://www.rfc-editor.org/info/rfc4861>.
[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-13 (work in progress), Communication", draft-ietf-6lo-nfc-15 (work in progress),
February 2019. July 2019.
[I-D.ietf-roll-aodv-rpl]
Anamalamudi, S., Zhang, M., Perkins, C., Anand, S., and B.
Liu, "Asymmetric AODV-P2P-RPL in Low-Power and Lossy
Networks (LLNs)", draft-ietf-roll-aodv-rpl-06 (work in
progress), March 2019.
[I-D.ietf-6tisch-6top-sfx]
Dujovne, D., Grieco, L., Palattella, M., and N. Accettura,
"6TiSCH Experimental Scheduling Function (SFX)", draft-
ietf-6tisch-6top-sfx-01 (work in progress), March 2018.
[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-04 (work in progress), January draft-ietf-6lo-blemesh-05 (work in progress), March 2019.
2019.
[I-D.satish-6tisch-6top-sf1]
Anamalamudi, S., Liu, B., Zhang, M., Sangi, A., Perkins,
C., and S. Anand, "Scheduling Function One (SF1): hop-by-
hop Scheduling with RSVP-TE in 6tisch Networks", draft-
satish-6tisch-6top-sf1-04 (work in progress), October
2017.
[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-00 (work in progress), February 2019. ietf-6lo-plc-00 (work in progress), February 2019.
[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/>.
skipping to change at page 23, line 26 skipping to change at page 20, line 35
communication transceivers for G3-PLC networks", ITU-T communication transceivers for G3-PLC networks", ITU-T
Recommendation", August 2017. Recommendation", August 2017.
[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]
"IEEE Standard (work-in-progress), IEEE-SA Standards
Board", <http://sites.ieee.org/sagroups-1901-1/>.
[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>.
[BACnet] "ASHRAE, "BACnet-A Data Communication Protocol for [BACnet] "ASHRAE, "BACnet-A Data Communication Protocol for
Building Automation and Control Networks", ANSI/ASHRAE Building Automation and Control Networks", ANSI/ASHRAE
Standard 135-2016", January 2016, Standard 135-2016", January 2016,
<http://www.techstreet.com/ashrae/standards/ <http://www.techstreet.com/ashrae/standards/ashrae-
ashrae-135-2016?product_id=1918140#jumps>. 135-2016?product_id=1918140#jumps>.
Appendix A. Other 6lo Use Case Examples
A.1. Use case of ITU-T G.9959: Smart Home
Z-Wave is one of the main technologies that may be used to enable
smart home applications. Born as a proprietary technology, Z-Wave
was specifically designed for this particular use case. Recently,
the Z-Wave radio interface (physical and MAC layers) has been
standardized as the ITU-T G.9959 specification.
Example: Use of ITU-T G.9959 for Home Automation
Variety of home devices (e.g. light dimmers/switches, plugs,
thermostats, blinds/curtains and remote controls) are augmented with
ITU-T G.9959 interfaces. A user may turn on/off or may control home
appliances by pressing a wall switch or by pressing a button in a
remote control. Scenes may be programmed, so that after a given
event, the home devices adopt a specific configuration. Sensors may
also periodically send measurements of several parameters (e.g. gas
presence, light, temperature, humidity, etc.) which are collected at
a sink device, or may generate commands for actuators (e.g. a smoke
sensor may send an alarm message to a safety system).
The devices involved in the described scenario are nodes of a network
that follows the mesh topology, which is suitable for path diversity
to face indoor multipath propagation issues. The multihop paradigm
allows end-to-end connectivity when direct range communication is not
possible. Security support is required, specially for safety-related
communication. When a user interaction (e.g. a button press)
triggers a message that encapsulates a command, if the message is
lost, the user may have to perform further interactions to achieve
the desired effect (e.g. a light is turned off). A reaction to a
user interaction will be perceived by the user as immediate as long
as the reaction takes place within 0.5 seconds [RFC5826].
A.2. Use case of DECT-ULE: Smart Home
DECT is a technology widely used for wireless telephone
communications in residential scenarios. Since DECT-ULE is a low-
power variant of DECT, DECT-ULE can be used to connect constrained
devices such as sensors and actuators to a Fixed Part, a device that
typically acts as a base station for wireless telephones. Therefore,
DECT-ULE is specially suitable for the connected home space in
application areas such as home automation, smart metering, safety,
healthcare, etc.
Example: Use of DECT-ULE for Smart Metering
The smart electricity meter of a home is equipped with a DECT-ULE
transceiver. This device is in the coverage range of the Fixed Part
of the home. The Fixed Part can act as a router connected to the
Internet. This way, the smart meter can transmit electricity
consumption readings through the DECT-ULE link with the Fixed Part,
and the latter can forward such readings to the utility company using
Wide Area Network (WAN) links. The meter can also receive queries
from the utility company or from an advanced energy control system
controlled by the user, which may also be connected to the Fixed Part
via DECT-ULE.
A.3. Use case of MS/TP: Building Automation Networks
The primary use case for IPv6 over MS/TP (6LoBAC) is in building
automation networks. [BACnet] is the open international standard
protocol for building automation, and MS/TP is defined in [BACnet]
Clause 9. MS/TP was designed to be a low cost multi-drop field bus
to inter-connect the most numerous elements (sensors and actuators)
of a building automation network to their controllers. A key aspect
of 6LoBAC is that it is designed to co-exist with BACnet MS/TP on the
same link, easing the ultimate transition of some BACnet networks to
native end-to-end IPv6 transport protocols. New applications for
6LoBAC may be found in other domains where low cost, long distance,
and low latency are required.
Example: Use of 6LoBAC in Building Automation Networks
The majority of installations for MS/TP are for "terminal" or
"unitary" controllers, i.e. single zone or room controllers that may
connect to HVAC or other controls such as lighting or blinds. The
economics of daisy-chaining a single twisted-pair between multiple
devices is often preferred over home-run Cat-5 style wiring.
A multi-zone controller might be implemented as an IP router between
a traditional Ethernet link and several 6LoBAC links, fanning out to
multiple terminal controllers.
The superior distance capabilities of MS/TP (~1 km) compared to other
6lo media may suggest its use in applications to connect remote
devices to the nearest building infrastructure. for example, remote
pumping or measuring stations with moderate bandwidth requirements
can benefit from the low cost and robust capabilities of MS/TP over
other wired technologies such as DSL, and without the line-of-site
restrictions or hop-by-hop latency of many low cost wireless
solutions.
A.4. Use case of NFC: Alternative Secure Transfer
According to applications, various secured data can be handled and
transferred. Depending on security level of the data, methods for
transfer can be alternatively selected.
Example: Use of NFC for Secure Transfer in Healthcare Services with Appendix A. Design Space Dimensions for 6lo Deployment
Tele-Assistance
A senior citizen who lives alone wears one to several wearable 6lo The [RFC6568] lists the dimensions used to describe the design space
devices to measure heartbeat, pulse rate, etc. The 6lo devices are of wireless sensor networks in the context of the 6LoWPAN working
densely installed at home for movement detection. An LoWPAN Border group. The design space is already limited by the unique
Router (LBR) at home will send the sensed information to a connected characteristics of a LoWPAN (e.g. low power, short range, low bit
healthcare center. Portable base stations with LCDs may be used to rate). In [RFC6568], the following design space dimensions are
check the data at home, as well. Data is gathered in both periodic described: Deployment, Network size, Power source, Connectivity,
and event-driven fashion. In this application, event-driven data can Multi-hop communication, Traffic pattern, Mobility, Quality of
be very time-critical. In addition, privacy also becomes a serious Service (QoS). However, in this document, the following design space
issue in this case, as the sensed data is very personal. dimensions are considered:
While the senior citizen is provided audio and video healthcare o Deployment/Bootstrapping: 6lo nodes can be connected randomly, or
services by a tele-assistance based on LTE connections, the senior in an organized manner. The bootstrapping has different
citizen can alternatively use NFC connections to transfer the characteristics for each link layer technology.
personal sensed data to the tele-assistance. At this moment, hidden
hackers can overhear the data based on the LTE connection, but they
cannot gather the personal data over the NFC connection.
A.5. Use case of PLC: Smart Grid o Topology: Topology of 6lo networks may inherently follow the
characteristics of each link layer technology. Point-to-point,
star, tree or mesh topologies can be configured, depending on the
link layer technology considered.
Smart grid concept is based on numerous operational and energy o L2-Mesh or L3-Mesh: L2-mesh and L3-mesh may inherently follow the
measuring sub-systems of an electric grid. It comprises of multiple characteristics of each link layer technology. Some link layer
administrative levels/segments to provide connectivity among these technologies may support L2-mesh and some may not support.
numerous components. Last mile connectivity is established over LV
segment, whereas connectivity over electricity distribution takes
place in HV segment.
Although other wired and wireless technologies are also used in Smart o Multi-link subnet, single subnet: The selection of multi-link
Grid (Advance Metering Infrastructure - AMI, Demand Response - DR, subnet and single subnet depends on connectivity and the number of
Home Energy Management System - HEMS, Wide Area Situational Awareness 6lo nodes.
- WASA etc), PLC enjoys the advantage of existing (power conductor)
medium and better reliable data communication. PLC is a promising
wired communication technology in that the electrical power lines are
already there and the deployment cost can be comparable to wireless
technologies. The 6lo related scenarios lie in the low voltage PLC
networks with most applications in the area of Advanced Metering
Infrastructure, Vehicle-to-Grid communications, in-home energy
management and smart street lighting.
Example: Use of PLC for Advanced Metering Infrastructure o Data rate: Typically, the link layer technologies of 6lo have low
rate of data transmission. But, by adjusting the MTU, it can
deliver higher upper layer data rate.
Household electricity meters transmit time-based data of electric o Buffering requirements: Some 6lo use case may require more data
power consumption through PLC. Data concentrators receive all the rate than the link layer technology support. In this case, a
meter data in their corresponding living districts and send them to buffering mechanism to manage the data is required.
the Meter Data Management System (MDMS) through WAN network (e.g.
Medium-Voltage PLC, Ethernet or GPRS) for storage and analysis. Two-
way communications are enabled which means smart meters can do
actions like notification of electricity charges according to the
commands from the utility company.
With the existing power line infrastructure as communication medium, o Security and Privacy Requirements: Some 6lo use case can involve
cost on building up the PLC network is naturally saved, and more transferring some important and personal data between 6lo nodes.
importantly, labor operational costs can be minimized from a long- In this case, high-level security support is required.
term perspective. Furthermore, this AMI application speeds up
electricity charge, reduces losses by restraining power theft and
helps to manage the health of the grid based on line loss analysis.
Example: Use of PLC (IEEE1901.1) for WASA in Smart Grid o Mobility across 6lo networks and subnets: The movement of 6lo
nodes depends on the 6lo use case. If the 6lo nodes can move or
moved around, a mobility management mechanism is required.
Many sub-systems of Smart Grid require low data rate and narrowband o Time synchronization requirements: The requirement of time
variant (IEEE1901.2) of PLC fulfils such requirements. Recently, synchronization of the upper layer service is dependent on the 6lo
more complex scenarios are emerging that require higher data rates. use case. For some 6lo use case related to health service, the
measured data must be recorded with exact time and must be
transferred with time synchronization.
WASA sub-system is an appropriate example that collects large amount o Reliability and QoS: Some 6lo use case requires high reliability,
of information about the current state of the grid over wide area for example real-time service or health-related services.
from electric substations as well as power transmission lines. The
collected feedback is used for monitoring, controlling and protecting
all the sub-systems.
A.6. Use case of IEEE 802.15.4e: Industrial Automation o Traffic patterns: 6lo use cases may involve various traffic
patterns. For example, some 6lo use case may require short data
length and random transmission. Some 6lo use case may require
continuous data and periodic data transmission.
Typical scenario of Industrial Automation where sensor and actuators o Security Bootstrapping: Without the external operations, 6lo nodes
are connected through the time-slotted radio access (IEEE 802.15.4e). must have the security bootstrapping mechanism.
For that, there will be a point-to-point control signal exchange in
between sensors and actuators to trigger the critical control
information. In such scenarios, point-to-point traffic flows are
significant to exchange the controlled information in between sensors
and actuators within the constrained networks.
Example: Use of IEEE 802.15.4e for P2P communication in closed-loop o Power use strategy: to enable certain use cases, there may be
application requirements on the class of energy availability and the strategy
followed for using power for communication [RFC7228]. Each link
layer technology defines a particular power use strategy which may
be tuned [RFC8352]. Readers are expected to be familiar with
[RFC7228] terminology.
AODV-RPL [I-D.ietf-roll-aodv-rpl] is proposed as a standard P2P o Update firmware requirements: Most 6lo use cases will need a
routing protocol to provide the hop-by-hop data transmission in mechanism for updating firmware. In these cases support for over
closed-loop constrained networks. Scheduling Functions i.e. SF0 the air updates are required, probably in a broadcast mode when
[I-D.ietf-6tisch-6top-sfx] and SF1 [I-D.satish-6tisch-6top-sf1] is bandwith is low and the number of identical devices is high.
proposed to provide distributed neighbor-to-neighbor and end-to-end
resource reservations, respectively for traffic flows in
deterministic networks (6TiSCH).
The potential scenarios that can make use of the end-to-end resource o Wired vs. Wireless: Plenty of 6lo link layer technologies are
reservations can be in health-care and industrial applications. wireless, except MS/TP and PLC. The selection of wired or
AODV-RPL and SF0/SF1 are the significant routing and resource wireless link layer technology is mainly dependent on the
reservation protocols for closed-loop applications in constrained requirement of 6lo use cases and the characteristics of wired/
networks. wireless technologies. For example, some 6lo use cases may
require easy and quick deployment, whereas others may need a
continuous source of power.
Authors' Addresses Authors' Addresses
Yong-Geun Hong Yong-Geun Hong
ETRI ETRI
161 Gajeong-Dong Yuseung-Gu 161 Gajeong-Dong Yuseung-Gu
Daejeon 305-700 Daejeon 305-700
Korea Korea
Phone: +82 42 860 6557 Phone: +82 42 860 6557
Email: yghong@etri.re.kr Email: yghong@etri.re.kr
Carles Gomez Carles Gomez
 End of changes. 50 change blocks. 
575 lines changed or deleted 334 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/