< draft-ietf-detnet-ip-over-tsn-05.txt		draft-ietf-detnet-ip-over-tsn-06.txt >
	DetNet B. Varga, Ed.		DetNet B. Varga, Ed.
	Internet-Draft J. Farkas		Internet-Draft J. Farkas
	Intended status: Informational Ericsson		Intended status: Informational Ericsson
	Expires: June 16, 2021 A. Malis		Expires: August 16, 2021 A. Malis
	Malis Consulting		Malis Consulting
	S. Bryant		S. Bryant
	Futurewei Technologies		Futurewei Technologies
	December 13, 2020		February 12, 2021
	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-05		draft-ietf-detnet-ip-over-tsn-06
	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. This document does not define		when operating over a TSN sub-network. This document does not define
	new procedures or processes. Whenever this document makes		new procedures or processes. Whenever this document makes
	requirements statements or recommendations, these are taken from		requirements statements or recommendations, these are taken from
	normative text in the referenced RFCs.		normative text in the referenced RFCs.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 38 ¶		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 June 16, 2021.		This Internet-Draft will expire on August 16, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 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 3, line 12 ¶		skipping to change at page 3, line 12 ¶
	headers are added to support DetNet IP flows, only the forwarding		headers are added to support DetNet IP flows, only the forwarding
	sub-layer functions are supported inside the DetNet domain. Service		sub-layer functions are supported inside the DetNet domain. Service
	protection can be provided on a per sub-network basis as shown here		protection can be provided on a per sub-network basis as shown here
	for the IEEE802.1 TSN sub-network scenario.		for the IEEE802.1 TSN sub-network scenario.
	2. Terminology		2. Terminology
	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 [RFC8655], and the reader is assumed to be		DetNet architecture [RFC8655]. TSN specific terms are defined in the
	familiar with that document and its terminology.		TSN TG of IEEE 802.1 Working Group. The reader is assumed to be
			familiar with these documents and their 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		FRER Frame Replication and Elimination for Redundancy (TSN
	skipping to change at page 5, line 8 ¶		skipping to change at page 5, line 9 ¶
	The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1		The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1
	Working Group have defined (and are defining) a number of amendments		Working Group have defined (and are defining) a number of amendments
	to IEEE 802.1Q [IEEE8021Q] that provide zero congestion loss and		to IEEE 802.1Q [IEEE8021Q] that provide zero congestion loss and
	bounded latency in bridged networks. Furthermore, IEEE 802.1CB		bounded latency in bridged networks. Furthermore, IEEE 802.1CB
	[IEEE8021CB] defines frame replication and elimination functions for		[IEEE8021CB] defines frame replication and elimination functions for
	reliability that should prove both compatible with and useful to		reliability that should prove both compatible with and useful to
	DetNet networks. All these functions have to identify flows that		DetNet networks. All these functions have to identify flows that
	require TSN treatment.		require TSN treatment.
	TSN capabilities of the TSN sub-network are made available for IP		TSN capabilities of the TSN sub-network are made available for IP
	(DetNet) flows via the protocol interworking function desribed in		(DetNet) flows via the protocol interworking function described in
	Annex C.5 of IEEE 802.1CB [IEEE8021CB]. For example, applied on the		Annex C.5 of IEEE 802.1CB [IEEE8021CB]. For example, applied on the
	TSN edge port it can convert an ingress unicast IP (DetNet) flow to		TSN edge port it can convert an ingress unicast IP (DetNet) flow to
	use a specific Layer-2 multicast destination MAC address and a VLAN,		use a specific Layer-2 multicast destination MAC address and a VLAN,
	in order to direct the packet through a specific path inside the		in order to direct the packet through a specific path inside the
	bridged network. A similar interworking function pair at the other		bridged network. A similar interworking function pair at the other
	end of the TSN sub-network would restore the packet to its original		end of the TSN sub-network would restore the packet to its original
	Layer-2 destination MAC address and VLAN.		Layer-2 destination MAC address and VLAN.
	Placement of TSN functions depends on the TSN capabilities of nodes.		Placement of TSN functions depends on the TSN capabilities of nodes.
	IP (DetNet) Nodes may or may not support TSN functions. For a given		IP (DetNet) Nodes may or may not support TSN functions. For a given
	skipping to change at page 10, line 34 ¶		skipping to change at page 10, line 34 ¶
	[RFC8939] Varga, B., Ed., Farkas, J., Berger, L., Fedyk, D., and S.		[RFC8939] Varga, B., Ed., Farkas, J., Berger, L., Fedyk, D., and S.
	Bryant, "Deterministic Networking (DetNet) Data Plane:		Bryant, "Deterministic Networking (DetNet) Data Plane:
	IP", RFC 8939, DOI 10.17487/RFC8939, November 2020,		IP", RFC 8939, DOI 10.17487/RFC8939, November 2020,
	<https://www.rfc-editor.org/info/rfc8939>.		<https://www.rfc-editor.org/info/rfc8939>.
	9.2. Informative references		9.2. Informative references
	[I-D.ietf-detnet-security]		[I-D.ietf-detnet-security]
	Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic		Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic
	Networking (DetNet) Security Considerations", draft-ietf-		Networking (DetNet) Security Considerations", draft-ietf-
	detnet-security-12 (work in progress), October 2020.		detnet-security-13 (work in progress), December 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>.
	[IEEE8021CB]		[IEEE8021CB]
	IEEE 802.1, "Standard for Local and metropolitan area		IEEE 802.1, "Standard for Local and metropolitan area
	networks - Frame Replication and Elimination for		networks - Frame Replication and Elimination for
	Reliability (IEEE Std 802.1CB-2017)", 2017,		Reliability (IEEE Std 802.1CB-2017)", 2017,
End of changes. 8 change blocks.
	9 lines changed or deleted		10 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/