draft-ietf-detnet-ip-over-tsn-01.txt		draft-ietf-detnet-ip-over-tsn-02.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 A. Malis		Expires: September 7, 2020 A. Malis
	Independent		Independent
	S. Bryant		S. Bryant
	Futurewei Technologies		Futurewei Technologies
	October 27, 2019		March 6, 2020
	DetNet Data Plane: IP over IEEE 802.1 Time Sensitive Networking (TSN)		DetNet Data Plane: IP over IEEE 802.1 Time Sensitive Networking (TSN)
	draft-ietf-detnet-ip-over-tsn-01		draft-ietf-detnet-ip-over-tsn-02
	Abstract		Abstract
	This document specifies the Deterministic Networking IP data plane		This document specifies the Deterministic Networking IP data plane
	when operating over a TSN sub-network.		when operating over a TSN sub-network.
	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 35 ¶		skipping to change at page 1, line 35 ¶
	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 September 7, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 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
	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 22 ¶		skipping to change at page 2, line 22 ¶
	2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3		2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
	2.3. Requirements Language . . . . . . . . . . . . . . . . . . 3		2.3. Requirements Language . . . . . . . . . . . . . . . . . . 3
	3. DetNet IP Data Plane Overview . . . . . . . . . . . . . . . . 3		3. DetNet IP Data Plane Overview . . . . . . . . . . . . . . . . 3
	4. DetNet IP Flows over an IEEE 802.1 TSN sub-network . . . . 5		4. DetNet IP Flows over an IEEE 802.1 TSN sub-network . . . . 5
	4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 6		4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 6
	4.2. TSN requirements of IP DetNet nodes . . . . . . . . . . . 6		4.2. TSN requirements of IP DetNet nodes . . . . . . . . . . . 6
	4.3. Service protection within the TSN sub-network . . . . . . 8		4.3. Service protection within the TSN sub-network . . . . . . 8
	4.4. Aggregation during DetNet flow to TSN Stream mapping . . 8		4.4. Aggregation during DetNet flow to TSN Stream mapping . . 8
	5. Management and Control Implications . . . . . . . . . . . . . 8		5. Management and Control Implications . . . . . . . . . . . . . 8
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 9		6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	9.1. Normative references . . . . . . . . . . . . . . . . . . 10		9.1. Normative references . . . . . . . . . . . . . . . . . . 10
	9.2. Informative references . . . . . . . . . . . . . . . . . 10		9.2. Informative references . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
	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 the DetNet		General background and concepts of DetNet can be found in the DetNet
	Architecture [I-D.ietf-detnet-architecture].		Architecture [RFC8655].
	[I-D.ietf-detnet-ip] specifies the DetNet data plane operation for IP		[I-D.ietf-detnet-ip] specifies the DetNet data plane operation for IP
	hosts and routers that provide DetNet service to IP encapsulated		hosts and routers that provide DetNet service to IP encapsulated
	data. This document focuses on the scenario where DetNet IP nodes		data. This document focuses on the scenario where DetNet IP nodes
	are interconnected by a TSN sub-network.		are interconnected by a TSN sub-network.
	The DetNet Architecture decomposes the DetNet related data plane		The DetNet Architecture decomposes the DetNet related data plane
	functions into two sub-layers: a service sub-layer and a forwarding		functions into two sub-layers: a service sub-layer and a forwarding
	sub-layer. The service sub-layer is used to provide DetNet service		sub-layer. The service sub-layer is used to provide DetNet service
	protection and reordering. The forwarding sub-layer is used to		protection and reordering. The forwarding sub-layer is used to
	provides congestion protection (low loss, assured latency, and		provides congestion protection (low loss, assured latency, and
	limited reordering). As described in [I-D.ietf-detnet-ip] no DetNet		limited reordering). As described in [I-D.ietf-detnet-ip] no DetNet
	specific headers are added to support DetNet IP flows, only the		specific headers are added to support DetNet IP flows, only the
	forwarding sub-layer functions are supported inside the DetNet		forwarding sub-layer functions are supported inside the DetNet
	domain. Service protection can be provided on a per sub-network		domain. Service protection can be provided on a per sub-network
	basis as shown here for the IEEE802.1 TSN sub-network scenario.		basis as shown here for the IEEE802.1 TSN sub-network scenario.
	2. Terminology		2. Terminology
	[Editor's note: Needs clean up.].
	2.1. Terms Used In This Document		2.1. Terms Used In This Document
	This document uses the terminology and concepts established in the		This document uses the terminology and concepts established in the
	DetNet architecture [I-D.ietf-detnet-architecture], and the reader is		DetNet architecture [RFC8655], and the reader is assumed to be
	assumed to be familiar with that document and its terminology.		familiar with that document and its terminology.
	2.2. Abbreviations		2.2. Abbreviations
	The following abbreviations used in this document:		The following abbreviations used in this document:
	DetNet Deterministic Networking.		DetNet Deterministic Networking.
	DF DetNet Flow.		DF DetNet Flow.
			FRER Frame Replication and Elimination for Redundancy (TSN
			function).
	L2 Layer-2.		L2 Layer-2.
	L3 Layer-3.		L3 Layer-3.
	PREOF Packet Replication, Ordering and Elimination Function.		PREOF Packet Replication, Ordering and Elimination Function.
	TSN Time-Sensitive Networking, TSN is a Task Group of the		TSN Time-Sensitive Networking, TSN is a Task Group of the
	IEEE 802.1 Working Group.		IEEE 802.1 Working Group.
	2.3. Requirements Language		2.3. Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	3. DetNet IP Data Plane Overview		3. DetNet IP Data Plane Overview
	[Editor's note: this section and highlights that DetNet IP over
	subnets scenario being the focus in the remaining part of the
	document.].
	[I-D.ietf-detnet-ip] describes how IP is used by DetNet nodes, i.e.,		[I-D.ietf-detnet-ip] describes how IP is used by DetNet nodes, i.e.,
	hosts and routers, to identify DetNet flows and provide a DetNet		hosts and routers, to identify DetNet flows and provide a DetNet
	service. From a data plane perspective, an end-to-end IP model is		service. From a data plane perspective, an end-to-end IP model is
	followed. DetNet uses "6-tuple" based flow identification, where		followed. DetNet uses "6-tuple" based flow identification, where
	"6-tuple" refers to information carried in IP and higher layer		"6-tuple" refers to information carried in IP and higher layer
	protocol headers.		protocol headers.
	DetNet flow aggregation may be enabled via the use of wildcards,		DetNet flow aggregation may be enabled via the use of wildcards,
	masks, prefixes and ranges. IP tunnels may also be used to support		masks, prefixes and ranges. IP tunnels may also be used to support
	flow aggregation. In these cases, it is expected that DetNet aware		flow aggregation. In these cases, it is expected that DetNet aware
	skipping to change at page 5, line 14 ¶		skipping to change at page 5, line 10 ¶
	DetNet routers ensure that detnet service requirements are met per		DetNet routers ensure that detnet service requirements are met per
	hop by allocating local resources, both receive and transmit, and by		hop by allocating local resources, both receive and transmit, and by
	mapping the service requirements of each flow to appropriate sub-		mapping the service requirements of each flow to appropriate sub-
	network mechanisms. Such mappings are sub-network technology		network mechanisms. Such mappings are sub-network technology
	specific. The mapping of DetNet IP flows to TSN streams and TSN		specific. The mapping of DetNet IP flows to TSN streams and TSN
	protection mechanisms are covered in Section 4.		protection mechanisms are covered in Section 4.
	4. DetNet IP Flows over an IEEE 802.1 TSN sub-network		4. DetNet IP Flows over an IEEE 802.1 TSN sub-network
	[Authors note: how do we handle control protocols such as ICMP,
	IPsec, etc.? If such protocols are part of the DetNet flow they can
	be identified by the Mask-and-match Stream identification function of
	P802.1CBdb.]
	This section covers how DetNet IP flows operate over an IEEE 802.1		This section covers how DetNet IP flows operate over an IEEE 802.1
	TSN sub-network. Figure 2 illustrates such a scenario, where two IP		TSN sub-network. Figure 2 illustrates such a scenario, where two IP
	(DetNet) nodes are interconnected by a TSN sub-network. Node-1 is		(DetNet) nodes are interconnected by a TSN sub-network. Node-1 is
	single homed and Node-2 is dual-homed to the TSN sub-network.		single homed and Node-2 is dual-homed to the TSN sub-network.
	IP (DetNet) IP (DetNet)		IP (DetNet) IP (DetNet)
	Node-1 Node-2		Node-1 Node-2
	............ ............		............ ............
	<--: Service :-- DetNet flow ---: Service :-->		<--: Service :-- DetNet flow ---: Service :-->
	skipping to change at page 8, line 39 ¶		skipping to change at page 8, line 31 ¶
	Implementations of this document SHALL use management and control		Implementations of this document SHALL use management and control
	information to map a DetNet flow to a TSN Stream. N:1 mapping		information to map a DetNet flow to a TSN Stream. N:1 mapping
	(aggregating DetNet flows in a single TSN Stream) SHALL be supported.		(aggregating DetNet flows in a single TSN Stream) SHALL be supported.
	The management or control function that provisions flow mapping SHALL		The management or control function that provisions flow mapping SHALL
	ensure that adequate resources are allocated and configured to		ensure that adequate resources are allocated and configured to
	provide proper service requirements of the mapped flows.		provide proper service requirements of the mapped flows.
	5. Management and Control Implications		5. Management and Control Implications
	[Editor's note: This section covers management/control plane related
	implications of creation, mapping, removal of TSN Stream IDs, their
	related parameters and, when needed, the configuration of FRER.]
	DetNet flow and TSN Stream mapping related information are required		DetNet flow and TSN Stream mapping related information are required
	only for TSN-aware IP (DetNet) nodes. From the Data Plane		only for TSN-aware IP (DetNet) nodes. From the Data Plane
	perspective there is no practical difference based on the origin of		perspective there is no practical difference based on the origin of
	flow mapping related information (management plane or control plane).		flow mapping related information (management plane or control plane).
	TSN-aware IP DetNet nodes are member of both the DetNet domain and		TSN-aware IP DetNet nodes are member of both the DetNet domain and
	the TSN sub-network. Within the TSN sub-network the TSN-aware IP		the TSN sub-network. Within the TSN sub-network the TSN-aware IP
	(DetNet) node has a TSN-aware Talker/Listener role, so TSN specific		(DetNet) node has a TSN-aware Talker/Listener role, so TSN specific
	management and control plane functionalities must be implemented.		management and control plane functionalities must be implemented.
	There are many similarities in the management plane techniques used		There are many similarities in the management plane techniques used
	skipping to change at page 9, line 49 ¶		skipping to change at page 9, line 37 ¶
	complicated as they are fully unaware of the sub-network and run		complicated as they are fully unaware of the sub-network and run
	independently.		independently.
	Configuration of TSN specific functions (e.g., FRER) inside the TSN		Configuration of TSN specific functions (e.g., FRER) inside the TSN
	sub-network is a TSN domain specific decision and may not be visible		sub-network is a TSN domain specific decision and may not be visible
	in the DetNet domain.		in the DetNet domain.
	6. Security Considerations		6. Security Considerations
	The security considerations of DetNet in general are discussed in		The security considerations of DetNet in general are discussed in
	[I-D.ietf-detnet-architecture] and [I-D.ietf-detnet-security].		[RFC8655] and [I-D.ietf-detnet-security]. DetNet IP data plane
	DetNet IP data plane specific considerations are summarized in		specific considerations are summarized in [I-D.ietf-detnet-ip].
			Encryption may provided by an underlying sub-net using MACSec
	[I-D.ietf-detnet-ip]. Encryption may provided by an underlying sub-		[IEEE802.1AE-2018] for DetNet IP over TSN flows.
	net using MACSec [IEEE802.1AE-2018] for DetNet IP over TSN flows.
	7. IANA Considerations		7. IANA Considerations
	None.		None.
	8. Acknowledgements		8. Acknowledgements
	The authors wish to thank Norman Finn, Lou Berger, Craig Gunther,		The authors wish to thank Norman Finn, Lou Berger, Craig Gunther,
	Christophe Mangin and Jouni Korhonen for their various contributions		Christophe Mangin and Jouni Korhonen for their various contributions
	to this work.		to this work.
	9. References		9. References
	9.1. Normative references		9.1. Normative references
			[I-D.ietf-detnet-ip]
			Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
			and S. Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-
			ip-05 (work in progress), February 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>.
	[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
	[G.8275.1]
	International Telecommunication Union, "Precision time
	protocol telecom profile for phase/time synchronization
	with full timing support from the network", ITU-T
	G.8275.1/Y.1369.1 G.8275.1, June 2016,
	<https://www.itu.int/rec/T-REC-G.8275.1/en>.
	[G.8275.2]
	International Telecommunication Union, "Precision time
	protocol telecom profile for phase/time synchronization
	with partial timing support from the network", ITU-T
	G.8275.2/Y.1369.2 G.8275.2, June 2016,
	<https://www.itu.int/rec/T-REC-G.8275.2/en>.
	[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-flow-information-model]		[I-D.ietf-detnet-flow-information-model]
	Farkas, J., Varga, B., Cummings, R., Jiang, Y., and D.		Farkas, J., Varga, B., Cummings, R., Jiang, Y., and D.
	Fedyk, "DetNet Flow Information Model", draft-ietf-detnet-		Fedyk, "DetNet Flow Information Model", draft-ietf-detnet-
	flow-information-model-05 (work in progress), September		flow-information-model-07 (work in progress), March 2020.
	2019.
	[I-D.ietf-detnet-ip]
	Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
	Bryant, S., and J. Korhonen, "DetNet Data Plane: IP",
	draft-ietf-detnet-ip-01 (work in progress), July 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-08 (work in progress), February 2020.
	[IEEE1588]
	IEEE, "IEEE 1588 Standard for a Precision Clock
	Synchronization Protocol for Networked Measurement and
	Control Systems Version 2", 2008.
	[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>.
	[IEEE8021CB]		[IEEE8021CB]
	Finn, N., "Draft Standard for Local and metropolitan area		Finn, N., "Draft Standard for Local and metropolitan area
	networks - Seamless Redundancy", IEEE P802.1CB		networks - Seamless Redundancy", IEEE P802.1CB
	/D2.1 P802.1CB, December 2015,		/D2.1 P802.1CB, December 2015,
	skipping to change at page 12, line 5 ¶		skipping to change at page 11, line 11 ¶
	IEEE 802.1, "Standard for Local and metropolitan area		IEEE 802.1, "Standard for Local and metropolitan area
	networks--Bridges and Bridged Networks (IEEE Std 802.1Q-		networks--Bridges and Bridged Networks (IEEE Std 802.1Q-
	2014)", 2014, <http://standards.ieee.org/about/get/>.		2014)", 2014, <http://standards.ieee.org/about/get/>.
	[IEEEP8021CBdb]		[IEEEP8021CBdb]
	Mangin, C., "Extended Stream identification functions",		Mangin, C., "Extended Stream identification functions",
	IEEE P802.1CBdb /D0.2 P802.1CBdb, August 2019,		IEEE P802.1CBdb /D0.2 P802.1CBdb, August 2019,
	<http://www.ieee802.org/1/files/private/cb-drafts/d2/802-		<http://www.ieee802.org/1/files/private/cb-drafts/d2/802-
	1CB-d2-1.pdf>.		1CB-d2-1.pdf>.
			[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. 20 change blocks.
	65 lines changed or deleted		32 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/