[arin-ppml] Policy idea: POC Validation
owen at delong.com
Mon Apr 13 18:36:59 EDT 2015
ARIN isn’t creating those separate POCs… They are created by CenturyLink or whoever in the ARIN database.
I would suggest asking CenturyLink or your other providers to use a consistent contact or find another way to deal with those registrations.
You can actually associate all of those contacts with the same ARIN online login, no hoops required.
Yes, you have to validate each one individually, but in my experience so far, that has consisted of clicking on a URL in the POC validation email and moving on.
> On Apr 13, 2015, at 2:52 PM, Jay Hennigan <jay at impulse.net> wrote:
> On 4/13/15 1:29 PM, Owen DeLong wrote:
>> I don’t see the angry phone call as the problem. I see it as a symptom.
>> The problem is the incorrect registrations. I want us to find out about those incorrect registrations and resolve them. I certainly don’t want to simply remove the symptom (angry phone call) by masking the problem (incorrect registration).
> They aren't necessarily incorrect registrations, they're redundant registrations never requested by the POC. I've been on the receiving end of this for several years. Here's one issue as I've observed it.
> We're a regional ISP, and from time to time will have a customer out of our service area with a need for direct Internet access. We contract with several major providers for this, and one of them is Centurylink.
> CenturyLink has some form of (presumably automated) process where they process our order and submit my contact information from their order to ARIN, consisting of my email address, phone number, etc. but with the street address of our end-user customer.
> For each of these, ARIN generates a separate unique POC record and then sends annual POC validation requests. Of course, until I get these annual requests, I have no idea that the POC records even exist.
> ARIN apparently expects me to, for each and every one of these, jump through several flaming hoops on their website to obtain a login, then validate each and every one of them separately.
> For anyone who hasn't done so, and this should be a requirement for anyone in ARIN's web coding group, go to the ARIN page and try to set up authentication for an existing POC for yourself that you didn't know existed. It isn't exactly fun, nor quick, nor intuitive.
> I haven't needed to resort to angry phone calls, but have generally been able to resolve this by email. Ignore the auto-response that suggests you do this yourself on the ARIN website, unless you like pain.
> Jay Hennigan | CCIE #7880 | jay at impulse.net | www.impulse.net
> Voice +1.805.884.6323 | Fax +1.805.880.1523 | WB6RDV
> Chief Network Architect | Impulse Advanced Communications
> 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:
> Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML