Signaling MNA Capability Using IGP and BGP-LS

Introduction describes the architectural framework for MPLS Network Action (MNA) technologies.MNA technologies are used to indicate actions for Label Switched Paths (LSPs) and/or MPLS packets and to transfer data needed for these actions.The specific encoding mechanisms and header formats for these actions are defined in . Building upon these specifications, and specify the mechanisms for carrying Network Resource Partition (NRP) Selectors and In-situ OAM (IOAM) data fields, respectively, using MPLS Network Actions. The ingress node /Controller should obtain the network action of the nodes within the MNA infrastructure, which ensure that the encapsulated data packets by the ingress node can be correctly parsed by the on-path nodes. Specifically, while intermediate nodes can skip unsupported actions, the ingress node need to know whether the decapsulating node is capable of parsing and removing the MNA-related headers (e.g., NRP or IOAM data fields), thereby avoiding potential packet drops or forwarding errors This document defines how the ingress node knows of the network action all the on-path nodes within the MNA infrastructure. It defines a mechanism to signal the MPLS Network actions(MNA) using IGP and BGP-LS.

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.

Advertising MNA Using IS-IS This section defines the MNA-Capabilities Sub-TLV that are inserted into the IS-IS Router Capability that is defined in . The format of the MNA-Capabilities Sub-TLV is: where: Type: TBD1. Length: 4. Flags: 4 octet of flags. The following are defined:

S: 13-bit NRP Selector flag. If set, then the router is capable of processing 13-bit NRP Selector (NRPS13) (as defined in Section 2.1 of ) on all interfaces.
N: 20-bit NRP Selector (NRPS20) flag. If set, then the router is capable of processing 20-bit NRP Selector (NRPS13)(as defined in Section 2.2 of ) on all interfaces.
C: 20-bit Entropy and NRP Selector (ENRPS20) flag. If set, then the router is capable of processing 20-bit Entropy and NRP Selector (ENRPS20) (as defined in Section 2.3 of ) on all interfaces.
I: IOAM ISD flag. If set, it indicates that the router is capable of processing the IOAM option encoded as In-Stack Data (ISD) (as defined in Section 4.2 of ) on all interfaces.
P: IOAM PSD flag. If set, it indicates that the router is capable of processing the IOAM option carried in the PSD (as defined in Section 4.1 of ) on all interfaces.

The TLVs defined in this section are applicable to both OSPFv2, OSPFv3 and BGP-LS.

Advertising MNA Using OSPF This section defines the MNA-Capabilities TLV that are inserted into the Router Information Opaque LSA（for OSPFv2）and OSPFv3 Router Information Opaque LSA（for OSPFv3）(defined in ). The format of the MNA-Capabilities TLV is the same as section 2.

Signaling MNA in BGP-LS The IGP extensions defined in this document can be advertised via BGP-LS (distribution of Link-State and Traffic Engineering information using BGP) using existing BGP-LS TLVs. This section defines the following Node Attribute TLV:

Acknowledgements TBD.

IANA Considerations TBD.

Security Considerations Procedures and protocol extensions defined in this document do not affect the IS-IS, OSPFv2 , OSPFv3 and BGP security model. See Section 5 of for a discussion of IS-IS security, Section 5 of for a discussion of OSPFv2 TLV-encoding considerations, Section 7 of for a discussion of OSPFv3 security and Section 8 of for a discussion of BGP-LS security.