<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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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 lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I agree 100%. If we cannot meet the bylaw requirements the right answer is to begin a process to change the bylaws – not for any part of the ICANN organization to unilaterally seek to waive them. More to the point, I don’t think that bylaws provisions are “waivable.” Without conformance to bylaws requirements, any subsequent action taken is illegitimate and likely subject to successful legal challenge<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Paul<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Paul Rosenzweig<o:p></o:p></p><p class=MsoNormal><a href="mailto:paul.rosenzweig@redbranchconsulting.com"><span style='color:#0563C1'>paul.rosenzweig@redbranchconsulting.com</span></a><o:p></o:p></p><p class=MsoNormal>O: +1 (202) 547-0660<o:p></o:p></p><p class=MsoNormal>M: +1 (202) 329-9650<o:p></o:p></p><p class=MsoNormal>VOIP: +1 (202) 738-1739<o:p></o:p></p><p class=MsoNormal><a href="http://www.redbranchconsulting.com/"><span style='color:#0563C1'>www.redbranchconsulting.com</span></a><o:p></o:p></p><p class=MsoNormal>My PGP Key: <a href="https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA066684"><span style='color:#0563C1'>https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA066684</span></a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>From:</b> NCSG-Discuss <NCSG-DISCUSS@LISTSERV.SYR.EDU> <b>On Behalf Of </b>Tomslin Samme-Nlar<br><b>Sent:</b> Wednesday, January 9, 2019 4:55 PM<br><b>To:</b> NCSG-DISCUSS@LISTSERV.SYR.EDU<br><b>Subject:</b> Re: [Consultation] Request for Resolution of IFRT Issues<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>What I find strange is that by accepting the ccNSO proposal, we'll have a team that doesn't meet ICANN bylaws' requirements, performing a review in accordance with a scope specified in the ICANN Bylaws.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>I couldn't find the rationale behind the requirement of a third ccNSO representative not being a ccNSO ccTLD member, but I am of the opinion that if the membership of the IFR team doesn't respect the bylaws requirements, the credibility of their output might be undermined in the community.<o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'>Cheers,<br>Tomslin<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Thu., 10 Jan. 2019, 00:11 Kris Seeburn <<a href="mailto:seeburn.k@gmail.com">seeburn.k@gmail.com</a> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal>I fully agree on this stand. It does not solve the immediate situation but do we always have someone immediately? Day after day I see Icann going into what I cannot imagine. Although things have started going way south some time back but I stand with ``James on this stand we need to be strong and not permit people playing around. If so why was a bylaws even put in place. We may as well be Mickey Mouse all the way through. Things are serious and we have to push for a respectful and strong stand and not play on this game. Next time another story will come up. It is a time to put stops and as we say checks and balances are important and it Becomes easy to play when you create precedence.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We all know what happens once precedence happens we play it on and on. That is my thinking process. I rarely state my mind and thoughts being pointed fingers but we need to stop those plays please and respect what is laid down. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>`````else we do another shutdown for an imaginary wall<o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black'>Kris Seeburn <br><a href="mailto:seeburn.k@gmail.com" target="_blank">seeburn.k@gmail.com</a><o:p></o:p></span></p></div><p class=MsoNormal><img border=0 width=32 height=32 style='width:.3333in;height:.3333in' id="m_64648521984431145745EB5240-A81E-4DB0-B531-713151EB810B" src="cid:4C68CF68-F5C8-444B-A031-61D097CFE11D"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black'><a href="http://linkedin.com/in/kseeburn/" target="_blank">linkedin.com/in/kseeburn/</a><br><br>"Life is a Beach, it all depends at how you look at it"<br><br></span><img border=0 width=32 height=32 style='width:.3333in;height:.3333in' id="m_646485219844311457C5B78A14-EC3C-485F-A37F-DBB7AABDDE35" src="cid:2B3C052F-D6B4-4773-9116-D703ACE1C1A9"><o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 9 Jan 2019, at 16:35, James Gannon <<a href="mailto:james@CYBERINVASION.NET" target="_blank">james@CYBERINVASION.NET</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>This is an important message, and we need to take a very strong stand here that the bylaws must be implemented as written, the ccNSO needs to fulfil its bylaws mandate and staff the IFR correctly.<o:p></o:p></p></div><div><p class=MsoNormal>We cannot continue to undermine the accountability mechanisms we created and agreed to during the IANA strwardship as we already have done with the AoC reviews. I hope this can be passed along to our councillors.<o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 9 Jan 2019, at 13:19, Rafik Dammak <<a href="mailto:rafik.dammak@GMAIL.COM" target="_blank">rafik.dammak@GMAIL.COM</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hi all, <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I am sharing here a communication sent by ICANN GDD asking from community input regarding 2 issues raised with the IANA Naming Function Review Team formation. More details about the 2 issues are in the attached documents.<o:p></o:p></p></div><div><p class=MsoNormal>looking forward to hear from you if there is any issue with the proposed options. In particular, those who were involved in the IANA Stewardship transition CWG may give some insights here.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Rafik<o:p></o:p></p><div><div><p class=MsoNormal>---------- Forwarded message ---------<br>From: <strong><span style='font-family:"Calibri",sans-serif'>Drazek, Keith via council</span></strong> <br>Date: mar. 8 janv. 2019 à 08:15<br>Subject: [council] FW: Request for Resolution of IFRT Issues<br>To: <o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi all,<o:p></o:p></p><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'>Please see the attached request from ICANN for community input on two membership appointment issues currently facing the IANA Naming Functions Review Team – one related to a geographical diversity requirement, and the other a ccTLD-facing representation concern. Both issues are in play due to the new ICANN bylaws language and requirements related to the IFRT, so please review and advise if your SGs and Cs have views on a reasonable path forward. <o:p></o:p></p><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'>Thanks in advance.<o:p></o:p></p><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'>Regards,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Keith<o:p></o:p></p><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'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <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> Trang Nguyen <br><b>Sent:</b> Monday, January 07, 2019 11:55 AM<br><b>To:</b> <br><b>Subject:</b> [EXTERNAL] Request for Resolution of IFRT Issues<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'>Dear Chairs, Co-Chairs, and Executive Committee,<o:p></o:p></p><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'>Please see attached letter regarding two issues with the IANA Naming Function Review Team that we are requesting your organization help address.<o:p></o:p></p><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'>Best,<o:p></o:p></p><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'>Trang Nguyen<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Vice President, GDD Strategic Programs<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>ICANN<o:p></o:p></p><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'> <o:p></o:p></p></div></div></div></div></div><p class=MsoNormal><ccNSO_IFRT letter to appointing orgs[1].pdf><IFR Issues Resolution Request.pdf><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></blockquote></div></div></div></div></body></html>