[mpls] Re: 1 week to comment : Resolving concerns with draft-ietf-mpls-mna-nrp-selector

["Zafar Ali (zali)" <[e-mail]>]

Hi Adrian, WG

I have couple of concerns.

1. NEW: " An implementation of this document must support receiving all three Opcodes, but may freely choose which one to use to encode an NRPS."

This is not acceptable - an implementation may just implement one of the NRPS encoding options.
I know your motivation for the proposed text is that the draft just proposes too many encoding options.
That connects it with my next comment.

2. NEW: "This document discusses a few options for using MPLS network actions to carry the NRP Selector."
As mentioned as part of the WGLC comment, I would like the current draft to limit to the 20-bit NRPSes, and to remove the 3rd 13-bit NRPS. The discussion can happen on the WGLC email.

Thanks

Regards … Zafar



On 12/2/25, 11:05 AM, "Adrian Farrel" <[e-mail] <mailto:[e-mail]>> wrote:


Hi,


This email asks for comments in a one week period ending at 16.00 GMT on 9th
December 2025.


An unresolved concern with draft-ietf-mpls-mna-nrp-selector was around what
happens if some implementations support just one Opcode and some just
another.


To clarify how implementations are supposed to behave, I'd like to propose
the following in Section 1. I believe it addresses the concerns without
destabilising the current text.


OLD
[I-D.ietf-mpls-mna-fwk] specifies an architectural framework for the
MPLS Network Actions (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 MNA
architecture can facilitate carrying the dedicated identifier based
NRP Selector in the MPLS label stack. This document discusses a few
options for using MPLS network actions to carry the NRP Selector.
The proposed encodings are compliant with the MNA header encoding
formats defined in [I-D.ietf-mpls-mna-hdr].
NEW
[I-D.ietf-mpls-mna-fwk] specifies an architectural framework for the
MPLS Network Actions (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 MNA
architecture can facilitate carrying the dedicated identifier based
NRPS in the MPLS label stack. This document defines three ways to
use MPLS network actions to carry the NRPS, each indicated by a
different MNA Opcode and compliant with the MNA header encoding
formats defined in [I-D.ietf-mpls-mna-hdr]. An implementation of this
document must support receiving all three Opcodes, but may freely
choose which one to use to encode an NRPS. Future documents may
define further NRPS formats using new Opcodes if necessary.
END


Could people please comment:
- Yes
- Yes, but <suggested changes>
- No, because <reason>


Thanks,
Adrian


_______________________________________________
mpls mailing list -- [e-mail] <mailto:[e-mail]>
To unsubscribe send an email to [e-mail] <mailto:[e-mail]>




Cisco Confidential