nanog mailing list archives
Re: Route Server Filters at IXPs and 4-byte ASNs
From: Jared Mauch <jared () puck nether net>
Date: Wed, 5 Feb 2014 09:02:52 -0500
On Feb 5, 2014, at 8:52 AM, Jeffrey Haas <jhaas () pfrc org> wrote:
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.I think that's the first clear articulation I've read about why some people want wide comms vs. a simple replacement for existing regular communities as extended communities. Thanks.
I suspect the operator confusion is that’s how they’ve been using 16-bit ASNs all along, so how did the IETF end up with something different. http://www.onesc.net/communities/ is a fairly comprehensive list of how they are used today. - jared
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)