Cisco Systems, Inc.

Canada jrajaman@cisco.com

Cisco Systems, Inc.

Canada rgandhi@cisco.com

Broadcom

royi.zigler@broadcom.com

Futurewei Technologies

haoyu.song@futurewei.com

Juniper Networks

United States of America kireeti.ietf@gmail.com

RTG mpls This document specifies the MPLS Network Action (MNA) Sub-Stack for carrying network actions and Ancillary Data (AD) in the MPLS label stack. MNA can be used to influence packet-forwarding decisions, carry additional Operations, Administration, and Maintenance (OAM) information in the MPLS packet, or perform user-defined operations. This document updates RFC 9789 to refine the list of pieces of information that must be included in any document that defines an MNA.

Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2026 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 () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.

Table of Contents

• .  Introduction
• .  Conventions Used in This Document
  • .  Requirements Language
  • .  Abbreviations
  • .  Terminology
• .  Overview
• .  Label Stack Entry Formats
  • .  LSE Format A: The MNA Sub-Stack Indicator
  • .  LSE Format B: The Initial Opcode
  • .  LSE Format C: Subsequent Opcodes
  • .  LSE Format D: Additional Data
• .  The MNA Sub-Stack
  • .  Opcodes
  • .  Ancillary Data
  • .  Scope
  • .  Unknown Network Action Handling
  • .  Ordering
• .  Special Opcodes
  • .  bSPL Protection
  • .  Flag-Based NAIs Without AD
  • .  No-Operation Opcode
  • .  Extension Opcode
• .  NAS Placement in the Label Stack
  • .  Actions When Pushing Labels
• .  Node Capability Signaling
• .  Processing the Network Action Sub-Stack
  • .   Encapsulating Node Responsibilities
  • .   Transit Node Responsibilities
  • .   Penultimate Node Responsibilities
  • .   Egress Node Responsibilities
• . Network Action Indicator Opcode Definition
• . Security Considerations
• . Operational Considerations
  • .  Manageability Considerations
  • .  Performance and Scale Considerations
  • .  Backward Compatibility
• . IANA Considerations
  • .  MNA bSPL Label
  • .  MPLS Network Actions Parameters
    • .  Network Action Flags Without Ancillary Data
    • .   Network Action Opcodes
• . References
  • .  Normative References
  • .  Informative References
• .  Examples
  • .  Network Action Encoding Examples
    • .  Network Action Flags Without AD
    • .  Network Action Opcode with AD
    • .  Network Action Opcode with More AD with Format B
    • .  Network Action Opcode with More AD with Format C
  • .  Network Action Processing Order
    • .  Network Action Processing Order
• Acknowledgments
• Contributors
• Authors' Addresses

Introduction defines the encoding of the MPLS label stack, the basic structure used to define a forwarding path. There are applications that require MPLS packets to perform special network actions and carry optional Ancillary Data (AD) that can affect the packet-forwarding decision or trigger Operations, Administration, and Maintenance (OAM) logging, for example, as described in . AD can be used to carry additional information, for example, for network slice purposes (see ). The requirements for in-stack network action and In-Stack Data (ISD) are described in . This document defines the syntax and semantics of network actions and AD encoded in an MPLS label stack. In-stack actions and AD are contained in a Network Action Sub-Stack (NAS), which is recognized by a new base Special-Purpose Label (bSPL). This document follows the framework specified in . provides details about information that a document defining a network action must contain. of this document updates by providing a refined list of pieces of information that must be included in any document that defines an MNA.

Conventions Used in This Document

Requirements Language 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.

Abbreviations Abbreviations

Abbreviation	Meaning	Reference
AD	Ancillary Data
bSPL	base Special-Purpose Label
BoS	Bottom of Stack
ECMP	Equal-Cost Multipath
HbH	Hop-by-Hop
I2E	Ingress to Egress
IHS	I2E, HbH, or Select	This document
ISD	In-Stack Data
LSE	Label Stack Entry
LSP	Label Switched Path
MNA	MPLS Network Action
NAI	Network Action Indicator
NAL	Network Action Length	This document
NAS	Network Action Sub-Stack
NSI	Network Action Sub-Stack Indicator	This document
NASL	Network Action Sub-Stack Length	This document
OAM	Operations, Administration, and Maintenance
RLD	Readable Label Depth
TC	Traffic Class
TTL	Time to Live

Terminology The following terms are used in this document.

MPLS Egress Node:

An MPLS edge node in its role in handling traffic as it leaves an MPLS domain .

MPLS Ingress Node:

An MPLS edge node in its role in handling traffic as it enters an MPLS domain .

MPLS Domain:

A contiguous set of nodes that operate MPLS routing and forwarding and that are also in one Routing or Administrative Domain .

Encapsulating Node:

A node that adds a NAS to the label stack.

