draft-chen-lsr-mpls-mna-capability-03.txt   draft-chen-lsr-mpls-mna-capability-04.txt 
LSR R. Chen LSR Working Group R. Chen
Internet-Draft D. Zhao Internet-Draft D. Zhao
Intended status: Standards Track ZTE Corporation Intended status: Standards Track ZTE Corporation
Expires: 23 January 2026 19 July 2025 Expires: 31 July 2026 27 January 2026
Signaling MNA Capability Using IGP and BGP-LS Signaling MNA Capability Using IGP and BGP-LS
draft-chen-lsr-mpls-mna-capability-03 draft-chen-lsr-mpls-mna-capability-04
Abstract Abstract
This document defines a mechanism to signal MNA Capability using IGP This document defines a mechanism to signal MNA Capability using IGP
and Border Gateway Protocol-Link State(BGP-LS). and Border Gateway Protocol-Link State(BGP-LS).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 23 January 2026. This Internet-Draft will expire on 31 July 2026.
Copyright Notice Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the Copyright (c) 2026 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Advertising MNA Using IS-IS . . . . . . . . . . . . . . . . . 3 2. Advertising MNA Using IS-IS . . . . . . . . . . . . . . . . . 3
3. Advertising MNA Using OSPF . . . . . . . . . . . . . . . . . 4 3. Advertising MNA Using OSPF . . . . . . . . . . . . . . . . . 4
4. Signaling MNA in BGP-LS . . . . . . . . . . . . . . . . . . . 4 4. Signaling MNA in BGP-LS . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4
8. Normative References . . . . . . . . . . . . . . . . . . . . 5 8. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
[I-D.ietf-mpls-mna-fwk] specifies an architectural framework for the [RFC9789] describes the architectural framework for MPLS Network
MPLS Network Actions (MNA) technologies. MNA technologies are used Action (MNA) technologies.MNA technologies are used to indicate
to indicate actions for Label Switched Paths (LSPs) and MPLS packets actions for Label Switched Paths (LSPs) and/or MPLS packets and to
to transfer data needed for these actions. 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] defines the syntax and semantics of network [I-D.ietf-mpls-mna-hdr].
actions encoded within an MPLS Label Stack. Network actions can be
encoded with or without Ancillary Data (AD), either in or after the
label stack. It defines four types of Label Stack Entry Formats.
However, for the same network action, multiple encoding format are Building upon these specifications, [I-D.ietf-mpls-mna-nrp-selector]
defined. For example, [I-D.li-mpls-mna-entropy]describes a network and [I-D.ietf-mpls-mna-ioam] specify the mechanisms for carrying
action for entropy and uses LSE Format C to encoded entropy action Network Resource Partition (NRP) Selectors and In-situ OAM (IOAM)
within an MPLS Label Stack. [RFC6790]defines MPLS encapsulation with data fields, respectively, using MPLS Network Actions.
ELI and entropy labels; [I-D.ietf-mpls-mna-nrp-selector] describes a
network action for NRP Selector, and it defines LSE Format B or LSE
Format C maybe used to carry the NRP Selector.
The ingress node /Controller should obtain the network action of the The ingress node /Controller should obtain the network action of the
nodes within the MNA infrastructure, which ensure that the nodes within the MNA infrastructure, which ensure that the
encapsulated data packets by the ingress node can be correctly parsed encapsulated data packets by the ingress node can be correctly parsed
by the on-path nodes. 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 This document defines how the ingress node knows of the network
action all the on-path nodes within the MNA infrastructure. It action all the on-path nodes within the MNA infrastructure. It
defines a mechanism to signal the MPLS Network actions(MNA) using IGP defines a mechanism to signal the MPLS Network actions(MNA) using IGP
and BGP-LS. and BGP-LS.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 3, line 20 skipping to change at page 3, line 12
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. Advertising MNA Using IS-IS 2. Advertising MNA Using IS-IS
This section defines the MNA-Capabilities Sub-TLV that are inserted This section defines the MNA-Capabilities Sub-TLV that are inserted
into the IS-IS Router Capability that is defined in [RFC7981]. into the IS-IS Router Capability that is defined in [RFC7981].
The format of the MNA-Capabilities Sub-TLV is: The format of the MNA-Capabilities Sub-TLV is:
0 1 2 3 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 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 | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |P|C|N|S|E| | |P|I|C|N|S|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1. MNA-Capabilities Sub-TLV
Figure 1
where: where:
Type: TBD. Type: TBD1.
Length: 4. Length: 4.
Flags: 4 octet of flags. The following are defined: Flags: 4 octet of flags. The following are defined:
* E: Entropy flag. If set, then the router is capable of processing
Entropy action in LSE Format B on all interfaces.
* S: 13-bit NRP Selector flag. If set, then the router is capable * S: 13-bit NRP Selector flag. If set, then the router is capable
of processing 13-bit NRP Selector (NRPS13) on all interfaces. of processing 13-bit NRP Selector (NRPS13) (as defined in
Section 2.1 of [I-D.ietf-mpls-mna-nrp-selector]) on all
interfaces.
* N: 20-bit NRP Selector (NRPS20). If set, then the router is * N: 20-bit NRP Selector (NRPS20) flag. If set, then the router is
capable of processing 20-bit NRP Selector (NRPS13) on all capable of processing 20-bit NRP Selector (NRPS13)(as defined in
Section 2.2 of [I-D.ietf-mpls-mna-nrp-selector]) on all
interfaces. interfaces.
* C: 20-bit Entropy and NRP Selector (ENRPS20). If set, then the * C: 20-bit Entropy and NRP Selector (ENRPS20) flag. If set, then
router is capable of processing 20-bit Entropy and NRP Selector the router is capable of processing 20-bit Entropy and NRP
(ENRPS20) on all interfaces. Selector (ENRPS20) (as defined in Section 2.3 of
[I-D.ietf-mpls-mna-nrp-selector]) on all interfaces.
* P: Performance Measurement with Alternate Marking Method (PMAMM) * I: IOAM ISD flag. If set, it indicates that the router is capable
flag. If set, then the router is capable of processing PMAMM on of processing the IOAM option encoded as In-Stack Data (ISD) (as
all interfaces. defined in Section 4.2 of [I-D.ietf-mpls-mna-ioam]) 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 [I-D.ietf-mpls-mna-ioam]) on all interfaces.
The TLVs defined in this section are applicable to both OSPFv2, The TLVs defined in this section are applicable to both OSPFv2,
OSPFv3 and BGP-LS. OSPFv3 and BGP-LS.
3. Advertising MNA Using OSPF 3. Advertising MNA Using OSPF
This section defines the MNA-Capabilities TLV that are inserted into This section defines the MNA-Capabilities TLV that are inserted into
the Router Information Opaque LSA（for OSPFv2）and OSPFv3 Router the Router Information Opaque LSA（for OSPFv2）and OSPFv3 Router
Information Opaque LSA（for OSPFv3）(defined in [RFC7770]). The format Information Opaque LSA（for OSPFv3）(defined in [RFC7770]). The format
of the MNA-Capabilities TLV is the same as section 2. of the MNA-Capabilities TLV is the same as section 2.
4. Signaling MNA in BGP-LS 4. Signaling MNA in BGP-LS
The IGP extensions defined in this document can be advertised via The IGP extensions defined in this document can be advertised via
BGP-LS (distribution of Link-State and Traffic Engineering BGP-LS (distribution of Link-State and Traffic Engineering
information using BGP) [RFC7752] using existing BGP-LS TLVs. information using BGP) [RFC7752] using existing BGP-LS TLVs.
This section defines the following Node Attribute TLV: This section defines the following Node Attribute TLV:
+============+==============================+ +============+==============================+
| Type | Description | | Type | Description |
+============+==============================+ +============+==============================+
| TBD | the MNA-Capabilities TLV | | TBD | the MNA-Capabilities TLV |
+------------+------------------------------+ +------------+------------------------------+
Figure 2
5. Acknowledgements 5. Acknowledgements
TBD. TBD.
6. IANA Considerations 6. IANA Considerations
TBD. TBD.
7. Security Considerations 7. Security Considerations
Procedures and protocol extensions defined in this document do not Procedures and protocol extensions defined in this document do not
affect the IS-IS, OSPFv2 , OSPFv3 and BGP security model. See the affect the IS-IS, OSPFv2 , OSPFv3 and BGP security model. See
"Security Considerations"section of [RFC7981] for a discussion of IS- Section 5 of [RFC7981] for a discussion of IS-IS security, Section 5
IS security, [RFC7684] for a discussion of OSPFv2 security, the of [RFC7684] for a discussion of OSPFv2 TLV-encoding considerations,
"Security Considerations"section of [RFC8362] for a discussion of Section 7 of [RFC8362] for a discussion of OSPFv3 security and
OSPFv3 security and [RFC4271] for a discussion of OSPFv2 security. Section 8 of [RFC7752] for a discussion of BGP-LS security.
8. Normative References 8. Normative References
[I-D.ietf-mpls-mna-fwk]
Andersson, L., Bryant, S., Bocci, M., and T. Li, "MPLS
Network Actions (MNA) Framework", Work in Progress,
Internet-Draft, draft-ietf-mpls-mna-fwk-10, 6 August 2024,
<https://datatracker.ietf.org/doc/html/draft-ietf-mpls-
mna-fwk-10>.
[I-D.ietf-mpls-mna-hdr] [I-D.ietf-mpls-mna-hdr]
Rajamanickam, J., Gandhi, R., Zigler, R., Song, H., and K. Rajamanickam, J., Gandhi, R., Zigler, R., Song, H., and K.
Kompella, "MPLS Network Action (MNA) Sub-Stack Solution", Kompella, "MPLS Network Action (MNA) Sub-Stack
Work in Progress, Internet-Draft, draft-ietf-mpls-mna-hdr- Specification including In-Stack Network Actions and
08, 30 August 2024, Data", Work in Progress, Internet-Draft, draft-ietf-mpls-
mna-hdr-18, 13 January 2026,
<https://datatracker.ietf.org/doc/html/draft-ietf-mpls- <https://datatracker.ietf.org/doc/html/draft-ietf-mpls-
mna-hdr-08>. mna-hdr-18>.
[I-D.ietf-mpls-mna-ioam]
Gandhi, R., Mirsky, G., Li, T., Song, H., and B. Wen,
"Supporting In Situ Operations, Administration and
Maintenance Using MPLS Network Actions", Work in Progress,
Internet-Draft, draft-ietf-mpls-mna-ioam-04, 20 November
2025, <https://datatracker.ietf.org/doc/html/draft-ietf-
mpls-mna-ioam-04>.
[I-D.ietf-mpls-mna-nrp-selector] [I-D.ietf-mpls-mna-nrp-selector]
Li, T., Drake, J., Beeram, V. P., Saad, T., and I. Meilik, Li, T., Beeram, V. P., Drake, J., Saad, T., and I. Meilik,
"MPLS Network Actions for Network Resource Partition "MPLS Network Actions for Network Resource Partition
Selector", Work in Progress, Internet-Draft, draft-ietf- Selector", Work in Progress, Internet-Draft, draft-ietf-
mpls-mna-nrp-selector-00, 13 May 2025, mpls-mna-nrp-selector-03, 23 December 2025,
<https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna- <https://datatracker.ietf.org/doc/html/draft-ietf-mpls-
nrp-selector-00>. mna-nrp-selector-03>.
[I-D.li-mpls-mna-entropy]
Li, T. and J. Drake, "MPLS Network Action for Entropy",
Work in Progress, Internet-Draft, draft-li-mpls-mna-
entropy-03, 30 August 2024,
<https://datatracker.ietf.org/doc/html/draft-li-mpls-mna-
entropy-03>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>.
[RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and
L. Yong, "The Use of Entropy Labels in MPLS Forwarding",
RFC 6790, DOI 10.17487/RFC6790, November 2012,
<https://www.rfc-editor.org/info/rfc6790>.
[RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute
Advertisement", RFC 7684, DOI 10.17487/RFC7684, November Advertisement", RFC 7684, DOI 10.17487/RFC7684, November
2015, <https://www.rfc-editor.org/info/rfc7684>. 2015, <https://www.rfc-editor.org/info/rfc7684>.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<https://www.rfc-editor.org/info/rfc7752>. <https://www.rfc-editor.org/info/rfc7752>.
skipping to change at page 6, line 45 skipping to change at page 6, line 19
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and [RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and
F. Baker, "OSPFv3 Link State Advertisement (LSA) F. Baker, "OSPFv3 Link State Advertisement (LSA)
Extensibility", RFC 8362, DOI 10.17487/RFC8362, April Extensibility", RFC 8362, DOI 10.17487/RFC8362, April
2018, <https://www.rfc-editor.org/info/rfc8362>. 2018, <https://www.rfc-editor.org/info/rfc8362>.
[RFC9089] Xu, X., Kini, S., Psenak, P., Filsfils, C., Litkowski, S., [RFC9789] Andersson, L., Bryant, S., Bocci, M., and T. Li, "MPLS
and M. Bocci, "Signaling Entropy Label Capability and Network Actions (MNAs) Framework", RFC 9789,
Entropy Readable Label Depth Using OSPF", RFC 9089, DOI 10.17487/RFC9789, July 2025,
DOI 10.17487/RFC9089, August 2021, <https://www.rfc-editor.org/info/rfc9789>.
<https://www.rfc-editor.org/info/rfc9089>.
Authors' Addresses Authors' Addresses
Ran Chen Ran Chen
ZTE Corporation ZTE Corporation
Nanjing Nanjing
China China
Email: chen.ran@zte.com.cn Email: chen.ran@zte.com.cn
Detao Zhao Detao Zhao
ZTE Corporation ZTE Corporation
Nanjing Nanjing
China China
 End of changes. 27 change blocks. 
96 lines changed or deleted 82 lines changed or added

This html diff was produced by rfcdiff 1.49. The latest version is available from https://github.com/ietf-tools/rfcdiff