[gnso-rds-pdp-wg] Action item - gap assessment

[Greg Shatan]

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.

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.

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.

Of course, if it's deemed necessary, I can create a separate use case for
this.

Greg

On Fri, Aug 12, 2016 at 2:18 PM, Lisa Phifer <lisa at corecom.com> wrote:

> Dear all,
>
> To address the following action item:
>
> *Action item*: WG members to review example use cases and identify any
> gaps that should be filled - preferably volunteering to draft and present
> them
>
> Example use cases identified by this WG to date are listed below and can
> be found here: https://community.icann.org/x/JA6bAw
>
> [image: Emacs!]
>
> In addition, cases originally drafted by the EWG are listed here:
> EWG Report - Example Use Case and Related Data Annexes.doc
> <https://community.icann.org/download/attachments/60490860/EWG%20Report%20-%20Use%20Case%20and%20Data%20Annexes.doc?version=1&modificationDate=1468862831000&api=v2>
> Contact staff if you would like to a copy of any EWG draft use case.
>
> As we are trying to examine a representative but not exhaustive set of
> examples prior to deliberation (see https://community.icann.org/x/JA6bAw),
> if you believe that a different and important example is missing from the
> above table, please raise that gap to the WG's attention.
>
> Best regards,
> Lisa
>
>
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160816/efcbde55/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7112244.jpg
Type: image/jpeg
Size: 303051 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160816/efcbde55/7112244.jpg>