January 2017 - Gnso-impl-thickwhois-rt

Thick Whois Implementation to be published on 1 February 2017
by Dennis Chang Feb. 1, 2017

Feb. 1, 2017

Dear Thick Whois IRT, As planned, we will be publishing the Implementation for the CL&D and Transition Policies on 1 February 2017. This is the scheduled date that was established more than 6 months ago. Thank you again for all of your support throughout the process in achieving this important milestone. When you see the policies published on the Consensus Policy webpage: https://www.icann.org/resources/pages/registrars/consensus-policies-en, you will note that the color issue that Marc pointed out does not appear. It turns out that all display factors including colors are taken care of by our webpage processing. On the Transition policy, you’ll note that we’ve added Background information as we have in the CL&D Policy. Also, for clarity we added the word “Policy” to the title of section 1.0 – making it clear this section contains the Policy and Effective Dates. The next IRT Meeting is scheduled for 14 February and I’ll send out an agenda this week. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

3 3

Thick Whois Policies - Final versions
by Dennis Chang Jan. 24, 2017

Jan. 24, 2017

Dear Thick IRT, Per your request from the IRT meeting today, I am providing you with clean copies of the policy documents we will be publishing. Thank you again for your continued support in achieving this important milestone. I know that It took many years for many of you to get here and we have another two years to go for completion of this project. The three key milestones we’ll focus going forward are: 1 August 2017 for CL&D 1 May 2018 for New Registration for Thick 1 February 2019 for Transition of Existing Domain Names No doubt, we’ll discover and learn as we implement these policies. I look to your guidance and support for successful implementation of these important policies. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

1 0

Thick Whois Policy Language revisions from the IRT meeting on 17 January 2017
by Dennis Chang Jan. 24, 2017

Jan. 24, 2017

Dear Thick IRT, Thank you for your participation and support today in reviewing the public comment and decisions made to handle them. As promised, we’ve revised the policy language per our discussion at the meeting. For CL&D Policy: 1. The “not to be deployed before date” was removed per the suggestion. For this policy, this is the only change. 2. No change was made for the suggestion to add a “provision for extension to the effective date” as the IRT agreed For Transition Policy: 1. The clause containing “RDAP” was removed from section 2.10. The resulting language is exactly as Francisco provided in the chat which IRT agreed to. 2. Section 2.4 had two changes per the suggestions and agreements by the IRT a. The word “starting” was changed to “by” to offer flexibility for the Registry Operator to provide support earlier. b. <contact:polstalinfo> was changed to <contact:postalinfo type> to identify the attribute more accurately 3. Changes to section 2.8 and 2.9 were made to make it more readable. IRT was already in agreement with the intent of the language and this change was only to make it easier to understand. 4. Regarding the suggestion to add “Alternative triggers for waivers,” there was no IRT agreement to make the change and therefore no change was made. This is considered the final review by the IRT before the publication and the announcement on 1 February 2017 per our plan. One more IRT meeting has been added for next Tuesday as you’ve requested. However, it can be cancelled if the IRT provides support for these finalized languages to be in alignment with the Policy Recommendation prior to the meeting date. We look forward to your prompt review and continued support. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&…> "One World, One Internet"

4 4

Additional triggers and privacy law
by theo geurts Jan. 22, 2017

Jan. 22, 2017

Hello all, I am not in favor in creating a "trigger" based on the data retention waiver. First of all, that process was horrible and costly, and I can only conclude that there still Registrars out there that started in 2013, still not have obtained a waiver in 2017. We as an IRT concluded that it is up to the Registrars own due diligence to determine if there is an issue with privacy laws. The rationale behind that is/was simple: 2011, 76 countries having data privacy laws. 2016, 109 countries having privacy laws. 2017, 35 more countries are currently drafting privacy laws. As mentioned before this is a moving target and not up to us to address. That being said, the current solution when it comes to the migration and issues with privacy law is not a solution. I appreciate the fact that Verisign noted it during the comment period, but as several Registrars has mentioned in the past, it is not a good solution. After the latest GNSO meeting I hoped to see some progress on the WHOIS IAG matter, but frankly, with the current speed, I am afraid that the WHOIS IAG will be overtaken by stationary objects. That either means there is a problem or there is not, and I would like to get some input from the IRT on it. If there is no problem, please provide me with some info on why it is not an issue. If it is an issue then how do we address it? We can't tell Registrars you must migrate WHOIS data before X date and if there is a problem then just break the law. We also cannot create a situation that if a Registrar can not migrate the data, run into compliance issues that might end up in de-accreditation of that Registrar, I think we all agree that is just plain silly and the wrong message. My solution here would be, and it is not great, to be honest, that until the matter can be resolved the Registry operator supports both thin and thick whois registrations and shall carry the burden for both systems. The Registrar might also carry a burden here. As they might come into a situation, they are forced to implement RDAP at some point as the rest of the world moves to RDAP. I already see ccTLDs Registries announce RDAP, go figure ;) Would the above solve the issue? And yes I am aware that the above language cannot be added to the draft in its current state, but I am sure staff can come up with something workable here. If the whole idea is plain silly, feel free to kick me under the table here. Theo

