<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: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;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-IE 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'>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'>I’ll do what I can to answer the questions. As you say, others may have a view.<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'>Please seen inline below.<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'>Trust that’s helpful.<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'>Jonathan<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><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'> Seun Ojedeji [mailto:seun.ojedeji@gmail.com] <br><b>Sent:</b> 12 April 2016 06:47<br><b>To:</b> cwg-stewardship@icann.org<br><b>Subject:</b> Re: [CWG-Stewardship] Notes, Recordings, Transcript CWG IANA Bylaws Review Meeting | 11 April 2016<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p>Dear Co-Chairs,<o:p></o:p></p><p>Will be good to hear response to my questions (bearing in mind the update provided by Grace).<o:p></o:p></p><p>Regards<br>PS: Anyone who has a clear understanding may help as well.<o:p></o:p></p><p>Sent from my LG G4<br>Kindly excuse brevity and typos<o:p></o:p></p><div><p class=MsoNormal>On 11 Apr 2016 19:55, "Seun Ojedeji" <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p>Sent from my LG G4<br>Kindly excuse brevity and typos<br>On 11 Apr 2016 6:39 p.m., "Brenda Brewer" <<a href="mailto:brenda.brewer@icann.org" target="_blank">brenda.brewer@icann.org</a>> wrote:<br>><br>><br>> · Question 9: change to reflect confirmation of the question: CSC liaison is intended to come from RrSG or NCSG. Only restriction is <br>> that this not be from a gTLD registry. <br>><br>SO: That there is still a "or" between NCSG and RrSG makes me wonder what this mean in practice; that NCSG will not appoint if RrSG appointed a liaison first or the other way round?<o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>As per the proposal, Registries substantially determine the composition of the CSC. IMO, the purpose of Liaison is to provide others in the GNSO with opportunity to monitor and interact with CSC. Liaison therefore to come from GNSO but not from Registries (i.e. NCPH or RrSG)<o:p></o:p></span></p><p>Secondly, what's the use of a liaison since the DUO are components of the GNSO. I have not gone to the proposal to check if this is inline but it seem like an overkill to me.<o:p></o:p></p><p>> · Question 10: no change. <br>><br>> · Question 11: the "it may be appropriate" section can be placed in the Charter. It is not for inclusion in Bylaws. <br>><br>> · Question 12: no change. <br>><br>> · Question 13: We can keep the clarification and refer to the original text as inclusive of the broader community of 'consumers'. <br>><br>SO: sounds more broadly inclusive and clear than the alternative.<o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Agreed<o:p></o:p></span></p><p>Or an <br>> alternative: direct customers of the naming services" (text used for CSC). That text is as follows: "Any necessary additions to the <br>> IANA SOW to account for the needs of the consumers of the IANA naming functions [and/or] the ICANN community at large". <br>><br>> Question 22: no support for defining a simple majority. There is support for use of consensus. The CWG-Stewardship <br>> proposal states that the SCWG would follow the stndards established by the CCWG-Principles. <br>><o:p></o:p></p><p>SO: Is this referring to the current CCWG framework open for PC or principles that will be set in the charter of each CCWG? If the former then fine(although I would note that having such mindset early would have been a good thing), however if it's the later I guess the high-level principles of the SCWG is indeed what we are discussing and I don't think it's something to be determined later.<o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>CWG proposal (para. 391, p. 91) says:<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>“The SCWG will follow the overall guidelines and procedures for ICANN Cross Community Working Groups.”<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I read this to be such guidelines (for CWGs) that are in place or developed from time to time. Therefore I read this to be the (outcome) of the former i.e. the CCWG-Principles has draft guidelines currently out for public comment.<o:p></o:p></span></p><p>Regards<o:p></o:p></p><p>> · Question 24: no change<br>><br>> · Other comments: Sharon has one question regaring 18.4a. Will reach out to Avri and Matt to clarify. <br>><br>> · Paul Kane noted concerns with consistency in Bylaws language and focus on gTLDs. <br>><br>> Action (Sharon): Reach out to Avri and Matt with Client Committee in copy about language in 18.4a. <br>><br>> 2. AOB<br>><br>> Next meeting (Thursday 14 April at 16:00 UTC). Group may not need a meeting on Thursday. The implementation update and other items <br>> may be able to be provided via email. <br>><br>> Action (Chairs): Due to time constraints on this call, Chairs will discuss and revert back to group with next steps. <br>><br>> <br>><br>><br>> _______________________________________________<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><br>><o:p></o:p></p></blockquote></div></div></body></html>