[140261] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Suspecious anycast prefixes

daemon@ATHENA.MIT.EDU (Randy Bush)
Sat May 7 01:33:26 2011

Date: Sat, 07 May 2011 07:33:36 +0200
From: Randy Bush <randy@psg.com>
To: Danny McPherson <danny@tcb.net>
In-Reply-To: <3C9D1E48-D9A2-44D4-B783-D4F4C26A9CD1@tcb.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

>>> 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
> 'A', not 'the', for the reasons conveyed in the draft (e.g., control 
> plane discriminator, RPKI foundations, etc..).

danny,

could you explain why this has anything to do with the rpki and origin
validation?

randy


home help back first fref pref prev next nref lref last post