[107055] in North American Network Operators' Group
Re: It's Ars Tech's turn to bang the IPv4 exhaustion drum
daemon@ATHENA.MIT.EDU (Matthew Kaufman)
Fri Aug 22 17:28:03 2008
Date: Fri, 22 Aug 2008 14:24:18 -0700
From: Matthew Kaufman <matthew@eeph.com>
To: nanog@nanog.org
In-Reply-To: <20080818170922.GB10900@cgi.jachomes.com>
Reply-To: matthew@eeph.com
Errors-To: nanog-bounces@nanog.org
Jay R. Ashworth wrote:
> http://arstechnica.com/news.ars/post/20080817-were-running-out-of-ipv4-addresses-time-for-ipv6-really.html
>
> Well, on reading it, it's more an "IPv6: It's great -- ask for
> it by name!" piece.
>
This article reminded me that I really needed to stop relying on a
tunnel over my backup DSL line for IPv6 and spend the time to get my own
ISP on the road to deploying IPv6.
Step 1: Request address space from ARIN
Took <1 day to get a reply that we'd be getting the space that day, a
few more hours to receive a /32. That was easy.
Step 2: Get set up for IPv6 peering and transit
Took 30 minutes for Equinix to tell me that all I need to do is fill out
a form and I'm all set. Even quicker than ARIN.
Took a little over 2 days for my transit provider (Abovenet) to tell me
that they don't offer IPv6 transit and don't know when they will.
Native IPv6 isn't important enough for me to spend money on a new
transit provider on yet, so I guess maybe next year we'll try this again
and see what's changed. In the meantime, I need to upgrade some routers
(including some that went EOL before IPv6 support came along) anyway.
Matthew Kaufman
http://www.matthew.at
