<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Dear members, with apologies for sending this directly, rather via Secretariat with our new process, I wanted to add this topic to our BC call today, given its priority to all BC members as a topic of interest. <div><br></div><div>We will organize a separate discussion, with Steve and Chris's collaboration, as this topic cuts across our larger ICANN governance input, and has implications for our Strat Plan, and Budget and Ops Plan input, as well as implications for outreach into the broader eco system of providers of Internet resources that rely on the DNS, but are broader in implications. </div><div><br></div><div>Marilyn Cade</div><div>BC Chair<br><br><div><hr id="stopSpelling">From: julie.hedlund@icann.org<br>To: soac-discussion@icann.org<br>Date: Wed, 9 Nov 2011 12:24:34 -0800<br>Subject: [soac-discussion] Board Resolution re: SAC051 Recommendations<br><br>
<meta http-equiv="Content-Type" content="text/html; charset=unicode">
<meta name="Generator" content="Microsoft SafeHTML">
<title>Board Resolution re: SAC051 Recommendations</title>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">Dear Chairs and Vice Chairs of the ICANN Supporting Organizations and Advisory Committees,<br>
<br>
Per the Board Resolution passed on 28 October 2011 at: <a href="http://www.icann.org/en/minutes/resolutions-28oct11-en.htm#5" target="_blank">http://www.icann.org/en/minutes/resolutions-28oct11-en.htm#5</a> 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: <a href="http://www.icann.org/en/committees/security/sac051.pdf" target="_blank">http://www.icann.org/en/committees/security/sac051.pdf</a> and, in particular, to the recommendations listed below.<br>
<br>
Please send your advice to me at <a href="http://julie.hedlund%40icann.org" target="_blank">julie.hedlund@icann.org</a> not later than 09 January 2011. Please also let me know if you have any questions.<br>
<br>
Thank you very much for your assistance in this matter.<br>
<br>
Best regards,<br>
<br>
Julie Hedlund<br>
Director, SSAC Support<br>
<br>
<b>Recommendations from Security and Stability Advisory Committee Report on Whois Terminology & Structure (SAC051)<br>
</b>Whereas, WHOIS service has been an important information service for the Internet community, and is part of all ICANN TLD contracts.<br>
<br>
Whereas, the shortcomings of the WHOIS protocol have been known for some time.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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<br>
<br>
<b>SAC051 Recommendations:<br>
</b><br>
<b>Recommendation 1:</b> The ICANN community should adopt the terminology outlined in this report in documents and discussions, in particular:<br>
· Domain Name Registration Data (DNRD). The data that domain name registrants provide when registering a domain name and that registrars or registries collects. <br>
· Domain Name Registration Data Access Protocol (DNRD-AP). The components of a (standard) communications exchange—queries and responses—that specify the access to DNRD. <br>
· 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. <br>
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.<br>
<br>
<b>Recommendation 2:</b> 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.<br>
<br>
<b>Recommendation 3</b>: 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.<br>
<br>
</span></font></div></div> </div></body>
</html>