[187735] in North American Network Operators' Group
Re: Cogent & Google IPv6
daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Wed Feb 24 15:04:07 2016
X-Original-To: nanog@nanog.org
From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <56CE0A23.2030206@netassist.ua>
Date: Wed, 24 Feb 2016 15:04:02 -0500
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
To answer Matt=E2=80=99s question, NO.
Assume Cogent peers with NTT. Assume Google peers with NTT. NTT has very =
good v6 connectivity (not an assumption).
Cogent cannot send a packet to NTT and say =E2=80=9Cplease hand this to =
Google=E2=80=9D. Nor can Google hand a packet to NTT with a destination =
of Cogent.
Under this scenario, NTT is not being paid by Cogent or Google. Why =
would they take a packet from one and give it to the other?
--=20
TTFN,
patrick
> On Feb 24, 2016, at 2:53 PM, Max Tulyev <maxtul@netassist.ua> wrote:
>=20
> If you connected to Internet ONLY through Cogent - there is no other
> way. If you have another upstreams - Google should be reachable.
>=20
> On 24.02.16 21:46, Matt Hoppes wrote:
>> Correct me if I'm wrong, but if Cogent isn't peering with Google =
IPv6,
>> shouldn't the traffic flow out to one of their peer points where =
another
>> peer DOES peer with Google IPv6 and get you in?
>>=20
>> Isn't that how the Internet is suppose to work?
>>=20
>>=20
>> On 2/24/16 2:43 PM, Damien Burke wrote:
>>> Not sure. I got the same thing today as well.
>>>=20
>>> Is this some kind of ipv6 war?
>>>=20
>>> -----Original Message-----
>>> From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Ian Clark
>>> Sent: Wednesday, February 24, 2016 10:25 AM
>>> To: NANOG
>>> Subject: Cogent & Google IPv6
>>>=20
>>> Anyone know what's actually going on here? We received the =
following
>>> information from the two of them, and this just started a week or so =
ago.
>>>=20
>>>=20
>>> *=46rom Cogent, the transit provider for a branch office of ours:*
>>>=20
>>> Dear Cogent Customer,
>>>=20
>>> Thank you for contacting Cogent Customer Support for information =
about
>>> the Google IPv6 addresses you are unable to reach.
>>>=20
>>> Google uses transit providers to announce their IPv4 routes to =
Cogent.
>>>=20
>>> At this time however, Google has chosen not to announce their IPv6
>>> routes to Cogent through transit providers.
>>>=20
>>> We apologize for any inconvenience this may cause you and will =
notify
>>> you if there is an update to the situation.
>>>=20
>>>=20
>>>=20
>>> *=46rom Google (re: Cogent):*
>>>=20
>>> Unfortunately it seems that your transit provider does not have IPv6
>>> connectivity with Google. We suggest you ask your transit provider =
to
>>> look for alternatives to interconnect with us.
>>>=20
>>> Google maintains an open interconnect policy for IPv6 and welcomes =
any
>>> network to peer with us for access via IPv6 (and IPv4). For those
>>> networks that aren't able, or chose not to peer with Google via =
IPv6,
>>> they are able to reach us through any of a large number of transit
>>> providers.
>>>=20
>>> For more information in how to peer directly with Google please =
visit
>>> https://peering.google.com
>>>=20
>>>=20
>>> --=20
>>> Ian Clark
>>> Lead Network Engineer
>>> DreamHost
>>>=20
>>=20
