draft-ietf-detnet-mpls-over-tsn-01.txt   draft-ietf-detnet-mpls-over-tsn-02.txt 
DetNet B. Varga, Ed. DetNet B. Varga, Ed.
Internet-Draft J. Farkas Internet-Draft J. Farkas
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: April 29, 2020 A. Malis Expires: September 7, 2020 A. Malis
Independent Independent
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
October 27, 2019 March 6, 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-01 draft-ietf-detnet-mpls-over-tsn-02
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.
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.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 April 29, 2020. This Internet-Draft will expire on September 7, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
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 . . . . . . . . . . . . . . . . . . 4 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 . . . 5
4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 7 4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 7
4.2. TSN requirements of MPLS DetNet nodes . . . . . . . . . . 7 4.2. TSN requirements of MPLS DetNet nodes . . . . . . . . . . 7
4.3. Service protection within the TSN sub-network . . . . . . 9 4.3. Service protection within the TSN sub-network . . . . . . 9
4.4. Aggregation during DetNet flow to TSN Stream mapping . . 9 4.4. Aggregation during DetNet flow to TSN Stream mapping . . 9
5. Management and Control Implications . . . . . . . . . . . . . 9 5. Management and Control Implications . . . . . . . . . . . . . 9
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 . . . . . . . . . . . . . . . . . 11 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 General background and concepts of DetNet can be found in [RFC8655].
[I-D.ietf-detnet-architecture].
The DetNet Architecture decomposes the DetNet related data plane The DetNet Architecture decomposes the DetNet related data plane
functions into two sub-layers: a service sub-layer and a forwarding functions into two sub-layers: a service sub-layer and a forwarding
sub-layer. The service sub-layer is used to provide DetNet service sub-layer. The service sub-layer is used to provide DetNet service
protection and reordering. The forwarding sub-layer is used to protection and reordering. The forwarding sub-layer is used to
provides congestion protection (low loss, assured latency, and provides congestion protection (low loss, assured latency, and
limited reordering) leveraging MPLS Traffic Engineering mechanisms. limited reordering) leveraging MPLS Traffic Engineering mechanisms.
[I-D.ietf-detnet-mpls] specifies the DetNet data plane operation for [I-D.ietf-detnet-mpls] specifies the DetNet data plane operation for
MPLS-based Packet Switched Network (PSN). MPLS encapsulated DetNet MPLS-based Packet Switched Network (PSN). MPLS encapsulated DetNet
flows can be carried over network technologies that can provide the flows can be carried over network technologies that can provide the
DetNet required level of service. This document focuses on the DetNet required level of service. This document focuses on the
scenario where MPLS (DetNet) nodes are interconnected by a IEEE 802.1 scenario where MPLS (DetNet) nodes are interconnected by a IEEE 802.1
TSN sub-network. TSN sub-network.
2. Terminology 2. Terminology
[Editor's note: Needs clean up.].
2.1. Terms Used in This Document 2.1. Terms Used in This Document
This document uses the terminology established in the DetNet This document uses the terminology established in the DetNet
architecture [I-D.ietf-detnet-architecture] and architecture [RFC8655] and [I-D.ietf-detnet-mpls], and the reader is
[I-D.ietf-detnet-mpls], and the reader is assumed to be familiar with assumed to be familiar with that document and its terminology.
that document and its terminology.
2.2. Abbreviations 2.2. Abbreviations
The following abbreviations are used in this document: The following abbreviations are used in this document:
CW Control Word. CW Control Word.
DetNet Deterministic Networking. DetNet Deterministic Networking.
DF DetNet Flow. DF DetNet Flow.
skipping to change at page 6, line 11 skipping to change at page 5, line 38
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 As described in the DetNet architecture [RFC8655] and also
[I-D.ietf-detnet-architecture] and also illustrated here in Figure 1 illustrated here in Figure 1 a sub-network provides from MPLS
a sub-network provides from MPLS perspective a single hop connection perspective a single hop connection between MPLS (DetNet) nodes.
between MPLS (DetNet) nodes. Functions used for resource allocation Functions used for resource allocation and explicit routes are
and explicit routes are treated as domain internal functions and does treated as domain internal functions and does not require function
not require function interworking across the DetNet MPLS network and interworking across the DetNet MPLS network and the TSN sub-network.
the TSN sub-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 2 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.
skipping to change at page 9, line 50 skipping to change at page 9, line 37
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
[Editor's note: This section covers management/control plane related
implications of creation, mapping, removal of TSN Stream IDs, their
related parameters and, when needed, the configuration of FRER.]
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).
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
skipping to change at page 11, line 13 skipping to change at page 10, line 45
independently. independently.
Configuration of TSN specific functions (e.g., FRER) inside the TSN Configuration of TSN specific functions (e.g., FRER) inside the TSN
sub-network is a TSN domain specific decision and may not be visible sub-network is a TSN domain specific decision and may not be visible
in the DetNet domain. Service protection interworking scenarios are in the DetNet domain. Service protection interworking scenarios are
left for further study. left for further study.
6. Security Considerations 6. Security Considerations
The security considerations of DetNet in general are discussed in The security considerations of DetNet in general are discussed in
[I-D.ietf-detnet-architecture] and [I-D.ietf-detnet-security]. [RFC8655] and [I-D.ietf-detnet-security]. DetNet IP data plane
DetNet IP data plane specific considerations are summarized in specific considerations are summarized in [I-D.ietf-detnet-ip].
[I-D.ietf-detnet-ip]. Encryption may provided by an underlying sub- Encryption may provided by an underlying sub-net using MACSec
net using MACSec [IEEE802.1AE-2018] for DetNet IP over TSN flows. [IEEE802.1AE-2018] for DetNet IP over TSN flows.
7. IANA Considerations 7. IANA Considerations
This document makes no IANA requests. This document makes no IANA requests.
8. Acknowledgements 8. Acknowledgements
The authors wish to thank Norman Finn, Lou Berger, Craig Gunther, The authors wish to thank Norman Finn, Lou Berger, Craig Gunther,
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]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS",
draft-ietf-detnet-mpls-05 (work in progress), February
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
[G.8275.1]
International Telecommunication Union, "Precision time
protocol telecom profile for phase/time synchronization
with full timing support from the network", ITU-T
G.8275.1/Y.1369.1 G.8275.1, June 2016,
<https://www.itu.int/rec/T-REC-G.8275.1/en>.
[G.8275.2]
International Telecommunication Union, "Precision time
protocol telecom profile for phase/time synchronization
with partial timing support from the network", ITU-T
G.8275.2/Y.1369.2 G.8275.2, June 2016,
<https://www.itu.int/rec/T-REC-G.8275.2/en>.
[I-D.ietf-detnet-architecture]
Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", draft-ietf-
detnet-architecture-13 (work in progress), May 2019.
[I-D.ietf-detnet-ip] [I-D.ietf-detnet-ip]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane: IP", and S. Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-
draft-ietf-detnet-ip-01 (work in progress), July 2019. ip-05 (work in progress), February 2020.
[I-D.ietf-detnet-mpls]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS",
draft-ietf-detnet-mpls-01 (work in progress), July 2019.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell,
J., Austad, H., Stanton, K., and N. Finn, "Deterministic J., Austad, H., and N. Finn, "Deterministic Networking
Networking (DetNet) Security Considerations", draft-ietf- (DetNet) Security Considerations", draft-ietf-detnet-
detnet-security-05 (work in progress), August 2019. security-08 (work in progress), February 2020.
[IEEE1588]
IEEE, "IEEE 1588 Standard for a Precision Clock
Synchronization Protocol for Networked Measurement and
Control Systems Version 2", 2008.
[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 Finn, N., "Draft Standard for Local and metropolitan area
networks - Seamless Redundancy", IEEE P802.1CB networks - Seamless Redundancy", IEEE P802.1CB
/D2.1 P802.1CB, December 2015, /D2.1 P802.1CB, December 2015,
skipping to change at page 13, line 23 skipping to change at page 12, line 28
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/>. 2014)", 2014, <http://standards.ieee.org/about/get/>.
[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 /D0.2 P802.1CBdb, August 2019,
<http://www.ieee802.org/1/files/private/cb-drafts/d2/802- <http://www.ieee802.org/1/files/private/cb-drafts/d2/802-
1CB-d2-1.pdf>. 1CB-d2-1.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. 19 change blocks. 
63 lines changed or deleted 37 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/