[arin-ppml] Draft Policy ARIN-2016-8: Removal of Indirect POC Validation Requirement

Alyssa Moore alyssa.moore at cybera.ca
Thu Dec 22 12:41:14 EST 2016


I think the unsolicited commercial e-mail argument is a bit of a straw-man,
at least from a legal perspective. Perhaps not from a landing ARIN on
anti-spam lists perspective.

Under the Canadian anti-spam law (CASL),  I believe the relationship with
ARIN would fall under implied consent by virtue of the
indirectly-registered user utilizing ARIN resources. Notably, the Canadian
anti-spam legislation also states that:

"If you continue to send CEMs over time, based on implied consent, there is
an ongoing need to maintain accurate records."

Not sure what that looks like stateside, or in the Caribbean. I'd
appreciate if a lawyer on the list could weigh in.

If we're going to pursue an alternative policy proposal that falls in the
middle ground between eliminating indirect POC validation and validating
every indirect POC, I like Scott's assertion that an immediate approach to
validation of a new resource user is necessary, if only for socialization
of the relationship going forward. This deviates from policy-making and
enters the weeds of ARIN operations, though.

On Thu, Dec 22, 2016 at 9:54 AM William Herrin <bill at herrin.us> wrote:

> On Wed, Dec 21, 2016 at 4:25 PM, james machado <hvgeekwtrvl at gmail.com>
> wrote:
> > As a former (and possibly current) assignee of a SWIP reassignment one of
> > the larger issues is I had no idea I had multiple POCs created by the
> ISPs
> > in the first place.
> >
> > Prior to getting my current assignment, the ISP I was using created a POC
> > for each SWIP it remembered to do.  Thus I had POCa, POCb ... POCn, one
> for
> > each circuit/address combo from each ISP.   Even after doing multiple
> > searches I am not sure I have found them all.
>
> Hi James,
>
> This sounds like another ARIN process issue to me. Unless you used a
> different email address for each one, ARIN should have been able to
> detect and do something sensible with the duplicates.
>
>
> > There should also be a stick.  I don't know the form of the stick but
> those
> > creating the third party POCs should be held accountable when they 1)
> don't
> > do them and 2) do them wrong.
>
> Just so.
>
> Regards,
> Bill Herrin
>
>
> --
> William Herrin ................ herrin at dirtside.com  bill at herrin.us
> Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/>
> _______________________________________________
> PPML
> 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.
>
-- 
Alyssa Moore
Policy & Strategy Analyst
Cybera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20161222/f21358f6/attachment-0001.html>


More information about the ARIN-PPML mailing list