draft-ietf-detnet-mpls-over-tsn-06.txt   draft-ietf-detnet-mpls-over-tsn-07.txt 
DetNet B. Varga, Ed. DetNet B. Varga, Ed.
Internet-Draft J. Farkas Internet-Draft J. Farkas
Intended status: Informational Ericsson Intended status: Informational Ericsson
Expires: August 16, 2021 A. Malis Expires: August 23, 2021 A. Malis
Malis Consulting Malis Consulting
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
February 12, 2021 February 19, 2021
DetNet Data Plane: MPLS over IEEE 802.1 Time-Sensitive Networking (TSN) DetNet Data Plane: MPLS over IEEE 802.1 Time-Sensitive Networking (TSN)
draft-ietf-detnet-mpls-over-tsn-06 draft-ietf-detnet-mpls-over-tsn-07
Abstract Abstract
This document specifies the Deterministic Networking MPLS data plane 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 new procedures or sub-network. This document does not define new procedures or
processes. Whenever this document makes requirements statements or processes. Whenever this document makes statements or
recommendations, these are taken from normative text in the recommendations, these are taken from normative text in the
referenced RFCs. referenced RFCs.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 16, 2021. This Internet-Draft will expire on August 23, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2021 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
skipping to change at page 2, line 16 skipping to change at page 2, line 16
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
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3 2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
3. DetNet MPLS Data Plane Overview . . . . . . . . . . . . . . . 4 3. DetNet MPLS Data Plane Overview . . . . . . . . . . . . . . . 3
4. DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks . . . 4 4. DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks . . . 4
4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 6 4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 6
4.2. TSN requirements of MPLS DetNet nodes . . . . . . . . . . 6 4.2. TSN requirements of MPLS DetNet nodes . . . . . . . . . . 6
4.3. Service protection within the TSN sub-network . . . . . . 8 4.3. Service protection within the TSN sub-network . . . . . . 8
4.4. Aggregation during DetNet flow to TSN Stream mapping . . 8 4.4. Aggregation during DetNet flow to TSN Stream mapping . . 8
5. Management and Control Implications . . . . . . . . . . . . . 8 5. Management and Control Implications . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . 11 9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
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 with low a network to DetNet flows. DetNet provides these flows with low
packet loss rates and assured maximum end-to-end delivery latency. packet loss rate and assured maximum end-to-end delivery latency.
General background and concepts of DetNet can be found in [RFC8655]. General background and concepts of DetNet can be found in [RFC8655].
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
provide congestion protection (low loss, assured latency, and limited provide congestion protection (low loss, assured latency, and limited
reordering) leveraging MPLS Traffic Engineering mechanisms. reordering) leveraging MPLS Traffic Engineering mechanisms.
[RFC8964] specifies the DetNet data plane operation for MPLS-based [RFC8964] specifies the DetNet data plane operation for MPLS-based
skipping to change at page 3, line 20 skipping to change at page 3, line 20
architecture [RFC8655] and [RFC8964]. TSN specific terms are defined architecture [RFC8655] and [RFC8964]. TSN specific terms are defined
in the TSN TG of IEEE 802.1 Working Group. The reader is assumed to in the TSN TG of IEEE 802.1 Working Group. The reader is assumed to
be familiar with these documents and their terminology. be familiar with these documents and their terminology.
2.2. Abbreviations 2.2. Abbreviations
The following abbreviations are used in this document: The following abbreviations are used in this document:
A-Label Aggregation label, a special case of an S-Label. A-Label Aggregation label, a special case of an S-Label.
CW Control Word. d-CW DetNet Control Word.
DetNet Deterministic Networking. DetNet Deterministic Networking.
DF DetNet Flow.
F-Label Forwarding label that identifies the LSP used by a F-Label Forwarding label that identifies the LSP used by a
DetNet flow. DetNet flow.
FRER Frame Replication and Elimination for Redundancy (TSN FRER Frame Replication and Elimination for Redundancy (TSN
function). function).
L2 Layer 2. L2 Layer 2.
L3 Layer 3. L3 Layer 3.
LSR Label Switching Router.
MPLS Multiprotocol Label Switching. MPLS Multiprotocol Label Switching.
PE Provider Edge.
PREOF Packet Replication, Elimination and Ordering Functions. PREOF Packet Replication, Elimination and Ordering Functions.
PSN Packet Switched Network. PSN Packet Switched Network.
PW PseudoWire. PW PseudoWire.
S-PE Switching Provider Edge. RSVP-TE Resource Reservation Protocol - Traffic Engineering.
S-Label Service label. S-Label Service label.
T-PE Terminating Provider Edge.
TSN Time-Sensitive Network. TSN Time-Sensitive Network.
3. DetNet MPLS Data Plane Overview 3. DetNet MPLS Data Plane Overview
The basic approach defined in [RFC8964] supports the DetNet service The basic approach defined in [RFC8964] supports the DetNet service
sub-layer based on existing pseudowire (PW) encapsulations and sub-layer based on existing pseudowire (PW) encapsulations and
mechanisms, and supports the DetNet forwarding sub-layer based on mechanisms, and supports the DetNet forwarding sub-layer based on
existing MPLS Traffic Engineering encapsulations and mechanisms. existing MPLS Traffic Engineering encapsulations and mechanisms.
A node operating on a DetNet flow in the Detnet service sub-layer, A node operating on a DetNet flow in the Detnet service sub-layer,
skipping to change at page 4, line 35 skipping to change at page 4, line 28
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 routes. is responsible for providing resource allocation and explicit routes.
The forwarding sub-layer is supported by one or more F-Labels. The forwarding sub-layer is supported by one or more F-Labels.
DetNet edge/relay nodes are DetNet service sub-layer aware, DetNet edge/relay nodes are DetNet service sub-layer aware,
understand the particular needs of DetNet flows and provide both understand the particular needs of DetNet flows and provide both
DetNet service and forwarding sub-layer functions. They add, remove DetNet service and forwarding sub-layer functions. They add, remove
and process d-CWs, S-Labels and F-labels as needed. MPLS DetNet and process d-CWs, S-Labels and F-labels as needed. MPLS DetNet
nodes and transit nodes include DetNet forwarding sub-layer nodes and transit nodes include DetNet forwarding sub-layer
functions, support for notably explicit routes, and resources functions, notably support for explicit routes, and resources
allocation to eliminate (or reduce) congestion loss and jitter. allocation to eliminate (or reduce) congestion loss and jitter.
Unlike other DetNet node types, transit nodes provide no service sub- Unlike other DetNet node types, transit nodes provide no service sub-
layer processing. layer processing.
MPLS (DetNet) nodes and transit nodes interconnected by a TSN sub- MPLS (DetNet) nodes and transit nodes interconnected by a TSN sub-
network are the primary focus of this document. The mapping of network are the primary focus of this document. The mapping of
DetNet MPLS flows to TSN streams and TSN protection mechanisms are DetNet MPLS flows to TSN streams and TSN protection mechanisms are
covered in Section 4. covered in Section 4.
4. DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks 4. DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks
skipping to change at page 5, line 12 skipping to change at page 5, line 8
o Service protection. o Service protection.
o Resource allocation. o Resource allocation.
o Explicit routes. o Explicit routes.
As described in the DetNet architecture [RFC8655] a sub-network As described in the DetNet architecture [RFC8655] a sub-network
provides from MPLS perspective a single hop connection between MPLS provides from MPLS perspective a single hop connection between MPLS
(DetNet) nodes. Functions used for resource allocation and explicit (DetNet) nodes. Functions used for resource allocation and explicit
routes are treated as domain internal functions and does not require routes are treated as domain internal functions and do not require
function interworking across the DetNet MPLS network and the TSN sub- function interworking across the DetNet MPLS network and the TSN sub-
network. network.
In case of the service protection function due to the similarities of In the case of the service protection function due to the
the DetNet PREOF and TSN FRER functions some level of interworking is similarities of the DetNet PREOF and TSN FRER functions some level of
possible. However, such interworking is out-of-scope in this interworking is possible. However, such interworking is out-of-scope
document and left for further study. in this document and left for further study.
Figure 1 illustrates a scenario, where two MPLS (DetNet) nodes are Figure 1 illustrates a scenario, where two MPLS (DetNet) nodes are
interconnected by a TSN sub-network. Node-1 is single homed and interconnected by a TSN sub-network. Node-1 is single homed and
Node-2 is dual-homed to the TSN sub-network. Node-2 is dual-homed to the TSN sub-network.
MPLS (DetNet) MPLS (DetNet) MPLS (DetNet) MPLS (DetNet)
Node-1 Node-2 Node-1 Node-2
+----------+ +----------+ +----------+ +----------+
<--| Service* |-- DetNet flow ---| Service* |--> <--| Service* |-- DetNet flow ---| Service* |-->
skipping to change at page 5, line 43 skipping to change at page 5, line 39
\ ,-------. / / \ ,-------. / /
+----[ 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
Figure 1: DetNet Enabled MPLS Network Over a TSN Sub-Network Figure 1: DetNet Enabled MPLS 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 those DetNet networks. All these functions have to identify flows those
require TSN treatment (i.e., applying TSN functions during require TSN treatment (i.e., applying TSN functions during
forwarding). forwarding).
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 (DetNet) flows via the protocol interworking function defined 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 MPLS (DetNet) flow to it can convert an ingress unicast MPLS (DetNet) flow to use a
use a specific Layer-2 multicast destination MAC address and a VLAN, specific Layer-2 multicast destination MAC address and a VLAN, in
in order to direct the packet through a specific path inside the order to direct the packet through a specific path inside the bridged
bridged network. A similar interworking function pair at the other network. A similar interworking function pair at the other end of
end of the TSN sub-network would restore the packet to its original the TSN sub-network would restore the packet to its original Layer-2
Layer-2 destination MAC address and VLAN. destination MAC address and VLAN.
Placement of TSN functions depends on the TSN capabilities of 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 nodes along the path. MPLS (DetNet) Nodes may or may not support TSN
functions. For a given TSN Stream (i.e., DetNet flow) an MPLS functions. For a given TSN Stream (i.e., DetNet flow) an MPLS
(DetNet) node is treated as a Talker or a Listener inside the TSN (DetNet) node is treated as a Talker or a Listener inside the TSN
sub-network. 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 MPLS flow to a TSN Stream is provided via the Mapping of a DetNet MPLS 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. The passive stream identification that operate at the frame level. The passive stream identification
function is used to catch the MPLS label(s) of a DetNet MPLS flow and function is used to catch the MPLS label(s) of a DetNet MPLS flow and
the active stream identification function is used to modify the the active stream identification function is used to modify the
Ethernet header according to the ID of the mapped TSN Stream. Ethernet header according to the ID of the mapped TSN Stream.
Clause 6.8 of IEEE P802.1CBdb [IEEEP8021CBdb] defines a Mask-and- Clause 6.8 of [IEEEP8021CBdb] defines a Mask-and-Match Stream
Match Stream identification function that can be used as a passive identification function that can be used as a passive function for
function for MPLS DetNet flows. MPLS DetNet 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, what can replace some Ethernet header
Ethernet header fields namely (1) the destination MAC-address, (2) fields namely (1) the destination MAC-address, (2) the VLAN-ID and
the VLAN-ID and (3) priority parameters with alternate values. (3) priority parameters with alternate values. Replacement is
Replacement is provided for the frame passed down the stack from the provided for the frame passed down the stack from the upper layers or
upper layers or up the stack from the lower layers. up the 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 a Listener to recover the
original addressing information. It can be used also in a TSN bridge original addressing information. It can be used also in a TSN bridge
that is providing translation as a proxy service for an End System. that is providing translation as a proxy service for an End System.
4.2. TSN requirements of MPLS DetNet nodes 4.2. TSN requirements of MPLS DetNet nodes
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 packet node using a TSN sub-network. The implementation of TSN packet
skipping to change at page 7, line 51 skipping to change at page 7, line 48
Note: * no service sub-layer required for transit nodes Note: * no service sub-layer required for transit nodes
Figure 2: MPLS (DetNet) Node with TSN Functions Figure 2: MPLS (DetNet) Node with TSN Functions
A TSN-aware MPLS (DetNet) node implementation must support the Stream A TSN-aware MPLS (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 functions (1) Active Destination MAC and VLAN Stream
identification function, (2) Mask-and-Match Stream identification identification function, (2) Mask-and-Match Stream identification
function and (3) the related managed objects in Clause 9 of IEEE function and (3) the related managed objects in Clause 9 of
802.1CB [IEEE8021CB] and IEEE P802.1CBdb [IEEEP8021CBdb]. [IEEE8021CB] and [IEEEP8021CBdb].
A TSN-aware MPLS (DetNet) node implementation must support the A TSN-aware MPLS (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 Clause 7.4 and 7.6 of [IEEE8021CB] in order for FRER to be
used inside the TSN sub-network. used inside 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 MPLS (DetNet) node implementation must support the Stream A TSN-aware MPLS (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 Clause 7.7 and 7.5 of [IEEE8021CB] in order for that node to be a
replication or elimination point for FRER. replication or 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 Frame Replication and
Elimination for Redundancy (FRER) as defined in Clause 8. of IEEE Elimination for Redundancy (FRER) as defined in Clause 8. of
802.1CB [IEEE8021CB] based on the loss service requirements of the [IEEE8021CB] based on the loss service requirements of the TSN
TSN Stream, which is derived from the DetNet service requirements of Stream, which is derived from the DetNet service requirements of the
the DetNet mapped flow. The specific operation of FRER is not DetNet mapped flow. The specific operation of FRER is not modified
modified by the use of DetNet and follows IEEE 802.1CB [IEEE8021CB]. by the use of DetNet and follows [IEEE8021CB].
FRER function and the provided service recovery is available only FRER function and the provided service recovery is available only
within the TSN sub-network as the TSN Stream-ID and the TSN sequence within the TSN sub-network as the TSN Stream-ID and the TSN sequence
number are not valid outside the sub-network. An MPLS (DetNet) node number are not valid outside the sub-network. An MPLS (DetNet) node
represents a L3 border and as such it terminates all related represents a L3 border and as such it terminates all related
information elements encoded in the L2 frames. information elements encoded in the L2 frames.
As the Stream-ID and the TSN sequence number are paired with the As the Stream-ID and the TSN sequence number are paired with the
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 scenarios may functions. Such service protection interworking scenarios may
require to move sequence number fields among TSN (L2) and PW (MPLS) require to move sequence number fields among TSN (L2) and PW (MPLS)
encapsulations and they are left for further study. encapsulations and they are left for further study.
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 Implementation 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 flow and TSN Stream mapping related information are required
only for TSN-aware MPLS (DetNet) nodes. From the Data Plane only for TSN-aware MPLS (DetNet) nodes. From the Data Plane
skipping to change at page 9, line 29 skipping to change at page 9, line 27
(as stream identification information defined in [IEEEP8021CBdb]). (as stream identification information defined in [IEEEP8021CBdb]).
Note, that managed objects for TSN Stream identification can be Note, that managed objects for TSN Stream identification can be
found in [IEEEP8021CBcv]. found in [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 challenges are highlighted of scope of the document. Some of the challenges are highlighted
below. below.
TSN-aware MPLS DetNet nodes are member of both the DetNet domain and TSN-aware MPLS DetNet nodes are members of both the DetNet domain and
the TSN sub-network. Within the TSN sub-network the TSN-aware MPLS the TSN sub-network. Within the TSN sub-network the TSN-aware MPLS
(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 MSRP (Multiple Stream
Therefore management and control plane design is an important aspect Registration Protocol) behaves differently. Therefore management and
of scenarios, where mapping between DetNet and TSN is required. 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 ones. DetNet flow ID and flow related parameters/requirements must
be converted to a TSN Stream ID and stream related parameters/ 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 end2end DetNet path (i.e., single hop from MPLS perspective), the end-2-end DetNet path (i.e., a single hop from MPLS 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 MPLS (DetNet) node related information. For example, on a TSN-aware MPLS (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 MPLS Next-Hop). However Listener of the mapped TSN stream (i.e., the MPLS Next-Hop). However
it may be not trivial to locate the point/interface where that it may be not 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 MPLS (DetNet) if not provided explicitly, can be done by a TSN-aware MPLS (DetNet)
skipping to change at page 11, line 36 skipping to change at page 11, line 36
Mangin, C., "Extended Stream identification functions", Mangin, C., "Extended Stream identification functions",
IEEE P802.1CBdb /D1.0 P802.1CBdb, September 2020, IEEE P802.1CBdb /D1.0 P802.1CBdb, September 2020,
<http://www.ieee802.org/1/files/private/db-drafts/d1/802- <http://www.ieee802.org/1/files/private/db-drafts/d1/802-
1CBdb-d1-0.pdf>. 1CBdb-d1-0.pdf>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, Label Switching Architecture", RFC 3031,
DOI 10.17487/RFC3031, January 2001, DOI 10.17487/RFC3031, January 2001,
<https://www.rfc-editor.org/info/rfc3031>. <https://www.rfc-editor.org/info/rfc3031>.
[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>.
[RFC8964] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., Bryant, [RFC8964] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., Bryant,
S., and J. Korhonen, "Deterministic Networking (DetNet) S., and J. Korhonen, "Deterministic Networking (DetNet)
Data Plane: MPLS", RFC 8964, DOI 10.17487/RFC8964, January Data Plane: MPLS", RFC 8964, DOI 10.17487/RFC8964, January
2021, <https://www.rfc-editor.org/info/rfc8964>. 2021, <https://www.rfc-editor.org/info/rfc8964>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic
Networking (DetNet) Security Considerations", draft-ietf- Networking (DetNet) Security Considerations", draft-ietf-
skipping to change at page 12, line 17 skipping to change at page 12, line 22
networks--Bridges and Bridged Networks (IEEE Std 802.1Q- networks--Bridges and Bridged Networks (IEEE Std 802.1Q-
2018)", 2018, <http://standards.ieee.org/about/get/>. 2018)", 2018, <http://standards.ieee.org/about/get/>.
[IEEEP8021CBcv] [IEEEP8021CBcv]
Kehrer, S., "FRER YANG Data Model and Management Kehrer, S., "FRER YANG Data Model and Management
Information Base Module", IEEE P802.1CBcv Information Base Module", IEEE P802.1CBcv
/D0.4 P802.1CBcv, August 2020, /D0.4 P802.1CBcv, August 2020,
<https://www.ieee802.org/1/files/private/cv-drafts/d0/802- <https://www.ieee802.org/1/files/private/cv-drafts/d0/802-
1CBcv-d0-4.pdf>. 1CBcv-d0-4.pdf>.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>.
Authors' Addresses Authors' Addresses
Balazs Varga (editor) Balazs Varga (editor)
Ericsson Ericsson
Magyar Tudosok krt. 11. Magyar Tudosok krt. 11.
Budapest 1117 Budapest 1117
Hungary Hungary
Email: balazs.a.varga@ericsson.com Email: balazs.a.varga@ericsson.com
 End of changes. 32 change blocks. 
65 lines changed or deleted 58 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/