[137393] in North American Network Operators' Group
Re: My upstream ISP does not support IPv6
daemon@ATHENA.MIT.EDU (Matthew Petach)
Fri Feb 11 22:24:49 2011
In-Reply-To: <185E6979-5F80-4F7A-8DE6-562132264990@delong.com>
Date: Fri, 11 Feb 2011 19:24:03 -0800
From: Matthew Petach <mpetach@netflight.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Fri, Feb 4, 2011 at 4:33 PM, Owen DeLong <owen@delong.com> wrote:
> I'll start..
>
> Hurricane Electric =A0 =A0 =A0Happily and readily provided me IPv6 Transi=
t on request.
> Layer42 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Happily and readi=
ly provided me IPv6 Transit on request.
>
> Owen
I'll second that--I've had native v6 connectivity with Layer42 at home, wit=
h a
secondary path via HE tunnelbroker via a secondary physical path for many,
many moons, and have had no complaints.
For those with smaller-sized connectivity needs, it's likely you'll have be=
tter
success getting v6 connectivity from a tier-2 provider, as there's less non=
-v6-
compliant hardware and software that needs to be taken into consideration.
There's also likely to be some level of impedance mismatch between the
upgrade priority for high-bandwidth-customer gear and low-bandwidth-custome=
r
gear at large-sized ISPs, which may relegate you to a slower deployment
scheduled than if you bring the question up with your local tier 2 provider=
.
Matt
