< draft-ietf-detnet-mpls-over-udp-ip-05.txt		draft-ietf-detnet-mpls-over-udp-ip-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: November 7, 2020 L. Berger
	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
	February 3, 2020		May 6, 2020
	DetNet Data Plane: MPLS over UDP/IP		DetNet Data Plane: MPLS over UDP/IP
	draft-ietf-detnet-mpls-over-udp-ip-05		draft-ietf-detnet-mpls-over-udp-ip-06
	Abstract		Abstract
	This document specifies the MPLS Deterministic Networking data plane		This document specifies the MPLS Deterministic Networking data plane
	operation and encapsulation over an IP network. The approach is		operation and encapsulation over an IP network. The approach is
	modeled on the operation of MPLS and over UDP/IP packet switched		modeled on the operation of MPLS and over UDP/IP packet switched
	networks.		networks.
	Status of This Memo		Status of This Memo
	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 August 6, 2020.		This Internet-Draft will expire on November 7, 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 22 ¶		skipping to change at page 2, line 22 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3		2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3
	2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3		2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
	2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4		2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4
	3. DetNet MPLS Operation over DetNet		3. DetNet MPLS Operation over DetNet
	IP PSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4		IP PSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
	4. DetNet Data Plane Procedures . . . . . . . . . . . . . . . . 5		4. DetNet Data Plane Procedures . . . . . . . . . . . . . . . . 5
	5. Management and Control Information Summary . . . . . . . . . 6		5. Management and Control Information Summary . . . . . . . . . 6
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 6		6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
	9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7		9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	10.1. Normative References . . . . . . . . . . . . . . . . . . 7		10.1. Normative References . . . . . . . . . . . . . . . . . . 7
	10.2. Informative References . . . . . . . . . . . . . . . . . 7		10.2. Informative References . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
	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].
	This document specifies use of the MPLS DetNet encapsulation over an		This document specifies use of the MPLS DetNet encapsulation over an
	skipping to change at page 6, line 7 ¶		skipping to change at page 6, line 7 ¶
	This includes QoS related traffic treatment.		This includes QoS related traffic treatment.
	To support the receive processing defined in this document, an		To support the receive processing defined in this document, an
	implementation MUST also support the provisioning of received UDP and		implementation MUST also support the provisioning of received UDP and
	IP header information. The provisioned information MUST be used to		IP header information. The provisioned information MUST be used to
	identify incoming app-flows based on the combination of S-Label and		identify incoming app-flows based on the combination of S-Label and
	incoming encapsulation header information. Normal receive processing		incoming encapsulation header information. Normal receive processing
	as defined in [I-D.ietf-detnet-mpls], including PEF and POF, can then		as defined in [I-D.ietf-detnet-mpls], including PEF and POF, can then
	take place.		take place.
			As specified in [RFC7510]: "MPLS-in-UDP MUST NOT be used over the
			general Internet, or over non-cooperating network operators, to carry
			traffic that is not congestion controlled."
	5. Management and Control Information Summary		5. Management and Control Information Summary
	The following summarizes the set of information that is needed to		The following summarizes the set of information that is needed to
	configure DetNet MPLS over UDP/IP:		configure DetNet MPLS over UDP/IP:
	o Label information (A-labels, S-labels and F-labels) to be mapped		o Label information (A-labels, S-labels and F-labels) to be mapped
	to UDP/IP flow. Note that for example, a single S-Label can map		to UDP/IP flow. Note that for example, a single S-Label can map
	to multiple sets of UDP/IP information when PREOF is used.		to multiple sets of UDP/IP information when PREOF is used.
	o IPv4 or IPv6 source address field.		o IPv4 or IPv6 source address field.
	skipping to change at page 6, line 39 ¶		skipping to change at page 6, line 43 ¶
	plane.		plane.
	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 provide the traffic treatment needed to meet each		resources needed to provide the traffic treatment needed to meet each
	flow's service requirements. This applies for aggregated and		flow's service requirements. This applies for aggregated and
	individual flows.		individual flows.
	6. Security Considerations		6. Security Considerations
	The security considerations of DetNet in general are discussed in		The solution defined in this document reuses mechanisms specified in
	[RFC8655] and [I-D.ietf-detnet-security]. MPLS and IP specific		other documents, and the security considerations in those documents
	security considerations are described in [I-D.ietf-detnet-mpls] and		apply equally to this document. Notably [RFC7510], as this document
	[I-D.ietf-detnet-ip]. This draft does not have additional security		is primarily an application of MPLS-in-UDP. Additionally, the
	considerations.		security considerations of DetNet in general are discussed in
			[RFC8655] and [I-D.ietf-detnet-security]. Finally,MPLS and IP
			specific security considerations are described in
			[I-D.ietf-detnet-mpls] and [I-D.ietf-detnet-ip]. This draft does not
			have additional security considerations.
	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.
	skipping to change at page 7, line 24 ¶		skipping to change at page 7, line 28 ¶
	This document is derived from an earlier draft that was edited by		This document is derived from an earlier draft that was edited by
	Jouni Korhonen (jouni.nospam@gmail.com) and as such, he contributed		Jouni Korhonen (jouni.nospam@gmail.com) and as such, he contributed
	to and authored text in this document.		to and authored text in this document.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[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-mpls]		[I-D.ietf-detnet-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: MPLS",		Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS",
	draft-ietf-detnet-mpls-04 (work in progress), November		draft-ietf-detnet-mpls-05 (work in progress), February
	2019.		2020.
	[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>.
	[RFC7510] Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black,		[RFC7510] Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black,
	"Encapsulating MPLS in UDP", RFC 7510,		"Encapsulating MPLS in UDP", RFC 7510,
	DOI 10.17487/RFC7510, April 2015,		DOI 10.17487/RFC7510, April 2015,
	<https://www.rfc-editor.org/info/rfc7510>.		<https://www.rfc-editor.org/info/rfc7510>.
	skipping to change at page 8, line 12 ¶		skipping to change at page 8, line 14 ¶
	10.2. Informative References		10.2. Informative References
	[I-D.ietf-6man-segment-routing-header]		[I-D.ietf-6man-segment-routing-header]
	Filsfils, C., Dukes, D., Previdi, S., Leddy, J.,		Filsfils, C., Dukes, D., Previdi, S., Leddy, J.,
	Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header		Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header
	(SRH)", draft-ietf-6man-segment-routing-header-26 (work in		(SRH)", draft-ietf-6man-segment-routing-header-26 (work in
	progress), October 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. 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.
	[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>.
	Authors' Addresses		Authors' Addresses
	Balazs Varga (editor)		Balazs Varga (editor)
	Ericsson		Ericsson
	skipping to change at page 8, line 46 ¶		skipping to change at page 8, line 47 ¶
	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
	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
End of changes. 14 change blocks.
	20 lines changed or deleted		27 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/