[arin-ppml] Policy Proposal 2010-10 - Global Policy for IPv4 Allocations by the IANA Post Exhaustion

[Dylan Ebner]

I think the transfer policy is important, but at Owen states, an enabling policy is also very important and possibly the policy could move forward without it if language was added that somehow required the transfer policy in the future.
Also, and I may be mistaken on this, doesn't IANA have a policy in which they are preferencing /8 allocations to RIRs that service developing nations? If they do, what happens if final /8 blocks start to run out and then the RIRs that should be getting those /8 allocations cannot get the blocks they need. I worry that AfriNIC and LACNIC will end up getting shafted here.


Dylan Ebner
-----Original Message-----
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Owen DeLong
Sent: Monday, August 30, 2010 9:28 PM
To: Hannigan, Martin
Cc: arin-ppml at arin.net
Subject: Re: [arin-ppml] Policy Proposal 2010-10 - Global Policy for IPv4 Allocations by the IANA Post Exhaustion

Just drop the transfer restriction in my opinion. The other RIRs can choose not to return space until the transfer issue is rectified, but at least we would have enabling policy at IANA.

Owen


Sent from my iPad

On Aug 31, 2010, at 8:37 AM, "Hannigan, Martin" <marty at akamai.com> wrote:

> 
> 
> 
> On 8/30/10 5:54 PM, "Chris Grundemann" <cgrundemann at gmail.com> wrote:
> 
>> On Mon, Aug 30, 2010 at 15:29, David Farmer <farmer at umn.edu> wrote:
>>> This isn't going to fly in APNIC.  APNIC will not agree to the no transfer
>>> provision.  Furthermore, as currently written it sets up a winner take all
>>> race to the bottom, a maximum allocation size would be an easy to fix this
>>> without making things to complicated.
>> 
>> The no-transfer provision is essential. Without it, a region with a
>> very liberal / non-needs-based transfer policy can potentially suck
>> all of the remnants into their region and sell them off.
> 
> I don't think that this is the intention of the transfer policy in APNIC,
> but this is an unfortunate effect of it and one that is a rather large,
> real, risk and which contributed to the demise of the previous discussion.
> 
> 
> [ clip ]
> 
>>> So my question to the rest of the AC, how should we proceed, keep text that
>>> we know will not succeed as global policy or change text?  What would it
>>> take to make a radical change to the Draft Policy?  Otherwise, we would need
>>> to come to the next meeting with new text which likely be past IANA run-out.
>> 
>> I disagree that radical changes are needed. Simply adding a maximum
>> allocation to the existing proposal would accomplish this.
> 
> I do too. This is part of the process. The operation of the allocation
> method does not match the stated intent of the proposal.
> 
>> From the proposal:
> 
>    "Defines "need" as the basis for further IPv4 allocations by the IANA."
> 
> The feedback from the APNIC region pointed out a mechanical problem. While
> need is intact in the definition of exhaustion and use, fairness was lost.
> Minor revision. If there's something to focus on it would be how to make
> this work if the transfer section will not work.
> 
> 
> [ clip ]
> 
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net if you experience any issues.