February 2016 - Gnso-impl-thickwhois-rt

Reminder - Due Wed. 24 Feb. COB - Transition - Input on Implementation Timeline for New Registrations
by Fabien Betremieux Feb. 25, 2016

Feb. 25, 2016

Dear IRT Members, We would like to remind you of the request below. Your input would be very much appreciated before close of business on Wednesday 24 February. Thank you in advance for your attention -- Fabien Betremieux Sr. Registry Services & Engagement Manager Global Domains Division, ICANN From: Fabien Betremieux <fabien.betremieux(a)icann.org> Date: Wednesday, February 17, 2016 at 11:19 PM To: "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: Transition - Input on Implementation Timeline for New Registrations Dear IRT Members, In our last IRT meeting on 11 February the following set of milestones was proposed for the implementation of the transition from thin to thick of new registrations in .COM, .NET and .JOBS: * Finalization of Thick WhoIs Policy * Registries to make system changes * Registrar notification of changes * Introduction of optional thick (contact support) in OT&E * Introduction of optional thick (contact support) in Production * Registrar notification/transition period * Cutover to required thick (contacts) for new registrations in OT&E * Cutover to required thick (contacts) for new registrations in Production It was further agreed that affected parties participating in the IRT would share their requirements in terms of notification periods and duration for each of these phases. With a view to reaching an agreement on an implementation timeline for the existing registration track during our next IRT meeting (currently being planned during the ICANN 55 meeting from 5 to 10 March), we would like to request you provide your input as soon as possible, and at the latest by Wednesday 24 February COB. This would allow for discussion of contributions on the mailing list prior to the meeting. In the meantime, please share on this list any questions you may have in relation to the above milestones. Thank you in advance for your collaboration Best Regards -- Fabien Betremieux Sr. Registry Services & Engagement Manager Global Domains Division, ICANN

5 4

Update to Data Analysis Scoping Paper - Existing Registrations - Please Review by 24 Feb.
by Fabien Betremieux Feb. 23, 2016

Feb. 23, 2016

Dear IRT Members, Following our meeting on 11 February 2016 during which we discussed your feedback on the initial Draft Scoping Paper for conducting Data Analysis on existing registrations in .COM, .NET and .JOBS, we would like to submit the updated paper for your review (clean and redline versions attached). We have made the following edits to the paper: * Section ³Thick Whois Data Requirements² now reflects our discussion of the need to consider both systems and contractual requirements * Contact Validation Rules for .COM and .NET, previously shared with the IRT, have been inserted as Appendix 1 * Contact Validation Rules for .JOBS, which were provided by the Registry Operator for this update, are inserted as Appendix 2 * Several clarifications of the language were made throughout the document. As we would like to share this paper to the RrSG Executive Committee this week, for discussion during ICANN 55, we would like to request you please review and provide your comments, if any, by this Wednesday 24 February 2016 COB in your timezone. Thank you in advance for your consideration Best Regards -- Fabien Betremieux Sr. Registry Services & Engagement Manager Global Domains Division, ICANN

2 1

Transition - Input on Implementation Timeline for New Registrations
by Fabien Betremieux Feb. 17, 2016

Feb. 17, 2016

Dear IRT Members, In our last IRT meeting on 11 February the following set of milestones was proposed for the implementation of the transition from thin to thick of new registrations in .COM, .NET and .JOBS: * Finalization of Thick WhoIs Policy * Registries to make system changes * Registrar notification of changes * Introduction of optional thick (contact support) in OT&E * Introduction of optional thick (contact support) in Production * Registrar notification/transition period * Cutover to required thick (contacts) for new registrations in OT&E * Cutover to required thick (contacts) for new registrations in Production It was further agreed that affected parties participating in the IRT would share their requirements in terms of notification periods and duration for each of these phases. With a view to reaching an agreement on an implementation timeline for the existing registration track during our next IRT meeting (currently being planned during the ICANN 55 meeting from 5 to 10 March), we would like to request you provide your input as soon as possible, and at the latest by Wednesday 24 February COB. This would allow for discussion of contributions on the mailing list prior to the meeting. In the meantime, please share on this list any questions you may have in relation to the above milestones. Thank you in advance for your collaboration Best Regards -- Fabien Betremieux Sr. Registry Services & Engagement Manager Global Domains Division, ICANN

1 0

Meeting Recording and Transcripts Available
by Aysegul Tekce Feb. 16, 2016

Feb. 16, 2016

Dear Colleagues, The recording, chat transcript and meeting transcript from our last meeting (Thursday 11 February 2016) are now available on the IRT Meeting's workspace: https://community.icann.org/display/TWCPI/IRT+Meetings Thank you for your attention. Aysegul Tekce Registry Services & Engagement Manager ICANN – Internet Corporation for Assigned Names and Numbers Istanbul, Turkey T: +90 212 999 6227

1 0

Thick WhoIs IRT - contact validation rules
by Anderson, Marc Feb. 13, 2016

Feb. 13, 2016

