Diff: draft-ietf-detnet-mpls-05.txt - draft-ietf-detnet-mpls-06.txt

	< draft-ietf-detnet-mpls-05.txt	draft-ietf-detnet-mpls-06.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: August 6, 2020 L. Berger	Expires: October 25, 2020 L. Berger
	D. Fedyk
	LabN Consulting, L.L.C.	LabN Consulting, L.L.C.
	A. Malis	A. Malis

	Independent	Malis Consulting
	S. Bryant	S. Bryant
	Futurewei Technologies	Futurewei Technologies
	J. Korhonen	J. Korhonen

	February 3, 2020	April 23, 2020

	DetNet Data Plane: MPLS	DetNet Data Plane: MPLS

	draft-ietf-detnet-mpls-05	draft-ietf-detnet-mpls-06

	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 38 ¶
	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 August 6, 2020.	This Internet-Draft will expire on October 25, 2020.

	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 2, line 43 ¶	skipping to change at page 2, line 42 ¶
	4.6. Forwarding Sub-Layer Considerations . . . . . . . . . . . 20	4.6. Forwarding Sub-Layer Considerations . . . . . . . . . . . 20
	4.6.1. Class of Service . . . . . . . . . . . . . . . . . . 20	4.6.1. Class of Service . . . . . . . . . . . . . . . . . . 20
	4.6.2. Quality of Service . . . . . . . . . . . . . . . . . 20	4.6.2. Quality of Service . . . . . . . . . . . . . . . . . 20
	5. Management and Control Information Summary . . . . . . . . . 21	5. Management and Control Information Summary . . . . . . . . . 21
	5.1. Service Sub-Layer Information Summary . . . . . . . . . . 22	5.1. Service Sub-Layer Information Summary . . . . . . . . . . 22
	5.1.1. Service Aggregation Information Summary . . . . . . . 23	5.1.1. Service Aggregation Information Summary . . . . . . . 23
	5.2. Forwarding Sub-Layer Information Summary . . . . . . . . 23	5.2. Forwarding Sub-Layer Information Summary . . . . . . . . 23
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 24	6. Security Considerations . . . . . . . . . . . . . . . . . . . 24
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25

	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25	9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 25
	9.1. Normative References . . . . . . . . . . . . . . . . . . 25	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
	9.2. Informative References . . . . . . . . . . . . . . . . . 27	10.1. Normative References . . . . . . . . . . . . . . . . . . 25
		10.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 [RFC8655].	General background and concepts of DetNet can be found in [RFC8655].

	The DetNet Architecture models the DetNet related data plane	The DetNet Architecture models the DetNet related data plane

	skipping to change at page 10, line 49 ¶	skipping to change at page 10, line 49 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

	Figure 5: DetNet Control Word	Figure 5: DetNet Control Word

	(bits 0 to 3)	(bits 0 to 3)

	Per [RFC4385], MUST be set to zero (0).	Per [RFC4385], MUST be set to zero (0).

	Sequence Number (bits 4 to 31)	Sequence Number (bits 4 to 31)


	An unsigned value implementing the DetNet sequence number.	An unsigned value implementing the DetNet sequence number. The
		sequence number space is a circular one.

	A separate sequence number space MUST be maintained by the node that	A separate sequence number space MUST be maintained by the node that
	adds the d-CW for each DetNet app-flow. The following sequence	adds the d-CW for each DetNet app-flow. The following sequence
	number field lengths MUST be supported:	number field lengths MUST be supported:

	0 bits	0 bits

	16 bits	16 bits

	28 bits	28 bits

	skipping to change at page 24, line 22 ¶	skipping to change at page 24, line 22 ¶
	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

	General security considerations are described in [RFC8655].	General security considerations are described in [RFC8655].
	Additionally, security considerations and a threat analysis are	Additionally, security considerations and a threat analysis are
	described in [I-D.ietf-detnet-security]. This section considers	described in [I-D.ietf-detnet-security]. This section considers

	exclusively security considerations which are specific to the DetNet	security considerations which are specific to the DetNet MPLS data
	MPLS data plane.	plane. The considerations raised related to MPLS networks in general
		in [RFC5920] are equally applicable to the the DetNet 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 24, line 52 ¶	skipping to change at page 25, line 5 ¶
	per-flow basis, which may provide controller plane attackers with	per-flow basis, which may provide controller plane attackers with
	additional information about the data flows (when compared to	additional information about the data flows (when compared to
	controller planes that do not include per-flow identification). This	controller planes that do not include per-flow identification). This
	is an inherent property of DetNet which has security implications	is an inherent property of DetNet which has security implications
	that should be considered when determining if DetNet is a suitable	that should be considered when determining if DetNet is a suitable
	technology for any given use case.	technology for any given use case.

	To provide uninterrupted availability of the DetNet service,	To provide uninterrupted availability of the DetNet service,
	provisions can be made against DOS attacks and delay attacks. To	provisions can be made against DOS attacks and delay attacks. To
	protect against DOS attacks, excess traffic due to malicious or	protect against DOS attacks, excess traffic due to malicious or

	malfunctioning devices can be prevented or mitigated, for example	malfunctioning devices is prevented or mitigated through the use of
	through the use of existing mechanism such as policing and shaping	existing mechanisms, for example by policing and shaping incoming
	applied at the input of a DetNet domain. To prevent DetNet packets	traffic. To prevent DetNet packets from being delayed by an entity
	from being delayed by an entity external to a DetNet domain, DetNet	external to a DetNet domain, DetNet technology definition can allow
	technology definition can allow for the mitigation of Man-In-The-	for the mitigation of Man-In-The-Middle attacks, for example through
	Middle attacks, for example through use of authentication and	use of authentication and authorization of devices within the DetNet
	authorization of devices within the DetNet domain.	domain.

	7. IANA Considerations	7. IANA Considerations

	This document makes no IANA requests.	This document makes no IANA requests.

	8. Acknowledgements	8. Acknowledgements

	The authors wish to thank Pat Thaler, Norman Finn, Loa Anderson,	The authors wish to thank Pat Thaler, Norman Finn, Loa Anderson,
	David Black, Rodney Cummings, Ethan Grossman, Tal Mizrahi, David	David Black, Rodney Cummings, Ethan Grossman, Tal Mizrahi, David
	Mozes, Craig Gunther, George Swallow, Yuanlong Jiang and Carlos J.	Mozes, Craig Gunther, George Swallow, Yuanlong Jiang and Carlos J.
	Bernardos for their various contributions to this work.	Bernardos for their various contributions to this work.


	9. References	9. Contributors


	9.1. Normative References	RFC7322 limits the number of authors listed on the front page of a
		draft to a maximum of 5. The editor wishes to thank and acknowledge
		the follow author for contributing text to this draft.

		Don Fedyk
		LabN Consulting, L.L.C.
		Email: dfedyk@labn.net

		10. References

		10.1. Normative References

	[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,
	<https://www.rfc-editor.org/info/rfc2119>.	<https://www.rfc-editor.org/info/rfc2119>.

	[RFC2211] Wroclawski, J., "Specification of the Controlled-Load	[RFC2211] Wroclawski, J., "Specification of the Controlled-Load
	Network Element Service", RFC 2211, DOI 10.17487/RFC2211,	Network Element Service", RFC 2211, DOI 10.17487/RFC2211,
	September 1997, <https://www.rfc-editor.org/info/rfc2211>.	September 1997, <https://www.rfc-editor.org/info/rfc2211>.


	skipping to change at page 27, line 14 ¶	skipping to change at page 27, line 23 ¶

	[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>.

	[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,	[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
	"Deterministic Networking Architecture", RFC 8655,	"Deterministic Networking Architecture", RFC 8655,
	DOI 10.17487/RFC8655, October 2019,	DOI 10.17487/RFC8655, October 2019,
	<https://www.rfc-editor.org/info/rfc8655>.	<https://www.rfc-editor.org/info/rfc8655>.


	9.2. Informative References	10.2. Informative References

	[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., Malis, A., and S.
	Bryant, S., and J. Korhonen, "DetNet Data Plane	Bryant, "DetNet Data Plane Framework", draft-ietf-detnet-
	Framework", draft-ietf-detnet-data-plane-framework-03	data-plane-framework-04 (work in progress), February 2020.
	(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",	and S. Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-
	draft-ietf-detnet-ip-04 (work in progress), November 2019.	ip-05 (work in progress), February 2020.

	[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., Berger, L., Fedyk, D., Malis, A., Bryant, S.,
	Bryant, S., and J. Korhonen, "DetNet Data Plane: IP over	and J. Korhonen, "DetNet Data Plane: IP over MPLS", draft-
	MPLS", draft-ietf-detnet-ip-over-mpls-04 (work in	ietf-detnet-ip-over-mpls-05 (work in progress), February
	progress), November 2019.	2020.

	[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-01 (work in	(TSN)", draft-ietf-detnet-mpls-over-tsn-02 (work in
	progress), October 2019.	progress), March 2020.

	[I-D.ietf-detnet-security]	[I-D.ietf-detnet-security]

	Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell,	Mizrahi, T. and E. Grossman, "Deterministic Networking
	J., Austad, H., and N. Finn, "Deterministic Networking
	(DetNet) Security Considerations", draft-ietf-detnet-	(DetNet) Security Considerations", draft-ietf-detnet-

	security-07 (work in progress), January 2020.	security-09 (work in progress), March 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,
	<https://ieeexplore.ieee.org/document/8585421>.	<https://ieeexplore.ieee.org/document/8585421>.

	[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.	[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
	Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1	Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
	Functional Specification", RFC 2205, DOI 10.17487/RFC2205,	Functional Specification", RFC 2205, DOI 10.17487/RFC2205,
	September 1997, <https://www.rfc-editor.org/info/rfc2205>.	September 1997, <https://www.rfc-editor.org/info/rfc2205>.

	skipping to change at page 29, line 5 ¶	skipping to change at page 29, line 10 ¶
	[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation	[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
	Element (PCE) Communication Protocol (PCEP)", RFC 5440,	Element (PCE) Communication Protocol (PCEP)", RFC 5440,
	DOI 10.17487/RFC5440, March 2009,	DOI 10.17487/RFC5440, March 2009,
	<https://www.rfc-editor.org/info/rfc5440>.	<https://www.rfc-editor.org/info/rfc5440>.

	[RFC5586] Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed.,	[RFC5586] Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed.,
	"MPLS Generic Associated Channel", RFC 5586,	"MPLS Generic Associated Channel", RFC 5586,
	DOI 10.17487/RFC5586, June 2009,	DOI 10.17487/RFC5586, June 2009,
	<https://www.rfc-editor.org/info/rfc5586>.	<https://www.rfc-editor.org/info/rfc5586>.


		[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
		Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010,
		<https://www.rfc-editor.org/info/rfc5920>.

	[RFC5921] Bocci, M., Ed., Bryant, S., Ed., Frost, D., Ed., Levrau,	[RFC5921] Bocci, M., Ed., Bryant, S., Ed., Frost, D., Ed., Levrau,
	L., and L. Berger, "A Framework for MPLS in Transport	L., and L. Berger, "A Framework for MPLS in Transport
	Networks", RFC 5921, DOI 10.17487/RFC5921, July 2010,	Networks", RFC 5921, DOI 10.17487/RFC5921, July 2010,
	<https://www.rfc-editor.org/info/rfc5921>.	<https://www.rfc-editor.org/info/rfc5921>.

	[RFC6003] Papadimitriou, D., "Ethernet Traffic Parameters",	[RFC6003] Papadimitriou, D., "Ethernet Traffic Parameters",
	RFC 6003, DOI 10.17487/RFC6003, October 2010,	RFC 6003, DOI 10.17487/RFC6003, October 2010,
	<https://www.rfc-editor.org/info/rfc6003>.	<https://www.rfc-editor.org/info/rfc6003>.

	[RFC6073] Martini, L., Metz, C., Nadeau, T., Bocci, M., and M.	[RFC6073] Martini, L., Metz, C., Nadeau, T., Bocci, M., and M.

	skipping to change at page 29, line 38 ¶	skipping to change at page 30, line 4 ¶
	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>.

	[RFC8660] Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S.,	[RFC8660] Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S.,
	Decraene, B., Litkowski, S., and R. Shakir, "Segment	Decraene, B., Litkowski, S., and R. Shakir, "Segment
	Routing with the MPLS Data Plane", RFC 8660,	Routing with the MPLS Data Plane", RFC 8660,
	DOI 10.17487/RFC8660, December 2019,	DOI 10.17487/RFC8660, December 2019,
	<https://www.rfc-editor.org/info/rfc8660>.	<https://www.rfc-editor.org/info/rfc8660>.

	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


	Janos Farkas	Janos Farkas
	Ericsson	Ericsson
	Magyar Tudosok krt. 11.	Magyar Tudosok krt. 11.
	Budapest 1117	Budapest 1117
	Hungary	Hungary

	Email: janos.farkas@ericsson.com	Email: janos.farkas@ericsson.com

	Lou Berger	Lou Berger
	LabN Consulting, L.L.C.	LabN Consulting, L.L.C.

	Email: lberger@labn.net	Email: lberger@labn.net


	Don Fedyk
	LabN Consulting, L.L.C.

	Email: dfedyk@labn.net

	Andrew G. Malis	Andrew G. Malis

	Independent	Malis Consulting

	Email: agmalis@gmail.com	Email: agmalis@gmail.com

	Stewart Bryant	Stewart Bryant
	Futurewei Technologies	Futurewei Technologies

	Email: stewart.bryant@gmail.com	Email: stewart.bryant@gmail.com

	Jouni Korhonen	Jouni Korhonen


End of changes. 23 change blocks.
	44 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/