draft-ietf-detnet-mpls-over-tsn-03.txt   draft-ietf-detnet-mpls-over-tsn-04.txt 
DetNet B. Varga, Ed. DetNet B. Varga, Ed.
Internet-Draft J. Farkas Internet-Draft J. Farkas
Intended status: Standards Track Ericsson Intended status: Informational Ericsson
Expires: December 10, 2020 A. Malis Expires: May 6, 2021 A. Malis
Malis Consulting Malis Consulting
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
June 8, 2020 November 2, 2020
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-03 draft-ietf-detnet-mpls-over-tsn-04
Abstract Abstract
This document specifies the Deterministic Networking MPLS data plane This document specifies the Deterministic Networking MPLS data plane
when operating over a TSN sub-network. when operating over a TSN sub-network. This document does not define
new procedures or processes. Whenever this document makes
requirements statements or recommendations, these are taken 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 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 December 10, 2020. This Internet-Draft will expire on May 6, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 15 skipping to change at page 2, line 17
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
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. DetNet MPLS Data Plane Overview . . . . . . . . . . . . . . . 4 3. DetNet MPLS Data Plane Overview . . . . . . . . . . . . . . . 4
4. DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks . . . 5 4. DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks . . . 4
4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 7 4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 6
4.2. TSN requirements of MPLS DetNet nodes . . . . . . . . . . 7 4.2. TSN requirements of MPLS DetNet nodes . . . . . . . . . . 6
4.3. Service protection within the TSN sub-network . . . . . . 9 4.3. Service protection within the TSN sub-network . . . . . . 8
4.4. Aggregation during DetNet flow to TSN Stream mapping . . 9 4.4. Aggregation during DetNet flow to TSN Stream mapping . . 8
5. Management and Control Implications . . . . . . . . . . . . . 9 5. Management and Control Implications . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 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 . . . . . . . . . . . . . . . . . 12 9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 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 a low a network to DetNet flows. DetNet provides these flows with a 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 [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
skipping to change at page 4, line 31 skipping to change at page 4, line 31
enable correct DetNet flow identification regardless of which input enable correct DetNet flow identification regardless of which input
interface or LSP the packet arrives on. The service sub-layer interface or LSP the packet arrives on. The service sub-layer
functions (i.e., PREOF) use a DetNet control word (d-CW). functions (i.e., PREOF) use a DetNet control word (d-CW).
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 forwarding The forwarding sub-layer is supported by one or more forwarding
labels (F-Labels). labels (F-Labels).
Edge Transit Relay
Node Node Node
(T-PE) (LSR) (S-PE)
+---------+
<--|Svc Proxy|-- End to End Service ----------->
+---------+ +---------+
|IP | |Svc|<-- DetNet flow ---| Service |--->
+---+ +---+ +---------+ +---------+
|Fwd| |Fwd| | Fwd | |Fwd| |Fwd|
+-.-+ +-.-+ +--.----.-+ +-.-+ +-.-+
: / ,-----. \ : Link : :
.....+ +-[TSN Sub]-+ +........+ +.....
[Network]
`-----'
|<----------- LSP ---------->| |<--- LSP -->|
|<------------- DetNet MPLS ------------
Figure 1: Part of a Simple DetNet MPLS Network using a TSN sub-net
Figure 1 illustrates an extract of a DetNet enabled MPLS network.
Edge/relay nodes sit at MPLS LSP boundaries and transit nodes are
LSRs. In this figure, two MPLS nodes (the edge node and the transit
node) are interconnected by a TSN sub-network.
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 enabled and process d-CWs, S-Labels and F-labels as needed. MPLS DetNet
DetNet nodes can enhance the reliability of delivery by enabling the nodes and transit nodes include DetNet forwarding sub-layer
replication of packets where multiple copies, possibly over multiple
paths, are forwarded through the DetNet domain. They can also
eliminate surplus previously replicated copies of DetNet packets.
MPLS (DetNet) nodes also include DetNet forwarding sub-layer
functions, support for notably explicit routes, and resources functions, support for notably 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-
layer processing.
DetNet transit nodes reside wholly within a DetNet domain, and also MPLS (DetNet) nodes and transit nodes interconnected by a TSN sub-
provide DetNet forwarding sub-layer functions in accordance with the network are the primary focus of this document. The mapping of
performance required by a DetNet flow carried over an LSP. Unlike DetNet MPLS flows to TSN streams and TSN protection mechanisms are
other DetNet node types, transit nodes provide no service sub-layer covered in Section 4.
processing.
4. DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks 4. DetNet MPLS Operation Over IEEE 802.1 TSN Sub-Networks
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, what maintains common architecture for both Layer 2 and Layer 3, what 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:
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] and also As described in the DetNet architecture [RFC8655] a sub-network
illustrated here in Figure 1 a sub-network provides from MPLS provides from MPLS perspective a single hop connection between MPLS
perspective a single hop connection between MPLS (DetNet) nodes. (DetNet) nodes. Functions used for resource allocation and explicit
Functions used for resource allocation and explicit routes are routes are treated as domain internal functions and does not require
treated as domain internal functions and does not require function function interworking across the DetNet MPLS network and the TSN sub-
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 case of the service protection function due to the similarities of
the DetNet PREOF and TSN FRER functions some level of interworking is the DetNet PREOF and TSN FRER functions some level of interworking is
possible. However, such interworking is out-of-scope in this possible. However, such interworking is out-of-scope in this
document and left for further study. document and left for further study.
Figure 2 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* |-->
+----------+ +----------+ +----------+ +----------+
|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
Figure 2: 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 The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1
Working Group have defined (and are defining) a number of amendments Working Group have defined (and are defining) a number of amendments
to IEEE 802.1Q [IEEE8021Q] that provide zero congestion loss and to IEEE 802.1Q [IEEE8021Q] that provide zero congestion loss and
bounded latency in bridged networks. Furthermore IEEE 802.1CB bounded latency in bridged networks. Furthermore IEEE 802.1CB
[IEEE8021CB] defines frame replication and elimination functions for [IEEE8021CB] defines frame replication and elimination functions for
reliability that should prove both compatible with and useful to, reliability that should prove both compatible with and useful to,
DetNet networks. All these functions have to identify flows those DetNet networks. All these functions have to identify flows those
require TSN treatment. require TSN treatment.
skipping to change at page 7, line 34 skipping to change at page 6, line 49
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
processing functions MUST be compliant with the relevant IEEE 802.1 processing functions must be compliant with the relevant IEEE 802.1
standards. standards.
From the TSN sub-network perspective MPLS (DetNet) nodes are treated From the TSN sub-network perspective MPLS (DetNet) nodes are treated
as Talker or Listener, that may be (1) TSN-unaware or (2) TSN-aware. as Talker or Listener, that may be (1) TSN-unaware or (2) TSN-aware.
In cases of TSN-unaware MPLS DetNet nodes the TSN relay nodes within In cases of TSN-unaware MPLS 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 MPLS flow (e.g., MAC translation, VLAN-ID setting, Sequence DetNet MPLS 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
MPLS DetNet nodes in this document. MPLS DetNet nodes in this document.
MPLS (DetNet) nodes being TSN-aware can be treated as a combination MPLS (DetNet) nodes being TSN-aware can be treated as a combination
of a TSN-unaware Talker/Listener and a TSN-Relay, as shown in of a TSN-unaware Talker/Listener and a TSN-Relay, as shown in
Figure 3. In such cases the MPLS (DetNet) node must provide the TSN Figure 2. In such cases the MPLS (DetNet) node must provide the TSN
sub-network specific Ethernet encapsulation over the link(s) towards sub-network specific Ethernet encapsulation over the link(s) towards
the sub-network. the sub-network.
MPLS (DetNet) MPLS (DetNet)
Node Node
<----------------------------------> <---------------------------------->
+----------+ +----------+
<--| Service* |-- DetNet flow ------------------ <--| Service* |-- DetNet flow ------------------
+----------+ +----------+
skipping to change at page 8, line 27 skipping to change at page 7, line 43
\__________/ \ \______ \__________/ \ \______
\_________ \_________
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
Figure 3: MPLS (DetNet) Node with TSN Functions Figure 2: MPLS (DetNet) Node with TSN Functions
A TSN-aware MPLS (DetNet) node impementations MUST support the Stream A TSN-aware MPLS (DetNet) node impementations 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 IEEE
802.1CB [IEEE8021CB] and IEEE P802.1CBdb [IEEEP8021CBdb]. 802.1CB [IEEE8021CB] and IEEE P802.1CBdb [IEEEP8021CBdb].
A TSN-aware MPLS (DetNet) node implementations MUST support the A TSN-aware MPLS (DetNet) node implementations 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 IEEE 802.1CB [IEEE8021CB] if FRER is
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 IEEE 802.1CB [IEEE8021CB].
A TSN-aware MPLS (DetNet) node implementations MUST support the A TSN-aware MPLS (DetNet) node implementations must support the
Stream splitting function and the Individual recovery function as Stream splitting function and the Individual recovery function as
defined in Clause 7.7 and 7.5 of IEEE 802.1CB [IEEE8021CB] when the defined in Clause 7.7 and 7.5 of IEEE 802.1CB [IEEE8021CB] when the
node is a replication or elimination point for FRER. node is a 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 IEEE
802.1CB [IEEE8021CB] based on the loss service requirements of the 802.1CB [IEEE8021CB] based on the loss service requirements of the
TSN Stream, which is derived from the DetNet service requirements of TSN Stream, which is derived from the DetNet service requirements of
skipping to change at page 9, line 28 skipping to change at page 8, line 41
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 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 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
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).
skipping to change at page 10, line 11 skipping to change at page 9, line 24
o TSN related configuration information according to the TSN role of o TSN related configuration information according to the TSN role of
the DetNet MPLS node, as per [IEEE8021Q], [IEEE8021CB] and the DetNet MPLS node, as per [IEEE8021Q], [IEEE8021CB] and
[IEEEP8021CBdb]. [IEEEP8021CBdb].
o Mapping between DetNet MPLS flow(s) (label information: A-labels, o Mapping between DetNet MPLS flow(s) (label information: A-labels,
S-labels and F-labels as defined in [I-D.ietf-detnet-mpls]) and S-labels and F-labels as defined in [I-D.ietf-detnet-mpls]) and
TSN Stream(s) (as stream identification information defined in TSN Stream(s) (as stream identification information defined in
[IEEEP8021CBdb]). Note, that managed objects for TSN Stream [IEEEP8021CBdb]). Note, that managed objects for TSN Stream
identification can be found in [IEEEP8021CBcv]. identification can be 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
of scope of the document. Some of the challanges are highligthed
below.
TSN-aware MPLS DetNet nodes are member of both the DetNet domain and TSN-aware MPLS DetNet nodes are member 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 behaves differently.
Therefore management and control plane design is an important aspect Therefore management and control plane design is an important aspect
of scenarios, where mapping between DetNet and TSN is required. of scenarios, where mapping between DetNet and TSN is required.
skipping to change at page 10, line 46 skipping to change at page 10, line 15
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)
node locally based on information provided for configuration of the node locally based on information provided for configuration of the
TSN Stream identification functions (Mask-and-match Stream TSN Stream identification functions (Mask-and-match Stream
identification and active Stream identification function). identification and Active Stream identification 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 MPLS (DetNet) nodes make such a triggering even more TSN-unaware MPLS (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
skipping to change at page 12, line 8 skipping to change at page 11, line 22
Christophe Mangin and Jouni Korhonen for their various contributions Christophe Mangin and Jouni Korhonen for their various contributions
to this work. to this work.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S., Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S.,
and J. Korhonen, "DetNet Data Plane: MPLS", draft-ietf- and J. Korhonen, "DetNet Data Plane: MPLS", draft-ietf-
detnet-mpls-06 (work in progress), April 2020. detnet-mpls-13 (work in progress), October 2020.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[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>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-detnet-ip] [I-D.ietf-detnet-ip]
Varga, B., Farkas, J., Berger, L., Fedyk, D., and S. Varga, B., Farkas, J., Berger, L., Fedyk, D., and S.
Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-ip-06 Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-ip-07
(work in progress), April 2020. (work in progress), July 2020.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Mizrahi, T. and E. Grossman, "Deterministic Networking Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic
(DetNet) Security Considerations", draft-ietf-detnet- Networking (DetNet) Security Considerations", draft-ietf-
security-10 (work in progress), May 2020. detnet-security-12 (work in progress), October 2020.
[IEEE802.1AE-2018] [IEEE802.1AE-2018]
IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC
Security (MACsec)", 2018, Security (MACsec)", 2018,
<https://ieeexplore.ieee.org/document/8585421>. <https://ieeexplore.ieee.org/document/8585421>.
[IEEE8021CB] [IEEE8021CB]
Finn, N., "Draft Standard for Local and metropolitan area IEEE 802.1, "Standard for Local and metropolitan area
networks - Seamless Redundancy", IEEE P802.1CB networks - Frame Replication and Elimination for
/D2.1 P802.1CB, December 2015, Reliability (IEEE Std 802.1CB-2017)", 2017,
<http://www.ieee802.org/1/files/private/cb-drafts/d2/802- <http://standards.ieee.org/about/get/>.
1CB-d2-1.pdf>.
[IEEE8021Q] [IEEE8021Q]
IEEE 802.1, "Standard for Local and metropolitan area IEEE 802.1, "Standard for Local and metropolitan area
networks--Bridges and Bridged Networks (IEEE Std 802.1Q- networks--Bridges and Bridged Networks (IEEE Std 802.1Q-
2014)", 2014, <http://standards.ieee.org/about/get/>. 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.3 P802.1CBcv, May 2020, /D0.4 P802.1CBcv, August 2020,
<http://www.ieee802.org/1/files/private/cv-drafts/d0/802- <https://www.ieee802.org/1/files/private/cv-drafts/d0/802-
1CBcv-d0-3.pdf>. 1CBcv-d0-4.pdf>.
[IEEEP8021CBdb] [IEEEP8021CBdb]
Mangin, C., "Extended Stream identification functions", Mangin, C., "Extended Stream identification functions",
IEEE P802.1CBdb /D0.2 P802.1CBdb, August 2019, IEEE P802.1CBdb /D1.0 P802.1CBdb, September 2020,
<http://www.ieee802.org/1/files/private/cb-drafts/d2/802- <http://www.ieee802.org/1/files/private/db-drafts/d1/802-
1CB-d2-1.pdf>. 1CBdb-d1-0.pdf>.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655, "Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019, DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>. <https://www.rfc-editor.org/info/rfc8655>.
Authors' Addresses Authors' Addresses
Balazs Varga (editor) Balazs Varga (editor)
Ericsson Ericsson
 End of changes. 33 change blocks. 
89 lines changed or deleted 68 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/