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

[David Farmer]

On 6/5/12 17:02 CDT, Kevin Kargel wrote:
>
> I strongly feel that addresses brought under *RSA should no longer be
> considered "Legacy".  To my way of thinking an active Legacy resource
> implies it is supported but not regulated by an agreement, and any version
> of RSA brings with it regulation by agreement.

So, what does legacy mean (the English word)?

Legacy
1. Law . a gift of property, especially personal property, as money, by 
will; a bequest.
2. anything handed down from the past, as from an ancestor or 
predecessor: the legacy of ancient Rome.
3. an applicant to or student at a school that was attended by his or 
her parent.
4. Obsolete . the office, function, or commission of a legate.
adjective
5. of or pertaining to old or outdated computer hardware, software, or 
data that, while still functional, does not work well with up-to-date 
systems.

#2 seem most the most appropriate to the situation, although #1, #5 are 
interesting side notes.

This seem to most directly speak to the relationship between ARIN and 
the resource registration, the registration was "handed down" to ARIN 
from its predecessor registries (Postel's notebook :), SRI, InterNIC, 
Etc...) by the US Gov (through NFS with the assent of several other fed 
agencies and oversight bodies).  When ARIN was created there wasn't any 
change in the relationship between the resource holder and the resource. 
  That relationship was established when the assignment was made.  Also, 
if the resource holder still exists and is using the resource, then I 
contend, the relationship between the resource and resource holder has 
never changed and never will change.

I'll add, there was nothing special about the "hand down" to ARIN, it 
was just the latest in a long long line of them.  And who knows, it very 
well may not the the last.  However, please lets not go through that 
again anytime soon. :)

Kevin, to your point; A contract clarifying the relationship between the 
resource holder and ARIN, neither changes the relationship between the 
resource holder and the resource nor ARIN and the resource registration, 
it only simply clarifies the relationship between ARIN and the resource 
holder, that is it. The registration was still "handed down" to ARIN.

Now if a resource holder seeks to transfer the resource, then that would 
change the relationship between both the resource and the resource 
holder and the resource registration and ARIN.  The registration is no 
longer "handed down" to ARIN but a new registration with ARIN, and the 
term legacy would seem to no longer seem to apply.

So, what about those other definitions;  #1 is interesting as it speaks 
to property but again the bequest seems to be to ARIN from it 
predecessor registries.  I don't see any change between the relationship 
of resource holder and the resource.  The resource holder isn't making a 
bequest, and if they were, of what to whom?  #5 would be an interesting 
usage, but would seem to apply to all IPv4 addresses. :)

So I would have to say a legacy address or resource: is a resource that 
the registration of which ARIN inherited and for which the registration 
has not been changed. It is probably useful to add a few additional 
details (like IPv4 and ASNs, the date ARIN was created, who ARIN 
inherited them from, etc...) but that is mostly icing on the cake, the 
cake is "ARIN inherited the registration, and registration hasn't been 
changed"

There is another definition that might be useful "legacy resource 
holder" in this case the term legacy now seems to refer to the 
transitive relationship of the resource holder to the resource and the 
resource registration to ARIN, therefore speaking to the relationship of 
ARIN and the resource holder.

Finally, I don't see where or how the term legacy creates any unique 
property of the resource itself, it only seems to be a property of the 
relationship between ARIN and the resource registration and possibly 
transitively to the relationship between the resource holder and ARIN.

-- 
===============================================
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
===============================================