< draft-ietf-roll-useofrplinfo-08.txt		draft-ietf-roll-useofrplinfo-09.txt >
	ROLL Working Group M. Robles		ROLL Working Group M. Robles
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Informational M. Richardson		Updates: 6550 (if approved) M. Richardson
	Expires: March 17, 2017 SSW		Intended status: Standards Track SSW
	P. Thubert		Expires: April 24, 2017 P. Thubert
	Cisco		Cisco
	September 13, 2016		October 21, 2016
	When to use RFC 6553, 6554 and IPv6-in-IPv6		When to use RFC 6553, 6554 and IPv6-in-IPv6
	draft-ietf-roll-useofrplinfo-08		draft-ietf-roll-useofrplinfo-09
	Abstract		Abstract
	This document looks at different data flows through LLN (Low-Power		This document looks at different data flows through LLN (Low-Power
	and Lossy Networks) where RPL (IPv6 Routing Protocol for Low-Power		and Lossy Networks) where RPL (IPv6 Routing Protocol for Low-Power
	and Lossy Networks) is used to establish routing. The document		and Lossy Networks) is used to establish routing. The document
	enumerates the cases where RFC 6553, RFC 6554 and IPv6-in-IPv6		enumerates the cases where RFC 6553, RFC 6554 and IPv6-in-IPv6
	encapsulation is required. This analysis provides the basis on which		encapsulation is required. This analysis provides the basis on which
	to design efficient compression of these headers.		to design efficient compression of these headers.
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 http://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 17, 2017.		This Internet-Draft will expire on April 24, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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		(http://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 3, line 40 ¶		skipping to change at page 3, line 40 ¶
	if there were any shortcuts, and this document is the result of that		if there were any shortcuts, and this document is the result of that
	discussion. This document should not be defining anything new, but		discussion. This document should not be defining anything new, but
	it may clarify what is correct and incorrect behaviour.		it may clarify what is correct and incorrect behaviour.
	The related document A Routing Header Dispatch for 6LoWPAN (6LoRH)		The related document A Routing Header Dispatch for 6LoWPAN (6LoRH)
	[I-D.ietf-roll-routing-dispatch] defines a method to compress RPL		[I-D.ietf-roll-routing-dispatch] defines a method to compress RPL
	Option information and Routing Header type 3 [RFC6554], an efficient		Option information and Routing Header type 3 [RFC6554], an efficient
	IP-in-IP technique, and use cases proposed for the		IP-in-IP technique, and use cases proposed for the
	[Second6TischPlugtest] involving 6loRH.		[Second6TischPlugtest] involving 6loRH.
			The related document updates [RFC6550]. In general, any packet that
			leaves the RPL domain of an LLN (or leaves the LLN entirely) will NOT
			be discarded, when it has the [RFC6553] RPL Option Header known as
			the RPI or [RFC6554] SRH3 Extension Header (S)RH3. Due to changes to
			[I-D.ietf-6man-rfc2460bis] the RPI Hop-by-Hop option MAY be left in
			place even if the end host does not understand it.
	2. Terminology and Requirements Language		2. Terminology and Requirements Language
	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 RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	Terminology defined in [RFC7102] applies to this document: LBR, LLN,		Terminology defined in [RFC7102] applies to this document: LBR, LLN,
	RPL, RPL Domain and ROLL.		RPL, RPL Domain and ROLL.
	RPL-node: It is device which implements RPL, thus we can say that the		RPL-node: It is device which implements RPL, thus we can say that the
	skipping to change at page 32, line 24 ¶		skipping to change at page 32, line 24 ¶
	The authors would like to acknowledge the review, feedback, and		The authors would like to acknowledge the review, feedback, and
	comments of Robert Cragie, Simon Duquennoy, Cenk Guendogan, Peter van		comments of Robert Cragie, Simon Duquennoy, Cenk Guendogan, Peter van
	der Stok, Xavier Vilajosana and Thomas Watteyne.		der Stok, Xavier Vilajosana and Thomas Watteyne.
	12. References		12. References
	12.1. Normative References		12.1. Normative References
	[I-D.ietf-6man-rfc2460bis]		[I-D.ietf-6man-rfc2460bis]
	Hinden, R., "Internet Protocol, Version 6 (IPv6)		Deering, S. and R. Hinden, "Internet Protocol, Version 6
	Specification", draft-ietf-6man-rfc2460bis-06 (work in		(IPv6) Specification", draft-ietf-6man-rfc2460bis-07 (work
	progress), September 2016.		in progress), October 2016.
	[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>.		<http://www.rfc-editor.org/info/rfc2119>.
	[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6		[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
	(IPv6) Specification", RFC 2460, December 1998.		(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
			December 1998, <http://www.rfc-editor.org/info/rfc2460>.
	[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>.		<http://www.rfc-editor.org/info/rfc6550>.
	[RFC6553] Hui, J. and JP. Vasseur, "The Routing Protocol for Low-		[RFC6553] Hui, J. and JP. Vasseur, "The Routing Protocol for Low-
	Power and Lossy Networks (RPL) Option for Carrying RPL		Power and Lossy Networks (RPL) Option for Carrying RPL
	skipping to change at page 33, line 21 ¶		skipping to change at page 33, line 21 ¶
	12.2. Informative References		12.2. Informative References
	[I-D.ietf-6tisch-architecture]		[I-D.ietf-6tisch-architecture]
	Thubert, P., "An Architecture for IPv6 over the TSCH mode		Thubert, P., "An Architecture for IPv6 over the TSCH mode
	of IEEE 802.15.4", draft-ietf-6tisch-architecture-10 (work		of IEEE 802.15.4", draft-ietf-6tisch-architecture-10 (work
	in progress), June 2016.		in progress), June 2016.
	[I-D.ietf-roll-routing-dispatch]		[I-D.ietf-roll-routing-dispatch]
	Thubert, P., Bormann, C., Toutain, L., and R. Cragie,		Thubert, P., Bormann, C., Toutain, L., and R. Cragie,
	"6LoWPAN Routing Header", draft-ietf-roll-routing-		"6LoWPAN Routing Header", draft-ietf-roll-routing-
	dispatch-00 (work in progress), March 2016.		dispatch-02 (work in progress), October 2016.
	[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet		[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
	Control Message Protocol (ICMPv6) for the Internet		Control Message Protocol (ICMPv6) for the Internet
	Protocol Version 6 (IPv6) Specification", RFC 4443,		Protocol Version 6 (IPv6) Specification", RFC 4443,
	DOI 10.17487/RFC4443, March 2006,		DOI 10.17487/RFC4443, March 2006,
	<http://www.rfc-editor.org/info/rfc4443>.		<http://www.rfc-editor.org/info/rfc4443>.
	[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)",
End of changes. 8 change blocks.
	11 lines changed or deleted		19 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/