Search RPD Archives
[rpd] proposed policy: reservation of resources for IXPs
dogwallah at gmail.com
Thu Oct 30 19:03:35 UTC 2014
On Thu, Oct 30, 2014 at 12:59 PM, David Huberman
<David.Huberman at microsoft.com> wrote:
> In regard to the proposed policy, "Resource Reservation for Internet Exchange Points", I have two comments:
> 1) I support the policy as written.
> 2) I ask the community for input on a separate policy proposal I would like to make, which is related.
> One of the lessons we've learned over 20+ years of operating public IXes is that the worst thing that can happen to an IX is to grow so big that it outgrows its peering fabric /24. Renumbering a peering fabric is a nightmare scenario. It is preventable by having allocation policies which keep successful IXes in mind.
> I propose, therefore, text which directs AFRINIC staff to:
> - issue no less than a /24 to each IX peering fabric
> - either reserve the adjacent /24 so the /24 can grow to a /23 in the case where the IX is successful; or
> - issue the /24s sparsely (using the bisection method) to ensure the most number of /24s can grow into /23s over time.
> By carefully issuing /24s on /23 boundaries, it allows the (relatively few) IXes that will outgrow a /24 to easily move into a /23 with the same starting IP address, which makes it easy for the participants at the exchange.
One would hope that procedure would dictate this, but I see no reason
not to include it in the policy text if the authors are willing.
"A name indicates what we seek. An address indicates where it is. A
route indicates how we get there." Jon Postel
More information about the RPD