nanog mailing list archives

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

From: Nick Hilliard <nick () foobar org>
Date: Sat, 25 Jan 2014 18:37:42 +0000

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.

Nick

Current thread:

Route Server Filters at IXPs and 4-byte ASNs Sebastian Spies (Jan 25)
- Re: Route Server Filters at IXPs and 4-byte ASNs Rubens Kuhl (Jan 25)
- Re: Route Server Filters at IXPs and 4-byte ASNs Job Snijders (Jan 25)
  - Re: Route Server Filters at IXPs and 4-byte ASNs Bryan Socha (Jan 25)
    - Re: Route Server Filters at IXPs and 4-byte ASNs Job Snijders (Jan 25)
    - Re: Route Server Filters at IXPs and 4-byte ASNs Bryan Socha (Jan 25)
    - Re: Route Server Filters at IXPs and 4-byte ASNs Sebastian Spies (Jan 25)
    - Re: Route Server Filters at IXPs and 4-byte ASNs Nick Hilliard (Jan 25)
- Re: Route Server Filters at IXPs and 4-byte ASNs Valdis . Kletnieks (Jan 26)
- <Possible follow-ups>
- RE: Route Server Filters at IXPs and 4-byte ASNs Jakob Heitz (Jan 25)
  - Re: Route Server Filters at IXPs and 4-byte ASNs Randy Bush (Jan 25)
    - Re: Route Server Filters at IXPs and 4-byte ASNs Nick Hilliard (Jan 25)