<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;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hey Seun,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A quick comment on this paragraph:<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">>Thanks for the explanation which was quite helpful. I must say the more i try to process this, the more it seem that the proposal attempts to practically create a new operator order than ICANN (re: PTI) being the operator and turns ICANN
to a "policy only" organisation. That seem like a major change in the Internet Corporation for Assigned Names and Numbers (ICANN) mission and purpose. How will this work with ccTLDs who for instance are practically engaging with ICANN just because it is the
IANA operator? how about existing gTLD contracts which were signed with the intent of ICANN being the operator?<br>
<br>
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think it’s important to remember that the IANA functions are not something that should be considered integral to ICANN, they are
<i>currently</i> operated by ICANN under contract from NTIA, and it has been repeated on a number of occasions that the concept of separability is very important to a large number of people involved in this process. I think it may be a dangerous road to go
down to suggest that IANA may never be moved out of ICANN as that would imply that any IANA accountability measures would have no recourse to move the IANA contract way from ICANN. If there are barriers to that separability then we need to example these as
part of any model that has a separability clause.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As has been developed within the RIR and IETF submissions, I think that it’s important that no matter what solution we end up deciding on that the ability for
the IANA functions to sustain operations regardless of its home should be at the core of discussions. This needs to be captured as part of the stress tests and should be one of the core concepts in my opinion, the survivability of the IANA functions is paramount
over any considerations of home/operator/jurisdiction.<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"><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""> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Seun Ojedeji<br>
<b>Sent:</b> Sunday, February 22, 2015 5:38 PM<br>
<b>To:</b> Avri Doria<br>
<b>Cc:</b> cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] Update on the Integrated model.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello Avri,<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thanks for the explanation which was quite helpful. I must say the more i try to process this, the more it seem that the proposal attempts to practically create a new operator order than ICANN (re: PTI) being
the operator and turns ICANN to a "policy only" organisation. That seem like a major change in the Internet Corporation for Assigned Names and Numbers (ICANN) mission and purpose. How will this work with ccTLDs who for instance are practically engaging with
ICANN just because it is the IANA operator? how about existing gTLD contracts which were signed with the intent of ICANN being the operator?<br>
<br>
Looking at the proposal, how do we achieve accountability of the "community board"? i mean why should one be comfortable that the "community board" will be more accountable than the current ICANN board? even if they are, why can't some of the proposed characteristics
of the "community board" be suggested within the CCWG in other to make ICANN board more accountable? I am overly concerned that we may be creating multiple structures and too many accountability points that could overall cripple the already efficient IANA
department.<br>
<br>
As you have also noted in the proposal; the outcome of the CCWG activities may indeed handle the accountability issues that the proposal attempts to address, just that it seem you don't think the implementation of the outcome will be timely? and i believe you
are speaking from experience (re: ATRT). However, i think things may be different this time and one could have faith in the CCWG process considering that NTIA categorically emphasised that outcome of ccwg with that of ICG is a prerequisite to transition. That
said, i appreciate the intent of separating IANA operation from the policy side of ICANN. Although one may argue that such septation already exist (with IANA being a department in ICANN) and can be maintained "through relevant addition to the bylaw" in the
absence of NTIA contract. <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Finally, its good to note that we now have 7 CWG proposals (yes Avri's is practically 3 in 1). From all the proposals, the IAP and CSC seem to cut across (in terms of their role). Maybe we should pick the CSC
and review its role and composition to ensure that it transparently provides it outcome to the entirely community. Utilising the outcome of the CSC to keep the board/IANA staff accountable is what CCWG could then worry about. This would avoid duplication of
accountability mechanism to ensure maintenance of a stable, secure and resilient IANA<o:p></o:p></p>
</div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<p class="MsoNormal">PS: These are personal views only!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Sat, Feb 21, 2015 at 6:09 PM, Avri Doria <<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 21-Feb-15 01:08, Seun Ojedeji wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>Hi,<o:p></o:p></p>
<p>How does this proposal address the few points below:<o:p></o:p></p>
<p>- ICANN is running IANA properly and should continue to be the operator<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
This proposal rest upon the same team being able to continue handling the operator functions. The 12 person IANA team is what is doing the job properly and what needs protecting in a stewardship transition.<br>
<br>
In the fully owned subsidiary configuration, ICANN remains the operator, or rather the owner or the operator.<br>
In the Shared Service Arrangement ICANN remains one of the owners. In this operational control is shared with the other operational communities while ICANN remains a co-owner, has SLA/MOUs and a board seats.<br>
<br>
It is only in the Free Standing configuration that ICANN would cease being an owner of a subsidiary though would probably remain owners, perhaps even members, of the Free Standing company. And would retain Community Board seats.<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>- ICANN is purpose built with it's main purpose of centrally operating IANA for the 3 communities<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
While this may have been the intention at day 0, the evolution of ICANN over the years has been anything but purpose built. ICANN has evolved into a much needed policy group that deals with the political, financial and other issues that grow out of its narrow
technical mandate. The remaining issue that has not been solved in the Internal models is the one where the policy organization for gTLDS, the bulk of ICANN's 100+ MUSD operations is not separated from IANA.<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>- The task at hand is to transition IANA stewardship, is the proposal not doing more than that?<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
Not really. Especially the model is very much about stewardship and finding ways to distribute that stewardship in the light of losing NTIA. In one configuration, ICANN retains complete control, just of a structurally separated internal component that provides
greater transparency. In the Shared Service Arrangement, IANA shares this ownership with the other 2 communities, if they are interested in sharing. If they aren't, I figure they will be fine with leaving it as a full Owned subsidiary of ICANN.<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>- Based on the response given by Milton, the practical implication of this proposal seem to imply absolute separation between IANA functions so names operation is no longer under ICANN oversight. If that is correct are we still within scope of our task by
proposing that?<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
I do not speak for Milton, that is beyond my pay grade. <br>
<br>
While there is structural separation it is not absolute - currently some try to argue that there is functional separation at ICANN as required by NTIA in the RFP, though some of us have our doubts on this actually being the case, especially since IANA isn't
even as separated as is GDD. Not all separation is the same or absolute.<br>
<br>
In two of the configurations, that structural separation is contained within the existing organizations and remains under ICANN protection. Even in the Free Standing configuration, ICANN remains on of the controling voices on the Community Board. ICANN retains
its share of the stewardship role in all of the configurations in the model. In no part of the model, and in none of it configurations is the separation complete or absolute. And remember we allegedly have functional separation today. This model is just
an evolution of current realities with as little disruption as possible.<br>
<br>
In fact for absolute or complete separation in this model, ICANN would have to utilize the same so-called nuclear option the other two operational communities are posting, the ability to take their business elsewhere. None of the configurations offered provides
absolute separation.<br>
<br>
I see nothing that excludes this from our scope to find the best stewardship solution we can given the constraint of multistakeholder general agreement. We face an impasse with strong smart people insisting they are correct on two very opposed sides of the
discussion. We can continue the tug of war about who is right; constantly worrying over who has the better argument of the day or the best allies. Perhaps we can even engage in some brinkmanship - just like US political leaders. We decided to try to find
a solution that satisfies many of the concerns of both camps without scaring those who are watching.<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>- What does the proposal intend to address; separability OR separation?<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
It is attempting to balance the most critical requirements for a multistakeholder solution, an Internal solution and also for an External solution, and one that is solid, stable and safe from International capture enough to satisfy Republicans in Congress as
well. It is meant to be a reasonable and based on a relatively standard business relationship that provides the multistakeholder control through ownership, sla/mous, and membership in the Post Transition Board. Separability is a principle that all solutions
must satisfy, but it is not a goal. The goal is stewardship for a multistakeholder, stable, secure and resilient IANA. The secondary goal was making the solution as simple as possible with as little reliance on CCWG-Accountabilty fundamental change as possible.<br>
<br>
thanks<span style="color:#888888"><br>
<br>
<span class="hoenzb">avri</span></span><br>
<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>Thanks<o:p></o:p></p>
<p>Regards<br>
sent from Google nexus 4<br>
kindly excuse brevity and typos.<o:p></o:p></p>
<div>
<p class="MsoNormal">On 21 Feb 2015 00:19, "Avri Doria" <<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>> wrote:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 20-Feb-15 16:50, Milton L Mueller wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">My question:
<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">Does this model provide for separability?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
First it provides structural separation in all configurations. That is a first level of severability and hopefully as much as really is ever needed. Additionally, in this model, ICANN would have the same ability to pick another provider, or perhaps a redundant
provider, just as the names or protocols can now. This is made possible by virtue of structural separation and the defintion of SLA/MOUs across a corporate boundary.<br>
<br>
Further levels of separability can, however, be obtained in the Shared Service Arrangement configuration or the finally in the Free Standing configuration.
<br>
<br>
Finally<br>
<br>
<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" 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>
</blockquote>
</div>
</blockquote>
<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>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">------------------------------------------------------------------------<span style="color:#888888"><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-right:0in">
<p class="MsoNormal" style="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="http://www.fuoye.edu.ng" target="_blank">http://www.fuoye.edu.ng</a><br>
</span></i><i><span style="font-family:"Garamond","serif";color:#006600">Mobile: +2348035233535</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="http://goog_1872880453" target="_blank">
</a><a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><span style="font-family:"Garamond","serif";color:#888888"><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-right:0in">
<p class="MsoNormal"><span style="font-family:"Garamond","serif";color:#888888">The key to understanding is humility - my view !<o:p></o:p></span></p>
</blockquote>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>