< draft-thubert-6lo-bier-dispatch-01.txt		draft-thubert-6lo-bier-dispatch-02.txt >
	6lo P. Thubert, Ed.		6lo P. Thubert, Ed.
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track Z. Brodard		Intended status: Standards Track Z. Brodard
	Expires: December 31, 2016 Ecole Polytechnique		Expires: July 28, 2017 Ecole Polytechnique
	H. Jiang		H. Jiang
	G. Texier		G. Texier
	Telecom Bretagne		Telecom Bretagne
	June 29, 2016		January 24, 2017
	A 6loRH for BitStrings		A 6loRH for BitStrings
	draft-thubert-6lo-bier-dispatch-01		draft-thubert-6lo-bier-dispatch-02
	Abstract		Abstract
	This specification extends the 6LoWPAN Routing Header to signal		This specification extends the 6LoWPAN Routing Header to signal
	BitStrings such as utilized in Bit Index Explicit Replication and its		BitStrings such as utilized in Bit Index Explicit Replication and its
	Traffic Engineering variant.		Traffic Engineering variant.
	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
	skipping to change at page 1, line 36 ¶		skipping to change at page 1, line 36 ¶
	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 December 31, 2016.		This Internet-Draft will expire on July 28, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 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		(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
	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 33 ¶		skipping to change at page 2, line 33 ¶
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	The type of information that needs to be present in a packet inside		The type of information that needs to be present in a packet inside
	the LLN but not outside of the LLN varies with the routing operation,		the LLN but not outside of the LLN varies with the routing operation,
	but there is overall a need for an extensible compression technique		but there is overall a need for an extensible compression technique
	that would simplify the IP-in-IP encapsulation, when needed, and		that would simplify the IP-in-IP encapsulation, when needed, and
	optimally compress existing routing artifacts found in LLNs.		optimally compress existing routing artifacts found in LLNs.
	The 6LoWPAN Routing Header [I-D.ietf-roll-routing-dispatch] (6LoRH)		The 6LoWPAN Routing Header (6LoRH) [RFC8025]
	specification is such a technique, that extends the 6lo adaptation		[I-D.ietf-roll-routing-dispatch] is such a technique, that extends
	layer framework [RFC4944],[RFC6282] so as to carry routing		the 6lo adaptation layer framework [RFC4944], [RFC6282] so as to
	information for Route-over use cases. The original specification		carry routing information for Route-over use cases. The original
	includes the formats necessary for RPL such as the Source Route		specification includes the formats necessary for RPL such as the
	Header (SRH) and is intended to be extended for additional routing		Source Route Header (SRH) and is intended to be extended for
	artifacts.		additional routing artifacts.
	The Bit Index Explicit Replication (BIER), as introduced in the BIER		The Bit Index Explicit Replication (BIER), as introduced in the BIER
	Architecture [I-D.ietf-bier-architecture], can be used as an		Architecture [I-D.ietf-bier-architecture], can be used as an
	alternate artifact to route multicast as well as unicast traffic.		alternate artifact to route multicast as well as unicast traffic.
	The Traffic Engineering for Bit Index Explicit Replication		The Traffic Engineering for Bit Index Explicit Replication
	[I-D.eckert-bier-te-arch] (BIER-TE) adds support for traffic		[I-D.eckert-bier-te-arch] (BIER-TE) adds support for traffic
	engineering by explicit hop-by-hop forwarding and loose hop		engineering by explicit hop-by-hop forwarding and loose hop
	forwarding of packets along a unicast route.		forwarding of packets along a unicast route.
	This specification provides additional formats for the 6LoRH		This specification provides additional formats for the 6LoRH
	skipping to change at page 3, line 45 ¶		skipping to change at page 3, line 45 ¶
	BIER and other bit-indexed methods that would leverage BitStrings		BIER and other bit-indexed methods that would leverage BitStrings
	will generally require additional information in the packet to		will generally require additional information in the packet to
	complement the BitString. For instance, BIER has the concept of a		complement the BitString. For instance, BIER has the concept of a
	BFR-id and an Entropy value in the BIER header. Since those		BFR-id and an Entropy value in the BIER header. Since those
	additional fields depend on the bit-indexed method, they are expected		additional fields depend on the bit-indexed method, they are expected
	to be transported separately from the BitString. This specification		to be transported separately from the BitString. This specification
	concentrates on the BitString alone.		concentrates on the BitString alone.
	Within the scope of Deterministic Networking		Within the scope of Deterministic Networking
	[I-D.finn-detnet-architecture] (DetNet), the DetNet Data Plane		[I-D.ietf-detnet-architecture] (DetNet), the DetNet Data Plane
	Protocol and Solution Alternatives [I-D.dt-detnet-dp-alt] document		Protocol and Solution Alternatives [I-D.ietf-detnet-dp-alt] document
	details how BIER-TE can be leveraged to activate the Deterministic		details how BIER-TE can be leveraged to activate the Deterministic
	Networking Replication and Elimination functions in a manner that is		Networking Replication and Elimination functions in a manner that is
	abstract to the data plane forwarding information. An adjacency,		abstract to the data plane forwarding information. An adjacency,
	which is represented by a bit in the BIER header, can be mapped in		which is represented by a bit in the BIER header, can be mapped in
	the data plane to an Ethernet hop, a Label Switched Path, or it may		the data plane to an Ethernet hop, a Label Switched Path, or it may
	correspond to a loose or a strict IPv6 Source Routed Path.		correspond to a loose or a strict IPv6 Source Routed Path.
	In the context of LLNs, the 6TiSCH Architecture		In the context of LLNs, the 6TiSCH Architecture
	[I-D.ietf-6tisch-architecture] introduces the concept of a Track that		[I-D.ietf-6tisch-architecture] introduces the concept of a Track that
	is a directional traffic-engineered path between a source and a		is a directional traffic-engineered path between a source and a
	skipping to change at page 7, line 27 ¶		skipping to change at page 7, line 27 ¶
	8. Acknowledgments		8. Acknowledgments
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[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-05 (work 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>.
	[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>.		<http://www.rfc-editor.org/info/rfc4944>.
	skipping to change at page 8, line 10 ¶		skipping to change at page 8, line 10 ¶
	[RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and		[RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and
	Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January		Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January
	2014, <http://www.rfc-editor.org/info/rfc7102>.		2014, <http://www.rfc-editor.org/info/rfc7102>.
	[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>.		<http://www.rfc-editor.org/info/rfc7228>.
			[RFC8025] Thubert, P., Ed. and R. Cragie, "IPv6 over Low-Power
			Wireless Personal Area Network (6LoWPAN) Paging Dispatch",
			RFC 8025, DOI 10.17487/RFC8025, November 2016,
			<http://www.rfc-editor.org/info/rfc8025>.
	9.2. Informative References		9.2. Informative References
	[I-D.bergmann-bier-ccast]		[I-D.bergmann-bier-ccast]
	Bergmann, O., Bormann, C., Gerdes, S., and H. Chen,		Bergmann, O., Bormann, C., Gerdes, S., and H. Chen,
	"Constrained-Cast: Source-Routed Multicast for RPL",		"Constrained-Cast: Source-Routed Multicast for RPL",
	draft-bergmann-bier-ccast-01 (work in progress), April		draft-bergmann-bier-ccast-02 (work in progress), October
	2016.		2016.
	[I-D.dt-detnet-dp-alt]
	Korhonen, J., Farkas, J., Mirsky, G., Thubert, P.,
	Zhuangyan, Z., and L. Berger, "DetNet Data Plane Protocol
	and Solution Alternatives", draft-dt-detnet-dp-alt-00
	(work in progress), March 2016.
	[I-D.eckert-bier-te-arch]		[I-D.eckert-bier-te-arch]
	Eckert, T., Cauchie, G., Braun, W., and M. Menth, "Traffic		Eckert, T., Cauchie, G., Braun, W., and M. Menth, "Traffic
	Engineering for Bit Index Explicit Replication BIER-TE",		Engineering for Bit Index Explicit Replication BIER-TE",
	draft-eckert-bier-te-arch-03 (work in progress), March		draft-eckert-bier-te-arch-04 (work in progress), July
	2016.		2016.
	[I-D.finn-detnet-architecture]
	Finn, N., Thubert, P., and M. Teener, "Deterministic
	Networking Architecture", draft-finn-detnet-
	architecture-04 (work in progress), March 2016.
	[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-bier-architecture]		[I-D.ietf-bier-architecture]
	Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and		Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
	S. Aldrin, "Multicast using Bit Index Explicit		S. Aldrin, "Multicast using Bit Index Explicit
	Replication", draft-ietf-bier-architecture-03 (work in		Replication", draft-ietf-bier-architecture-05 (work in
	progress), January 2016.		progress), October 2016.
			[I-D.ietf-detnet-architecture]
			Finn, N. and P. Thubert, "Deterministic Networking
			Architecture", draft-ietf-detnet-architecture-00 (work in
			progress), September 2016.
			[I-D.ietf-detnet-dp-alt]
			Korhonen, J., Farkas, J., Mirsky, G., Thubert, P.,
			Zhuangyan, Z., and L. Berger, "DetNet Data Plane Protocol
			and Solution Alternatives", draft-ietf-detnet-dp-alt-00
			(work in progress), October 2016.
	[I-D.thubert-6tisch-4detnet]		[I-D.thubert-6tisch-4detnet]
	Thubert, P., "6TiSCH requirements for DetNet", draft-		Thubert, P., "6TiSCH requirements for DetNet", draft-
	thubert-6tisch-4detnet-01 (work in progress), June 2015.		thubert-6tisch-4detnet-01 (work in progress), June 2015.
	[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>.		<http://www.rfc-editor.org/info/rfc6282>.
End of changes. 14 change blocks.
	30 lines changed or deleted		35 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/