<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple style='word-wrap: break-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hello again all,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Unfortunately, I will again be missing tomorrow’s call, so I’m sending through my comments in advance.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Privacy/proxy<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I’ve made some edits and suggestions directly to the small group working on the privacy-proxy recommendations. I’m not sure where that will end up before the call, but I am encouraged that the group is making good progress.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Recommendation 17<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>In short, I really like Emily’s new version. I’m interested in other views, but to me this gets to the heart of (this part of) the accessibility issue, and is clear, actionable, and should avoid the confusion we had with our earlier version. My one question on this is whether we should also explicitly recommend that ICANN actively and widely promote this new/improved service – i.e. even if it’s improved, won’t it only be useful if people know about it? My initial thinking is that we should recommend this, as it would form an important part of the bigger goal of improving awareness and accessibility, but I’d like to hear other views.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Recommendation 3<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>My broad question on this one is whether we would be better served separating the ‘WHOIS priority’ and ‘compliance’ parts of this into completely separate findings and recommendations? While these are clearly linked, our expectations seem to be quite distinct, and it seems to me that there is potential for confusion if we roll them together – i.e. the ‘priority’ issue will not be resolved by simply having more or better compliance, and the ‘compliance’ issues won’t be resolved by having a WHOIS tsar or similar. I think we risk having people think we’re talking about one or the other, rather than both, if we leave them together. Depending on what others think about separating these two issues, with dedicated findings and recommendations for each, I’d be happy to assist with the detail. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Recommendation 5<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Just in case it was missed, I wanted to restate my question on recommendation 5: are the new edits on timing only intended to apply to the data accuracy recommendations, or more broadly to all of our recommendations? I’ve read the notes from the last call and gather that it is intended to put some pretty clear timing expectations around this recommendation, and I strongly support that. What wasn’t clear to me from the call notes was whether having similarly clear timing expectations for our other recommendations was discussed (noting that the actual timing/expectations may be different for each recommendation)?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I apologise if I’ve missed any other outstanding redrafts, and would appreciate any comments and updates that anyone is able to share in advance of, or in addition to, the call notes.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Peter<o:p></o:p></span></p><div><div><div><div><p class=MsoNormal><span style='font-size:7.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div></div></div></div></div>
<P><br/><B>-------------------------------------------------------------------------------</B><br/>
NOTICE: This email message is for the sole use of the intended recipient(s) <br/> and may contain confidential and privileged information. Any unauthorized <br/> review, use, disclosure or distribution is prohibited. If you are not the <br/> intended recipient, please contact the sender by reply email and destroy all <br/> copies of the original message. <br/><br/>This message has been content scanned by the Axway MailGate. <br/>MailGate uses policy enforcement to scan for known viruses, spam, undesirable content and malicious code. For more information on Axway products please visit www.axway.com.<br/>
<br/><B>-------------------------------------------------------------------------------</B><br/>
</P></body></html>