[arin-ppml] Draft Policy ARIN-2017-5: Equalization of Assignment Registration requirements between IPv4 and IPv6

Andrew Bagrin abagrin at mydigitalshield.com
Fri Jul 21 07:23:48 EDT 2017


Wow, what did I miss?



I hope we’re not trying solve a security problem through a strict
requirement of SWIP or anything that we’re doing. I hate to break it to
everyone, but bad guys always find another way around and don’t really care
about following any rules we create. We should be more focused on what
makes sense and will benefit the general population when used correctly.

As soon as ARIN decides to do something for “security” and that enforcement
is “worked around”, ARIN will be looked at as a failure.



As long the tool is available and all ISP are motivated to use it properly,
it will work in general. There will always be exceptions. (fake entries
etc..) some for bad reasons (like spammers) and some for good reasons
(anonymity).



I’m good with any of the proposed. I would like to see more SWIP occurring
and motivate ISP’s to do it by default unless the customer specifies they
do not want their info tied to that IP address (commercial and
residential).



*From:* ARIN-PPML [mailto:arin-ppml-bounces at arin.net] *On Behalf Of *
Marilson
*Sent:* Friday, July 21, 2017 12:46 AM
*To:* Owen DeLong <owen at delong.com>; Pallieter Koopmans <
Pallieter at pallieter.org>
*Cc:* arin-ppml at arin.net
*Subject:* Re: [arin-ppml] Draft Policy ARIN-2017-5: Equalization of
Assignment Registration requirements between IPv4 and IPv6



Gentlemen, let me introduce practical elements into this "difficult and
onerous" attitude, but ethical, on the tech and abuse contact requests.



Let's see in practice how it works when organizations accept and disclose
absolutely false data, and when questioned, they simply lie or ignore it.

We have on one side a well-known and hated spammer, on the other an ISP who
insists on ignoring the denunciations, norms and laws, protecting and
maintaining the profits that this spammer provides. And above all an entity
that is self-titled as the regulator of good practice on the internet:



*From:* Marilson

*Sent:* Wednesday, July 19, 2017 3:55 AM

*To:* compliance at icann.org ; complaints at icann.org

*Cc:* crain at icann.org ; tips at nytimes.com ; spam at uce.gov ;
privacy at council.bbb.org ; iana at iana.org ; anonbrpt at anonymousbrasil.com

