<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 15 (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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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 bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Dear members of the IRP IOT,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As mentioned, I wrote to PTI President Elise Gerich about our draft letter to inform direct customers of the IANA naming functions of their special-rules provision in the bylaws (specifically in Section 4.3(n)(ii)).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Elise’s reply is below. She helpfully suggested a combination of the “direct customers of naming functions” letter with our draft letter to SOs/ACs – and her suggestion makes sense. The point for us (recalling that these are informational letters) is to get the word out as broadly as possible. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am attaching a re-draft of our letter to SOs/ACs in which I have included the “special rules” language for direct customers of the naming functions. Thus there appears no need for two separate letters under the approach that a letter to SOs/ACs will reach the direct customers of the naming functions appropriately. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Unless I hear an objection, I will ask Bernie to distribute the letter to SOs/ACs next Tuesday, Feb. 28<sup>th</sup> at 20:00 UTC.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best wishes to all,<o:p></o:p></p><p class=MsoNormal>David<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>David McAuley<o:p></o:p></p><p class=MsoNormal>International Policy Manager<o:p></o:p></p><p class=MsoNormal>Verisign Inc.<o:p></o:p></p><p class=MsoNormal>703-948-4154<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Elise Gerich [mailto:elise.gerich@iana.org] <br><b>Sent:</b> Wednesday, February 08, 2017 6:34 PM<br><b>To:</b> McAuley, David <dmcauley@Verisign.com><br><b>Cc:</b> Bernard Turcotte (turcotte.bernard@gmail.com) <turcotte.bernard@gmail.com>; Samantha Eisner <Samantha.Eisner@icann.org><br><b>Subject:</b> [EXTERNAL] Re: [Ext] questions for helping the IRP IOT team<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi David - <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I understand that the IOT will also be reaching out to the supporting organizations and advisory committees for a similar purpose. I think that you can streamline your process to only send a single letter and reduce potential for confusion. I recommend that in each of those letters, you add in a section that says:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To the extent your group (in whole or in part) is a direct customer of the IANA Naming Function, please note that Section 4.3(n)(ii) is of particular interest to “direct customers” of the IANA naming functions, stating in part:<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><i>Specialized Rules of Procedure may be designed for reviews of PTI service complaints that are asserted by direct customers of the IANA naming functions and are not resolved through mediation. The Rules of Procedure shall be published and subject to a period of public comment that complies with the designated practice for public comment periods within ICANN, and take effect upon approval by the Board, such approval not to be unreasonably withheld.</i><o:p></o:p></p><p class=MsoNormal>Direct customers of the IANA naming functions should have an opportunity to inform us of your views on the matter.<o:p></o:p></p><p class=MsoNormal>We urge you to review the provisions of Section 4.3(n) generally on IRP rules of procedure and let the IRP IOT know of any requests along these lines. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best regards,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> --Elise<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='color:black'>Elise Gerich <o:p></o:p></span></p><p class=MsoNormal>President | PTI<o:p></o:p></p><p class=MsoNormal><span lang=NO-BOK>12025 Waterfront Drive | Suite 300<o:p></o:p></span></p><p class=MsoNormal><span lang=NO-BOK>Los Angeles, CA 90094<o:p></o:p></span></p><p class=MsoNormal>+1-310-463-1108<o:p></o:p></p></div><p class=MsoNormal><b><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></b></p><p class=MsoNormal><b><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='color:black'>From: </span></b><span style='color:black'>"McAuley, David" <<a href="mailto:dmcauley@verisign.com">dmcauley@verisign.com</a>><br><b>Date: </b>Friday, February 3, 2017 at 11:22 AM<br><b>To: </b>Elise Gerich <<a href="mailto:elise.gerich@iana.org">elise.gerich@iana.org</a>><br><b>Cc: </b>"Bernard Turcotte (<a href="mailto:turcotte.bernard@gmail.com">turcotte.bernard@gmail.com</a>)" <<a href="mailto:turcotte.bernard@gmail.com">turcotte.bernard@gmail.com</a>><br><b>Subject: </b>[Ext] questions for helping the IRP IOT team</span><span style='font-size:12.0pt;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-left:.5in'>Hi Elise,<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>I am the lead of the IRP Implementation Oversight Team (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pages_viewpage.action-3FpageId-3D59643726&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=pXgd7rUFmOGPSaTcf3kROMV5Rt3fTXejagLVImG-D14&m=yQllUB1-8s_dPTOooAAlqHpcrjYA73Vv8sM5QrxlLBU&s=H19tVsy6M5Wy2n_pgW-jL9C9rkc-pu4eQaxKrjA-Kfo&e=">https://community.icann.org/pages/viewpage.action?pageId=59643726[community.icann.org]</a>) that is working on implementing the new ICANN bylaws respecting IRP.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Bylaw Section 4.3(n)(ii) provides:<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='color:red;background:white'>The Rules of Procedure shall be informed by international arbitration norms and consistent with the Purposes of the IRP. Specialized Rules of Procedure may be designed for reviews of PTI service complaints that are asserted by direct customers of the<span class=apple-converted-space> </span></span><span style='color:red'>IANA<span class=apple-converted-space><span style='background:white'> </span></span><span style='background:white'>naming functions and are not resolved through mediation. The Rules of Procedure shall be published and subject to a period of public comment that complies with the designated practice for public comment periods within<span class=apple-converted-space> </span></span>ICANN<span style='background:white'>, and take effect upon approval by the Board, such approval not to be unreasonably withheld.</span></span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>We are trying to notify various groups of their rights/responsibilities under the new bylaws – for example we have written to the SOs/ACs about their input into the panel of arbitrators.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>The bylaw above speaks to “direct customers of the IANA naming functions” – we want to send them the attached notice.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Are you able to help us in how exactly that notice might be made?<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Any help or insight would be appreciated. <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Meantime,<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Best wishes,<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>David<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>David McAuley<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>International Policy Manager<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Verisign Inc.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>703-948-4154<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p></div></body></html>