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] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
- Previous message (by thread): [address-policy-wg] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Fri Jun 17 13:19:54 CEST 2016
Hi, > My suggesting is instead of removing the main problem (i.e. "lack of IPv4 > for those who need"), please bring policies on the table which help those > who really require IP, can get IP. I wish we could, but IPv4 has run out. If we went back to the previous allocation policy and would hand out addresses from the pool based on bed then that pool would be empty in a month or two, and then we would be in a worse situation than we are now because then even handing out a /22 to a new LIR would be impossible. We allowed transfers to get unused allocations back in use. If you need more than your /22 then that is where you need to go. RIPE NCC doesn't have enough addresses to give everybody what they want. Cheers, Sander
- Previous message (by thread): [address-policy-wg] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]