Overview The MPLS NAS is a set of Label Stack Entries (LSEs) that appear as part of an MPLS label stack and serve to encode information about the network actions that should be invoked for the packet. Multiple NASes may appear in a label stack and be placed as described in . This document specifies how network actions and their optional AD are encoded as part of a NAS as a stack of LSEs. Mechanisms that allow sharing of AD between multiple network actions encoded in the same NAS can be described in other documents and do not rely on any explicit provision in the encodings described in this document. This document defines new LSE formats beyond those in that define behaviors or are processed in different ways than MPLS labels as defined in . Three new LSE formats are defined to carry 7 bits of network action opcodes and varying amounts of opcode-specific AD. Specifically, Format B LSE carries up to 13 bits of AD in an LSE. Format C LSE carries up to 20 bits of AD in an LSE. Format D LSE is used when additional AD is needed by the opcodes in Format B or Format C LSEs. As shown in , the first LSE in an MNA Sub-Stack uses Format A. The second LSE uses Format B and is followed by a Format D LSE to carry additional data. Next, there may be a Format C LSE for an additional network action followed by another Format D LSE for additional data. Additional Format C and Format D LSEs may be added as needed for additional network actions and data.

An MNA Sub-Stack Encoding Example 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-- | MNA-Label=bSPL | TC |S| TTL |A +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-- | Opcode | 13-bit Data |R|IHS|S| NASL |U| NAL |B +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-- |1| 22-bit Data |S| 8-bit Data |D* +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-- | Opcode | 16-bit Data |S|4b Data|U| NAL |C +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-- |1| 22-bit Data |S| 8-bit Data |D* +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-- | Opcode | 16-bit Data |S|4b Data|U| NAL |C +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-- ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-- * Format D LSE presence indicated by NAL greater than one

Label Stack Entry Formats The NAS uses a variety of different formats of LSEs for different purposes. This section describes the syntax of the various formats while the overall structure of the NAS and the semantics of the various LSEs are described in the sections below.

LSE Format A: The MNA Sub-Stack Indicator LSE Format A is an LSE as described in and . The label value is 4 for the MNA bSPL label from the "Base Special-Purpose MPLS Label Values" IANA registry (see ) to indicate the presence of an MNA in the packet and the beginning of an MNA Sub-Stack in the label stack.

LSE Format A: The MNA Sub-Stack Indicator 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MNA-Label=bSPL | TC |S| TTL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

S (1 bit):

The BoS . MUST be set to 0 on transmitted packets. If a packet is received with an LSE containing the bSPL (4) and with S bit set to 1, then the packet MUST be dropped.

LSE Format B: The Initial Opcode LSE Format B is used to encode the first opcode in the NAS, plus a number of other fields about the NAS. The Data field of this LSE can carry up to 13 bits of AD.

LSE Format B: The Initial Opcode 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode | 13-bit Data |R|IHS|S| NASL |U| NAL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Opcode (7 bits):

The operation code for this LSE. See .

Data (13 bits):

Opcode-specific AD.

R (1 bit): Reserved.

This bit MUST be set to zero on transmission and ignored upon receipt.

IHS (2 bits):

The scope of all the network actions in this NAS. See .

S (1 bit):

The BoS . If the NASL value is non-zero, then the S bit MUST be 0. If a packet is received with the S bit set to 1 and a non-zero NASL value, then the packet MUST be dropped. The encapsulating node MUST ensure that the S bit is set to 1 only in the last LSE in the MPLS header.

NASL (4 bits):

The Network Action Sub-Stack Length. The number of Format C and Format D LSEs in the NAS, i.e., not including the leading Format A LSE and the Format B LSE.

U (1 bit):

Unknown Network Action Handling. See .

NAL (3 bits):

Network Action Length. The number of LSEs of additional data, encoded in Format D LSEs (), following this Format B LSE. The NAL value MUST be less than or equal to the NASL value in the Format B LSE. If not, the packet MUST be dropped. A Format C LSE would be following when the NAL value is less than the NASL value.

LSE Format C: Subsequent Opcodes LSE Format C is used to encode the subsequent opcodes in the NAS.

LSE Format C: Subsequent Opcodes 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode | 16-bit Data |S|4b Data|U| NAL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Opcode (7 bits):

The operation code for this LSE. See .

Data (16 bits + 4 bits):

Opcode-specific AD.

S (1 bit):

The BoS . If the NAL value is non-zero and if the S bit is set to 1, then the packet MUST be dropped. If this is not the last LSE in the NAS and if the S bit is set to 1, then the packet MUST be dropped. The encapsulating node MUST ensure that the S bit is set to 1 only in the last LSE.

U (1 bit):

Unknown Network Action Handling. See .

NAL (3 bits):

Network Action Length. The number of LSEs of additional data, encoded in Format D LSEs () following this Format C LSE. The NAL value MUST be less than or equal to the NASL value in the Format B LSE. If not, the packet MUST be dropped.

A Format A and a Format B LSE MUST be present when a Format C LSE is carried in the NAS.

LSE Format D: Additional Data LSE Format D is used to encode additional data that did not fit in the LSE with the preceding opcode.

LSE Format D: Additional Data 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1| 22-bit Data |S| 8-bit Data | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

1 (1 bit):

The most significant bit MUST be set. This prevents legacy implementations from misinterpreting this LSE as containing a special purpose label if the data begins with zeros.

S (1 bit):

The BoS . If this is not the last LSE for the network action based on the NAL value and if the S bit is set to 1, then the packet MUST be dropped. If this is not the last LSE in the NAS and if the S bit is set to 1, then the packet MUST be dropped. The encapsulating node MUST ensure that the S bit is set to 1 only in the last LSE.

Data (22 bits + 8 bits):

Opcode-specific AD.

A Format A and a Format B LSE MUST be present when a Format D LSE is carried in the NAS.

