This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 2019-05 New Policy Proposal (Revised IPv4 assignment policy for IXPs)
- Previous message (by thread): [address-policy-wg] 2019-05 New Policy Proposal (Revised IPv4 assignment policy for IXPs)
- Next message (by thread): [address-policy-wg] 2019-05 New Policy Proposal (Revised IPv4 assignment policy for IXPs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Radu-Adrian FEURDEAN
ripe-wgs at radu-adrian.feurdean.net
Wed May 29 16:13:15 CEST 2019
On Wed, May 29, 2019, at 15:11, Denis Fondras wrote: > Just because of "It no longer provides for IXPs that need more than a > /23 of IPv4 > space" I am against this proposal. Hi, The alternative is that in just a few years it will no longer provide IXPs with any space. Right now, according to peeringdb, in RIPE region there are 5 IXPs holding a /21 and 5 (or 4, depending on how you consider the 2 LINX LANs) that hold a /22, and 14 (12, depending on how you count multi-LAN IXPs) that hold a /23. Let's hear their point of view, since building an IXP so big takes a lot of time (took almost 9 years for FranceIX to get there). Those being said, I'm in favour of the proposal. Just one reserve on wording of the assignment of "dust" (less than /24): if a request (for smaller than /24) is being made before the reserved pool exhaustion, will it be taken from he reserved pool or from the "dust" ? -- Radu-Adrian FEURDEAN
- Previous message (by thread): [address-policy-wg] 2019-05 New Policy Proposal (Revised IPv4 assignment policy for IXPs)
- Next message (by thread): [address-policy-wg] 2019-05 New Policy Proposal (Revised IPv4 assignment policy for IXPs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]