Re: Route Server Filters at IXPs and 4-byte ASNs

[Martin Pels <martin.pels () ams-ix net>]

Jeffrey,

On Tue, 4 Feb 2014 22:53:40 -0500
Jeffrey Haas <jhaas () pfrc org> wrote:

> 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

This draft does not cater for the use case of describing a 32-bit ASN peering
with a 32-bit route server, which would require a 4-byte Global Administrator
as well as a 4-byte Local Administrator sub-field.

Kind regards,
Martin