MPLS Encapsulation for Deterministic Latency Network Action

As specified in and , Deterministic Networking (DetNet) operates at the IP layer and delivers service with low data loss rates and bounded latency guarantee within a network domain. As defined in , the DetNet MPLS data plane provides a foundation of building blocks to enable PREOF (Packet Replication, Elimination and Ordering Functions (PREOF)) functions to DetNet service and forwarding sub-layer. The DetNet service sub-layer includes a DetNet Control Word (d-CW), service label (S-Label), an aggregation label (A-Label) in special case of S-Label used for aggregation. The DetNet forwarding sub-layer supports one or more forwarding labels (F-Labels) used to forward a DetNet flow over MPLS domains. The DetNet forwarding sub-layer provides corresponding forwarding assurance with IETF existing functions using resource allocations and explicit routes. But these functions may not be enough to provide the deterministic latency (including bounded latency, low packet loss and in-order delivery) assurance. Because latency variation in one DetNet system results in the need for extra buffer space in the next-hop DetNet system(s), which in turn increases the worst-case per-hop latency. So standard queuing and scheduling algorithms are required to compute and reserve the sufficient buffer space for DetNet nodes along the path of DetNet flows. To support time-sensitive service with ultra-low loss rates and deterministic latency, it is required to apply feasible scheduling mechanisms to specific applications for deterministic networking. As described in , the end-to-end bounded latency is considered as the sum of non-queuing and queuing delay bounds along with the queuing mechanisms. The value for non-queuing delay bounds (which consist of packet output delay, link delay, frame preemption delay and processing delay) is relative with the physical capability of on-used networks and can be considered to be stable. The unstable latency delay bounds are mainly from queuing delay and regulation delay. The regulation delay is mainly from regulation policy. To simplify the question this draft assumes there is no regulation policy. So the question is left to address the selection for queuing mechanisms and queuing delay information encapsulation in data plane. The queuing mechanisms, as mentioned in and , which include Time Aware Shaping IEEE802.1Qbv, Asynchronous Traffic Shaping IEEE802.1Qcr, cyclic-scheduling queuing mechanism proposed in IEEE802.1Qch. There are also discussions on new queuing or scheduling mechanisms such as and . In terms of delay guarantee for different applications, to select the right scheduling/queuing mechanism applied to a specific application is required. Based on the existing DetNet MPLS encapsulations and mechanisms , the draft defines the encoding format for Deterministic Latency Network Action (DLNA) option in MPLS data plane. MPLS Network Actions (MNA) are used to indicate actions for LSPs and/or MPLS packets and to transfer data needed for these actions. defines the MNA solution for carrying Network Actions with In-Stack Data and associated Ancillary Data (AD) (i.e., in the MPLS label stack). defines the MNA solution for carrying Network Actions with Post-Stack Data and associated Ancillary Data (i.e., below the bottom of the MPLS label stack). This draft describes MNA solutions for DLNA in DetNet.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Refer to , , and for the key terms used in this document. Deterministic Latency (DL):the bound of network latency and delay variation between two DetNet endpoints. It may includes parameters such as bounded latency, bounded delay variation, etc. Deterministic Latency Network Action (DLNA): used to indicate deterministic latency network action for MPLS data plane.

provides the architecture for deterministic networking (DetNet) which enables the service delivery of DetNet flows with extremely low packet loss rates and deterministic latency. The forwarding sub-layer provides corresponding forwarding assurance but can not provide the deterministic latency (including bounded latency, low packet loss and in-order delivery). As described at , the end-to-end bounded latency for one DetNet flow is the sum of delay bound of non-queuing and queuing processing latency. The delay bound for non-queuing processing may include output delay, link delay, frame preemption delay, and processing delay, the delay bound for queuing processing may include regulator delay, queuing delay. It is assumed that the delay of non-queuing processing is fixed or be ignorable, the delay of queuing processing is variable. To realize the guarantee of bounded latency service it is important to select right queuing methodology applied to specific applications and carry necessary queuing delay information for computation of end-to-end latency.

The DetNet data plane encapsulation in transport network with MPLS data plane is specified in . has proposed a commom DetNet data fields for enhanced DetNet data plane and defined a DLNA option to carry queuing-based metadata.This document provides additional encapsulation for the DLNA in MPLS data plane. The DetNet routers in data plane perform MPLS forwarding functions to choose a feasible way with sufficient network resources for the incoming packets, and makes right selection on the queuing or scheduling mechanisms applied for specific DetNet flows to satisfy strict QoS criteria in the forwarding output port. The information for the queuing or scheduling mechanisms are carried in DetNet DLNA header. Refer to , considering the time latency information are processed per hop so the time latency informations (such as deadline time, cycle identify, etc.) of each DetNet node for DetNet flows are expected to be carried as a set of lists of LSEs in MPLS data plane.

The DetNet MPLS header follows . To support deterministic bounded latency service this draft introduces 2 options to carry DetNet DLNA data using MPLS MNA solutions. As shown in figure 1, the MNA label is inserted to indicate the recognition of MPLS Network Actions, the DetNet DLNA can be carried in or after MPLS Label Stack. Option 1, the DetNet IS-DLNA are inserted to MPLS In-Stack Option 2, the DetNet PS-DLNA are located to MPLS Post-Stack The format for MPLS DetNet IS-DLNA follows MNA (MPLS Network Action) encapsulation specified in and , which is comprised of a set of Label Stack Entries (LSEs) that carry the DetNet DLNA Network Action Indicator and Ancillary Data to perform DLNA actions for MPLS packets. The format for MPLS DetNet PS-DLNA refers to . The detailed DetNet IS-DLNA and PS-DLNA encapsulation refers to the following section in the draft.

