[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 17:02:39 EDT 2017

Unless reasonable efforts are made to contact the POC, and this includes
researching and contacting the organization along with every possibly
department, identifying clearly the reason for the call, and actually
trying to update the POC, I fully entirely 100% disagree with discontinuing
rDNS services.

Image the negative affect to a small ISP who purchases a unit of a major
corporation, somehow the transfer is not done properly, something is not
updated properly, and suddenly every customer of that small ISP who does
not realize they missed updating the POC on a /18 and now a few hundred
small businesses are screwed?

Image the reverse situation. A major corporation buys a small ISP, I know
we care less and less about the negative impact of policy on ma bell, but
how many innocent users will not receive email, how many inexperienced
users cannot access their own regional bank due to SSL issues thanks to an
arbitrary removal of a few pointers that cost absolutely nothing to keep up?

I wholly disagree with policy that has the potential to negatively impact
innocent or otherwise inexperienced users based on the unwillingness of an
actual human person to do minor due diligence. If this is too costly an
endeavor for ARIN, scrap the policy altogether.

Am I reading too far into this or is this outcome entirely impossible?

*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 12:28 PM, <hostmaster at uneedus.com> wrote:

> So in effect, all the proposed 3.6.4 does is to formalize what is the
> current practice of allowing the change.  Thus, there should be no problems
> with the change.
> Albert Erdmann
> Network Administrator
> Paradise On Line Inc.
> On Wed, 10 May 2017, John Curran wrote:
> On 10 May 2017, at 2:34 PM, John Santos <JOHN at egh.com<mailto:JOHN at egh.com>>
>> wrote:
>> ...
>> I'm a little confused by this because my company is a legacy holder and
>> I'm certain I've updated our POC information several times in the past.
>> (At least once because the phone company changed our area code, once
>> because the Post Office changed our ZIP code, and one of our original POCs
>> retired and I changed our company's administrative POC as a result.)  I've
>> also changed our rDNS server addresses several times over the years. If it
>> makes any difference, I have been responding to the annual "please validate
>> your POC information" email from ARIN.
>> Am I currently prohibited from making changes, or has maintaining the POC
>> information been sufficient to retain my right to update our records?
>> John -
>>  It’s a perfectly reasonable question (as there is quite a bit of
>> misinformation out there…)
>>  At ARIN’s formation, the Board of Trustees decided that ARIN would
>> provide registration
>>  services for these legacy number resources without requiring legacy
>> resource holders
>>  to enter into a registration services agreement or pay any fees.
>>  All legacy number resource holders are provided these traditional
>> registry services
>>  (including the ability to update their information in the ARIN registry)
>> but also have
>>  the option to enter into an agreement and pay standard fees if they wish
>> additional
>>  services or to formalize their contractual relationship with ARIN.
>>  Please refer to <https://www.arin.net/resources/legacy/services.html>
>> for details.
>> Thanks!
>> /John
>> John Curran
>> President and CEO
> _______________________________________________
> 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.

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/20170510/29738a7b/attachment.html>

More information about the ARIN-PPML mailing list