The MNA Sub-Stack The MNA Sub-Stack MUST begin with a Format A LSE (). The label value of the LSE contains the MNA bSPL (4) to indicate the presence of the MNA Sub-Stack. The TC and TTL values of the Format A LSE retain their semantics as defined in and . The TTL and TC values in the Format A LSE are copied from the forwarding label at the top of the label stack. The penultimate node on the path copies the TTL and TC values from the preceding LSE to the next LSE on the label stack, overwriting the TTL and TC values of the next LSE, as specified in and in the Uniform Mode LSPs. If the node performing this copy is not aware of MNA, this could overwrite the values in the Format A LSE of the NAS. The second LSE in a NAS MUST be a Format B LSE (). This LSE contains an initial opcode plus additional fields that describe the NAS. The Format B LSE () could optionally carry additional data in Format D () LSEs, up to the length encoded in the LSE's NAL value. A NAS MAY contain more Format C () and Format D () LSEs, up to the length encoded in the NASL value. All Format D LSEs MUST follow a Format C or Format B LSE and be included in that LSE's NAL value.

Opcodes The opcode is a 7-bit field that indicates the semantics of its LSE. Several opcodes are assigned special semantics (). Other opcodes act as NAIs and are assigned through IANA (see Sections and ).

Ancillary Data The data field carries opcode-specific data that is AD for a network action. In the case of opcode 1, the data field carries Flag-Based NAIs without AD. The label value (most significant 20 bits) in one or more consecutive LSEs is commonly used for load-balancing data flows in an ECMP environment. Modifying the first 20 bits in an LSE might alter a packet's path and result in out-of-order delivery of packets belonging to a given flow. To maintain the stability of deployed services in ECMP environments that rely on label value information for load-balancing, care must be taken when encoding network action data in the given LSE. If the network action data may differ among packets in the same flow or change during forwarding across the MPLS network, it MUST NOT be placed in the most significant 20 bits of a Format B LSE (), a Format C LSE (), or a Format D LSE (). Thus, the available bits for data that can change by a transit node or differ among packets of the same flow in Format A and Format B LSEs is 0, in a Format C LSE 7 (bits 20-22 and 25-28), and in a Format D LSE 11 (bits 20-22 and 24-31). Similarly, to preserve service stability, such data also MUST NOT be carried in the most significant 23 bits of these LSEs when the legacy implementation also uses the TC value, in addition to the label value, in all LSEs when computing ECMP decisions. The available mitigations for these problems are to use additional Format D LSEs to carry the data or to place the data in Post-Stack Data as described in . In network deployments where it is known that a load-balancing of data flows is not used, or if only the explicitly signaled entropy value is used, and it is certain that the load-balancing path selection will not be based on the label value of the LSEs, then the data in the label value of the LSEs in the ISD MAY be mutable within the data flow without causing the out-of-order delivery of packets.

Scope The IHS field in the Format B LSE indicates the scope of all the NAIs encoded in the NAS. Scope defines which nodes along the MPLS path should perform the network actions found within the NAS. The specific values of the IHS field are as follows: IHS Scope Values

Bits	Scope
00	I2E
01	HbH
10	Select
11	Reserved for future use

Ingress to Egress (I2E):

The network actions in this NAS MUST NOT be processed by any node except the egress node.

Hop-by-Hop (HbH):

All nodes along the path MUST process the NAS.

Select:

Only specific nodes along the path that bring NAS to the top of the stack will perform the action.

A given NAS can only carry NAIs with the same scope (I2E/HbH/Select). To support multiple scopes for a single packet, multiple NASes MAY be included in a single label stack. The egress node is included in the HbH scope. This implies that the penultimate node MUST NOT remove a NAS with HbH scope. The egress node may receive a NAS at the top of the label stack as discussed in . A NAS with I2E scope, if present, MUST be encoded after any HbH or Select scope NASes. This makes it easier for the transit nodes to process a NAS with HbH or Select scope. If a packet is received with the IHS scope set to "Reserved for future use", the packet is processed based on the U bit in the Format B LSE in the NAS.

Unknown Network Action Handling The Unknown Network Action Handling (U) field in a Format B LSE () and Format C LSE () is a 1-bit value that defines the action to be taken by a node that does not understand an action within the NAS. The different types of Unknown Network Action Handling actions are defined below. Unknown Network Action Handling

Bit	Action
0	Skip to the next NA
1	Drop the packet

When a packet with an Unknown Network Action Handling is dropped, the node should maintain a local counter for this event and may send a rate-limited notification to the operator.

Ordering The network actions encoded in the NAS MUST be processed in the order that they appear in the NAS, from the top of the NAS to the bottom. NAIs encoded as flags (see ) MUST be processed from the most significant bit to the least significant bit. If a label stack contains multiple NASes, they MUST be processed in the order that they appear in the label stack, subject to the restrictions in .

Special Opcodes Below are the special opcodes defined to build a basic in-stack MNA solution and assigned in the "Network Action Opcodes" IANA registry (see ). In the future, additional special opcodes may be defined and their code points assigned from this registry.

bSPL Protection

Opcode:

0

Purpose:

Legacy implementations may scan the label stack looking for bSPL values. As long as the opcode field is non-zero, an LSE cannot be misinterpreted as containing a bSPL. Therefore, opcode 0 is reserved and not to be used.

Flag-Based NAIs Without AD

Opcode:

