<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=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Calibri-Bold;
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:972255565;
        mso-list-type:hybrid;
        mso-list-template-ids:-539049362 201916417 201916419 201916421 201916417 201916419 201916421 201916417 201916419 201916421;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        margin-left:72.0pt;
        text-indent:-18.0pt;
        font-family:Symbol;}
@list l1
        {mso-list-id:1107655269;
        mso-list-template-ids:-1531154076;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:36.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2
        {mso-list-id:1150709344;
        mso-list-type:hybrid;
        mso-list-template-ids:1250316764 201916417 201916419 201916421 201916417 201916419 201916421 201916417 201916419 201916421;}
@list l2:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        margin-left:72.0pt;
        text-indent:-18.0pt;
        font-family:Symbol;}
@list l3
        {mso-list-id:1288467037;
        mso-list-type:hybrid;
        mso-list-template-ids:1343379802 201916417 201916419 201916421 201916417 201916419 201916421 201916417 201916419 201916421;}
@list l3:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Symbol;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
--></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><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Omar and all,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Following from Omar’s email on part 5 of the GAC advice, I thought it may be worth copying other relevant parts from the GAC’s Prague communique, so that all the text is in one place (sorry for not doing this earlier, but I kept having formatting problems with cutting and pasting from the PDF).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I hope this makes things a bit easier.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Peter<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:Calibri-Bold'>2. ICANN’s role as an industry self-regulatory organisation<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:Calibri-Bold'><o:p>&nbsp;</o:p></span></b></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Calibri","sans-serif"'>a. The GAC understands that ICANN’s role includes:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:72.0pt;text-autospace:none'><span style='font-family:"Calibri","sans-serif"'>i. Overseeing the global DNS industry, and accrediting organisations to participate in that industry<o:p></o:p></span></p><p class=MsoNormal style='margin-left:72.0pt;text-autospace:none'><span style='font-family:"Calibri","sans-serif"'>ii. Use of contracts to establish relationships with specific industry participants.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:72.0pt;text-autospace:none'><span style='font-family:"Calibri","sans-serif"'>iii. Overseeing and enforcing compliance with those contracts<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Calibri","sans-serif"'>b. The GAC welcomes the briefing on ICANN’s role in overseeing the global DNS industry, and looks forward to further targeted discussions on this issue  <o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><b><span style='font-family:Calibri-Bold'>The GAC requests a written briefing </span></b><span style='font-family:"Calibri","sans-serif"'>from</span><b><span style='font-family:Calibri-Bold'> </span></b><span style='font-family:"Calibri","sans-serif"'>the</span><b><span style='font-family:Calibri-Bold'> </span></b><span style='font-family:"Calibri","sans-serif"'>Board</span><b><span style='font-family:Calibri-Bold'> </span></b><span style='font-family:"Calibri","sans-serif"'>that</span><b><span style='font-family:Calibri-Bold'> </span></b><span style='font-family:"Calibri","sans-serif"'>explains:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><b><span style='font-family:Calibri-Bold'><o:p>&nbsp;</o:p></span></b></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l3 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'>The broad principles and particular mechanisms used by ICANN when overseeing the global DNS industry, including details of each of the self-regulatory mechanisms it has developed for this role (including contracts, code of conduct, and so on)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l3 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'>Why ICANN has chosen to accredit and contract with some industry participants directly (for example, registries and registrars), and not others (for example, resellers)?<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l3 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'>How ICANN would resolve a situation where a reseller was identified as breaching an ICANN policy or contractual obligation? How would a breach involving a privacy/proxy provider be handled? It would be useful for these hypothetical circumstances to reflect any documented procedures, contractual obligations, and escalation measures.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:Calibri-Bold'>3. ICANN’s role in the development of contracts<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:Calibri-Bold'><o:p>&nbsp;</o:p></span></b></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Helvetica","sans-serif"'>a. </span><span style='font-family:"Calibri","sans-serif"'>The GAC welcomes the publication by ICANN of the draft new Registrar Accreditation Agreement (RAA). It appears that this draft contains many changes from the current RAA, and has clearly been informed by a number of LEA/GAC recommendations.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Helvetica","sans-serif"'>b. </span><span style='font-family:"Calibri","sans-serif"'>Several questions relating to privacy and data protection issues and the accountability of resellers remain outstanding. As discussed in the public meeting with the Board, the GAC stands ready to assist in these discussions. The GAC encourages the Board to provide written questions on any privacy and data retention matters to the GAC to facilitate an early response.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Helvetica","sans-serif"'>c. </span><span style='font-family:"Calibri","sans-serif"'>The GAC emphasises the need for all ICANN contracts to be clear, unambiguous and enforceable, and welcomes ICANN’s efforts to enhance its compliance and termination tools as a part of the RAA negotiation process. The timeliness of this work is increasingly important.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:Calibri-Bold'><o:p>&nbsp;</o:p></span></b></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><b><span style='font-family:Calibri-Bold'>The GAC advises the Board<o:p></o:p></span></b></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><b><span style='font-family:Calibri-Bold'><o:p>&nbsp;</o:p></span></b></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l2 level1 lfo3;text-autospace:none'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'>that this work should be finalised as a matter of priority, and<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l2 level1 lfo3;text-autospace:none'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'>that all the necessary amendments and procedures should be in place in advance of the delegation of any new gTLDs<b>.</b> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Calibri","sans-serif"'>The GAC reiterates its interest and availability to assist with the resolution of these issues.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:Calibri-Bold'>4. ICANN’s contract oversight and compliance role<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:Calibri-Bold'><o:p>&nbsp;</o:p></span></b></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Helvetica","sans-serif"'>a. </span><span style='font-family:"Calibri","sans-serif"'>At the San Jose meeting, the GAC had asked the Board for an update on the status of the LEA/GAC recommendations that relate to due diligence by ICANN, and would appreciate a response.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Helvetica","sans-serif"'>b. </span><span style='font-family:"Calibri","sans-serif"'>The importance of an effective industry oversight and compliance function will become more important with the upcoming introduction of new gTLDs, and an increase in the number of contracts that ICANN will need to oversee. With the accompanying likelihood of new entrants to the industry, it will be important for ICANN to ensure that its compliance policies and processes are clear, publicly known and consistently enforced.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><span style='font-family:"Helvetica","sans-serif"'>c. </span><span style='font-family:"Calibri","sans-serif"'>The GAC has provided the Board with examples of organisations that have separated their regulatory and operational responsibilities (see Annex 1). As previously advised at the San Jose meeting, the GAC considers that a principles-based approach to structuring ICANN’s compliance activities would support a robust and consistent oversight and compliance function.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:Calibri-Bold'><o:p>&nbsp;</o:p></span></b></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><b><span style='font-family:Calibri-Bold'>The GAC advises the Board<o:p></o:p></span></b></p><p class=MsoNormal style='margin-left:36.0pt;text-autospace:none'><b><span style='font-family:Calibri-Bold'><o:p>&nbsp;</o:p></span></b></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo4;text-autospace:none'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'>to finalise improvements to its compliance and industry oversight functions before any new gTLDs are launched.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Omar Kaminski [mailto:omar@kaminski.adv.br] <br><b>Sent:</b> Tuesday, 3 July 2012 11:25 AM<br><b>To:</b> Nettlefold, Peter<br><b>Cc:</b> rt4-whois@icann.org<br><b>Subject:</b> Re: [Rt4-whois] GAC endorses WHOIS RT recommendations [SEC=UNCLASSIFIED]<o:p></o:p></span></p></div><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Glad to know, thanks for the update, Peter!<br><b><br>5. WHOIS Review Team</b><br><br>a. The GAC welcomes the final report of the WHOIS Review Team, and notes that there are a number of common themes identified by the WHOIS Review Team’s recommendations, the LEA/GAC recommendations, and the<br>GAC’s advice relating to ICANN’s industry oversight and compliance function.<br><br>b. The GAC endorses the recommendations of the WHOIS Review Team, and will closely monitor the Board’s response and subsequent implementation activities.<br><b><br>The GAC advises the Board </b><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'>to take account of the WHOIS Review Team’s recommendations as part of the current RAA amendment process.<o:p></o:p></li></ul><p class=MsoNormal style='margin-bottom:12.0pt'>Omar<br><br><br><o:p></o:p></p><div><p class=MsoNormal>2012/7/2 Nettlefold, Peter &lt;<a href="mailto:Peter.Nettlefold@dbcde.gov.au" target="_blank">Peter.Nettlefold@dbcde.gov.au</a>&gt;<o:p></o:p></p><div><div><div><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hello all,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Following the Prague meeting, I just wanted to let you know that the GAC has endorsed the WHOIS RT recommendations, and has also provided advice on related industry oversight, contract development, and compliance issues.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For those who are interested, these issues are addressed in parts 2-5 of the ‘GAC advice to the Board’ section of the attached Prague communique.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I’m happy to discuss any of this, and look forward to seeing you all again at a future meeting.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Peter</span><o:p></o:p></p></div></div></div></div></div></div></div><p class=MsoNormal><o:p>&nbsp;</o:p></p></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>