<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font class="Apple-style-span" face="Arial">Dear all</font></div><div><font class="Apple-style-span" face="Arial"><br></font></div><div><font class="Apple-style-span" face="Arial">In preparation for the San Francisco meeting, and as agreed in our last call, we have been trying to arrange slots with the SO/ACs during the ICANN meeting. In preparation for this, I had a conversation this morning with Patrik Faltstrom, the Chair of ICANN's Security and Stability Advisory Committee (SSAC) this morning. </font></div><div><font class="Apple-style-span" face="Arial"><br></font></div><div><font class="Apple-style-span" face="Arial">These are the key points that he would like us to be aware of in preparation for our meeting with SSAC in San Francisco, and (I think) an interesting take on why the underlying protocol is relevant to our discussions. Patrik has reviewed this note, and is happy for me to share it with you.</font></div><div><font class="Apple-style-span" face="Arial"><br></font></div><div><font class="Apple-style-span" face="Arial">Key messages:</font></div><div><font class="Apple-style-span" face="Arial"><br></font></div><div><font class="Apple-style-span" face="Arial">- It is important that the RT, in its deliberations, draws a distinction between discussions over WHOIS </font><i><font class="Apple-style-span" face="Arial">service</font></i><font class="Apple-style-span" face="Arial"> and the underlying </font><i><font class="Apple-style-span" face="Arial">protocol. </font></i><font class="Apple-style-span" face="Arial">This distinction is summarised in the staff paper to the Cartagena meeting </font><span class="Apple-style-span" style="line-height: 17px; "><font class="Apple-style-span" face="Arial"> </font><a href="http://cartagena39.icann.org/meetings/cartagena2010/presentation-tech-evolution-whois-service-15nov10-en.pdf" class="external-link" rel="nofollow" style="color: rgb(0, 51, 102); font-weight: bold; "><font class="Apple-style-span" face="Arial">Technical Evolution of the Whois Service</font></a><font class="Apple-style-span" face="Arial">, which also reviews potential successor protocols, IRIS and RWS. </font></span></div><div><span class="Apple-style-span" style="line-height: 17px; "><font class="Apple-style-span" face="Arial"><br></font></span></div><div><font class="Apple-style-span" face="Arial">- SSAC's focus </font>has been to try to separate the discussion of the protocol from the discussion of the service and the various policies that are attached to each one of the two. So far SSAC has the view that there has been slow progress as still too much of the discussion in ICANN mix the two.</div><div style="font-family: Arial; "><br></div><div style="font-family: Arial; ">The IETF has reviewed the existing whois protocol and developed (at least) one successor, IRIS, as described in the staff report.</div><div><font class="Apple-style-span" face="Arial"><br></font></div><div><font class="Apple-style-span" face="Arial">- For the RT's purposes, the relevance of the protocol is its impact on policy and its implementation. A useful focus from SSAC's perspective would be to enhance understanding about why better protocols have not enjoyed widespread adoption, and what role ICANN might play in supporting migration.</font></div><div><font class="Apple-style-span" face="Arial"><br></font></div><div><font class="Apple-style-span" face="Arial">SSAC's key documents, included in the background materials are:</font></div><div><font class="Apple-style-span" face="Arial"><br></font></div><div><span class="Apple-style-span" style="line-height: 17px; "><ul style="line-height: 13pt; list-style-type: disc; "><li style="line-height: 13pt; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><b><font class="Apple-style-span" face="Arial">SAC 023</font></b><font class="Apple-style-span" face="Arial"> -- </font><a href="http://www.icann.org/en/committees/security/sac023.pdf" class="external-link" rel="nofollow" style="color: rgb(0, 51, 102); font-weight: bold; "><font class="Apple-style-span" face="Arial">Is the WHOIS Service a Source for email Addresses for Spammers?</font></a><font class="Apple-style-span" face="Arial"> (23 October 2007)</font></li><li style="line-height: 13pt; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><b><font class="Apple-style-span" face="Arial">SAC 027</font></b><font class="Apple-style-span" face="Arial"> -- </font><a href="http://www.icann.org/en/committees/security/sac027.pdf" class="external-link" rel="nofollow" style="color: rgb(0, 51, 102); font-weight: bold; "><font class="Apple-style-span" face="Arial">SSAC Comment to GNSO regarding WHOIS studies</font></a><font class="Apple-style-span" face="Arial"> (7 February 2008)</font></li><li style="line-height: 13pt; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><b><font class="Apple-style-span" face="Arial">SAC 033 -- </font></b><a href="http://www.icann.org/en/committees/security/sac033.pdf" class="external-link" rel="nofollow" style="color: rgb(0, 51, 102); font-weight: bold; "><font class="Apple-style-span" face="Arial">Domain Name Registration Information and Directory Services</font></a><font class="Apple-style-span" face="Arial"> (20 June 2008)</font></li><li style="line-height: 13pt; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><b><font class="Apple-style-span" face="Arial">SAC 037 --</font></b><font class="Apple-style-span" face="Arial"> </font><a href="http://www.icann.org/en/committees/security/sac037.pdf" class="external-link" rel="nofollow" style="color: rgb(0, 51, 102); font-weight: bold; "><font class="Apple-style-span" face="Arial">Display and usage of Internationalized Registration Data: Support for characters from local languages or scripts</font></a><font class="Apple-style-span" face="Arial"> (21 April 2009)</font></li><li style="line-height: 13pt; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><b><font class="Apple-style-span" face="Arial">SAC 038</font></b><font class="Apple-style-span" face="Arial"> </font><a href="http://www.icann.org/en/committees/security/sac038.pdf" class="external-link" rel="nofollow" style="color: rgb(0, 51, 102); font-weight: bold; "><font class="Apple-style-span" face="Arial">– Registrar Abuse Point of Contact</font></a><font class="Apple-style-span" face="Arial"> (25 February 2009)</font></li></ul></span></div><div>Best wishes,</div><div><br></div><div>Emily</div><div><br></div><div>
<style type="text/css">
body{margin:0;padding:10px;font-family: arial,helvetica,sans-serif;}
html{margin: 0;padding: 0;}
img{margin-bottom: 20px;}
p{font-family: arial,helvetica,sans-serif;font-size: 14px;color: #666;}
a{color: #333;font-weight: bold;}
.bold{font-weight: bold;}
</style>
<img style="margin-top:20px;" moz-do-not-send="true" src="http://www.etlaw.co.uk/images/stories/etlaw/logo310.gif" alt="Emily Taylor Consultant (Internet Law and Governance)" width="310" height="47">
<p style="font-family: arial,helvetica,sans-serif;font-size: 14px;color: #666;">76 Temple Road, Oxford OX4 2EZ UK <br> telephone: <b> 01865 582 811</b> mobile: <b> 07540 049 322</b> <br> <a href="mailto:emily.taylor@etlaw.co.uk">emily.taylor@etlaw.co.uk</a> <a href="http://www.etlaw.co.uk">www.etlaw.co.uk</a></p>
</div>
<br></body></html>