[gnso-rds-pdp-wg] DT6 Final Deliverable

[consult at cgomes.com]

Please review the attached final deliverable from RDS Drafting Team 6 about
proposed RDS purpose 'Legal Actions' before the upcoming RDS PDP WG meeting
on Saturday, 28 October and identify any questions you may have so that they
can be discussed in that meeting.  Remember that the goal in this exercise
is to try to make sure that all WG members understand this proposed purpose
before we start debating whether it is a legitimate purpose for collecting
and displaying RDS data.

 

Drafting Team 6 (DT6) was tasked with answering the following questions
relating to the use of RDS in connection with "legal actions":

1.	Who are the parties that request WHOIS data today for legal action
purpose?
2.	What role does gTLD registration data play for legal action purpose?
3.	Why is access to Whois data needed to fulfill legal action purpose?
4.	What is a proposed definition for the legal action purpose?

In order to answer these questions, DT6 identified the tasks, parties, and
specific RDS data typically associated with the use of RDS in connection
with legal actions, and attempted to summarize the "legal actions" purpose
succinctly in one paragraph in the template requested by the RDS leadership
team.  We note that there may be some overlap with other identified RDS
purposes, such as regulatory and contractual enforcement, or criminal
investigation and DNS abuse mitigation.

 

Staff - Please post this on the WG wiki.

 

Chuck

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20171026/e44f8550/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RDS WG DT6 Draft - Revised 10.26.2017 v3.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 27247 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20171026/e44f8550/RDSWGDT6Draft-Revised10.26.2017v3-0001.docx>