draft-ietf-detnet-mpls-01.txt   draft-ietf-detnet-mpls-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: January 2, 2020 L. Berger Expires: April 18, 2020 L. Berger
D. Fedyk D. Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
A. Malis A. Malis
Independent
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
J. Korhonen J. Korhonen
July 1, 2019 October 16, 2019
DetNet Data Plane: MPLS DetNet Data Plane: MPLS
draft-ietf-detnet-mpls-01 draft-ietf-detnet-mpls-02
Abstract Abstract
This document specifies the Deterministic Networking data plane when This document specifies the Deterministic Networking data plane when
operating over an MPLS Packet Switched Networks. operating over an MPLS Packet Switched Networks.
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 38 skipping to change at page 1, line 39
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 January 2, 2020. This Internet-Draft will expire on April 18, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 5 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 5
3. DetNet MPLS Data Plane Overview . . . . . . . . . . . . . . . 5 3. DetNet MPLS Data Plane Overview . . . . . . . . . . . . . . . 5
3.1. Layers of DetNet Data Plane . . . . . . . . . . . . . . . 5 3.1. Layers of DetNet Data Plane . . . . . . . . . . . . . . . 5
3.2. DetNet MPLS Data Plane Scenarios . . . . . . . . . . . . 6 3.2. DetNet MPLS Data Plane Scenarios . . . . . . . . . . . . 6
4. MPLS-Based DetNet Data Plane Solution . . . . . . . . . . . . 8 4. MPLS-Based DetNet Data Plane Solution . . . . . . . . . . . . 8
4.1. DetNet Over MPLS Encapsulation Components . . . . . . . . 8 4.1. DetNet Over MPLS Encapsulation Components . . . . . . . . 8
4.2. MPLS Data Plane Encapsulation . . . . . . . . . . . . . . 9 4.2. MPLS Data Plane Encapsulation . . . . . . . . . . . . . . 9
skipping to change at page 3, line 33 skipping to change at page 3, line 38
over different network technologies is out of scope of this document. over different network technologies is out of scope of this document.
MPLS encapsulated DetNet flows can carry different types of traffic. MPLS encapsulated DetNet flows can carry different types of traffic.
The details of the types of traffic that are carried in DetNet are The details of the types of traffic that are carried in DetNet are
also out of scope of this document. An example of IP using DetNet also out of scope of this document. An example of IP using DetNet
MPLS sub-networks can be found in [I-D.ietf-detnet-ip]. DetNet MPLS MPLS sub-networks can be found in [I-D.ietf-detnet-ip]. DetNet MPLS
may use an associated controller and Operations, Administration, and may use an associated controller and Operations, Administration, and
Maintenance (OAM) functions that are defined outside of this Maintenance (OAM) functions that are defined outside of this
document. document.
Important background information common to all data planes for DetNet Background information common to all data planes for DetNet can be
can be found in the DetNet Data Plane Framework found in the DetNet Data Plane Framework
[I-D.ietf-detnet-data-plane-framework]. [I-D.ietf-detnet-data-plane-framework].
2. Terminology 2. Terminology
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 the the DetNet Data architecture [I-D.ietf-detnet-architecture] and the the DetNet Data
Plane Framework [I-D.ietf-detnet-data-plane-framework]. The reader Plane Framework [I-D.ietf-detnet-data-plane-framework]. The reader
is assumed to be familiar with these documents and any terminology is assumed to be familiar with these documents and any terminology
skipping to change at page 15, line 35 skipping to change at page 15, line 35
service requirements of the DetNet flow or flows carried in the LSPs service requirements of the DetNet flow or flows carried in the LSPs
represented by the F-Labels. This includes normal push, pop and swap represented by the F-Labels. This includes normal push, pop and swap
operations. Such processing is essentially the same type of operations. Such processing is essentially the same type of
processing provided for TE LSPs, although the specific service processing provided for TE LSPs, although the specific service
parameters, or traffic specification, can differ. When the DetNet parameters, or traffic specification, can differ. When the DetNet
service parameters of the app-flow or flows carried in an LSP service parameters of the app-flow or flows carried in an LSP
represented by an F-Label can be met by an exiting TE mechanism, the represented by an F-Label can be met by an exiting TE mechanism, the
forwarding sub-layer processing node MAY be a DetNet unaware, i.e., forwarding sub-layer processing node MAY be a DetNet unaware, i.e.,
standard, MPLS LSR. Such TE LSPs may provide LSP forwarding service standard, MPLS LSR. Such TE LSPs may provide LSP forwarding service
as defined in, but not limited to, [RFC3209], [RFC3270], [RFC3272], as defined in, but not limited to, [RFC3209], [RFC3270], [RFC3272],
[RFC3473], [RFC4875], [RFC5440], and [RFC6006]. [RFC3473], [RFC4875], [RFC5440], and [RFC8306].
More specifically, as mentioned above, the DetNet forwarding sub- More specifically, as mentioned above, the DetNet forwarding sub-
layer provides explicit routes and allocated resources, and F-Labels layer provides explicit routes and allocated resources, and F-Labels
are used to map to each. Explicit routes are supported based on the are used to map to each. Explicit routes are supported based on the
topmost (outermost) F-Label that is pushed or swapped and the LSP topmost (outermost) F-Label that is pushed or swapped and the LSP
that corresponds to this label. This topmost (outgoing) label MUST that corresponds to this label. This topmost (outgoing) label MUST
be associated with a provisioned outgoing interface and, for non- be associated with a provisioned outgoing interface and, for non-
point-to-point outgoing interfaces, a next hop LSR. Note that this point-to-point outgoing interfaces, a next hop LSR. Note that this
information MUST be provisioned via configuration or the controller information MUST be provisioned via configuration or the controller
plane. In the previously mentioned special case where there are no plane. In the previously mentioned special case where there are no
skipping to change at page 27, line 8 skipping to change at page 27, line 8
9.2. Informative References 9.2. Informative References
[I-D.ietf-detnet-architecture] [I-D.ietf-detnet-architecture]
Finn, N., Thubert, P., Varga, B., and J. Farkas, Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", draft-ietf- "Deterministic Networking Architecture", draft-ietf-
detnet-architecture-13 (work in progress), May 2019. detnet-architecture-13 (work in progress), May 2019.
[I-D.ietf-detnet-data-plane-framework] [I-D.ietf-detnet-data-plane-framework]
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 Bryant, S., and J. Korhonen, "DetNet Data Plane
Framework", draft-ietf-detnet-data-plane-framework-00 Framework", draft-ietf-detnet-data-plane-framework-02
(work in progress), May 2019. (work in progress), September 2019.
[I-D.ietf-detnet-ip]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane: IP",
draft-ietf-detnet-ip-01 (work in progress), July 2019.
[I-D.ietf-detnet-ip-over-mpls] [I-D.ietf-detnet-ip-over-mpls]
Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S., Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
and J. Korhonen, "DetNet Data Plane: IP over MPLS", draft- Bryant, S., and J. Korhonen, "DetNet Data Plane: IP over
ietf-detnet-ip-over-mpls-00 (work in progress), May 2019. MPLS", draft-ietf-detnet-ip-over-mpls-01 (work in
progress), July 2019.
[I-D.ietf-detnet-mpls-over-tsn] [I-D.ietf-detnet-mpls-over-tsn]
Varga, B., Farkas, J., Malis, A., Bryant, S., and J. Varga, B., Farkas, J., Malis, A., Bryant, S., and J.
Korhonen, "DetNet Data Plane: MPLS over IEEE 802.1 Time Korhonen, "DetNet Data Plane: MPLS over IEEE 802.1 Time
Sensitive Networking (TSN)", draft-ietf-detnet-mpls-over- Sensitive Networking (TSN)", draft-ietf-detnet-mpls-over-
tsn-00 (work in progress), May 2019. tsn-00 (work in progress), May 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., Stanton, K., and N. Finn, "Deterministic
Networking (DetNet) Security Considerations", draft-ietf- Networking (DetNet) Security Considerations", draft-ietf-
detnet-security-04 (work in progress), March 2019. detnet-security-05 (work in progress), August 2019.
[I-D.ietf-spring-segment-routing-mpls] [I-D.ietf-spring-segment-routing-mpls]
Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., Bashandy, A., Filsfils, C., Previdi, S., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing with MPLS Litkowski, S., and R. Shakir, "Segment Routing with MPLS
data plane", draft-ietf-spring-segment-routing-mpls-22 data plane", draft-ietf-spring-segment-routing-mpls-22
(work in progress), May 2019. (work in progress), May 2019.
[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,
skipping to change at page 29, line 5 skipping to change at page 29, line 9
[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>.
[RFC6003] Papadimitriou, D., "Ethernet Traffic Parameters", [RFC6003] Papadimitriou, D., "Ethernet Traffic Parameters",
RFC 6003, DOI 10.17487/RFC6003, October 2010, RFC 6003, DOI 10.17487/RFC6003, October 2010,
<https://www.rfc-editor.org/info/rfc6003>. <https://www.rfc-editor.org/info/rfc6003>.
[RFC6006] Zhao, Q., Ed., King, D., Ed., Verhaeghe, F., Takeda, T.,
Ali, Z., and J. Meuric, "Extensions to the Path
Computation Element Communication Protocol (PCEP) for
Point-to-Multipoint Traffic Engineering Label Switched
Paths", RFC 6006, DOI 10.17487/RFC6006, September 2010,
<https://www.rfc-editor.org/info/rfc6006>.
[RFC6073] Martini, L., Metz, C., Nadeau, T., Bocci, M., and M. [RFC6073] Martini, L., Metz, C., Nadeau, T., Bocci, M., and M.
Aissaoui, "Segmented Pseudowire", RFC 6073, Aissaoui, "Segmented Pseudowire", RFC 6073,
DOI 10.17487/RFC6073, January 2011, DOI 10.17487/RFC6073, January 2011,
<https://www.rfc-editor.org/info/rfc6073>. <https://www.rfc-editor.org/info/rfc6073>.
[RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and [RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and
L. Yong, "The Use of Entropy Labels in MPLS Forwarding", L. Yong, "The Use of Entropy Labels in MPLS Forwarding",
RFC 6790, DOI 10.17487/RFC6790, November 2012, RFC 6790, DOI 10.17487/RFC6790, November 2012,
<https://www.rfc-editor.org/info/rfc6790>. <https://www.rfc-editor.org/info/rfc6790>.
[RFC8306] Zhao, Q., Dhody, D., Ed., Palleti, R., and D. King,
"Extensions to the Path Computation Element Communication
Protocol (PCEP) for Point-to-Multipoint Traffic
Engineering Label Switched Paths", RFC 8306,
DOI 10.17487/RFC8306, November 2017,
<https://www.rfc-editor.org/info/rfc8306>.
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
skipping to change at page 29, line 44 skipping to change at page 30, line 4
Magyar Tudosok krt. 11. Magyar Tudosok krt. 11.
Budapest 1117 Budapest 1117
Hungary Hungary
Email: janos.farkas@ericsson.com Email: janos.farkas@ericsson.com
Lou Berger Lou Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Email: lberger@labn.net Email: lberger@labn.net
Don Fedyk Don Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Email: dfedyk@labn.net Email: dfedyk@labn.net
Andrew G. Malis Andrew G. Malis
Futurewei Technologies Independent
Email: agmalis@gmail.com Email: agmalis@gmail.com
Stewart Bryant Stewart Bryant
Futurewei Technologies Futurewei Technologies
Email: stewart.bryant@gmail.com Email: stewart.bryant@gmail.com
Jouni Korhonen Jouni Korhonen
 End of changes. 16 change blocks. 
23 lines changed or deleted 30 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/