draft-ietf-detnet-ip-over-tsn-05.txt   rfc9023.txt 
DetNet B. Varga, Ed. Internet Engineering Task Force (IETF) B. Varga, Ed.
Internet-Draft J. Farkas Request for Comments: 9023 J. Farkas
Intended status: Informational Ericsson Category: Informational Ericsson
Expires: June 16, 2021 A. Malis ISSN: 2070-1721 A. Malis
Malis Consulting Malis Consulting
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
December 13, 2020 June 2021
DetNet Data Plane: IP over IEEE 802.1 Time Sensitive Networking (TSN) Deterministic Networking (DetNet) Data Plane: IP over IEEE 802.1
draft-ietf-detnet-ip-over-tsn-05 Time-Sensitive Networking (TSN)
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 Time-Sensitive Networking (TSN) sub-network.
new procedures or processes. Whenever this document makes This document does not define new procedures or processes. Whenever
requirements statements or recommendations, these are taken from this document makes statements or recommendations, these are taken
normative text in the referenced RFCs. from normative text in the referenced RFCs.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet
Standard; see Section 2 of RFC 7841.
This Internet-Draft will expire on June 16, 2021. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9023.
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology
2.1. Terms Used In This Document . . . . . . . . . . . . . . . 3 2.1. Terms Used in This Document
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Abbreviations
3. DetNet IP Data Plane Overview . . . . . . . . . . . . . . . . 3 3. DetNet IP Data Plane Overview
4. DetNet IP Flows over an IEEE 802.1 TSN sub-network . . . . 4 4. DetNet IP Flows over an IEEE 802.1 TSN Sub-network
4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 5 4.1. Functions for DetNet Flow to TSN Stream Mapping
4.2. TSN requirements of IP DetNet nodes . . . . . . . . . . . 6 4.2. TSN Requirements of IP DetNet Nodes
4.3. Service protection within the TSN sub-network . . . . . . 7 4.3. Service Protection within the TSN Sub-network
4.4. Aggregation during DetNet flow to TSN Stream mapping . . 7 4.4. Aggregation during DetNet Flow to TSN Stream Mapping
5. Management and Control Implications . . . . . . . . . . . . . 8 5. Management and Control Implications
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 7. IANA Considerations
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 8. References
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8.1. Normative References
9.1. Normative references . . . . . . . . . . . . . . . . . . 10 8.2. Informative References
9.2. Informative references . . . . . . . . . . . . . . . . . 10 Acknowledgements
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses
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 [RFC8655]. Architecture [RFC8655].
[RFC8939] specifies the DetNet data plane operation for IP hosts and [RFC8939] specifies the DetNet data plane operation for IP hosts and
routers that provide DetNet service to IP encapsulated data. This routers that provide DetNet service to IP-encapsulated data. This
document focuses on the scenario where DetNet IP nodes are document focuses on the scenario where DetNet IP nodes are
interconnected by a TSN sub-network. interconnected by a Time-Sensitive Networking (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 provide congestion protection (low loss, assured latency, and limited
limited reordering). As described in [RFC8939] no DetNet specific reordering). As described in [RFC8939], no DetNet-specific headers
headers are added to support DetNet IP flows, only the forwarding are added to support DetNet IP flows. So, only the forwarding sub-
sub-layer functions are supported inside the DetNet domain. Service layer functions can be supported inside the DetNet IP domain.
protection can be provided on a per sub-network basis as shown here Service protection can be provided on a per-sub-network basis as
for the IEEE802.1 TSN sub-network scenario. shown here for the IEEE 802.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 by the
familiar with that document and its terminology. TSN Task Group of the 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 are used in this document:
DetNet Deterministic Networking.
DF DetNet Flow. DetNet Deterministic Networking
FRER Frame Replication and Elimination for Redundancy (TSN FRER Frame Replication and Elimination for Redundancy (TSN
function). function)
L2 Layer-2.
L3 Layer-3. L2 Layer 2
PREOF Packet Replication, Ordering and Elimination Function. L3 Layer 3
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.
3. DetNet IP Data Plane Overview 3. DetNet IP Data Plane Overview
[RFC8939] describes how IP is used by DetNet nodes, i.e., hosts and [RFC8939] describes how IP is used by DetNet nodes, i.e., hosts and
routers, to identify DetNet flows and provide a DetNet service. From routers, to identify DetNet flows and provide a DetNet service. From
a data plane perspective, an end-to-end IP model is followed. DetNet a data plane perspective, an end-to-end IP model is followed. DetNet
uses "6-tuple" based flow identification, where "6-tuple" refers to uses flow identification based on a "6-tuple", where "6-tuple" refers
information carried in IP and higher layer protocol headers. to information carried in IP- and higher-layer protocol headers as
defined in [RFC8939].
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
intermediate nodes will provide DetNet service assurance on the intermediate nodes will provide DetNet service assurance on the
aggregate through resource allocation and congestion control aggregate through resource allocation and congestion control
mechanisms. mechanisms.
Congestion protection, latency control and the resource allocation Congestion protection, latency control, and the resource allocation
(queuing, policing, shaping) are supported using the underlying link (queuing, policing, and shaping) are supported using the underlying
/ sub-net specific mechanisms. Service protections (packet link / sub-net-specific mechanisms. Service protections (packet-
replication and packet elimination functions) are not provided at the replication and packet-elimination functions) are not provided at the
IP DetNet layer end-to-end due the lack of a unified end-to-end IP DetNet layer end to end due to the lack of unified end-to-end
sequencing information that would be available for intermediate sequencing information that would be available for intermediate
nodes. However, such service protection can be provided on a per nodes. However, such service protection can be provided per
underlying L2 link and sub-network basis. underlying L2 link and per sub-network.
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, by both receiving and
mapping the service requirements of each flow to appropriate sub- transmitting, and by mapping the service requirements of each flow to
network mechanisms. Such mappings are sub-network technology appropriate sub-network mechanisms. Such mappings are sub-network
specific. DetNet nodes interconnected by a TSN sub-network are the technology specific. DetNet nodes interconnected by a TSN sub-
primary focus of this document. The mapping of DetNet IP flows to network are the primary focus of this document. The mapping of
TSN streams and TSN protection mechanisms are covered in Section 4. DetNet IP flows to TSN Streams and TSN 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
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 1 illustrates such a scenario, where two IP TSN sub-network. Figure 1 illustrates such a scenario where two IP
(DetNet) nodes are interconnected by a TSN sub-network. Dotted lines (DetNet) nodes are interconnected by a TSN sub-network. Dotted lines
around the Service components of the IP (DetNet) Nodes indicate that around the Service components of the IP (DetNet) nodes indicate that
they are DetNet service aware but do not perform any DetNet service they are DetNet service aware but do not perform any DetNet service
sub-layer function. Node-1 is single homed and Node-2 is dual-homed sub-layer function. Node-1 is single homed and Node-2 is dual homed
to the TSN sub-network. to the TSN sub-network, and they are treated as Talker or Listener
inside the TSN sub-network. Note that from the TSN perspective,
dual-homed characteristics of Talker or Listener nodes are
transparent to the IP Layer.
IP (DetNet) IP (DetNet) IP (DetNet) IP (DetNet)
Node-1 Node-2 Node-1 Node-2
............ ............ ............ ............
<--: Service :-- DetNet flow ---: Service :--> <--: Service :-- DetNet flow ---: Service :-->
+----------+ +----------+ +----------+ +----------+
|Forwarding| |Forwarding| |Forwarding| |Forwarding|
+--------.-+ <-TSN Str-> +-.-----.--+ +--------.-+ <-TSN Str-> +-.-----.--+
\ ,-------. / / \ ,-------. / /
+----[ TSN-Sub ]---+ / +----[ TSN Sub-]---+ /
[ Network ]--------+ [ Network ]--------+
`-------' `-------'
<----------------- DetNet IP -----------------> <----------------- DetNet IP ----------------->
Figure 1: DetNet (DN) Enabled IP Network over a TSN sub-network Figure 1: DetNet-Enabled IP Network over a TSN Sub-network
The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1 At the time of this writing, the Time-Sensitive Networking (TSN) Task
Working Group have defined (and are defining) a number of amendments Group of the IEEE 802.1 Working Group have defined (and are defining)
to IEEE 802.1Q [IEEE8021Q] that provide zero congestion loss and a number of amendments to [IEEE8021Q] that provide zero congestion
bounded latency in bridged networks. Furthermore, IEEE 802.1CB loss and bounded latency in bridged networks. Furthermore,
[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 [IEEE8021CB]. For example, applied on the TSN edge port
TSN edge port it can convert an ingress unicast IP (DetNet) flow to it can convert an ingress unicast IP (DetNet) flow to use a specific
use a specific Layer-2 multicast destination MAC address and a VLAN, L2 multicast destination Media Access Control (MAC) address and a
in order to direct the packet through a specific path inside the VLAN in order to forward the packet through a specific path inside
bridged network. A similar interworking function pair at the other the bridged network. A similar interworking function pair at the
end of the TSN sub-network would restore the packet to its original other end of the TSN sub-network would restore the packet to its
Layer-2 destination MAC address and VLAN. original L2 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
TSN Stream (i.e., a mapped DetNet flow) an IP (DetNet) node is TSN Stream (i.e., a mapped DetNet flow), an IP (DetNet) node is
treated as a Talker or a Listener inside the TSN sub-network. treated as a Talker or a Listener inside the TSN sub-network.
4.1. Functions for DetNet Flow to TSN Stream Mapping 4.1. Functions for DetNet Flow to TSN Stream Mapping
Mapping of a DetNet IP flow to a TSN Stream is provided via the Mapping of a DetNet IP flow to a TSN Stream is provided via the
combination of a passive and an active stream identification function combination of a passive and an active Stream identification function
that operate at the frame level (Layer-2). The passive stream that operate at the frame level (Layer 2). The passive Stream
identification function is used to catch the 6-tuple of a DetNet IP identification function is used to catch the 6-tuple of a DetNet IP
flow and the active stream identification function is used to modify flow, and the active Stream identification function is used to modify
the Ethernet header according to the ID of the mapped TSN Stream. the Ethernet header according to the ID of the mapped TSN Stream.
Clause 6.7 of IEEE 802.1CB [IEEE8021CB] defines an IP Stream Clause 6.7 of [IEEE8021CB] defines an IP Stream identification
identification function that can be used as a passive function for IP function that can be used as a passive function for IP DetNet flows
DetNet flows using UDP or TCP. Clause 6.8 of IEEE P802.1CBdb using UDP or TCP. Clause 6.8 of [IEEEP8021CBdb] defines a Mask-and-
[IEEEP8021CBdb] defines a Mask-and-Match Stream identification Match Stream identification function that can be used as a passive
function that can be used as a passive function for any IP DetNet function for any IP DetNet flows.
flows.
Clause 6.6 of IEEE 802.1CB [IEEE8021CB] defines an Active Destination Clause 6.6 of [IEEE8021CB] defines an Active Destination MAC and VLAN
MAC and VLAN Stream identification function, what can replace some Stream identification function that can replace some Ethernet header
Ethernet header fields namely (1) the destination MAC-address, (2) fields: (1) the destination MAC address, (2) the VLAN-ID, and (3)
the VLAN-ID and (3) priority parameters with alternate values. priority parameters with alternate values. Replacement is provided
Replacement is provided for the frame passed down the stack from the for the frame passed down the stack from the upper layers or up the
upper layers or up the stack from the lower layers. stack from the lower layers.
Active Destination MAC and VLAN Stream identification can be used Active Destination MAC and VLAN Stream identification can be used
within a Talker to set flow identity or a Listener to recover the within a Talker to set flow identity or within a Listener to recover
original addressing information. It can be used also in a TSN bridge the original addressing information. It can be used also in a TSN
that is providing translation as a proxy service for an End System. bridge that is providing translation as a proxy service for an End
System.
4.2. TSN requirements of IP DetNet nodes 4.2. TSN Requirements of IP DetNet Nodes
This section covers required behavior of a TSN-aware DetNet node This section covers the required behavior of a TSN-aware DetNet node
using a TSN sub-network. The implementation of TSN packet processing using a TSN sub-network. The implementation of TSN packet-processing
functions must be compliant with the relevant IEEE 802.1 standards. functions must be compliant with the relevant IEEE 802.1 standards.
From the TSN sub-network perspective DetNet IP nodes are treated as From the TSN sub-network perspective, DetNet IP nodes are treated as
Talker or Listener, that may be (1) TSN-unaware or (2) TSN-aware. a Talker or Listener that may be (1) TSN unaware or (2) TSN aware.
In cases of TSN-unaware IP DetNet nodes the TSN relay nodes within In cases of TSN-unaware IP DetNet nodes, the TSN relay nodes within
the TSN sub-network must modify the Ethernet encapsulation of the the TSN sub-network must modify the Ethernet encapsulation of the
DetNet IP flow (e.g., MAC translation, VLAN-ID setting, Sequence DetNet IP flow (e.g., MAC translation, VLAN-ID setting, sequence
number addition, etc.) to allow proper TSN specific handling inside number addition, etc.) to allow proper TSN-specific handling inside
the sub-network. There are no requirements defined for TSN-unaware the sub-network. There are no requirements defined for TSN-unaware
IP DetNet nodes in this document. IP DetNet nodes in this document.
IP (DetNet) nodes being TSN-aware can be treated as a combination of IP (DetNet) nodes being TSN aware can be treated as a combination of
a TSN-unaware Talker/Listener and a TSN-Relay, as shown in Figure 2. a TSN-unaware Talker/Listener and a TSN relay, as shown in Figure 2.
In such cases the IP (DetNet) node must provide the TSN sub-network In such cases, the IP (DetNet) node must provide the TSN sub-network-
specific Ethernet encapsulation over the link(s) towards the sub- specific Ethernet encapsulation over the link(s) towards the sub-
network. network.
IP (DetNet) IP (DetNet)
Node Node
<----------------------------------> <---------------------------------->
............ ............
<--: Service :-- DetNet flow ------------------ <--: Service :-- DetNet flow ------------------
+----------+ +----------+
|Forwarding| |Forwarding|
+----------+ +---------------+ +----------+ +---------------+
| L2 | | L2 Relay with |<--- TSN --- | L2 | | L2 Relay with |<--- TSN ---
| | | TSN function | Stream | | | TSN function | Stream
+-----.----+ +--.------.---.-+ +-----.----+ +--.------.---.-+
\__________/ \ \______ \__________/ \ \______
\_________ \_________
TSN-unaware TSN-unaware
Talker / TSN-Bridge Talker / TSN Bridge
Listener Relay Listener Relay
<----- TSN Sub-network ----- <----- TSN Sub-network -----
<------- TSN-aware Tlk/Lstn -------> <------- TSN-aware Tlk/Lstn ------->
Figure 2: IP (DetNet) node with TSN functions Figure 2: IP (DetNet) Node with TSN Functions
A TSN-aware IP (DetNet) node impementations must support the Stream A TSN-aware IP (DetNet) node implementation must support the Stream
Identification TSN component for recognizing flows. identification TSN component for recognizing flows.
A Stream identification component must be able to instantiate the A Stream identification component must be able to instantiate the
following functions (1) Active Destination MAC and VLAN Stream following: (1) Active Destination MAC and VLAN Stream identification,
identification function, (2) IP Stream identification function, (3) (2) IP Stream identification, (3) Mask-and-Match Stream
Mask-and-Match Stream identification function and (4) the related identification, and (4) the related managed objects in Clause 9 of
managed objects in Clause 9 of IEEE 802.1CB [IEEE8021CB] and IEEE [IEEE8021CB] and [IEEEP8021CBdb].
P802.1CBdb [IEEEP8021CBdb].
A TSN-aware IP (DetNet) node implementations must support the A TSN-aware IP (DetNet) node implementation must support the
Sequencing function and the Sequence encode/decode function as Sequencing function and the Sequence encode/decode function as
defined in Clause 7.4 and 7.6 of IEEE 802.1CB [IEEE8021CB] if FRER is defined in Clauses 7.4 and 7.6 of [IEEE8021CB] if FRER is used inside
used inside the TSN sub-network. the TSN sub-network.
The Sequence encode/decode function must support the Redundancy tag The Sequence encode/decode function must support the Redundancy tag
(R-TAG) format as per Clause 7.8 of IEEE 802.1CB [IEEE8021CB]. (R-TAG) format as per Clause 7.8 of [IEEE8021CB].
A TSN-aware IP (DetNet) node implementations must support the Stream A TSN-aware IP (DetNet) node implementation must support the Stream
splitting function and the Individual recovery function as defined in splitting function and the Individual recovery function as defined in
Clause 7.7 and 7.5 of IEEE 802.1CB [IEEE8021CB] when the node is a Clauses 7.7 and 7.5 of [IEEE8021CB] when the node is a replication or
replication or elimination point for FRER. elimination point for FRER.
4.3. Service protection within the TSN sub-network 4.3. Service Protection within the TSN Sub-network
TSN Streams supporting DetNet flows may use Frame Replication and TSN Streams supporting DetNet flows may use FRER as defined in Clause
Elimination for Redundancy (FRER) as defined in Clause 8. of IEEE 8 of [IEEE8021CB] based on the loss service requirements of the TSN
802.1CB [IEEE8021CB] based on the loss service requirements of the Stream, which is derived from the DetNet service requirements of the
TSN Stream, which is derived from the DetNet service requirements of DetNet mapped flow. The specific operation of FRER is not modified
the DetNet mapped flow. The specific operation of FRER is not by the use of DetNet and follows [IEEE8021CB].
modified by the use of DetNet and follows IEEE 802.1CB [IEEE8021CB].
FRER function and the provided service recovery is available only The FRER function and the provided service recovery are available
within the TSN sub-network as the TSN Stream-ID and the TSN sequence only within the TSN sub-network, as the TSN Stream ID and the TSN
number are not valid outside the sub-network. An IP (DetNet) node sequence number are not valid outside the sub-network. An IP
represents a L3 border and as such it terminates all related (DetNet) node represents an L3 border and as such, it terminates all
information elements encoded in the L2 frames. related information elements encoded in the L2 frames.
4.4. Aggregation during DetNet flow to TSN Stream mapping 4.4. Aggregation during DetNet Flow to TSN Stream Mapping
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
DetNet flow and TSN Stream mapping related information are required DetNet flows 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).
The following summarizes the set of information that is needed to The following summarizes the set of information that is needed to
configure DetNet IP over TSN: configure DetNet IP over TSN:
o DetNet IP related configuration information according to the * DetNet-IP-related configuration information according to the
DetNet role of the DetNet IP node, as per [RFC8939]. DetNet role of the DetNet IP node, as per [RFC8939].
o TSN related configuration information according to the TSN role of * TSN-related configuration information according to the TSN role of
the DetNet IP node, as per [IEEE8021Q], [IEEE8021CB] and the DetNet IP node, as per [IEEE8021Q], [IEEE8021CB], and
[IEEEP8021CBdb]. [IEEEP8021CBdb].
o Mapping between DetNet IP flow(s) (as flow identification defined * Mapping between DetNet IP flow(s) and TSN Stream(s). DetNet IP
in [RFC8939], it is summarized in Section 5.1 of that document, flow identification is summarized in Section 5.1 of [RFC8939] and
and includes all wildcards, port ranges and the ability to ignore includes all wildcards, port ranges, and the ability to ignore
specific IP fields) and TSN Stream(s) (as stream identification specific IP fields. Information on TSN Stream identification
information defined in [IEEE8021CB] and [IEEEP8021CBdb]). Note, information is defined in [IEEE8021CB] and [IEEEP8021CBdb]. Note
that managed objects for TSN Stream identification can be found in that managed objects for TSN Stream identification can be found in
[IEEEP8021CBcv]. [IEEEP8021CBcv].
This information must be provisioned per DetNet flow. This information must be provisioned per DetNet flow.
Mappings between DetNet and TSN management and control planes are out Mappings between DetNet and TSN management and control planes are out
of scope of the document. Some of the challanges are highligthed of scope of this document. Some of the challenges are highlighted
below. below.
TSN-aware IP DetNet nodes are member of both the DetNet domain and TSN-aware IP DetNet nodes are members 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
in DetNet and TSN, but that is not the case for the control plane in DetNet and TSN, but that is not the case for the control plane
protocols. For example, RSVP-TE and MSRP behaves differently. protocols. For example, RSVP-TE and the Multiple Stream Registration
Therefore management and control plane design is an important aspect Protocol (MSRP) of IEEE 802.1 behave differently. Therefore,
of scenarios, where mapping between DetNet and TSN is required. management and control plane design is an important aspect of
scenarios where mapping between DetNet and TSN is required.
In order to use a TSN sub-network between DetNet nodes, DetNet In order to use a TSN sub-network between DetNet nodes, DetNet-
specific information must be converted to TSN sub-network specific specific information must be converted to TSN sub-network-specific
ones. DetNet flow ID and flow related parameters/requirements must information. DetNet flow ID and flow-related parameters/requirements
be converted to a TSN Stream ID and stream related parameters/ must be converted to a TSN Stream ID and stream-related parameters/
requirements. Note that, as the TSN sub-network is just a portion of requirements. Note that, as the TSN sub-network is just a portion of
the end-to-end DetNet path (i.e., single hop from IP perspective), the end-to-end DetNet path (i.e., single hop from an IP perspective),
some parameters (e.g., delay) may differ significantly. Other some parameters (e.g., delay) may differ significantly. Other
parameters (like bandwidth) also may have to be tuned due to the L2 parameters (like bandwidth) also may have to be tuned due to the L2
encapsulation used within the TSN sub-network. encapsulation used within the TSN sub-network.
In some case it may be challenging to determine some TSN Stream In some cases, it may be challenging to determine some TSN Stream-
related information. For example, on a TSN-aware IP (DetNet) node related information. For example, on a TSN-aware IP (DetNet) node
that acts as a Talker, it is quite obvious which DetNet node is the that acts as a Talker, it is quite obvious which DetNet node is the
Listener of the mapped TSN stream (i.e., the IP Next-Hop). However Listener of the mapped TSN Stream (i.e., the IP next-hop). However,
it may be not trivial to locate the point/interface where that it may not be trivial to locate the point/interface where that
Listener is connected to the TSN sub-network. Such attributes may Listener is connected to the TSN sub-network. Such attributes may
require interaction between control and management plane functions require interaction between control and management plane functions
and between DetNet and TSN domains. and between DetNet and TSN domains.
Mapping between DetNet flow identifiers and TSN Stream identifiers, Mapping between DetNet flow identifiers and TSN Stream identifiers,
if not provided explicitly, can be done by a TSN-aware IP (DetNet) if not provided explicitly, can be done by a TSN-aware IP (DetNet)
node locally based on information provided for configuration of the node locally based on information provided for configuration of the
TSN Stream identification functions (IP Stream identification, Mask- TSN Stream identification functions (IP Stream identification, Mask-
and-match Stream identification and active Stream identification and-Match Stream identification, and the active Stream identification
function). function).
Triggering the setup/modification of a TSN Stream in the TSN sub- Triggering the setup/modification of a TSN Stream in the TSN sub-
network is an example where management and/or control plane network is an example where management and/or control plane
interactions are required between the DetNet and TSN sub-network. interactions are required between the DetNet and TSN sub-network.
TSN-unaware IP (DetNet) nodes make such a triggering even more TSN-unaware IP (DetNet) nodes make such a triggering even more
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
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 [DETNET-SECURITY]. General security considerations are described in
described in [RFC8655]. DetNet IP data plane specific considerations [RFC8655]. Considerations specific to the DetNet IP data plane are
are summarized in [RFC8939]. This section considers exclusively summarized in [RFC8939]. This section discusses security
security considerations which are specific to the DetNet IP over TSN considerations that are specific to the DetNet IP-over-TSN sub-
sub-network scenario. network scenario.
The sub-network between DetNet nodes needs to be subject to The sub-network between DetNet nodes needs to be subject to
appropriate confidentiality. Additionally, knowledge of what DetNet/ appropriate confidentiality. Additionally, knowledge of what DetNet/
TSN services are provided by a sub-network may supply information TSN services are provided by a sub-network may supply information
that can be used in a variety of security attacks. The ability to that can be used in a variety of security attacks. The ability to
modify information exchanges between connected DetNet nodes may modify information exchanges between connected DetNet nodes may
result in bogus operations. Therefore, it is important that the result in bogus operations. Therefore, it is important that the
interface between DetNet nodes and TSN sub-network are subject to interface between DetNet nodes and the TSN sub-network are subject to
authorization, authentication, and encryption. authorization, authentication, and encryption.
The TSN sub-network operates at Layer-2 so various security The TSN sub-network operates at Layer 2, so various security
mechanisms defined by IEEE can be used to secure the connection mechanisms defined by IEEE can be used to secure the connection
between the DetNet nodes (e.g., encryption may be provided using between the DetNet nodes (e.g., encryption may be provided using
MACSec [IEEE802.1AE-2018]). MACsec [IEEE802.1AE-2018]).
7. IANA Considerations 7. IANA Considerations
None. This document has no IANA actions.
8. Acknowledgements 8. References
The authors wish to thank Norman Finn, Lou Berger, Craig Gunther, 8.1. Normative References
Christophe Mangin and Jouni Korhonen for their various contributions
to this work.
9. References [IEEE8021CB]
IEEE, "IEEE Standard for Local and metropolitan area
networks--Frame Replication and Elimination for
Reliability", IEEE 802.1CB-2017,
DOI 10.1109/IEEESTD.2017.8091139, October 2017,
<https://standards.ieee.org/standard/802_1CB-2017.html>.
9.1. Normative references [IEEEP8021CBdb]
IEEE, "Draft Standard for Local and metropolitan area
networks -- Frame Replication and Elimination for
Reliability -- Amendment: Extended Stream Identification
Functions", IEEE P802.1CBdb / D1.3, April 2021,
<https://1.ieee802.org/tsn/802-1cbdb/>.
[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>.
[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 8.2. Informative References
[I-D.ietf-detnet-security] [DETNET-SECURITY]
Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic Grossman, E., Ed., Mizrahi, T., and A. Hacker,
Networking (DetNet) Security Considerations", draft-ietf- "Deterministic Networking (DetNet) Security
detnet-security-12 (work in progress), October 2020. Considerations", Work in Progress, Internet-Draft, draft-
ietf-detnet-security-16, March 2021,
<https://tools.ietf.org/html/draft-ietf-detnet-security-
16>.
[IEEE802.1AE-2018] [IEEE802.1AE-2018]
IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC IEEE, "IEEE Standard for Local and metropolitan area
Security (MACsec)", 2018, networks--Media Access Control (MAC) Security", IEEE
<https://ieeexplore.ieee.org/document/8585421>. 802.1AE-2018, DOI 10.1109/IEEESTD.2018.8585421, December
2018, <https://ieeexplore.ieee.org/document/8585421>.
[IEEE8021CB]
IEEE 802.1, "Standard for Local and metropolitan area
networks - Frame Replication and Elimination for
Reliability (IEEE Std 802.1CB-2017)", 2017,
<http://standards.ieee.org/about/get/>.
[IEEE8021Q] [IEEE8021Q]
IEEE 802.1, "Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and Metropolitan Area
networks--Bridges and Bridged Networks (IEEE Std 802.1Q- Network--Bridges and Bridged Networks", IEEE Std 802.1Q-
2018)", 2018, <http://standards.ieee.org/about/get/>. 2018, DOI 10.1109/IEEESTD.2018.8403927, July 2018,
<https://ieeexplore.ieee.org/document/8403927>.
[IEEEP8021CBcv] [IEEEP8021CBcv]
Kehrer, S., "FRER YANG Data Model and Management IEEE 802.1, "Draft Standard for Local and metropolitan
Information Base Module", IEEE P802.1CBcv area networks--Frame Replication and Elimination for
/D0.4 P802.1CBcv, August 2020, Reliability--Amendment: Information Model, YANG Data Model
<https://www.ieee802.org/1/files/private/cv-drafts/d0/802- and Management Information Base Module", IEEE P802.1CBcv,
1CBcv-d0-4.pdf>. Draft 1.1, February 2021,
<https://1.ieee802.org/tsn/802-1cbcv/>.
[IEEEP8021CBdb] Acknowledgements
Mangin, C., "Extended Stream identification functions",
IEEE P802.1CBdb /D1.0 P802.1CBdb, September 2020,
<http://www.ieee802.org/1/files/private/db-drafts/d1/802-
1CBdb-d1-0.pdf>.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, The authors wish to thank Norman Finn, Lou Berger, Craig Gunther,
"Deterministic Networking Architecture", RFC 8655, Christophe Mangin, and Jouni Korhonen for their various contributions
DOI 10.17487/RFC8655, October 2019, to this work.
<https://www.rfc-editor.org/info/rfc8655>.
Authors' Addresses Authors' Addresses
Balazs Varga (editor) Balázs Varga (editor)
Ericsson Ericsson
Budapest
Magyar Tudosok krt. 11. Magyar Tudosok krt. 11.
Budapest 1117 1117
Hungary Hungary
Email: balazs.a.varga@ericsson.com Email: balazs.a.varga@ericsson.com
Janos Farkas János Farkas
Ericsson Ericsson
Budapest
Magyar Tudosok krt. 11. Magyar Tudosok krt. 11.
Budapest 1117 1117
Hungary Hungary
Email: janos.farkas@ericsson.com Email: janos.farkas@ericsson.com
Andrew G. Malis Andrew G. Malis
Malis Consulting Malis Consulting
Email: agmalis@gmail.com Email: agmalis@gmail.com
Stewart Bryant Stewart Bryant
Futurewei Technologies Futurewei Technologies
Email: stewart.bryant@gmail.com Email: sb@stewartbryant.com
 End of changes. 97 change blocks. 
242 lines changed or deleted 252 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/