FYI... the post I made on this topic back in July. Thank you, Marc From: gnso-impl-thickwhois-rt-bounces@icann.org [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Anderson, Marc Sent: Friday, July 15, 2016 9:09 AM To: gnso-impl-thickwhois-rt@icann.org Subject: Re: [Gnso-impl-thickwhois-rt] Reminder: For IRT Review - Consistent Labeling & Display - Revised Policy Language Dear IRT members, Thank you for the opportunity to review and provide feedback on the latest draft of the Registry Registration Data Directory Services Consistent Labeling and Display Policy. Verisign is supportive of the proposed changes to the Policy clarifying that the Registrar Registration Expiration Date and Reseller fields are optional. Verisign is also generally supportive of coordinating the RDAP implementation with the Thick Whois implementation; however, it does not support including requirement number 12 in the Policy which states that the "implementation of an RDAP service in accordance with the 'RDAP Operational Profile for gTLD Registries and Registrars' is required for all gTLD registries in order to achieve consistent labeling and display ". As previously noted by Verisign and others within the ICANN community, the requirement to implement the RDAP Operational Profile developed by ICANN staff is premature, as the RDAP Operational Profile has not yet been completed and is technically and functionally incomplete (see 09 February 2016 RySG comments). As has also been previously noted by Verisign and others within the ICANN community, numerous constituencies and cross constituency groups within ICANN and the IETF have worked (and continue to work) diligently to address the many operational deficiencies associated with the Whois protocol, including the lack of support in the current Whois protocol for user authentication/access control and internationalization/localization. The current proposal to implement the RDAP Operational Profile prematurely in a manner consistent with the current Whois protocol perpetuates, rather than solves, the functionally deficient status quo. Considering that currently there is a GNSO PDP underway on the Next-Generation gTLD Registration Directory Service (RDS), the timing of requiring all gTLD registries to implement the RDAP Operational Profile developed by staff appears to be particularly premature and at odds with the ongoing community processes. The first question that Next-Generation RDS PDP has been tasked to consider is if a replacement RDDS protocol is the most appropriate means to address the widely-recognized deficiencies in the current Whois protocol. Given the ongoing community work within the Next-Generation RDS PDP, it seems appropriate to wait at least until the PDP has answered that question before proceeding with a requirement to implement the RDAP Operational Profile. Verisign recognizes that ICANN staff proposed meeting the Consistent Labeling and Display requirements of the thick Whois PDP with RDAP in response to community concern over the large volume of RDDS related initiatives and their impacts on contracted parties. The initial proposal to combine the two initiatives was supported by the IRT, including Verisign. Given that additional policy work is required before RDAP can be implemented in a way that addresses the shortcomings of Whois, rather than perpetuating those shortcomings in a new protocol, Verisign supports deferring the implementation of RDAP contingent on the results of the Next-Generation RDS PDP. Thank you From: gnso-impl-thickwhois-rt-bounces@icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Fabien Betremieux Sent: Thursday, July 07, 2016 6:14 PM To: gnso-impl-thickwhois-rt@icann.org<mailto:gnso-impl-thickwhois-rt@icann.org> Subject: [Gnso-impl-thickwhois-rt] Reminder: For IRT Review - Consistent Labeling & Display - Revised Policy Language Dear IRT members, This is a friendly reminder for your review of the revised Consistent Labeling & Display Policy Language by Friday 8 July COB in your time zone. Please note that this document was presented and discussed in our last meeting on June 30 in Helsinki. The recording and transcript of our discussion are available here: http://sched.co/7Mdw Thank you for your attention Best Regards -- Fabien Betremieux Sr. Registry Services & Engagement Manager Global Domains Division, ICANN From: Fabien Betremieux <fabien.betremieux@icann.org<mailto:fabien.betremieux@icann.org>> Date: Wednesday, June 29, 2016 at 5:42 PM To: "gnso-impl-thickwhois-rt@icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt@icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>> Subject: For IRT Review - Consistent Labeling & Display - Revised Policy Language Dear IRT members, As discussed in our meeting earlier today, we have posted our revision of the Policy language for implementation of the Consistent Labeling and Display requirement on our wiki: https://community.icann.org/pages/editpage.action?pageId=52889541. It is also attached to this email for your convenience. Please note that the format of the policy, after our revision, is different from the draft we posted for public comments in December (https://www.icann.org/public-comments/rdds-output-2015-12-03-en). We believe this was necessary to address the feedback we received from the community and the IRT in terms of the linkage of the Policy with Specification 3 of the 2013 RRA and the Whois Clarifications Advisory. For instance, while the draft policy required "The labeling and display of all gTLD registries web-based RDDS output , must be consistent with: (a) Specification 3 of the 2013 Registrar Accreditation Agreement (RAA)", the revised policy lists specific requirements such as "3. If shown, the "Registrar Registration Expiration Date" field MUST appear immediately after the "Registry Expiry Date" field." Please also note that while the Policy has changed in format, it did not change in substance in order to address the community's feedback we received in the public comment forum. Therefore, we believe this revision does not require further public comments and can be announced by 31 July 2016 for implementation with an effective date of 1 February 2017. Please review this revised Policy language as soon as possible, ideally before Friday 8 July COB. In the meantime, we will use the opportunity of our meeting in Helsinki tomorrow (http://sched.co/7Mdw) to present and discuss this revised policy language. Thank you for your consideration Best Regards -- Fabien Betremieux Sr. Registry Services & Engagement Manager Global Domains Division, ICANN