Search RPD Archives
[rpd] Fwd: new policy proposal "Soft Landing - SD"
Andrew.Alston at liquidtelecom.com
Sun Apr 2 17:49:54 UTC 2017
Sorry but that is *NOT* what was posted to the list – that is not a clarification – it is a fundamental change in what was written, the policy in effect contradicts itself in its summary and in the actual proposal:
* Disallowing allocation to organisations who have been allocated up to the maximum prefixes during each phase.
That is the in summary – that however does not form part of the actual policy when evaluated – summaries are just that, it is the actual policy against which assignments are meant to be done
The policy it says reads:
Exhaustion Phase 1:
During this phase, allocation/assignment of address space will continue as in the Current phase (/24 for a EU and /22 for a LIR) but the maximum will change from /10 to /17.
There is no maximum in the current phase on the number of times people can apply or how much TOTAL space they can get. Under this policy, the ability to still return for as many /17s as you like, still exists by my reading of it.
Then, to add to this:
If you look at the number of members who hold /17 or greater – considering you have allocated 128 /17s in Phase 1, how long does you think with a restriction on the ability to get more than that in Phase 1 that is going to last us? My prediction – years and years and years – while the remaining space goes to waste and becomes less and less useable as the world moves on.
Secondly – This policy does nothing to address the fact that large amounts of space is still held for future unforeseen despite the fact that v4 is largely deprecated from developmental aspects of the Internet and we are just wasting space doing this. Yet another reason I oppose this policy.
In the spirit of finding compromise and consensus though –
a.) If the issue of space locked up for future unforeseen is dealt with and that text is removed in entirety – as well as any other lockdowns for specific use case *AND*
b.) There is a transfer policy passed that *AT MINIMUM* supports inbound transfers – BEFORE this policy is heard *AND*
c.) The maximum in phase 1 is raised to a proper boundary (/16)
At that point – my stance in opposition of this policy *MAY* change – but certainly not before then. I remain opposed
From: Seun Ojedeji [mailto:seun.ojedeji at gmail.com]
Sent: 02 April 2017 19:04
To: Alan Barrett <alan.barrett at afrinic.net>
Cc: rpd <rpd at afrinic.net>
Subject: Re: [rpd] Fwd: new policy proposal "Soft Landing - SD"
You actually got it right as i am assuming some typo in what you've posted. For clarity, below is what it means:
"The total amount of IPv4 space allocated or assigned to any organisation during Exhaustion Phase 1 may not exceed the equivalent of a /17, and the total amount of IPv4 space allocated or assigned to any organisation during Exhaustion Phase 2 may not exceed the equivalent of a /20. Such total amounts of IPv4 space may be made up of multiple smaller allocations or assignments (but not less than /24)."
I hope this also answers McTim's clarification question.
On 2 Apr 2017 16:42, "Alan Barrett" <alan.barrett at afrinic.net<mailto:alan.barrett at afrinic.net>> wrote:
> On 2 Apr 2017, at 10:07, Ernest <ernest at afrinic.net<mailto:ernest at afrinic.net>> wrote:
> Policy Proposal: Soft Landing SD
> ID: AFPUB2017V4001DRAFT01
> Submission Date: 30 March 2017
> Modify section 5.4.4 of the CPM to the following:
> For any LIR or End User requesting IPv4 address space during the Exhaustion There is no explicit limit on the number of times an organization may request additional IPv4 address space, so long as such organisation has not received allocations/assignments equivalent to the maximum prefix during
> each phase.
I find this wording difficult to understand. I think you mean something like this:
The total amount of IPv4 space allocated or assigned to any organisation during Exhaustion Phase 1 may not exceed the equivalent of a /17, and the total amount of IPv4 space allocated or assigned to any organisation during Exhaustion Phase 1 may not exceed the equivalent of a /22. Such total amounts of IPv4 space may be made up of multiple smaller allocations or assignments.
RPD mailing list
RPD at afrinic.net<mailto:RPD at afrinic.net>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the RPD