[137760] in North American Network Operators' Group
Re: Internet Exchange Point(IXP) questions
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Fri Feb 18 16:45:05 2011
Date: Fri, 18 Feb 2011 13:44:56 -0800
From: Leo Bicknell <bicknell@ufp.org>
To: Christopher Morrow <morrowc.lists@gmail.com>
Mail-Followup-To: Christopher Morrow <morrowc.lists@gmail.com>,
"Michael K. Smith - Adhost" <mksmith@adhost.com>,
"nanog@nanog.org" <nanog@nanog.org>,
"Yaoqing(Joey) Liu" <joey.liuyq@gmail.com>
In-Reply-To: <AANLkTinY8d9UVQV8aeh9NzbBpKZviekXHbAz1hDqMm7V@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>,
"Yaoqing\(Joey\) Liu" <joey.liuyq@gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--T4sUOijqQbZv57TR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In a message written on Fri, Feb 18, 2011 at 04:36:28PM -0500, Christopher =
Morrow wrote:
> leaking the IX prefix to customers, to me, seems like a recipe for
> much wider/unintended leakage :(
Oh, it is. I remember when MAE-EAST was injected by at least 50 people
into the DFZ because back then people weren't careful enough to just
send such things to customers.
AMS-IX (and others) have the better solution. They have AS1200,
announce the exchange LAN from AS1200 (195.69.144.0/22). They will
peer with you if you are at the exchange, see
http://www.ams-ix.net/as1200-peering/. I believe, but can't find
a reference really quick that they get transit for it from a couple
of providers so those that don't peer still have the route.
I mean really, you have a block. If your IXP matters it's already
taking up space in all of the largest ISP's tables anyway, so there's no
"saving a route argument". Get an ASN, which since your multi-homed is
trivial, announce the block from there and peer with your exchange
participants. Everyone is happy, the route is consistent, and life is
good.
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
--T4sUOijqQbZv57TR
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
iQIVAwUBTV7oWLN3O8aJIdTMAQKxaRAAozXMLB4tMEu/qYHpXEog2pGuOnzjYDYF
agvbNGdF4djQVSGcTK/Na3YPpPAt81Q11u6sH7NRx5OpkOW9SQLuzUnWie7owZji
7VRG37w/fx74XXn625LnpBn7cjSXn4A+qtQj5++1S64u9uHdauKUjER4P/JhIUt2
EOc5ysBkAluL/JVQIA1k7tQXBKM26YIX3mVHJMgQr2oj7FgE2dr+rMW7pBUeE8py
w3otG4Z39SuWCe9BFSvnXEnhOBuBi+45+fIvMmMv+DIPpe/1Vx8nj0fdoWj+NlAo
9h1EWZ1Vo2gEgLaZR5eLyToo4tTVa0PLIn4eVpSkfH5iF/IPM+WXwejjGc8Hwdpq
iXoIlaCZdUmfcVSfCKr5FXyaFajAEPQvwlyL9I8F3S2Kedh9KNPiqDeygolVwLZt
8lew/T4ECw1RzuVlVVrG+RstetCfa+RUwsuKI8qb8pSwHskNgGJ/I7Ky2ua0D9eO
XWA/MC8Ka7uOGZNjg2+cxjmfA6x9W+tQ4w61l2FEid9BnAVm+JCzfxVtSwUjGGWU
bussuggUX1h9xMk412QFPfIyV3V6t5SWK7Sx9n+EzvWR75sIGtXZw+2WdGs+btVI
HRdOyKOhemIuWME6pN23DqScL/dsKTevCdGbxI0fdLlydKrsnMMK7e8Qb3mZ0mZJ
uORJ5sWI2lQ=
=HsB+
-----END PGP SIGNATURE-----
--T4sUOijqQbZv57TR--
