IANA IPv4 Special Purpose Address Registry
RFC 5736

Note: This ballot was opened for revision 02 and is now closed.

(Jari Arkko) Yes

Comment (2009-08-13)
No email
send info
Shouldn't RFC 5226 be a normative reference (e.g., this document uses specific terms and rules from RFC 5226)?

(Ron Bonica) Yes

(Russ Housley) Yes

(Ralph Droms) No Objection

(Lisa Dusseault) No Objection

(Lars Eggert) (was Discuss) No Objection

Comment (2009-08-11)
No email
send info
Section 6., paragraph 1:
>    [IANA]     IANA, "IANA Matrix for Protocol Parameter Assignment/
>               Registration Procedures",
>               <http://www.iana.org/numbers.html>.

  Unused Reference: 'IANA' is defined on line 192, but no explicit
  reference was found in the text


Section 6., paragraph 3:
>    [RFC2928]  Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial
>               IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000.

  Unused Reference: 'RFC2928' is defined on line 200, but no explicit
  reference was found in the text

(Pasi Eronen) No Objection

(Adrian Farrel) No Objection

(Cullen Jennings) No Objection

Alexey Melnikov No Objection

Comment (2009-08-08 for -)
No email
send info
3.  IANA Considerations

   This recommendation concerns the management of the address pool used
   for IETF protocol assignments as documented in [rfc3330bis] in
   [date], namely 192.0.0.0/24.

"in [date]" looks like a placeholder.


The document doesn't use any RFC 2119, but I suppose this is Ok.

(Tim Polk) No Objection

(Robert Sparks) No Objection