1

Purpose:

This opcode is used for network actions that do not require AD. A single flag can be used to indicate each of these network actions.

LSE Formats:

B, C, D

Data:

The data field carries NAIs, which should be evaluated from the most significant bit to the least significant bit. If this opcode is used with LSE Format B only, then up to 13 flags may be carried. If this opcode is used with LSE Format C only, then up to 20 flags may be carried. Format D LSEs can be used with Format C LSEs to encode more than 20 flags. Flags are assigned from the "Network Action Flags Without Ancillary Data" registry (). If flags need to be evaluated in a different order, multiple LSEs using this opcode may be used to specify the requested order. The Flag-Based NAIs MUST follow the procedure for data specified in .

Scope:

This opcode can be used with any scope.

No-Operation Opcode

Opcode:

2

Purpose:

This opcode is used to indicate that it does not perform any network action and MUST be skipped.

LSE Format:

B

Scope:

Any scope value may be set and MUST be ignored.

Extension Opcode

Opcode:

127

Purpose:

This opcode is used to extend the current opcode range beyond 127 in the future. If this opcode is not supported, then the packet with opcode 127 MUST be dropped regardless of the setting of the U bit. Use of this opcode is outside the scope of this document.

NAS Placement in the Label Stack The node adding a NAS to the label stack places a copy of the NAS where the relevant nodes can read it. Each downstream node along the path has a Readable Label Depth (RLD). If the NAS is to be processed by a downstream MNA-capable node, then the entire NAS MUST be placed so that it is within RLD by the time the packet reaches the downstream MNA-capable node. The RLD of the downstream MNA-capable node MUST be learned as described in . If the label stack is deep, several copies of the NAS may need to be encoded in the label stack. For a NAS with HbH scope, every node will process the top copy of the NAS. However, the NAS MUST NOT appear at the top of the stack at any MNA-incapable node on the path that is ensured by the encapsulating node using the node capability, as described in . A NAS MUST NOT appear at the top of the stack after popping the forwarding label on an MNA-incapable node on the path. The behavior of a node where a NAS with I2E and HbH scopes is also removed along with popping the forwarding label on a PHP node is outside the scope of this document. A NAS with Select scope is processed by the node that brings the NAS to the top of the stack (for example, in the case of using the MPLS label pop operation in Segment Routing); then, the NAS is removed from the stack. The Select scope NAS needs to be inserted after the forwarding label and before the next forwarding label. It could be inserted before or after a NAS with HbH scope. Note that the case of a NAS with Select scope with an MPLS label swap operation (for example, with RSVP-TE LSPs) is for future study. For a NAS with I2E scope, only one copy of the NAS needs to be added at the bottom of the stack. A transit node that is not the penultimate node that pops a forwarding label and exposes a copy of a NAS MUST remove that NAS. An MNA-capable node performing Penultimate Hop Popping (PHP) that pops the forwarding label with only the NAS(es) remaining on the stack MUST NOT remove the NAS(es). Instead, it forwards the packet with the NAS(es) at the top of the stack to the next node. Note that the behavior of the PHP node, as defined in for TC processing and as defined in for TTL processing, is not modified regardless of whether the PHP node supports MNA. The node that receives the NAS at the top of the label stack MUST process and remove it.

Actions When Pushing Labels An MNA-capable node may need to push additional labels as well as push new network actions onto a received packet. While pushing additional labels onto the label stack of the received packet, the MNA-capable node MUST verify that the entire topmost NAS with HbH scope is still within the RLD of the downstream MNA-capable nodes. If required, the MNA-capable node MAY create a copy of the topmost NAS with HbH scope and insert it within the RLD of the downstream MNA-capable nodes on the label stack. When an MNA-capable node needs to push a new NAS with HbH scope on to a received packet that already has a NAS with HbH scope, it SHOULD copy (and merge) the network actions (including their AD) from the received topmost NAS with HbH scope in the new NAS with HbH scope. The new NAS MUST be placed within the RLD of the downstream MNA-capable nodes. This behavior can be based on local policy. The new network actions added MUST NOT conflict with the network actions in the received NAS with HbH scope. The mechanism to resolve such conflicts depends on the network actions and can be based on local policy. The MNA-capable node that pushes entries MUST understand any network actions that it is pushing that may result in a conflict and MUST resolve any conflicts between new and received network actions. In the usual case of a conflict of duplicating a network action, the definition of a network action MUST give guidance on conflict resolution.

Node Capability Signaling The encapsulating node MUST make sure that the NAS can be processed by the transit and egress nodes. In addition, the encapsulated packet MUST NOT exceed the path MTU as described in .

• The node responsible for selecting a path through the MPLS network needs to know and consider the MNA-capabilities and RLD of the transit nodes as well as the MNA-capabilities of the egress node as described in .
• Information about the capabilities of the nodes may be configured, collected through management protocols, or distributed by control protocols (such as advertising by routing protocols).
• The node responsible for selecting a path through the MPLS network learns about the capabilities of nodes using mechanisms that are out of scope for this document.
• In the case of Segment Routing over MPLS (SR-MPLS), as well as the RLD, the path computation system needs to know the Maximum SID Depth (MSD) that can be imposed at the ingress node of a given SR path. This ensures that the label stack depth of a computed path does not exceed the maximum number of labels (i.e., MSD) the node is capable of imposing and the maximum number of labels that can be read by the MNA-processing nodes in the path. The MSD MUST include the MNA Sub-Stacks that will be added.
• The encapsulating node MUST learn about the RLD of the nodes in the path as described in .

