Administration of the IANA Special Purpose IPv6 Address Block
RFC 4773

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

(Brian Carpenter) Yes

Comment (2006-10-03)
No email
send info
Possible editorial clarification to the first sentence of the last paragraph of section 2:

OLD:
   This document directs IANA to open a Special Purpose IPv6 address
   registry for the management of these IANA-designated address blocks.

NEW:
   The present document directs IANA to open a Special Purpose IPv6 address
   registry for the management of these IANA-designated address blocks.

(Dan Romascanu) Yes

Comment (2006-09-20)
No email
send info
1. Comment from Juergen Schoenwaelder who reviewed the document on behalf of the security directorate:

I suggest to change the title to make it clear for the reader that this document talks about IPv6 address blocks by inserting "IPv6" into the title:

     Administration of the IANA Special Purpose IPv6 Address Block

2. idnits problems:

idnits 1.109 

tmp/draft-huston-ipv6-iana-specials-01.txt:


  Checking nits according to http://www.ietf.org/ID-Checklist.html:
    
    Checking conformance with RFC 3978/3979 boilerplate...

  * The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. 

    RFC 3978 Section 5.4 paragraph 2 text:
    "This document is subject to the rights, licenses and restrictions
    contained in BCP 78, and except as set forth therein, the authors
    retain all their rights."

  * The document seems to lack an RFC 3978 Section 5.5 Disclaimer. 

    RFC 3978bis Section 5.5 text:
    "This document and the information contained herein are provided on an
    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."

  * The document seems to lack an RFC 3979 Section 5, para 2 IPR Disclosure
    Acknowledgement -- however, there's a paragraph with a matching beginning.
    Boilerplate error?

    RFC 3979 Section 5 paragraph 2 text:
    "Copies of IPR disclosures made to the IETF Secretariat and any
    assurances of licenses to be made available, or the result of an
    attempt made to obtain a general license or permission for the use of
    such proprietary rights by implementers or users of this
    specification can be obtained from the IETF on-line IPR repository at
    http://www.ietf.org/ipr."
  
    ... text found in draft:
    "Copies of IPR disclosures made to the IETF Secretariat and any
    assurances of license")
.........................^


  * The document seems to lack an RFC 3979 Section 5, para 3 IPR Disclosure
    Invitation. 

    RFC 3979 Section 5 paragraph 3 text:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at
    ietf-ipr@ietf.org."

(Jari Arkko) No Objection

(Lisa Dusseault) No Objection

Lars Eggert (was Discuss) No Objection

Comment (2006-09-26)
No email
send info
Section 1., paragraph 1:
>    This is a direction to IANA concerning the management of the IANA
>    Special Purpose IPv6 address assignment registry.

  Nit: Consider removing (identical to abstract).

(Bill Fenner) No Objection

(Russ Housley) No Objection

Comment (2006-09-25)
No email
send info
  From SecDir Review by Juergen Schoenwaelder:

  I suggest to change the title to make it clear for the reader that
  this document talks about IPv6 address blocks by inserting "IPv6" into
  the title:

     Administration of the IANA Special Purpose IPv6 Address Block

(Cullen Jennings) No Objection

(Mark Townsley) No Objection

(Magnus Westerlund) No Objection

(David Kessens) Recuse

Comment (2006-09-28)
No email
send info
I was part of the Adhoc team which was involved with this document