draft-ietf-detnet-tsn-vpn-over-mpls-04.txt   draft-ietf-detnet-tsn-vpn-over-mpls-05.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: May 6, 2021 A. Malis Expires: June 16, 2021 A. Malis
Malis Consulting Malis Consulting
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
D. Fedyk D. Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
November 2, 2020 December 13, 2020
DetNet Data Plane: IEEE 802.1 Time Sensitive Networking over MPLS DetNet Data Plane: IEEE 802.1 Time Sensitive Networking over MPLS
draft-ietf-detnet-tsn-vpn-over-mpls-04 draft-ietf-detnet-tsn-vpn-over-mpls-05
Abstract Abstract
This document specifies the Deterministic Networking data plane when This document specifies the Deterministic Networking data plane when
TSN networks are interconnected over a DetNet MPLS Network. TSN networks are interconnected over a DetNet MPLS 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 37 skipping to change at page 1, line 37
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 May 6, 2021. This Internet-Draft will expire on June 16, 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 25 skipping to change at page 2, line 25
3. IEEE 802.1 TSN Over DetNet MPLS Data Plane Scenario . . . . . 4 3. IEEE 802.1 TSN Over DetNet MPLS Data Plane Scenario . . . . . 4
4. DetNet MPLS Data Plane . . . . . . . . . . . . . . . . . . . 6 4. DetNet MPLS Data Plane . . . . . . . . . . . . . . . . . . . 6
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. TSN over DetNet MPLS Encapsulation . . . . . . . . . . . 7 4.2. TSN over DetNet MPLS Encapsulation . . . . . . . . . . . 7
5. TSN over MPLS Data Plane Procedures . . . . . . . . . . . . . 8 5. TSN over MPLS Data Plane Procedures . . . . . . . . . . . . . 8
5.1. Edge Node TSN Procedures . . . . . . . . . . . . . . . . 8 5.1. Edge Node TSN Procedures . . . . . . . . . . . . . . . . 8
5.2. Edge Node DetNet Service Proxy Procedures . . . . . . . . 9 5.2. Edge Node DetNet Service Proxy Procedures . . . . . . . . 9
5.3. Edge Node DetNet Service and Forwarding Sub-Layer 5.3. Edge Node DetNet Service and Forwarding Sub-Layer
Procedures . . . . . . . . . . . . . . . . . . . . . . . 10 Procedures . . . . . . . . . . . . . . . . . . . . . . . 10
6. Controller Plane (Management and Control) Considerations . . 11 6. Controller Plane (Management and Control) Considerations . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . 13 10.1. Normative References . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . 14 10.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
The Time-Sensitive Networking Task Group (TSN TG) within IEEE 802.1 The Time-Sensitive Networking Task Group (TSN TG) within IEEE 802.1
Working Group deals with deterministic services through IEEE 802 Working Group deals with deterministic services through IEEE 802
networks. Deterministic Networking (DetNet) defined by IETF is a networks. Deterministic Networking (DetNet) defined by IETF is a
service that can be offered by a L3 network to DetNet flows. General service that can be offered by a L3 network to DetNet flows. General
background and concepts of DetNet can be found in [RFC8655]. background and concepts of DetNet can be found in [RFC8655].
This document specifies the use of a DetNet MPLS network to This document specifies the use of a DetNet MPLS network to
interconnect TSN nodes/network segments. DetNet MPLS data plane is interconnect TSN nodes/network segments. DetNet MPLS data plane is
defined in [I-D.ietf-detnet-mpls]. defined in [I-D.ietf-detnet-mpls].
2. Terminology 2. Terminology
2.1. Terms Used in This Document 2.1. Terms Used in This Document
This document uses the terminology and concepts established in the This document uses the terminology and concepts established in the
DetNet architecture [RFC8655] and DetNet architecture [RFC8655] and [RFC8938], and
[I-D.ietf-detnet-data-plane-framework], and [I-D.ietf-detnet-mpls]. [I-D.ietf-detnet-mpls]. The reader is assumed to be familiar with
The reader is assumed to be familiar with these documents and their these documents and their terminology.
terminology.
2.2. Abbreviations 2.2. Abbreviations
The following abbreviations are used in this document: The following abbreviations are used in this document:
AC Attachment Circuit. AC Attachment Circuit.
CE Customer Edge equipment. CE Customer Edge equipment.
CW Control Word. CW Control Word.
skipping to change at page 10, line 30 skipping to change at page 10, line 30
configured to provide proper service requirements of the mapped configured to provide proper service requirements of the mapped
flows. flows.
Due to the (intentional) similarities of the DetNet PREOF and TSN Due to the (intentional) similarities of the DetNet PREOF and TSN
FRER functions service protection function interworking is possible FRER functions service protection function interworking is possible
between the TSN and the DetNet domains. Such service protection between the TSN and the DetNet domains. Such service protection
interworking scenarios MAY require to copy sequence number fields interworking scenarios MAY require to copy sequence number fields
from TSN (L2) to PW (MPLS) encapsulation. However, such interworking from TSN (L2) to PW (MPLS) encapsulation. However, such interworking
is out-of-scope in this document and left for further study. is out-of-scope in this document and left for further study.
A MPLS DetNet flow is configured to carry any number of TSN flows.
The DetNet flow specific bandwidth profile SHOULD match the required
bandwidth of the App-flow aggregate.
5.3. Edge Node DetNet Service and Forwarding Sub-Layer Procedures 5.3. Edge Node DetNet Service and Forwarding Sub-Layer Procedures
In the design of [I-D.ietf-detnet-mpls] an MPLS service label (the In the design of [I-D.ietf-detnet-mpls] an MPLS service label (the
S-Label), similar to a pseudowire (PW) label [RFC3985], is used to S-Label), similar to a pseudowire (PW) label [RFC3985], is used to
identify both the DetNet flow identity and the payload MPLS payload identify both the DetNet flow identity and the payload MPLS payload
type. The DetNet sequence number is carried in the DetNet Control type. The DetNet sequence number is carried in the DetNet Control
word (d-CW) which carries the Data/OAM discriminator as well. In word (d-CW) which carries the Data/OAM discriminator as well. In
[I-D.ietf-detnet-mpls] two sequence number sizes are supported: a 16 [I-D.ietf-detnet-mpls] two sequence number sizes are supported: a 16
bit sequence number and a 28 bit sequence number. bit sequence number and a 28 bit sequence number.
PREOF functions and the provided service recovery is available only PREOF functions and the provided service recovery is available only
within the DetNet domain as the DetNet flow-ID and the DetNet within the DetNet domain as the DetNet flow-ID and the DetNet
sequence number are not valid outside the DetNet network. MPLS sequence number are not valid outside the DetNet network. MPLS
(DetNet) Edge node terminates all related information elements (DetNet) Edge node terminates all related information elements
encoded in the MPLS labels. encoded in the MPLS labels.
The LSP used to forward the DetNet packet may be of any type (MPLS-
LDP, MPLS-TE, MPLS-TP [RFC5921], or MPLS-SR [RFC8660]). The LSP
(F-Label) label and/or the S-Label may be used to indicate the queue
processing as well as the forwarding parameters.
When a PE receives a packet from the Service Proxy function it MUST When a PE receives a packet from the Service Proxy function it MUST
add to the packet the DetNet flow-ID specific S-label and create a handle the packet as defined in [I-D.ietf-detnet-mpls].
d-CW. The PE MUST forward the packet according to the configured
DetNet Service and Forwarding sub-layer rules to other PE nodes.
When a PE receives an MPLS packet from a remote PE, then, after When a PE receives an MPLS packet from a remote PE, then, after
processing the MPLS label stack, if the top MPLS label ends up being processing the MPLS label stack, if the top MPLS label ends up being
a DetNet S-label that was advertised by this node, then the PE MUST a DetNet S-label that was advertised by this node, then the PE MUST
forward the packet according to the configured DetNet Service and forward the packet according to the configured DetNet Service and
Forwarding sub-layer rules to other PE nodes or via the Detnet Forwarding sub-layer rules to other PE nodes or via the Detnet
Service Proxy function towards locally connected CE(s). Service Proxy function towards locally connected CE(s).
For further details on DetNet Service and Forwarding sub-layers see For further details on DetNet Service and Forwarding sub-layers see
[I-D.ietf-detnet-mpls]. [I-D.ietf-detnet-mpls].
skipping to change at page 14, line 7 skipping to change at page 13, line 40
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>.
10.2. Informative References 10.2. Informative References
[I-D.ietf-detnet-data-plane-framework]
Varga, B., Farkas, J., Berger, L., Malis, A., and S.
Bryant, "DetNet Data Plane Framework", draft-ietf-detnet-
data-plane-framework-06 (work in progress), May 2020.
[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-
detnet-security-12 (work in progress), October 2020. detnet-security-12 (work in progress), October 2020.
[IEEE802.1AE-2018]
IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC
Security (MACsec)", 2018,
<https://ieeexplore.ieee.org/document/8585421>.
[IEEE8021CB] [IEEE8021CB]
IEEE 802.1, "Standard for Local and metropolitan area IEEE 802.1, "Standard for Local and metropolitan area
networks - Frame Replication and Elimination for networks - Frame Replication and Elimination for
Reliability (IEEE Std 802.1CB-2017)", 2017, Reliability (IEEE Std 802.1CB-2017)", 2017,
<http://standards.ieee.org/about/get/>. <http://standards.ieee.org/about/get/>.
[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-
2018)", 2018, <http://standards.ieee.org/about/get/>. 2018)", 2018, <http://standards.ieee.org/about/get/>.
skipping to change at page 14, line 44 skipping to change at page 14, line 21
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>.
[RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation [RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation
Edge-to-Edge (PWE3) Architecture", RFC 3985, Edge-to-Edge (PWE3) Architecture", RFC 3985,
DOI 10.17487/RFC3985, March 2005, DOI 10.17487/RFC3985, March 2005,
<https://www.rfc-editor.org/info/rfc3985>. <https://www.rfc-editor.org/info/rfc3985>.
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, DOI 10.17487/RFC4301,
December 2005, <https://www.rfc-editor.org/info/rfc4301>.
[RFC5921] Bocci, M., Ed., Bryant, S., Ed., Frost, D., Ed., Levrau, [RFC5921] Bocci, M., Ed., Bryant, S., Ed., Frost, D., Ed., Levrau,
L., and L. Berger, "A Framework for MPLS in Transport L., and L. Berger, "A Framework for MPLS in Transport
Networks", RFC 5921, DOI 10.17487/RFC5921, July 2010, Networks", RFC 5921, DOI 10.17487/RFC5921, July 2010,
<https://www.rfc-editor.org/info/rfc5921>. <https://www.rfc-editor.org/info/rfc5921>.
[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>.
[RFC8660] Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S., [RFC8660] Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing with the MPLS Data Plane", RFC 8660, Routing with the MPLS Data Plane", RFC 8660,
DOI 10.17487/RFC8660, December 2019, DOI 10.17487/RFC8660, December 2019,
<https://www.rfc-editor.org/info/rfc8660>. <https://www.rfc-editor.org/info/rfc8660>.
[RFC8938] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., and S.
Bryant, "Deterministic Networking (DetNet) Data Plane
Framework", RFC 8938, DOI 10.17487/RFC8938, November 2020,
<https://www.rfc-editor.org/info/rfc8938>.
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
Janos Farkas Janos Farkas
Ericsson Ericsson
Magyar Tudosok krt. 11. Magyar Tudosok krt. 11.
Budapest 1117 Budapest 1117
Hungary Hungary
Email: janos.farkas@ericsson.com Email: janos.farkas@ericsson.com
Andrew G. Malis Andrew G. Malis
Malis Consulting Malis Consulting
 End of changes. 15 change blocks. 
38 lines changed or deleted 16 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/