Processing the Network Action Sub-Stack This section defines the specific responsibilities for nodes along an LSP .

Encapsulating Node Responsibilities The encapsulating node MAY add NASes to the label stack in accordance with its policies, the placement restrictions in , and the capabilities learned from . If there is an existing label stack, the encapsulating node MUST NOT modify the first 20 bits of any LSE in the label stack when the ECMP technique in the network uses hashing of the labels on the label stack.

Transit Node Responsibilities The transit node is the node that processes a NAS in the label stack but does not push any new NAS. The transit node MUST follow the procedure for data specified in . Transit nodes MUST process the NASes in the label stack according to the rules set out in . A transit node that processes a NAS and does not recognize the value of an opcode MUST follow the rules according to the setting of the Unknown Network Action Handling value in the NAS as described in .

Penultimate Node Responsibilities In addition to the transit node responsibilities, the penultimate node and penultimate SR-MPLS segment node MUST NOT remove the last copy of an HbH or I2E NAS when it is exposed after removing the forwarding (transport) label. This allows the egress node to process the NAS.

Egress Node Responsibilities The egress node MUST remove any NAS it receives.

Network Action Indicator Opcode Definition The following information MUST be defined for a new NAI opcode request in the document that specifies the network action. This updates the list found in and should be used instead of that list.

Format:

The definition of the new network action MUST specify the LSE formats. The opcode can define the network action in Format B or C or both Formats B and C. Both Format B and C LSEs MAY optionally carry Format D LSEs.

Scope:

The definition of the new network action MUST specify at least one scope (I2E, HbH, Select) for the network action and MAY specify more than one scope.

Ancillary Data:

The definition of the new network action MUST specify the quantity, syntax, and semantics of any associated AD. The AD MAY be variable length, but the NAL MUST be computable based on the data added in the NAS.

Processing:

The definition of the new network action MUST specify the detailed procedure for processing the network action.

Interactions:

The definition of the new network action MUST specify its interaction including merging with other currently defined network action if there is any.

An assignment for a NAI MAY make requests from any combination of the "Network Action Opcodes" or "Network Action Flags Without Ancillary Data" assignments (see ). This decision should optimize for eventual encoding efficiency. If the NAI does not require any AD, then a flag is preferred as only one bit is used in the encoding.

Security Considerations The security considerations in and also apply to this document. In addition, MNA creates a new dimension in security concerns:

• The actions of an encapsulating node can affect any or all of the nodes along the path. In the most common and benign situations, a syntactically incorrect packet could result in packet loss or corruption, for example.
• The semantics of a network action are unbounded and may be insecure. A network action could be defined that makes arbitrary changes to the memory of the forwarding router, which could then be used by the encapsulating node to compromise every MNA-capable router in the network.
• The MNA architecture supports locally defined network actions. For such actions, there will be limited oversight to ensure that the semantics do not create security issues. Implementors and network operators will need to ensure that even the locally defined network actions do not compromise the security of the network by following the security considerations specified in this document.
• The MPLS domain border nodes MUST ensure that the MPLS packets with MNA from any domain with a different administrative control can be filtered to prevent entering the provider MPLS domain. The filtering capability MAY be enabled on a per-network-action basis, and it can be based on a local policy. The filtering capability MUST be implemented on those nodes before deploying MNA in the provider MPLS domain. The RLD on the filtering node MUST be higher than the RLD on all other nodes in the provider MPLS domain.
• The MNA architecture supports modifying the AD on the intermediate nodes so the critical network functions either should not rely on the data or should be aware of the risks and use other means to verify the security of the whole network.
• System designers must be aware that information included in AD may be transmitted "in the clear". Network actions that require the exchange of sensitive data MUST be defined in such a way that the data is encrypted in transit. Otherwise, sensitive data MUST NOT be transmitted using these mechanisms.
• Mis-delivery of a packet due to malformed forwarding action data could be considered a security risk.

Operational Considerations

Manageability Considerations An MNA implementation MAY collect the following counters:

• Packets with MNA received
• MNA Sub-Stacks processed
• MNA per-network-action counters
• Packets with MNA dropped due to unknown actions
• Packets with MNA skipped due to unknown actions
• Packets with MNA dropped due to malformed NAS

Additionally, tracking both successful invocations and failures for each specific network action is RECOMMENDED to provide granular visibility. Nodes MAY generate rate-limited notifications or alarms for significant operational events, such as sustained high rates of MNA packet drops or frequent encounters of malformed MNA Sub-Stacks, to alert operators to potential issues. Comprehensive logging of MNA processing details and outcomes can aid in the network diagnostics and post-mortem analysis.

Performance and Scale Considerations Performance and scale assessments are outside the scope of this document; the authors of any future MNA application documents are encouraged to address them.

