<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 14 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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
{mso-style-priority:99;
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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1447967556;
mso-list-type:hybrid;
mso-list-template-ids:-509973386 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Milton,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I want to make sure that you understand what approach is planned for creating the FY17 budget for PTI. We discussed this on our last two CWG calls. The plan
is to first build a budget based on what is being called a Base Case that would involve minimal operational changes and then, in addition to that, estimate costs for alternative operational changes that would go beyond the minimum. It is my understand that
the Base Case “</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">would not involve any movement, separation or transfer of facilities</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”.
In case it is decided that the Base Case does not sufficiently meet the CWG Stewardship recommendations, then the draft budget would also contain estimated costs for various operational changes so that the community will be able to see what the estimated cost
impact would be for such changes. In the end, without having to go back and redo the draft budget, we should be able to simply add the already estimated costs for any alternatives to the Base Case costs. For example, if it was decided that the IANA staff
needed to relocate into different facilities than where they are presently located, then the estimated costs for doing that would need to be added to the estimated costs for the Base Case.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As I pointed out on the last CWG call, we will of course be able to comment in the FY 17 Draft Operating Plan and Budget public comment period that is scheduled
to start on 5 March. But if there is consensus in the CWG that certain operational changes must happen beyond the base case, communicating those sooner rather than later might save time in the long run. Staff has set a target of 15 January for defining
assumptions for the draft budget to allow them time to create the draft operating plan and budget in time for public comment starting on 5 March. So I asked the following question of CWG participants:
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Are there any operational areas for which you think more than minimal changes might be in order? If we identify those by 15 January, it will ensure that they are included
as alternatives in the draft budget.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Mueller, Milton L<br>
<b>Sent:</b> Friday, December 11, 2015 2:42 PM<br>
<b>To:</b> Greg Shatan<br>
<b>Cc:</b> cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] FW: [client com] CWG Comment Letter to CCWG 3rd Draft Proposal<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Greg:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">J</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> I see that you _<i>still</i>_ don’t quite understand what the IANA is. That is to
say, the distinction between an IFO, a functionary contracted to carry out certain functions for the operational communities who are responsible for the registries, and “the IANA” – the generic term for the top level registries as embodied in the IETF RFCs
– seems to elude you. I refer you back to our original conversations about this. You were arguing that ICANN or PTI should control the trademarks and domains and you lost that argument. I will have to continue to insist, therefore, that PTI not be called
“the IANA” and I really don’t see why you insist on contesting this, because there is nothing tangible to gain by so doing. Fundamentally, I care simply because it is inaccurate but it also has implication for separability and a clean handling of the trademark
issue.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am also a bit astounded by the story you have made up about PTI’s organization. Please direct me to anywhere in our proposal, or in our deliberations, where
it was decided that PTI should be nothing more than a re-labeling of ICANN’s IANA department and that the transition would not involve any movement, separation or transfer of facilities. I would be very curious to know how and when you got the idea that your
personal assumptions about what the separation of PTI got ratified as the one and only version of implementation (“that is our proposal”). PTI is a separate corporation. It may be a controlled subsidiary of ICANN but it is a separate entity, with its own staff,
budget, management, and board. Sure, there can be some resource sharing with ICANN but I think we need to devote some serious thought to the implications of blurring the lines between it and ICANN so much that the whole point of legal separation is lost.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">--MM<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Greg Shatan [<a href="mailto:gregshatanipc@gmail.com">mailto:gregshatanipc@gmail.com</a>]
<br>
<b>Sent:</b> Friday, December 11, 2015 2:06 PM<br>
<b>To:</b> Mueller, Milton L<br>
<b>Cc:</b> <a href="mailto:jrobinson@afilias.info">jrobinson@afilias.info</a>; <a href="mailto:cwg-stewardship@icann.org">
cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] FW: [client com] CWG Comment Letter to CCWG 3rd Draft Proposal<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">My comments on the letter are attached. (Sorry for the "anonymization" of most of my comments; that appears to be the default setting on this particular document.)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">In response to Milton's comments, I made one further change. I think the remaining references to IANA are appropriate and should not be changed. Also in response to Milton's comments: <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">While PTI would be a separate corporation, and the current IANA staff would become PTI employees, PTI will be treated as a wholly-owned subsidiary of ICANN and will not be set up as an isolated,
independent organization. As stated in our proposal, "</span><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif"">ICANN will provide funding and administrative resources to PTI through an agreed-upon budget.</span><span style="font-family:"Verdana","sans-serif"">"
Operationally, this means that PTI will not have its own full-time administrative staff and support services (HR, accounting, IT, office manager, etc.) but would have a support services arrangement where ICANN would provide those services to PTI. Similarly,
PTI would not be kicked out of ICANN's offices and forced to set up its own facilities, but would have some form of sharing arrangement (possibly as formal as a sublease, possibly not). It would be expensive and wasteful for a corporation with a dozen or
so staffers to hire full-time people across a range of admin/support/back-office functions, and this was never contemplated in our plan. I don't think this subverts our proposal; this is our proposal. If PTI is going to be disaffiliated from ICANN, there
will be ample time to make arrangements to replace ICANN's support services and to move out of ICANN -- and if PTI becomes affiliated with another larger entity in place of ICANN, that entity can provide support services and potentially facilities as well.
Only if a post-separation PTI is truly stand-alone would it need to incur the costs of being an independent entity.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">As far as the use of IANA name goes, I disagree with what I believe Milton was saying (the email appears somewhat garbled). As part of the license from the new holder of the IANA trademarks,
PTI can be granted the right to use the marks in identifying itself. Indeed, PTI should be licensed the right to use the term "Internet Assigned Numbers Authority" as its name, since that is exactly the function that it will be carrying out. PTI would also
be using the IANA logo (which combines "IANA" in stylized letters with the name "Internet Assigned Numbers Authority"). If PTI disaffiliates from ICANN, these rights would go along with it. If there is a future separation, and the IANA functions are no longer
handled by PTI, the new IFO would be licensed these rights. If there's a partial separation, the mini-IFOs could be termed "Internet Assigned Numbers Authority-Names" ("IANA-Names"), IANA-Numbers and IANA-Protocols (or something like that). Indeed it would
be rather odd for the IANA Functions Operator (or operators) not to be called "IANA."<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Greg<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Dec 11, 2015 at 1:10 PM, Mueller, Milton L <<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Jonathan, Lise and all:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I reviewed the response and only found one thing that needs modification. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Section 2, about I am a budget. In this paragraph there are references to an "IANA department". After the transition there will be no IANA department there will only be PTI. I suggest that all references to IANA in this paragraph be changed
to PTI. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Furthermore, the section about transparency of cost seems to be based on the premise that IANA still is a department of ICANN rather than a separate corporation that is contracted to perform the functions. It is not clear from this discussion
whether you are referring to the existing costs of the IANA department, which need to be itemized perhaps in order to determine the size of the PTI budget going forward, or whether you are referring to the PTI budget. For example when you refer to support
functions allocation and shared resources what are you taking about? one would think that when PTI is separate almost all costs will be direct. PTI should be a separate organization with its own facilities and staff. We don't want to encourage a situation
where the purpose of legal separation is subverted but I am betting I am so deeply within I can that it really is not a separate corporation. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">One other issue. It is now important to be careful about the name of the PTI. Going forward the term IANA Will be a trademark in the domain owned by the IETF trust or some equivalent. Because it is a principle of the transition that the
banana functions operator will not control these terms, it would not be appropriate for the name the corporate name of PTI<br>
<br>
Milton L Mueller <o:p></o:p></p>
<div>
<p class="MsoNormal">Professor, School of Public Policy<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Georgia Institute of Technology<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Dec 11, 2015, at 11:53, Jonathan Robinson <<a href="mailto:jrobinson@afilias.info" target="_blank">jrobinson@afilias.info</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">All,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Please see attached for the (Sidley Austin authored) proposed CWG response to the current CCWG proposal with reference to the CWG dependence on that
proposal.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Our plan is for the CWG to review and comment on this response before (and possibly during) the meeting on Tuesday next week such that we get ourselves
into a position to provide a thorough response to the current CCWG proposal. </span>
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">In addition to communicating our response to the CCWG via the Co-chairs, we also plan to submit the final document into the public comment forum before
21 December and to provide it to the CCWG chartering organisations.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Therefore, please provide any feedback or suggested edits as soon as you are able to properly review the document.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Thank-you</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Jonathan</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> Flanagan, Sharon [<a href="mailto:sflanagan@sidley.com" target="_blank">mailto:sflanagan@sidley.com</a>]
<br>
<b>Sent:</b> 11 December 2015 06:57<br>
<b>To:</b> Client Committee <<a href="mailto:cwg-client@icann.org" target="_blank">cwg-client@icann.org</a>><br>
<b>Subject:</b> [client com] CWG Comment Letter to CCWG 3rd Draft Proposal<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Dear Client Committee,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Attached is a draft of the CWG comment letter on the 3<sup>rd</sup> CCWG draft proposal. We will leave it to you to forward along to the CWG.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Holly and Sharon</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:cwg-client-bounces@icann.org" target="_blank">cwg-client-bounces@icann.org</a> [<a href="mailto:cwg-client-bounces@icann.org" target="_blank">mailto:cwg-client-bounces@icann.org</a>]
<b>On Behalf Of </b>Grace Abuhamad<br>
<b>Sent:</b> Thursday, December 03, 2015 8:00 AM<br>
<b>To:</b> Client Committee<br>
<b>Subject:</b> [client com] Call next week and approved project</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black">Dear Sidley team, </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black">Below is a note from the Chairs outlining a process for review of the CCWG-Accountability dependencies. Following on the process for the CCWG’s 2nd Public Comment, the Chairs suggested to the CWG-Stewardship that Sidley
assist with tracking these dependencies. During the CWG-Stewardship meeting today (archived
<a href="https://community.icann.org/x/kbpYAw" target="_blank">here</a>), the group approved instruction to Sidley for this project. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black">The request is for Sidley to work on item #1 and have in mind that the CWG-Stewardship will be requesting item #2 as an update in the future. I’ve copied the two items directly below for your convenience: </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in">
<span style="font-size:10.5pt;color:black">1.</span><span style="font-size:7.0pt;color:black">
</span><i><span style="font-size:10.5pt;color:black">Review the CCWG proposal put out for public comment and then submit confirmation to the public comment that the CCWG proposal does meet the CWG conditionality (if indeed it does) and; </span></i><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in">
<span style="font-size:10.5pt;color:black">2.</span><span style="font-size:7.0pt;color:black">
</span><i><span style="font-size:10.5pt;color:black">Confirm that the final proposal (to be prepared following the public comment period) continues to meet the CWG conditionality (if indeed it does).</span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black">Ideally, this work should be ready for the CWG-Stewardship call on 15 December so that the CWG-Stewardship can review and make its submission to the CCWG-Accountability Public Comment thereafter. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black">I’m sending this note on behalf of the Client Committee due to the relative urgency of the project. To discuss other approved projects, the Client Committee proposes a teleconference next week. Please reply to indicate
any times/dates for which you are unavailable and we will schedule accordingly. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black">Thank you, </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black">Grace</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<b><span style="color:black">From: </span></b><span style="color:black"><<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>> on behalf of Jonathan Robinson <<a href="mailto:jrobinson@afilias.info" target="_blank">jrobinson@afilias.info</a>><br>
<b>Organization: </b>Afilias<br>
<b>Reply-To: </b>Jonathan Robinson <<a href="mailto:jrobinson@afilias.info" target="_blank">jrobinson@afilias.info</a>><br>
<b>Date: </b>Friday, November 27, 2015 at 10:02 AM<br>
<b>To: </b>"<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>" <<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>><br>
<b>Subject: </b>[CWG-Stewardship] A process to resolve CWG Stewardship dependencies on CCWG Accountability</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">All,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">During our CWG meeting last week, we were unable to deal fully with the topic of the CCWG on ICANN accountability in so far as it is directly relevant to the work of this group.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">In particular, confirming the process to deal with the fact that the CWG Stewardship response to the ICG is expressly conditioned on the CCWG Accountability proposal.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">The CCWG have had a formal <a href="https://www.icann.org/news/blog/ccwg-accountability-issues-formal-update-on-progress-made-in-and-after-icann54-in-dublin" target="_blank">
update</a> out for a while now, ahead of publication of their 3<sup>rd</sup> draft proposal which is due out on Monday, November 30<sup>th</sup>.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">We propose to utilise the services of Sidley Austin to confirm that the CCWG Accountability proposal does indeed meet the conditionality requirements of the CWG Stewardship. As you will recall, Sidley reviewed the previous CCWG proposal
and assisted similarly.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">Moreover, we propose to undertake this work in two stages:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p style="margin-left:1.0in"><span style="color:black">1.</span><span style="font-size:7.0pt;color:black">
</span><span style="color:black">Review the CCWG proposal put out for public comment and then submit confirmation to the public comment that the CCWG proposal does meet the CWG conditionality (if indeed it does) and
</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span style="color:black">2.</span><span style="font-size:7.0pt;color:black">
</span><span style="color:black">Confirm that the final proposal (to be prepared following the public comment period) continues to meet the CWG conditionality (if indeed it does).</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">We believe that by working in this way, we will be able to</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p style="margin-left:1.0in"><span style="color:black">A.</span><span style="font-size:7.0pt;color:black">
</span><span style="color:black">Assist the CCWG by clearly communicating our position at the key stages. As we have done throughout the course of their work</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span style="color:black">B.</span><span style="font-size:7.0pt;color:black">
</span><span style="color:black">Assist the CCWG chartering organisations at key stages of their processes such that the they will be able to review the proposal and make their respective decisions with clear knowledge of the CWG position.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">We look forward to working with the CWG on this and other matters over the forthcoming weeks.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">Thank-you.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">Lise & Jonathan</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">Lise Fuhr & Jonathan Robinson</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">Co-chairs, CWG Stewardship</span><o:p></o:p></p>
</div>
</div>
<p> <o:p></o:p></p>
<p>****************************************************************************************************<br>
This e-mail is sent by a law firm and may contain information that is privileged or confidential.<br>
If you are not the intended recipient, please delete the e-mail and any attachments and notify us<br>
immediately.<br>
<br>
****************************************************************************************************<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><CWG Comment Letter.docx><o:p></o:p></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><Untitled attachment 00135.txt><o:p></o:p></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>