< draft-thubert-bier-replication-elimination-00.txt		draft-thubert-bier-replication-elimination-01.txt >
	DetNet P. Thubert, Ed.		DetNet P. Thubert, Ed.
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track Z. Brodard		Intended status: Standards Track Z. Brodard
	Expires: March 18, 2017 Ecole Polytechnique		Expires: January 25, 2018 Ecole Polytechnique
	H. Jiang		H. Jiang
	Telecom Bretagne		Telecom Bretagne
	September 14, 2016		July 24, 2017
	BIER-TE-based OAM, Replication and Elimination		BIER-TE-based OAM, Replication and Elimination
	draft-thubert-bier-replication-elimination-00		draft-thubert-bier-replication-elimination-01
	Abstract		Abstract
	This specification leverages Bit Index Explicit Replication - Traffic		This specification leverages Bit Index Explicit Replication - Traffic
	Engineering to control in the data plane the DetNet Replication and		Engineering to control in the data plane the DetNet Replication and
	Elimination activities, and to provide traceability on links where		Elimination activities, and to provide traceability on links where
	replication and loss happen, in a manner that is abstract to the		replication and loss happen, in a manner that is abstract to the
	forwarding information.		forwarding information.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 18, 2017.		This Internet-Draft will expire on January 25, 2018.
	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 29 ¶		skipping to change at page 2, line 29 ¶
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
	10.1. Normative References . . . . . . . . . . . . . . . . . . 9		10.1. Normative References . . . . . . . . . . . . . . . . . . 9
	10.2. Informative References . . . . . . . . . . . . . . . . . 10		10.2. Informative References . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
	1. Introduction		1. Introduction
	Deterministic Networking (DetNet) [I-D.ietf-detnet-problem-statement]		Deterministic Networking (DetNet) [I-D.ietf-detnet-problem-statement]
	provides a capability to carry unicast or multicast data flows for		provides a capability to carry unicast or multicast data flows for
	real-time applications with extremely low data loss rates and known		real-time applications with extremely low data loss rates and known
	upper bound maximum latency [I-D.finn-detnet-architecture].		upper bound maximum latency [I-D.ietf-detnet-architecture].
	DetNet applies to multiple environments where there is a desire to		DetNet applies to multiple environments where there is a desire to
	replace a point to point serial cable or a multidrop bus by a		replace a point to point serial cable or a multidrop bus by a
	switched or routed infrastucture, in order to scale, lower costs, and		switched or routed infrastucture, in order to scale, lower costs, and
	simplify management. One classical use case is found in particular		simplify management. One classical use case is found in particular
	in the context of the convergence of IT with Operational Technology		in the context of the convergence of IT with Operational Technology
	(OT), also referred to as the Industrial Internet. But there are		(OT), also referred to as the Industrial Internet. But there are
	many others use cases [I-D.ietf-detnet-use-cases], for instance in in		many others use cases [I-D.ietf-detnet-use-cases], for instance in in
	professional audio and video, automotive, radio fronthauls, etc..		professional audio and video, automotive, radio fronthauls, etc..
	The DetNet data plane alternatives [I-D.dt-detnet-dp-alt] studies the		The DetNet data plane alternatives [I-D.dt-detnet-dp-alt] studies the
	applicability of existing and emerging dataplane techniques that can		applicability of existing and emerging dataplane techniques that can
	be leveraged to enable DetNet properties in IP networks. One		be leveraged to enable DetNet properties in IP networks. One
	critical feature in the dataplane is traceability, the capability to		critical feature in the dataplane is traceability, the capability to
	control the activity of intermediate nodes on a packet. For		control the activity of intermediate nodes on a packet. For
	instance, if Replication and Elimination is applied to a packet, then		instance, if Replication and Elimination is applied to a packet, then
	it is desirable to determine which node performed a certain copy of		it is desirable to determine which node performed a certain copy of
	that packet that is circulating in the network.		that packet that is circulating in the network.
	Traceability belongs to Operations, Administration, and Maintenance		Traceability belongs to Operations, Administration, and Maintenance
	(OAM), which is the toolset for fault detection and isolation, and		(OAM) which is the toolset for fault detection and isolation, and for
	for performance measurement. An Overview of OAM Tools is available		performance measurement. More can be found on OAM Tools in "An
	at [I-D.ietf-detnet-use-cases].		Overview of Operations, Administration and Maintenance (OAM) Tools"
			[I-D.ietf-opsawg-oam-overview].
	This document proposes a new set to OAM tools based on Bit Indexed		This document proposes a new set to OAM tools based on Bit Indexed
	Explicit Replication [I-D.ietf-bier-architecture] (BIER) and more		Explicit Replication [I-D.ietf-bier-architecture] (BIER) and more
	specifically BIER Traffic Engineering [I-D.eckert-bier-te-arch]		specifically BIER Traffic Engineering [I-D.eckert-bier-te-arch]
	(BIER-TE) to control the process or Replication and Elimination, and		(BIER-TE) to control the process or Replication and Elimination, and
	provide traceability of these operations, in the DetNet dataplane.		provide traceability of these operations, in the DetNet dataplane.
	An adjacency, which is represented by a bit in the BIER header, can		An adjacency, which is represented by a bit in the BIER header, can
	correspond in the dataplane to an Ethernet hop, a Label Switched		correspond in the dataplane to an Ethernet hop, a Label Switched
	Path, or it can correspond to an IPv6 loose or strict source routed		Path, or it can correspond to an IPv6 loose or strict source routed
	path.		path.
	skipping to change at page 9, line 46 ¶		skipping to change at page 9, line 46 ¶
	Zhuangyan Zhuang		Zhuangyan Zhuang
	The authors also like to thank the DetNet chairs Lou Berger and Pat		The authors also like to thank the DetNet chairs Lou Berger and Pat
	Thaler, as well as Thomas Watteyne, 6TiSCH co-chair, for their		Thaler, as well as Thomas Watteyne, 6TiSCH co-chair, for their
	contributions and support to this work.		contributions and support to this work.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[I-D.finn-detnet-architecture]
	Finn, N. and P. Thubert, "Deterministic Networking
	Architecture", draft-finn-detnet-architecture-08 (work in
	progress), August 2016.
	[I-D.ietf-bier-architecture]
	Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
	S. Aldrin, "Multicast using Bit Index Explicit
	Replication", draft-ietf-bier-architecture-04 (work in
	progress), July 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>.
	10.2. Informative References		10.2. Informative References
	[I-D.dt-detnet-dp-alt]		[I-D.dt-detnet-dp-alt]
	Korhonen, J., Farkas, J., Mirsky, G., Thubert, P.,		Korhonen, J., Farkas, J., Mirsky, G., Thubert, P.,
	Zhuangyan, Z., and L. Berger, "DetNet Data Plane Protocol		Zhuangyan, Z., and L. Berger, "DetNet Data Plane Protocol
	and Solution Alternatives", draft-dt-detnet-dp-alt-03		and Solution Alternatives", draft-dt-detnet-dp-alt-04
	(work in progress), August 2016.		(work in progress), September 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-bier-architecture]
	Thubert, P., "An Architecture for IPv6 over the TSCH mode		Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
	of IEEE 802.15.4", draft-ietf-6tisch-architecture-10 (work		S. Aldrin, "Multicast using Bit Index Explicit
	in progress), June 2016.		Replication", draft-ietf-bier-architecture-07 (work in
			progress), June 2017.
			[I-D.ietf-detnet-architecture]
			Finn, N., Thubert, P., Varga, B., and J. Farkas,
			"Deterministic Networking Architecture", draft-ietf-
			detnet-architecture-02 (work in progress), June 2017.
	[I-D.ietf-detnet-problem-statement]		[I-D.ietf-detnet-problem-statement]
	Finn, N. and P. Thubert, "Deterministic Networking Problem		Finn, N. and P. Thubert, "Deterministic Networking Problem
	Statement", draft-ietf-detnet-problem-statement-00 (work		Statement", draft-ietf-detnet-problem-statement-01 (work
	in progress), April 2016.		in progress), September 2016.
	[I-D.ietf-detnet-use-cases]		[I-D.ietf-detnet-use-cases]
	Grossman, E., Gunther, C., Thubert, P., Wetterwald, P.,		Grossman, E., Gunther, C., Thubert, P., Wetterwald, P.,
	Raymond, J., Korhonen, J., Kaneko, Y., Das, S., Zha, Y.,		Raymond, J., Korhonen, J., Kaneko, Y., Das, S., Zha, Y.,
	Varga, B., Farkas, J., Goetz, F., and J. Schmitt,		Varga, B., Farkas, J., Goetz, F., Schmitt, J., Vilajosana,
			X., Mahmoodi, T., Spirou, S., and P. Vizarreta,
	"Deterministic Networking Use Cases", draft-ietf-detnet-		"Deterministic Networking Use Cases", draft-ietf-detnet-
	use-cases-10 (work in progress), July 2016.		use-cases-12 (work in progress), April 2017.
	[I-D.ietf-opsawg-oam-overview]		[I-D.ietf-opsawg-oam-overview]
	Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.		Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.
	Weingarten, "An Overview of Operations, Administration,		Weingarten, "An Overview of Operations, Administration,
	and Maintenance (OAM) Tools", draft-ietf-opsawg-oam-		and Maintenance (OAM) Tools", draft-ietf-opsawg-oam-
	overview-16 (work in progress), March 2014.		overview-16 (work in progress), March 2014.
	[I-D.ietf-spring-segment-routing]		[I-D.ietf-spring-segment-routing]
	Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,		Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
	and R. Shakir, "Segment Routing Architecture", draft-ietf-		and R. Shakir, "Segment Routing Architecture", draft-ietf-
	spring-segment-routing-09 (work in progress), July 2016.		spring-segment-routing-12 (work in progress), June 2017.
	[RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6
	Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
	DOI 10.17487/RFC6282, September 2011,
	<http://www.rfc-editor.org/info/rfc6282>.
	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. 15 change blocks.
	38 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/