This confusion has been haunting the final /8 policy
from day one - it was never about what to do with specifically
185/8, but what to do with all future allocations from the moment
we needed to start allocating out of it. The policy text itself
was never limited to a single /8, nor was that limitation any part
of the discussion.
I looked up the policy proposal at
https://www.ripe.net/participate/policies/proposals/2010-02
"
This proposal describes how the RIPE NCC
should distribute IPv4 address space from the final /8 address
block it receives from the IANA."
Reading the rest of the proposal I fully understand the confusion
and find it hard to read your interpretation into the proposal.
The updated policy after this proposal can be found in RIPE 509
https://www.ripe.net/publications/docs/ripe-509#----use-of-last----for-pa-allocations
* The following
policies come into effect as soon as RIPE NCC is required to make
allocations from the final /8 it receives from the IANA.
It does not discuss the event where RIPE NCC gets more address
space and could allocate from - which would strictly speaking not
be allocation from the last /8
Tracing the policy text trough the versions - This text was first
removed between
* RIPE 599 published on 20 December 2013
https://www.ripe.net/publications/docs/ripe-599#Use-last-for-PA-Allocations
and
* RIPE 604 - published on 4 Feb 2014:
https://www.ripe.net/publications/docs/ripe-604
Where the text was changed to:
- The size of the
allocation made will be exactly one /22.
- The sum of all
allocations made to a single LIR by the RIPE NCC after the 14th
of September 2012 is limited to a maximum of 1024 IPv4 addresses
(a single /22 or the equivalent thereof).
and no reference to the last /8.
So I can easily understand the confusion.
--
Hans Petter Holen
Mobile +47 45 06 60 54 | hph@oslo.net | http://hph.oslo.net