[arin-ppml] ARIN-prop-172 Additional definition for NRPM Section 2 - Legacy Resources

[Martin Hannigan]

This works for me.


Anyone else have a constructive suggestion before I submit a final revision?



On Tue, Jun 5, 2012 at 4:12 PM, Lindsey, Marc <mlindsey at lb3law.com> wrote:
> Owen – I’m not up to the task of convincing you to change your beliefs about
> the nature of the rights (or lack of rights) embodied in legacy numbers.   I
> will simply point out that the proposed policy at issue (i.e., establishing
> a definition for legacy resources) is itself an acknowledgment that there
> is, in practice, a meaningful distinction between legacy and non-legacy
> numbers.
>
>
>
> I accept the constructive criticism regarding the structure of my proposed
> revision to the definition.  I’ve restated it below in a way that,
> hopefully, is more readable:
>
>
>
> A legacy resource is an IPv4 address or Autonomous System Number that
> satisfies both of the following two criteria:
>
>
>
> (1)    it was issued to an entity (other than a Regional Internet Registry)
> or individual (the “original legacy holder”) prior to ARIN's inception on
> Dec 22, 1997 either by an organization authorized by the United States to
> perform the Internet Assigned Numbers Authority (“IANA”) functions or an
> Internet Registry; and
>
>
>
> (2)    it has not been returned to a Regional Internet Registry under a
> binding written agreement between the original legacy holder (or its legal
> successor or assign) and the RIR for subsequent allocation and assignment in
> accordance with such RIR’s number resource policies and membership (or
> service) agreements.
>
>
>
> -Marc
>
>
>
> From: Owen DeLong [mailto:owen at delong.com]
>
> Sent: Tuesday, June 05, 2012 3:26 PM
> To: Lindsey, Marc
> Cc: 'arin-ppml at arin.net'
> Subject: Re: [arin-ppml] ARIN-prop-172 Additional definition for NRPM
> Section 2 - Legacy Resources
>
>
>
>
>
> On Jun 5, 2012, at 12:06 PM, Lindsey, Marc wrote:
>
>
>
> I support creating a definition in the NRPM of legacy resources so that
> future policy proposals can properly acknowledge and address the distinction
> between the bundle of rights associated with legacy numbers and the
> specifically defined contract rights attributable to non-legacy resources.
>
>
>
>
>
> What distinction would that be?
>
>
>
> I remain unconvinced that any such distinction exists other than some
> ability to remain static and not pay fees.
>
>
>
> I would , however, suggest some revisions to the definition as proposed.
> The revised definition is as follows:
>
>
>
> A legacy resource is an IPv4 address or Autonomous System Number that (a)
> was issued to an entity (other than a Regional Internet Registry) or
> individual (the “original legacy holder”) prior to ARIN's inception on Dec
> 22, 1997 either by an organization authorized by the United States to
> perform the Internet Assigned Numbers Authority (“IANA”) functions or an
> Internet Registry, and (b) has not been returned to a Regional Internet
> Registry under a binding written agreement between the original legacy
> holder (or its legal successor or assign) and the RIR for subsequent
> allocation and assignment in accordance with such RIR’s number resource
> policies and membership (or service) agreements.
>
>
>
> That's a very complex and difficult to parse runon sentence.
>
>
>
> As much as it pains me to do so, I have to agree with Milton that the best
> definition is: "Legacy allocations/assignments are those
> allocations/assignments maintained in the ARIN database not covered by any
> form of RSA between ARIN and the recipient."
>
>
>
> Owen
>
>
>
>
> _______________________________________________
> 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.