[Int-area] Re: Shepherd Review for draft-ietf-intarea-extended-icmp-nodeid-02

[Luigi Iannone <[e-mail]>]

Hi Bill,

on last thing about the document.

I was preparing the writeup and reviewing again the IANA section and noticed that the document say nothing on the policy to allcated the remaining sub-types. Section 3.1.1 state in which order to allocate but not the type of action. First Come First Served? Expert Review ? 

Can you add a sentence at the end of the IANA section that states which type of action is needed to allocate sub-types?

Thanks

L.

> On 7 Aug 2025, at 15:11, Bill Fenner <[e-mail]> wrote:
> 
> Great, thanks, Luigi! I've submitted -03, which I believe addresses all of your comments and also Jen's.
> 
> Name:     draft-ietf-intarea-extended-icmp-nodeid
> Revision: 03
> Title:    Adding Extensions to ICMP Errors for Originating Node Identification
> Date:     2025-08-07
> Group:    intarea
> Pages:    12
> URL:      https://www.ietf.org/archive/id/draft-ietf-intarea-extended-icmp-nodeid-03.txt
> Status:   https://datatracker.ietf.org/doc/draft-ietf-intarea-extended-icmp-nodeid/
> HTML:     https://www.ietf.org/archive/id/draft-ietf-intarea-extended-icmp-nodeid-03.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-intarea-extended-icmp-nodeid
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-intarea-extended-icmp-nodeid-03
> 
> Abstract:
> 
>    RFC5837 describes a mechanism for Extending ICMP for Interface and
>    Next-Hop Identification, which allows providing additional
>    information in an ICMP error that helps identify interfaces
>    participating in the path.  This is especially useful in environments
>    where a given interface may not have a unique IP address to respond
>    to, e.g., a traceroute.
> 
>    This document introduces a similar ICMP extension for Node
>    Identification.  It allows providing a unique IP address and/or a
>    textual name for the node, in the case where each node may not have a
>    unique IP address (e.g., a deployment in which all interfaces have
>    IPv6 addresses and all nexthops are IPv6 nexthops, even for IPv4
>    routes).
> 
>   Bill
>