MNA Label: A new bSPL value is to be assigned by IANA. It is used to indicate the presence of the MPLS Network Action Sub-Stack (NASS). The assignment for this field value refers to . The MPLS In-Stack Data encoding format for DLNA option is shown in the figure 3. The format provides DLNA Indicator to describe the set of the DLNA network action. Its detailed information is carried in the following Ancillary Data for the present DLNA network action.

IS-DLNA (7 bits): This is the first 7-bit value in the Label Field. The value is used to indicate DLNA network action with In-Stack Data and to be assigned by IANA as value TBA1. Flag (16 bits): identifies the type of queuing mechanisms used in the network. The queuing type format is defined in section 4.2 of . S (1 bit) : The Bottom of Stack . Data (4 bits) : Reserved bits for future use. NAL (4 bits): The DLNA action length. It indicates the number of AD LSEs in the sub-stack. The first bit in the Label field of the following AD LSEs MUST be set to "1". As specified in this is to prevent aliasing the label field with other bSPLs on the legacy routers. Ancillary Data: The 19-bit Label field and 4-bit TC field and 8-bit TTL field (except S bit) in the additional LSEs are used to carry the Ancillary Data for specific DLNA latency information. The Ancillary Data LSE1 is expected to carry the latency information DLNA option data defined in section 4.2.2 of of the edge DetNet node. Depend on specific queuing mechanisms used in the network the DLNA field length for the latency information for one DetNet node is variable. The specific queuing (including cycle, deadline, etc.) data encapsulation are described in . The first AD LSE is expected to carry the latency information for edge DetNet node. When the length of latency information is more than 32bits less than 64bits, both AD LSE1 and LSE2 are expected to carry the latency information for edge DetNet node. In this case, the DLNA option data of next hop is carried in AD LSE3 and LSE4. Along the path of DetNet flows the AD LSE(n-1) and LSEn carry the DLNA option data for the peer edge DetNet node. With the DetNet flows are being forwarded in its output ports the corresponding node latency information carried in DLNA options are processed hop by hop.

There are some limitaions to use MPLS In-Stack Data for DLNA. For example, the total length for In-Stack Data LSEs seems small (no more than 16LSEs), but on the other hand the latency information of each nodes (nodes number may be more than 16 in DetNet) along the path of DetNet flows needs be carried in the MPLS sub-stack. Besides, HBH scenario brings high packet overload and low encapsulation efficiency. This document does not exclude MNA Post-Stack solution for carrying DLNA. The MPLS Post-Stack format for DLNA Network Action refers to and and shown in figure 4.

As specified at , The header for In-Stack Network Action encodes: P (1 Bit) : This document sets the value to 1 to identify the presence of Post-Stack Network Action. IHS (2 Bit) : Indicates the combined scope of the In-Stack and the Post-Stack Network Actions. U (1 Bit) : Indicates the combined Unknown Action Handling of the In-Stack and the Post-Stack Network Actions. As specified at , The header for Post-Stack Network Action encodes: Sequence Number: The format of DetNet Control Word (d-CW) refers to . NNNN (4 bits): This first nibble identifies the start of the Post-Stack Network Actions. A new value can be assigned by IANA. Generic Associated Channel (0001b) can be used instead. The assignment for this field value is out of the scope of this draft. Version (4 bits): This is Post-Stack MNA version. PS-MNA-LEN (8 bits): Post-Stack MNA Total Length in words. This excludes the Post-Stack Top header. TYPE (16 bits): Type is set to POST-STACK-MNA. In case of DetNet MPLS, this is DLNA Type. PS-DLNA (7 bits): Post-Stack Network Action Opcode. The value is used to indicate DLNA network action with Post-Stack Data and to be assigned by IANA as value TBA2. DLNA Ancillary Data (16 bits): Post-Stack Ancillary Data associated with the DLNA. R (2 bits): Reserved bits. PS-DLNA-LEN (7 bits): Post-Stack DLNA Network Action Length. The number of LSEs of the following Ancillary Data. The MPLS DLNA Network Action encapsulation with Post-Stack Data refers to the latest MPLS WG discussions and follows the encoding principles of the MNA Post-Stack Data speicified at MPLS WG.

This document requests two new IANA-managed code-points for DetNet application processing. IANA maintains the "In-Stack MNA Opcode" registry when created from IANA request in . IANA is requested to allocate a value for In-Stack Network Action Opcode for DLNA application from this registry: Value Description Reference TBA1 IS-DLNA this document IANA maintains the "Post-Stack MNA Opcode" registry when created from IANA request in . IANA is requested to allocate a value for Post-Stack Network Action Opcode for DLNA application from this registry: Value Description Reference TBA2 PS-DLNA this document

Security considerations for DetNet are covered in the DetNet Architecture RFC8655 and DetNet Security Considerations . MPLS security considerations are covered in , , . These security considerations also apply to this document. The MNA security considerations speicified at and are also applicable to the procedures defined in this document.

The authors would like to acknowledge Shaofu Peng for his thorough review and very helpful comments.