[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Route Server Filters at IXPs and 4-byte ASNs

Subject: Route Server Filters at IXPs and 4-byte ASNs
From: effulgence at gmail.com (Aris Lambrianidis)
Date: Thu, 6 Feb 2014 17:45:46 +0100
In-reply-to: <20140205135203.GA594@pfrc>
References: <[email protected]> <[email protected]> <CAAYzVeGSaQW_AfENn5Bs0im1rG00e8FZvxFLkmb0gqKJaij3jQ@mail.gmail.com> <[email protected]> <CAAYzVeE2K6WUh5X+gYAR6381v-wWPu2On_6GXGJBuZMdcoq0Ng@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]> <20140205100631.479da729@fizzix>

Food for thought:

- ASNs can be reused at different locations by IXPs, barring perhaps
certain business or administrative reasons. Ask Equinix.

- For IXPs that already have 16-bit ASNs for route servers, this saves additional 
allocations from RIRs and mitigates concerns for the IXP getting potentially a 32-bit ASN, 
thus having trouble with BGP communities as described. Having a single ASN
may raise other issues but it is an option. 

- I believe it would help if RIRs reserved 16-bit ASNs
in addition to IPv4 micro allocations for IXPs, until a formal
solution can be finally found about the 32-bit ASN BGP communities issue. 

Aris Lambrianidis

References:
- Route Server Filters at IXPs and 4-byte ASNs
  - From: jhaas at pfrc.org (Jeffrey Haas)
- Route Server Filters at IXPs and 4-byte ASNs
  - From: martin.pels at ams-ix.net (Martin Pels)
- Route Server Filters at IXPs and 4-byte ASNs
  - From: jhaas at pfrc.org (Jeffrey Haas)

Prev by Date: carrier comparison
Next by Date: SIP on FTTH systems
Previous by thread: Route Server Filters at IXPs and 4-byte ASNs
Next by thread: Route Server Filters at IXPs and 4-byte ASNs
Index(es):
- Date
- Thread