[arin-ppml] ARIN Draft Policy 2017-3: Update to NPRM 3.6: Annual Whois POC Validation

Chris James chris at datacate.com
Wed May 10 20:48:54 EDT 2017


Voluntary return of resource, and court order should be the only conditions
in which a POC and rDNS pointer is removed. Possibly an exception for
verified hijacking of resources, but even then the conditions would need to
be ultra stringent and only to prevent further verified malicious activity.
Removing a resource due to lack of updated information which could wholly
be due to simple oversight, lack of former administrator documentation or
even a spam filter will have negative repercussions for the internet as a
whole with emphasis on smaller ISPs who can afford this the least.


*Chris James*


[image: Datacate]


t. 916-526-0737 ext 1002
e. chris at datacate.com
a. 2999 Gold Canal Dr., Rancho Cordova, CA 95670
w. https://www.datacate.net
*__________________________________________*

On Wed, May 10, 2017 at 5:17 PM, John Curran <jcurran at arin.net> wrote:

> On 10 May 2017, at 5:57 PM, hostmaster at uneedus.com wrote:
> >
> > Just as a point of information, can someone from ARIN tell us under what
> conditions (if any) is the POC or the rDNS pointers removed under the
> current policy?
>
> When the resources are reclaimed/returned/returned to ARIN, the number
> resources
> are updated in the registry to point to ARIN, including POC and reverse
> DNS pointers.
> Once reissued, they are changed once again (as it done with any issuance)
> to point
> to the new resource holder.
>
> Thanks,
> /John
>
> John Curran
> President and CEO
> ARIN
>
>
>

-- 
This e-mail message may contain confidential or legally privileged 
information and is intended only for the use of the intended recipient(s). 
Any unauthorized disclosure, dissemination, distribution, copying or the 
taking of any action in reliance on the information herein is prohibited. 
E-mails are not secure and cannot be guaranteed to be error free as they 
can be intercepted, amended, or contain viruses. Anyone who communicates 
with us by e-mail is deemed to have accepted these risks. This company is 
not responsible for errors or omissions in this message and denies any 
responsibility for any damage arising from the use of e-mail. Any opinion 
and other statement contained in this message and any attachment are solely 
those of the author and do not necessarily represent those of the company.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20170511/372bb492/attachment-0001.html>


More information about the ARIN-PPML mailing list