--- 1/draft-ietf-detnet-mpls-10.txt 2020-08-16 09:13:19.524714596 -0700 +++ 2/draft-ietf-detnet-mpls-11.txt 2020-08-16 09:13:19.588716220 -0700 @@ -1,25 +1,25 @@ DetNet B. Varga, Ed. Internet-Draft J. Farkas Intended status: Standards Track Ericsson -Expires: January 27, 2021 L. Berger +Expires: February 17, 2021 L. Berger LabN Consulting, L.L.C. A. Malis Malis Consulting S. Bryant Futurewei Technologies J. Korhonen - July 26, 2020 + August 16, 2020 DetNet Data Plane: MPLS - draft-ietf-detnet-mpls-10 + draft-ietf-detnet-mpls-11 Abstract This document specifies the Deterministic Networking data plane when operating over an MPLS Packet Switched Network. It leverages existing pseudowire (PW) encapsulations and MPLS Traffic Engineering encapsulations and mechanisms. This document builds on the DetNet Architecture and Data Plane Framework. Status of This Memo @@ -30,21 +30,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 January 27, 2021. + This Internet-Draft will expire on February 17, 2021. Copyright Notice Copyright (c) 2020 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 @@ -99,21 +99,21 @@ a network to DetNet flows. DetNet provides these flows with extremely low packet loss rates and assured maximum end-to-end delivery latency. 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). + loss, assured latency, and limited out-of-order delivery). This document specifies the DetNet data plane operation and the on- wire encapsulation of DetNet flows over an MPLS-based Packet Switched Network (PSN) using the service reference model. MPLS encapsulation already provides a solid foundation of building blocks to enable the DetNet service and forwarding sub-layer functions. MPLS encapsulated DetNet can be carried over a variety of different network technologies that can provide the DetNet required level of service. However, the specific details of how DetNet MPLS is carried over different network technologies is out of scope of this document. @@ -315,22 +315,22 @@ potential DetNet compound flow packet replication and elimination points. In this example, service protection is supported utilizing at least two DetNet member flows and TE LSPs. For a unidirectional flow, R1 supports PRF and R3 supports PEF and POF. Note that the relay nodes may change the underlying forwarding sub-layer, for example tunneling MPLS over IEEE 802.1 TSN [I-D.ietf-detnet-mpls-over-tsn], or simply over interconnect network links. DetNet DetNet - MPLS Service Transit Transit Service MPLS - DetNet | |<-Tnl->| |<-Tnl->| | DetNet + DetNet Service Transit Transit Service DetNet + MPLS | |<-Tnl->| |<-Tnl->| | MPLS End | V 1 V V 2 V | End System | +--------+ +--------+ +--------+ | System +---+ | | R1 |=======| R2 |=======| R3 | | +---+ | X...DFa...|._X_....|..DF1..|.__ ___.|..DF3..|...._X_.|.DFa..|.X | |CE1|========| \ | | X | | / |======|CE2| | | | | \_.|..DF2..|._/ \__.|..DF4..|._/ | | | | +---+ | |=======| |=======| | +---+ ^ +--------+ +--------+ +--------+ ^ | Relay Node Relay Node Relay Node | | (S-PE) (S-PE) (S-PE) | @@ -565,24 +565,24 @@ encapsulations for consistency but there is no hard requirement in this regard. 4.2.2.1. Packet Replication Function Processing The Packet Replication Function (PRF) function MAY be supported by an implementation for outgoing DetNet flows. The use of the PRF for a particular DetNet service MUST be provisioned via configuration, e.g., via the controller plane described in [I-D.ietf-detnet-data-plane-framework]. When replication is - configure, the same app-flow data will be sent over multiple outgoing - DetNet member flows using forwarding sub-layer LSPs. An S-Label - value MUST be configured per outgoing member flow. The same d-CW - field value MUST be used on all outgoing member flows for each + configured, the same app-flow data will be sent over multiple + outgoing DetNet member flows using forwarding sub-layer LSPs. An + S-Label value MUST be configured per outgoing member flow. The same + d-CW field value MUST be used on all outgoing member flows for each replicated MPLS packet. 4.2.2.2. Packet Elimination Function Processing Implementations MAY support the Packet Elimination Function (PEF) for received DetNet MPLS flows. When supported, use of the PEF for a particular DetNet service MUST be provisioned via configuration, e.g., via the controller plane described in [I-D.ietf-detnet-data-plane-framework]. @@ -592,23 +592,23 @@ implementation MUST track the sequence number contained in received d-CWs and MUST ensure that duplicate (replicated) instances of a particular sequence number are discarded. The specific mechanisms used for an implementation to identify which received packets are duplicates and which are new is an implementation choice. Note that per Section 4.2.1 the sequence number field length may be 16 or 28 bits, and the field value can wrap. PEF MUST NOT be used with DetNet flows configured with a d-CW sequence number field length of 0 bits. Note that an implementation MAY wish to constrain the maximum number - sequence numbers that are tracked, on platform-wide or per flow + of sequence numbers that are tracked, on platform-wide or per flow basis. Some implementations MAY support the provisioning of the - maximum number sequence numbers that are tracked number on either a + maximum number of sequence numbers that are tracked on either a platform-wide or per flow basis. 4.2.2.3. Packet Ordering Function Processing A function that is related to in-order delivery is the Packet Ordering Function (POF). Implementations MAY support POF. When supported, use of the POF for a particular DetNet service MUST be provisioned via configuration, e.g., via the controller plane described by [I-D.ietf-detnet-data-plane-framework]. Implementations MAY required that PEF and POF be used in combination. There is no @@ -933,22 +933,23 @@ 2, by IEEE 802.1p priority code point (PCP). CoS for DetNet flows carried in PWs and MPLS is provided using the existing MPLS Differentiated Services (DiffServ) architecture [RFC3270]. Both E-LSP and L-LSP MPLS DiffServ modes MAY be used to support DetNet flows. The Traffic Class field (formerly the EXP field) of an MPLS label follows the definition of [RFC5462] and [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]. + MAY be used for MPLS LSPs supporting DetNet flows. MPLS Explicit + Congestion Notification (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 [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 @@ -1289,21 +1290,21 @@ [I-D.ietf-detnet-mpls-over-tsn] 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-03 (work in progress), June 2020. [I-D.ietf-detnet-security] Mizrahi, T. and E. Grossman, "Deterministic Networking (DetNet) Security Considerations", draft-ietf-detnet- - security-10 (work in progress), May 2020. + security-11 (work in progress), August 2020. [I-D.ietf-detnet-yang] Geng, X., Chen, M., Ryoo, Y., Fedyk, D., Li, Z., and R. Rahman, "Deterministic Networking (DetNet) Configuration YANG Model", draft-ietf-detnet-yang-07 (work in progress), July 2020. [IEEE802.1AE-2018] IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC Security (MACsec)", 2018,