Route Server Filters at IXPs and 4-byte ASNs

Jakob Heitz jakob.heitz at
Sat Jan 25 19:26:35 UTC 2014

I would support that.
How would you modify it?

To me, that draft looks hugely complicated, like everything you
could possibly think of was thrown in. I would support a simplified
version (and be able to code it without bugs) if it contained just useful stuff.

Jakob Heitz.

Date: Sat, 25 Jan 2014 18:37:42 +0000
From: Nick Hilliard <nick at>
To: Sebastian Spies <s+Mailinglisten.nanog at>, nanog at
Subject: Re: Route Server Filters at IXPs and 4-byte ASNs
Message-ID: <52E40476.20200 at>
Content-Type: text/plain; charset=ISO-8859-1

On 25/01/2014 15:48, Sebastian Spies wrote:
> To make things worse: even if the IXPs ASN is 2-byte, I would assume,
> that RS implementors chose to interpret extended community strings as
> always being in the format 4-byte:2-byte (see RFC5668).

some ixp operators (e.g. me) are rather enthusiastic about the idea of a
modified form of draft-raszuk-wide-bgp-communities getting more traction.
This would solve this particular problem and many others.


More information about the NANOG mailing list