[ppml] IPv6 initial allocation policy

Owen DeLong owen at delong.com
Tue Mar 14 00:44:20 EST 2006

I'd encourage as many businesses and members of the IPv6 Business Council 
care about this as possible to attend the Montreal meeting or comment on
PPML or both.


--On March 13, 2006 7:56:09 PM -0500 Daniel Golding 
<dgolding at burtongroup.com> wrote:

> On 3/13/06 11:07 AM, "Anthony A. Crumb" <Crumb_Anthony_A at cat.com> wrote:
> My organization has begun working through the definition of an enterprise
> IPv6 acquisition, allocation, and deployment strategy. I was charged with
> identifying the process required to acquire IPv6 address space from the
> three registrars (ARIN, RIPE, and APNIC) from which we currently have
> carrier independent IPv4 allocations. Our thoughts are, because we have a
> dual carrier connected Internet POP within each of these IPv4 allocations
> we should request provider independent IPv6 space from each of the
> registrars. Imagine my surprise when I found that each registrar has
> adopted a policy that does not allow for the assignment of carrier
> independent IPv6 address space to end customers. This policy runs counter
> to an obligation to our customers, supplier and dealer to provide no less
> than two connection paths into and out of our Internet facing network
> application environments. Not to mention robbing us of the leverage
> needed to be able to shop our very considerable WAN circuit business
> between carriers. Is anyone aware of a coalition of companies that is
> working together to over turn this policy?
> [snip]
> Apologies for the off-topic post, but I’d suggest any enterprises
> interested in this issue should contact the IPv6 Business Council, ASAP.

If this message was not signed with gpg key 0FE2AA3D, it's probably
a forgery.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20060313/79c7ab00/attachment-0001.sig>

More information about the ARIN-PPML mailing list