[arin-discuss] IPv6 Provider Woes

[Ric Moseley]

I run several datacenters under a single ASN but with discreet IPv4
space. When I originally went to ARIN for IPv6 space, they allocated me
a /32.  I went to announce smaller /36 blocks out of that /32, and
discovered that one of my backbone providers (NTT) would not accept
anything smaller than a /32.  As a result, I went back to ARIN and told
them this.  They basically said I would have to work it out with NTT.
After going back and forth with NTT and pointing ARIN's rules out
several times, they changed their policy and implemented a fix to the
routers we peer with to allow down to a /36.  This took over 4 months
and they still have not rolled it out across their entire backbone (from
what I understand).  I am not bagging on NTT as they ultimately came
through for me; however, my point is that there needs to be some give
and take on both sides for IPv6 to be successful.

Thanks.

Ric Moseley
VP of Engineering
rmoseley at softlayer.com 
Softlayer Technologies, Inc.
www.softlayer.com 
214-442-0555 direct
972-989-7813 cell

-----Original Message-----
From: arin-discuss-bounces at arin.net
[mailto:arin-discuss-bounces at arin.net] On Behalf Of
michael.dillon at bt.com
Sent: Tuesday, November 25, 2008 4:58 AM
To: arin-discuss at arin.net
Subject: Re: [arin-discuss] IPv6 Provider Woes


> This is not to bash Verizon (specifically) but to point out 
> that there is a significant disconnect between the 
> marketplace and the RIR's already developing. 

This is nothing new. It is something that Verizon customers
should take up with their account managers, or switch to 
a Verizon competitor who doesn't have silly rules.

> is Verizon off their nut?

Exactly. Verizon is a big complex (read confusing) company
which means that the right hands rarely know or care what
the left hands are doing.

ARIN can't do anything about this directly.

Remember, the /32 prefix is supposed to go to the operator of
a single network. It may be that the Verizon customer actually
operates multiple networks and should therefore have multiple
/32s. Or maybe it's just one of those startup hiccups caused 
by the fact that nobody really knows how to do IPv6 Internet
routing yet, because nobody has much experience with it. There
are certainly a few people with some experience who have strong
opinions, but a consensus has yet to form. I suggest that the
whole transit-free tier 1 national network provider model of
IPv4 may not be the best one to follow for IPv6. It may make
more sense to put services like Google at the core of the
network, i.e. tier 1, rather than national networks.

--Michael Dillon
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (ARIN-discuss at arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-discuss
Please contact info at arin.net if you experience any issues.