<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>On today’s BC call, several of us talked about Milton Mueller’s post regarding resistance from ICANN legal when it came time to implement the numbers and protocol transition plans. (post is
<a 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/">
here</a>, Milton’s email is below)</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div>Bill Woodcock just posted a reply to Milton’s post, clarifying his role in the meetings with ICANN. (<a 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/">link</a>).
Bill concludes with a confirmation of the troubling trend that Milton reported:</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><font face="Calibri,sans-serif">Those particulars aside, the rest of your description of the situation seems accurate to me. The IAB minutes that you cite are particularly worthy of note: that ICANN is _refusing to renew_ the MOU under which they provide
Protocol Registry services to the IETF, because it contains a termination clause, I find very disturbing. I have to admit that if I were in the IETF’s shoes, I might very well just take ICANN at their word and go on my merry way, if they say they don’t want
to renew the agreement.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
</blockquote>
<div><font face="Calibri,sans-serif">Let’s assume we will encounter the same resistance when it comes time to ‘negotiate’ implementation of CWG and CCWG proposals.</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div id=""></div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div 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">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black">---------- Forwarded message ----------<br>
From: <b>Milton L Mueller</b> <<a href="mailto:mueller@syr.edu" target="_blank">mueller@syr.edu</a>><br>
Date: Thu, Apr 30, 2015 at 2:27 PM<br>
Subject: Ominous update on the IANA transition<br>
To: <a href="mailto:NCSG-DISCUSS@listserv.syr.edu" target="_blank">NCSG-DISCUSS@listserv.syr.edu</a><br>
<br>
<br>
<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Dear NCSG:<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">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></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Those of you who read my
<a 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 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></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">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></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">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 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></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">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></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Milton L Mueller<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Laura J. and L. Douglas Meredith Professor<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Syracuse University School of Information Studies<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="http://faculty.ischool.syr.edu/mueller/" target="_blank">http://faculty.ischool.syr.edu/mueller/</a><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Internet Governance Project<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="http://internetgovernance.org/" target="_blank">http://internetgovernance.org</a><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</span></div>
</span><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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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.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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
--></style>
</body>
</html>