Thanks for letting us know. Best regards, Marika From: Richard Leaning <rleaning@ripe.net> Date: Friday, March 2, 2018 at 23:43 To: "Anderson, Marc" <mcanderson@verisign.com> Cc: Marika Konings <marika.konings@icann.org>, "gnso-rds-pdp-7@icann.org" <gnso-rds-pdp-7@icann.org> Subject: [Ext] Re: [Gnso-rds-pdp-7] ICANN61 Prep Assignment Hi Marika Sorry about the late reply. I have just arrived back from a week at APRICOT/APNIC meeting and I have just seen this while catching up on my emails. Like Rod, am away next week at another conference and will not have the time to give this a proper look, I won’t be at the f2f as I don’t arrive in PR until Sunday night. Kind Regards Dick Richard Leaning External Relations RIPE NCC On 2 Mar 2018, at 21:53, Anderson, Marc via Gnso-rds-pdp-7 <gnso-rds-pdp-7@icann.org<mailto:gnso-rds-pdp-7@icann.org>> wrote: Marika, thanks for the recap of the assignment. I’ve been swamped as I’m sure the rest of you are, but I wanted to send out a few thoughts before we get into the weekend to try and kick start the conversation. Based on our discussions last time I’d say the answers to these questions depend on the use case. We identified a number of use cases but I think for these questions they can probably be divided between two categories. 1) RDS data used to notify a victim and 2) RDS data used to identify/prosecute a criminal. I know this is over simplifying things and ignores the gray area in between where (especially initially) it might not be know if the domain registrant is the victim or the abuser, but given the short time frame until ICANN 61, it might be helpful to frame our answers around those two scenarios. Any thoughts… does that sound reasonable? I’ll take a first pass at some answers for the victim notification use case (mostly because I think those will be easier to answer ☺ ). 1. Who associated with the domain name registration needs to be identified and/or contacted for each purpose? With traditional Whois data fields I would answer this by saying the Registrant, Admin and Technical contact. As I’m a proponent of trying not to think in terms of the legacy data fields (and like the roles based approach suggested by the EWG) I’d answer with the domain name owner and the admin, tech and abuse roles for the domain. Here I think “contact-ability” is key and so what’s important for this use case if having accurate and up to date information about how to contact someone with authority for the domain name is what is needed. 1. What is the objective achieved by identifying and/or contacting each of those entities? The objective seems to be basically stated in the use case: notify the domain name owner and/or someone with authority for the domain name of abuse associated with the domain name registration. 1. What might be expected of that entity with regard to the domain name? Here I think the expected action is for the domain name owner or person with authority for the domain name to take action to correct the abuse associated with the domain name. Hopefully I’m on the right track and that gets us started. Thanks, Marc From: Gnso-rds-pdp-7 <gnso-rds-pdp-7-bounces@icann.org<mailto:gnso-rds-pdp-7-bounces@icann.org>> on behalf of Marika Konings <marika.konings@icann.org<mailto:marika.konings@icann.org>> Date: Tuesday, February 27, 2018 at 14:27 To: "gnso-rds-pdp-7@icann.org<mailto:gnso-rds-pdp-7@icann.org>" <gnso-rds-pdp-7@icann.org<mailto:gnso-rds-pdp-7@icann.org>> Subject: [Gnso-rds-pdp-7] ICANN61 Prep Assignment Dear Drafting Team 7, As those who were on today’s call 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 Criminal Activity/ DNS Abuse Mitigation: https://community.icann.org/download/attachments/74580010/DraftingTeam7-CrimInvAbuseMit-10%20Nov%202017%20clean.pdf?version=1&modificationDate=1510442602000&api=v2[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_74580010_DraftingTeam7-2DCrimInvAbuseMit-2D10-2520Nov-25202017-2520clean.pdf-3Fversion-3D1-26modificationDate-3D1510442602000-26api-3Dv2&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=4XkuN0mI8lTURiGQhW61dB8Vl4vtLI1ZFsKnn77Gv18&s=P8rM4hLqr7CS87KoJZq7AHSCqbGvboArUB9zm0d6TQY&e=> 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. To give us a head start, attached please find a first draft at answers, prepared by me from our past output, and raising a few potential gaps for discussion. To learn more about this assignment, please read these instructions: https://community.icann.org/download/attachments/79432608/Drafting%20Team%20Assignment%2026%20Feb.pdf[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_79432608_Drafting-2520Team-2520Assignment-252026-2520Feb.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=4XkuN0mI8lTURiGQhW61dB8Vl4vtLI1ZFsKnn77Gv18&s=0M9FjdGCKYUICHHdvnDVObkL7VYFH5L8ABeW0AnTyQU&e=>. 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[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_oAu8B&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=4XkuN0mI8lTURiGQhW61dB8Vl4vtLI1ZFsKnn77Gv18&s=rMb4cxPSpNtURSGjcj3vI4Dbo4PfNWmSnYr5r9PRNH4&e=>. 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-7@icann.org<mailto:gnso-rds-pdp-7@icann.org>. Thanks for doing what you can to help this drafting team come through on this new assignment. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings@icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses[learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_...> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gns...>. _______________________________________________ Gnso-rds-pdp-7 mailing list Gnso-rds-pdp-7@icann.org<mailto:Gnso-rds-pdp-7@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-7