[168810] in North American Network Operators' Group
Re: Route Server Filters at IXPs and 4-byte ASNs
daemon@ATHENA.MIT.EDU (Jeffrey Haas)
Tue Feb 4 22:53:56 2014
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <52E40476.20200@foobar.org>
Date: Tue, 4 Feb 2014 22:53:40 -0500
To: Nick Hilliard <nick@foobar.org>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Sent from my iPad
> On Jan 25, 2014, at 1:37 PM, Nick Hilliard <nick@foobar.org> wrote:
>
>> 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.
>
Wide communities is the wrong tool here. You want this:
http://tools.ietf.org/html/draft-ietf-idr-as4octet-extcomm-generic-subtype-06
-- Jeff
> Nick
>