*Subject:* Fw: [#HTK-505-74506]: Whois Inaccuracy complaint re:
boasvendas.info closed



Lie! The domain was not suspended and neither the Registrar or ISP
suspended, deleted, cancelled or even deactivated the domain name. The
spammer continues with their totally incorrect WHOIS data, making it
impossible to take any defensive action because he has the protection of
his ISP, Registrar, RIR and ICANN.



What makes me impressed is how all of you treat the complaints, as if we
were all morons.



Your behavior is exactly like the behavior of most ISPs when receiving spam
and scam complaints. Greed and lack of ethics in protecting spammers and
scammers, to increase traffic on the internet, has no limits. You...
(truncated). And you survive because you have the protection of your
governments that are, as a rule, run by corrupt politicians.



Thanks for nothing

Marilson



*******************************************************************************************************************************

*From:* compliance-tickets at icann.org

*Sent:* Monday, July 17, 2017 11:43 PM

*To:* marilson.mapa at gmail.com

*Subject:* [#HTK-505-74506]: Whois Inaccuracy complaint re: boasvendas.info
closed



Dear Marilson,

Thank you for submitting a Whois Inaccuracy complaint concerning the domain
name boasvendas.info. ICANN has reviewed and closed your complaint because:

- Based on the current Whois data, the domain was suspended when the
complaint was received by ICANN, or the registrar demonstrated that it took
reasonable steps to investigate the Whois inaccuracy claim by suspending,
deleting, cancelling or otherwise deactivating the domain name.

ICANN considers this matter now closed.

Please do not reply to the email. If you require future assistance, please
email compliance at icann.org; if you have a new complaint, please submit it
at http://www.icann.org/resources/compliance/complaints .

ICANN is requesting your feedback on this closed complaint. Please complete
this optional survey at
https://www.surveymonkey.com/s/8F2Z6DP?ticket=HTK-505-74506 .

Sincerely,

ICANN Contractual Compliance

############################################

The problem summary:

Reporter Name: Marilson
Reporter Email: marilson.mapa at gmail.com
Domain being reported: boasvendas.info

Time of submission/processing: Wed Jun 28 17:59:43 2017

Problem in whois block: Expiration Date
--- Error in date: Nothing to report

Problem in whois block: Technical Contact
--- Error in address: Incorrect address
--- Error in phone number: Incorrect phone
--- Error in name: Wrong person or entity
--- Error in email: Nothing to report
--- Error in fax number: Fax is missing
--- Comment: He is a spammer and someone want to keep him hidden from his
victims.

Problem in whois block: Registrant Contact
--- Error in address: Incorrect address
--- Error in name: Wrong person or entity
--- Comment: Registrant ID: C205479611-LRMS
Registrant Name: BenL. A.  - FAKE – DOESNOT EXIST
Registrant Organization: ???
Registrant Street: Estrada J. C. - FAKE – DOESNOT EXIST
Registrant City: Curtume - FAKE – DOESNOT EXIST
Registrant State/Province: Sao Paulo
Registrant Postal Code: 18110000 - FAKE – DOESNOT EXIST
Registrant Country: BR
Registrant Phone: +55.4333566600 - FAKE – DOESNOT EXIST

He is a spammer and someone want to keep him hidden from his victims.

Problem in whois block: Registration Date
--- Error in date: Nothing to report

Problem in whois block: Administrative Contact
--- Error in address: Incorrect address
--- Error in phone number: Incorrect phone
--- Error in name: Wrong person or entity
--- Error in email: Nothing to report
--- Error in fax number: Fax is missing
--- Comment: Boasvendas.info is a spammer and someone want to keep him
hidden from his victims.

The whois at the time of processing is:

REGISTRY WHOIS:

Domain Name: BOASVENDAS.INFO
Registry Domain ID: D503300000040848348-LRMS
Registrar WHOIS Server:
Registrar URL: http://www.wildwestdomains.com
Updated Date: 2017-06-24T11:29:56Z
Creation Date: 2017-06-19T21:44:52Z
Registry Expiry Date: 2018-06-19T21:44:52Z
Registrar Registration Expiration Date:
Registrar: Wild West Domains, LLC
Registrar IANA ID: 440
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: clientDeleteProhibited
https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited
https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited
https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited
https://icann.org/epp#clientUpdateProhibited
Domain Status: serverTransferProhibited
https://icann.org/epp#serverTransferProhibited
Registry Registrant ID: C205479611-LRMS
Registrant Name: BenL. A.
Registrant Organization:
Registrant Street: Estrada J. C.
Registrant City: Curtume
Registrant State/Province: Sao Paulo
Registrant Postal Code: 18110000
Registrant Country: BR
Registrant Phone: +55.4333566600
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: bouces1967 at gmail.com
Registry Admin ID: C205479613-LRMS
Admin Name: BenL. A.
Admin Organization:
Admin Street: Estrada J. C.
Admin City: Curtume
Admin State/Province: Sao Paulo
Admin Postal Code: 18110000
Admin Country: BR
Admin Phone: +55.4333566600
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: bouces1967 at gmail.com
Registry Tech ID: C205479612-LRMS
Tech Name: BenL. A.
Tech Organization:
Tech Street: Estrada J. C.
Tech City: Curtume
Tech State/Province: Sao Paulo
Tech Postal Code: 18110000
Tech Country: BR
Tech Phone: +55.4333566600
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: bouces1967 at gmail.com
Registry Billing ID: C205479614-LRMS
Billing Name: BenL. A.
Billing Organization:
Billing Street: Estrada J. C.
Billing City: Curtume
Billing State/Province: Sao Paulo
Billing Postal Code: 18110000
Billing Country: BR
Billing Phone: +55.4333566600
Billing Phone Ext:
Billing Fax:
Billing Fax Ext:
Billing Email: bouces1967 at gmail.com
Name Server: NS1.BOASVENDAS.INFO
Name Server: NS2.BOASVENDAS.INFO
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form:
https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2017-06-28T17:59:03Z <<<

For more information on Whois status codes, please visit
https://icann.org/epp
------------------------------



That is it.

Marilson



*******************************************************************************************************************************

*From:* Owen DeLong <owen at delong.com>

*Sent:* Thursday, July 20, 2017 5:16 PM

*To:* Pallieter Koopmans <Pallieter at pallieter.org>

*Cc:* arin-ppml at arin.net

*Subject:* Re: [arin-ppml] Draft Policy ARIN-2017-5: Equalization of
Assignment Registration requirements between IPv4 and IPv6



How can it be overly difficult to fill out an email template with your
customers’
Name, Address, Phone Number?

Really?

Owen

> On Jul 19, 2017, at 23:48 , Pallieter Koopmans <Pallieter at pallieter.org>
wrote:
>
> Hello,
>
> ARIN could quantify and require rules for when to SWIP, but in the
> end, there are going to be exceptions needed if the rules are to be
> strictly followed. Many will not separately SWIP a separately routed
> sub-block if it is too difficult or pointless to gather and share that
> data back upstream to ARIN.
>
> Thus a more fuzzy rule to require a best-effort and to add a
> rule-based reason (preferably both a carrot and a stick) for block
> owners to do their best to provide (only) useful data. In order to do
> that, one needs to look back at why that data is needed. For a block
> owner to assign the SWIP on a sub-block, he basically delegates tech
> and abuse contact requests down to those that are probably more likely
> to be able to actually act on the tech/abuse requests (and thus reduce
> request-handling workload higher up and overall). But for that to
> work, those tech/abuse contact requests need to be actually handled,
> otherwise, it is better to leave them with the block owner.
>
> In the end, the contact details should be as close to the "person"
> that is actually capable to both handle (think: volume/languages/etc)
> and act (think: authority) on the tech/abuse requests.
>
> eBrain
> Innovative Internet Ideas
>
> Pallieter Koopmans
> Managing Director
>
> +31-6-3400-3800 (mon-sat 9-22 CET)
> Skype: PallieterKoopmans
> _______________________________________________
> 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.

_______________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20170721/3d7d5588/attachment.html>


More information about the ARIN-PPML mailing list