Hello Sander, Would it be an option to have something written in the policy that means the following? The reserved /10 (or other range) from the last /8 RIPE NCC receives from IANA is to be used for PA allocations. Whenever there are no other addresses available to use for PI allocations the /10 (or part of that)(that effective are the last IPv4 addresses RIPE NCC can provide to the RIPE community at that time) can also be used for other allocations, like PI. Something in the policy mentioning it is a good thing if you ask me, I mention it because making policy takes a while. So I like to mention it directly, if possible, so the RIPE NCC can continue to provide IPv4 addresses as long as they don't run out. Regards, Mark Scholten -----Original Message----- From: address-policy-wg-admin@ripe.net [mailto:address-policy-wg-admin@ripe.net] On Behalf Of Sander Steffann Sent: dinsdag 15 september 2009 9:49 To: Leo Vegoda Cc: Michiel Klaver; address-policy-wg@ripe.net Subject: Re: [address-policy-wg] The final /8 policy proposals, part 3.2 Hi Leo,
We are talking about PA prefixes here, and this pool is only meant for initial allocations (PA), not PI.
I know.
Ok :)
True. There might be organizations that become an LIR to get that initial /24 allocation.
Has any work been done to identify what proportion of those organizations that are normally satisfied with PI or PA assignments are likely to go for a /24 PA "allocation" if that's all there is? I think some data identifying likely outcomes would be useful when making deciding on the prefix length to reserve.
Hmmm. This is difficult. I don't think any of us has a crystal ball of that quality. My guess is that the only thing we can do is to reserve more addresses (a /10?) now. We can always decide to 'release' them later if it turns out that we reserved too many. Thanks, Sander