2 1

Thick Whois IRT letter to GNSO Council: Notification of the Emerging Privacy Issues
by Dennis Chang Jan. 19, 2017

Jan. 19, 2017

Dear Amr - GNOS Council Liaison for the Thick Whois IRT Thank you for standing by and supporting the IRT throughout this process. There is no further comment from the IRT on the final draft and therefore, the attached letter is now ready for submission to the GNSO Council. Please accept the attached letter of notification from the Thick Whois IRT regarding the emerging privacy issues. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

6 10

Re: [Gnso-impl-thickwhois-rt] [Ext] RE: Thick Whois IRT meeting agenda for 17 January 2017 meeting
by Dennis Chang Jan. 17, 2017

Jan. 17, 2017

Both will be discussed today. I’ll see you in AC room in 30 minutes. Please be sure to join us. Thanks Dennis Chang From: "Metalitz, Steven" <met(a)msk.com> Date: Tuesday, January 17, 2017 at 10:29 AM To: Dennis Chang <dennis.chang(a)icann.org>, "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: [Ext] RE: [Gnso-impl-thickwhois-rt] Thick Whois IRT meeting agenda for 17 January 2017 meeting A couple of questions for staff: The report of public comments (https://www.icann.org/public-comments/rdds-labeling-display-2016-10-21-en#s…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>) on the CL&D policy includes in the analysis section two topics on which it is stated “ICANN organization will discuss the suggestion with the Implementation Review Team.” Does staff have any recommendation on whether these changes should be made? When will the report of public comments on the transition to thick Whois for com/net/jobs be published? Will this topic be discussed and decided on today’s call, or only CL&D? I note that only three substantive comments were received on this. https://forum.icann.org/lists/comments-whois-transition-26oct16/[forum.ican…<https://urldefense.proofpoint.com/v2/url?u=https-3A__forum.icann.org_lists_…> Thanks. Steve Metalitz [mage001] Steven J. Metalitz | Partner, through his professional corporation T: 202.355.7902 | met(a)msk.com<mailto:met@msk.com> Mitchell Silberberg & Knupp LLP | www.msk.com[msk.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.msk.com_&d=DwMGaQ&c…> 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-impl-thickwhois-rt-bounces(a)icann.org [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Dennis Chang Sent: Wednesday, January 11, 2017 9:40 PM To: gnso-impl-thickwhois-rt(a)icann.org Subject: [Gnso-impl-thickwhois-rt] Thick Whois IRT meeting agenda for 17 January 2017 meeting Dear Thick Whois IRT, The agenda for our next meeting on 17 January 2017 has been posted on the IRT wiki space and provided below for your convenience. The meeting should already be on your calendar as Michelle sent out invites at the end of last year. Please be sure to join us as we’ll be review the public comments received and discuss potential impact to the project schedule. 17 January 2017 ________________________________ * Agenda: * Project Status * Public Comment Review * Policy language revision review * Next step — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&…> "One World, One Internet"

1 0

Thick Whois IRT meeting agenda for 17 January 2017 meeting
by Dennis Chang Jan. 17, 2017

Jan. 17, 2017

Dear Thick Whois IRT, The agenda for our next meeting on 17 January 2017 has been posted on the IRT wiki space and provided below for your convenience. The meeting should already be on your calendar as Michelle sent out invites at the end of last year. Please be sure to join us as we’ll be review the public comments received and discuss potential impact to the project schedule. 17 January 2017 ________________________________ * Agenda: * Project Status * Public Comment Review * Policy language revision review * Next step — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

2 1