Orbit

APNIC staff - how many organisations have been denied v6 space under the current proposal?

becaus eof the 200 limit

I don't know the numbers but it would be interesting to know whether there is considerable pent-up demand that would be released with a wording tweak.

<rant>

i love the tradition of speaking for those not present. one can claim anything! personally, i know that, if we painted the prefixes cerulean blue, that 2,319 more users would deploy ipv6.

but looking at actual measurements, e.g. foil 3 of the study of actual announcement, http://rip.psg.com/~randy/071022.v6-use.pdf, we see that allocations of ipv6 space within the apnic region continues on a steep curve. this would hint that the barrier to *allocation* is negligible.

on the other hand, on that same foil, note that actual bgp announcement, i.e. *use* of ipv6 allocations has been flat. i.e. people get the space and do not use it. this should give us a very big clue.

at best, removing the 200 limit will allow a few hoarders to pick up ipv6 space cheap which we will later complain about just as we complain about legacy ipv4 holders today. cheap thrills.

so sitting here tweaking some trivial words is a lazy and useless path. as is spinning fantasies about ipv6 saving battery life.

what is needed is to make ipv6 *usable* for the isps' customers. this is not so easy. i know as i have been putting some effort into it.

one is just documenting getting some servers and services converted. i have been keeping notes at http://rip.psg.com/~randy/ipv6-westin.html. i solicit and would appreciate further contributions and collection of clue.

second is planning an educational experiment at nanog, apricot, ietf, ripe, ... where ipv4 transit is shut off for an hour or so, and we show that pure ipv6 does not really work, what different ipv6 crutches are needed to actually deploy at an enterprise-like end site, and how to deploy those crutches so isps can do this for their customers. see the working notes at http://www.civil-tongue.net/clusterf/wiki/NANOG%20IPv6%20Hour%20-%20February%202008#NANOGIPv6Hour-February2008. again, contributions and clue would be appreciated. the engineering design team for this will actually be meeting monday in the bay area.

randy