[188189] in North American Network Operators' Group
Re: Cogent - Google - HE Fun
daemon@ATHENA.MIT.EDU (Fredy Kuenzler)
Thu Mar 10 17:42:16 2016
X-Original-To: nanog@nanog.org
From: Fredy Kuenzler <kuenzler@init7.net>
Date: Thu, 10 Mar 2016 23:42:05 +0100
In-Reply-To: <96E55947-ABE3-4596-9D67-929C6CE18876@ipifony.com>
To: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
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 wit=
hout much collateral damage. It would support Google/HE's position. And mayb=
e 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>=
:
>=20
> I have contemplated whether such mechanisms matter to Cogent, etc.
>=20
> I=E2=80=99m inclined to think that if Google is willing to pull the routes=
and they still don=E2=80=99t blink, then certainly us smaller shops aren=E2=
=80=99t going to impact them=E2=80=A6
>=20
> However=E2=80=A6 If enough prefixes disappear from the _apparent_ Cogent t=
able as viewed by outsiders, this may ultimately impact their sales of new i=
nterconnection=E2=80=A6.
>=20
> 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=E2=80=99=
s IPv6 routing table to outsiders and especially to Cogent=E2=80=99s peers =E2=
=80=94 and one that still doesn=E2=80=99t negatively impact the single-home c=
ustomers of Cogent:
>=20
> "set community 174:3000" on your IPv6 advertisement to Cogent. This will c=
onstrain the advertisement to Cogent and Cogent=E2=80=99s customers only. Fo=
r good measure, prepend your own AS to this advertisement at least a couple o=
f times, potentially discouraging even Cogent customers who see the route fr=
om 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.
>=20
>=20
>> On Mar 10, 2016, at 3:47 PM, Fredy Kuenzler <kuenzler@init7.net> wrote:
>>=20
>> 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 t=
heir IPv6 bgp session. Let=E2=80=99s see if we can make their graph freefall=
.
>>=20
>>=20
>> Alternative:
>>=20
>> set community [do not announce to Cogent]
>>=20
>> *SCNR*
>=20
