[arin-ppml] ARIN-prop-131: Section 5.0 Legacy Addresses - revised
owen at delong.com
Fri Feb 11 16:16:54 EST 2011
Legacy space returned to ARIN is treated like any other returned space today to the extent that is specified in this proposal.
Without the 30 day clause, this proposal is a no-op.
With the word Legacy, the policy is harmful.
On Feb 11, 2011, at 1:07 PM, David Farmer wrote:
> On 2/11/11 12:01 CST, Martin Hannigan wrote:
>> Thanks. If you'd like to target additional non-specific concerns, I'd
>> suggest that you craft a proposal for consideration.
> I probably will, I've thought of a few ideas subsequent to responding.
>> I'm targeting a
>> specific, highly charged, global issue and the proposal needs to be
>> crystal clear.
> Yep, I understand.
>> Based on preliminary feedback, I believe that it is in
>> it's current state.
> I disagree, there is one issue that is muddying things for me still. Let me quote the operable part of the policy text and then I'll explain.
>> Legacy IPv4 addresses returned to or recovered by ARIN will be made
>> available for registration and distribution in the ARIN region within
>> thirty days of their receipt.
> In the first part you I think you are trying to say "treat any Legacy IPv4 address space returned or recovered the same way any non-legacy IPv4 addresses would be within the ARIN region." It is the last part of the sentence "within thirty days of their receipt." that muddies things for me. It is kind of saying "BUT, now treat it in this different way", which conflict with the intent of the beginning part. Pull out the 30 day clause, then it makes sense to me for this policy to be limited to Legacy IPv4 addresses.
> However, with the 30 day clause in there I want that clause to apply to both Legacy and non-Legacy address space. I actually think the 30 day clause is a good policy intent, but it needs to apply to both Legacy and non-Legacy IPv4 address space, applying it to Legacy only is bad and broken policy.
> So, I think it is the 30 day clause that has a number of people asking why should this policy only apply to Legacy IPv4 address space.
>> With respect to administration, I'll wait until
>> the full staff and legal review before I comment, or edit, further.
> Furthermore, I believe that clause without additional clarification creates a conflicts with contractual obligations that ARIN has with any organization that has signed the LRSA.
> Unless, you believe that once an organization signs a LRSA its resources are no longer Legacy IPv4 addresses.
> So, if you want to keep this policy crystal clear pull the 30 day clause out, then I could probably support it.
> David Farmer Email:farmer at umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE Phone: 612-626-0815
> Minneapolis, MN 55414-3029 Cell: 612-812-9952
> 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:
> Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML