[123535] in North American Network Operators' Group
Re: IPv6 enabled carriers?
daemon@ATHENA.MIT.EDU (Michael Hallgren)
Wed Mar 10 15:08:27 2010
From: Michael Hallgren <m.hallgren@free.fr>
To: Seth Mattinen <sethm@rollernet.us>
In-Reply-To: <4B97F08B.2070500@rollernet.us>
Date: Wed, 10 Mar 2010 21:07:45 +0100
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--=-VJxYZEcb/bz1HPiyqYA6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Le mercredi 10 mars 2010 =C3=A0 11:18 -0800, Seth Mattinen a =C3=A9crit :
> On 3/10/10 11:00 AM, Charles Mills wrote:
> > Does anyone have a list of carriers who are IPv6 capable today?
> >=20
> > I would assume this would be rolled out in larger cities first but
> > anything outside of "testbed environments" and "trials" as in
> > Comcast's recent announcement seems to be all that is available.
> >=20
> > I'm being tasked with coming up with an IPv6 migration plan for a data =
center.
> >=20
> > Mostly interested in if ATT, Level3, GLBX, Saavis, Verizon Business
> > and Qwest are capable as those are the typical ones I deal with.
> >=20
>=20
> Ones I have personal experience with:
>=20
> GLBX - yes
> SAVVIS - no
> VZB - yes, good luck
> ATT - "Beginning in 1Q2010 MIS will provide the ability to support IPv6
> in a dual stack mode."
>=20
> When I disconnected my SAVVIS circuit in November 2009 I explicitly told
> them IPv6 was a deciding factor. Not all of Verizon's pops are IPv6
> enabled, which may cause you trouble ordering it. It's put me in month
> 11 of trying to turn up a dual-stack circuit because they refuse to read
> the order and keep putting it in Sacramento (v4 only) when it needs to
> go to San Jose (dual-stack). Sprint wasn't on your list, but they are
> rolling out native IPv6 support on all of 1239. I've been using their
> 6175 testbed since 2005.
>=20
+ Tata AS6453, production network since quite some time now, dual stack.
mh
> ~Seth
>=20
--=20
michael hallgren, mh2198-ripe
--=-VJxYZEcb/bz1HPiyqYA6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Ceci est une partie de message
=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkuX/AsACgkQZNZ/rrgsqae1XwCfSf+kN1yxOnZDDdFTSYNm7IJj
Wd8AoJpKUJbbTEMm9TcvjKtcsCWKO32q
=dq2p
-----END PGP SIGNATURE-----
--=-VJxYZEcb/bz1HPiyqYA6--
