nanog mailing list archives
Re: Route Server Filters at IXPs and 4-byte ASNs
From: Jeffrey Haas <jhaas () pfrc org>
Date: Tue, 4 Feb 2014 22:53:40 -0500
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
Current thread:
- Re: Route Server Filters at IXPs and 4-byte ASNs Jeffrey Haas (Feb 04)
- Re: Route Server Filters at IXPs and 4-byte ASNs Martin Pels (Feb 05)
- Re: Route Server Filters at IXPs and 4-byte ASNs Jeffrey Haas (Feb 05)
- Re: Route Server Filters at IXPs and 4-byte ASNs Jared Mauch (Feb 05)
- Re: Route Server Filters at IXPs and 4-byte ASNs Jeffrey Haas (Feb 05)
- Re: Route Server Filters at IXPs and 4-byte ASNs Jared Mauch (Feb 05)
- Re: Route Server Filters at IXPs and 4-byte ASNs Jeffrey Haas (Feb 05)
- Route Server Filters at IXPs and 4-byte ASNs Aris Lambrianidis (Feb 06)
- Re: Route Server Filters at IXPs and 4-byte ASNs Martin Pels (Feb 05)
- <Possible follow-ups>
- Re: Route Server Filters at IXPs and 4-byte ASNs Jeffrey Haas (Feb 04)
- Re: Route Server Filters at IXPs and 4-byte ASNs Randy Bush (Feb 05)