[mpls] Re: AD review for draft-ietf-mpls-mna-fwk-10

[Tony Li <[e-mail]>]

Hi Jim,

> Thank you for a nicely written and easy to digest document. I have minimal comments as follows (note I have used the line numbers from nits for v-10 to highlight where in the document the comment is relevant):
> 
> 26             operational models and capabilities of MPLS networks.  Some of these
> 27             actions are defined in existing MPLS specifications, while others
> 28             require extensions to existing specifications to meet the
> 29             requirements found in "Requirements for Solutions that Support MPLS
> 30             Network Actions (MNA)".
> 
> Jim> I assume that the above sentence is talking about I-D.ietf-mpls-mna-requirements but as it is in the abstract it cannot contain a citation.

Exactly.

> Perhaps remove this last sentence as it is repeated and clarified in the Introduction section (?). Note also that I-D.ietf-mpls-mna-requirements is now RFC 9613 so please update this document throughout to reflect this.


Done


> 137          MNA technologies may redefine the semantics of the Label, Traffic
> 138          Class (TC), and Time to Live (TTL) fields in an MPLS Label Stack
> 139          Entry (LSE) within a NAS.
> 
> Jim> Please expand on NAS. I realize that it is defined in the terminology section, but it took me a minute to find it and stop scratching my head.


Done


> 221          | MSD          | Maximimum SID  | [RFC8491]                        |
> 
> Jim> s/Maximimum/Maximum


Done


> 266          Label.[RFC6790]
> 
> Jim> s/.[RFC6790]/[RFC6790].


Done


> 280          *  In-Stack Data (ISD): A set of zero or more LSEs that carry
> 281              ancillary data for the network actions that are present.  Network
> 282              action indicators are not considered ancillary data.
> 
> Jim> should Post-Stack Data (PSD) also be defined here for completeness (?)


PSD is already defined in RFC 9613. We can repeat that definition here if you like, but it is wholly redundant and the framework doesn’t have much to say about PSD. If we don’t proceed with PSD, it would seem like a distraction.

Tony