[Ivy] Re: [Int-area] Solicit Feedback on an AD sponsorship request of draft-pignataro-icmp-enviro-info (Ends 30/11/2026)

[Bob Hinden <[e-mail]>]

Eric, Med,

> On Oct 14, 2026, at 2:50 AM, Eric Vyncke (evyncke) <evyncke=[e-mail]> wrote:
> 
> Hi Med,
> 
> Thanks for asking.
> 
> With my INT AD hat, I would push back using ICMP for any use that is not about "IP control" and the used described in this draft is clearly not about the IP layer. As said at the mic line in OPSAWG at IETF-126, let's use a SNMP-like protocol for querying values (that are not linked to IP) of a device.

Good point.   I agree this would be better done with some other protocol other than ICMP for the reasons you stated.

Also, looking at the security considerations section of the draft, I think the environmental data carried needs to be encrypted for privacy and integrity.   That is another reason why ICMP is not a good choice for a protocol to carry this information.

Bob



> 
> Also, as noted by S. Moonesamy, the registry is FCFS, so a simple note to the IANA will be enough to get a code point, but to create other registries, a RFC is probably required.
> 
> Finally, I vastly prefer to have this I-D following the full WG process in int area if the author(s) insist to use ICMP, with an unclear success.
> 
> Regards,
> 
> -éric
> 
> 
> From: [e-mail] <[e-mail]>
> Date: Tuesday, 13 October 2026 at 08:58
> To: Internet Area <[e-mail]>; opsawg <[e-mail]>; Getting Ready for Energy-Efficient Networking Discussion List <[e-mail]>; Network Inventory YANG Discussion List <[e-mail]>
> Cc: [e-mail] <[e-mail]>
> Subject: [Int-area] Solicit Feedback on an AD sponsorship request of draft-pignataro-icmp-enviro-info (Ends 30/11/2026)
> 
> Hi all,
>  
> I received a request to AD-sponsor this Experimental I-D: https://datatracker.ietf.org/doc/draft-pignataro-icmp-enviro-info/. More details about AD-sponsored publication process can be found in the IESG Statement on “Guidance on Area Director Sponsoring of Documents” [1].
>  
> The document is in a boundary of several areas (INT/OPS) and its approach should be positioned vs. other tools defined in other WGs (e.g., IVY for inventory and GREEN for node capabilities).
>  
> Your feedback about the technical approach, deployablity, usability, whether this is (or not) suitable for publication in the IETF stream, whether this is better handled in an existing WG, etc. is highly appreciated. Also, please share your comments whether you think this should or should not be published as a RFC.
>  
> Please share your feedback before 30/11/2026. Thank you.
>  
> FWIW, I’m planning to make a decision (i.e., accept or decline the request) based on the feedback but ** not before we have a clear direction on Updated ICMP Use Policy effort (BCP189 <https://datatracker.ietf.org/doc/bcp189/>) **. A discussion is scheduled for IETF#127 [2].
>  
> Cheers,
> Med
>  
> [1] https://datatracker.ietf.org/doc/statement-iesg-guidance-on-area-director-sponsoring-of-documents-20070320/
>  
> [2] https://github.com/IETF-OPS-AD/OPSAREA-meetings/blob/main/ietf127.md#update-on-icmp-use-policy-ron-bonica-15-min
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> _______________________________________________
> Int-area mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]