IANA IPv6 registry actions
gih at apnic.net
Tue Jun 13 03:40:33 CEST 2006
I could assert that such tardiness on the part of IANA will cause the
Internet as we know it to explode into lots of little tiny pieces, but I'm
pretty sure that I'd be lying!
At 10:03 AM 13/06/2006, David Conrad wrote:
>Yep. Will get to it asap. Hopefully it won't cause anyone any
>operational issues between now and when I can get the web pages
>On Jun 12, 2006, at 1:39 PM, Geoff Huston wrote:
>>Simple removal from http://www.iana.org/assignments/ipv6-unicast-
>>address-assignments should be appropriate, as that registry lists
>>current allocated address ranges and this range is no longer
>>currently allocations. (also remove footnote 5 and renumber foot
>>notes 6, and 7)
>>As per http://www.iana.org/assignments/ipv6-address-space, the
>>block then reverts to the status "Reserved by the IETF"
>>At 05:45 AM 13/06/2006, Kevin Loch wrote:
>>> > We'll be removing the ip6 delegation from .INT today.
>>>Would it be possible to update:
>>>to indicate the current status of 3ffe::/16?
>>>I'm not sure if simply marking it as "RESERVED" or deleting
>>>it from the enumerated list completely would give the clearest
>>>indication of it's current status (if it is in fact reserved
>>>as I haven't seen anything from IANA indicating this yet).
>>>The footnote  should also be updated to reflect current
>>>status. If the 3ffe::/16 line is deleted then the footnote could
>>>be moved to the first line as in:
>>>"IPV6 GLOBAL UNICAST ADDRESS ASSIGNMENTS  "
More information about the ipv6-ops