[arin-ppml] ARIN-prop-172 Additional definition for NRPM Section 2 - Legacy Resources
Kevin Kargel
kkargel at polartel.com
Mon Jun 18 10:44:23 EDT 2012
>
> Yes, I agree that there are several other things that need to be
> implemented at the same time. And I agree that an 8.3 transfer
> terminates legacy status. There are several type sub types of
> transactions that occur under 8.2, some of these I feel it would be
> unfair to terminate Legacy status for, others I would probably be OK
> with it terminating legacy status. Unless we tweeze apart 8.2 into sub
> categories, I'd suggest we just allow M&As to keep legacy status, but
> how about we discuss that on one of the other threads.
>
> --
> ===============================================
> David Farmer Email:farmer at umn.edu
I still feel that if a "Legacy" resource is transferred from one party to
another for whatever reason or through whatever mechanism it should no
longer retain "Legacy" status.
Kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4935 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20120618/b9a7d85c/attachment.bin>
More information about the ARIN-PPML
mailing list