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] The final /8 policy proposals, part 3.2
- Previous message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
- Next message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Per Heldal
heldal at eml.cc
Tue Sep 15 19:26:17 CEST 2009
On Tue, 2009-09-15 at 11:58 +0200, Sander Steffann wrote: > Which is why I proposed to reserve space for PA initial allocations :) I > could be wrong here ofcourse... Isn't it a bit of a problem that it is rather pointless to talk about initial v4 PA allocations at the point in the end-game when it is no longer possible to meet the requested block-size? In the past we've dismissed suggestions to link v4 allocations to subjective requirements such as "must prove intention to deploy v6". During the runout the situation changes. The only real option for a new PA network operator will be to use v6 (unless there are address-resources available outside the RIR-system). Thus tying micro v4 allocations to v6 PA-allocations makes perfect sense if you want to keep the PI crowd out. //per
- Previous message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
- Next message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]