Backward Compatibility This section discusses interactions between MNA-capable and MNA-incapable nodes. An MNA encapsulating node MUST ensure that the MPLS NAS is not at the top of the MPLS label stack when the packet arrives at an MNA-incapable node. If such a packet did arrive at an MNA-incapable node, it will most likely be dropped as described in . Any node could scan the label stack, potentially looking for a label value containing a bSPL. To ensure that the LSE formats described herein do not appear to contain a bSPL value, the opcode value of 0 has been reserved. By ensuring that there is a non-zero value in the high-order 7 bits, we are assured that the high-order 20 bits cannot be misinterpreted as containing a bSPL value (0-15). The TC and TTL values of the Format A LSE are not repurposed for encoding, as the penultimate node on the MPLS packet path may propagate TTL from the transport (or forwarding) label to the next label on the label stack, overwriting the TTL on the next label. If the penultimate node is a legacy node, it might perform this action, potentially corrupting other values stored in the TC and TTL values. To protect against this, we retain the TC and TTL values in the Format A LSE. When adding the Entropy Label Indicator (ELI) (bSPL 7) and Entropy Label (EL) as defined in , along with an MNA NAS, the RLD MUST be considered for the placement of both, and they both can be placed in any order. If a transit LSR chooses to use as much of the whole label stack as feasible as a key for the load-balancing function, the MNA-reserved label MUST NOT be used as a key for the load-balancing function, as specified in . Note that the behavior of an MNA-incapable transit LSR that scans the label stack for ELI and EL but encounters a different, unrecognized reserved label first, is not modified by this document. Similarly, when adding the Flow-ID Label Indicator (FLI) (including the extension label 15) and Flow-ID Label (FL) as defined in , along with an MNA NAS, the RLD MUST be considered for the placement of both, and they both can be placed in any order. Note that the behavior of an MNA-incapable transit LSR that scans the label stack for FLI (including the extension label 15) and FL, but encounters a different, unrecognized reserved label first, is not modified by this document. However, as the existing behavior is not specified for transit LSRs, upon encountering any unrecognized bSPLs or extended SPLs (eSPLs) below the top of the label stack, some existing implementations may have chosen to implement non-standardized actions, such as discarding packets. Any uses of a new bSPL or eSPL would cause issues with such existing implementations using the non-standardized actions upon encountering unrecognized bSPLs or eSPLs below the top of the label stack. Since this is a generic problem, any clarifications for the treatment of unrecognized bSPL or eSPL are outside the scope of this document.

IANA Considerations

MNA bSPL Label IANA has allocated the value 4 for the MNA bSPL label from the "Base Special-Purpose MPLS Label Values" registry to indicate the presence of an MNA Sub-Stack in the label stack. The description of the value is "MPLS Network Actions".

MPLS Network Actions Parameters IANA has created a registry group called "MPLS Network Actions". This registry group contains the "Network Action Flags Without Ancillary Data" registry (see ) and the "Network Action Opcodes" registry (see ).

Network Action Flags Without Ancillary Data For the "Network Action Flags Without Ancillary Data" registry, registration requests should comply with . Depending on the range, the registration procedure for this registry is "IETF Review", "Experimental Use", or "Private Use" (as defined in ). The fields in this registry are "Bit Position" (integer), "Description" (string), and "Reference" (string). Bit Position refers to the position relative to the most significant bit in LSE Format B or C Data fields and any subsequent Format D LSEs. Bit Position 0 is the most significant bit in an LSE Format B or C Data field. Bit Position 20 is the most significant bit in the first LSE Format D Data field. There are 20 bits available in LSE Format C and 30 bits available in LSE Format D. There are, at most, 14 Format D LSEs per opcode (due to the NASL limit of 15 and the constraint of Format D requiring a Format C LSE), so there are at most 20 + 14 * 30 = 440 bit positions. The value listed in the Bit Position column is an integer with value between 0-439. The initial registry has no entries. The registration procedures for code point allocation for this registry are defined in : Registration Procedures for the "Network Action Flags Without Ancillary Data" Registry

Range	Registration Procedure
0-14	IETF Review
15-16	Experimental Use
17-19	Private Use
20-439	IETF Review

Network Action Opcodes For the "Network Action Opcodes" registry, registration requests should comply with as well as the Security Considerations section (). Depending on the range, the registration procedure for this registry is "IETF Review", "Experimental Use", or "Private Use" (as defined in ). The fields are "Opcode" (integer), "Description" (string), and "Reference" (string). Opcode is an integer with value 1-126. Registration Procedures for the "Network Action Opcodes" Registry

Range	Registration Procedure
1-110	IETF Review
111-114	Experimental Use
115-126	Private Use
127	IETF Review

IANA has allocated values for the following network action opcodes from the "Network Action Opcodes" registry. Initial Contents of the "Network Action Opcodes" Registry

