[Gnso-rds-pdp-2] ICANN61 Prep Assignment - Domain Name Control and Individual Internet Use

[Deacon, Alex]

Hi DT2 Team,

I’ve attempted to kick start the answers to our questions.  Please see attached v.02 version with a quick and dirty first shot at it.   As I was not a member of the original DT I’m sure I have missed important nuance here so look for you to make updates/corrections/additions.  Thanks so much!

Alex



From: "Deacon, Alex" <Alex_Deacon at mpaa.org>
Date: Wednesday, February 28, 2018 at 1:07 PM
To: "gnso-rds-pdp-2 at icann.org" <gnso-rds-pdp-2 at icann.org>
Subject: ICANN61 Prep Assignment - Domain Name Control and Individual Internet Use


Drafting Team 2,

As those who were on the RDS WG call on Tuesday heard, we have decided to take a week to prep for ICANN61 by working on a specific assignment in drafting team mode.

Our team’s assignment is to reexamine our past output on Domain Name Control and Individual Internet Use.  As a reminder the final output of your team can be reviewed at

https://community.icann.org/download/attachments/74580010/RDS%20WG%20DT2%20Draft%20edits%201113.pdf

We have now been asked to answer the following questions more explicitly and conceptually:
1.      Who associated with the domain name registration needs to be identified and/or contacted for each purpose?
2.      What is the objective achieved by identifying and/or contacting each of those entities?
3.      What might be expected of that entity with regard to the domain name?

To prep for ICANN61, it is imperative that we discuss these questions and produce output over the next week – ideally by 5 March but no later than 7 March.

We know this is a tall order, give a short timeframe. However, the leadership believes that this will help us use our F2F time at ICANN61 more effectively, which I hope we all agree would be a terrific idea.

I’ve attached a template for us to use in answering these questions.   I hope to propose some answer to these questions later today but given the time crunch I wanted to send this email (and the template) to the team sooner rather than later.

To learn more about this assignment, please read these instructions:
https://community.icann.org/download/attachments/79432608/Drafting%20Team%20Assignment%2026%20Feb.pdf<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.icann.org%2Fdownload%2Fattachments%2F79432608%2FDrafting%2520Team%2520Assignment%252026%2520Feb.pdf&data=02%7C01%7Calex_deacon%40mpaa.org%7C403c5194d9b24cdbce8108d57e1ac039%7C17e50b56d5dd439b962acc7ecd9ab7fe%7C0%7C1%7C636553575726608430&sdata=rbXIwELATuc9kmt%2BWjCKSPgwJqivfp64RfN%2BSGy3FQ8%3D&reserved=0>

If you were unable to attend today’s WG call, please catch up by reading or listening to the call recording/notes/transcript:
https://community.icann.org/x/oAu8B<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.icann.org%2Fx%2FoAu8B&data=02%7C01%7Calex_deacon%40mpaa.org%7C403c5194d9b24cdbce8108d57e1ac039%7C17e50b56d5dd439b962acc7ecd9ab7fe%7C0%7C0%7C636553575726608430&sdata=B%2Bbb3x73oTSnnvxRoTfSPhQmtvvit%2FvJr2uEqFMQIMQ%3D&reserved=0>

To get started, please ask any questions you may have about this assignment within the next 24 hours.

If you have any suggested edits or additions or deletions to the attached first draft, even better!  I encourage you to share them in reply to this message, copying the DT mailing list gnso-rds-pdp-2 at icann.org<mailto:gnso-rds-pdp-2 at icann.org>

Thanks for doing what you can to help this drafting team come through on this new assignment.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-2/attachments/20180301/2c7c747e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RDS WG DT2 ICANN61 - v.02.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 30664 bytes
Desc: RDS WG DT2 ICANN61 - v.02.docx
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-2/attachments/20180301/2c7c747e/RDSWGDT2ICANN61-v.02-0001.docx>