nanog mailing list archives
Re: Cogent - Google - HE Fun
From: Fredy Kuenzler <kuenzler () init7 net>
Date: Thu, 10 Mar 2016 23:42:05 +0100
This would work for those which are using IPv6 transit from Cogent. For anyone else which is using IPv6 transit from Hurricane Electric and some other suppliers such as L3 or NTT: to set the community 'do not announce to Cogent' only on every other transit but HE would help to isolate Cogent without much collateral damage. It would support Google/HE's position. And maybe help to bring back Cogent onto a cooperative track, after all. -- Fredy Kuenzler Init7 (Switzerland) Ltd. St.-Georgen-Strasse 70 CH-8400 Winterthur Switzerland http://www.init7.net/
Am 10.03.2016 um 23:19 schrieb Matthew D. Hardeman <mhardeman () ipifony com>: I have contemplated whether such mechanisms matter to Cogent, etc. I’m inclined to think that if Google is willing to pull the routes and they still don’t blink, then certainly us smaller shops aren’t going to impact them… However… If enough prefixes disappear from the _apparent_ Cogent table as viewed by outsiders, this may ultimately impact their sales of new interconnection…. For those of us multihomed with Cogent and other transit providers on IPv6 there is a less drastic way to impact the perceived value of Cogent’s IPv6 routing table to outsiders and especially to Cogent’s peers — and one that still doesn’t negatively impact the single-home customers of Cogent: "set community 174:3000" on your IPv6 advertisement to Cogent. This will constrain the advertisement to Cogent and Cogent’s customers only. For good measure, prepend your own AS to this advertisement at least a couple of times, potentially discouraging even Cogent customers who see the route from using it if they have other transit. It will prevent the path via Cogent being selected by Cogent IPv6 peers versus your other transit providers.On Mar 10, 2016, at 3:47 PM, Fredy Kuenzler <kuenzler () init7 net> wrote: Am 10.03.2016 um 22:25 schrieb Damien Burke <damien () supremebytes com>:Anyone who is multihomed with cogent ipv6 in their mix should shutdown their IPv6 bgp session. Let’s see if we can make their graph freefall.Alternative: set community [do not announce to Cogent] *SCNR*
Current thread:
- Re: AW: Cogent - Google - HE Fun, (continued)
- Re: AW: Cogent - Google - HE Fun William Herrin (Mar 10)
- RE: AW: Cogent - Google - HE Fun Damien Burke (Mar 10)
- Re: AW: Cogent - Google - HE Fun Fredy Kuenzler (Mar 10)
- Re: Cogent - Google - HE Fun Matthew D. Hardeman (Mar 10)
- Re: Cogent - Google - HE Fun Mark Andrews (Mar 10)
- Re: Cogent - Google - HE Fun Matthew D. Hardeman (Mar 10)
- RE: Cogent - Google - HE Fun Robert Jacobs (Mar 11)
- Re: Cogent - Google - HE Fun Christopher Morrow (Mar 11)
- Re: Cogent - Google - HE Fun Jay Hennigan (Mar 18)
- Re: Cogent - Google - HE Fun Jay R. Ashworth (Mar 11)
- Re: Cogent - Google - HE Fun Fredy Kuenzler (Mar 10)
- Re: Cogent - Google - HE Fun Matthew D. Hardeman (Mar 10)
- Re: AW: Cogent - Google - HE Fun Randy Bush (Mar 11)
- Re: AW: Cogent - Google - HE Fun Jon Lewis (Mar 11)
- Re: AW: Cogent - Google - HE Fun William Herrin (Mar 11)
- Re: Cogent - Google - HE Fun Owen DeLong (Mar 11)
- Re: AW: Cogent - Google - HE Fun Dave Bell (Mar 11)
- Re: AW: Cogent - Google - HE Fun Mikael Abrahamsson (Mar 11)
- Re: Cogent - Google - HE Fun Owen DeLong (Mar 11)
- Message not available
- Re: AW: Cogent - Google - HE Fun Mark Tinka (Mar 10)
- Message not available
- Re: Cogent - Google - HE Fun Mark Tinka (Mar 10)