<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 05/01/2015 05:57 AM, Avri Doria
wrote:<br>
</div>
<blockquote cite="mid:5542B347.1040407@acm.org" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
Hi,<br>
<br>
One might wonder whether this kerfuffle might not be some
inspiration for becoming a co-owner and co-oversight of PTI as
opposed to remaining at ICANN's tender mercy.<br>
<br>
avri<br>
</blockquote>
<br>
Thanks, Avri, to make all of us who are not native speaker of
English (especially of the British version) to study this language
more - in order to really get what you want to express.<br>
<br>
<br>
So I found:<br>
<b><br>
</b><b>1.</b><b><br>
</b><b>Definition of KERFUFFLE</b><br>
chiefly British<br>
: <b>disturbance, fuss</b><br>
Examples of KERFUFFLE: <predictably, the royal scandal caused
quite a kerfuffle on Fleet Street><br>
<br>
<div class="waypoint-wrapper header-row header-first-row"
data-href="source-luna">
<h1 class="head-entry"><small><small>2.</small></small><br>
<small><small><span class="me" data-syllable="ker·fuf·fle"><span
class="js-headword"><span class="syllable">ker</span><span
class="syllable">fuf</span><span class="last-syllable">fle</span></span></span></small></small></h1>
<div class="audio-wrapper"> </div>
</div>
<div class="header-row header-extras pronounce pronset">
<div>
<span style="display: inline;" class="pron spellpron">[ker-<span
class="dbox-bold">fuhf</span>-<span class="dbox-italic">uh</span>
l] </span>
<span class="pre-def-data"> </span>
</div>
<div>
</div>
</div>
<header class="main-header oneClick-disabled head-big">
<div class="header-row header-extras pronounce pronset">
<div>
</div>
</div>
<span class="def-number"><span><span class="oneClick-link"><br>
</span></span></span></header>
<div class="def-list">
<section class="def-pbk">
<div class="def-set">
<div class="def-content">
<span class="dbox-italic"><span><span class="oneClick-link">Chiefly</span>
<span class="oneClick-link">British</span> <span
class="oneClick-link">Informal.</span> </span></span><span><b><span
class="oneClick-link">a</span></b><b> </b><b><span
class="oneClick-link">fuss;</span></b><b> </b><b><span
class="oneClick-link">commotion.</span></b> </span></div>
</div>
</section>
<br>
==<br>
</div>
<br>
So is it just a "fuss," a "disturbance" what we are reading about -
or is it a serious discussion of important things?<br>
<br>
<br>
Norbert<br>
Cambodia<br>
<br>
<br>
<br>
<blockquote cite="mid:5542B347.1040407@acm.org" type="cite"> <br>
<div class="moz-cite-prefix">On 30-Apr-15 16:07, Milton L Mueller
wrote:<br>
</div>
<blockquote
cite="mid:47aa275544da41439b0b26f91e93e779@EX13-MBX-13.ad.syr.edu"
type="cite">
<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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;}
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{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;}
/* List Definitions */
@list l0
{mso-list-id:1285624115;
mso-list-type:hybrid;
mso-list-template-ids:-1982136560 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1416247186;
mso-list-type:hybrid;
mso-list-template-ids:-1982136560 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><font size="2" color="#1f497d"
face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Seun<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d"
face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Of
course there are still uncertainties and there is still
room for interpretation regarding what is happening
between IETF and ICANN. <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d"
face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">However,
there are several pieces of evidence working against
your more benign interpretation. <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d"
face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l1 level1 lfo1"><!--[if !supportLists]--><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span
style="mso-list:Ignore">1.<font size="1" face="Times
New Roman"><span style="font:7.0pt "Times New
Roman""> </span></font></span></span></font><!--[endif]--><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The
ICANN response to the RIR CRISP team proposal, which
indicates that ICANN wants a sole-source contract in
perpetuity.<o:p></o:p></span></font></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l1 level1 lfo1"><!--[if !supportLists]--><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span
style="mso-list:Ignore">2.<font size="1" face="Times
New Roman"><span style="font:7.0pt "Times New
Roman""> </span></font></span></span></font><!--[endif]--><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The
fact that the _<i><span style="font-style:italic">existing</span></i>_
contract with NTIA commits ICANN to make a smooth
transition to a new operator, and the _<i><span
style="font-style:italic">existing</span></i>_ MoU
with IETF provides the IETF with the right to terminate
the contract. Why would it be in breach of that contract
to acknowledge these existing requirements? If it is in
breach, why didn’t ICANN say it is willing to sign but
is seeking the approval of the US Govt contracting
officer? <o:p></o:p></span></font></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l1 level1 lfo1"><!--[if !supportLists]--><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span
style="mso-list:Ignore">3.<font size="1" face="Times
New Roman"><span style="font:7.0pt "Times New
Roman""> </span></font></span></span></font><!--[endif]--><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The
fact, already put forward as evidence in my earlier
message, and which you did not address in this message,
that the IETF believes</span></font><font size="2"
color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"></span></font><font
size="2" color="#5b9bd5" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><font
color="black"><span style="color:windowtext">that the
disputed statements are “already </span></font></span></font><font
size="2" color="#5b9bd5" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><font
color="black"><span style="color:windowtext">part of
our agreement with ICANN, and that we are merely
elaborating</span></font></span></font><font
size="2" color="#5b9bd5" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><font
color="black"><span style="color:windowtext"> </span></font></span></font><font
size="2" color="#5b9bd5" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><font
color="black"><span style="color:windowtext">details
of that existing agreement”</span></font></span></font><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></font></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l1 level1 lfo1"><!--[if !supportLists]--><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span
style="mso-list:Ignore">4.<font size="1" face="Times
New Roman"><span style="font:7.0pt "Times New
Roman""> </span></font></span></span></font><!--[endif]--><font
size="2" color="#5b9bd5" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><font
color="black"><span style="color:windowtext">The fact
that this seems to be the first time ICANN has not
accepted the IETF’s supplemental agreement</span></font></span></font><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d"
face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d"
face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If
our only problem here is a technicality regarding the
timing of the agreement, then that’s great. But even you
have to admit that there could be more to it than that.
<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d"
face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<div style="border:none;border-left:solid blue
1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;font-weight:bold">From:</span></font></b><font
size="2" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
NCSG-Discuss [<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU</a>]
<b><span style="font-weight:bold">On Behalf Of </span></b>Seun
Ojedeji<br>
<b><span style="font-weight:bold">Sent:</span></b>
Thursday, April 30, 2015 1:23 PM<br>
<b><span style="font-weight:bold">To:</span></b> <a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br>
<b><span style="font-weight:bold">Subject:</span></b>
Re: [NCSG-Discuss] Ominous update on the IANA
transition<o:p></o:p></span></font></p>
</div>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span
style="font-size:12.0pt"><o:p> </o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">Hi Prof,<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">I read the mail before
responding as well(as you know I am also on that list)
and you are right that there is a concern which I also
agree with. However, it's our interpretation of the
concern that I think we disagree on.<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">Below is the exact wording of
the IAB chair:<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">" ICANN has informed<br>
us that they are unable to agree to that text right
now. ICANN told<br>
us that, in their opinion, agreeing to that text now
would possibly<br>
put them in breach of their existing agreement with
the NTIA. "<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">The use of the phrase "right
now" is what I think makes the difference in our
interpretation of the situation.<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">At ICANN 49, a question was
raised during public forum whether the NTIA contract
was weightier than the existing MoU; i.e if NTIA
decide to assign IANA to another operator, can the
respective communities(based on their current mou)
insist that ICANN has meet up with their SLA and by so
should continue to operate their function?<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">There was no definite
response to that question and I think that is what is
happening in this current situation; if ICANN signs
such SLA, that would indirectly imply double oversight
body. The specific section below is what buttresses
my point:<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">" It is possible in the
future that the operation of the protocol<br>
parameters registries may be transitioned from
ICANN to subsequent<br>
operator(s). It is the preference of the IETF
community that, as<br>
part of the NTIA transition, ICANN acknowledge
that it will carry<br>
out the obligations established under C.7.3 and
I.61 of the<br>
current IANA functions contract between ICANN and
the NTIA<br>
[NTIA-Contract] to achieve a smooth transition to
subsequent<br>
operator(s), should the need arise. "<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">So how can ICANN sign an
agreement reflecting the statement above without
actually either getting permission from NTIA OR having
the current agreement with NTIA terminated. The
requirements listed by IAB chair were developed in
response to ICG request and that process is on-going,
so I don't see why implementation should begin before
NTIA's approval.<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">Overall, I think the
important question has been asked on the IANA-plan
list which is to know the actual text in the new SLA
that ICANN can not agree to "at the moment". Until
such information is made available, ordinary community
member like me (and you?) would only be speculating.
So my interpretation of the issue may be largely
incorrect but it's based on the information currently
available to me.<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">Regards<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">sent from Google nexus 4<br>
kindly excuse brevity and typos.<o:p></o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">On 30 Apr 2015 17:36,
"Milton L Mueller" <<a moz-do-not-send="true"
href="mailto:mueller@syr.edu">mueller@syr.edu</a>>
wrote:<o:p></o:p></span></font></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>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Seun:</span></font><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I
suggest that you read the letter from the IETF
people. </span></font><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></font><o:p></o:p></p>
<pre><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">“</span></font><font color="black"><span style="color:black">It is our view that the substance of the statements above is already</span></font><o:p></o:p></pre>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="black" face="Courier New"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black">part of our agreement
with ICANN, and that we are merely elaborating</span></font><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="black" face="Courier New"><span
style="font-size:10.0pt;font-family:"Courier
New";color:black">details of that
existing agreement.</span></font><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></font><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I
could be wrong, but I don’t think IETF would
be publicizing this the way it is if it were
not concerned. </span></font><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Given
the precedent established with CRISP, ICANN’s
refusal to accept an agreement that, in IETF’s
opinion, already existed, is troublesome to
say the least. </span></font><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--MM</span></font><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="2" color="#1f497d" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></font><o:p></o:p></p>
<div style="border:none;border-left:solid blue
1.5pt;padding:0in 0in 0in 4.0pt">
<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><font
size="2" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;font-weight:bold">From:</span></font></b><font
size="2" face="Calibri"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
NCSG-Discuss [mailto:<a
moz-do-not-send="true"
href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU"
target="_blank">NCSG-DISCUSS@LISTSERV.SYR.EDU</a>]
<b><span style="font-weight:bold">On
Behalf Of </span></b>Seun Ojedeji<br>
<b><span style="font-weight:bold">Sent:</span></b>
Thursday, April 30, 2015 11:55 AM<br>
<b><span style="font-weight:bold">To:</span></b>
<a moz-do-not-send="true"
href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU"
target="_blank">
NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br>
<b><span style="font-weight:bold">Subject:</span></b>
Re: [NCSG-Discuss] Ominous update on the
IANA transition</span></font><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"> <o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">Hi Milton,<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">Thanks for this
share, I am not sure what was posted on the
IANA-plan list by the IAB chair implied that
ICANN is refusing IETF from moving it's
function if required.<br>
I understood his message to imply ICANN is
refusing to sign and agreement of such
ability because they already have a
commitment on such with the NTIA.<br>
I am not a lawyer, but I think it makes a
lot of sense to activate such agreement at
the termination of the other.<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">A question to ask
is whether ICANN is committed to signing the
SLA once NTIA relinquishes it's current
agreement.<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">Regards<o:p></o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span
style="font-size:12.0pt">sent from Google
nexus 4<br>
kindly excuse brevity and typos.<o:p></o:p></span></font></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">On 30 Apr 2015
14:27, "Milton L Mueller" <<a
moz-do-not-send="true"
href="mailto:mueller@syr.edu"
target="_blank">mueller@syr.edu</a>>
wrote:<o:p></o:p></span></font></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;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">
<o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">Dear NCSG:<o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">It’s now
official: ICANN doesn’t even want to
let the IETF have a choice of its
IANA functions operator. <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">Those of
you who read my <a
moz-do-not-send="true"
href="http://www.internetgovernance.org/2015/04/28/icann-wants-an-iana-functions-monopoly-and-its-willing-to-wreck-the-transition-process-to-get-it/"
target="_blank"> blog post on
ICANN’s interactions with the
numbers community</a> will already
know that ICANN is refusing to
accept the consensus of the numbers
community by recognizing its
contractual right to terminate its
IANA functions operator agreement
with ICANN. In that blog, I referred
to second-hand reports that IETF was
encountering similar problems with
ICANN. Those reports are now public;
the chairs of the IETF, IAB and IETF
Administrative Oversight Committee
have <a moz-do-not-send="true"
href="http://www.ietf.org/mail-archive/web/ianaplan/current/msg01680.html"
target="_blank"> sent a letter to
their community</a> noting that
ICANN is refusing to renew their
supplemental service level agreement
because it includes new provisions
designed to facilitate change in
IANA functions operators should IETF
become dissatisfied with ICANN. <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">These are
truly shocking moves, because in
effect ICANN’s legal staff is
telling both the numbers and the
protocols communities that they will
not accept the proposals for the
IANA transition that they have
developed as part of the IANA
Stewardship Coordination Group (ICG)
process. In both cases, the
proposals were consensus proposals
within the affected communities, and
were approved by the ICG as complete
and conformant to the NTIA criteria.
Thus, ICANN is in effect usurping
the entire process, setting itself
(rather than ICG and NTIA) as the
arbiter of what is an acceptable
transition proposal.<o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">The key
point of conflict here seems to be
the issue of whether ICANN will have
a permanent monopoly on the
provision of IANA functions, or
whether each of the affected
communities – names, numbers and
protocols – will have the right to
choose the operator of their global
registries. Separability is
explicitly recognized by the Cross
community working group on Names as
a principle to guide the transition,
and was also listed as a requirement
by the CRISP team. And the IETF has
had an agreement with ICANN giving
them separability since 2000 (<a
moz-do-not-send="true"
href="https://tools.ietf.org/html/rfc2860"
target="_blank">RFC 2860</a>).
Yet despite the wishes of the
community, ICANN seems to insist on
a monopoly and seems to be
exploiting the transition process to
get one. <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">Of course,
a severable contract for the IANA
functions is the most effective and
important form of accountability. If
the users of IANA are locked in to a
single provider, it is more
difficult to keep the IANA
responsive, efficient and
accountable. Given the implications
of these actions for the
accountability CCWG, I hope someone
on that list will forward this
message to their list, if someone
has not noted this event already. <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">Milton L
Mueller<o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">Laura J.
and L. Douglas Meredith Professor<o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">Syracuse
University School of Information
Studies<o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"><a
moz-do-not-send="true"
href="http://faculty.ischool.syr.edu/mueller/"
target="_blank">http://faculty.ischool.syr.edu/mueller/</a><o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt">Internet
Governance Project<o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"><a
moz-do-not-send="true"
href="http://internetgovernance.org/"
target="_blank">http://internetgovernance.org</a><o:p></o:p></span></font></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><font
size="3" face="Times New Roman"><span
style="font-size:12.0pt"> <o:p></o:p></span></font></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
<br>
<br>
<hr style="border:none; color:#909090; background-color:#B0B0B0;
height: 1px; width: 99%;">
<table style="border-collapse:collapse;border:none;">
<tbody>
<tr>
<td style="border:none;padding:0px 15px 0px 8px"> <a
moz-do-not-send="true" href="http://www.avast.com/"> <img
moz-do-not-send="true"
src="http://static.avast.com/emails/avast-mail-stamp.png"
alt="Avast logo" border="0"> </a> </td>
<td>
<p style="color:#3d4d5a;
font-family:"Calibri","Verdana","Arial","Helvetica";
font-size:12pt;"> This email has been checked for
viruses by Avast antivirus software. <br>
<a moz-do-not-send="true" href="http://www.avast.com/">www.avast.com</a>
</p>
</td>
</tr>
</tbody>
</table>
<br>
</blockquote>
<br>
</body>
</html>