[arin-ppml] ARIN-prop-131: Section 5.0 Legacy Addresses

cja@daydream.com packetgrrl at gmail.com
Mon Feb 14 14:18:53 EST 2011


I'd like to understand the argument as to why we should only include legacy
space and not non-legacy space?  Can someone explain it to me?

I really thought this policy was to fill the gap in the IANA policy that
only allows /8s to go from IANA to the RIRs and to be specific about what
ARIN was going to do with any returned address space post IANA depletion.
 As shepherd for this proposal I am really trying to understand why it is
specifically limited to legacy space?

Thanks!

On Mon, Feb 14, 2011 at 11:56 AM, Martin Hannigan <hannigan at gmail.com>wrote:

> On Mon, Feb 14, 2011 at 1:44 PM, Chris Grundemann <cgrundemann at gmail.com>
>
> >
> > I agree. I see no reason to distinguish in this case. IMHO, this
> > policy should apply to ALL addresses returned to ARIN.
> >
>
>
> I disagree. If some on the AC want to modify this when the AC receives
> it, that's up to them. I've made the edits that will resolve the
> issues that I've identified in the most clear and concise way
> possible. So far, I've heard only straw-men as to why to include any
> other text. If I read something that is significant and that doesn't
> seek to lop on complexity and unnecessary actions, I'll be happy to
> reconsider.
>
> Best,
>
> -M<
> _______________________________________________
> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20110214/3f839230/attachment.html>


More information about the ARIN-PPML mailing list