Opcode	Description	Reference
0	Reserved	RFC 9994
1	Flag-Based Network Action Indicators without AD	RFC 9994
2	No operation Opcode	RFC 9994
127	Opcode Range Extension Beyond 127	RFC 9994

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document specifies the encoding to be used by an LSR in order to transmit labeled packets on Point-to-Point Protocol (PPP) data links, on LAN data links, and possibly on other data links as well. This document also specifies rules and procedures for processing the various fields of the label stack encoding. [STANDARDS-TRACK] This document defines a flexible solution for support of Differentiated Services (Diff-Serv) over Multi-Protocol Label Switching (MPLS) networks. [STANDARDS-TRACK] This document describes Time To Live (TTL) processing in hierarchical Multi-Protocol Label Switching (MPLS) networks and is motivated by the need to formalize a TTL-transparent mode of operation for an MPLS label-switched path. It updates RFC 3032, "MPLS Label Stack Encoding". TTL processing in both Pipe and Uniform Model hierarchical tunnels are specified with examples for both "push" and "pop" cases. The document also complements RFC 3270, "MPLS Support of Differentiated Services" and ties together the terminology introduced in that document with TTL processing in hierarchical MPLS networks. [STANDARDS-TRACK] The early Multiprotocol Label Switching (MPLS) documents defined the form of the MPLS label stack entry. This includes a three-bit field called the "EXP field". The exact use of this field was not defined by these documents, except to state that it was to be "reserved for experimental use". Although the intended use of the EXP field was as a "Class of Service" (CoS) field, it was not named a CoS field by these early documents because the use of such a CoS field was not considered to be sufficiently defined. Today a number of standards documents define its usage as a CoS field. To avoid misunderstanding about how this field may be used, it has become increasingly necessary to rename this field. This document changes the name of the field to the "Traffic Class field" ("TC field"). In doing so, it also updates documents that define the current use of the EXP field. [STANDARDS-TRACK] Load balancing is a powerful tool for engineering traffic across a network. This memo suggests ways of improving load balancing across MPLS networks using the concept of "entropy labels". It defines the concept, describes why entropy labels are useful, enumerates properties of entropy labels that allow maximal benefit, and shows how they can be signaled and used for various applications. This document updates RFCs 3031, 3107, 3209, and 5036. [STANDARDS-TRACK] RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document discusses and recommends terminology that may be used when MPLS Special-Purpose Labels (SPLs) are specified and documented. This document applies that terminology change to the relevant IANA registry and also clarifies the use of the Entropy Label Indicator (7) when immediately preceded by the Extension Label (15). This document updates RFCs 3032 and 7274. This document describes an architectural framework for MPLS Network Action (MNA) technologies. MNA technologies are used to indicate actions that impact the forwarding or other processing (such as monitoring) of the packet along the Label Switched Path (LSP) of the packet and to transfer any additional data needed for these actions. This document provides the foundation for the development of a common set of network actions and information elements supporting additional operational models and capabilities of MPLS networks. Informative References This document specifies the architecture for Multiprotocol Label Switching (MPLS). [STANDARDS-TRACK] At first glance, the acronym "OAM" seems to be well-known and well-understood. Looking at the acronym a bit more closely reveals a set of recurring problems that are revisited time and again. This document provides a definition of the acronym "OAM" (Operations, Administration, and Maintenance) for use in all future IETF documents that refer to OAM. There are other definitions and acronyms that will be discussed while exploring the definition of the constituent parts of the "OAM" term. This memo documents an Internet Best Current Practice. This document provides guidelines for implementers regarding MPLS forwarding and a basis for evaluations of forwarding implementations. Guidelines cover many aspects of MPLS forwarding. Topics are highlighted where implementers might otherwise overlook practical requirements which are unstated or under emphasized or are optional for conformance to RFCs but are often considered mandatory by providers. Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226. Segment Routing (SR) enables any head-end node to select any path without relying on a hop-by-hop signaling technique (e.g., LDP or RSVP-TE). It depends only on "segments" that are advertised by link-state Interior Gateway Protocols (IGPs). An SR path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), an explicit configuration, or a Path Computation Element (PCE). This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) that allow a stateful PCE to compute and initiate Traffic-Engineering (TE) paths, as well as a Path Computation Client (PCC) to request a path subject to certain constraints and optimization criteria in SR networks. This document updates RFC 8408. This document specifies requirements for the development of MPLS Network Actions (MNAs) that affect the forwarding or other processing of MPLS packets. These requirements are informed by a number of proposals for additions to the MPLS information in the labeled packet to allow such actions to be performed, either by a transit or terminating Label Switching Router (i.e., the Label Edge Router - LER). This document defines the encapsulation for MPLS performance measurement with the Alternate-Marking Method, which performs flow-based packet loss, delay, and jitter measurements on MPLS traffic. This document presents use cases that have a common feature that may be addressed by encoding network action indicators and associated ancillary data within MPLS packets. There is community interest in extending the MPLS data plane to carry such indicators and ancillary data to address these use cases. The use cases described in this document are not an exhaustive set but rather the ones that have been actively discussed by members of the IETF MPLS, PALS, and DetNet Working Groups from the beginning of work on MPLS Network Action (MNA) until the publication of this document.

Examples

Network Action Encoding Examples

Network Action Flags Without AD

NAS with Network Action Flags 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MNA-Label=bSPL | TC |S| TTL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=1 | 13-bit Flags |R|IHS|S|NASL=0 |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

This is an example of a NAS with Flag-Based NAIs without AD. Details:

Opcode=1:

This opcode indicates that the LSE carries Flag-Based NAIs without AD.

Data:

The data field carries the Flag-Based NAIs.

S:

This is the bottom of the stack bit. Set if and only if this LSE is the bottom of the stack.

U:

Action to be taken if one of the NAIs is not recognized by the processing node.

NASL:

The NASL value is set to 0, as there are no additional LSEs.

NAL:

The NAL value is set to 0, as there are no additional AD encoded using Format D.

Network Action Flags Without AD Using LSE Format D 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MNA-Label=bSPL | TC |S| TTL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=2 | Data=0 |R|IHS|S|NASL=2 |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=1 | Flag-Based NAIs |S| NAIs |U|NAL=1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1| Additional Flag-Based NAIs |S|Flag-Based-NAIs| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

