<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 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;}
span.EmailStyle17
{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">David,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Was travelling and sorry I was not able to answer this sooner. The legal affiliate model of IANA has to be seen as a middle ground between two extremes that are
not capable of achieving consensus. <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">While everyone recognizes the need to separate policy making from implementation (and in fact such a requirement to keep IANA employees out of the policy process
was written into the NTIA contract), a wholly independent IANA seems to scare people, because they are afraid it might be captured by someone who wants to use it to circumvent or block bottom up policy developed in ICANN.<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">A wholly ICANN-controlled IANA was equally scary to many because a permanent monopoly on the IANA functions would likely make ICANN unresponsive to its primary
customers/direct users, and more able to abuse or circumvent the policy process itself.
<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">Legal separation into a new “Post Transition IANA” (PTI) gives us some of the benefits of separation and enhanced severability without the risks of complete independence.
For example, if IANA is a separate entity, it is easier for the names community to “fire” its IANA functions operator, whereas if it were completely entangled with ICANN that would be much more difficult. The PTI proposal also contains a periodic review process
that can lead to an RFP for a new operator. Legal separation focuses management accountability on the PTI and its board, rather than relying on the ICANN board, which has much broader, more diffuse responsibilities.
<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">The key issue is the composition and independent of the Post-Transition IANA board. An independent board, coupled with an independent review team, will mean that
PTI is not just a passive creature of the ICANN. I would agree that if the board of PTI is merely appointed by ICANN staff/board, then the point of separation is lost. And since the composition of the PTI board is still open, I hope that NCSG members will
understand the need to push for an independent PTI board that contains IETF and RIR representatives as well as naming community representatives.
<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"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></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><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"> NCSG-Discuss [mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU]
<b>On Behalf Of </b>David Post<br>
<b>Sent:</b> Thursday, April 23, 2015 11:27 AM<br>
<b>To:</b> NCSG-DISCUSS@LISTSERV.SYR.EDU<br>
<b>Subject:</b> Re: [NCSG-Discuss] Public Comments on IANA proposal<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Milton/All<br>
<br>
I'm sure this was talked about at length during the development of the proposal, but it does seem rather odd to me that "functional and legal separation" between the IANA naming functions and ICANN (which I agree is an important principle) has been implemented
in this proposal by means of setting up a new corporation that is a wholly-owned subsidiary of ICANN's (with an ICANN-designated Board - sec III.A.i.b). Can you say a few words as to why you think that provides for the necessary independence? The PTI Board
will be answerable to the ICANN Board, because ICANN is the only "member" of PTI - ??
<br>
<br>
David<br>
<br>
<br>
The At 10:58 AM 4/23/2015, Milton L Mueller wrote:<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Dear NCSG-ers:<br>
<br>
The domain names part of the IANA transition is finally being formed. A draft proposal was released yesterday and it is open for public comment.
<br>
<br>
In my view, this is a big win for accountability. By legally separating the IANA functions operator from ICANN, it will be easier to hold ICANN’s board and staff accountable for the policy making process, and easier to hold the post-transition IANA accountable
for its performance of the IANA functions. Lines of responsibility will be more direct, and policy more clearly separated from implementation.
<br>
<br>
The proposal also promotes accountability by creating a periodic review process that could allow the names community to “fire” the existing IANA if there was great dissatisfaction with its performance. This enhances the accountability sought by the numbers
and protocols communities as well as creating separability for the names community for the first time.
<br>
<br>
The legal affiliate structure seems to have found the middle ground in the debate over ICANN’s role in the IANA functions. Although IANA will still be a subsidiary of ICANN, Inc., thus defusing any concerns about creating new organizations, it will have a separate
board and a clearer line of demarcation between the politics of ICANN the policy maker and the technical coordination functions provided by the IANA functions operator.
<br>
<br>
You can read the (very long) proposal here:<br>
<br>
<a href="https://www.icann.org/news/announcement-2015-04-22-en">https ://www.icann.org/news/announcement-2015-04-22-en</a><br>
<br>
You can comment on it here:<br>
<b> <br>
</b><a href="https://www.icann.org/public-comments/cwg-stewardship-draft-proposal-2015-04-22-en">https://www.icann.org/public-comments/cwg-stewardship-draft-proposal-2015-04-22-en</a>
<o:p></o:p></p>
<p class="MsoNormal" align="center" style="text-align:center"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
*******************************<br>
David G Post - Senior Fellow, Open Technology Institute/New America Foundation<br>
blog (Volokh Conspiracy) <a href="http://www.washingtonpost.com/people/david-post">
http://www.washingtonpost.com/people/david-post<br>
</a>book (Jefferson's Moose) <a href="http://tinyurl.com/c327w2n%A0%A0%A0%A0%A0">
http://tinyurl.com/c327w2n </a><br>
music <a href="http://tinyurl.com/davidpostmusic">http://tinyurl.com/davidpostmusic</a> publications etc.
<a href="http://www.davidpost.com /">http://www.davidpost.com </a><br>
******************************* <o:p></o:p></p>
</div>
</div>
</body>
</html>