Re: [sig-policy] prop-085: Eligibility for critical infrastructure assig
I'm a bit confused by the whole discussion (I've been away from the list
for a few days, so just catching up).
The final /8 policy comes into force once APNIC has no other IPv4
address space left.
My understanding is that the final /8 policy applies to the final /8 (we
left it to the Secretariat staff to make the operational decision
whether this is an identified /8 block or an equivalent). It supercedes
all other policies for IPv4 address distribution.
And yes it does mean that there is no PI policy and no CI policy when we
move into the final /8 phase. This was discussed at length during the
process discussing the final /8 policy.
Now, what policy reserves 188.8.131.52/16 for CI? APNIC has chosen to use
184.108.40.206/16 for CI (for their and Internet operational reasons), but
there is no policy mandating that this address block cannot be used for
So this is all very simple in my view - once APNIC has no other IPv4
address space left to distribute, the final /8 policy comes into force.
Terence Zhang YH said the following on 21/08/10 22:55 :
> Dear all,
>>From the previous discussion, we understand there will be 2
> possibilities when we enter the final /8:
> Case 1:
> If the Secretariat reserve the final /8 from IANA for use in the final /8 policy,
> at some point, any unused space reserved for special use (IX, CI, etc)
> may be released for general allocations and assignments, after they are all
> allocated/assigned, we enter the final /8 phase.
> Case 2:
> If the Secretariat doesn't reserve the final /8 from IANA for use in the final /8 policy,
> we enter the final /8 phase when the total of remaining address space is less than a /8,
> in this case, the remaining space in the reserved block 220.127.116.11/16 become
> part of the final /8 space, and the final /8 policy applies to it.
> In either case, critical infrastructure assignments are no longer possible because
> all previous allocation and assignment policies (including CI assignments)
> become void when we enter the final /8 phase.
>>From the previous discussions, most people tend to feel comfortable with
> 'Allowing Critical Infrastructure assignments from the current reserved block
> until it runs out'
> So, in Case 1, in order to continue to provide CI assignments, we may propose
> 'Not to release the CI block for general purpose, allow Critical Infrastructure
> assignments from the current reserved block until it runs out'
> But that seems impractical as a policy statement, theoretically speaking, it might
> produce a deadlock as we have a /8 plus some thing and cannot trigger
> the final /8 phase.
> So, in Case 1, I will suggest:
> -Continue to allow CI assignments according to 11.3, "Critical infrastructure"
> -Let the Secretariat decide the best way to accommodate new CI assignment when we
> enter the final /8 ( We may state this explicitly, but I feel it's unneccessary, any suggestion? )
> In Case 2, the remaining space in the reserved CI block become part of
> the final /8 space, in order to continue to use it to provide CI assignments,
> we have to continue to allow CI assignments according to 11.3, "Critical infrastructure"
> So, looks like the current text of the proposal already address the above 2 situations.
> Given the current CI statistics, and consider there are 16K /22s in the final /8,
> allowing CI assignments will NOT have significant impact to the final /8 allocations.
> Any one has any suggestions?
> Thanks & Regards
> Terence Zhang