<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 5 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 5 4 2 2 2 2 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;}
@font-face
{font-family:TimesNewRomanPSMT;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
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";}
p.b38f6367-f135-4dad-b9a0-613f19acd7a4, li.b38f6367-f135-4dad-b9a0-613f19acd7a4, div.b38f6367-f135-4dad-b9a0-613f19acd7a4
{mso-style-name:b38f6367-f135-4dad-b9a0-613f19acd7a4;
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";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{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">Mike:<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">Thanks for your email.<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">My personal view is that patent trolls are a scourge and that the law needs to be changed to deal with the issue. This has been recognized from President Obama
on down. (Caveat: Not every “non-practicing entity” (i.e., an entity enforcing a patent they do not exploit themselves) is necessarily a troll.) However, I think patent troll litigation is an outlier. (Certain plaintiff class actions and shareholder derivative
suits might also fit these concerns, but the latter would not be relevant to [ICANN] and the former seems unlikely (and if it occurs, might not be frivolous).) I don’t deny that parties in the US seem relatively more likely to commence litigation than in
some other jurisdictions (access to the courts can be considered a “freedom”). However, litigation that is truly vexatious, frivolous or in bad faith often results in costs and sanctions (and may hit the attorney as well as the litigant), and is relatively
rare. (Bad cases may be another thing.) As a result I think the “let’s avoid the US because it’s so litigious argument” is more FUD than fact, and not by itself a reason to avoid a US entity. Furthermore, avoiding a US entity will not avoid US jurisdiction.<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">More specifically to the case at hand, ICANN has actually had a fairly quiet litigation history, and I don’t know if any of those cases have involved the IANA
function. I also don’t know of any that could be considered rogue, although a couple have been relatively far “out there.” So the idea that [ICANN] needs to be protected from litigation does not seem to be grounded in any concrete reality. And if [ICANN]
deserves to be sued, that’s a differently problem entirely.<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">As noted above, the protection from vexatious, frivolous and bad faith litigation is statutory, and a case that is above these bars but lacks significant merit
is likely to be disposed of on a motion to dismiss. That is not to say that there are no litigation horror stories, and of course even meritorious litigation can be very expensive.<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">Off the top of my head, I can’t think of any structures that provide protection from frivolous litigation as a general matter. (There are structures designed
to shield entities higher in the corporate chain from litigation, and specific cases such as the use of bankruptcy-remote entities to avoid involuntary bankruptcy, but neither of these seem germane.)<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">As for indemnification, who are you thinking would be the indemnifying party, and who would be the indemnified parties? I can’t think of a scenario where [ICANN]
is indemnified by any other party (except in very specific circumstances under contract) or indemnifies any other party (ditto). There is certainly no indemnity built into the California “public benefit” (i.e., non-profit) statute that I know of.<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">Thanks!<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">Greg<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"><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-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Michael Roberts [mailto:mmr1936@gmail.com]
<b>On Behalf Of </b>Mike Roberts<br>
<b>Sent:</b> Monday, March 03, 2014 10:18 AM<br>
<b>To:</b> Shatan, Gregory S.<br>
<b>Cc:</b> Ian Peter; Suzanne Woolf; John Curran; discuss@1net.org<br>
<b>Subject:</b> Re: [discuss] Second draft - proposed Netmundial submission<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Greg - <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I believe the points you mention were first contained in a contribution from me some time ago, so I will respond -<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">- the context in which they appeared was that of comparing possible future makeups for IANA to the current one, i.e, if we change, the new arrangement needs to be as good as or better than current in these areas<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">- the reference to rogue litigation had in mind such abuses as patent trolls in the U.S. In general, the atmosphere of litigiousness in the US and elsewhere suggests that forethought be given to the legal base for a new arrangement<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">- by way of comparison to “robust,” one could think of the public benefit statute under which ICANN is currently incorporated, including features such as indemnity protections, etc. This is not protection from justifiable suit, it is (some)
protection from frivolous litigation.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">- Mike<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mar 2, 2014, at 10:52 PM, Shatan, Gregory S. <<a href="mailto:GShatan@ReedSmith.com">GShatan@ReedSmith.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Ian:</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you for this. It does provide food for thought and discussion.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A couple of thoughts and questions come to mind, and I’d be curious to hear what your or others think.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">First, I don’t think it is accurate or supportable to say that the direction you propose has “widespread support” from the “private sector.” My initial thought
is that the private sector is largely unaware of the issue. To the extent that the private sector is aware of the issue, I think many don’t see the current structure as a problem (and if they do, they may not see ICANN internalization as the solution). Of
course, there are a number of subsectors within the private sector, and opinions may differ within the private sector.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Second, the focus here and elsewhere on “protection of the root zone from political or other improper interference” seems to be overblown. There don’t seem
to be any particular examples of political influence on the root zone (even post-Snowden). To the extent this is based on vague concerns about “trust” and the US Government, I have seen no evidence of USG interest in (much less incursion into or exploits
aimed at) the root. It seems to me that parties who have long wished to change the current root management scheme have seized on the current climate to try to gain ground, without satisfying any of the leaps of logic needed to get there.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Third, I am curious what you are thinking of when you mention “rogue litigation attacks”. Are there past or current litigation matters that induced you to
include this point? If not, and it’s just a theoretical possibility, what kind of litigation are you thinking of? And what constitutes “rogue litigation”? </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Finally, by a “legal structure that is robust” against such attacks, are you suggesting an entity that somehow cannot be sued anywhere in the world? This seems
rather dangerous (as well as highly unlikely). Or is your primary concern/target to move away from the current structure where ICANN is a US corporation and this amenable to suit in the US?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for considering these points.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Greg Shatan</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="mailto:discuss-bounces@1net.org"><span style="color:purple">discuss-bounces@1net.org</span></a><span class="apple-converted-space"> </span>[<a href="mailto:discuss-bounces@1net.org"><span style="color:purple">mailto:discuss-bounces@1net.org</span></a>]<span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Ian Peter<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Sunday, March 02, 2014 6:11 PM<br>
<b>To:</b><span class="apple-converted-space"> </span>Suzanne Woolf; John Curran<br>
<b>Cc:</b><span class="apple-converted-space"> </span><a href="mailto:discuss@1net.org"><span style="color:purple">discuss@1net.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>[discuss] Second draft - proposed Netmundial submission</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">Thanks to everyone who has made suggestions about this, both on and off list.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">As a result I have made a few changes, as below. I still feel perhaps the best path is for me to submit this as an individual to keep things less complicated,
unless there is a strong feeling otherwise. The deadline is March 8.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">My main objective here is a roadmap; some simple steps in the right direction that will help to a achieve a good outcome. If this is made too complicated, it
will go nowhere. Plenty of time to examine complexities later when we have an agreed path forward.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">Here is my proposed new wording. All comments and suggested improvements welcome.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">Ian Peter</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">DRAFT FOLLOWS</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">Roadmap (and principles) for internalisation of the former IANA functions under a multistakeholder governance model involving ICANN and associated technical
organisations.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">This roadmap concentrates on one internet governance issue only – the future of the IANA functions which have been the subject of much past discussion because
current arrangements are seen by many to be outside of the preferred multistakeholder model.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">Indeed, IANA itself was established in an era before most current internet governance institutions (eg ICANN) were in existence. The emergence of a trusted
global body to take over these functions was envisaged at the time and this submission suggests that we can now proceed to transfer remaining functions to a multistakeholder model of management.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">ROADMAP</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">This roadmap suggests that the IANA functions, though necessary processes in the secure and authoritative functioning of the Internet, no longer need a separate
identity and would more productively merged with similar functions under the auspices of ICANN and associated technical bodies. Subject of course to many concerns about details, this direction appears to have widespread support from governments, civil society,
technical community, and private sector.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">In order to achieve this desired change efficiently and productively, the following roadmap is proposed.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;line-height:13.0pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">1.</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">ICANN should be requested to
prepare a proposal for management of the previous IANA functions within the multistakeholder model of internet governance, including among other considerations the following criteria:</span><o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;line-height:13.0pt">
<span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;line-height:13.0pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">(a) protection of the root zone from political or other improper interference;</span><o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;line-height:13.0pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">(b) integrity, stability, continuity, security and robustness of the administration of the root zone;</span><o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;line-height:13.0pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">(c) widespread [international] trust by Internet users in the administration of this function; (d) support of a single unified root zone; and</span><o:p></o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:10.0pt;margin-left:.5in;line-height:13.0pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">(e) agreement regarding an accountability mechanism for this function that is broadly accepted as being in the global public interest."</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">2. Preparation of the proposal should involve discussion with all major stakeholder groups, with a completion timetable for a first draft for discussion at the
Internet Governance Forum in Turkey in September 2014.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">3. To expedite completion in a timely manner, it is suggested that outside consultants be engaged to prepare the discussion paper (proposal) in consultation
with major stakeholders.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">4. The solution must have the following characteristics</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><br>
<span style="font-size:11.0pt">(a) offers a legal structure that is robust against rogue litigation attacks<br>
<br>
(b) is aligned with the Internet technical infrastructure in a way that supports innovative, technology based evolution of the DNS .</span><br>
<br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">(c) is an inclusive model</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">(d) is a demonstrable improvement on current processes in this area</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">END DRAFT</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="mailto:suzworldwide@gmail.com" title="suzworldwide@gmail.com"><span style="color:purple">Suzanne
Woolf</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Sent:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Sunday,
March 02, 2014 8:52 PM</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">To:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="mailto:jcurran@istaff.org" title="jcurran@istaff.org"><span style="color:purple">John
Curran</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Cc:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="mailto:ian.peter@ianpeter.com" title="ian.peter@ianpeter.com"><span style="color:purple">Ian
Peter</span></a><span class="apple-converted-space"> </span>;<span class="apple-converted-space"> </span><a href="mailto:discuss@1net.org" title="discuss@1net.org"><span style="color:purple">mailto:discuss@1net.org</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Subject:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Re:
[discuss] Thoughts welcome on proposed Netmundial submission</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">On Feb 28, 2014, at 12:00 AM, John Curran <<a href="mailto:jcurran@istaff.org"><span style="color:purple">jcurran@istaff.org</span></a>> wrote:</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">On Feb 27, 2014, at 7:32 PM, Ian Peter <<a href="mailto:ian.peter@ianpeter.com"><span style="color:purple">ian.peter@ianpeter.com</span></a>> wrote:</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Ian -</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> Very nice writeup... I have just a couple of comments, which you may use or</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> discard as desired.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"> <span style="font-size:11.0pt">ROADMAP</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt"> 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 functions under the auspices of ICANN.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">It is an interesting formulation of the problem statement... At present, I would describe</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">the IANA functions as "a set of tasks" rather than an "entity", and hence would instead</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">phrase the purpose of a roadmap as:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">"This roadmap suggests that the IANA functions (which are necessary for the secure</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">and proper functioning of the Internet) that are currently administered by ICANN per</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">USG contract should remain at ICANN and be performed instead under its auspices</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">via the strengthening of accountability mechanisms to meet the global public interest."</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">I like Ian's initial note and this suggested refinement, but would also like to see some clarification regarding those IANA functions which do not relate to the DNS root.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt">Subject of course to many concerns about details, this direction appears to have widespread support from governments, civil society, technical community, and
private sector.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:13.0pt"><span style="font-size:11.0pt"> In order to achieve this desired change efficiently and productively, the following roadmap is proposed.</span><o:p></o:p></p>
<div style="margin-left:.5in">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:13.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">1.</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">ICANN
should be requested to prepare a proposal for management of the previous IANA functions within the ICANN multistakeholder model, bearing in mind the following criteria:</span><o:p></o:p></p>
</div>
</div>
<p class="MsoListParagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;line-height:13.0pt">
<span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<div style="margin-left:.5in">
<div>
<p class="MsoNormal" style="line-height:13.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">(a) protection of the root zone from political or other improper interference;</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">The above criteria confuses me - are we referring to ICANN's DNS policy development role,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">or performance of the IANA functions? The latter are technical tasks in registry administration</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">and the<span class="apple-converted-space"> </span></span><span style="font-family:"Calibri","sans-serif"">most important criteria would be that ICANN continue to implement
all IANA registry</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">functions in accordance with the respective policies (I guess one could further elaborate to</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">point out that operating per respective policies means free from political or other interference,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">but that really is secondary to making sure that the IANA follows IETF protocol, RIR IP, and</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">ICANN DNS policies, both presently adopted and as revised in the future.)</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Right. In particular, one would hope that proper administration of the IANA functions includes protection from "improper interference" in any of them as an initial requirement.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">The IANA functions do not consist only of those related to the DNS, yet many of the suggestions and assumptions we see tend to be limited to issues and mechanisms that may apply more closely
to DNS-related IANA functions than to others. It would be helpful to be clear whether we're talking about the DNS-related functions only, or the full scope of IANA's responsibilities to the internet community.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">best,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Suzanne</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p> </o:p></span></p>
</div>
<p class="b38f6367-f135-4dad-b9a0-613f19acd7a4" style="margin:0in;margin-bottom:.0001pt">
<span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">* * *</span><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">This E-mail, along with any attachments, is considered confidential and may well be legally privileged. If you have received it in error, you are on notice of its status. Please
notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Thank you for your cooperation.</span><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">* * *</span><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">To ensure compliance with Treasury Department regulations, we inform you that, unless otherwise indicated in writing, any U.S. Federal tax advice contained in this communication
(including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (1) avoiding penalties under the Internal Revenue Code or applicable state and local provisions or (2) promoting, marketing or recommending to another
party any tax-related matters addressed herein.</span><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">Disclaimer Version RS.US.20.10.00</span><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif""><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TimesNewRomanPSMT","serif"">_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@1net.org"><span style="color:purple">discuss@1net.org</span></a><br>
<a href="http://1net-mail.1net.org/mailman/listinfo/discuss"><span style="color:purple">http://1net-mail.1net.org/mailman/listinfo/discuss</span></a><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>