[arin-ppml] IPv6 Transition Policy (aka Soft Landing)
On Fri, Oct 8, 2010 at 12:00 PM, Chris Grundemann <cgrundemann at gmail.com> wrote:
> Rough Policy Text:
> ~ Requester defines classes in their network - only classes where IPv6
> is in production qualify for IPv6
> ~ New addresses must be deployed on dual-stacked interfaces plus one
> additional existing IPv4-only interface must be dual stacked, up to
> 80% of all interfaces.
> ~ The service that the address is used to provide must be fully IPv6
> accessible (if you deploy an A record, you must also have a AAAA and
> both must answer)
> ~ All end-sites must dual-stack all Internet facing services before
> getting this space
> ~ For each down stream customer site where these addresses are
> deployed, another pre-existing IPv4 only down stream site must also be
> IPv6 enabled, up to 80% of the total customer base.
Suggestion: keep it simple, keep it grounded.
"To qualify for additional IPv4 addresses, the requesting organization
must first deploy AAAA records for its most used customer-facing web
site and maintain IPv6 connectivity to it from the public Internet."
Or something similarly simple and terse. I'm not sure there's time to
get something like this through before depletion consumes the
addresses you would preserve, but I think you'll have a better chance
with something brief and readily accomplishable that kicks the
requester to start moving on IPv6.
William D. Herrin ................ herrin at dirtside.com bill at herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004