Per action item 4 of Lisa's notes, attached (and pasted below) please find a draft of the purpose definition paragraph as called for in our template. I have italicized the second sentence because it may not be needed, strictly speaking --- all of these "who's" can be found in the use cases referenced in the third sentence --- but because "a variety of entities" may seem too vague we might wish to list them here. Steve Metalitz DRAFT 10/23/17 A variety of entities from both the public sector (apart from traditional law enforcement agencies) and the private sector have a remit to enforce obligations, arising under contracts, industry best practices, or governmental regulation, that relate to activities on the Internet. These entities include governmental tax authorities, UDRP providers, the ICANN organization, intellectual property owners, and merchant account monitoring solution providers, among others. The use cases presented below, as well as those identified by the EWG (see https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf <https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf%20%2...> , pages 9, 24, 28) and in earlier proceedings of this WG (see https://community.icann.org/download/attachments/60493753/14-WHOIS%20queries...) , illustrate scenarios in which such enforcement efforts, and/or the necessary investigative steps preliminary to such enforcement, depend upon access to information relating to the identity and/or location of domain name registrants, or other data contained in the RDS. This purpose makes it possible for these public and private enforcement entities to identify (and in many cases contact) domain name registrants to resolve issues associated with compliance with these contracts, best practices, or regulations. [image001] Steven J. Metalitz | Partner, through his professional corporation T: 202.355.7902 | met@msk.com<mailto:met@msk.com> Mitchell Silberberg & Knupp LLP | www.msk.com<http://www.msk.com/> 1818 N Street NW, 8th Floor, Washington, DC 20036 THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS. THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION, FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM YOUR SYSTEM. THANK YOU. From: gnso-rds-pdp-5-bounces@icann.org [mailto:gnso-rds-pdp-5-bounces@icann.org] On Behalf Of Lisa Phifer Sent: Monday, October 23, 2017 8:58 AM To: gnso-rds-pdp-5@icann.org Subject: [Gnso-rds-pdp-5] Notes and Action Items from 23 October call Notes and Action Items from Drafting Team #5 Call - 23 October 1. Roll call * Attendees: Krishna Seeburn, Theo Geurts, Elizabeth Bacon, Steve Metalitz, Farell Folly, Bastiaan Goslings * Apologies: Bastiaan Goslings 2. Review, discuss and confirm support and understanding of all input to date on i, ii, & iii. * Kris has additions to page 1, item i: Apart from the IP this is also used to identify the identity of the holders of domain names as a first level review. This can come from individuals or small companies equally * Do pages 2-3 overlap with anti-abuse purpose? * Action: Beth to share pages 2-3 with DT7 (Marika) and to suggest revisions to pages 2-3 to focus more on use in reg/contract enforcement, but mid-day Tuesday * No concerns expressed to page 1, item ii * Volunteer to add data elements (page 1, item iii) * Action: Steve Metalitz, to add today - done, see below: * Additional text for iii) is given here: "Data tending to establish the identity and/or location of domain name registrant. For example, Registrant name and at least province/country address could be relevant here." * Comments on I,II,II on page 1 - text to be integrated into i,ii,iii on the same page 3. Identify a volunteer to consolidate input into one coherent document, populating Word template * Action: Beth Bacon, by Tuesday mid-day * Action: Chuck to apply any final edits suggested on-list Wednesday 4. Identify a volunteer to draft a brief one paragraph definition of the purpose Definition: Describe the purpose succinctly in one paragraph, identifying who, what, and why * Action: Steve draft definition, send to DT5 list by mid-day Tuesday 5. Timeline a. Items 3 & 4 (new text from Beth and Steve) - not later than midday Tuesday b. List discussion & input on items 3 & 4 - midday Tuesday to midday Wednesday c. Confirm support & understanding - Wednesday afternoon * Action: All DT5 members to review entire draft, including new text to be supplied by Steve and Beth, and comment to list as to whether it's understandable. Google docs link: https://docs.google.com/document/d/1NvoYYmMsjqgt48mAYt5nCr8uPk-E-2IngGt50wDkaFU/edit<https://docs.google.com/document/d/1NvoYYmMsjqgt48mAYt5nCr8uPk-E-2IngGt50wDkaFU/edit> d. Cancel Thursday call if not needed - Wednesday evening * Action: GNSO-secs to schedule Thursday call, cancelled if everyone expresses understanding Wednesday on the consolidated draft e. Team to present output at ICANN60 in Abu Dhabi - those who will be present in person are Beth, Kris (also attending conflicting ALAC session), Chuck, Theo (may have conflicting NomCom session) * Action: Kris prepare to give intro of team's output in-person, with back up from Beth, and help answer any questions about this purpose from full WG