<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
{font-family:inherit;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
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:707146854;
mso-list-template-ids:-474586636;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
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">Others may have already pointed this out but, in case not, I will do so. It is true that SOs and ACs appoint ICANN Board directors but, according to the Bylaws,
it is not accurate to say that those directors represent their respective SOs and ACs.<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>
<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>Kris Seeburn<br>
<b>Sent:</b> Thursday, October 23, 2014 2:19 PM<br>
<b>To:</b> cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">@ Seun : I stand corrected but the SO/ACs have representation on the ICANN board already so the representation is there. What i am tempted to see going forward really is to formalise a council or whatever between the main groups on the
CWG as it is right now with chairs and whatever to have a structure of oversight on IANA.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">@ All: I would love to see IANA as an entity independent completely and we ascertain an oversight on it via some process or entity. If we do that the challenges of administration and costs etc., would get in the process which ICANN happily
does today. If we turn it around and say we work on developing an Entity that keeps only an oversight role having all CWGs together as we work on setting up a common Policy Development Process within the CWG to ascertain that the varied groups are doing a
common force of work. That could just play the bit. We ensure a leadership of an Entity group and this same entity group creates an influx for the PDP which would replicate the RIR process for the PDP but should be enough to ensure that there is a clear and
transparent process where issues arise.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kris<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Oct 23, 2014, at 9:49 PM, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">+1. Just to also mention that this route may even complicate things further. One of the questions govt would ask the ccNSO is "who made you Lord over us to sign a contract on our
behalf"<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I think the more we think that contract is the only way forward, the more we loose focus on the main point of weakness which is the names PDP; how can we ensure that the names PDP
gets strengthened and immune from ICANN board interference as much as possible is the puzzle for me. This is one of the reasons why the numbers PDP has progressed for so long (not just because it has membership). One way to approach this could be to consider
having actual representation of the relevant SO/AC on the board. That way the community will indirectly have an oversight on the implementation of policies they have created.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Nevertheless, having an ultimate jury that can come to the rescue if ICANN becomes so out of control (which is improbable) is a good thing to consider. Thinking about this I wonder
if IETF (being a longer historical source) will not fit for such role.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Cheers!<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">sent from Google nexus 4<br>
kindly excuse brevity and typos.<o:p></o:p></p>
<div>
<p class="MsoNormal">On 23 Oct 2014 18:13, "Guru Acharya" <<a href="mailto:gurcharya@gmail.com">gurcharya@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">I'm not versed with US law, but at the face of it, I see a few anomalies in Becky's suggestion that an unincorporated entity (comprising of CCNSO & GNSO) can enter into a SLA contract with ICANN.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Firstly, the parallel/analogy with NFL is flawed.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Even though NFL is an unincorporated association, the 32 independent teams that comprise the unincorporated association are legal entities. These 32 legal entities then collectively enter to into pooled-rights contract with any third party.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In comparison, CCNSO and GNSO are not legal entities; and they can not form an unincorporated association.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Oct 23, 2014 at 9:39 PM, Burr, Becky <<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>> wrote:<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The law varies from jurisdiction to jurisdiction, but in the US, the question is whether there is an enforceable contract and not whether one of the contracting parties is
a formal legal entity. I can assure you, the NFL enforces contracts all the time.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">J. Beckwith Burr</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-bottom-alt:auto"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Neustar, Inc. /</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif""> Deputy General Counsel and Chief
Privacy Officer</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">1775 Pennsylvania Avenue NW, Washington, DC 20006</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Office</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">:
<a href="tel:%2B%201.202.533.2932" target="_blank">+ 1.202.533.2932</a> <span style="color:#068658"> Mobile</span>:
<a href="tel:%2B1.202.352.6367" target="_blank">+1.202.352.6367</a> <span style="color:#068658">/ <a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a> /
<a href="http://www.neustar.biz/" target="_blank">www.neustar.biz</a></span></span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><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:11.0pt;font-family:"Calibri","sans-serif"">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Allan MacGillivray <<a href="mailto:allan.macgillivray@cira.ca" target="_blank">allan.macgillivray@cira.ca</a>><br>
<b>Date: </b>Thursday, October 23, 2014 at 12:04 PM<br>
<b>To: </b>Becky Burr <<a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a>>, Milton L Mueller <<a href="mailto:mueller@syr.edu" target="_blank">mueller@syr.edu</a>>, Fouad Bajwa <<a href="mailto:fouadbajwa@gmail.com" target="_blank">fouadbajwa@gmail.com</a>><br>
<b>Cc: </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>RE: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Becky – you raise a very important point as to whether unincorporated entities can enter
into enforceable contracts. If they can, it may simplify things considerably e.g. have ccNSO, GNSO, ALAC? 'take over’ the contact with ICANN. I had been labouring under the assumption that the ccNSO, GNSO would have to incorporate to do this. How can we
get clarity on this?</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Allan
</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-CA"><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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Burr, Becky<br>
<b>Sent:</b> October-23-14 11:43 AM<br>
<b>To:</b> Milton L Mueller; Fouad Bajwa<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities</span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA"> <o:p></o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Rather than starting with legal constructs, let’s begin by talking about what we need to accomplish
requisite accountability. To me, we need some independent committee, council, unincorporated association, or representative group to have a contract with ICANN/IANA for performing IANA functions consistent with SLA’s to be negotiated and documented. We need
this entity, presumably representative of IANA service consumers, to have recourse if the SLA’s are not met. </span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif"">If this is correct, then we can look at what kind of legal entity we need for the “SLA Council.” Seems
to me that the core of this group would be registry operators, perhaps with representation from other stakeholders like registstrars, registrants, etc. Could be stand alone or perhaps housed in ISOC or the IETF? I am pretty sure that unincorporated associations
can enter into enforceable contracts, etc. (For example, the National Football League in the US is actually an unincorporated association).</span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Second, we need a mechanism that ensure recourse and redress for a registry that is wrongfully revoked,
delegated, etc. That mechanism can be provided to all through the ICANN bylaws, e.g., as an independent review.</span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:9.0pt;font-family:"Arial","sans-serif"">J. Beckwith Burr</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-CA" style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Neustar, Inc. /</span></b><span lang="EN-CA" style="font-size:9.0pt;font-family:"Arial","sans-serif""> Deputy
General Counsel and Chief Privacy Officer</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:9.0pt;font-family:"Arial","sans-serif"">1775 Pennsylvania Avenue NW, Washington, DC 20006</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Office</span><span lang="EN-CA" style="font-size:9.0pt;font-family:"Arial","sans-serif"">:
<a href="tel:%2B%201.202.533.2932" target="_blank">+ 1.202.533.2932</a> <span style="color:#068658"> Mobile</span>:
<a href="tel:%2B1.202.352.6367" target="_blank">+1.202.352.6367</a> <span style="color:#068658">/ <a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a> /
<a href="http://www.neustar.biz/" target="_blank">www.neustar.biz</a></span></span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-CA"><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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:
</span></b><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Milton L Mueller <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailto-3Amueller-40syr.edu&d=AAMFAw&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=9jEM_hACGXiATouHvV-V_jUNH5sc3y-bQFzqRD4_qRU&s=WD5mnQGH8gOzXMllT3aJRt_wLg7aZMZR0oiM_ERgS0g&e=" target="_blank">mueller@syr.edu</a>><br>
<b>Date: </b>Thursday, October 23, 2014 at 11:17 AM<br>
<b>To: </b>Fouad Bajwa <<a href="mailto:fouadbajwa@gmail.com" target="_blank">fouadbajwa@gmail.com</a>><br>
<b>Cc: </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>Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities</span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Fouad:</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">By the “technical community proposals” I assume you mean the protocols community.
</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What your argument misses is that IANA _<i>is</i>_ a separate organizational entity for both the
numbers and protocols communities. </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The protocol community has an MoU with ICANN that authorizes ICANN to perform the IANA functions
for them. That MoU can be revoked, and IETF can decide to use someone else. That is the perfect accountability mechanism. Now, tell me how the names community achieves that same wonderful state? There are two ways to do it: pull the IANA out of ICANN, or set
up a new contracting authority to replace the NTIA, which could periodically award the contract to ICANN or to anyone else qualified.
</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">No one wants “the IANA technical and policy functions [might] fall into the hands and whims of governments.”
That in fact is a requirement imposed on the transition by the NTIA. But we do need to make significant organizational changes if we are to meet the requirement of accountability. I think scare talk about take overs can divert our attention from needed reforms
and I would resist that kind of talk. </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a name="1493dffcebd90b2e_1493dc613f878322__MailE"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></a><span lang="EN-CA"><o:p></o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I don't think that IANA should be evolved as a separate entity at all and create new opportunities for bureaucracies for governments and industry control. <span lang="EN-CA"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The technical community proposals are highly reasonable to not make such a big fuss out of it and help IANA transition under a body that is somewhat messed up but can be improved
in the long run however, ICANN would need some changes. <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The technical community has also shown its concern that it doesn't want the IANA technical and policy function to fall into the hands of the whims of governments because it functions
to the technical community's needs adequately in its present environment and role. <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Your challenge and for the ICG is to propose that most transparent and accountable way forward that ensures an open and inclusive relationship with the Internet community treating
stakeholders in their respective roles but not giving preference to one group over another another. I don't have to go through the Internet Governance ideals over and over again here.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">First ICANN Board control as the final word for IANA affairs would have to be reviewed and should be taken into a broader community review process. I do not trust the ICANN Board
to be able to manage both ICANN and IANA in a transparent and accountable way, their progress over the years has had its own set of troubles already. <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The proposals are interesting but not the final word. The final word will remain with NTIA and thats my concern from a developing country member citizen perspective. I am going
through a great deal of suggestions and proposals and all show a similar aspect, don't disturb the IANA technical function and the policies for IANA developed by the community have work so far but require more transparency, accountability and functional relationships
with the community ensuring open and inclusive participation in its policy development processes. <span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On Thu, Oct 23, 2014 at 7:27 PM, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<span lang="EN-CA"><o:p></o:p></span></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" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">+1 Option 2 is preferred from my end also. However i also added Option 4 as a second preference just incase things get delayed with the accountability process.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Cheers!<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On Thu, Oct 23, 2014 at 3:15 PM, Olivier MJ Crepin-Leblond <<a href="mailto:ocl@gih.com" target="_blank">ocl@gih.com</a>> wrote:<span lang="EN-CA"><o:p></o:p></span></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>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hello all,<br>
<br>
you might wish to see an expanded set of "Options", in a Google Doc which has been shared.<br>
<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1B46mlsyZUFF4bZfeWgGCdqIQHCP2BMOy4KZU4RiRiE8_edit-3Fusp-3Dsharing&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=fUDcpKHcSBfPHc8c3PFUK3EGMl9QAYJOV5JFJEPECSo&e=" target="_blank">https://docs.google.com/document/d/1B46mlsyZUFF4bZfeWgGCdqIQHCP2BMOy4KZU4RiRiE8/edit?usp=sharing</a><br>
<br>
So far, I note that the majority of our participants on the At-Large IANA Issues WG appears to prefer Option 2.<br>
<br>
Kind regards,<br>
<br>
Olivier<span lang="EN-CA"><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
<br>
<span lang="EN-CA"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On 15/10/2014 22:55, Olivier MJ Crepin-Leblond wrote:<span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
</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">FYI<span lang="EN-CA"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
<br>
-------- Forwarded Message -------- <span lang="EN-CA"><o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td nowrap="" valign="top" style="padding:0in 0in 0in 0in">
<p class="MsoNormal" align="right" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right">
<b>Subject: </b><o:p></o:p></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">[CWG-Stewardship] Names Community vs the other two communities<o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0in 0in 0in 0in">
<p class="MsoNormal" align="right" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right">
<b>Date: </b><o:p></o:p></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Thu, 16 Oct 2014 02:40:47 +0530<o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0in 0in 0in 0in">
<p class="MsoNormal" align="right" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right">
<b>From: </b><o:p></o:p></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Guru Acharya
<a href="mailto:gurcharya@gmail.com" target="_blank"><gurcharya@gmail.com></a><o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0in 0in 0in 0in">
<p class="MsoNormal" align="right" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right">
<b>To: </b><o:p></o:p></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <span lang="EN-CA"><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">How the names community approach will differ from the approach adopted by the numbers community and protocols community?<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Numbers Community: APNIC has reached consensus on its proposal. According to the proposal, IANA will continue to reside in ICANN. It proposes to replace NTIA oversight with a Service
Level Agreement (SLA) and Affirmation of Commitment (AOC) between NRO and ICANN.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.slideshare.net_fullscreen_apnic_report-2Dianatransition_1&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=ipQr6NSV4s2YyeTKtleRzaehK6NnJP70z0QOuy57W7o&e=" target="_blank">www.slideshare.net/fullscreen/apnic/report-ianatransition/1</a><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Protocols Community: The IETF draft proposal suggests that no structural changes are required as a result of the transition. The MOU between ICANN and the IETF community will continue
to govern the existing relationship. Again, IANA will continue to reside in ICANN.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__tools.ietf.org_html_draft-2Dietf-2Dianaplan-2Dicg-2Dresponse-2D00&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=hsoL84pOSYzJR4QRMfhJYR6ybddmed3Zi1M-kuVH5uQ&e=" target="_blank">http://tools.ietf.org/html/draft-ietf-ianaplan-icg-response-00</a><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Therefore, neither the numbers community, nor the protocol community appear to be in the direction of suggesting a new MS Oversight Entity to replace NTIA and its oversight. Merely
contracts between existing entities will be updated to replace NTIA oversight.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Can the names community adopt a similar approach? Can a contractual agreement (SLA/AOC/MOU) between ICANN and GNSO/CCNSO be expected to replace NTIA oversight?<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Clearly NO! This approach can not be adopted by the names community because the names community resides within ICANN, which is also the IANA operator. Specifically, GNSO and CCNSO
are essentially subsets of ICANN, and therefore a contractual agreement (SLA/AOC/MOU) between ICANN and GNSO/CCNSO can not be expected to replace NTIA oversight.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Therefore, it is essential to either<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Option (i): create a new legal entity, which has a contractual oversight relationship with ICANN. This would be similar to <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.internetgovernance.org_2014_08_04_students-2Dschool-2Dfaculty-2Don-2Diana-2Dtransition-2Dthe-2Dmeissen-2Dproposal_&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=HC19PauLIvR68L1aaQZMUV1ysZRdzy1Rku_FhtwR4P0&e=" target="_blank">http://www.internetgovernance.org/2014/08/04/students-school-faculty-on-iana-transition-the-meissen-proposal/</a><span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Option (ii): expect ICANN to self-regulate<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Option (iii): make a new legal entity comprising of CCNSO and GNSO that is structurally independent of ICANN and require that new entity to enter into a contractual oversight agreement
(SLA/AOC/MOU) with ICANN.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">From the above three options, clearly option (ii) is not acceptable because of the lack of trust in the ICANN enhanced accountability process.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I also feel that option (iii) is not feasible because the CCNSO and GNSO are heavily integrated with ICANN and structural separation of these two communities from ICANN will be
in-feasible.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Also, from the Jordan Carter document, the option on page 7 can be discarded, which makes ICANN the oversight body, as IANA will continue to reside in ICANN, as clearly suggested
by the proposals of the protocols and numbers community.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Therefore, option (i) is clearly the only option available with the names community.<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Regards,<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Acharya<span lang="EN-CA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
<br>
<span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
<pre>_______________________________________________<span lang="EN-CA"><o:p></o:p></span></pre>
<pre>Iana-issues mailing list<span lang="EN-CA"><o:p></o:p></span></pre>
<pre><a href="mailto:Iana-issues@atlarge-lists.icann.org" target="_blank">Iana-issues@atlarge-lists.icann.org</a><span lang="EN-CA"><o:p></o:p></span></pre>
<pre><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_iana-2Dissues&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=z-dUNEELhtQ-yVDbG2261BTmwYXpCqVfPM_t-PljY5Q&e=" target="_blank">https://mm.icann.org/mailman/listinfo/iana-issues</a><span lang="EN-CA"><o:p></o:p></span></pre>
</blockquote>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
<br>
<span lang="EN-CA"><o:p></o:p></span></p>
<pre>-- <span lang="EN-CA"><o:p></o:p></span></pre>
<pre>Olivier MJ Crépin-Leblond, PhD<span lang="EN-CA"><o:p></o:p></span></pre>
<pre><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.gih.com_ocl.html&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=u0-58tAisZxOIbFv-8rGIWKmmQ0MbrreYyVITk4iFgM&e=" target="_blank">http://www.gih.com/ocl.html</a><span lang="EN-CA"><o:p></o:p></span></pre>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
_______________________________________________<br>
Iana-issues mailing list<br>
<a href="mailto:Iana-issues@atlarge-lists.icann.org" target="_blank">Iana-issues@atlarge-lists.icann.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_iana-2Dissues&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=z-dUNEELhtQ-yVDbG2261BTmwYXpCqVfPM_t-PljY5Q&e=" target="_blank">https://mm.icann.org/mailman/listinfo/iana-issues</a><span lang="EN-CA"><o:p></o:p></span></p>
</blockquote>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
<br clear="all">
<br>
-- <span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">------------------------------------------------------------------------<span lang="EN-CA"><o:p></o:p></span></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">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><i><span style="font-family:"Garamond","serif";color:#006600">Seun Ojedeji,<br>
Federal University Oye-Ekiti<br>
web: </span></i><i><span style="font-family:"Garamond","serif";color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fuoye.edu.ng&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=ZYONh-kEmB5dv3rzYIFWLLSMsZ6JohvhU3mRuNA0IvA&e=" target="_blank">http://www.fuoye.edu.ng</a><br>
</span></i><i><span style="font-family:"Garamond","serif";color:#006600">Mobile: <a href="tel:%2B2348035233535" target="_blank">
+2348035233535</a></span></i><i><span style="font-family:"Garamond","serif";color:#888888"><br>
</span></i><i><span style="font-family:"Garamond","serif";color:#006600">alt email:<a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><span lang="EN-CA"><o:p></o:p></span></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">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Garamond","serif";color:#888888">The key to understanding is humility - my view !</span><span lang="EN-CA"><o:p></o:p></span></p>
</blockquote>
</blockquote>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
_______________________________________________<br>
Iana-issues mailing list<br>
<a href="mailto:Iana-issues@atlarge-lists.icann.org" target="_blank">Iana-issues@atlarge-lists.icann.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_iana-2Dissues&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=z-dUNEELhtQ-yVDbG2261BTmwYXpCqVfPM_t-PljY5Q&e=" target="_blank">https://mm.icann.org/mailman/listinfo/iana-issues</a><span lang="EN-CA"><o:p></o:p></span></p>
</blockquote>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
<br clear="all">
<span lang="EN-CA"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="EN-CA"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
<br>
Regards.<br>
--------------------------<br>
Fouad Bajwa<br>
ICT4D and Internet Governance Advisor<br>
My Blog: Internet's Governance: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__internetsgovernance.blogspot.com_&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=zkexu-3haN6fnsOXhCc6YlS9R1_kJqU41Ly9Qg6NDw8&e=" target="_blank">
http://internetsgovernance.blogspot.com/</a><br>
Follow my Tweets: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_fouadbajwa&d=AAMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=iSr26xOvv_x1A2nuUqvtaRwVOgTvzV0efqUDkGy07cw&s=Q41AU5yY9bUlqSxfJs-fCoCh4KuNHdFYeG8IwC5gisw&e=" target="_blank">
http://twitter.com/fouadbajwa</a><span lang="EN-CA"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</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>
</div>
<p class="MsoNormal">_______________________________________________<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">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Kris Seeburn<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:seeburn.k@gmail.com">seeburn.k@gmail.com</a><o:p></o:p></p>
</div>
<div>
<ul style="margin-top:0in;outline: 0px;display:table-cell" type="disc">
<li class="MsoNormal" style="color:#333333;line-height:14.4pt;mso-list:l0 level1 lfo1;vertical-align:top;outline: 0px;font-style:inherit;font-variant:inherit">
<a name="webProfileURL"></a><a href="http://www.linkedin.com/in/kseeburn/" title="View public profile"><span style="font-size:8.5pt;font-family:"inherit","serif";color:#666666;border:none windowtext 1.0pt;padding:0in;text-decoration:none">www.linkedin.com/in/kseeburn/</span></a><span style="font-size:8.5pt;font-family:"inherit","serif""><o:p></o:p></span></li></ul>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>