< draft-ietf-6lo-use-cases-05.txt		draft-ietf-6lo-use-cases-06.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 1, 2019 UPC		Expires: September 12, 2019 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
	June 30, 2018		March 11, 2019
	IPv6 over Constrained Node Networks (6lo) Applicability & Use cases		IPv6 over Constrained Node Networks (6lo) Applicability & Use cases
	draft-ietf-6lo-use-cases-05		draft-ietf-6lo-use-cases-06
	Abstract		Abstract
	This document describes the applicability of IPv6 over constrained		This document describes the applicability of IPv6 over constrained
	node networks (6lo) and provides practical deployment examples. In		node networks (6lo) and provides practical deployment examples. In
	addition to IEEE 802.15.4, various link layer technologies such as		addition to IEEE 802.15.4, various link layer technologies such as
	ITU-T G.9959 (Z-Wave), BLE, DECT-ULE, MS/TP, NFC, PLC (IEEE 1901.2),		ITU-T G.9959 (Z-Wave), BLE, DECT-ULE, MS/TP, NFC, 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 node networks connecting devices to		to-end IPv6 over the constrained node networks connecting devices to
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 January 1, 2019.		This Internet-Draft will expire on September 12, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2019 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 7, line 13 ¶		skipping to change at page 7, line 13 ¶
	secure transfer in healthcare services.		secure transfer in healthcare services.
	3.6. PLC (specified)		3.6. PLC (specified)
	PLC is a data transmission technique that utilizes power conductors		PLC is a data transmission technique that utilizes power conductors
	as medium. Unlike other dedicated communication infrastructure,		as medium. Unlike other dedicated communication infrastructure,
	power conductors are widely available indoors and outdoors.		power conductors are widely available indoors and outdoors.
	Moreover, wired technologies are more susceptible to cause		Moreover, wired technologies are more susceptible to cause
	interference but are more reliable than their wireless counterparts.		interference but are more reliable than their wireless counterparts.
	PLC is a data transmission technique that utilizes power conductors		PLC is a data transmission technique that utilizes power conductors
	as medium.		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 9, line 37 ¶		skipping to change at page 9, line 37 ¶
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	| 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 # | | | | | draft- | draft- | |		| RFC # | | | | | draft- | draft- | |
	| or | RFC7428| RFC7668| RFC8105| RFC8163|ietf-6lo|hou-6lo-| RFC7554|		| or | RFC7428| RFC7668| RFC8105| RFC8163|ietf-6lo|ietf-6lo| RFC7554|
	| Draft | | | | | -nfc | plc | |		| Draft | | | | | -nfc | -plc | |
	+-----------+--------+--------+--------+--------+--------+--------+--------+		+-----------+--------+--------+--------+--------+--------+--------+--------+
	Table 2: Comparison between 6lo Link layer technologies		Table 2: Comparison between 6lo Link layer technologies
	4. 6lo Deployment Scenarios		4. 6lo Deployment Scenarios
	4.1. jupitermesh in Smart Grid using 6lo in network layer		4.1. 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 15, line 42 ¶		skipping to change at page 15, line 42 ¶
	length and random transmission. Some 6lo use case may require		length and random transmission. Some 6lo use case may require
	continuous data and periodic data transmission.		continuous data and periodic data transmission.
	o Security Bootstrapping: Without the external operations, 6lo nodes		o Security Bootstrapping: Without the external operations, 6lo nodes
	must have the security bootstrapping mechanism.		must have the security bootstrapping mechanism.
	o Power use strategy: to enable certain use cases, there may be		o Power use strategy: to enable certain use cases, there may be
	requirements on the class of energy availability and the strategy		requirements on the class of energy availability and the strategy
	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 [RFC8352]. Readers are expected to be familiar with
	to be familiar with [RFC7228] terminology.		[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		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/
	skipping to change at page 21, line 32 ¶		skipping to change at page 21, line 32 ¶
	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>.
			[RFC8352] Gomez, C., Kovatsch, M., Tian, H., and Z. Cao, Ed.,
			"Energy-Efficient Features of Internet of Things
			Protocols", RFC 8352, DOI 10.17487/RFC8352, April 2018,
			<https://www.rfc-editor.org/info/rfc8352>.
	10.2. Informative References		10.2. Informative References
	[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,		[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, <https://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,
	<https://www.rfc-editor.org/info/rfc4861>.		<https://www.rfc-editor.org/info/rfc4861>.
	[I-D.ietf-6lo-nfc]		[I-D.ietf-6lo-nfc]
	Choi, Y., Hong, Y., Youn, J., Kim, D., and J. Choi,		Choi, Y., Hong, Y., Youn, J., Kim, D., and J. Choi,
	"Transmission of IPv6 Packets over Near Field		"Transmission of IPv6 Packets over Near Field
	Communication", draft-ietf-6lo-nfc-09 (work in progress),		Communication", draft-ietf-6lo-nfc-13 (work in progress),
	January 2018.		February 2019.
	[I-D.ietf-lwig-energy-efficient]
	Gomez, C., Kovatsch, M., Tian, H., and Z. Cao, "Energy-
	Efficient Features of Internet of Things Protocols",
	draft-ietf-lwig-energy-efficient-08 (work in progress),
	October 2017.
	[I-D.ietf-roll-aodv-rpl]		[I-D.ietf-roll-aodv-rpl]
	Anamalamudi, S., Zhang, M., Sangi, A., Perkins, C., Anand,		Anamalamudi, S., Zhang, M., Perkins, C., Anand, S., and B.
	S., and B. Liu, "Asymmetric AODV-P2P-RPL in Low-Power and		Liu, "Asymmetric AODV-P2P-RPL in Low-Power and Lossy
	Lossy Networks (LLNs)", draft-ietf-roll-aodv-rpl-03 (work		Networks (LLNs)", draft-ietf-roll-aodv-rpl-06 (work in
	in progress), March 2018.		progress), March 2019.
	[I-D.ietf-6tisch-6top-sfx]		[I-D.ietf-6tisch-6top-sfx]
	Dujovne, D., Grieco, L., Palattella, M., and N. Accettura,		Dujovne, D., Grieco, L., Palattella, M., and N. Accettura,
	"6TiSCH Experimental Scheduling Function (SFX)", draft-		"6TiSCH Experimental Scheduling Function (SFX)", draft-
	ietf-6tisch-6top-sfx-01 (work in progress), March 2018.		ietf-6tisch-6top-sfx-01 (work in progress), March 2018.
	[I-D.ietf-6lo-blemesh]		[I-D.ietf-6lo-blemesh]
	Gomez, C., Darroudi, S., and T. Savolainen, "IPv6 Mesh		Gomez, C., Darroudi, S., Savolainen, T., and M. Spoerk,
	over BLUETOOTH(R) Low Energy using IPSP", draft-ietf-6lo-		"IPv6 Mesh over BLUETOOTH(R) Low Energy using IPSP",
	blemesh-02 (work in progress), September 2017.		draft-ietf-6lo-blemesh-04 (work in progress), January
			2019.
	[I-D.satish-6tisch-6top-sf1]		[I-D.satish-6tisch-6top-sf1]
	Anamalamudi, S., Liu, B., Zhang, M., Sangi, A., Perkins,		Anamalamudi, S., Liu, B., Zhang, M., Sangi, A., Perkins,
	C., and S. Anand, "Scheduling Function One (SF1): hop-by-		C., and S. Anand, "Scheduling Function One (SF1): hop-by-
	hop Scheduling with RSVP-TE in 6tisch Networks", draft-		hop Scheduling with RSVP-TE in 6tisch Networks", draft-
	satish-6tisch-6top-sf1-04 (work in progress), October		satish-6tisch-6top-sf1-04 (work in progress), October
	2017.		2017.
			[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.
	[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/>.
	[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/
End of changes. 13 change blocks.
	25 lines changed or deleted		30 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/