| Internet-Draft | MNA Capability advertisement | January 2026 |
| Chen & Zhao | Expires 31 July 2026 | [Page] |
This document defines a mechanism to signal MNA Capability using IGP and Border Gateway Protocol-Link State(BGP-LS).¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
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 31 July 2026.¶
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 (https://trustee.ietf.org/license-info) 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.¶
[RFC9789] 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 [I-D.ietf-mpls-mna-hdr].¶
Building upon these specifications, [I-D.ietf-mpls-mna-nrp-selector] and [I-D.ietf-mpls-mna-ioam] 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.¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This section defines the MNA-Capabilities Sub-TLV that are inserted into the IS-IS Router Capability that is defined in [RFC7981].¶
The format of the MNA-Capabilities Sub-TLV is:¶
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |P|I|C|N|S|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1. MNA-Capabilities Sub-TLV
¶
where:¶
Type: TBD1.¶
Length: 4.¶
Flags: 4 octet of flags. The following are defined:¶
The TLVs defined in this section are applicable to both OSPFv2, OSPFv3 and BGP-LS.¶
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 [RFC7770]). The format of the MNA-Capabilities TLV is the same as section 2.¶
The IGP extensions defined in this document can be advertised via BGP-LS (distribution of Link-State and Traffic Engineering information using BGP) [RFC7752] using existing BGP-LS TLVs.¶
This section defines the following Node Attribute TLV:¶
+============+==============================+
| Type | Description |
+============+==============================+
| TBD | the MNA-Capabilities TLV |
+------------+------------------------------+
¶
TBD.¶
TBD.¶
Procedures and protocol extensions defined in this document do not affect the IS-IS, OSPFv2 , OSPFv3 and BGP security model. See Section 5 of [RFC7981] for a discussion of IS-IS security, Section 5 of [RFC7684] for a discussion of OSPFv2 TLV-encoding considerations, Section 7 of [RFC8362] for a discussion of OSPFv3 security and Section 8 of [RFC7752] for a discussion of BGP-LS security.¶