[193912] in North American Network Operators' Group
Re: google ipv6 routes via cogent
daemon@ATHENA.MIT.EDU (Faisal Imtiaz)
Thu Mar 2 10:18:22 2017
X-Original-To: nanog@nanog.org
Date: Thu, 2 Mar 2017 14:23:30 +0000 (GMT)
From: Faisal Imtiaz <faisal@snappytelecom.net>
To: Aaron <aaron1@gvtc.com>
In-Reply-To: <001801d28f7e$d063ac10$712b0430$@gvtc.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Just Google for it.. this is probably one of the oldest running Klan dispute in the industry..
http://www.datacenterknowledge.com/archives/2009/10/22/peering-disputes-migrate-to-ipv6/
Regards.
Faisal Imtiaz
Snappy Internet & Telecom
7266 SW 48 Street
Miami, FL 33155
Tel: 305 663 5518 x 232
Help-desk: (305)663-5518 Option 2 or Email: Support@Snappytelecom.net
----- Original Message -----
> From: "Aaron" <aaron1@gvtc.com>
> To: "nanog list" <nanog@nanog.org>
> Sent: Saturday, February 25, 2017 10:49:56 AM
> Subject: google ipv6 routes via cogent
> Hi, I'm new to the nanog list, hope this isn't out of scope for what is
> usually discussed here.
>
>
>
> Cogent is telling me that I can't route through cogent to get to google ipv6
> routes (particularly the well known dns addresses 2001:4860:4860::88xx)
> because google decided not to advertise those route to one of their mutual
> peers.
>
>
>
> Anyone know anything about this ? .and why it happened and when it will be
> resolved ?
>
>
>
> -Aaron
