[140139] in North American Network Operators' Group
Re: Suspecious anycast prefixes
daemon@ATHENA.MIT.EDU (Bill Woodcock)
Tue May 3 06:19:14 2011
From: Bill Woodcock <woody@pch.net>
In-Reply-To: <ED2AB7F4-9B84-4DC2-87A7-92E2A6EF6D49@hopcount.ca>
Date: Tue, 3 May 2011 03:17:20 -0700
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On May 2, 2011, at 12:35 PM, Joe Abley wrote:
> It's perhaps worth noting that there is work in the IETF to recommend =
that every prefix originated as part of an anycast cloud uses a unique =
origin AS (see =
<http://tools.ietf.org/html/draft-ietf-grow-unique-origin-as-00>). I'm =
not personally convinced of the arguments in the draft, but mentioning =
it in this thread seems reasonable.
I'm also not convinced of the arguments in the draft, since it argues =
that it would be a best-practice for me to originate my address space =
from more than 8,000 different ASNs, when I currently do just fine =
advertising it from three. I'd much rather there not exist a document =
that clueless people can point at and claim is a "best common practice" =
when it's neither best nor common.
-Bill
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
iEYEARECAAYFAk2/1jEACgkQGvQy4xTRsBH89wCfSD9h/1v/jNtKwk18XP4In6cE
Z3wAniPsu6QvtMfHLlz/Jn7tGUwRzQvX
=3DiuXT
-----END PGP SIGNATURE-----
