<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=us-ascii"><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: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><!--[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'>At a guess, with only limited information, I do not think the NTIA will accept this proposal if it is told clearly by the community that ICANN is thwarting the community’s will …<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'>Paul<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><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Paul Rosenzweig<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><a href="mailto:paul.rosenzweigesq@redbranchconsulting.com"><span style='color:#0563C1'>paul.rosenzweig@redbranchconsulting.com</span></a> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>O: +1 (202) 547-0660<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>M: +1 (202) 329-9650<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>VOIP: +1 (202) 738-1739<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Skype: paul.rosenzweig1066<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><a href="http://www.redbranchconsulting.com/index.php?option=com_content&view=article&id=19&Itemid=9"><span style='color:#0563C1'>Link to my PGP Key</span></a><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><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 #E1E1E1 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'> Robin Gross [mailto:robin@ipjustice.org] <br><b>Sent:</b> Thursday, April 30, 2015 1:03 PM<br><b>To:</b> Accountability Cross Community<br><b>Subject:</b> Re: [CCWG-ACCT] Ominous update on the IANA transition<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Very troubling. On a practical level, will this put ICANN and the NTIA in a "stand-off" or will NTIA allow ICANN to get away with this?<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks for forwarding it, Ed.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best,<o:p></o:p></p></div><div><p class=MsoNormal>Robin<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Apr 30, 2015, at 9:22 AM, Jonathan Zuck wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif;color:black'>Exactly<o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif;color:black'><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-family:"Calibri",sans-serif;color:black'>From: </span></b><span style='font-family:"Calibri",sans-serif;color:black'>Keith Drazek<br><b>Date: </b>Thursday, April 30, 2015 at 11:41 AM<br><b>To: </b>Accountability Cross Community<br><b>Subject: </b>Re: [CCWG-ACCT] Ominous update on the IANA transition<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p></div><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Wow….</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>A timely reminder of the importance of our work to improve ICANN’s Accountability.</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Best,<br>Keith</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black'> <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> [<a href="mailto:accountability-cross-community-bounces@icann.org">mailto:accountability-cross-community-bounces@icann.org</a>] <b>On Behalf Of </b>Edward Morris<br><b>Sent:</b> Thursday, April 30, 2015 10:15 AM<br><b>To:</b> Accountability Cross Community<br><b>Subject:</b> [CCWG-ACCT] Ominous update on the IANA transition</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p></div><div><div><div><p class=MsoNormal><span style='color:black'>Hi,<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><p class=MsoNormal><span style='color:black'>I think this post on the NCSG list by Dr. Mueller might be of interest to those of us working on Accountability. <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><p class=MsoNormal><span style='color:black'>Best,<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><p class=MsoNormal><span style='color:black'>Ed Morris<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><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p></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></body></html>