< draft-thubert-6lo-bier-dispatch-02.txt		draft-thubert-6lo-bier-dispatch-03.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: July 28, 2017 Ecole Polytechnique		Expires: January 25, 2018 Ecole Polytechnique
	H. Jiang		H. Jiang
	G. Texier		G. Texier
	Telecom Bretagne		Telecom Bretagne
	January 24, 2017		July 24, 2017
	A 6loRH for BitStrings		A 6loRH for BitStrings
	draft-thubert-6lo-bier-dispatch-02		draft-thubert-6lo-bier-dispatch-03
	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 July 28, 2017.		This Internet-Draft will expire on January 25, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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
	skipping to change at page 2, line 13 ¶		skipping to change at page 2, line 13 ¶
	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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 3
	4. The BIER-6LoRH encoding . . . . . . . . . . . . . . . . . . . 4		4. The BIER-6LoRH encoding . . . . . . . . . . . . . . . . . . . 4
	4.1. The Bit-by-bit BitStrings . . . . . . . . . . . . . . . . 5		4.1. The Bit-by-bit BitStrings . . . . . . . . . . . . . . . . 4
	4.2. Bloom Filters . . . . . . . . . . . . . . . . . . . . . . 5		4.2. Bloom Filters . . . . . . . . . . . . . . . . . . . . . . 5
	4.3. Types of BIER-6LoRH header . . . . . . . . . . . . . . . 5		4.3. Types of BIER-6LoRH header . . . . . . . . . . . . . . . 5
	5. Implementation Status . . . . . . . . . . . . . . . . . . . . 6		5. Implementation Status . . . . . . . . . . . . . . . . . . . . 6
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 7		6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7		8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	9.1. Normative References . . . . . . . . . . . . . . . . . . 7		9.1. Normative References . . . . . . . . . . . . . . . . . . 7
	9.2. Informative References . . . . . . . . . . . . . . . . . 8		9.2. Informative References . . . . . . . . . . . . . . . . . 8
	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 (6LoRH) [RFC8025]		The 6LoWPAN Routing Header (6LoRH) [RFC8025] [RFC8138] is such a
	[I-D.ietf-roll-routing-dispatch] is such a technique, that extends		technique, that extends the 6lo adaptation layer framework [RFC4944],
	the 6lo adaptation layer framework [RFC4944], [RFC6282] so as to		[RFC6282] so as to carry routing information for Route-over use
	carry routing information for Route-over use cases. The original		cases. The original specification includes the formats necessary for
	specification includes the formats necessary for RPL such as the		RPL such as the Source Route Header (SRH) and is intended to be
	Source Route Header (SRH) and is intended to be extended for		extended for additional routing 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 44 ¶		skipping to change at page 3, line 42 ¶
	3. Applicability		3. Applicability
	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 context of "the Deterministic Networking (DetNet)
	[I-D.ietf-detnet-architecture] (DetNet), the DetNet Data Plane		Architecture" [I-D.ietf-detnet-architecture] ), the "BIER-TE-based
	Protocol and Solution Alternatives [I-D.ietf-detnet-dp-alt] document		OAM, Replication and Elimination"
	details how BIER-TE can be leveraged to activate the Deterministic		[I-D.thubert-bier-replication-elimination] document details how BIER-
	Networking Replication and Elimination functions in a manner that is		TE can be leveraged to activate the Deterministic Networking
	abstract to the data plane forwarding information. An adjacency,		Replication and Elimination functions in a manner that is abstract to
	which is represented by a bit in the BIER header, can be mapped in		the data plane forwarding information. An adjacency, which is
	the data plane to an Ethernet hop, a Label Switched Path, or it may		represented by a bit in the BIER header, can be mapped in the data
	correspond to a loose or a strict IPv6 Source Routed Path.		plane to an Ethernet hop, a Label Switched Path, or it may 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
	destination. A Track is indicated in a packet by a Source or		destination. A Track is indicated in a packet by a Source or
	Destination IPv6 Address and a RPL Local Instance. The RPL Instance		Destination IPv6 Address and a RPL Local Instance. The RPL Instance
	is carried in an IPv6 packet as part of the RPL Packet Information		is carried in an IPv6 packet as part of the RPL Packet Information
	(RPI), and a bit in the RPI indicates whether the Instance is Local		(RPI), and a bit in the RPI indicates whether the Instance is Local
	to the Source or the Destination Address. The RPI can be compressed		to the Source or the Destination Address. The RPI can be compressed
	as a RPI 6LoRH header (RPI-6LoRH) as described in		as a RPI 6LoRH header (RPI-6LoRH) as described in [RFC8138].
	[I-D.ietf-roll-routing-dispatch].
	The 6TiSCH requirements for DetNet [I-D.thubert-6tisch-4detnet]		The 6TiSCH requirements for DetNet [I-D.thubert-6tisch-4detnet]
	indicate that a 6TiSCH Track may leverage replication and elimination		indicate that a 6TiSCH Track may leverage replication and elimination
	as defined in DetNet. This specification enables this behavior as		as defined in DetNet. This specification enables this behavior as
	follows: if a BIER-6LoRH is positioned right after a RPI-6LoRH, then		follows: if a BIER-6LoRH is positioned right after a RPI-6LoRH, then
	the BitString in the BIER-6LoRH applies to the context of the Track		the BitString in the BIER-6LoRH applies to the context of the Track
	indicated by the source or destination address of the packet and the		indicated by the source or destination address of the packet and the
	local Instance ID associated to the source or destination of the		local Instance ID associated to the source or destination of the
	packet.		packet.
	skipping to change at page 7, line 7 ¶		skipping to change at page 7, line 7 ¶
	github: https://github.com/zach-b/openwsn-fw/tree/BIER		github: https://github.com/zach-b/openwsn-fw/tree/BIER
	OpenWSN firmware: https://openwsn.atlassian.net/wiki/pages/		OpenWSN firmware: https://openwsn.atlassian.net/wiki/pages/
	viewpage.action?pageId=688187		viewpage.action?pageId=688187
	OpenMote hardware: http://www.openmote.com/		OpenMote hardware: http://www.openmote.com/
	6. Security Considerations		6. Security Considerations
	The security considerations of [I-D.ietf-roll-routing-dispatch]		The security considerations of [RFC8138] apply.
	apply.
	7. IANA Considerations		7. IANA Considerations
	This document extends the IANA registry created by		This document extends the IANA registry created by [RFC8138] for the
	[I-D.ietf-roll-routing-dispatch] for the 6LoWPAN Routing Header Type,		6LoWPAN Routing Header Type, and adds the following values:
	and adds the following values:
	15..24 : BIER-6LoRH [RFCthis]		15..24 : BIER-6LoRH [RFCthis]
	8. Acknowledgments		8. Acknowledgments
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[I-D.ietf-roll-routing-dispatch]
	Thubert, P., Bormann, C., Toutain, L., and R. Cragie,
	"6LoWPAN Routing Header", draft-ietf-roll-routing-
	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>.
	[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>.
	[RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and
	Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January
	2014, <http://www.rfc-editor.org/info/rfc7102>.
	[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for
	Constrained-Node Networks", RFC 7228,
	DOI 10.17487/RFC7228, May 2014,
	<http://www.rfc-editor.org/info/rfc7228>.
	[RFC8025] Thubert, P., Ed. and R. Cragie, "IPv6 over Low-Power		[RFC8025] Thubert, P., Ed. and R. Cragie, "IPv6 over Low-Power
	Wireless Personal Area Network (6LoWPAN) Paging Dispatch",		Wireless Personal Area Network (6LoWPAN) Paging Dispatch",
	RFC 8025, DOI 10.17487/RFC8025, November 2016,		RFC 8025, DOI 10.17487/RFC8025, November 2016,
	<http://www.rfc-editor.org/info/rfc8025>.		<http://www.rfc-editor.org/info/rfc8025>.
			[RFC8138] Thubert, P., Ed., Bormann, C., Toutain, L., and R. Cragie,
			"IPv6 over Low-Power Wireless Personal Area Network
			(6LoWPAN) Routing Header", RFC 8138, DOI 10.17487/RFC8138,
			April 2017, <http://www.rfc-editor.org/info/rfc8138>.
	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-02 (work in progress), October		draft-bergmann-bier-ccast-02 (work in progress), October
	2016.		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-04 (work in progress), July		draft-eckert-bier-te-arch-05 (work in progress), June
	2016.		2017.
	[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-11 (work
	in progress), June 2016.		in progress), January 2017.
	[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-05 (work in		Replication", draft-ietf-bier-architecture-07 (work in
	progress), October 2016.		progress), June 2017.
	[I-D.ietf-detnet-architecture]		[I-D.ietf-detnet-architecture]
	Finn, N. and P. Thubert, "Deterministic Networking		Finn, N., Thubert, P., Varga, B., and J. Farkas,
	Architecture", draft-ietf-detnet-architecture-00 (work in		"Deterministic Networking Architecture", draft-ietf-
	progress), September 2016.		detnet-architecture-02 (work in progress), June 2017.
	[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.
			[I-D.thubert-bier-replication-elimination]
			Thubert, P., Brodard, Z., and H. Jiang, "BIER-TE-based
			OAM, Replication and Elimination", draft-thubert-bier-
			replication-elimination-00 (work in progress), September
			2016.
	[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>.
			[RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and
			Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January
			2014, <http://www.rfc-editor.org/info/rfc7102>.
			[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for
			Constrained-Node Networks", RFC 7228,
			DOI 10.17487/RFC7228, May 2014,
			<http://www.rfc-editor.org/info/rfc7228>.
	Authors' Addresses		Authors' Addresses
	Pascal Thubert (editor)		Pascal Thubert (editor)
	Cisco Systems		Cisco Systems
	Village d'Entreprises Green Side		Village d'Entreprises Green Side
	400, Avenue de Roumanille		400, Avenue de Roumanille
	Batiment T3		Batiment T3
	Biot - Sophia Antipolis 06410		Biot - Sophia Antipolis 06410
	FRANCE		FRANCE
End of changes. 19 change blocks.
	57 lines changed or deleted		54 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/