< draft-ietf-detnet-mpls-03.txt		draft-ietf-detnet-mpls-04.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: April 29, 2020 L. Berger		Expires: May 24, 2020 L. Berger
	D. Fedyk		D. Fedyk
	LabN Consulting, L.L.C.		LabN Consulting, L.L.C.
	A. Malis		A. Malis
	Independent		Independent
	S. Bryant		S. Bryant
	Futurewei Technologies		Futurewei Technologies
	J. Korhonen		J. Korhonen
	October 27, 2019		November 21, 2019
	DetNet Data Plane: MPLS		DetNet Data Plane: MPLS
	draft-ietf-detnet-mpls-03		draft-ietf-detnet-mpls-04
	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 Networks.		operating over an MPLS Packet Switched Networks.
	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
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 April 29, 2020.		This Internet-Draft will expire on May 24, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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 10 ¶		skipping to change at page 3, line 10 ¶
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
	9.1. Normative References . . . . . . . . . . . . . . . . . . 25		9.1. Normative References . . . . . . . . . . . . . . . . . . 25
	9.2. Informative References . . . . . . . . . . . . . . . . . 27		9.2. Informative References . . . . . . . . . . . . . . . . . 27
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
	1. Introduction		1. Introduction
	Deterministic Networking (DetNet) is a service that can be offered by		Deterministic Networking (DetNet) is a service that can be offered by
	a network to DetNet flows. DetNet provides these flows extremely low		a network to DetNet flows. DetNet provides these flows extremely low
	packet loss rates and assured maximum end-to-end delivery latency.		packet loss rates and assured maximum end-to-end delivery latency.
	General background and concepts of DetNet can be found in		General background and concepts of DetNet can be found in [RFC8655].
	[I-D.ietf-detnet-architecture].
	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 reordering).
	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
	skipping to change at page 3, line 47 ¶		skipping to change at page 3, line 46 ¶
	Background information common to all data planes for DetNet can be		Background information common to all data planes for DetNet can be
	found in the DetNet Data Plane Framework		found in the DetNet Data Plane Framework
	[I-D.ietf-detnet-data-plane-framework].		[I-D.ietf-detnet-data-plane-framework].
	2. Terminology		2. Terminology
	2.1. Terms Used in This Document		2.1. Terms Used in This Document
	This document uses the terminology established in the DetNet		This document uses the terminology established in the DetNet
	architecture [I-D.ietf-detnet-architecture] and the the DetNet Data		architecture [RFC8655] and the the DetNet Data Plane Framework
	Plane Framework [I-D.ietf-detnet-data-plane-framework]. The reader		[I-D.ietf-detnet-data-plane-framework]. The reader is assumed to be
	is assumed to be familiar with these documents and any terminology		familiar with these documents and any terminology defined therein.
	defined therein.
	The following terminology is introduced in this document:		The following terminology is introduced in this document:
	F-Label A Detnet "forwarding" label that identifies the LSP		F-Label A Detnet "forwarding" label that identifies the LSP
	used to forward a DetNet flow across an MPLS PSN, e.g.,		used to forward a DetNet flow across an MPLS PSN, e.g.,
	a hop-by-hop label used between label switching routers		a hop-by-hop label used between label switching routers
	(LSR).		(LSR).
	S-Label A DetNet "service" label that is used between DetNet		S-Label A DetNet "service" label that is used between DetNet
	nodes that implement also the DetNet service sub-layer		nodes that implement also the DetNet service sub-layer
	skipping to change at page 20, line 42 ¶		skipping to change at page 20, line 42 ¶
	[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 ECN MAY also
	be used as defined in ECN [RFC5129] and updated by [RFC5462].		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
	[I-D.ietf-detnet-architecture], there are different mechanisms that		[RFC8655], there are different mechanisms that maybe used separately
	maybe used separately or in combination to deliver a zero congestion		or in combination to deliver a zero congestion loss service. This
	loss service. This includes Quality of Service (QoS) mechanisms at		includes Quality of Service (QoS) mechanisms at the MPLS layer, that
	the MPLS layer, that may be combined with the mechanisms defined by		may be combined with the mechanisms defined by the underlying network
	the underlying network layer such as 802.1TSN.		layer such as 802.1TSN.
	Quality of Service (QoS) mechanisms for flow specific traffic		Quality of Service (QoS) mechanisms for flow specific traffic
	treatment typically includes a guarantee/agreement for the service,		treatment typically includes a guarantee/agreement for the service,
	and allocation of resources to support the service. Example QoS		and allocation of resources to support the service. Example QoS
	mechanisms include discrete resource allocation, admission control,		mechanisms include discrete resource allocation, admission control,
	flow identification and isolation, and sometimes path control,		flow identification and isolation, and sometimes path control,
	traffic protection, shaping, policing and remarking. Example		traffic protection, shaping, policing and remarking. Example
	protocols that support QoS control include Resource ReSerVation		protocols that support QoS control include Resource ReSerVation
	Protocol (RSVP) [RFC2205] (RSVP) and RSVP-TE [RFC3209] and [RFC3473].		Protocol (RSVP) [RFC2205] (RSVP) and RSVP-TE [RFC3209] and [RFC3473].
	The existing MPLS mechanisms defined to support CoS [RFC3270] can		The existing MPLS mechanisms defined to support CoS [RFC3270] can
	skipping to change at page 24, line 12 ¶		skipping to change at page 24, line 12 ¶
	It is the responsibility of the DetNet controller plane to properly		It is the responsibility of the DetNet controller plane to properly
	provision both flow identification information and the flow specific		provision both flow identification information and the flow specific
	resources needed to provided the traffic treatment needed to meet		resources needed to provided the traffic treatment needed to meet
	each flow's service requirements. This applies for aggregated and		each flow's service requirements. This applies for aggregated and
	individual flows.		individual flows.
	6. Security Considerations		6. Security Considerations
	Security considerations for DetNet are described in detail in		Security considerations for DetNet are described in detail in
	[I-D.ietf-detnet-security]. General security considerations are		[I-D.ietf-detnet-security]. General security considerations are
	described in [I-D.ietf-detnet-architecture]. This section considers		described in [RFC8655]. This section considers exclusively security
	exclusively security considerations which are specific to the DetNet		considerations which are specific to the DetNet MPLS data plane.
	MPLS data plane.
	Security aspects which are unique to DetNet are those whose aim is to		Security aspects which are unique to DetNet are those whose aim is to
	provide the specific quality of service aspects of DetNet, which are		provide the specific quality of service aspects of DetNet, which are
	primarily to deliver data flows with extremely low packet loss rates		primarily to deliver data flows with extremely low packet loss rates
	and bounded end-to-end delivery latency.		and bounded end-to-end delivery latency.
	The primary considerations for the data plane is to maintain		The primary considerations for the data plane is to maintain
	integrity of data and delivery of the associated DetNet service		integrity of data and delivery of the associated DetNet service
	traversing the DetNet network. Application flows can be protected		traversing the DetNet network. Application flows can be protected
	through whatever means is provided by the underlying technology. For		through whatever means is provided by the underlying technology. For
	skipping to change at page 27, line 7 ¶		skipping to change at page 27, line 7 ¶
	(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic		(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic
	Class" Field", RFC 5462, DOI 10.17487/RFC5462, February		Class" Field", RFC 5462, DOI 10.17487/RFC5462, February
	2009, <https://www.rfc-editor.org/info/rfc5462>.		2009, <https://www.rfc-editor.org/info/rfc5462>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	9.2. Informative References		9.2. Informative References
	[I-D.ietf-detnet-architecture]
	Finn, N., Thubert, P., Varga, B., and J. Farkas,
	"Deterministic Networking Architecture", draft-ietf-
	detnet-architecture-13 (work in progress), May 2019.
	[I-D.ietf-detnet-data-plane-framework]		[I-D.ietf-detnet-data-plane-framework]
	Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,		Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
	Bryant, S., and J. Korhonen, "DetNet Data Plane		Bryant, S., and J. Korhonen, "DetNet Data Plane
	Framework", draft-ietf-detnet-data-plane-framework-02		Framework", draft-ietf-detnet-data-plane-framework-03
	(work in progress), September 2019.		(work in progress), October 2019.
	[I-D.ietf-detnet-ip]		[I-D.ietf-detnet-ip]
	Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,		Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
	Bryant, S., and J. Korhonen, "DetNet Data Plane: IP",		Bryant, S., and J. Korhonen, "DetNet Data Plane: IP",
	draft-ietf-detnet-ip-01 (work in progress), July 2019.		draft-ietf-detnet-ip-03 (work in progress), October 2019.
	[I-D.ietf-detnet-ip-over-mpls]		[I-D.ietf-detnet-ip-over-mpls]
	Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,		Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
	Bryant, S., and J. Korhonen, "DetNet Data Plane: IP over		Bryant, S., and J. Korhonen, "DetNet Data Plane: IP over
	MPLS", draft-ietf-detnet-ip-over-mpls-01 (work in		MPLS", draft-ietf-detnet-ip-over-mpls-03 (work in
	progress), July 2019.		progress), October 2019.
	[I-D.ietf-detnet-mpls-over-tsn]		[I-D.ietf-detnet-mpls-over-tsn]
	Varga, B., Farkas, J., Malis, A., Bryant, S., and J.		Varga, B., Farkas, J., Malis, A., and S. Bryant, "DetNet
	Korhonen, "DetNet Data Plane: MPLS over IEEE 802.1 Time		Data Plane: MPLS over IEEE 802.1 Time Sensitive Networking
	Sensitive Networking (TSN)", draft-ietf-detnet-mpls-over-		(TSN)", draft-ietf-detnet-mpls-over-tsn-01 (work in
	tsn-00 (work in progress), May 2019.		progress), October 2019.
	[I-D.ietf-detnet-security]		[I-D.ietf-detnet-security]
	Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell,		Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell,
	J., Austad, H., Stanton, K., and N. Finn, "Deterministic		J., Austad, H., and N. Finn, "Deterministic Networking
	Networking (DetNet) Security Considerations", draft-ietf-		(DetNet) Security Considerations", draft-ietf-detnet-
	detnet-security-05 (work in progress), August 2019.		security-06 (work in progress), November 2019.
	[I-D.ietf-spring-segment-routing-mpls]		[I-D.ietf-spring-segment-routing-mpls]
	Bashandy, A., Filsfils, C., Previdi, S., Decraene, B.,		Bashandy, A., Filsfils, C., Previdi, S., Decraene, B.,
	Litkowski, S., and R. Shakir, "Segment Routing with MPLS		Litkowski, S., and R. Shakir, "Segment Routing with MPLS
	data plane", draft-ietf-spring-segment-routing-mpls-22		data plane", draft-ietf-spring-segment-routing-mpls-22
	(work in progress), May 2019.		(work in progress), May 2019.
	[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,
	skipping to change at page 29, line 31 ¶		skipping to change at page 29, line 26 ¶
	RFC 6790, DOI 10.17487/RFC6790, November 2012,		RFC 6790, DOI 10.17487/RFC6790, November 2012,
	<https://www.rfc-editor.org/info/rfc6790>.		<https://www.rfc-editor.org/info/rfc6790>.
	[RFC8306] Zhao, Q., Dhody, D., Ed., Palleti, R., and D. King,		[RFC8306] Zhao, Q., Dhody, D., Ed., Palleti, R., and D. King,
	"Extensions to the Path Computation Element Communication		"Extensions to the Path Computation Element Communication
	Protocol (PCEP) for Point-to-Multipoint Traffic		Protocol (PCEP) for Point-to-Multipoint Traffic
	Engineering Label Switched Paths", RFC 8306,		Engineering Label Switched Paths", RFC 8306,
	DOI 10.17487/RFC8306, November 2017,		DOI 10.17487/RFC8306, November 2017,
	<https://www.rfc-editor.org/info/rfc8306>.		<https://www.rfc-editor.org/info/rfc8306>.
			[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
			"Deterministic Networking Architecture", RFC 8655,
			DOI 10.17487/RFC8655, October 2019,
			<https://www.rfc-editor.org/info/rfc8655>.
	Authors' Addresses		Authors' Addresses
	Balazs Varga (editor)		Balazs Varga (editor)
	Ericsson		Ericsson
	Magyar Tudosok krt. 11.		Magyar Tudosok krt. 11.
	Budapest 1117		Budapest 1117
	Hungary		Hungary
	Email: balazs.a.varga@ericsson.com		Email: balazs.a.varga@ericsson.com
End of changes. 15 change blocks.
	35 lines changed or deleted		32 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/