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] new policy idea for PA allocations
- Previous message (by thread): [address-policy-wg] new policy idea for PA allocations
- Next message (by thread): [address-policy-wg] new policy idea for PA allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Conrad
drc at virtualized.org
Thu Aug 7 18:27:40 CEST 2008
Remco, >>>> Could someone submit another request immediately afterwards though, >>>> since current policies are based on need? >>> if you again qualify for another allocation you can come back for >>> one. If >>> that's immediate, it's immediate. >> What's the point? If I qualify for a /15 and I want a /15 but all the >> RIR has available is a bunch of /18s, I'll take those /18s. > The point is quite simple - why bother being strict in allocating > small > blocks when in the end you're going to hand them over to a single > request anyway. I don't want anyone filing a request that cleans out > the > cupboard in one go. So, you're proposing the addition of increased administrative overhead (in the form of requiring multiple applications for address space to obtain the amount of address space originally requested) as a mechanism to reduce the demand on the fragmented pool? Thanks, -drc
- Previous message (by thread): [address-policy-wg] new policy idea for PA allocations
- Next message (by thread): [address-policy-wg] new policy idea for PA allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]