[ARIN-consult] Community Consultation on CKN23-ARIN Now Open

[Steve Noble]

Hi John,

Having been bit by this and ending up in a multi-year mess to get control
of an AS that was clearly mine, while still getting billed for it, I am
concerned about the vetting process. My experience with the vetting process
was very uncomfortable and is something that I do not believe anyone should
have to go through.

My suggestion is to remove the incorrect information such as CKN23-ARIN
from the objects and return them to their proper state. This will give those
in control of the object the ability to update information such as the
physical address.


On Mar 28, 2017 7:46 AM, "John Curran" <jcurran at arin.net> wrote:

On 28 Mar 2017, at 10:20 AM, Jason Schiller <jschiller at google.com> wrote:
>
> I am comfortable with option 3 where the records are restored, but the
POC is not provided ARIN-Online access so long as there is a process by
which a resource holder can validate the chain of custody and fully vet
their right to use the resource without signing an RSA.

Jason -

Yes, that is the intention - we will lock the resources until the contact
has has vetted
and is confirmed valid.

As always, resource holders may opt to enter into an RSA (if they wish
contractual
statement of rights and use of new services), but once vetted they are not
required
to do so in order to administer their legacy resource (i.e. setting such
attributes as
contacts, reverse DNS servers, and origin AS tag.)

Thanks for the feedback,
/John

John Curran
President and CEO
ARIN




_______________________________________________
ARIN-Consult
You are receiving this message because you are subscribed to the ARIN
Consult Mailing
List (ARIN-consult at arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN
Member Services
Help Desk at info at arin.net if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20170328/bba4c7ee/attachment.html>