I support. ________________________________ From: owner-council@gnso.icann.org To: Liz Gasster ; GNSO Council Sent: Sat Nov 12 05:32:30 2011 Subject: Re: [council] [soac-discussion] Board Resolution re: SAC051 Recommendations Thanks Liz, If staff does not mind, I think it would be useful to prepare an update as you suggest so that Council can then consider whether to send it or not. Councillors, do you support this approach? Stéphane Le 11 nov. 2011 à 18:29, Liz Gasster a écrit : Stéphane and all, If I may add to Stéphane’s point about whether the Council wishes to make comments on the SAC 051 Recommendations as requested by the Board, I would note in particular the Board’s Resolved to: Resolved (2011.10.28.27), the Board directs staff to produce, in consultation with the community, a roadmap for the coordination of the technical and policy discussions necessary to implement the recommendations outlined in SAC 051. The WHOIS Service Requirements Survey Working Group had a preliminary discussion about this at its working group meeting yesterday, noting the possibility that information from the survey could contribute to informing such a roadmap. In addition, the joint SSAC-GNSO IRD Working Group has a draft Final Report currently out for public comment that is also relevant to Recommendation 2 of the SAC report, which states: The ICANN community should evaluate and adopt a replacement domain name registration data access protocol that supports the query and display of Internationalized DNRD as well as addressing the relevant recommendations in SAC 003, SAC 027 and SAC 033. At minimum, it might be advisable to provide an update to the Board on these pending GNSO Whois protocol-related activities to ensure that the roadmap and any subsequent related actions take into consideration the work of these groups. Staff would be happy to prepare a draft of update from the Council on these matters if you would like. Best regards, Liz From: owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Stéphane Van Gelder Sent: Thursday, November 10, 2011 2:05 AM To: GNSO Council Subject: [council] Fwd: [soac-discussion] Board Resolution re: SAC051 Recommendations Councillors, Please see the message below. At this point, we do not have to respond if we do not think we have anything to add. However, we may wish to respond if there are comments to be made. Please share with your groups and let me know if there is a desire to discuss this at our next Council meeting. Thanks, Stéphane Début du message réexpédié : De : Julie Hedlund <julie.hedlund@icann.org> Objet : [soac-discussion] Board Resolution re: SAC051 Recommendations Date : 9 novembre 2011 21:24:34 HNEC À : "soac-discussion@icann.org" <soac-discussion@icann.org> Dear Chairs and Vice Chairs of the ICANN Supporting Organizations and Advisory Committees, Per the Board Resolution passed on 28 October 2011 at: http://www.icann.org/en/minutes/resolutions-28oct11-en.htm#5 and listed below, the Board directed staff to forward SAC051 “SSAC Report on WHOIS Terminology and Structure” to ICANN’s Advisory Committees and Supporting Organizations for their advice, if any, with regards to implementing the SSAC recommendations. Please refer to SAC051 at:http://www.icann.org/en/committees/security/sac051.pdf and, in particular, to the recommendations listed below. Please send your advice to me at julie.hedlund@icann.org <x-msg://78/julie.hedlund@icann.org> not later than 09 January 2011. Please also let me know if you have any questions. Thank you very much for your assistance in this matter. Best regards, Julie Hedlund Director, SSAC Support Recommendations from Security and Stability Advisory Committee Report on Whois Terminology & Structure (SAC051) Whereas, WHOIS service has been an important information service for the Internet community, and is part of all ICANN TLD contracts. Whereas, the shortcomings of the WHOIS protocol have been known for some time. Whereas, on 20 September 2011, ICANN's Security and Stability Advisory Committee (SSAC) published a report "SSAC Report on Domain Name WHOIS Terminology and Structure" (SAC 051), including specific recommendations aimed at clarity of terminology and structure with regard to discussions regarding WHOIS. Resolved (2011.10.28.26), the Board hereby acknowledges the receipt of SAC 051, and thanks SSAC and other contributors for their efforts in the creation of the report. Resolved (2011.10.28.27), the Board directs staff to produce, in consultation with the community, a roadmap for the coordination of the technical and policy discussions necessary to implement the recommendations outlined in SAC 051. Resolved (2011.10.28.28), the Board directs staff to forward SAC 051 to ICANN's Advisory Committees and Supporting Organizations for their advice, if any, with regards to implementing the SSAC recommendations, and to forward SAC 051 to the Whois Review Team SAC051 Recommendations: Recommendation 1: The ICANN community should adopt the terminology outlined in this report in documents and discussions, in particular: · Domain Name Registration Data (DNRD). The data that domain name registrants provide when registering a domain name and that registrars or registries collects. · Domain Name Registration Data Access Protocol (DNRD-AP). The components of a (standard) communications exchange—queries and responses—that specify the access to DNRD. · Doman Name Registration Data Directory Service (DNRD-DS). The service(s) offered by domain name registries and registrars to implement the DNRD-AP and to provide access to DNRD-DSD. Additional terminology includes “DNRDe,” “DNRD Policy,” “DNRD-DS Policy,” “Internationalized DNRD,” and “Localized DNRD.” The term “WHOIS” should only be used when referring to the protocol as currently specified in RFC 3912. Recommendation 2: The ICANN community should evaluate and adopt a replacement domain name registration data access protocol that supports the query and display of Internationalized DNRD as well as addressing the relevant recommendations in SAC 003, SAC 027 and SAC 033. Recommendation 3: The ICANN community should develop a uniform and standard framework for accessing DNRD that would provide mechanisms to define and implement a range of verification methods, credential services, and access control capabilities.