Re: [mpls] draft-ietf-mpls-lsp-ping-ospfv3-codepoint-04.txt

[Loa Andersson <[e-mail]>]

Tom,

While I'm a great fan of references, I don't see that it is necessary in 
this case.

draft-ietf-mpls-lsp-ping-registries-update updates the Message Types, 
Reply Modes, Return Codes. TLV and sub-TLV registries.

The code point for draft-ietf-mpls-lsp-ping-ospfv3-codepoint is 
allocated from the "Protocol in the Segment ID sub-TLV" registry. This 
registry is not change, so I don't see that the scenario you describe 
below could play out.

/Loa

On 03/02/2021 01:39, tom petch wrote:
> I believe that this I-D needs a Normative Reference to
>               Updating the IANA MPLS LSP Ping Parameters
>               draft-ietf-mpls-lsp-ping-registries-update
> since that I-D updates the registry that this I-D then seeks to update and if this I-D gets there first then the update can be overridden by
>               Updating the IANA MPLS LSP Ping Parameters
>               draft-ietf-mpls-lsp-ping-registries-update-07
> and lost.
> 
> And this last I-D changes the meaning of the registry which could be seen as theoretically rendering this I-D invalid.
> 
> Tom Petch
> 
> From: mpls <[e-mail]> on behalf of [e-mail] <[e-mail]>
> Sent: 27 January 2021 20:58
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Multiprotocol Label Switching WG of the IETF.
> 
>          Title           : OSPFv3 CodePoint for MPLS LSP Ping
>          Authors         : Nagendra Kumar Nainar
>                            Carlos Pignataro
>                            Mustapha Aissaoui
>          Filename        : draft-ietf-mpls-lsp-ping-ospfv3-codepoint-04.txt
>          Pages           : 6
>          Date            : 2021-01-27
> 

-- 

Loa Andersson                        email: [e-mail]
Senior MPLS Expert                          [e-mail]
Bronze Dragon Consulting             phone: [phone]