Dear IRT Members, At the last IRT meeting we discussed that in order for Registrars to properly assess the amount of work involved in the backfill of thick data for existing Registrations, it is necessary to know the fields required and their validation rules. Along with providing that information, I want to make sure everyone has the same understanding of the difference between a thin Registry and a thick Registry. A thin domain registration does not have any contacts associated with it. Currently, a Registrar cannot even create contacts for the .com or .net Registry. As part of a transition to thick, the com/net registry would start supporting contacts by allowing Registrars to add, modify and delete contacts. A thick domain registration MUST have a contact ID for each contact type (Registrant, Admin, Technical and Billing). The same contact can be re-used across domains and/or contact types. For example, if a Registrant were to register two domains in a thick gTLD via the same Registrar, that Registrar could create one contact and associate that with both domain registrations or could create two separate contacts, one for each domain. Either is fine, but I'm calling it out because it will have an impact on the effort required by Registrars to backfill thick data for existing registrations. There are no other differences between a thin and a thick registration. I recognize that the Billing contact is not universally required by all thick Registries. Some (including Verisign) require it; some allow it as an optional field and some don't allow it at all. I don't believe this was addressed by the Thick WhoIs PDP working group so it may be worth consideration by the IRT. Attached please find a document containing the contact validation rules that Verisign would implement to assist Registrars in assessing impacts. Thank you, Marc Anderson Marc Anderson Product Manager mcanderson(a)verisign.com<mailto:mcanderson@verisign.com> m: 571.521.9943 t: 703.948.3404 12061 Bluemont Way, Reston, VA 20190 VerisignInc.com<http://www.verisigninc.com/> [Verisign(tm)]

6 8

Please Review by 29 Jan. - Data Analysis Scoping Paper - Existing Registrations
by Fabien Betremieux Feb. 10, 2016

Feb. 10, 2016

Dear IRT Members, In our meeting on 13 January 2016, we further discussed need to conduct data analysis to better understand the type of challenges we may face when transitioning existing registrations in .COM, .NET and .JOBS from thin to thick Whois. It was agreed among IRT participants that we should reach out to the Registrar Stakeholder Group (RrSG) and assemble a team of volunteers to conduct such analysis. We would like to confirm that this topic will be on the agenda of the RrSG meeting in Marrakech during ICANN 55. We will provide more details when available. Additionally, as discussed during our IRT meeting, we have drafted a scoping paper for this analysis (attached). We are targeting to forward this paper to the RrSG on Monday 1 February. In the meantime, we would like to request you review this paper and share your edits by this Friday 29 January COB in your time zone. Please note that the scoping paper needs your input in the following sections: * Scope of analysis * Thick Whois Data Requirements * Next Steps and Expected Timeline Thank you in advance for your time. Best Regards -- Fabien Betremieux Sr. Registry Services & Engagement Manager Global Domains Division, ICANN

3 4

Reminder - Next IRT Meeting - Thur. 11 Feb 2016 19:00 UTC
by Aysegul Tekce Feb. 3, 2016

Feb. 3, 2016

Dear IRT Members, Based on your input in the doodle pool, our next meeting will be held on Thursday 11 February 2016 at 19.00 UTC (for other time zones: http://tinyurl.com/twirt-11feb16) The proposed agenda for our call is the following: Transition from thin to thick – Existing Registrations Track Discussion of feedback on Draft Data Analysis Scoping Paper Discussion of Contact Validation Rules document (as needed) Finalizing our Draft Data Analysis Scoping Paper for sharing with Registrars in advance of the ICANN 55 meeting Transition from thin to thick – New Registrations Track Discussion of implementation timeline Thank you in advance for your participation, Kind Regards, Aysegul Tekce Registry Services & Engagement Manager ICANN – Internet Corporation for Assigned Names and Numbers Istanbul, Turkey T: +90 212 999 6227

1 0

Next IRT meeting - Doodle Poll - Due 2 Feb 21:00 UTC
by Fabien Betremieux Feb. 1, 2016

Feb. 1, 2016

Dear IRT Members, In order to provide more time for review as well as a forum for discussing the recent documents shared on the IRT mailing list (Draft Data Analysis Scoping Paper by ICANN Staff and Contact Validation Rules for .COM and .NET by Verisign) we suggest holding an IRT meeting for interested parties this week or next week depending on availability. Please fill in your availability in the following doodle poll, ideally by Tuesday 2 February 21:00 UTC (12:00 PST, 15:00 EST): http://doodle.com/poll/wcd3ky53ues447nv (please make sure the poll display your timezone appropriately, top left of time options) The objective of our call would be to: * Discuss feedback on Draft Data Analysis Scoping Paper * Discuss the Contact Validation Rules document * Finalize our Draft Data Analysis Scoping Paper for sharing with Registrars in advance of the ICANN 55 meeting Thank you in advance for your time Best Regards -- Fabien Betremieux Sr. Registry Services & Engagement Manager Global Domains Division, ICANN

1 0