On Thu, Mar 10, 2016 at 10:09 AM, Dennis Burgess
<[email protected]> wrote:
> Not wishing to get into a pissing war with who is right or wrong, but it
> sounds like google already pays or has an agreement with cogent for v4, as
> that's unaffected, cogent says google is simply not advertising v6 prefixes
> to them, so, how is that cogent's fault?
>
Did you check that on Cogent's LookingGlass?
"BGP routing table entry for 216.239.32.0/24, version 3740382954
Paths: (1 available, best #1, table Default-IP-Routing-Table)
6453 15169
154.54.13.206 (metric 10102020) from 154.54.66.21 (154.54.66.21)
Origin IGP, metric 4294967294, localpref 100, valid, internal, best
Community: 174:10031 174:20666 174:21000 174:22013
Originator: 66.28.1.9, Cluster list: 154.54.66.21"
is a lookup on: http://www.cogentco.com/en/network/looking-glass
if 216.239.32.0 - which holds ns1.google.com... I'd expect that
ns1.google.com would be routed via the majority of links 15169 has
with the world.
>
> -----Original Message-----
> From: Jon Lewis [mailto:[email protected]]
> Sent: Wednesday, March 9, 2016 11:26 AM
> To: Jürgen Jaritsch <[email protected]>
> Cc: Dennis Burgess <[email protected]>; North American Network
> Operators' Group <[email protected]>
> Subject: Re: AW: Cogent - Google - HE Fun
>
> In other words, GOOG is playing peering chicken with Cogent for IPv6. I'm
> not surprised. I suggested it during talks with GOOG roughly 10 years
> ago...not saying I had any influence...I'm pretty sure I did not. :)
>
> GOOG wants Cogent to peer. Cogent wants GOOG to pay for transit (from them
> or someone else to get to Cogent). If you're well peered / multihomed, it's
> not much of an issue. If you're a single-homed Cogent customer, you should
> complain to Cogent that they're not providing full
> IPv6 connectivity.
>
> On Wed, 9 Mar 2016, Jürgen Jaritsch wrote:
>
>> Hi,
>>
>> mail from Cogent:
>>>>>>
>> Dear Cogent Customer,
>>
>> Thank you for contacting Cogent Customer Support for information about the
>> Google IPv6 addresses you are unable to reach.
>>
>> Google uses transit providers to announce their IPv4 routes to Cogent.
>>
>> At this time however, Google has chosen not to announce their IPv6 routes to
>> Cogent through transit providers.
>>
>> We apologize for any inconvenience this may cause you and will notify you if
>> there is an update to the situation.
>> <<<<
>>
>> Mail from Google:
>>>>>>
>> 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.
>>
>> 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.
>>
>> For more information in how to peer directly with Google please visit
>> https://peering.google.com <<<<
>>
>> best regards
>>
>> Jürgen Jaritsch
>> Head of Network & Infrastructure
>>
>> ANEXIA Internetdienstleistungs GmbH
>>
>> Telefon: +43-5-0556-300
>> Telefax: +43-5-0556-500
>>
>> E-Mail: [email protected]
>> Web: http://www.anexia-it.com
>>
>>
>>
>> Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020
>> Klagenfurt
>> Geschäftsführer: Alexander Windbichler
>> Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT
>> U63216601
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: NANOG [mailto:[email protected]] Im
>> Auftrag von Dennis Burgess
>> Gesendet: Mittwoch, 09. März 2016 17:01
>> An: North American Network Operators' Group
>> Betreff: Cogent - Google - HE Fun
>>
>> I just noticed that I am NOT getting IPV6 Google prefixes though Cogent at
>> all. I was told google pulled all of their peering with Cogent? If I bring
>> up a SIT tunnel with HE, I get the prefixes but at horrible speed and
>> latency .. anyone else?
>>
>> [DennisBurgessSignature]
>> www.linktechs.net<http://www.linktechs.net/> - 314-735-0270 x103 -
>> [email protected]<mailto:[email protected]>
>>
>>
>
> ----------------------------------------------------------------------
> Jon Lewis, MCP :) | I route
> | therefore you are _________
> http://www.lewis.org/~jlewis/pgp for PGP public key_________
