< draft-ietf-6lo-use-cases-08.txt		draft-ietf-6lo-use-cases-09.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: May 7, 2020 UPC		Expires: January 14, 2021 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
	November 4, 2019		July 13, 2020
	IPv6 over Constrained Node Networks (6lo) Applicability & Use cases		IPv6 over Constrained Node Networks (6lo) Applicability & Use cases
	draft-ietf-6lo-use-cases-08		draft-ietf-6lo-use-cases-09
	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 May 7, 2020.		This Internet-Draft will expire on January 14, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2020 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
	skipping to change at page 2, line 48 ¶		skipping to change at page 2, line 48 ¶
	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 . . . . . . . . . . . . 14		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 . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . 17
	Appendix A. Design Space Dimensions for 6lo Deployment . . . . . 22		Appendix A. Design Space Dimensions for 6lo Deployment . . . . . 22
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
	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[IEEE802154] have a frame size of 127 octets and IPv6 requires		layers[IEEE802154] have a frame size of 127 octets and IPv6 requires
	the layer below to support an MTU of 1280 bytes, therefore an		the layer below to support an MTU of 1280 bytes, therefore an
	skipping to change at page 3, line 50 ¶		skipping to change at page 3, line 50 ¶
	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:
	o 6lo applicability and use cases MAY be uniquely different from		o 6lo applicability and use cases are uniquely different from those
	those of 6LoWPAN defined for IEEE 802.15.4.		of 6LoWPAN defined for IEEE 802.15.4.
	o It SHOULD cover various IoT related wire/wireless link layer		o It covers various IoT related wire/wireless link layer
	technologies providing practical information of such technologies.		technologies providing practical information of such technologies.
	o A general guideline on how the 6LoWPAN stack can be modified for a		o A general guideline on how the 6LoWPAN stack can be modified for a
	given L2 technology.		given L2 technology is described.
	o Example use cases and practical deployment examples.		o Various 6lo use cases and practical deployment examples are
			described.
	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		3. 6lo Link layer technologies
	3.1. ITU-T G.9959		3.1. ITU-T G.9959
	skipping to change at page 7, line 10 ¶		skipping to change at page 7, line 10 ¶
	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		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 cause less interference to the radio
	interference but are more reliable than their wireless counterparts.		medium than wireless technologies and are more reliable than their
	PLC is a data transmission technique that utilizes power conductors		wireless counterparts. PLC is a data transmission technique that
	as medium[I-D.ietf-6lo-plc].		utilizes power conductors 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.
	+-------------+-----------------+------------+-----------+----------+		+-------------+-----------------+------------+-----------+----------+
	| PLC Systems | Frequency Range | Type | Data Rate | Distance |		| PLC Systems | Frequency Range | Type | Data Rate | Distance |
	+-------------+-----------------+------------+-----------+----------+		+-------------+-----------------+------------+-----------+----------+
	| IEEE1901 | <100MHz | Broadband | 200Mbps | 1000m |		| IEEE1901 | <100MHz | Broadband | 200Mbps | 1000m |
	| | | | | |		| | | | | |
	| IEEE1901.1 | <15MHz | PLC-IoT | 10Mbps | 2000m |		| IEEE1901.1 | <15MHz | PLC-IoT | 10Mbps | 2000m |
	| | | | | |		| | | | | |
	skipping to change at page 7, line 46 ¶		skipping to change at page 7, line 46 ¶
	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. Comparison between 6lo Link layer technologies		3.7. 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 are described.
	candidate are described. The following table shows that dominant		The following table shows dominant parameters of each use case
	paramters of each use case corresponding to the 6lo link layer		corresponding to the 6lo link layer technology.
	technology.
	+--------------+---------+---------+---------+---------+---------+---------+		+--------------+---------+---------+---------+---------+---------+---------+
	| | Z-Wave | BLE | DECT-ULE| MS/TP | NFC | PLC |		| | Z-Wave | BLE | DECT-ULE| MS/TP | NFC | PLC |
	+--------------+---------+---------+---------+---------+---------+---------+		+--------------+---------+---------+---------+---------+---------+---------+
	| | Home | Interact| | Building| Health- | |		| | Home | Interact| | Building| Health- | |
	| Usage | Auto- | w/ Smart| Meter | Auto- | care | Smart |		| Usage | Auto- | w/ Smart| Meter | Auto- | care | Smart |
	| | mation | Phone | Reading | mation | Service | Grid |		| | 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 |		| & | or | & | | | | Tree |
	skipping to change at page 10, line 33 ¶		skipping to change at page 10, line 33 ¶
	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. Guidelines for adopting IPv6 stack (6lo/6LoWPAN)		5. 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
	IPv6 Link-local and global addresses, L2-address-derived IPv6		IPv6 Link-local and global addresses, L2-address-derived IPv6
	addresses are specified in [RFC4944], but there exist implications		addresses are specified in [RFC4944], but there exist implications
	for privacy. For global usage, a unique IPv6 address must be		for privacy. For global usage, a unique IPv6 address must be
	derived using an assigned prefix and a unique interface ID.		derived using an assigned prefix and a unique interface ID.
	[RFC8065] provides such guidelines. For MAC derived IPv6 address,		[RFC8065] provides such guidelines. For MAC derived IPv6 address,
	please refer to [RFC8163] for IPv6 address mapping examples.		please refer to [RFC8163] for IPv6 address mapping examples.
	Broadcast and multicast support are dependent on the L2 networks.		Broadcast and multicast support are dependent on the L2 networks.
	Most low-power L2 implementations map multicast to broadcast		Most low-power L2 implementations map multicast to broadcast
	networks. So care must be taken in the design when to use		networks. So care must be taken in the design when to use
	broadcast and try to stick to unicast messaging whenever possible.		broadcast and try to stick to unicast messaging whenever possible.
	o MTU Considerations: The deployment SHOULD consider their need for		o MTU Considerations: The deployment SHOULD consider their need for
	maximum transmission unit (MTU) of a packet over the link layer		maximum transmission unit (MTU) of a packet over the link layer
	and should consider if fragmentation and reassembly of packets are		and SHOULD consider if fragmentation and reassembly of packets are
	needed at the 6LoWPAN layer. For example, if the link layer		needed at the 6LoWPAN layer. For example, if the link layer
	supports fragmentation and reassembly of packets, then 6LoWPAN		supports fragmentation and reassembly of packets, then 6LoWPAN
	layer may skip supporting fragmentation/reassembly. In fact, for		layer may skip supporting fragmentation/reassembly. In fact, for
	most efficiency, choosing a low-power link layer that can carry		most efficiency, choosing a low-power link layer that can carry
	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
	skipping to change at page 17, line 42 ¶		skipping to change at page 17, line 42 ¶
	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,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
			10.2. Informative References
			[BACnet] "ASHRAE, "BACnet-A Data Communication Protocol for
			Building Automation and Control Networks", ANSI/ASHRAE
			Standard 135-2016", January 2016,
			<http://www.techstreet.com/ashrae/standards/ashrae-
			135-2016?product_id=1918140#jumps>.
			[G.9903] "International Telecommunication Union, "Narrowband
			orthogonal frequency division multiplexing power line
			communication transceivers for G3-PLC networks", ITU-T
			Recommendation", August 2017.
			[G.9959] "International Telecommunication Union, "Short range
			narrow-band digital radiocommunication transceivers - PHY
			and MAC layer specifications", ITU-T Recommendation",
			January 2015.
			[G3-PLC] "G3-PLC Alliance", <http://www.g3-plc.com/home/>.
			[IEEE1901]
			"IEEE Standard, IEEE Std. 1901-2010 - IEEE Standard for
			Broadband over Power Line Networks: Medium Access Control
			and Physical Layer Specifications", 2010,
			<https://standards.ieee.org/findstds/
			standard/1901-2010.html>.
			[IEEE1901.2]
			"IEEE Standard, IEEE Std. 1901.2-2013 - IEEE Standard for
			Low-Frequency (less than 500 kHz) Narrowband Power Line
			Communications for Smart Grid Applications", 2013,
			<https://standards.ieee.org/findstds/
			standard/1901.2-2013.html>.
			[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".
			[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-23 (work in
			progress), April 2020.
			[I-D.ietf-6lo-blemesh]
			Gomez, C., Darroudi, S., Savolainen, T., and M. Spoerk,
			"IPv6 Mesh over BLUETOOTH(R) Low Energy using IPSP",
			draft-ietf-6lo-blemesh-07 (work in progress), December
			2019.
			[I-D.ietf-6lo-nfc]
			Choi, Y., Hong, Y., Youn, J., Kim, D., and J. Choi,
			"Transmission of IPv6 Packets over Near Field
			Communication", draft-ietf-6lo-nfc-16 (work in progress),
			July 2020.
			[I-D.ietf-6lo-plc]
			Hou, J., Liu, B., Hong, Y., Tang, X., and C. Perkins,
			"Transmission of IPv6 Packets over PLC Networks", draft-
			ietf-6lo-plc-04 (work in progress), June 2020.
			[I-D.ietf-roll-useofrplinfo]
			Robles, I., Richardson, M., and P. Thubert, "Using RPI
			Option Type, Routing Header for Source Routes and IPv6-in-
			IPv6 encapsulation in the RPL Data Plane", draft-ietf-
			roll-useofrplinfo-40 (work in progress), June 2020.
			[IETF_6lo]
			"IETF IPv6 over Networks of Resource-constrained Nodes
			(6lo) working group",
			<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/>.
			[NETRICITY]
			"Netricity program in HomePlug Powerline Alliance",
			<http://groups.homeplug.org/tech/Netricity>.
			[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
			"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
			DOI 10.17487/RFC4861, September 2007,
			<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>.
	[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,
	<https://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,
	<https://www.rfc-editor.org/info/rfc4944>.		<https://www.rfc-editor.org/info/rfc4944>.
	skipping to change at page 19, line 32 ¶		skipping to change at page 21, line 47 ¶
	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, <https://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, <https://www.rfc-editor.org/info/rfc8163>.		May 2017, <https://www.rfc-editor.org/info/rfc8163>.
			[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>.
	[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.		[RFC8505] Thubert, P., Ed., Nordmark, E., Chakrabarti, S., and C.
	Perkins, "Registration Extensions for IPv6 over Low-Power		Perkins, "Registration Extensions for IPv6 over Low-Power
	Wireless Personal Area Network (6LoWPAN) Neighbor		Wireless Personal Area Network (6LoWPAN) Neighbor
	Discovery", RFC 8505, DOI 10.17487/RFC8505, November 2018,		Discovery", RFC 8505, DOI 10.17487/RFC8505, November 2018,
	<https://www.rfc-editor.org/info/rfc8505>.		<https://www.rfc-editor.org/info/rfc8505>.
	10.2. Informative References
	[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
	"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
	DOI 10.17487/RFC4861, September 2007,
	<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]
	Choi, Y., Hong, Y., Youn, J., Kim, D., and J. Choi,
	"Transmission of IPv6 Packets over Near Field
	Communication", draft-ietf-6lo-nfc-15 (work in progress),
	July 2019.
	[I-D.ietf-6lo-blemesh]
	Gomez, C., Darroudi, S., Savolainen, T., and M. Spoerk,
	"IPv6 Mesh over BLUETOOTH(R) Low Energy using IPSP",
	draft-ietf-6lo-blemesh-06 (work in progress), September
	2019.
	[I-D.ietf-6lo-plc]
	Hou, J., Liu, B., Hong, Y., Tang, X., and C. Perkins,
	"Transmission of IPv6 Packets over PLC Networks", draft-
	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 IPv6 over Networks of Resource-constrained Nodes
	(6lo) working group",
	<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/>.
	[NETRICITY]
	"Netricity program in HomePlug Powerline Alliance",
	<http://groups.homeplug.org/tech/Netricity>.
	[G.9959] "International Telecommunication Union, "Short range
	narrow-band digital radiocommunication transceivers - PHY
	and MAC layer specifications", ITU-T Recommendation",
	January 2015.
	[G.9903] "International Telecommunication Union, "Narrowband
	orthogonal frequency division multiplexing power line
	communication transceivers for G3-PLC networks", ITU-T
	Recommendation", August 2017.
	[IEEE1901]
	"IEEE Standard, IEEE Std. 1901-2010 - IEEE Standard for
	Broadband over Power Line Networks: Medium Access Control
	and Physical Layer Specifications", 2010,
	<https://standards.ieee.org/findstds/
	standard/1901-2010.html>.
	[IEEE1901.2]
	"IEEE Standard, IEEE Std. 1901.2-2013 - IEEE Standard for
	Low-Frequency (less than 500 kHz) Narrowband Power Line
	Communications for Smart Grid Applications", 2013,
	<https://standards.ieee.org/findstds/
	standard/1901.2-2013.html>.
	[BACnet] "ASHRAE, "BACnet-A Data Communication Protocol for
	Building Automation and Control Networks", ANSI/ASHRAE
	Standard 135-2016", January 2016,
	<http://www.techstreet.com/ashrae/standards/ashrae-
	135-2016?product_id=1918140#jumps>.
	Appendix A. Design Space Dimensions for 6lo Deployment		Appendix A. Design Space Dimensions for 6lo Deployment
	The [RFC6568] lists the dimensions used to describe the design space		The [RFC6568] lists the dimensions used to describe the design space
	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], the following design space dimensions are
	described: Deployment, Network size, Power source, Connectivity,		described: Deployment, Network size, Power source, Connectivity,
	Multi-hop communication, Traffic pattern, Mobility, Quality of		Multi-hop communication, Traffic pattern, Mobility, Quality of
	Service (QoS). However, in this document, the following design space		Service (QoS). However, in this document, the following design space
	skipping to change at page 24, line 4 ¶		skipping to change at page 24, line 10 ¶
	o Wired vs. Wireless: Plenty of 6lo link layer technologies are		o Wired vs. Wireless: Plenty of 6lo link layer technologies are
	wireless, except MS/TP and PLC. The selection of wired or		wireless, except MS/TP and PLC. The selection of wired or
	wireless link layer technology is mainly dependent on the		wireless link layer technology is mainly dependent on the
	requirement of 6lo use cases and the characteristics of wired/		requirement of 6lo use cases and the characteristics of wired/
	wireless technologies. For example, some 6lo use cases may		wireless technologies. For example, some 6lo use cases may
	require easy and quick deployment, whereas others may need a		require easy and quick deployment, whereas others may need a
	continuous source of power.		continuous source of power.
	Authors' Addresses		Authors' Addresses
	Yong-Geun Hong		Yong-Geun Hong
	ETRI		ETRI
	161 Gajeong-Dong Yuseung-Gu		218 Gajeongno, Yuseong
	Daejeon 305-700		Daejeon 34129
	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 34129
	Korea		Korea
	Phone: +82 42 860 1429		Phone: +82 42 860 1429
	Email: yhc@etri.re.kr		Email: yhc@etri.re.kr
	Abdur Rashid Sangi		Abdur Rashid Sangi
	Huaiyin Institute of Technology		Huaiyin Institute of Technology
	No.89 North Beijing Road, Qinghe District		No.89 North Beijing Road, Qinghe District
	Huaian 223001		Huaian 223001
	P.R. China		P.R. China
End of changes. 22 change blocks.
	127 lines changed or deleted		128 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/