Subject: [Int-area] RFC Editor Note for draft-ietf-intarea-probe-10

From: Suresh Krishnan <[email-masked]>
Date: Thu, 1 Feb 2018 23:32:25 -0500

Hi all,
 The IANA evaluation of this document and the resulting codepoint allocation pointed out a potential misunderstanding regarding the desired range of code points (Thanks Amanda and Ron for sorting this out!). It would be nice to fix the IANA considerations text in the document to clarify this for posterity. I would like to take care of this with an RFC Editor Note instead of doing this during AUTH48. Please let me know if you have any comments or concerns regarding this.

Thanks
Suresh

OLD:
Add an entry to the "ICMPv6 "type" Numbers" registry, representing  the Extended Echo Reply.  This entry has the following codes: (0) No Error, (1) Malformed Query, (2) No Such Interface, (3) No Such Table Entry, (4) Multiple Interfaces Satisfy Query.

NEW:
Add an entry to the "ICMPv6 "type" Numbers" registry, representing  the Extended Echo Reply.  This entry has the following codes: (0) No Error, (1) Malformed Query, (2) No Such Interface, (3) No Such Table Entry, (4) Multiple Interfaces Satisfy Query. As ICMPv6 distinguishes between informational and error messages,  and this is an informational message, the value must be assigned  from the range 128-255.