--- 1/draft-ietf-detnet-mpls-03.txt 2019-11-21 18:13:36.797486663 -0800 +++ 2/draft-ietf-detnet-mpls-04.txt 2019-11-21 18:13:36.857488200 -0800 @@ -1,26 +1,26 @@ DetNet B. Varga, Ed. Internet-Draft J. Farkas Intended status: Standards Track Ericsson -Expires: April 29, 2020 L. Berger +Expires: May 24, 2020 L. Berger D. Fedyk LabN Consulting, L.L.C. A. Malis Independent S. Bryant Futurewei Technologies J. Korhonen - October 27, 2019 + November 21, 2019 DetNet Data Plane: MPLS - draft-ietf-detnet-mpls-03 + draft-ietf-detnet-mpls-04 Abstract This document specifies the Deterministic Networking data plane when operating over an MPLS Packet Switched Networks. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -28,21 +28,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 May 24, 2020. Copyright Notice Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -88,22 +88,21 @@ 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 9.1. Normative References . . . . . . . . . . . . . . . . . . 25 9.2. Informative References . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 1. Introduction Deterministic Networking (DetNet) is a service that can be offered by a network to DetNet flows. DetNet provides these flows extremely low packet loss rates and assured maximum end-to-end delivery latency. - General background and concepts of DetNet can be found in - [I-D.ietf-detnet-architecture]. + General background and concepts of DetNet can be found in [RFC8655]. The DetNet Architecture models the DetNet related data plane functions decomposed into two sub-layers: a service sub-layer and a forwarding sub-layer. The service sub-layer is used to provide DetNet service functions such as protection and reordering. The forwarding sub-layer is used to provide forwarding assurance (low loss, assured latency, and limited reordering). This document specifies the DetNet data plane operation and the on- wire encapsulation of DetNet flows over an MPLS-based Packet Switched @@ -125,24 +124,23 @@ Background information common to all data planes for DetNet can be found in the DetNet Data Plane Framework [I-D.ietf-detnet-data-plane-framework]. 2. Terminology 2.1. Terms Used in This Document This document uses the terminology established in the DetNet - architecture [I-D.ietf-detnet-architecture] and the the DetNet Data - Plane Framework [I-D.ietf-detnet-data-plane-framework]. The reader - is assumed to be familiar with these documents and any terminology - defined therein. + architecture [RFC8655] and the the DetNet Data Plane Framework + [I-D.ietf-detnet-data-plane-framework]. The reader is assumed to be + familiar with these documents and any terminology defined therein. The following terminology is introduced in this document: F-Label A Detnet "forwarding" label that identifies the LSP used to forward a DetNet flow across an MPLS PSN, e.g., a hop-by-hop label used between label switching routers (LSR). S-Label A DetNet "service" label that is used between DetNet nodes that implement also the DetNet service sub-layer @@ -912,25 +910,25 @@ [RFC3270]. The Uniform, Pipe, and Short Pipe DiffServ tunneling and TTL processing models are described in [RFC3270] and [RFC3443] and MAY be used for MPLS LSPs supporting DetNet flows. MPLS ECN MAY also be used as defined in ECN [RFC5129] and updated by [RFC5462]. 4.6.2. Quality of Service In addition to explicit routes, and packet replication and elimination, described in Section 4 above, DetNet provides zero congestion loss and bounded latency and jitter. As described in - [I-D.ietf-detnet-architecture], there are different mechanisms that - maybe used separately or in combination to deliver a zero congestion - loss service. This includes Quality of Service (QoS) mechanisms at - the MPLS layer, that may be combined with the mechanisms defined by - the underlying network layer such as 802.1TSN. + [RFC8655], there are different mechanisms that maybe used separately + or in combination to deliver a zero congestion loss service. This + includes Quality of Service (QoS) mechanisms at the MPLS layer, that + may be combined with the mechanisms defined by the underlying network + layer such as 802.1TSN. Quality of Service (QoS) mechanisms for flow specific traffic treatment typically includes a guarantee/agreement for the service, and allocation of resources to support the service. Example QoS mechanisms include discrete resource allocation, admission control, flow identification and isolation, and sometimes path control, traffic protection, shaping, policing and remarking. Example protocols that support QoS control include Resource ReSerVation Protocol (RSVP) [RFC2205] (RSVP) and RSVP-TE [RFC3209] and [RFC3473]. The existing MPLS mechanisms defined to support CoS [RFC3270] can @@ -1072,23 +1070,22 @@ It is the responsibility of the DetNet controller plane to properly provision both flow identification information and the flow specific resources needed to provided the traffic treatment needed to meet each flow's service requirements. This applies for aggregated and individual flows. 6. Security Considerations Security considerations for DetNet are described in detail in [I-D.ietf-detnet-security]. General security considerations are - described in [I-D.ietf-detnet-architecture]. This section considers - exclusively security considerations which are specific to the DetNet - MPLS data plane. + described in [RFC8655]. This section considers exclusively security + considerations which are specific to the DetNet MPLS data plane. Security aspects which are unique to DetNet are those whose aim is to provide the specific quality of service aspects of DetNet, which are primarily to deliver data flows with extremely low packet loss rates and bounded end-to-end delivery latency. The primary considerations for the data plane is to maintain integrity of data and delivery of the associated DetNet service traversing the DetNet network. Application flows can be protected through whatever means is provided by the underlying technology. For @@ -1203,53 +1200,48 @@ (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field", RFC 5462, DOI 10.17487/RFC5462, February 2009, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . 9.2. Informative References - [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-data-plane-framework] Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., Bryant, S., and J. Korhonen, "DetNet Data Plane - Framework", draft-ietf-detnet-data-plane-framework-02 - (work in progress), September 2019. + Framework", draft-ietf-detnet-data-plane-framework-03 + (work in progress), October 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. + draft-ietf-detnet-ip-03 (work in progress), October 2019. [I-D.ietf-detnet-ip-over-mpls] Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., Bryant, S., and J. Korhonen, "DetNet Data Plane: IP over - MPLS", draft-ietf-detnet-ip-over-mpls-01 (work in - progress), July 2019. + MPLS", draft-ietf-detnet-ip-over-mpls-03 (work in + progress), October 2019. [I-D.ietf-detnet-mpls-over-tsn] - Varga, B., Farkas, J., Malis, A., Bryant, S., and J. - Korhonen, "DetNet Data Plane: MPLS over IEEE 802.1 Time - Sensitive Networking (TSN)", draft-ietf-detnet-mpls-over- - tsn-00 (work in progress), May 2019. + Varga, B., Farkas, J., Malis, A., and S. Bryant, "DetNet + Data Plane: MPLS over IEEE 802.1 Time Sensitive Networking + (TSN)", draft-ietf-detnet-mpls-over-tsn-01 (work in + progress), October 2019. [I-D.ietf-detnet-security] Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, - J., Austad, H., Stanton, K., and N. Finn, "Deterministic - Networking (DetNet) Security Considerations", draft-ietf- - detnet-security-05 (work in progress), August 2019. + J., Austad, H., and N. Finn, "Deterministic Networking + (DetNet) Security Considerations", draft-ietf-detnet- + security-06 (work in progress), November 2019. [I-D.ietf-spring-segment-routing-mpls] Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., and R. Shakir, "Segment Routing with MPLS data plane", draft-ietf-spring-segment-routing-mpls-22 (work in progress), May 2019. [IEEE802.1AE-2018] IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC Security (MACsec)", 2018, @@ -1321,20 +1313,25 @@ RFC 6790, DOI 10.17487/RFC6790, November 2012, . [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, . + [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, + "Deterministic Networking Architecture", RFC 8655, + DOI 10.17487/RFC8655, October 2019, + . + Authors' Addresses Balazs Varga (editor) Ericsson Magyar Tudosok krt. 11. Budapest 1117 Hungary Email: balazs.a.varga@ericsson.com