rfc9037xml2.original.xml   rfc9037.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml2rfc.tools.ietf.org/public/rfc/bibxml/refe
rence.RFC.2119.xml">
<!ENTITY rfc3031 PUBLIC "" "http://xml2rfc.tools.ietf.org/public/rfc/bibxml/refe
rence.RFC.3031.xml">
]> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no"?>
<?rfc strict="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="info"
docName="draft-ietf-detnet-mpls-over-tsn-07"
ipr="trust200902"
submissionType="IETF">
<front>
<title abbrev="DetNet MPLS over TSN">
DetNet Data Plane: MPLS over IEEE 802.1 Time-Sensitive Networking (TSN)</tit
le>
<author role="editor" fullname="Bal&aacute;zs Varga" initials="B." surname="Va <rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-detnet-mpls-
rga"> over-tsn-07"
<organization>Ericsson</organization> number="9037" ipr="trust200902" submissionType="IETF" category="info" consensus=
<address> "true"
<postal> obsoletes="" updates="" xml:lang="en" tocInclude="true" symRefs="true" sortRefs=
<street>Magyar Tudosok krt. 11.</street> "true"
<city>Budapest</city> version="3">
<country>Hungary</country>
<code>1117</code>
</postal>
<email>balazs.a.varga@ericsson.com</email>
</address>
</author>
<author fullname="J&aacute;nos Farkas" initials="J." surname="Farkas"> <!-- xml2rfc v2v3 conversion 3.5.0 -->
<front>
<title abbrev="DetNet MPLS over TSN">
Deterministic Networking (DetNet) Data Plane: MPLS over IEEE 802.1 Time-Sens
itive Networking (TSN)</title>
<seriesInfo name="RFC" value="9037"/>
<author role="editor" fullname="Balázs Varga" initials="B." surname="Varga">
<organization>Ericsson</organization>
<address>
<postal>
<street>Magyar Tudosok krt. 11.</street>
<city>Budapest</city>
<country>Hungary</country>
<code>1117</code>
</postal>
<email>balazs.a.varga@ericsson.com</email>
</address>
</author>
<author fullname="János Farkas" initials="J." surname="Farkas">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address> <address>
<postal> <postal>
<street>Magyar Tudosok krt. 11.</street> <street>Magyar Tudosok krt. 11.</street>
<city>Budapest</city> <city>Budapest</city>
<country>Hungary</country> <country>Hungary</country>
<code>1117</code> <code>1117</code>
</postal> </postal>
<email>janos.farkas@ericsson.com</email> <email>janos.farkas@ericsson.com</email>
</address> </address>
</author> </author>
<author fullname="Andrew G. Malis" initials="A." surname="Malis">
<author fullname="Andrew G. Malis" initials="A.G." surname="Malis
">
<organization>Malis Consulting</organization> <organization>Malis Consulting</organization>
<address> <address>
<email>agmalis@gmail.com</email> <email>agmalis@gmail.com</email>
</address> </address>
</author> </author>
<author fullname="Stewart Bryant" initials="S." surname="Bryant"> <author fullname="Stewart Bryant" initials="S." surname="Bryant">
<organization>Futurewei Technologies</organization> <organization>Futurewei Technologies</organization>
<address> <address>
<email>stewart.bryant@gmail.com</email> <email>sb@stewartbryant.com</email>
</address> </address>
</author> </author>
<date year="2021" month="June" />
<date /> <workgroup>DetNet</workgroup>
<workgroup>DetNet</workgroup> <abstract>
<t>
<abstract> This document specifies the Deterministic Networking (DetNet) MPLS data pla
<t> ne
This document specifies the Deterministic Networking MPLS data plane
when operating over an IEEE 802.1 Time-Sensitive Networking (TSN) when operating over an IEEE 802.1 Time-Sensitive Networking (TSN)
sub-network. This document does not define sub-network. This document does not define
new procedures or processes. Whenever this document makes new procedures or processes. Whenever this document makes
statements or recommendations, these are taken from normative text in th e statements or recommendations, they are taken from normative text in the
referenced RFCs. referenced RFCs.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle>
<middle> <section anchor="sec_intro" numbered="true" toc="default">
<section title="Introduction" anchor="sec_intro"> <name>Introduction</name>
<t> <t>
Deterministic Networking (DetNet) is a service that can be offered by a Deterministic Networking (DetNet) is a service that can be offered by a
network to DetNet flows. DetNet provides these flows with low packet loss network to DetNet flows. DetNet provides these flows with low packet loss
rate and assured maximum end-to-end delivery latency. General background rate and assured maximum end-to-end delivery latency. General background
and concepts of DetNet can be found in <xref and concepts of DetNet can be found in <xref target="RFC8655" format="defaul
target="RFC8655"/>. t"/>.
</t> </t>
<t> <t>
The DetNet Architecture decomposes the DetNet related data plane The DetNet architecture decomposes DetNet-related data plane
functions into two sub-layers: a service sub-layer and a forwarding sub-laye r. functions into two sub-layers: a service sub-layer and a forwarding sub-laye r.
The service sub-layer is used to provide DetNet service protection and The service sub-layer is used to provide DetNet service protection and
reordering. The forwarding sub-layer is used to provide congestion reordering. The forwarding sub-layer is used to provide congestion
protection (low loss, assured latency, and limited reordering) protection (low loss, assured latency, and limited reordering)
leveraging MPLS Traffic Engineering mechanisms. leveraging MPLS Traffic Engineering mechanisms.
</t> </t>
<t> <t>
<xref target="RFC8964"/> specifies the DetNet data plane <xref target="RFC8964" format="default"/> specifies the DetNet data plane
operation for MPLS-based Packet Switched Network (PSN). MPLS encapsulate operation for an MPLS-based PSN. MPLS-encapsulated
d
DetNet flows can be carried over network technologies that can provide th e DetNet flows can be carried over network technologies that can provide th e
DetNet required level of service. This document focuses on the scenario DetNet-required level of service. This document focuses on the scenario
where MPLS (DetNet) nodes are interconnected by a IEEE 802.1 TSN sub-netw where MPLS (DetNet) nodes are interconnected by an IEEE 802.1 TSN sub-net
ork. work.
There is close cooperation between the IETF DetNet WG and the IEEE 802.1 There is close cooperation between the IETF DetNet Working Group and the
TSN TG. IEEE 802.1 Time-Sensitive Networking Task Group (TSN TG).
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Terminology"> <name>Terminology</name>
<section numbered="true" toc="default">
<section title="Terms Used in This Document"> <name>Terms Used in This Document</name>
<t> <t>
This document uses the terminology established in the DetNet architecture This document uses the terminology established in the DetNet architecture
<xref target="RFC8655"/> and <xref target="RFC8655" format="default"/>
<xref target="RFC8964"/>. TSN specific terms are defined in the TSN TG <xref target="RFC8964" format="default"/>. TSN-specific terms are defined in
of IEEE 802.1 Working Group. The reader is assumed the TSN TG
of the IEEE 802.1 Working Group. The reader is assumed
to be familiar with these documents and their terminology. to be familiar with these documents and their terminology.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Abbreviations"> <name>Abbreviations</name>
<t> <t>
The following abbreviations are used in this document: The following abbreviations are used in this document:
<list style="hanging" hangIndent="14"> </t>
<t hangText="A-Label">Aggregation label, a special case of an S-Label.</t> <dl newline="false" spacing="normal" indent="14">
<t hangText="d-CW">DetNet Control Word.</t> <dt>A-Label</dt>
<t hangText="DetNet">Deterministic Networking.</t> <dd>Aggregation label; a special case of an S-Label.</dd>
<t hangText="F-Label">Forwarding label that identifies the LSP used by a <dt>d-CW</dt>
DetNet flow.</t> <dd>DetNet Control Word</dd>
<t hangText="FRER">Frame Replication and Elimination for Redundancy <dt>DetNet</dt>
(TSN function).</t> <dd>Deterministic Networking</dd>
<t hangText="L2">Layer 2.</t> <dt>F-Label</dt>
<t hangText="L3">Layer 3.</t> <dd>Forwarding label that identifies the LSP used by a
<t hangText="MPLS">Multiprotocol Label Switching.</t> DetNet flow.</dd>
<t hangText="PREOF">Packet Replication, Elimination and Ordering Functions.< <dt>FRER</dt>
/t> <dd>Frame Replication and Elimination for Redundancy
<t hangText="PSN">Packet Switched Network.</t> (TSN function)</dd>
<t hangText="PW">PseudoWire.</t> <dt>L2</dt>
<t hangText="RSVP-TE">Resource Reservation Protocol - Traffic Engineering.</ <dd>Layer 2</dd>
t> <dt>L3</dt>
<t hangText="S-Label">Service label.</t> <dd>Layer 3</dd>
<t hangText="TSN">Time-Sensitive Network.</t> <dt>LSP</dt><dd>Label Switched Path</dd>
</list> <dt>MPLS</dt>
</t> <dd>Multiprotocol Label Switching</dd>
</section> <dt>PREOF</dt>
<!-- <section title="Requirements Language"> <dd>Packet Replication, Elimination, and Ordering Functions</dd>
<t> <dt>PSN</dt>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <dd>Packet Switched Network</dd>
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and <dt>PW</dt>
"OPTIONAL" in this document are to be interpreted as described in <dd>Pseudowire</dd>
BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and <dt>RSVP-TE</dt>
only when, they appear in all capitals, as shown here. <dd>Resource Reservation Protocol - Traffic Engineering</dd>
</t> <dt>S-Label</dt>
</section> --> <dd>Service label</dd>
</section> <!-- end of terminology --> <dt>TSN</dt>
<dd>Time-Sensitive Networking</dd>
</dl>
</section>
</section>
<section title="DetNet MPLS Data Plane Overview" anchor="sec_dt_dp"> <section anchor="sec_dt_dp" numbered="true" toc="default">
<t> <name>DetNet MPLS Data Plane Overview</name>
The basic approach defined in <xref target="RFC8964"/> <t>
supports the DetNet service sub-layer based on existing pseudowire (PW) The basic approach defined in <xref target="RFC8964" format="default"/>
encapsulations and mechanisms, and supports the DetNet forwarding supports the DetNet service sub-layer based on existing PW
encapsulations and mechanisms and supports the DetNet forwarding
sub-layer based on existing MPLS Traffic Engineering encapsulations sub-layer based on existing MPLS Traffic Engineering encapsulations
and mechanisms. and mechanisms.
</t> </t>
<t> <t>
A node operating on a DetNet flow in the Detnet service sub-layer, i.e. A node operates on a DetNet flow in the DetNet service sub-layer, i.e.,
a node processing a DetNet packet which has the S-Label as top of stack uses a node processing a DetNet packet that has the service label (S-Label) as the
the local context associated with that service label (S-Label), for example a top of stack uses
received the local context associated with that S-Label, for example, a received
forwarding label (F-Label), to determine what local DetNet operation(s) are ap forwarding label (F-Label), to determine what local DetNet operation(s) is app
plied to that lied to that
packet. An S-Label may be unique when taken from the platform packet. An S-Label may be unique when taken from the platform
label space <xref target="RFC3031"/>, which would enable correct DetNet flow label space <xref target="RFC3031" format="default"/>, which would enable corr ect DetNet flow
identification regardless of which input interface or LSP the packet arrives identification regardless of which input interface or LSP the packet arrives
on. The service sub-layer functions (i.e., PREOF) use a DetNet control word on. The service sub-layer functions (i.e., PREOF) use a d-CW.
(d-CW). </t>
</t> <t>
<t>
The DetNet MPLS data plane builds on MPLS Traffic Engineering The DetNet MPLS data plane builds on MPLS Traffic Engineering
encapsulations and mechanisms to provide a forwarding sub-layer that encapsulations and mechanisms to provide a forwarding sub-layer that
is responsible for providing resource allocation and explicit is responsible for providing resource allocation and explicit
routes. The forwarding sub-layer is supported by one or more routes. The forwarding sub-layer is supported by one or more
F-Labels. F-Labels.
</t> </t>
<t> <t>
DetNet edge/relay nodes are DetNet service sub-layer DetNet edge/relay nodes are DetNet service sub-layer-aware,
aware, understand the particular needs of DetNet flows and understand the particular needs of DetNet flows, and
provide both DetNet service and forwarding sub-layer functions. provide both DetNet service and forwarding sub-layer functions.
They add, remove and process d-CWs, S-Labels and F-labels as They add, remove, and process d-CWs, S-Labels, and F-Labels as
needed. MPLS DetNet nodes and transit nodes include needed. MPLS DetNet nodes and transit nodes include
DetNet forwarding sub-layer functions, notably support for DetNet forwarding sub-layer functions, notable support for
explicit routes, and resources allocation to eliminate (or explicit routes, and resource allocation to eliminate (or
reduce) congestion loss and jitter. Unlike other DetNet node types, reduce) congestion loss and jitter. Unlike other DetNet node types,
transit nodes provide no service sub-layer processing. transit nodes provide no service sub-layer processing.
</t> </t>
<t> <t>
MPLS (DetNet) nodes and transit nodes interconnected by a TSN MPLS (DetNet) nodes and transit nodes interconnected by a TSN
sub-network are the primary focus of this document. sub-network are the primary focus of this document.
The mapping of DetNet MPLS flows to TSN streams and TSN protectio The mapping of DetNet MPLS flows to TSN Streams and TSN protectio
n n
mechanisms are covered in <xref target="mpls-over-tsn"/>. mechanisms are covered in <xref target="mpls-over-tsn" format="de
</t> fault"/>.
</section> <!-- end of data plane overview --> </t>
</section>
<!-- ===================================================================== -->
<section anchor="mpls-over-tsn" <section anchor="mpls-over-tsn" numbered="true" toc="default">
title="DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks"> <name>DetNet MPLS Operation over IEEE 802.1 TSN Sub-networks</name>
<t> <t>
The DetNet WG collaborates with IEEE 802.1 TSN in order to define a The DetNet WG collaborates with IEEE 802.1 TSN in order to define a
common architecture for both Layer 2 and Layer 3, that maintains common architecture for both Layer 2 and Layer 3 that maintains
consistency across diverse networks. Both DetNet MPLS and TSN use consistency across diverse networks. Both DetNet MPLS and TSN use
the same techniques to provide their deterministic service: the same techniques to provide their deterministic service:
<list style="symbols"> </t>
<t> <ul spacing="normal">
Service protection. <li>
</t><t> Service protection
Resource allocation. </li>
</t><t> <li>
Explicit routes. Resource allocation
</t> </li>
</list> <li>
Explicit routes
</li>
</ul>
<t>
As described in the DetNet architecture As described in the DetNet architecture
<xref target="RFC8655"/> a sub-network provides from <xref target="RFC8655" format="default"/>, from the MPLS perspect
MPLS perspective a single hop connection between MPLS (DetNet) no ive, a sub-network provides
des. a single-hop connection between MPLS (DetNet) nodes.
Functions used for resource allocation and explicit routes Functions used for resource allocation and explicit routes
are treated as domain internal functions and do not require funct ion are treated as domain internal functions and do not require funct ion
interworking across the DetNet MPLS network and the TSN sub-netwo rk. interworking across the DetNet MPLS network and the TSN sub-netwo rk.
</t> </t>
<t> <t>
In the case of the service protection function due to the similar In the case of the service protection function, due to the simila
ities of rities of
the DetNet PREOF and TSN FRER functions some level of interworkin the DetNet PREOF and TSN FRER functions, some level of interworki
g is ng is
possible. However, such interworking is out-of-scope in this docu possible. However, such interworking is out of scope of this docu
ment ment
and left for further study. and left for further study.
</t> </t>
<t> <t>
<xref target="fig_mpls_detnet_to_tsn"/> illustrates a scenario, where <xref target="fig_mpls_detnet_to_tsn" format="default"/> illustrates a sce
nario where
two MPLS (DetNet) nodes are interconnected by a TSN sub-network. Node-1 two MPLS (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. is single-homed, and Node-2 is dual-homed to the TSN sub-network.
</t> </t>
<figure anchor="fig_mpls_detnet_to_tsn">
<figure align="center" anchor="fig_mpls_detnet_to_tsn" <name>DetNet-Enabled MPLS Network over a TSN Sub-network</name>
title="DetNet Enabled MPLS Network Over a TSN Sub-Network"> <artwork name="" type="" align="left" alt=""><![CDATA[
<artwork><![CDATA[
MPLS (DetNet) MPLS (DetNet) MPLS (DetNet) MPLS (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 MPLS ---------------> <---------------- DetNet MPLS --------------->
Note: * no service sub-layer required for transit nodes Note: * no service sub-layer required for transit nodes
]]></artwork> ]]></artwork>
</figure> </figure>
<t>
<t>
At the time of this writing, At the time of this writing,
the Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1 the TSN TG of the IEEE 802.1
Working Group have defined (and are defining) a number of amendme nts Working Group have defined (and are defining) a number of amendme nts
to <xref target="IEEE8021Q"/> that provide zero to <xref target="IEEE8021Q" format="default"/> that provide zero
congestion loss and bounded latency in bridged networks. Furtherm congestion loss and bounded latency in bridged networks. Furtherm
ore ore,
<xref target="IEEE8021CB"/> defines frame replication <xref target="IEEE8021CB" format="default"/> defines frame replic
ation
and elimination functions for reliability that should prove both and elimination functions for reliability that should prove both
compatible with and useful to, DetNet networks. All these functio compatible with and useful to DetNet networks. All these function
ns s
have to identify flows those require TSN treatment (i.e., applyin have to identify flows that require TSN treatment (i.e., applying
g TSN TSN
functions during forwarding). functions during forwarding).
</t> </t>
<t> <t>
TSN capabilities of the TSN sub-network are made available for MPLS TSN capabilities of the TSN sub-network are made available for MPLS
(DetNet) flows via the protocol interworking function defined in Annex C .5 of (DetNet) flows via the protocol interworking function defined in Annex C .5 of
<xref target="IEEE8021CB"/>. For example, <xref target="IEEE8021CB" format="default"/>. For example,
applied on the TSN edge port it can convert an ingress unicast when applied on the TSN edge port, it can convert an ingress unicast
MPLS (DetNet) flow to use a specific Layer-2 multicast destinatio MPLS (DetNet) flow to use a specific Layer 2 multicast destinatio
n n
MAC address and a VLAN, in order to direct the packet through a Media Access Control (MAC) address and a VLAN, in order to direct
the packet through a
specific path inside the bridged network. specific path inside the bridged network.
A similar interworking function pair at the A similar interworking function pair at the
other end of the TSN sub-network would restore the packet to its other end of the TSN sub-network would restore the packet to its
original Layer-2 destination MAC address and VLAN. original Layer 2 destination MAC address and VLAN.
</t> </t>
<t> <t>
Placement of TSN functions depends on the TSN capabilities of the The placement of TSN functions depends on the TSN capabilities of the
nodes along the path. MPLS (DetNet) Nodes may or may not support TSN fun nodes along the path. MPLS (DetNet) nodes may or may not support TSN fun
ctions. For ctions. For
a given TSN Stream (i.e., DetNet flow) an MPLS (DetNet) node is a given TSN Stream (i.e., DetNet flow), an MPLS (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.
</t> </t>
<section numbered="true" toc="default">
<section title="Functions for DetNet Flow to TSN Stream Mapping"> <name>Functions for DetNet Flow to TSN Stream Mapping</name>
<t> <t>
Mapping of a DetNet MPLS flow to a TSN Stream is provided via Mapping of a DetNet MPLS flow to a TSN Stream is provided via
the combination of a passive and an active stream ident the combination of a passive and an active Stream ident
ification ification
function that operate at the frame level. The passive s function that operate at the frame level. The passive S
tream tream
identification function is used to catch the MPLS label (s) of a identification function is used to catch the MPLS label (s) of a
DetNet MPLS flow and the active stream identification f unction DetNet MPLS flow, and the active Stream identification function
is used to modify the Ethernet header according to the ID of the is used to modify the Ethernet header according to the ID of the
mapped TSN Stream. mapped TSN Stream.
</t> </t>
<t> <t>
Clause 6.8 of <xref target="IEEEP8021CBdb"/> defines a Clause 6.8 of <xref target="IEEEP8021CBdb" format="defa
ult"/> defines a
Mask-and-Match Stream identification function that can be used Mask-and-Match Stream identification function that can be used
as a passive function for MPLS DetNet flows. as a passive function for MPLS DetNet flows.
</t> </t>
<t> <t>
Clause 6.6 of <xref target="IEEE8021CB"/> defines an Clause 6.6 of <xref target="IEEE8021CB" format="default"/> defines
Active Destination MAC and VLAN Stream identification function, an
what can replace some Ethernet header fields namely (1) the Active Destination MAC and a VLAN Stream identification function
destination MAC-address, (2) the VLAN-ID and (3) priority that can replace some Ethernet header fields, namely (1) the
destination MAC address, (2) the VLAN-ID, and (3) priority
parameters with alternate values. Replacement is provided for parameters with alternate values. Replacement is provided for
the frame passed down the stack from the upper layers or up the the frame that is passed either down the stack from the upper laye rs or up the
stack from the lower layers. stack from the lower layers.
</t> </t>
<t> <t>
Active Destination MAC and VLAN Stream identification can be Active Destination MAC and VLAN Stream identification can be
used within a Talker to set flow identity or a Listener to used within a Talker to set flow identity or a Listener to
recover the original addressing information. It can be used also recover the original addressing information. It can also be used
in a TSN bridge that is providing translation as a proxy service in a TSN bridge that is providing translation as a proxy service
for an End System. for an end system.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="TSN requirements of MPLS DetNet nodes"> <name>TSN Requirements of MPLS DetNet Nodes</name>
<t> <t>
This section covers required behavior of a TSN-aware MPLS (DetNet) This section covers required behavior of a TSN-aware MPLS (DetNet)
node using a TSN sub-network. The implementation of TSN node using a TSN sub-network. The implementation of TSN
packet packet-processing
processing functions must be compliant with the relevan functions must be compliant with the relevant IEEE 802.
t IEEE 802.1 1
standards. standards.
</t> </t>
<t> <t>
From the TSN sub-network perspective MPLS (DetNet) nodes are treat From the TSN sub-network perspective, MPLS (DetNet) nodes are trea
ed ted
as Talker or Listener, that may be (1) TSN-unaware or as a Talker or Listener, which may be (1) TSN-unaware o
r
(2) TSN-aware. (2) TSN-aware.
</t> </t>
<t> <t>
In cases of TSN-unaware MPLS DetNet nodes the TSN relay nodes In cases of TSN-unaware MPLS DetNet nodes, the TSN relay nodes
within the TSN sub-network must modify the Ethernet enc apsulation within the TSN sub-network must modify the Ethernet enc apsulation
of the DetNet MPLS flow (e.g., MAC translation, VLAN-ID setting, of the DetNet MPLS flow (e.g., MAC translation, VLAN-ID setting,
Sequence number addition, etc.) to allow proper TSN spe cific sequence number addition, etc.) to allow proper TSN-spe cific
handling inside the sub-network. There are no requirem ents handling inside the sub-network. There are no requirem ents
defined for TSN-unaware MPLS DetNet nodes in this docum ent. defined for TSN-unaware MPLS DetNet nodes in this docum ent.
</t> </t>
<t> <t>
MPLS (DetNet) nodes being TSN-aware can be treated as a MPLS (DetNet) nodes that are TSN-aware can be treated as a
combination of a TSN-unaware Talker/Listener and a TSN-Relay, as combination of a TSN-unaware Talker/Listener and a TSN-Relay, as
shown in <xref target="fig_mpls_with_tsn"/>. In such cases the shown in <xref target="fig_mpls_with_tsn" format="default"/>. In
MPLS (DetNet) node must provide the TSN sub-network spe such cases, the
cific MPLS (DetNet) node must provide the TSN sub-network-spe
cific
Ethernet encapsulation over the link(s) towards the sub -network. Ethernet encapsulation over the link(s) towards the sub -network.
</t> </t>
<figure anchor="fig_mpls_with_tsn">
<figure align="center" anchor="fig_mpls_with_tsn" <name>MPLS (DetNet) Node with TSN Functions</name>
title="MPLS (DetNet) Node with TSN Functions"> <artwork name="" type="" align="left" alt=""><![CDATA[
<artwork><![CDATA[
MPLS (DetNet) MPLS (DetNet)
Node Node
<----------------------------------> <---------------------------------->
+----------+ +----------+
<--| Service* |-- DetNet flow ------------------ <--| Service* |-- DetNet flow ------------------
+----------+ +----------+
|Forwarding| |Forwarding|
+----------+ +---------------+ +----------+ +---------------+
| L2 | | L2 Relay with |<--- TSN --- | L2 | | L2 Relay with |<--- TSN ---
skipping to change at line 371 skipping to change at line 362
\__________/ \ \______ \__________/ \ \______
\_________ \_________
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 ------->
Note: * no service sub-layer required for transit nodes Note: * no service sub-layer required for transit nodes
]]></artwork> ]]></artwork>
</figure> </figure>
<t>
<t>
A TSN-aware MPLS (DetNet) node implementation must supp ort the A TSN-aware MPLS (DetNet) node implementation must supp ort the
Stream Identification TSN component for recognizing flo Stream identification TSN component for recognizing flo
ws. ws.
</t> </t>
<t> <t>
A Stream identification component must be able to instantiate A Stream identification component must be able to instantiate
the following functions (1) Active Destination MAC and VLAN the following functions: (1) Active Destination MAC and VLAN
Stream identification function, Stream identification function,
(2) Mask-and-Match Stream identification function and (2) Mask-and-Match Stream identification function, and
(3) the related managed objects in Clause 9 of (3) the related managed objects in Clause 9 of
<xref target="IEEE8021CB"/> and <xref target="IEEE8021CB" format="default"/> and
<xref target="IEEEP8021CBdb"/>. <xref target="IEEEP8021CBdb" format="default"/>.
</t> </t>
<t> <t>
A TSN-aware MPLS (DetNet) node implementation must supp ort the A TSN-aware MPLS (DetNet) node implementation must supp ort the
Sequencing function and the Sequence encode/decode func tion as Sequencing function and the Sequence encode/decode func tion as
defined in Clause 7.4 and 7.6 of <xref target="IEEE802 1CB"/> defined in Clauses 7.4 and 7.6 of <xref target="IEEE802 1CB" format="default"/>
in order for FRER to be used inside the TSN sub-network . in order for FRER to be used inside the TSN sub-network .
</t> </t>
<t> <t>
The Sequence encode/decode function must support the Redundancy The Sequence encode/decode function must support the Redundancy
tag (R-TAG) format as per Clause 7.8 of <xref tag (R-TAG) format as per Clause 7.8 of <xref target="IEEE8021CB"
target="IEEE8021CB"/>. format="default"/>.
</t> </t>
<t> <t>
A TSN-aware MPLS (DetNet) node implementation must supp ort the A TSN-aware MPLS (DetNet) node implementation must supp ort the
Stream splitting Stream splitting
function and the Individual recovery function as define d in function and the Individual recovery function as define d in
Clause 7.7 and 7.5 of <xref target="IEEE8021CB"/> Clauses 7.5 and 7.7 of <xref target="IEEE8021CB" format ="default"/>
in order for that node to be a replication or eliminati on in order for that node to be a replication or eliminati on
point for FRER. point for FRER.
</t> </t>
</section> </section>
<section title="Service protection within the TSN sub-network"> <section numbered="true" toc="default">
<t> <name>Service Protection within the TSN Sub-network</name>
TSN Streams supporting DetNet flows may use Frame Replication <t>
and Elimination for Redundancy (FRER) as defined in Clause 8. of TSN Streams supporting DetNet flows may use FRER as defined in Cla
<xref target="IEEE8021CB"/> based on the use 8 of
<xref target="IEEE8021CB" format="default"/> based on t
he
loss service requirements of the TSN Stream, which is derived loss service requirements of the TSN Stream, which is derived
from the DetNet service requirements of the DetNet mapped flow. from the DetNet service requirements of the DetNet mapped flow.
The specific operation of FRER is not modified by the use of The specific operation of FRER is not modified by the use of
DetNet and follows <xref target="IEEE8021CB"/>. DetNet and follows <xref target="IEEE8021CB" format="default"/>.
</t> </t>
<t> <t>
FRER function and the provided service recovery is available FRER function and the provided service recovery is available
only within the TSN sub-network as the TSN Stream-ID and the TSN only within the TSN sub-network as the TSN Stream-ID and the TSN
sequence number are not valid outside the sub-network. An MPLS sequence number are not valid outside the sub-network. An MPLS
(DetNet) node represents a L3 border and as such it terminates (DetNet) node represents an L3 border, and as such, it terminates
all related information elements encoded in the L2 frames. all related information elements encoded in the L2 frames.
</t> </t>
<t> <t>
As the Stream-ID and the TSN sequence number are paired As the Stream-ID and the TSN sequence number are paired
with the with
similar MPLS flow parameters, FRER can be combined with PREOF similar MPLS flow parameters, FRER can be combined with PREOF
functions. Such service protection interworking scenari os may functions. Such service protection interworking scenari os may
require to move sequence number fields among TSN (L2) a require moving sequence number fields among TSN (L2) an
nd PW d PW
(MPLS) encapsulations and they are left for further stu (MPLS) encapsulations, and they are left for further st
dy. udy.
</t> </t>
</section> </section>
<section title="Aggregation during DetNet flow to TSN Stream ma <section numbered="true" toc="default">
pping"> <name>Aggregation during DetNet Flow to TSN Stream Mapping</name>
<t> <t>
Implementation of this document shall use management and Implementation of this document shall use management and
control information to map a DetNet flow to a TSN control information to map a DetNet flow to a TSN
Stream. N:1 mapping (aggregating DetNet flows in a single Stream. N:1 mapping (aggregating DetNet flows in a single
TSN Stream) shall be supported. The management or control TSN Stream) shall be supported. The management or control
function that provisions flow mapping shall ensure that function that provisions flow mapping shall ensure that
adequate resources are allocated and configured to provid e adequate resources are allocated and configured to provid e
proper service requirements of the mapped flows. proper service requirements of the mapped flows.
</t> </t>
</section> </section>
</section> </section>
<!-- ============================================================= -->
<section title="Management and Control Implications"> <section numbered="true" toc="default">
<t> <name>Management and Control Implications</name>
DetNet flow and TSN Stream mapping related information ar <t>
e Information related to DetNet flow and TSN Stream mapping
is
required only for TSN-aware MPLS (DetNet) nodes. From the required only for TSN-aware MPLS (DetNet) nodes. From the
Data Plane perspective there is no practical difference data plane perspective, there is no practical difference
based on the origin of flow mapping related information based on the origin of flow-mapping-related information
(management plane or control plane). (management plane or control plane).
</t> </t>
<t> <t>
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 TSN: configure DetNet MPLS over TSN:
<list style="symbols"> </t>
<t>DetNet MPLS related configuration information accord <ul spacing="normal">
ing to the <li>DetNet MPLS-related configuration information according to the
DetNet role of the DetNet MPLS node, as per DetNet role of the DetNet MPLS node, as per
<xref target="RFC8964"/>. </t> <xref target="RFC8964" format="default"/>. </li>
<t>TSN related configuration information according to t <li>TSN-related configuration information according to the
he
TSN role of the DetNet MPLS node, as per TSN role of the DetNet MPLS node, as per
<xref target="IEEE8021Q"/>, <xref target="IEEE80 <xref target="IEEE8021Q" format="default"/>, <xr
21CB"/> and ef target="IEEE8021CB" format="default"/>, and
<xref target="IEEEP8021CBdb"/>. </t> <xref target="IEEEP8021CBdb" format="default"/>. </l
<t>Mapping between DetNet MPLS flow(s) (label information: i>
A-labels, S-labels and F-labels as defined in <li>Mapping between a DetNet MPLS flow(s) (label information:
<xref target="RFC8964"/>) and TSN A-Labels, S-Labels, and F-Labels as defined in
Stream(s) (as stream identification information defined <xref target="RFC8964" format="default"/>) and a TSN
in Stream(s) (as Stream identification information defined
<xref target="IEEEP8021CBdb"/>). in
Note, that managed objects for TSN Stream identificatio <xref target="IEEEP8021CBdb" format="default"/>).
n can be Note that managed objects for TSN Stream identification
found in <xref target="IEEEP8021CBcv"/>. can be
</t> found in <xref target="IEEEP8021CBcv" format="default"/
</list> >.
</li>
</ul>
<t>
This information must be provisioned per DetNet flow. This information must be provisioned per DetNet flow.
</t> </t>
<t> <t>
Mappings between DetNet and TSN management and control pl anes are Mappings between DetNet and TSN management and control pl anes are
out of scope of the document. Some of the challenges are out of scope of this document. Some of the challenges are
highlighted below. highlighted below.
</t> </t>
<t> <t>
TSN-aware MPLS DetNet nodes are members of both the DetNe t TSN-aware MPLS DetNet nodes are members of both the DetNe t
domain and the TSN sub-network. Within the TSN domain and the TSN sub-network. Within the TSN
sub-network the TSN-aware MPLS (DetNet) node has a TSN-aw sub-network, the TSN-aware MPLS (DetNet) node has a TSN-a
are ware
Talker/Listener role, so TSN specific management and Talker/Listener role, so TSN-specific management and
control plane functionalities must be implemented. There control plane functionalities must be implemented. There
are many similarities in the management plane techniques are many similarities in the management plane techniques
used in DetNet and TSN, but that is not the case for the used in DetNet and TSN, but that is not the case for the
control plane protocols. For example, RSVP-TE and MSRP control plane protocols. For example, RSVP-TE and the
(Multiple Stream Registration Protocol) Multiple Stream Registration Protocol (MSRP)
behaves differently. Therefore management and control behave differently. Therefore, management and control pla
plane design is an important aspect of scenarios, where ne
design are important aspects of scenarios where
mapping between DetNet and TSN is required. mapping between DetNet and TSN is required.
</t> </t>
<t> <t>
In order to use a TSN sub-network between DetNet nodes, In order to use a TSN sub-network between DetNet nodes,
DetNet specific information must be converted to TSN DetNet-specific information must be converted to information specif
sub-network specific ones. DetNet flow ID and flow related ic to the TSN
sub-network. DetNet flow ID and flow-related
parameters/requirements must be converted to a TSN Stream parameters/requirements must be converted to a TSN Stream
ID and stream related parameters/requirements. Note that, ID and stream-related parameters/requirements.
as the TSN sub-network is just a portion of the end-2-end
DetNet path (i.e., a single hop from MPLS perspective), some Note that,
as the TSN sub-network is just a portion of the end-to-end
DetNet path (i.e., a single hop from the MPLS perspective), some
parameters (e.g., delay) may differ significantly. Other parameters (e.g., delay) may differ significantly. Other
parameters (like bandwidth) also may have to be tuned due parameters (like bandwidth) also may have to be tuned due
to the L2 encapsulation used within the TSN sub-network. to the L2 encapsulation used within the TSN sub-network.
</t> </t>
<t> <t>
In some cases it may be challenging to determine some TSN In some cases, it may be challenging to determine some TSN-Stream-r
Stream related information. For example, on a TSN-aware MPLS elated
information. For example, on a TSN-aware MPLS
(DetNet) node that acts as a Talker, it is quite obvious (DetNet) node that acts as a Talker, it is quite obvious
which DetNet node is the Listener of the mapped TSN stream which DetNet node is the Listener of the mapped TSN Stream
(i.e., the MPLS Next-Hop). However it may be not trivial to (i.e., the MPLS next hop). However, it may be not trivial to
locate the point/interface where that Listener is locate the point/interface where that Listener is
connected to the TSN sub-network. Such attributes may connected to the TSN sub-network. Such attributes may
require interaction between control and management plane require interaction between control and management plane
functions and between DetNet and TSN domains. functions and between DetNet and TSN domains.
</t> </t>
<t> <t>
Mapping between DetNet flow identifiers and TSN Stream Mapping between DetNet flow identifiers and TSN Stream
identifiers, if not provided explicitly, can be done by a identifiers, if not provided explicitly, can be done by a
TSN-aware MPLS (DetNet) node locally based on information TSN-aware MPLS (DetNet) node locally based on information
provided for configuration of the TSN Stream provided for configuration of the TSN Stream
identification functions (Mask-and-match Stream identification identification functions (Mask-and-Match Stream identification
and Active Stream identification function). and active Stream identification).
</t> </t>
<t> <t>
Triggering the setup/modification of a TSN Stream in the Triggering the setup/modification of a TSN Stream in the
TSN sub-network is an example where management and/or TSN sub-network is an example where management and/or
control plane interactions are required between the DetNet control plane interactions are required between the DetNet
and TSN sub-network. TSN-unaware MPLS (DetNet) nodes make and TSN sub-network. TSN-unaware MPLS (DetNet) nodes make
such a triggering even more complicated as they are fully such a triggering even more complicated as they are fully
unaware of the sub-network and run independently. unaware of the sub-network and run independently.
</t> </t>
<t> <t>
Configuration of TSN specific functions (e.g., FRER) Configuration of TSN-specific functions (e.g., FRER)
inside the TSN sub-network is a TSN domain specific decision inside the TSN sub-network is a TSN-domain-specific decision
and may not be visible in the DetNet domain. Service protection and may not be visible in the DetNet domain. Service protection
interworking scenarios are left for further study. interworking scenarios are left for further study.
</t> </t>
</section> </section>
<!-- ===================================================================== -->
<section title="Security Considerations"> <section numbered="true" toc="default">
<t> <name>Security Considerations</name>
<t>
Security considerations for DetNet are described in detail in Security considerations for DetNet are described in detail in
<xref target="I-D.ietf-detnet-security"/>. General security considerati <xref target="I-D.ietf-detnet-security" format="default"/>. General sec
ons urity considerations
are described in <xref target="RFC8655"/>. are described in <xref target="RFC8655" format="default"/>.
DetNet MPLS data plane specific considerations are summarized in Considerations specific to the DetNet MPLS data plane are summarized in
<xref target="RFC8964"/>. <xref target="RFC8964" format="default"/>.
This section considers exclusively security considerations which are This section considers exclusively security considerations that are
specific to the DetNet MPLS over TSN sub-network scenario. specific to the DetNet MPLS over TSN sub-network scenario.
</t> </t>
<t> <t>
The sub-network between DetNet nodes needs to be subject to appropriate The sub-network between DetNet nodes needs to be subject to appropriate
confidentiality. Additionally, knowledge of what DetNet/TSN services ar e confidentiality. Additionally, knowledge of what DetNet/TSN services ar e
provided by a sub-network may supply information that can be used in a provided by a sub-network may supply information that can be used in a
variety of security attacks. The ability to modify information exchange s variety of security attacks. The ability to modify information exchange s
between connected DetNet nodes may result in bogus operations. Therefor e, between connected DetNet nodes may result in bogus operations. Therefor e,
it is important that the interface between DetNet nodes and TSN it is important that the interface between DetNet nodes and the TSN
sub-network are subject to authorization, authentication, and encryptio n. sub-network are subject to authorization, authentication, and encryptio n.
</t> </t>
<t> <t>
The TSN sub-network operates at Layer-2 so various security mechanisms The TSN sub-network operates at Layer 2, so various security mechanisms
defined by IEEE can be used to secure the connection between the DetNet defined by IEEE can be used to secure the connection between the DetNet
nodes (e.g., encryption may be provided using MACSec nodes (e.g., encryption may be provided using MACsec
<xref target="IEEE802.1AE-2018"/>). <xref target="IEEE802.1AE-2018" format="default"/>).
</t> </t>
</section> </section>
<section anchor="iana" numbered="true" toc="default">
<name>IANA Considerations</name>
<t>
This document has no IANA actions.
</t>
</section>
<section anchor="iana" title="IANA Considerations"> </middle>
<t> <back>
This document makes no IANA requests.
</t>
</section>
<section anchor="acks" title="Acknowledgements"> <displayreference target="I-D.ietf-detnet-security" to="DETNET-SECURITY"/>
<t>
The authors wish to thank Norman Finn, Lou Berger, Craig Gunther,
Christophe Mangin and Jouni Korhonen for their various contributi
ons
to this work.
</t>
</section>
</middle>
<back> <references>
<references title="Normative References"> <name>References</name>
<!-- &rfc2119; --> <references>
<?rfc include="reference.RFC.3031"?> <name>Normative References</name>
<!-- <?rfc include="reference.RFC.8174"?> -->
<?rfc include="reference.RFC.8655"?>
<?rfc include="reference.RFC.8964"?>
<reference anchor="IEEE8021CB" <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
target="http://standards.ieee.org/about/get/"> C.3031.xml"/>
<front> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF
<title>Standard for Local and metropolitan area networks - C.8655.xml"/>
Frame Replication and Elimination for Reliability <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
(IEEE Std 802.1CB-2017)</title> FC.8964.xml"/>
<author>
<organization>IEEE 802.1</organization>
</author>
<date year="2017"/>
</front>
<format type="PDF" target="http://standards.ieee.org/about/get/"/>
</reference>
<reference anchor="IEEEP8021CBdb" <reference anchor="IEEE8021CB" target="https://ieeexplore.ieee.org/docum
target="http://www.ieee802.org/1/files/private/db-drafts/d1/802 ent/8091139">
-1CBdb-d1-0.pdf"> <front>
<front> <title>IEEE Standard for Local and metropolitan area networks--Frame
<title>Extended Stream identification functions</title> Replication and Elimination for Reliability</title>
<author initials="C. M." surname="Mangin" fullname="Christophe Mangin" <author>
> <organization>IEEE</organization>
<organization>IEEE 802.1</organization> </author>
</author> <date month="October" year="2017"/>
<date month="September" year="2020"/> </front>
</front> <seriesInfo name="DOI" value="10.1109/IEEESTD.2017.8091139"/>
<seriesInfo name="IEEE P802.1CBdb /D1.0" value="P802.1CBdb"/> <refcontent>IEEE Std 802.1CB-2017</refcontent>
<format type="PDF" target="http://www.ieee802.org/1/files/private/db-dra </reference>
fts/d1/802-1CBdb-d1-0.pdf"/>
</reference>
</references> <reference anchor="IEEEP8021CBdb" target="https://1.ieee802.org/tsn/802-1cbdb/">
<references title="Informative References"> <front>
<!-- <?rfc include="reference.I-D.ietf-detnet-ip"?> --> <title>Draft Standard for Local and metropolitan area networks -—
<?rfc include="reference.I-D.ietf-detnet-security"?> Frame Replication and Elimination for Reliability -— Amendment:
Extended Stream Identification Functions</title>
<author>
<organization>IEEE</organization>
</author>
<date month="April" year="2021"/>
</front>
<refcontent>IEEE P802.1CBdb / D1.3</refcontent>
</reference>
</references>
<references>
<reference anchor="IEEE802.1AE-2018" <name>Informative References</name>
target="https://ieeexplore.ieee.org/document/8585421">
<front>
<title>IEEE Std 802.1AE-2018 MAC Security (MACsec)</title>
<author>
<organization>IEEE Standards Association</organization>
</author>
<date year="2018" />
</front>
</reference>
<reference anchor="IEEE8021Q" <!-- [I-D.ietf-detnet-security-15] RFC-EDITOR -->
target="http://standards.ieee.org/about/get/"> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.i
<front> etf-detnet-security.xml"/>
<title>Standard for Local and metropolitan area networks--Bridges
and Bridged Networks (IEEE Std 802.1Q-2018)</title>
<author>
<organization>IEEE 802.1</organization>
</author>
<date year="2018"/>
</front>
<format type="PDF" target="http://standards.ieee.org/about/get/"/>
</reference>
<reference anchor="IEEEP8021CBcv" <reference anchor="IEEE802.1AE-2018" target="https://ieeexplore.ieee.org
target="https://www.ieee802.org/1/files/private/cv-drafts/d0/80 /document/8585421">
2-1CBcv-d0-4.pdf"> <front>
<front> <title>IEEE Standard for Local and metropolitan area networks-Media
<title>FRER YANG Data Model and Management Information Base Module</ti Access Control (MAC) Security</title>
tle> <author>
<author initials="S." surname="Kehrer" fullname="Stephan Kehrer"> <organization>IEEE</organization>
<organization>IEEE 802.1</organization> </author>
</author> <date month="December" year="2018"/>
<date month="August" year="2020"/> </front>
</front> <seriesInfo name="DOI" value="10.1109/IEEESTD.2018.8585421"/>
<seriesInfo name="IEEE P802.1CBcv /D0.4" value="P802.1CBcv"/> <refcontent>IEEE Std 802.1AE-2018</refcontent>
<format type="PDF" target="https://www.ieee802.org/1/files/private/cv-dr </reference>
afts/d0/802-1CBcv-d0-4.pdf"/>
</reference> <reference anchor="IEEE8021Q" target="https://ieeexplore.ieee.org/docume
nt/8403927/">
<front>
<title>IEEE Standard for Local and metropolitan area networks--Bridg
es
and Bridged Networks</title>
<author>
<organization>IEEE</organization>
</author>
<date month="July" year="2018"/>
</front>
<seriesInfo name="DOI" value="10.1109/IEEESTD.2018.8403927"/>
<refcontent>IEEE Std 802.1Q-2018</refcontent>
</reference>
<reference anchor="IEEEP8021CBcv" target="https://1.ieee802.org/tsn/802-
1cbcv/">
<front>
<title>Draft Standard for Local and metropolitan area networks -- Fr
ame Replication and Elimination for Reliability -- Amendment: Information Model,
YANG Data Model and Management Information Base Module</title>
<author>
<organization>IEEE 802.1</organization>
</author>
<date month="February" year="2021"/>
</front>
<refcontent>IEEE P802.1CBcv, Draft 1.1</refcontent>
</reference>
</references>
</references> </references>
</back> <section anchor="acks" numbered="false" toc="default">
<name>Acknowledgements</name>
<t>
The authors wish to thank <contact fullname="Norman Finn"/>, <co
ntact fullname="Lou Berger"/>, <contact fullname="Craig Gunther"/>,
<contact fullname="Christophe Mangin"/>, and <contact fullname=
"Jouni Korhonen"/> for their various contributions
to this work.
</t>
</section>
</back>
</rfc> </rfc>
 End of changes. 108 change blocks. 
485 lines changed or deleted 502 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/