nanog mailing list archives
Re: Cogent - Google - HE Fun
From: Dennis Bohn <bohn () adelphi edu>
Date: Wed, 16 Mar 2016 09:56:59 -0400
So if someone (say an eyeball network) was putting out a RFQ for a gig say of upstream cxn and wanted to spec full reachability to the full V6 net, what would the wording for that spec look like? Would that get $provider's attention? On Mar 15, 2016 12:50 AM, "Todd Crane" <todd.crane () n5tech com> wrote:
This is only tangentially related but it looks like HE has surpassedCogent on IPv4 adjacencies. That said the source probably suffers from a selection bias at the very least.http://bgp.he.net/report/peersHit reply by mistake instead of reply all.Todd CraneOn Mar 14, 2016, at 8:40 PM, Matthew D. Hardeman <mhardeman () ipifony com>wrote:It looks like Google is experimenting with a change in course on thisissue.Here’s a look at the IPv6 routing table tonight on my router borderingCogent.*>i 2607:f8b0:4013::/48 2620:121:a000:f0::2(fe80::618:d6ff:fef1:c540) 0 150 015169 i* 2001:550:2:22::1d:1(fe80::12f3:11ff:fe29:2c24) 0 90 0174 6461 15169 i*>i 2607:f8b0:4014::/48 2620:121:a000:f0::2(fe80::618:d6ff:fef1:c540) 0 110 06939 6461 15169 i* 2001:550:2:22::1d:1(fe80::12f3:11ff:fe29:2c24) 0 90 0174 6461 15169 i*>i 2607:f8b0:4016::/48 2620:121:a000:f0::2(fe80::618:d6ff:fef1:c540) 0 150 015169 i* 2001:550:2:22::1d:1(fe80::12f3:11ff:fe29:2c24) 0 90 0174 6461 15169 iThis is only 3 IPv6 prefixes (out of 47 prefixes seen in my IPv6routing table). Two of these prefixes I see via direct peering with Google and, alternatively, via Cogent through Zayo transit. One of these prefixes doesn’t advertise in Google’s direct peering session (at least not in mine, but HE picks it up via Zayo and Cogent picks it up via Zayo).All of these are /48 subnets of their greater 2620:f8b0::/32 prefix,which does show up in both their direct session and in HE via Zayo.On Mar 13, 2016, at 9:31 AM, Dennis Burgess <dmburgess () linktechs net>wrote:In the end, google has made a choice. I think these kinds of choiceswill delay IPv6 adoption.-----Original Message----- From: Damien Burke [mailto:damien () supremebytes com] Sent: Friday, March 11, 2016 2:51 PM To: Mark Tinka <mark.tinka () seacom mu>; Owen DeLong <owen () delong com>;Dennis Burgess <dmburgess () linktechs net>Cc: North American Network Operators' Group <nanog () nanog org> Subject: RE: Cogent - Google - HE Fun Just received an updated statement from cogent support: "We appreciate your concerns. This is a known issue that originateswith Google as it is up to their discretion as to how they announce routes to us v4 or v6.Once again, apologies for any inconvenience." And: "The SLA does not cover route transit beyond our network. We cannotroute to IPs that are not announced to us by the IP owner, directly or through a network peer."
Current thread:
- Re: Cogent - Google - HE Fun, (continued)
- Re: Cogent - Google - HE Fun James Milko (Mar 14)
- Re: Cogent - Google - HE Fun William Herrin (Mar 14)
- RE: Cogent - Google - HE Fun Matthew Huff (Mar 14)
- Re: Cogent - Google - HE Fun Matthew D. Hardeman (Mar 14)
- RE: Cogent - Google - HE Fun Matthew Huff (Mar 14)
- Re: Cogent - Google - HE Fun Matthew D. Hardeman (Mar 14)
- RE: Cogent - Google - HE Fun Matthew Huff (Mar 14)
- Re: Cogent - Google - HE Fun Baldur Norddahl (Mar 13)
- Re: Cogent - Google - HE Fun Matthew D. Hardeman (Mar 14)
- Message not available
- Re: Cogent - Google - HE Fun Todd Crane (Mar 14)
- Re: Cogent - Google - HE Fun Dennis Bohn (Mar 16)
- Re: Cogent - Google - HE Fun Christopher Morrow (Mar 16)
- Re: Cogent - Google - HE Fun Dennis Bohn (Mar 16)
- Re: Cogent - Google - HE Fun Owen DeLong (Mar 16)
- Re: Cogent - Google - HE Fun Christopher Morrow (Mar 16)
- Re: Cogent - Google - HE Fun Mark Tinka (Mar 16)
- Re: Cogent - Google - HE Fun Owen DeLong (Mar 16)
- Re: Cogent - Google - HE Fun Mark Tinka (Mar 16)
- Re: Cogent - Google - HE Fun Owen DeLong (Mar 16)
- Re: Cogent - Google - HE Fun Mark Tinka (Mar 16)
- Re: Cogent - Google - HE Fun Baldur Norddahl (Mar 16)