[arin-ppml] Incorrect POC on resource records
snoble at sonn.com
Wed Sep 26 11:11:55 EDT 2012
On Sep 26, 2012, at 8:01 AM, Ted Mittelstaedt <tedm at ipinc.net> wrote:
> Sorry, but the address user is required to respond. When they signed the RSA the RSA requires them to supply POCs. By allowing a POC to become invalid they are no longer supplying the POC and are thus in
> violation of the contract.
> In any case, if an org deliberately ignores an invoice, their account
> with ARIN runs in arrears and they lose the assignment.
> If an org pays an invoice sent to the POC address then they ARE responding.
Then that does not explain why ARIN would purposely change a post-ARIN ORG POC to No, Contact Known if they are getting paid, which I can personally attest they have done at least once.
> The issue are the so called Legacy assignments made pre-ARIN that there
> is no RSA on file for. However, the NRPM requires ARIN to mark these
> as invalid if the POC fails to respond.
> So while your opinion may be that ARIN should never break a record,
> the NRPM says otherwise.
So marking a ORG invalid requires that ARIN put an invalid POC in the record and then force the owner to go through hoops to get the ORG restored? That makes no sense. Can you give me the part of the NRPM that you are quoting?
> Frankly, I see absolutely no benefit to the community to allow POCs
> to remain in WHOIS that do not respond to anyone. At least, if the POC
> is responding to ARIN but nobody else, that is some justification for
> leaving them in there. But if they don't even respond to ARIN?
How do you know they are not responding to anyone. Just because they do not respond to ARIN means nothing. And even if they are responding to ARIN, are you claiming that ARIN does not invalidate POCs if they get a response? I again will claim otherwise.
> Screw 'em!
That is exactly the attitude we should be trying to avoid.
More information about the ARIN-PPML