<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: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;}
/* 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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{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;}
/* List Definitions */
@list l0
{mso-list-id:669721052;
mso-list-type:hybrid;
mso-list-template-ids:-690823116 201916431 201916441 201916443 201916431 201916441 201916443 201916431 201916441 201916443;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:54.0pt;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:90.0pt;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:126.0pt;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:162.0pt;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:198.0pt;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:234.0pt;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:270.0pt;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:306.0pt;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1379164591;
mso-list-type:hybrid;
mso-list-template-ids:-920475290 -1568010736 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l1:level1
{mso-level-start-at:0;
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;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{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;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{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;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
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-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi Seun,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Donna’s responses seem quite sound to me.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">If I may add my tuppence worth:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Most (all?) of the CSC stuff really needs a degree of flexibility. Remember that the CSC is an operational body – like a
contract or project manager. Its role is to ensure good performance and that failings are remedied (or at least understood). So the charter does need to be flexible and certainly should not be locked down in a bylaw – fundamental or standard. I’d even wonder
whether it should be detailed in the ICANN-PTI contract, except to note that it should be seen as the framework for resolving problems (or, if it fails to get issues remedied, to escalate).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">As such, while it
<i>might</i> be appropriate to make reference to the CSC in the bylaws, it should probably only be that the ccNSO and RySG/GNSO (delete as appropriate) should work together to establish such a committee.<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I also wonder how much needs to be written down in an ICANN-PTI contract. The main CSC role will be monitoring the performance
of PTI, in particular how well it is fulfilling it service level obligations (and understanding where there are problems associated with meeting them). The draft charter gives examples of escalation processes/steps. It is because I see a lot of escalation
to be a case-by-case decision (which is why I think that the action followed should not be too heavily specified. I think that this is the only place where I diverge a bit from Chuck’s analysis: CSC was conceived as a committee of experts from customer organisations
who would recognise where a failure was force majeure but of no serious consequence and when it was serious in implications and represented a systemic failure. I do not think that this can be written in bylaws or contracts satisfactorily.<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hence for the include in the ICANN-PTI contract I would be inclined to suggest:<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">An obligation on PTI to provide monthly reports to the CSC on performance against service level obligations and trends (with
an explanation of deterioration of performance or failure to comply)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">An obligation on PTI to discuss performance with the CSC on a monthly basis<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">An obligation on PTI and its Board to work with CSC to address problems<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">An obligation on ICANN to respond to the CSC, should the CSC consider it necessary to raise concerns directly with ICANN<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">A recognition that, should CSC not be able to address and resolve its concerns, it will escalate the issue(s) to the ccNSO
and GNSO for decisions on further action, if avenues to resolve issues have been tried and failed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I would agree that the CSC probably needs to develop its charter to cover remedial action and escalation, but I would note
that we should recognise that the DT-C work cited examples of the sort of processes that could be followed: I certainly do not see it as prescriptive except that it should seek to exhaust channels. Recognising as fundamental the role of CSC to help resolve
issues and giving <b>examples</b> of escalation action could be helpfully covered in the charter.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I’ve annotated the “staff analysis” spreadsheet with comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Martin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Austin, Donna<br>
<b>Sent:</b> 02 February 2016 23:45<br>
<b>To:</b> Seun Ojedeji <seun.ojedeji@gmail.com>; Jonathan Robinson <jrobinson@afilias.info><br>
<b>Cc:</b> cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] Update & Planning for Feb 4th Meeting of CWG<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi Seun<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">As the lead of the DT for the CSC, I’ve responded to your related questions inline below.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I would also welcome input from Martin who was also a member of the DT for the CSC.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Donna<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">
</span><a href="mailto:cwg-stewardship-bounces@icann.org"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">cwg-stewardship-bounces@icann.org</span></a><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">
[</span><a href="mailto:cwg-stewardship-bounces@icann.org"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">mailto:cwg-stewardship-bounces@icann.org</span></a><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">]
<b>On Behalf Of </b>Seun Ojedeji<br>
<b>Sent:</b> Tuesday, 2 February 2016 11:30 AM<br>
<b>To:</b> Jonathan Robinson <</span><a href="mailto:jrobinson@afilias.info"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">jrobinson@afilias.info</span></a><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Cc:</b> </span><a href="mailto:cwg-stewardship@icann.org"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">cwg-stewardship@icann.org</span></a><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Subject:</b> Re: [CWG-Stewardship] Update & Planning for Feb 4th Meeting of CWG<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-AU"><o:p> </o:p></span></p>
<p><span lang="EN-AU">Hello,<o:p></o:p></span></p>
<p><span lang="EN-AU">Thanks for the share, did a quick read and have a few general comments/question:<o:p></o:p></span></p>
<p style="margin-left:18.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo4"><![if !supportLists]><span lang="EN-AU" style="color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-AU">Isn't there a way to have the CSC charter separate and not incorporated into the bylaw as the bylaw is looking quite bulky. That said, I note that it's referred to as Annex D so I assume that is perhaps the
only reference that would exist in the bylaw?<span style="color:#1F497D"><o:p></o:p></span></span></p>
<p><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">DA COMMENT: I believe this is up for discussion of CWG members. While I think that it makes sense to have the existence of the CSC contained in the bylaws, the charter
itself could simply be referenced, particularly given it is envisioned that the Charter would be reviewed on a somewhat regular basis.
<o:p></o:p></span></p>
<p style="margin-left:18.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo4"><![if !supportLists]><span lang="EN-AU"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-AU">I believe any change in the CSC charter should involved other chartering SO/AC not just be based on the ccNSO and GNSO decision.<o:p></o:p></span></p>
<p><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">DA COMMENT: The mission of the CSC is to ensure continued satisfactory performance of the IANA Function for the direct customers of the naming services. The primary
role of the CSC is to monitor the performance of the IANA naming function against agreed service level targets on a regular basis. It was the view of the DT that as the direct customers of the naming services came from the ccNSO and GNSO, that any changes
to the Charter should only be ratified by those SOs. <o:p></o:p></span></p>
<p><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The Charter does provide for input from all ICANN stakeholders through the provision of a public comment period associated with an initial review of the Charter to
be conducted by representatives of the ccNSO and RySG after one year of the first meeting of the CSC. Any recommended changes are to be ratified by the ccNSO and GNSO.
<o:p></o:p></span></p>
<p><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The Charter also provides that “… thereafter, the Charter will be reviewed at the request of the CSC, ccNSO or GNSO and may also be reviewed in connection with the
IANA Function Review.” <o:p></o:p></span></p>
<p><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The Charter is currently silent on how any future reviews should be conducted and it may make sense that any review requested by the CSC, ccNSO or GNSO follow the
same form as the initial review in that it be conducted by representatives of the ccNSO and RySG and that the “… review is to include the opportunity for input from other ICANN stakeholders, via a Public Comment process.”
<o:p></o:p></span></p>
<p><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I believe that any review of the CSC Charter conducted in connection with the IANA Function Review has a separate process.
<o:p></o:p></span></p>
<p style="margin-left:18.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo4"><![if !supportLists]><span lang="EN-AU"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-AU">The CCWG proposed process to approve update of any text in the bylaw (including CSC charter) should be applied. So I think the charter update(depending on whether this will be standard or fundamental bylaw)
should be subject to board approval.<o:p></o:p></span></p>
<p><span lang="EN-AU" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">DA comment: The DT did not believe that Board approval was required for a change to the CSC Charter and I do not support any suggestion that this be changed at this
time.<o:p></o:p></span></p>
<p><span lang="EN-AU">4. Some of the decision making does not recognise other community like ALAC as part of the decision makers. For instance the decision process for SCWG.<o:p></o:p></span></p>
<p><span lang="EN-AU">5. Could it be indicated which of the texts goes to fundamental bylaw and which one to standard?<o:p></o:p></span></p>
<p><span lang="EN-AU">Regards<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-AU">On 2 Feb 2016 6:21 p.m., "Jonathan Robinson" <</span><a href="mailto:jrobinson@afilias.info"><span lang="EN-AU">jrobinson@afilias.info</span></a><span lang="EN-AU">> wrote:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE">All,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE">A couple of updates since our previous meeting and ahead of our meeting on Thursday Feb 4 @ 16h00 UTC.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE">We are waiting for the final wording from CWG Accountability in relation to our requirements on IANA Budget and IRP but now expect that these will be satisfactorily
dealt with.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE">As per Grace’s note on the CCWG agenda for their meeting today, these matters were subject to “final reading” by the CCWG today.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE">On the series of questions presented by Sidley in preparation for drafting the proposed ICANN Bylaws to deal with the work of the CWG Stewardship, Grace’s email
of Jan 25 sought further input from our group.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE">Essentially we have:<o:p></o:p></span></p>
<p><span lang="EN-IE">a.</span><span lang="EN-IE" style="font-size:7.0pt"> </span>
<span lang="EN-IE">Input from relevant DT leads (Thank-you!)<o:p></o:p></span></p>
<p><span lang="EN-IE">b.</span><span lang="EN-IE" style="font-size:7.0pt"> </span>
<span lang="EN-IE">Input from staff<o:p></o:p></span></p>
<p><span lang="EN-IE">c.</span><span lang="EN-IE" style="font-size:7.0pt"> </span>
<span lang="EN-IE">Remaining open questions<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE">Any input to point c above will be helpful.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE">The plan (as per our last meeting and captured in Grace’s email of Jan 25)
</span><span lang="EN-IE" style="font-size:10.5pt;color:black">was to review and provide input so that responses can be provided to Sidley after the Feb 4 Call.</span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black">This work to be done via the mailing list by using the ‘track changes’ feature in Word. Staff will monitor the list and manage
version control if needed. </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black">If there are outstanding issues, or disagreement on a response, this can be discussed further at the next meeting. </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black"> </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><u><span lang="EN-IE" style="font-size:10.5pt;color:red">If you are able to review the document (re-attached for convenience) and provide any input over the next 24 hours or so,
that will be very helpful.</span></u><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black"> </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black">Thank-you,</span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black"> </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black"> </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black"> </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black">Jonathan & Lise</span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black"> </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE" style="font-size:10.5pt;color:black"> </span><span lang="EN-IE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-IE"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-AU"><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
</span><a href="mailto:CWG-Stewardship@icann.org"><span lang="EN-AU">CWG-Stewardship@icann.org</span></a><span lang="EN-AU"><br>
</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_cwg-2Dstewardship&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=oZrItGoEGaS03omqLFaFXVQ6qZVX3ovRDY89oqmEWOc&s=_4RgEuOarPhzBaAGOAA6E3ZHasnvA6pw9ZAj1Io2hrI&e=" target="_blank"><span lang="EN-AU">https://mm.icann.org/mailman/listinfo/cwg-stewardship</span></a><span lang="EN-AU"><o:p></o:p></span></p>
</blockquote>
</div>
</div>
</body>
</html>