< draft-ietf-6lo-use-cases-07.txt		draft-ietf-6lo-use-cases-08.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: March 13, 2020 UPC		Expires: May 7, 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
	September 10, 2019		November 4, 2019
	IPv6 over Constrained Node Networks (6lo) Applicability & Use cases		IPv6 over Constrained Node Networks (6lo) Applicability & Use cases
	draft-ietf-6lo-use-cases-07		draft-ietf-6lo-use-cases-08
	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, and PLC (IEEE		ITU-T G.9959 (Z-Wave), BLE, DECT-ULE, MS/TP, NFC, and PLC (IEEE
	1901.2) are used as examples. The document targets an audience who		1901.2) are used as examples. The document targets an audience who
	like to understand and evaluate running end-to-end IPv6 over the		like to understand and evaluate running end-to-end IPv6 over the
	constrained node networks connecting devices to each other or to		constrained node networks connecting devices to each other or to
	skipping to change at page 1, line 45 ¶		skipping to change at page 1, line 45 ¶
	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 March 13, 2020.		This Internet-Draft will expire on May 7, 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
	skipping to change at page 2, line 39 ¶		skipping to change at page 2, line 39 ¶
	3.5. NFC . . . . . . . . . . . . . . . . . . . . . . . . . . . 6		3.5. NFC . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3.6. PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . 7		3.6. PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
	3.7. Comparison between 6lo Link layer technologies . . . . . 7		3.7. Comparison between 6lo Link layer technologies . . . . . 7
	4. 6lo Deployment Scenarios . . . . . . . . . . . . . . . . . . 8		4. 6lo Deployment Scenarios . . . . . . . . . . . . . . . . . . 8
	4.1. G3-PLC usage of 6lo in network layer . . . . . . . . . . 8		4.1. G3-PLC usage of 6lo in network layer . . . . . . . . . . 8
	4.2. Netricity usage of 6lo in network layer . . . . . . . . . 9		4.2. Netricity usage of 6lo in network layer . . . . . . . . . 9
	5. Guidelines for adopting IPv6 stack (6lo/6LoWPAN) . . . . . . 10		5. Guidelines for adopting IPv6 stack (6lo/6LoWPAN) . . . . . . 10
	6. 6lo Use Case Examples . . . . . . . . . . . . . . . . . . . . 12		6. 6lo Use Case Examples . . . . . . . . . . . . . . . . . . . . 12
	6.1. Use case of ITU-T G.9959: Smart Home . . . . . . . . . . 12		6.1. Use case of ITU-T G.9959: Smart Home . . . . . . . . . . 12
	6.2. Use case of Bluetooth LE: Smartphone-based Interaction . 13		6.2. Use case of Bluetooth LE: Smartphone-based Interaction . 13
	6.3. Use case of DECT-ULE: Smart Home . . . . . . . . . . . . 13		6.3. Use case of DECT-ULE: Smart Home . . . . . . . . . . . . 14
	6.4. Use case of MS/TP: Building Automation Networks . . . . . 14		6.4. Use case of MS/TP: Building Automation Networks . . . . . 14
	6.5. Use case of NFC: Alternative Secure Transfer . . . . . . 15		6.5. Use case of NFC: Alternative Secure Transfer . . . . . . 15
	6.6. Use case of PLC: Smart Grid . . . . . . . . . . . . . . . 15		6.6. Use case of PLC: Smart Grid . . . . . . . . . . . . . . . 15
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 16		8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16		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. Design Space Dimensions for 6lo Deployment . . . . . 20		Appendix A. Design Space Dimensions for 6lo Deployment . . . . . 22
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
	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[IEEE802154] have a frame size of 127 octets and IPv6 requires
	below to support an MTU of 1280 bytes, therefore an appropriate		the layer below to support an MTU of 1280 bytes, therefore an
	fragmentation and reassembly adaptation layer must be provided at the		appropriate fragmentation and reassembly adaptation layer must be
	layer below IPv6. Also, the limited size of IEEE 802.15.4 frame and		provided at the layer below IPv6. Also, the limited size of IEEE
	low energy consumption requirements make the need for header		802.15.4 frame and low energy consumption requirements make the need
	compression. The IETF 6LoPWAN (IPv6 over Low powerWPAN) working		for header compression. The IETF 6LoPWAN (IPv6 over Low powerWPAN)
	group published an adaptation layer for sending IPv6 packets over		working group published an adaptation layer for sending IPv6 packets
	IEEE 802.15.4 [RFC4944], which includes a compression format for IPv6		over IEEE 802.15.4 [RFC4944], which includes a compression format for
	datagrams over IEEE 802.15.4-based networks [RFC6282], and Neighbor		IPv6 datagrams over IEEE 802.15.4-based networks [RFC6282], and
	Discovery Optimization for 6LoPWAN [RFC6775].		Neighbor 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), and Power Line		Passing (MS/TP), Near Field Communication (NFC), and Power Line
	Communication (PLC) have been defined at [IETF_6lo] working group.		Communication (PLC) have been defined at IETF 6lo working
	IPv6 stacks for constrained node networks use a variation of the		group[IETF_6lo]. IPv6 stacks for constrained node networks use a
	6LoWPAN stack applied to each particular link layer technology.		variation of the 6LoWPAN stack applied to each particular link 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,
	power source, connectivity, multi-hop communication, traffic pattern,		power source, connectivity, multi-hop communication, traffic pattern,
	security level, mobility, and QoS requirements etc. In addition, it		security level, mobility, and QoS requirements etc. In addition, it
	describes a few set of 6LoPWAN application scenarios and practical		describes a few set of 6LoPWAN application scenarios and practical
	deployment as examples.		deployment as examples.
	This document provides the applicability and use cases of 6lo,		This document provides the applicability and use cases of 6lo,
	considering the following aspects:		considering the following aspects:
	skipping to change at page 9, line 28 ¶		skipping to change at page 9, line 28 ¶
	o Distribution Automation		o Distribution Automation
	o Home/Building Energy Management Systems		o Home/Building Energy Management Systems
	o Smart Street Lighting		o Smart Street Lighting
	o Advanced Metering Infrastructure (AMI) backbone network		o Advanced Metering Infrastructure (AMI) backbone network
	o Wind/Solar Farm Monitoring		o Wind/Solar Farm Monitoring
	In the G3-PLC specification, the 6lo adaptation layer utilizes the		In the G3-PLC specification, the 6lo adaption layer utilizes the
	6LoWPAN functions (e.g. header compression, fragmentation and		6LoWPAN functions (e.g. header compression, fragmentation and
	reassembly) so as to enable IPv6 packet transmission. LOADng, which		reassembly). However, due to the different characteristics of the
	is a lightweight variant of AODV, is applied as the mesh-under		PLC media, the 6LoWPAN adaptation layer cannot perfectly fulfill the
	routing protocol in G3-PLC networks. Address assignment and network		requirements[I-D.ietf-6lo-plc]. The ESC dispatch type is used in the
	configuration are based on the bootstrapping protocol specified in		G3-PLC to provide native mesh routing and bootstrapping
	ITU-T G.9903. The network layer consists of IPv6 and ICMPv6 while		functionalities[RFC8066].
	the transport protocol UDP is used for data transmission.
	4.2. 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
	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
	skipping to change at page 11, line 22 ¶		skipping to change at page 11, line 22 ¶
	unfragmented application packets would be optimum for packet		unfragmented application packets would be optimum for packet
	transmission if the deployment can afford it. Please refer to 6lo		transmission if the deployment can afford it. Please refer to 6lo
	RFCs [RFC7668], [RFC8163], [RFC8105] for example guidance.		RFCs [RFC7668], [RFC8163], [RFC8105] for example guidance.
	o Mesh or L3-Routing: 6LoWPAN specifications do provide mechanisms		o Mesh or L3-Routing: 6LoWPAN specifications do provide mechanisms
	to support for mesh routing at L2. [RFC6550] defines layer three		to support for mesh routing at L2. [RFC6550] defines layer three
	(L3) routing for low power lossy networks using directed graphs.		(L3) routing for low power lossy networks using directed graphs.
	6LoWPAN is routing protocol agnostic and other L2 or L3 routing		6LoWPAN is routing protocol agnostic and other L2 or L3 routing
	protocols can be run using a 6LoWPAN stack.		protocols can be run using a 6LoWPAN stack.
	o Address Assignment: 6LoWPAN requires that IPv6 Neighbor Discovery		o Address Assignment: 6LoWPAN developed a new version of IPv6
	for low power networks [RFC6775] be used for autoconfiguration of		Neighbor Discovery[RFC4861][RFC4862] that relies on a proactive
	stateless IPv6 address assignment. Considering the energy		registration to avoid the use of multicast. 6LoWPAN Neighbor
	sensitive networks [RFC6775] makes optimization from classical		Discovery[RFC6775][RFC8505] inherits from IPv6 Neighbor Discovery
	IPv6 ND [RFC4861] protocol. It is the responsibility of the		for mechanisms such as Stateless Address Autoconfiguration(SLAAC)
	deployment to ensure unique global IPv6 addresses for the Internet		and Neighbor Unreachability Detection(NUD), but uses a unicast
	connectivity. For local-only connectivity IPv6 ULA may be used.		method for Duplicate Address Detection(DAD), and avoids multicast
	[RFC6775] specifies the 6LoWPAN border router(6LBR) which is		lookups from all nodes by using non-onlink prefixes. A 6LoWPAN
	responsible for prefix assignment to the 6lo/6LoWPAN network. 6LBR		Node is also expected to be an IPv6 host per[RFC8200] which means
	can be connected to the Internet or Enterprise network via its one		it should ignore consumed routing headers and Hop-by-Hop options;
	of the interfaces. Please refer to [RFC7668] and [RFC8105] for		when operating in a RPL network[RFC6550], it is also beneficial to
	examples of address assignment considerations. In addition,		support IP-in-IP encapsulation [I-D.ietf-roll-useofrplinfo]. The
	privacy considerations [RFC8065] must be consulted for		6LoWPWAN Node should also support [RFC8505] and use it as the
	applicability. In certain scenarios, the deployment may not		default Neighbor Discovery method. It is the responsibility of
			the deployment to ensure unique global IPv6 addresses for the
			Internet connectivity. For local-only connectivity IPv6 ULA may
			be used. [RFC6775] specifies the 6LoWPAN border router(6LBR)
			which is responsible for prefix assignment to the 6lo/6LoWPAN
			network. 6LBR can be connected to the Internet or Enterprise
			network via its one of the interfaces. Please refer to [RFC7668]
			and [RFC8105] for examples of address assignment considerations.
			In addition, privacy considerations [RFC8065] must be consulted
			for applicability. In certain scenarios, the deployment may not
	support autoconfiguration of IPv6 addressing due to regulatory and		support autoconfiguration of IPv6 addressing due to regulatory and
	business reasons and may choose to offer a separate address		business reasons and may choose to offer a separate address
	assignment service.		assignment service.
	o Header Compression: IPv6 header compression [RFC6282] is a vital		o Header Compression: IPv6 header compression [RFC6282] is a vital
	part of IPv6 over low power communication. Examples of header		part of IPv6 over low power communication. Examples of header
	compression for different link-layers specifications are found in		compression for different link-layers specifications are found in
	[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 [IETF_ace] and
	should be consulted for application and transport level security.		[IETF_core] should be consulted for application and transport
	6lo working group is working on address authentication [6lo-ap-nd]		level security. 6lo working group is working on address
	and secure bootstrapping is also being discussed at IETF.		authentication [I-D.ietf-6lo-ap-nd] and secure bootstrapping is
			also being discussed at IETF. However, there may be different
	However, there may be different levels of security available in a		levels of security available in a deployment through other
	deployment through other standards such as hardware level security		standards such as hardware level security or certificates for
	or certificates for initial booting process. Encryption is		initial booting process. Encryption is important if the
	important if the implementation can afford it.		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,
	skipping to change at page 19, line 21 ¶		skipping to change at page 19, line 37 ¶
	[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, <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>.
			[RFC8505] Thubert, P., Ed., Nordmark, E., Chakrabarti, S., and C.
			Perkins, "Registration Extensions for IPv6 over Low-Power
			Wireless Personal Area Network (6LoWPAN) Neighbor
			Discovery", RFC 8505, DOI 10.17487/RFC8505, November 2018,
			<https://www.rfc-editor.org/info/rfc8505>.
	10.2. Informative References		10.2. Informative References
	[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>.
			[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
			Address Autoconfiguration", RFC 4862,
			DOI 10.17487/RFC4862, September 2007,
			<https://www.rfc-editor.org/info/rfc4862>.
			[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
			(IPv6) Specification", STD 86, RFC 8200,
			DOI 10.17487/RFC8200, July 2017,
			<https://www.rfc-editor.org/info/rfc8200>.
	[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-15 (work in progress),		Communication", draft-ietf-6lo-nfc-15 (work in progress),
	July 2019.		July 2019.
	[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-05 (work in progress), March 2019.		draft-ietf-6lo-blemesh-06 (work in progress), September
			2019.
	[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.
			[I-D.ietf-roll-useofrplinfo]
			Robles, I., Richardson, M., and P. Thubert, "Using RPL
			Option Type, Routing Header for Source Routes and IPv6-in-
			IPv6 encapsulation in the RPL Data Plane", draft-ietf-
			roll-useofrplinfo-31 (work in progress), August 2019.
			[I-D.ietf-6lo-ap-nd]
			Thubert, P., Sarikaya, B., Sethi, M., and R. Struik,
			"Address Protected Neighbor Discovery for Low-power and
			Lossy Networks", draft-ietf-6lo-ap-nd-12 (work in
			progress), April 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/>.
			[IETF_ace]
			"IETF Authentication and Authorization for Constrained
			Environments (ace) working group",
			<https://datatracker.ietf.org/wg/ace/charter/>.
			[IETF_core]
			"IETF Constrained RESTful Environments (core) working
			group", <https://datatracker.ietf.org/wg/core/charter/>.
			[IEEE802154]
			IEEE standard for Information Technology, "IEEE Std.
			802.15.4, Part. 15.4: Wireless Medium Access Control (MAC)
			and Physical Layer (PHY) Specifications for Low-Rate
			Wireless Personal Area Networks".
	[TIA-485-A]		[TIA-485-A]
	"TIA, "Electrical Characteristics of Generators and		"TIA, "Electrical Characteristics of Generators and
	Receivers for Use in Balanced Digital Multipoint Systems",		Receivers for Use in Balanced Digital Multipoint Systems",
	TIA-485-A (Revision of TIA-485)", March 2003,		TIA-485-A (Revision of TIA-485)", March 2003,
	<https://global.ihs.com/		<https://global.ihs.com/
	doc_detail.cfm?item_s_key=00032964>.		doc_detail.cfm?item_s_key=00032964>.
	[G3-PLC] "G3-PLC Alliance", <http://www.g3-plc.com/home/>.		[G3-PLC] "G3-PLC Alliance", <http://www.g3-plc.com/home/>.
	[NETRICITY]		[NETRICITY]
End of changes. 22 change blocks.
	55 lines changed or deleted		109 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/