< draft-ietf-6lo-use-cases-02.txt		draft-ietf-6lo-use-cases-03.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: January 4, 2018 UPC/i2cat		Expires: May 3, 2018 UPC/i2cat
	Y-H. Choi		Y-H. Choi
	ETRI		ETRI
	D-Y. Ko		D-Y. Ko
	SKtelecom		SKtelecom
	AR. Sangi		AR. Sangi
	Individual Contributor		Huaiyin Institute of Technology
	T. Aanstoot		T. Aanstoot
	Modio AB		Modio AB
	S. Chakrabarti		S. Chakrabarti
	July 3, 2017		October 30, 2017
	IPv6 over Constrained Node Networks (6lo) Applicability & Use cases		IPv6 over Constrained Node Networks (6lo) Applicability & Use cases
	draft-ietf-6lo-use-cases-02		draft-ietf-6lo-use-cases-03
	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),		ITU-T G.9959 (Z-Wave), BLE, DECT-ULE, MS/TP, NFC, PLC (IEEE 1901.2),
	and IEEE 802.15.4e (6tisch) are used as examples. The document		and IEEE 802.15.4e (6tisch) are used as examples. The document
	targets an audience who like to understand and evaluate running end-		targets an audience who like to understand and evaluate running end-
	to-end IPv6 over the constrained link layer networks connecting		to-end IPv6 over the constrained link layer networks connecting
	devices to each other or to each cloud.		devices to each other or to each cloud.
	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 http://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 January 4, 2018.		This Internet-Draft will expire on May 3, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(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
	skipping to change at page 2, line 41 ¶		skipping to change at page 2, line 41 ¶
	3.7. IEEE 802.15.4e (specified) . . . . . . . . . . . . . . . 7		3.7. IEEE 802.15.4e (specified) . . . . . . . . . . . . . . . 7
	3.8. LTE MTC (example of a potential candidate) . . . . . . . 8		3.8. LTE MTC (example of a potential candidate) . . . . . . . 8
	3.9. Comparison between 6lo Link layer technologies . . . . . 8		3.9. Comparison between 6lo Link layer technologies . . . . . 8
	4. 6lo Deployment Scenarios . . . . . . . . . . . . . . . . . . 9		4. 6lo Deployment Scenarios . . . . . . . . . . . . . . . . . . 9
	4.1. jupitermesh in Smart Grid using 6lo in network layer . . 9		4.1. jupitermesh in Smart Grid using 6lo in network layer . . 9
	4.2. Wi-SUN usage of 6lo stacks . . . . . . . . . . . . . . . 11		4.2. Wi-SUN usage of 6lo stacks . . . . . . . . . . . . . . . 11
	5. Design Space and Guidelines for 6lo Deployment . . . . . . . 12		5. Design Space and Guidelines for 6lo Deployment . . . . . . . 12
	5.1. Design Space Dimensions for 6lo Deployment . . . . . . . 12		5.1. Design Space Dimensions for 6lo Deployment . . . . . . . 12
	5.2. Guidelines for adopting IPv6 stack (6lo/6LoWPAN) . . . . 14		5.2. Guidelines for adopting IPv6 stack (6lo/6LoWPAN) . . . . 14
	6. 6lo Use Case Examples . . . . . . . . . . . . . . . . . . . . 16		6. 6lo Use Case Examples . . . . . . . . . . . . . . . . . . . . 16
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 17		8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
	10.1. Normative References . . . . . . . . . . . . . . . . . . 17		10.1. Normative References . . . . . . . . . . . . . . . . . . 17
	10.2. Informative References . . . . . . . . . . . . . . . . . 19		10.2. Informative References . . . . . . . . . . . . . . . . . 19
	Appendix A. Other 6lo Use Case Examples . . . . . . . . . . . . 21		Appendix A. Other 6lo Use Case Examples . . . . . . . . . . . . 21
	A.1. Use case of ITU-T G.9959: Smart Home . . . . . . . . . . 21		A.1. Use case of ITU-T G.9959: Smart Home . . . . . . . . . . 21
	A.2. Use case of DECT-ULE: Smart Home . . . . . . . . . . . . 22		A.2. Use case of DECT-ULE: Smart Home . . . . . . . . . . . . 22
	A.3. Use case of MS/TP: Management of District Heating . . . . 22		A.3. Use case of MS/TP: Management of District Heating . . . . 22
	A.4. Use case of NFC: Alternative Secure Transfer . . . . . . 23		A.4. Use case of NFC: Alternative Secure Transfer . . . . . . 23
	A.5. Use case of PLC: Smart Grid . . . . . . . . . . . . . . . 23		A.5. Use case of PLC: Smart Grid . . . . . . . . . . . . . . . 24
	A.6. Use case of IEEE 802.15.4e: Industrial Automation . . . . 24		A.6. Use case of IEEE 802.15.4e: Industrial Automation . . . . 25
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
	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
	skipping to change at page 5, line 47 ¶		skipping to change at page 5, line 47 ¶
	for smart metering in a home.		for smart metering in a home.
	3.4. MS/TP (specified)		3.4. MS/TP (specified)
	MS/TP is a contention-free access method for the RS-485 physical		MS/TP is a contention-free access method for the RS-485 physical
	layer, which is used extensively in building automation networks.		layer, which is used extensively 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. Together with low data rates		limited processing power and memory. Together with low data rates
	and a small address space, these constraints are similar to those		and a small address space, these constraints are similar to those
	faced in 6lowpan networks and suggest some elements of that solution		faced in 6LoWPAN networks and suggest some elements of that solution
	might be leveraged. MS/TP differs significantly from 6lowpan in at		might be leveraged. MS/TP differs significantly from 6LoWPAN in at
	least three aspects: a) MS/TP devices typically have a continuous		least three aspects: a) MS/TP devices typically have a continuous
	source of power, b) all MS/TP devices on a segment can communicate		source of power, b) all MS/TP devices on a segment can communicate
	directly so there are no hidden node or mesh routing issues, and c)		directly so there are no hidden node or mesh routing issues, and c)
	recent changes to MS/TP provide support for large payloads,		recent changes to MS/TP provide support for large payloads,
	eliminating the need for link-layer fragmentation and reassembly.		eliminating the need for link-layer fragmentation and reassembly.
	MS/TP is designed to enable multidrop networks over shielded twisted		MS/TP is designed to enable multidrop networks over shielded twisted
	pair wiring, although not according to standards, in lower speeds,		pair wiring, although not according to standards, in lower speeds,
	normally 9600 bit/s, re-purposed telecom wiring is widely in use,		normally 9600 bit/s, re-purposed telecom wiring is widely in use,
	keeping deployment cost down. It can support a data rate of 115,200		keeping deployment cost down. It can support a data rate of 115,200
	skipping to change at page 9, line 12 ¶		skipping to change at page 9, line 12 ¶
	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 | TSCH |
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| | Home |Interact| | | Health-| |Industr-|		| | Home |Interact| | | Health-| |Industr-|
	| Usage | Auto- |w/ Smart| Meter |District| care | Smart |ial Aut-|		| Usage | Auto- |w/ Smart| Meter |District| care | Smart |ial Aut-|
	| | mation | Phone | Reading| Heating| Service| Grid | mation |		| | mation | Phone | Reading| Heating| Service| Grid | mation |
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| Topology | L2-mesh| Star | Star | Bus | P2P | Tree | |		| Topology | L2-mesh| Star | Star | Bus | P2P | Star | |
	| & | or | | | | | | Mesh |		| & | or | | | | | Tree | Mesh |
	| Subnet | L3-mesh| No mesh| No mesh| MS/TP | L2-mesh| No mesh| |		| Subnet | L3-mesh| No mesh| No mesh| MS/TP | L2-mesh| Mesh | |
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| | | | | | | | |		| | | | | | | | |
	| Mobility | No | Low | No | No |Moderate| No | No |		| Mobility | No | Low | No | No |Moderate| No | No |
	| Reqmt | | | | | | | |		| Reqmt | | | | | | | |
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| | High + | | High + | High + | | igh + | High + |		| | High + | | High + | High + | | High + | High + |
	| Security | Privacy| Parti- | Privacy| Authen.| High |Encrypt.| Privacy|		| Security | Privacy| Parti- | Privacy| Authen.| High |Encrypt.| Privacy|
	| Reqmt |required| ally |required|required| |required|required|		| Reqmt |required| ally |required|required| |required|required|
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| | | | | | | | |		| | | | | | | | |
	| Buffering | Low | Low | Low | Low | Low | Low | Low |		| Buffering | Low | Low | Low | Low | Low | Low | Low |
	| Reqmpt | | | | | | | |		| Reqmpt | | | | | | | |
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| Latency, | | | | | | | |		| Latency, | | | | | | | |
	| QoS | High | Low | Low | High | High | Low | High |		| QoS | High | Low | Low | High | High | Low | High |
	| Reqmt | | | | | | | |		| Reqmt | | | | | | | |
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| | | | | | | | |		| | | | | | | | |
	| Data |Infrequ-|Infrequ-|Infrequ-|Frequent| Small |Infrequ-|Infrequ-|		| Data |Infrequ-|Infrequ-|Infrequ-|Frequent| Small |Infrequ-|Infrequ-|
	| Rate | ent | ent | ent | | | ent | ent |		| Rate | ent | ent | ent | | | ent | ent |
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| RFC # | | | | | | | |		| RFC # | | | | | draft- | draft- | |
	| or | RFC7428| RFC7668| RFC8105| RFC8163| 6lo-nfc|hou-6lo-| RFC7554|		| or | RFC7428| RFC7668| RFC8105| RFC8163|ietf-6lo|hou-6lo-| RFC7554|
	| Draft | | | | | | 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. jupitermesh in Smart Grid using 6lo in network layer
	jupiterMesh is a multi-hop wireless mesh network specification		jupiterMesh is a multi-hop wireless mesh network specification
	designed mainly for deployment in large geographical areas. Each		designed mainly for deployment in large geographical areas. Each
	skipping to change at page 10, line 44 ¶		skipping to change at page 10, line 44 ¶
	802.15.4-2015], supporting multiple operating modes for deployment		802.15.4-2015], supporting multiple operating modes for deployment
	in different regulatory domains and deployment scenarios in terms		in different regulatory domains and deployment scenarios in terms
	of density and bandwidth requirements. jupiterMesh supports bit		of density and bandwidth requirements. jupiterMesh supports bit
	rates from 50 kbps to 800 kbps, frame size up to 2048 bytes, up to		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		11 different RF bands and 3 modulation types (i.e., FSK, OQPSK and
	OFDM).		OFDM).
	o The MAC layer is based on IEEE 802.15.4 TSCH specification [IEEE		o The MAC layer is based on IEEE 802.15.4 TSCH specification [IEEE
	802.15.4-2015]. With frequency hopping capability, TSCH MAC		802.15.4-2015]. With frequency hopping capability, TSCH MAC
	supports scheduling of dedicated timeslot enabling bandwidth		supports scheduling of dedicated timeslot enabling bandwidth
	management and QOS.		management and QoS.
	o The security layer consists of a certificate-based (i.e. X.509)		o The security layer consists of a certificate-based (i.e. X.509)
	network access authentication using EAP-TLS, with IEEE		network access authentication using EAP-TLS, with IEEE
	802.15.9-based KMP (Key Management Protocol) transport, and PANA		802.15.9-based KMP (Key Management Protocol) transport, and PANA
	and link layer encryption using AES-128 CCM as specified in IEEE		and link layer encryption using AES-128 CCM as specified in IEEE
	802.15.4-2015 [IEEE 802.15.4-2015].		802.15.4-2015 [IEEE 802.15.4-2015].
	o Address assignment and network configuration are specified using		o Address assignment and network configuration are specified using
	DHCPv6 [RFC3315]. Neighbor Discovery (ND) [RFC6775] and stateless		DHCPv6 [RFC3315]. Neighbor Discovery (ND) [RFC6775] and stateless
	address auto-configuration (SLAAC) are not supported.		address auto-configuration (SLAAC) are not supported.
	o The network layer consists of IPv6, ICPMv6 and 6lo/6LoPWAN header		o The network layer consists of IPv6, ICMPv6 and 6lo/6LoPWAN header
	compression [RFC6282]. Multicast is supported using MPL. Two		compression [RFC6282]. Multicast is supported using MPL. Two
	domains are supported, a delay sensitive MPL domain for low		domains are supported, a delay sensitive MPL domain for low
	latency applications (e.g. DSM, DSR) and a delay insensitive one		latency applications (e.g. DSM, DSR) and a delay insensitive one
	for less stringent applications (e.g. OTA file transfers).		for less stringent applications (e.g. OTA file transfers).
	o The routing layer uses RPL [RFC6550] in non-storing mode with the		o The routing layer uses RPL [RFC6550] in non-storing mode with the
	MRHOF objective function based on the ETX metric.		MRHOF objective function based on the ETX metric.
	4.2. Wi-SUN usage of 6lo stacks		4.2. Wi-SUN usage of 6lo stacks
	skipping to change at page 11, line 31 ¶		skipping to change at page 11, line 31 ¶
	the IEEE 802.15.4g standard. Wi-SUN networks support star and mesh		the IEEE 802.15.4g standard. Wi-SUN networks support star and mesh
	topologies, as well as hybrid star/mesh deployments, but are		topologies, as well as hybrid star/mesh deployments, but are
	typically laid out in a mesh topology where each node relays data for		typically laid out in a mesh topology where each node relays data for
	the network to provide network connectivity. Wi-SUN networks are		the network to provide network connectivity. Wi-SUN networks are
	deployed on both powered and battery-operated devices.		deployed on both powered and battery-operated devices.
	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		o Advanced Metering Infrastructure (AMI)
	o Infrastructure (AMI)
	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 etc)		o Structural health (bridges, buildings etc)
	o Monitoring and Asset Management		o Monitoring and Asset Management
	o Smart Thermostats, Air Conditioning and Heat Controls		o Smart Thermostats, Air Conditioning and Heat Controls
	o Energy Usage Information Displays
			o Energy Usage Information Displays
	The Wi-SUN Alliance Field Area Network (FAN) covers primarily outdoor		The Wi-SUN Alliance Field Area Network (FAN) covers primarily outdoor
	networks, and its specification is oriented towards meeting the more		networks, and its specification is oriented towards meeting the more
	rigorous challenges of these environments. Examples include from		rigorous challenges of these environments. Examples include from
	meter to outdoor access point/router for AMI and DR, or between		meter to outdoor access point/router for AMI and DR, or between
	switches for DA. However, nothing in the profile restricts it to		switches for DA. However, nothing in the profile restricts it to
	outdoor use. It has the following features;		outdoor use. It has the following features;
	o Open standards based on IEEE802, IETF, TIA, ETSI		o Open standards based on IEEE802, IETF, TIA, ETSI
	o Architecture is an IPv6 frequency hopping wireless mesh network		o Architecture is an IPv6 frequency hopping wireless mesh network
	skipping to change at page 12, line 46 ¶		skipping to change at page 12, line 44 ¶
	forwarding is utilized.		forwarding is utilized.
	5. Design Space and Guidelines for 6lo Deployment		5. Design Space and Guidelines for 6lo Deployment
	5.1. Design Space Dimensions for 6lo Deployment		5.1. 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
	of wireless sensor networks in the context of the 6LoWPAN working		of wireless sensor networks in the context of the 6LoWPAN working
	group. The design space is already limited by the unique		group. The design space is already limited by the unique
	characteristics of a LoWPAN (e.g., low power, short range, low bit		characteristics of a LoWPAN (e.g., low power, short range, low bit
	rate). In [RFC6568], the following design space dimensions are		rate). In [RFC6568], design space dimensions are described;
	described; Deployment, Network size, Power source, Connectivity,		Deployment, Network size, Power source, Connectivity, Multi-hop
	Multi-hop communication, Traffic pattern, Mobility, Quality of		communication, Traffic pattern, Mobility, Quality of Service (QoS).
	Service (QoS). However, in this document, the following design space		However, in this document, the following design space dimensions are
	dimensions are considered:		considered:
	o Deployment/Bootstrapping: 6lo nodes can be connected randomly, or		o Deployment/Bootstrapping: 6lo nodes can be connected randomly, or
	in an organized manner. The bootstrapping has different		in an organized manner. The bootstrapping has different
	characteristics for each link layer technology.		characteristics for each link layer technology.
	o Topology: Topology of 6lo networks may inherently follow the		o Topology: Topology of 6lo networks may inherently follow the
	characteristics of each link layer technology. Point-to-point,		characteristics of each link layer technology. Point-to-point,
	star, tree or mesh topologies can be configured, depending on the		star, tree or mesh topologies can be configured, depending on the
	link layer technology considered.		link layer technology considered.
	skipping to change at page 14, line 20 ¶		skipping to change at page 14, line 20 ¶
	followed for using power for communication [RFC7228]. Each link		followed for using power for communication [RFC7228]. Each link
	layer technology defines a particular power use strategy which may		layer technology defines a particular power use strategy which may
	be tuned [I-D.ietf-lwig-energy-efficient]. Readers are expected		be tuned [I-D.ietf-lwig-energy-efficient]. Readers are expected
	to be familiar with [RFC7228] terminology.		to be familiar with [RFC7228] terminology.
	o Update firmware requirements: Most 6lo use cases will need a		o Update firmware requirements: Most 6lo use cases will need a
	mechanism for updating firmware. In these cases support for over		mechanism for updating firmware. In these cases support for over
	the air updates are required, probably in a broadcast mode when		the air updates are required, probably in a broadcast mode when
	bandwith is low and the number of identical devices is high.		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 and some 6lo use cases may require continuous
			source of power.
	5.2. Guidelines for adopting IPv6 stack (6lo/6LoWPAN)		5.2. Guidelines for adopting IPv6 stack (6lo/6LoWPAN)
	The following guideline targets candidates for new constrained L2		The following guideline targets candidates for new constrained L2
	technologies that consider running modified 6LoWPAN stack. The		technologies that consider running modified 6LoWPAN stack. The
	modification of 6LoWPAN stack should be based on the following:		modification of 6LoWPAN stack should be based on 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 33 ¶		skipping to change at page 17, line 37 ¶
	jupiterMesh and Paul Duffy has provided valuable information of Wi-		jupiterMesh and Paul Duffy has provided valuable information of Wi-
	SUN for this draft.		SUN for this draft.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC4919] Kushalnagar, N., Montenegro, G., and C. Schumacher, "IPv6		[RFC4919] Kushalnagar, N., Montenegro, G., and C. Schumacher, "IPv6
	over Low-Power Wireless Personal Area Networks (6LoWPANs):		over Low-Power Wireless Personal Area Networks (6LoWPANs):
	Overview, Assumptions, Problem Statement, and Goals",		Overview, Assumptions, Problem Statement, and Goals",
	RFC 4919, DOI 10.17487/RFC4919, August 2007,		RFC 4919, DOI 10.17487/RFC4919, August 2007,
	<http://www.rfc-editor.org/info/rfc4919>.		<https://www.rfc-editor.org/info/rfc4919>.
	[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,		[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
	"Transmission of IPv6 Packets over IEEE 802.15.4		"Transmission of IPv6 Packets over IEEE 802.15.4
	Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007,		Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007,
	<http://www.rfc-editor.org/info/rfc4944>.		<https://www.rfc-editor.org/info/rfc4944>.
	[RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation		[RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation
	Routing Requirements in Low-Power and Lossy Networks",		Routing Requirements in Low-Power and Lossy Networks",
	RFC 5826, DOI 10.17487/RFC5826, April 2010,		RFC 5826, DOI 10.17487/RFC5826, April 2010,
	<http://www.rfc-editor.org/info/rfc5826>.		<https://www.rfc-editor.org/info/rfc5826>.
	[RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6		[RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6
	Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,		Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
	DOI 10.17487/RFC6282, September 2011,		DOI 10.17487/RFC6282, September 2011,
	<http://www.rfc-editor.org/info/rfc6282>.		<https://www.rfc-editor.org/info/rfc6282>.
	[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,		[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
	Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,		Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,
	JP., and R. Alexander, "RPL: IPv6 Routing Protocol for		JP., and R. Alexander, "RPL: IPv6 Routing Protocol for
	Low-Power and Lossy Networks", RFC 6550,		Low-Power and Lossy Networks", RFC 6550,
	DOI 10.17487/RFC6550, March 2012,		DOI 10.17487/RFC6550, March 2012,
	<http://www.rfc-editor.org/info/rfc6550>.		<https://www.rfc-editor.org/info/rfc6550>.
	[RFC6568] Kim, E., Kaspar, D., and JP. Vasseur, "Design and		[RFC6568] Kim, E., Kaspar, D., and JP. Vasseur, "Design and
	Application Spaces for IPv6 over Low-Power Wireless		Application Spaces for IPv6 over Low-Power Wireless
	Personal Area Networks (6LoWPANs)", RFC 6568,		Personal Area Networks (6LoWPANs)", RFC 6568,
	DOI 10.17487/RFC6568, April 2012,		DOI 10.17487/RFC6568, April 2012,
	<http://www.rfc-editor.org/info/rfc6568>.		<https://www.rfc-editor.org/info/rfc6568>.
	[RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.		[RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
	Bormann, "Neighbor Discovery Optimization for IPv6 over		Bormann, "Neighbor Discovery Optimization for IPv6 over
	Low-Power Wireless Personal Area Networks (6LoWPANs)",		Low-Power Wireless Personal Area Networks (6LoWPANs)",
	RFC 6775, DOI 10.17487/RFC6775, November 2012,		RFC 6775, DOI 10.17487/RFC6775, November 2012,
	<http://www.rfc-editor.org/info/rfc6775>.		<https://www.rfc-editor.org/info/rfc6775>.
	[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for		[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for
	Constrained-Node Networks", RFC 7228,		Constrained-Node Networks", RFC 7228,
	DOI 10.17487/RFC7228, May 2014,		DOI 10.17487/RFC7228, May 2014,
	<http://www.rfc-editor.org/info/rfc7228>.		<https://www.rfc-editor.org/info/rfc7228>.
	[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, <http://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,
	<http://www.rfc-editor.org/info/rfc7428>.		<https://www.rfc-editor.org/info/rfc7428>.
	[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using		[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using
	IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the		IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the
	Internet of Things (IoT): Problem Statement", RFC 7554,		Internet of Things (IoT): Problem Statement", RFC 7554,
	DOI 10.17487/RFC7554, May 2015,		DOI 10.17487/RFC7554, May 2015,
	<http://www.rfc-editor.org/info/rfc7554>.		<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,
	<http://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,
	<http://www.rfc-editor.org/info/rfc8036>.		<https://www.rfc-editor.org/info/rfc8036>.
	[RFC8065] Thaler, D., "Privacy Considerations for IPv6 Adaptation-		[RFC8065] Thaler, D., "Privacy Considerations for IPv6 Adaptation-
	Layer Mechanisms", RFC 8065, DOI 10.17487/RFC8065,		Layer Mechanisms", RFC 8065, DOI 10.17487/RFC8065,
	February 2017, <http://www.rfc-editor.org/info/rfc8065>.		February 2017, <https://www.rfc-editor.org/info/rfc8065>.
	[RFC8066] Chakrabarti, S., Montenegro, G., Droms, R., and J.		[RFC8066] Chakrabarti, S., Montenegro, G., Droms, R., and J.
	Woodyatt, "IPv6 over Low-Power Wireless Personal Area		Woodyatt, "IPv6 over Low-Power Wireless Personal Area
	Network (6LoWPAN) ESC Dispatch Code Points and		Network (6LoWPAN) ESC Dispatch Code Points and
	Guidelines", RFC 8066, DOI 10.17487/RFC8066, February		Guidelines", RFC 8066, DOI 10.17487/RFC8066, February
	2017, <http://www.rfc-editor.org/info/rfc8066>.		2017, <https://www.rfc-editor.org/info/rfc8066>.
	[RFC8105] Mariager, P., Petersen, J., Ed., Shelby, Z., Van de Logt,		[RFC8105] Mariager, P., Petersen, J., Ed., Shelby, Z., Van de Logt,
	M., and D. Barthel, "Transmission of IPv6 Packets over		M., and D. Barthel, "Transmission of IPv6 Packets over
	Digital Enhanced Cordless Telecommunications (DECT) Ultra		Digital Enhanced Cordless Telecommunications (DECT) Ultra
	Low Energy (ULE)", RFC 8105, DOI 10.17487/RFC8105, May		Low Energy (ULE)", RFC 8105, DOI 10.17487/RFC8105, May
	2017, <http://www.rfc-editor.org/info/rfc8105>.		2017, <https://www.rfc-editor.org/info/rfc8105>.
	[RFC8163] Lynn, K., Ed., Martocci, J., Neilson, C., and S.		[RFC8163] Lynn, K., Ed., Martocci, J., Neilson, C., and S.
	Donaldson, "Transmission of IPv6 over Master-Slave/Token-		Donaldson, "Transmission of IPv6 over Master-Slave/Token-
	Passing (MS/TP) Networks", RFC 8163, DOI 10.17487/RFC8163,		Passing (MS/TP) Networks", RFC 8163, DOI 10.17487/RFC8163,
	May 2017, <http://www.rfc-editor.org/info/rfc8163>.		May 2017, <https://www.rfc-editor.org/info/rfc8163>.
	10.2. Informative References		10.2. Informative References
	[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,		[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
	C., and M. Carney, "Dynamic Host Configuration Protocol		C., and M. Carney, "Dynamic Host Configuration Protocol
	for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July		for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
	2003, <http://www.rfc-editor.org/info/rfc3315>.		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,
	<http://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-07 (work in progress),		Communication", draft-ietf-6lo-nfc-07 (work in progress),
	June 2017.		June 2017.
	[I-D.ietf-lwig-energy-efficient]		[I-D.ietf-lwig-energy-efficient]
	Gomez, C., Kovatsch, M., Tian, H., and Z. Cao, "Energy-		Gomez, C., Kovatsch, M., Tian, H., and Z. Cao, "Energy-
	Efficient Features of Internet of Things Protocols",		Efficient Features of Internet of Things Protocols",
	draft-ietf-lwig-energy-efficient-07 (work in progress),		draft-ietf-lwig-energy-efficient-08 (work in progress),
	March 2017.		October 2017.
	[I-D.ietf-roll-aodv-rpl]		[I-D.ietf-roll-aodv-rpl]
	Anamalamudi, S., Zhang, M., Sangi, A., Perkins, C., and S.		Anamalamudi, S., Zhang, M., Sangi, A., Perkins, C., and S.
	Anand, "Asymmetric AODV-P2P-RPL in Low-Power and Lossy		Anand, "Asymmetric AODV-P2P-RPL in Low-Power and Lossy
	Networks (LLNs)", draft-ietf-roll-aodv-rpl-01 (work in		Networks (LLNs)", draft-ietf-roll-aodv-rpl-02 (work in
	progress), March 2017.		progress), September 2017.
	[I-D.ietf-6tisch-6top-sf0]		[I-D.ietf-6tisch-6top-sf0]
	Dujovne, D., Grieco, L., Palattella, M., and N. Accettura,		Dujovne, D., Grieco, L., Palattella, M., and N. Accettura,
	"6TiSCH 6top Scheduling Function Zero (SF0)", draft-ietf-		"6TiSCH 6top Scheduling Function Zero (SF0)", draft-ietf-
	6tisch-6top-sf0-04 (work in progress), April 2017.		6tisch-6top-sf0-05 (work in progress), July 2017.
	[I-D.satish-6tisch-6top-sf1]		[I-D.satish-6tisch-6top-sf1]
	Anamalamudi, S., Zhang, M., Sangi, A., Perkins, C., and S.		Anamalamudi, S., Zhang, M., Sangi, A., Perkins, C., and S.
	Anand, "Scheduling Function One (SF1) for hop-by-hop		Anand, "Scheduling Function One (SF1) for hop-by-hop
	Scheduling in 6tisch Networks", draft-satish-6tisch-6top-		Scheduling in 6tisch Networks", draft-satish-6tisch-6top-
	sf1-03 (work in progress), February 2017.		sf1-03 (work in progress), February 2017.
			[I-D.hou-6lo-plc]
			Hou, J., Hong, Y., and X. Tang, "Transmission of IPv6
			Packets over PLC Networks", draft-hou-6lo-plc-01 (work in
			progress), June 2017.
	[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/>.
	[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.
	skipping to change at page 25, line 34 ¶		skipping to change at page 26, line 4 ¶
	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
	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 305-700		Daejeon 305-700
	Korea		Korea
	Phone: +82 42 860 1429		Phone: +82 42 860 1429
	Email: yhc@etri.re.kr		Email: yhc@etri.re.kr
	Deoknyong Ko		Deoknyong Ko
	SKtelecom		SKtelecom
	9-1 Byundang-gu Sunae-dong, Seongnam-si		9-1 Byundang-gu Sunae-dong, Seongnam-si
	Gyeonggi-do 13595		Gyeonggi-do 13595
	Korea		Korea
	Phone: +82 10 3356 8052		Phone: +82 10 3356 8052
	Email: engineer@sk.com		Email: engineer@sk.com
	Abdur Rashid Sangi		Abdur Rashid Sangi
	Individual Contributor		Huaiyin Institute of Technology
			No.89 North Beijing Road, Qinghe District
			Huaian 223001
			P.R. China
	Email: sangi_bahrian@yahoo.com		Email: sangi_bahrian@yahoo.com
	Take Aanstoot		Take Aanstoot
	Modio AB		Modio AB
	S:t Larsgatan 15, 582 24		S:t Larsgatan 15, 582 24
	Linkoping		Linkoping
	Sweden		Sweden
	Email: take@modio.se		Email: take@modio.se
End of changes. 48 change blocks.
	58 lines changed or deleted		72 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/