<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I think that Case 19 ("WHOIS misused to shame, anger or scare a registrant") suggests a potential gap or at least a counter-case ("WHOIS used to find those posting personally identifiable information to shame, anger or scare a registrant"'). As Case 19 posits, this involves posting information on the Internet. In many cases, the information is posted on websites using domains registered for such purpose, or sent using email addresses using domains registered for that purpose. WHOIS data is an important and much-used tool in determining the identity of those disseminating the PII under those circumstances.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I have personal experience with this. When my client was the victim of a doxing attack (and this involved publishing confidential documents, not merely publicly available contact information), WHOIS data was critical in tracking down the identity of the individuals responsible. There was much more to it, but the WHOIS data was the first lead in the chain. Without that data, the results may have been quite different.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default"><font face="verdana, sans-serif">Rather than drafting a whole new use case, I think that this use case is similar enough to existing use cases 06, 09, 21 and 22 to point to those cases for more detail. I would point in particular to use case 21's statement that "telltales
may be found in resources used to register the domain" which in turn lead to other information necessary to move forward. "Telltales" may also be found in information that is not completely accurate. This point should not be lost -- WHOIS records can reveal telltales and "breadcrumbs" even when the information is not a bald-faced registration in the name of the "miscreant" (as use case 22) put its.</font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Of course, if it's deemed necessary, I can create a separate use case for this.</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><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 12, 2016 at 2:18 PM, Lisa Phifer <span dir="ltr"><<a href="mailto:lisa@corecom.com" target="_blank">lisa@corecom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Dear all,<br><br>
To address the following action item:<br><br>
<b><i>Action item</i></b>: WG members to review example use cases and
identify any gaps that should be filled - preferably volunteering to
draft and present them<br><br>
Example use cases identified by this WG to date are listed below and
can be found here:
<a href="https://community.icann.org/x/JA6bAw" target="_blank">
https://community.icann.org/x/<wbr>JA6bAw</a><br><br>
<img src="cid:6.2.3.4.2.20160812114757.10229f00@mail.corecom.com.0" width="649" height="611" alt="Emacs!">
<br><br>
In addition, cases originally drafted by the EWG are listed here: <br>
<a href="https://community.icann.org/download/attachments/60490860/EWG%20Report%20-%20Use%20Case%20and%20Data%20Annexes.doc?version=1&modificationDate=1468862831000&api=v2" target="_blank">
EWG Report - Example Use Case and Related Data Annexes.doc</a><br>
Contact staff if you would like to a copy of any EWG draft use
case.<br><br>
As we are trying to examine a representative but not exhaustive set of
examples prior to deliberation (see
<a href="https://community.icann.org/x/JA6bAw" target="_blank">https://community.icann.org/x/<wbr>JA6bAw</a>), if you believe that a different
and important example is missing from the above table, please raise that
gap to the WG's attention.<br><br>
Best regards,<br>
Lisa<br>
</div>
<br>______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br></blockquote></div><br></div>