<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Bill,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I would have seen your email earlier, but it was caught in my spam filter.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br>Best regards,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 28, 2018 at 2:22 PM Bill Silverstein <"<a href="mailto:icann.org@sorehands.com">icann.org@sorehands.com</a>"@<a href="http://sorehands.com">sorehands.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am going to take many exceptions to all of this.<br>
<br>
I am one of those individuals who track down spammers. I know several<br>
other people who do similar work, but this is not a business per se.<br>
<br>
As a mail service provider I use the Whois information in deciding to<br>
filter, capture, block spam. Spam filters may do this.<br>
<br>
I capture Whois information of some spam coming in to detect patterns,<br>
determine if the spam is in violation of California law and to determine<br>
if I will file a lawsuit. Whether I am a lawyer is not relevant as I have<br>
brought lawsuits on my own. Even if I did decide to retain an attorney, I<br>
would have had to make the determination to bring a lawsuit.<br>
<br>
What people seemed to have ignored, or forgotten, is that the domain name<br>
registration is voluntary and one does not need to register a domain name.<br>
<br>
What about the right of a recipient knowing the identity of the person<br>
sending them e-mail? What about the right of a mail service provider to<br>
be able to determine who is using my resources and determine if the person<br>
is a spammer? What about Spamhaus? Doesn't Spamhaus use this information<br>
to identify and track spammers? What about other spam filters or<br>
reporters?<br>
<br>
On Tue, August 28, 2018 10:41 am, Gordon Chillcott wrote:<br>
><br>
> Hello, Greg:<br>
><br>
><br>
> I apologize for being so late with my reply here.<br>
><br>
><br>
> I have read Chris' remarks and I do take point on the subject of<br>
> “separate authenticating bodies for each type of eligible user group†<br>
> and he is right about the possibility of gaming strategies. On the other<br>
> hand, it may be difficult to avoid this in some cases. Certain groups<br>
> have accreditation/governing bodies that might be used for this purpose<br>
> – they have already validated their “community members†.<br>
><br>
> The challenge here is to examine the gaming possibilities and build<br>
> mechanisms to avoid them.<br>
><br>
><br>
> On Chris' concern about data retention: I would recommend that the<br>
> intended data retention period be part of the data access request, along<br>
> with a statement of purpose that covers the proposed use of the data and<br>
> its retention.<br>
><br>
><br>
> On the topic of bulk data access, we need a much sharper definition of<br>
> what we mean by this. It certainly cannot be a wholesale download of the<br>
> whole, or even part of the database. It might be, for example, a stream<br>
> of selected fields across a region that is to be used for statistical<br>
> purposes (and with a tightly restricted retention period). This sort of<br>
> access needs to be spelled out. Requests by Law Enforcement Agencies<br>
> present their own challenges, though.<br>
><br>
><br>
> On some of the questions in Section E (pages 7-8):<br>
><br>
><br>
> 1. I believe that requests for non-public WHOIS data should<br>
> describe its purpose on each request. I really need to see the<br>
> arguments against this.<br>
><br>
> 2. Full WHOIS data should not be returned on a request unless that<br>
> request specifically asks for it and provides a legitimate<br>
> reason.<br>
><br>
> 3. Again, I would need to see the arguments against this one, but I<br>
> feel that the registrant should be allowed to request access to<br>
> the logs of query activities.<br>
><br>
><br>
> On question 5 (page 8) the suggestion that fees would be desirable has<br>
> been mentioned in discussions I have had, including with members of my<br>
> ALS. There was some sympathy for the position some Registrars have<br>
> taken; another suggestion was that this might curb “frivolous†<br>
> requests.<br>
><br>
><br>
> Regards,<br>
><br>
><br>
> Gordon Chillcott<br>
> Greater Toronto Area Linux Users Group<br>
><br>
><br>
> On Thu, 2018-08-23 at 00:25 -0400, Greg Shatan wrote:<br>
>> All,<br>
>><br>
>><br>
>><br>
>> As mentioned on today's CPWG call, ICANN org published a blog earlier<br>
>> this week releasing the proposed Unified Access Model for community<br>
>> input.<br>
>><br>
>><br>
>><br>
>> <a href="https://www.icann.org/news/blog/possible-unified-access-model-published-for-community-input" rel="noreferrer" target="_blank">https://www.icann.org/news/blog/possible-unified-access-model-published-for-community-input</a><br>
>><br>
>><br>
>> The proposal itself can be found here: Draft Framework for a Possible<br>
>> Unified Access Model for Continued Access to Full WHOIS Data – For<br>
>> Discussion<br>
>><br>
>><br>
>> I am the penholder on this comment. Please reply to this email if your<br>
>> are interested in commenting. Thanks!<br>
>><br>
>><br>
>> Greg<br>
>><br>
>> --<br>
>> Greg Shatan<br>
>> <a href="mailto:greg@isoc-ny.org" target="_blank">greg@isoc-ny.org</a><br>
>><br>
>><br>
>> "The Internet is for everyone"<br>
>> _______________________________________________<br>
>> CPWG mailing list<br>
>> <a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
>> <a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
><br>
><br>
> _______________________________________________<br>
> CPWG mailing list<br>
> <a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
> _______________________________________________<br>
> registration-issues-wg mailing list<br>
> <a href="mailto:registration-issues-wg@atlarge-lists.icann.org" target="_blank">registration-issues-wg@atlarge-lists.icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/registration-issues-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/registration-issues-wg</a><br>
><br>
<br>
<br>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
_______________________________________________<br>
registration-issues-wg mailing list<br>
<a href="mailto:registration-issues-wg@atlarge-lists.icann.org" target="_blank">registration-issues-wg@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/registration-issues-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/registration-issues-wg</a><br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Greg Shatan<div><a href="mailto:greg@isoc-ny.org" target="_blank">greg@isoc-ny.org</a></div><div><br></div><div>"The Internet is for everyone"</div></div></div>