In this example, the NAS contains a Format B LSE with a No-Operation Opcode value 2. The next LSE uses Format C, but the network action flag is not in a bit position contained within the Format C LSE, so a single Format D LSE has been added to the NAS to carry the flag. NAL is set to 1 to indicate that Flag-Based NAIs are also encoded in the next LSE. NASL is set to 2 to indicate that two additional LSEs are used.

Network Action Opcode with AD

Network Action Opcode with Ancillary Data 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MNA-Label=bSPL | TC |S| TTL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=8 | Ancillary Data |R|IHS|S|NASL=0 |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

In this example, the NAS is carrying only one Network Action that requires 13 bits of AD. Details on the second LSE:

Opcode=8:

A network action allocation is outside of this document.

Data:

The data field contains 13 bits of AD.

Network Action Opcode with More AD with Format B A network action may require more AD than can fit in a single LSE. In this example, a Format D LSE is added to carry additional AD.

Network Action with Additional Ancillary Data 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MNA-Label=bSPL | TC |S| TTL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=10 | Ancillary Data |R|IHS|S|NASL=1 |U|NAL=1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1| Ancillary Data |S|Ancillary Data | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

In this example, opcode 10 is encoded in Format B, and it requires more than one LSE's worth of AD, so a Format D LSE is added. Details on the second LSE:

Opcode=10:

An opcode allocation is outside of this document.

Ancillary Data:

AD required to process the network action opcode 10.

NAL:

Length of additional LSEs used to encode its AD.

Details on the third LSE:

Ancillary Data:

22 bits of additional AD.

Ancillary Data:

8 bits of additional AD.

Network Action Opcode with More AD with Format C A network action may require more AD than can fit in a single LSE. In this example, a Format D LSE is added to carry additional AD.

Network Action with Additional Ancillary Data 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MNA-Label=bSPL | TC |S| TTL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=2 | Data=0 |R|IHS|S|NASL=2 |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=9 | Ancillary Data |S| AD |U|NAL=1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1| Ancillary Data |S|Ancillary Data | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

In this example, opcode 9 requires more than one LSE's worth of AD, so a Format D LSE is added. Details on the third LSE:

Opcode=9:

An opcode allocation is outside of this document.

Ancillary Data:

Most significant bits of AD.

AD:

4 bits of additional AD.

Details on the fourth LSE:

Ancillary Data:

22 bits of additional AD.

Ancillary Data:

8 bits of additional AD.

Network Action Processing Order The semantics of a network action can vary widely and the results of processing one network action may affect the processing of a subsequent network action. See .

Network Action Processing Order

In-Stack NA Processing Order 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MNA-Label=bSPL | TC |S| TTL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=8 | Ancillary Data |R|IHS|S|NASL=2 |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=7 | Ancillary Data7 |S| AD7 |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=1 | Flag-Based NAIs |S| NAI |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

In this example, opcode 8 is processed first, then opcode 7, and then the network action flags are processed from most significant to least significant. In a different case, some Flag-Based NAIs may need to be processed before opcode 7, and some Flag-Based NAIs may need to be processed after opcode 7. This can be done by causing some NAIs to appear earlier in the NAS.

Interleaving Network Actions 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MNA-Label=bSPL | TC |S| TTL | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=8 | Ancillary Data |R|IHS|S|NASL=3 |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=1 | 0x01 |S| NAI |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=7 | Ancillary Data7 |S| AD7 |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Opcode=1 | 0x02 |S| NAI |U|NAL=0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

In the above example, opcode 8 is processed first, then Flag-Based NAI 0x01 is processed, then opcode 7 is processed, and finally NAI 0x02 is processed.

Acknowledgments The authors of this document would like to thank the MPLS Working Group Open Design Team for the discussions and comments on this document. The authors would also like to thank for reviewing the IANA Considerations and providing many useful suggestions. The authors would like to thank , , , , and for reviewing this document and providing many useful suggestions. The authors would like to thank and , both from the University of Tuebingen, for reviewing and implementing the solution defined in this document in P4 pipeline. Also, thank you to for the Shepherd's review, for the OpsDir review, for the Rtgdir review, for the Secdir review, and for the AD review, , , , , and for the IESG review, which helped improve this document.

Contributors The following people have substantially contributed to this document: Cisco Systems, Inc.

jisu@cisco.com

Orange

bruno.decraene@orange.com

China Mobile

chengweiqiang@chinamobile.com

ZTE Corp.

xiao.min2@zte.com.cn

Verizon

luay.jalil@verizon.com

Huawei Technologies

Huawei Campus, No. 156 Beiqing Rd. Beijing 100095 China jie.dong@huawei.com

Huawei Technologies

China zhoutianran@huawei.com

Comcast

Bin_Wen@cable.comcast.com

Ciena

sboutros@ciena.com

Juniper Networks

United States of America tony.li@tony.li

Juniper Networks

United States of America jdrake@juniper.net

Authors' Addresses Cisco Systems, Inc.

Canada jrajaman@cisco.com

Cisco Systems, Inc.

Canada rgandhi@cisco.com

Broadcom

royi.zigler@broadcom.com

Futurewei Technologies

haoyu.song@futurewei.com

Juniper Networks

United States of America kireeti.ietf@gmail.com