<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 28/02/2014, at 6:00 PM, John Curran wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Feb 27, 2014, at 7:32 PM, Ian Peter <<a href="mailto:ian.peter@ianpeter.com">ian.peter@ianpeter.com</a>> wrote:<br><div><br></div><div>Ian -</div><div><br></div><div> Very nice writeup... I have just a couple of comments, which you may use or </div><div> discard as desired.</div><div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div dir="ltr">
<div style="font-family: Calibri;"><p class="MsoNormal" style="margin: 0cm 0cm 10pt; line-height: 13pt;"><span style="font-size: 12pt; line-height: 13pt;"> </span><span style="font-size: 11pt; line-height: 13pt;">ROADMAP</span></p><p class="MsoNormal" style="font-size: 12pt; margin: 0cm 0cm 10pt; line-height: 13pt;"><font style="FONT-SIZE: 11pt"> </font><font style="FONT-SIZE: 11pt">This roadmap
suggests that the IANA functions, though necessary processes in the secure and
authoritative functioning of the Internet, no longer need a separate entity and
would more productively merged with similar function</font></p></div></div></div></blockquote></div></div></blockquote><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div style="font-family: Calibri;"><p class="MsoNormal" style="font-size: 12pt; margin: 0cm 0cm 10pt; line-height: 13pt;"><font style="FONT-SIZE: 11pt">under the auspices of
ICANN. </font></p></div></div></div></blockquote></div></div></blockquote><div>To me, this substantially misses the major point, and appears confused about the current set up.</div><div><br></div><div>IANA functions do not have a separate entity - they are are a set of functions performed already by ICANN.</div><div>That means they are already a function under the auspices of ICANN.</div><div><br></div><div>THE issue in play is that ICANN performs these functions under a contract from the USG.</div><div><br></div>The issue is that this contract provides the USG with an unequal advantage compared with other government, and all other IG actors.</div><div><br></div><div>Making progress on this issue means removing the contract, and the contractual relationship that it creates. The USG originally signaled in Clinton's time that it would complete a handover to the NewCo of the White Paper, once it was built. One avenue is therefor to return to the USG and say that ICANN has now become the trusted global body envisaged by the White Paper, and that transfer should now be done.</div><div><br></div><div>How that gets done is important - there should be no opportunity for US politicians to argue that the Administration "gave away the Internet".</div><div><br></div><div>Time in Singapore and Brazil should productively focus on the mechanisms by which this transition should occur.</div><div>I have suggested several in the past - eg treating the IANA functions as "trust" property, with ICANN as Trustee. If necessary, the USG could retain a role settlor of the Trust, with the power to appoint trustees - not a huge distance from the current (contractual) situation, but a lot better in practice. ICANN would "own" IANA, the beneficiaries would be the Internet community. The terms of the trust would include that ICANN operate IANA under DNS directions frm ICANN, etc etc etc.</div><div><br></div><div>Or, the USG could "assign" the IANA functions, with a security ( like a mortgage) over them. The terms of the mortgage would be the similar to the obligations in the Trust deed above.</div><div><br></div><div>This would allow the USG to exercise a right of re-entry if the terms of the mortgage were breached.</div><div><br></div><div>These arrangements need to satisfy both masters - the global internet community, looking for a way to lessen the USG role and US politicians who see the Internet (wrongly) as a US fief.</div><div>The solution should be very long term, so that there is stability.</div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div>It is an interesting formulation of the problem statement... At present, I would describe </div><div>the IANA functions as "a set of tasks" rather than an "entity", and hence would instead</div><div>phrase the purpose of a roadmap as:</div><div><br></div><div>"This roadmap suggests that the IANA functions (which are necessary for the secure </div><div>and proper functioning of the Internet) that are currently administered by ICANN per</div><div>USG contract should remain at ICANN and be performed instead under its auspices </div></div></div></blockquote><div><br></div>better<br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div>via the strengthening of accountability mechanisms to meet the global public interest.</div></div></div></blockquote><div><br></div>but this is a non-sequitur.</div><div>Improving the accountability mechanisms ( a most worthy goal, which needs to be built in to the DNA) wont keep the IANA functions at ICANN.</div><div><br></div><div>1 - they are already at ICANN and there is no suggestion they should be moved, and 2. they are there under a contract, which is the root cause of the problem.</div><div><br></div><div>Nor will improving accountability keep them being performed under ICANN auspices, if the USG decides to re-let the contract, or take the functions in-house.</div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div style="font-size: 12pt; font-family: Calibri;"><p class="MsoNormal" style="MARGIN: 0cm 0cm 10pt; LINE-HEIGHT: 13pt"><font style="FONT-SIZE: 11pt">Subject of course to many concerns about details, this direction appears
to have widespread support from governments, civil society, technical community,
and private sector.</font></p><p class="MsoNormal" style="MARGIN: 0cm 0cm 10pt; LINE-HEIGHT: 13pt"><font style="FONT-SIZE: 11pt"> </font><font style="FONT-SIZE: 11pt">In order to
achieve this desired change efficiently and productively, the following roadmap
is proposed.</font></p><div style="margin: 0cm 0cm 0pt 36pt; line-height: 13pt; text-indent: -18pt;"><span style="mso-bidi-font-family: calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list: ignore"><font style="FONT-SIZE: 11pt">1.</font><span style="FONT-FAMILY: ; LINE-HEIGHT: normal"><font face="Times New Roman"><font style="FONT-SIZE: 7pt">
</font></font></span></span></span><font style="FONT-SIZE: 11pt">ICANN should be
requested to prepare a proposal for management of the previous IANA functions
within the ICANN multistakeholder model</font></div></div></div></div></blockquote></div></div></blockquote><div><br></div>ICANN manages the IANA within the MSM.</div><div>Under the terms of the SOW there has to be functional separation inside ICANN between the policy making and the implementation, but IANA is inside ICANN. </div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div style="font-size: 12pt; font-family: Calibri;"><div style="margin: 0cm 0cm 0pt 36pt; line-height: 13pt; text-indent: -18pt;"><font style="FONT-SIZE: 11pt"> bearing in mind the following
criteria:</font></div><p class="MsoListParagraphCxSpMiddle" style="MARGIN: 0cm 0cm 0pt 36pt; LINE-HEIGHT: 13pt"><font style="FONT-SIZE: 11pt"></font> </p><div style="margin: 0cm 0cm 0pt 36pt; line-height: 13pt;"><font style="FONT-SIZE: 11pt">(a) protection of the root zone from political or other
improper interference; </font></div></div></div></div></blockquote><br><div dir="ltr"><div dir="ltr"><div style="font-family: Calibri; font-size: 12pt;"><span style="font-family: Helvetica; font-size: 13px;">The above criteria confuses me - are we referring to ICANN's DNS policy development role, </span></div><div style="font-family: Calibri; font-size: 12pt;"><span style="font-family: Helvetica; font-size: 13px;">or </span><span style="font-family: Helvetica; font-size: 13px;">performance of the IANA functions? The latter are technical tasks in registry administration</span></div><div><span style="font-family: Helvetica; font-size: 13px;">and the </span>most important criteria would be that ICANN continue to implement all IANA registry </div><div>functions in accordance with the respective policies (I guess one could further elaborate to </div><div>point out that operating per respective policies means free from political or other interference,</div><div>but that really is secondary to making sure that the IANA follows IETF protocol, RIR IP, and </div><div>ICANN DNS policies, both presently adopted and as revised in the future.)</div><div><br></div></div></div></div></div></blockquote>What is needed is cut and paste from the SOW with NTIA, so that these controls (worth and necessary) which are there are captured are continued in the new ( non-contractual) instrument, plus a community debate about the appropriateness of new and other controls.</div><div><br></div><div>Another topic that should be prominent on the agenda's in Singapore and Brazil.</div><div><br></div><div><br></div><div>regards</div><div><br></div><div><br></div><div>Peter</div><div><br></div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div dir="ltr"><div dir="ltr"><div>That's it - thanks again for sending this!</div><div>/John</div><div><br></div><div>Disclaimer: My views alone.</div><div><br></div><div><br></div><div style="font-family: Calibri; font-size: 12pt;"><br></div><div style="font-family: Calibri; font-size: 12pt;"><br></div></div></div></div><br></div>_______________________________________________<br>discuss mailing list<br><a href="mailto:discuss@1net.org">discuss@1net.org</a><br>http://1net-mail.1net.org/mailman/listinfo/discuss</blockquote></div><br></body></html>