[arin-ppml] ARIN-prop-131: Section 5.0 Legacy Addresses
jeffrey.lyon at blacklotus.net
Mon Feb 14 16:13:43 EST 2011
On Mon, Feb 14, 2011 at 3:23 PM, Owen DeLong <owen at delong.com> wrote:
> Legacy and other addresses returned should be treated the same.
> Once an address is returned to ARIN, it is no longer a legacy address.
> This policy does not make sense so long as it singles out legacy addresses.
> On Feb 14, 2011, at 6:55 AM, Martin Hannigan wrote:
>> On Wed, Feb 9, 2011 at 6:22 PM, Chris Grundemann <cgrundemann at gmail.com> wrote:
>> [ snip ]
>>> Marty - Can you shed some light onto why this is (and needs to be)
>>> limited to legacy space? I don't see a need for the distinction but
>>> could certainly be missing something.
>> In the past, we've heard numerous ARIN folks talking about "clear
>> instructions from the community".
>> Right now, we have multiple global policies circulating trying to
>> determine what should be done with ipv4 legacy addresses in the ARIN
>> ARIN has always treated IPv4 legacy addresses different (LRSA, etc)
>> and our discussions make distinctions between "RSA" and "legacy
>> There is likely some minor, but necessary policy required to make
>> whatever will transpire with legacy addresses acceptable and workable
>> to all.
>> This would be a clear instruction that would leave no ambiguity with
>> respect to what the community wants ARIN to do with legacy addresses.
>> This proposal leaves noone wondering what will happen to addresses
>> returned to ARIN and it codifies the requirement.
>> Is there a problem with resources already in ARIN's possession being
>> returned to "inventory"? If there is, in the interest of clarity, I
>> think it would be better to submit an ASCP item or propose something
>> specific IMHO.
>> I've softened this enough to hopefully clarify it's intent. As a side
>> benefit, it should also encourage people writing global policies to
>> work together.
>> 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.
> 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.
I also agree with Owen on this point.
Jeffrey Lyon, Leadership Team
jeffrey.lyon at blacklotus.net | http://www.blacklotus.net
Black Lotus Communications - AS32421
First and Leading in DDoS Protection Solutions
More information about the ARIN-PPML