[routing-wg] Bogon ASN Filter Policy

Hi Colin,

On Mon, Jun 13, 2016 at 04:19:38PM +0200, Colin Petrie wrote:
> On 02/06/16 21:43, Job Snijders wrote:
> > After the Bogon ASN filter policy has been deployed, AS 2914 will
> > not accept route announcements from any eBGP neighbor which contains
> > a Bogon ASN anywhere in the AS_PATH or its atomic aggregate
> > attribute.
> 
> However, I do want to mention that filtering route announcements with
> Bogon ASNs in the AGGREGATOR attribute will result in dropping the
> current RIS Routing Beacon announcements.

This is an astute observation! Thanks for spotting that :)

> If there is a desire to block the propagation of routes with these
> attributes, we will need to investigate alternatives to the current
> beacon encoding.
> 
> We are, of course, happy to consider any community input into how this
> should be handled.

The aggregator IP address can still be used to encode information. I
recommend using AS 3333 as the aggregator AS. Furthermore one could use
32-bit BGP communities (and possibly extended BGP communities too for a
level of information redundancy) to encode additional meta information. 

Kind regards,

Job