Hi Ron, We need to ask for one more thing that we didn't ask for in our review, and it's because there's an error in the registration procedure data in the registries. Both https://www.iana.org/assignments/icmpv6-parameters and https://www.iana.org/assignments/icmp-parameters incorrectly state that the IESG Approval or Standards Action are the registration procedures for all "Code" registries.
However, RFC 4443 and RFC 2780 state that "The policy for assigning Code values for new IPv6 ICMP Types not defined in this document should be defined in the document defining the new Type" (https://tools.ietf.org/html/rfc4443#section-6.1) and "The policy for assigning Code values for new IPv4 ICMP Types should be defined in the document defining the new Type value" (https://tools.ietf.org/html/rfc2780, section 6). Can you provide registration procedures for all of the Code registries? For our purposes, these could be added to the document as late as after IESG approval, when we're completing the actions, if that's more convenient/appropriate. Was our identification of 15 as the maximum values for the Code registries correct? Amanda On Tue Dec 12 21:14:40 2017, rbon...@juniper.net wrote: > Folks, > > I have posted a new version of draft-ietf-intarea-probe reflecting > IETF LC comments from Joel, Stewart, Stephan, Yaron and Amanda. Please > take a look at the document to make sure that I have addressed your > comments satisfactorily. > > Ron > > > -----Original Message----- > From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] > Sent: Tuesday, December 12, 2017 3:59 PM > To: Ron Bonica <rbon...@juniper.net>; Mohamed Boucadair > <mohamed.boucad...@orange.com>; Jen Linkova <fu...@google.com>; Reji > Thomas <rejitho...@juniper.net>; J. Linkova <fu...@google.com>; Chris > Lenart <chris.len...@verizon.com> > Subject: New Version Notification for draft-ietf-intarea-probe-08.txt > > > A new version of I-D, draft-ietf-intarea-probe-08.txt has been > successfully submitted by Ron Bonica and posted to the IETF > repository. > > Name: draft-ietf-intarea-probe > Revision: 08 > Title: PROBE: A Utility For Probing Interfaces > Document date: 2017-12-12 > Group: intarea > Pages: 17 > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-intarea-probe/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-intarea-probe-08 > https://datatracker.ietf.org/doc/html/draft-ietf-intarea-probe-08 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-intarea-probe-08 > > Abstract: > This document describes a network diagnostic tool called PROBE. > PROBE is similar to PING, in that it can be used to query the > status > of a probed interface. It differs from PING in that it does not > require bidirectional connectivity between the probing and probed > interfaces. Instead, PROBE requires bidirectional connectivity > between the probing interface and a proxy interface. The proxy > interface can reside on the same node as the probed interface or it > can reside on a node to which the probed interface is directly > connected. This document updates RFC 4884. > > > > > Please note that it may take a couple of minutes from the time of > submission until the htmlized version and diff are available at > tools.ietf.org. > > The IETF Secretariat > _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
