< draft-ietf-detnet-mpls-10.txt		draft-ietf-detnet-mpls-11.txt >
	DetNet B. Varga, Ed.		DetNet B. Varga, Ed.
	Internet-Draft J. Farkas		Internet-Draft J. Farkas
	Intended status: Standards Track Ericsson		Intended status: Standards Track Ericsson
	Expires: January 27, 2021 L. Berger		Expires: February 17, 2021 L. Berger
	LabN Consulting, L.L.C.		LabN Consulting, L.L.C.
	A. Malis		A. Malis
	Malis Consulting		Malis Consulting
	S. Bryant		S. Bryant
	Futurewei Technologies		Futurewei Technologies
	J. Korhonen		J. Korhonen
	July 26, 2020		August 16, 2020
	DetNet Data Plane: MPLS		DetNet Data Plane: MPLS
	draft-ietf-detnet-mpls-10		draft-ietf-detnet-mpls-11
	Abstract		Abstract
	This document specifies the Deterministic Networking data plane when		This document specifies the Deterministic Networking data plane when
	operating over an MPLS Packet Switched Network. It leverages		operating over an MPLS Packet Switched Network. It leverages
	existing pseudowire (PW) encapsulations and MPLS Traffic Engineering		existing pseudowire (PW) encapsulations and MPLS Traffic Engineering
	encapsulations and mechanisms. This document builds on the DetNet		encapsulations and mechanisms. This document builds on the DetNet
	Architecture and Data Plane Framework.		Architecture and Data Plane Framework.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	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 27, 2021.		This Internet-Draft will expire on February 17, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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
	skipping to change at page 3, line 18 ¶		skipping to change at page 3, line 18 ¶
	a network to DetNet flows. DetNet provides these flows with		a network to DetNet flows. DetNet provides these flows with
	extremely low packet loss rates and assured maximum end-to-end		extremely low packet loss rates and assured maximum end-to-end
	delivery latency. General background and concepts of DetNet can be		delivery latency. General background and concepts of DetNet can be
	found in [RFC8655].		found in [RFC8655].
	The DetNet Architecture models the DetNet related data plane		The DetNet Architecture models the DetNet related data plane
	functions decomposed into two sub-layers: a service sub-layer and a		functions decomposed into two sub-layers: a service sub-layer and a
	forwarding sub-layer. The service sub-layer is used to provide		forwarding sub-layer. The service sub-layer is used to provide
	DetNet service functions such as protection and reordering. The		DetNet service functions such as protection and reordering. The
	forwarding sub-layer is used to provide forwarding assurance (low		forwarding sub-layer is used to provide forwarding assurance (low
	loss, assured latency, and limited reordering).		loss, assured latency, and limited out-of-order delivery).
	This document specifies the DetNet data plane operation and the on-		This document specifies the DetNet data plane operation and the on-
	wire encapsulation of DetNet flows over an MPLS-based Packet Switched		wire encapsulation of DetNet flows over an MPLS-based Packet Switched
	Network (PSN) using the service reference model. MPLS encapsulation		Network (PSN) using the service reference model. MPLS encapsulation
	already provides a solid foundation of building blocks to enable the		already provides a solid foundation of building blocks to enable the
	DetNet service and forwarding sub-layer functions. MPLS encapsulated		DetNet service and forwarding sub-layer functions. MPLS encapsulated
	DetNet can be carried over a variety of different network		DetNet can be carried over a variety of different network
	technologies that can provide the DetNet required level of service.		technologies that can provide the DetNet required level of service.
	However, the specific details of how DetNet MPLS is carried over		However, the specific details of how DetNet MPLS is carried over
	different network technologies is out of scope of this document.		different network technologies is out of scope of this document.
	skipping to change at page 8, line 5 ¶		skipping to change at page 8, line 5 ¶
	network. The 'X' in the end systems, and relay nodes represents		network. The 'X' in the end systems, and relay nodes represents
	potential DetNet compound flow packet replication and elimination		potential DetNet compound flow packet replication and elimination
	points. In this example, service protection is supported utilizing		points. In this example, service protection is supported utilizing
	at least two DetNet member flows and TE LSPs. For a unidirectional		at least two DetNet member flows and TE LSPs. For a unidirectional
	flow, R1 supports PRF and R3 supports PEF and POF. Note that the		flow, R1 supports PRF and R3 supports PEF and POF. Note that the
	relay nodes may change the underlying forwarding sub-layer, for		relay nodes may change the underlying forwarding sub-layer, for
	example tunneling MPLS over IEEE 802.1 TSN		example tunneling MPLS over IEEE 802.1 TSN
	[I-D.ietf-detnet-mpls-over-tsn], or simply over interconnect network		[I-D.ietf-detnet-mpls-over-tsn], or simply over interconnect network
	links.		links.
	DetNet DetNet		DetNet DetNet
	MPLS Service Transit Transit Service MPLS		DetNet Service Transit Transit Service DetNet
	DetNet | |<-Tnl->| |<-Tnl->| | DetNet		MPLS | |<-Tnl->| |<-Tnl->| | MPLS
	End | V 1 V V 2 V | End		End | V 1 V V 2 V | End
	System | +--------+ +--------+ +--------+ | System		System | +--------+ +--------+ +--------+ | System
	+---+ | | R1 |=======| R2 |=======| R3 | | +---+		+---+ | | R1 |=======| R2 |=======| R3 | | +---+
	| X...DFa...|._X_....|..DF1..|.__ ___.|..DF3..|...._X_.|.DFa..|.X |		| X...DFa...|._X_....|..DF1..|.__ ___.|..DF3..|...._X_.|.DFa..|.X |
	|CE1|========| \ | | X | | / |======|CE2|		|CE1|========| \ | | X | | / |======|CE2|
	| | | | \_.|..DF2..|._/ \__.|..DF4..|._/ | | | |		| | | | \_.|..DF2..|._/ \__.|..DF4..|._/ | | | |
	+---+ | |=======| |=======| | +---+		+---+ | |=======| |=======| | +---+
	^ +--------+ +--------+ +--------+ ^		^ +--------+ +--------+ +--------+ ^
	| Relay Node Relay Node Relay Node |		| Relay Node Relay Node Relay Node |
	| (S-PE) (S-PE) (S-PE) |		| (S-PE) (S-PE) (S-PE) |
	| |		| |
	|<---------------------- DetNet MPLS --------------------->|		|<---------------------- DetNet MPLS --------------------->|
	skipping to change at page 13, line 18 ¶		skipping to change at page 13, line 18 ¶
	encapsulations for consistency but there is no hard requirement in		encapsulations for consistency but there is no hard requirement in
	this regard.		this regard.
	4.2.2.1. Packet Replication Function Processing		4.2.2.1. Packet Replication Function Processing
	The Packet Replication Function (PRF) function MAY be supported by an		The Packet Replication Function (PRF) function MAY be supported by an
	implementation for outgoing DetNet flows. The use of the PRF for a		implementation for outgoing DetNet flows. The use of the PRF for a
	particular DetNet service MUST be provisioned via configuration,		particular DetNet service MUST be provisioned via configuration,
	e.g., via the controller plane described in		e.g., via the controller plane described in
	[I-D.ietf-detnet-data-plane-framework]. When replication is		[I-D.ietf-detnet-data-plane-framework]. When replication is
	configure, the same app-flow data will be sent over multiple outgoing		configured, the same app-flow data will be sent over multiple
	DetNet member flows using forwarding sub-layer LSPs. An S-Label		outgoing DetNet member flows using forwarding sub-layer LSPs. An
	value MUST be configured per outgoing member flow. The same d-CW		S-Label value MUST be configured per outgoing member flow. The same
	field value MUST be used on all outgoing member flows for each		d-CW field value MUST be used on all outgoing member flows for each
	replicated MPLS packet.		replicated MPLS packet.
	4.2.2.2. Packet Elimination Function Processing		4.2.2.2. Packet Elimination Function Processing
	Implementations MAY support the Packet Elimination Function (PEF) for		Implementations MAY support the Packet Elimination Function (PEF) for
	received DetNet MPLS flows. When supported, use of the PEF for a		received DetNet MPLS flows. When supported, use of the PEF for a
	particular DetNet service MUST be provisioned via configuration,		particular DetNet service MUST be provisioned via configuration,
	e.g., via the controller plane described in		e.g., via the controller plane described in
	[I-D.ietf-detnet-data-plane-framework].		[I-D.ietf-detnet-data-plane-framework].
	skipping to change at page 13, line 45 ¶		skipping to change at page 13, line 45 ¶
	implementation MUST track the sequence number contained in received		implementation MUST track the sequence number contained in received
	d-CWs and MUST ensure that duplicate (replicated) instances of a		d-CWs and MUST ensure that duplicate (replicated) instances of a
	particular sequence number are discarded. The specific mechanisms		particular sequence number are discarded. The specific mechanisms
	used for an implementation to identify which received packets are		used for an implementation to identify which received packets are
	duplicates and which are new is an implementation choice. Note that		duplicates and which are new is an implementation choice. Note that
	per Section 4.2.1 the sequence number field length may be 16 or 28		per Section 4.2.1 the sequence number field length may be 16 or 28
	bits, and the field value can wrap. PEF MUST NOT be used with DetNet		bits, and the field value can wrap. PEF MUST NOT be used with DetNet
	flows configured with a d-CW sequence number field length of 0 bits.		flows configured with a d-CW sequence number field length of 0 bits.
	Note that an implementation MAY wish to constrain the maximum number		Note that an implementation MAY wish to constrain the maximum number
	sequence numbers that are tracked, on platform-wide or per flow		of sequence numbers that are tracked, on platform-wide or per flow
	basis. Some implementations MAY support the provisioning of the		basis. Some implementations MAY support the provisioning of the
	maximum number sequence numbers that are tracked number on either a		maximum number of sequence numbers that are tracked on either a
	platform-wide or per flow basis.		platform-wide or per flow basis.
	4.2.2.3. Packet Ordering Function Processing		4.2.2.3. Packet Ordering Function Processing
	A function that is related to in-order delivery is the Packet		A function that is related to in-order delivery is the Packet
	Ordering Function (POF). Implementations MAY support POF. When		Ordering Function (POF). Implementations MAY support POF. When
	supported, use of the POF for a particular DetNet service MUST be		supported, use of the POF for a particular DetNet service MUST be
	provisioned via configuration, e.g., via the controller plane		provisioned via configuration, e.g., via the controller plane
	described by [I-D.ietf-detnet-data-plane-framework]. Implementations		described by [I-D.ietf-detnet-data-plane-framework]. Implementations
	MAY required that PEF and POF be used in combination. There is no		MAY required that PEF and POF be used in combination. There is no
	skipping to change at page 21, line 7 ¶		skipping to change at page 21, line 7 ¶
	2, by IEEE 802.1p priority code point (PCP).		2, by IEEE 802.1p priority code point (PCP).
	CoS for DetNet flows carried in PWs and MPLS is provided using the		CoS for DetNet flows carried in PWs and MPLS is provided using the
	existing MPLS Differentiated Services (DiffServ) architecture		existing MPLS Differentiated Services (DiffServ) architecture
	[RFC3270]. Both E-LSP and L-LSP MPLS DiffServ modes MAY be used to		[RFC3270]. Both E-LSP and L-LSP MPLS DiffServ modes MAY be used to
	support DetNet flows. The Traffic Class field (formerly the EXP		support DetNet flows. The Traffic Class field (formerly the EXP
	field) of an MPLS label follows the definition of [RFC5462] and		field) of an MPLS label follows the definition of [RFC5462] and
	[RFC3270]. The Uniform, Pipe, and Short Pipe DiffServ tunneling and		[RFC3270]. The Uniform, Pipe, and Short Pipe DiffServ tunneling and
	TTL processing models are described in [RFC3270] and [RFC3443] and		TTL processing models are described in [RFC3270] and [RFC3443] and
	MAY be used for MPLS LSPs supporting DetNet flows. MPLS ECN MAY also		MAY be used for MPLS LSPs supporting DetNet flows. MPLS Explicit
	be used as defined in ECN [RFC5129] and updated by [RFC5462].		Congestion Notification (ECN) MAY also be used as defined in ECN
			[RFC5129] and updated by [RFC5462].
	4.6.2. Quality of Service		4.6.2. Quality of Service
	In addition to explicit routes, and packet replication and		In addition to explicit routes, and packet replication and
	elimination, described in Section 4 above, DetNet provides zero		elimination, described in Section 4 above, DetNet provides zero
	congestion loss and bounded latency and jitter. As described in		congestion loss and bounded latency and jitter. As described in
	[RFC8655], there are different mechanisms that maybe used separately		[RFC8655], there are different mechanisms that maybe used separately
	or in combination to deliver a zero congestion loss service. This		or in combination to deliver a zero congestion loss service. This
	includes Quality of Service (QoS) mechanisms at the MPLS layer, that		includes Quality of Service (QoS) mechanisms at the MPLS layer, that
	may be combined with the mechanisms defined by the underlying network		may be combined with the mechanisms defined by the underlying network
	skipping to change at page 28, line 31 ¶		skipping to change at page 28, line 31 ¶
	[I-D.ietf-detnet-mpls-over-tsn]		[I-D.ietf-detnet-mpls-over-tsn]
	Varga, B., Farkas, J., Malis, A., and S. Bryant, "DetNet		Varga, B., Farkas, J., Malis, A., and S. Bryant, "DetNet
	Data Plane: MPLS over IEEE 802.1 Time Sensitive Networking		Data Plane: MPLS over IEEE 802.1 Time Sensitive Networking
	(TSN)", draft-ietf-detnet-mpls-over-tsn-03 (work in		(TSN)", draft-ietf-detnet-mpls-over-tsn-03 (work in
	progress), June 2020.		progress), June 2020.
	[I-D.ietf-detnet-security]		[I-D.ietf-detnet-security]
	Mizrahi, T. and E. Grossman, "Deterministic Networking		Mizrahi, T. and E. Grossman, "Deterministic Networking
	(DetNet) Security Considerations", draft-ietf-detnet-		(DetNet) Security Considerations", draft-ietf-detnet-
	security-10 (work in progress), May 2020.		security-11 (work in progress), August 2020.
	[I-D.ietf-detnet-yang]		[I-D.ietf-detnet-yang]
	Geng, X., Chen, M., Ryoo, Y., Fedyk, D., Li, Z., and R.		Geng, X., Chen, M., Ryoo, Y., Fedyk, D., Li, Z., and R.
	Rahman, "Deterministic Networking (DetNet) Configuration		Rahman, "Deterministic Networking (DetNet) Configuration
	YANG Model", draft-ietf-detnet-yang-07 (work in progress),		YANG Model", draft-ietf-detnet-yang-07 (work in progress),
	July 2020.		July 2020.
	[IEEE802.1AE-2018]		[IEEE802.1AE-2018]
	IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC		IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC
	Security (MACsec)", 2018,		Security (MACsec)", 2018,
End of changes. 11 change blocks.
	19 lines changed or deleted		20 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/