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/address-policy-wg@ripe.net/
[address-policy-wg] "last /8" allocation size - community feedback request before engaging PDP
- Previous message (by thread): [address-policy-wg] "last /8" allocation size - community feedback request before engaging PDP
- Next message (by thread): [address-policy-wg] "last /8" allocation size - community feedback request before engaging PDP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carsten Schiefner
ripe-wgs.cs at schiefner.de
Mon Sep 14 15:32:47 CEST 2015
Richard, all - On 14.09.2015 10:14, Richard Hartmann wrote: > On Mon, Sep 14, 2015 at 9:17 AM, Radu-Adrian FEURDEAN > <ripe-wgs at radu-adrian.feurdean.net> wrote: > >> 1. Separate pools or single pool >> a. have a "last /8 pool" which is 185.0.0.0/8 (strictly one /22 per >> LIR) and a "recovered space pool" containing all space received from >> IANA as "recovered and redistributed space" (for extra allocations) - >> APNIC-like separation of pools >> b. treat all addressing space available for allocation as a single >> pool > > The only reason I can see is to keep the unused, continuous blocks in > 185.0.0.0/8 if we ever need them for something else and thus try to > get rid of the recovered pool first. how about combining this by treating all addresses equal in a single pool, but advising the NCC to hand out recovered addresses first unless there are specific, yet-to-be-defined reasons that they rather need to come from the 185/8 heap? Cheers, -C.
- Previous message (by thread): [address-policy-wg] "last /8" allocation size - community feedback request before engaging PDP
- Next message (by thread): [address-policy-wg] "last /8" allocation size - community feedback request before engaging PDP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]