<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Perhaps we need to consider one of the hallmarks of accountability -
separation of duties. We can all agree that we are not looking for
yet another bureaucratic layer, but we are equally not willing to
rely on a "trust us" methodology; having the only recourse being a
lawsuit for a contract violation. I think we need to bring some
more imagination to this process.<br>
<br>
Joe<br>
<div class="moz-cite-prefix">On 5/9/2014 10:29 PM, Mike Roberts
wrote:<br>
</div>
<blockquote
cite="mid:F97EF0CC-E7D5-409E-8B46-8483D1CDFD73@darwin.ptvy.ca.us"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
"without creating any new fluffy free standing institutions”
<div><br>
</div>
<div>Thank you, David!</div>
<div><br>
</div>
<div>= "<span style="font-family: TimesNewRomanPSMT;">an expanded
MS to serve IG needs would “float" in the ether,</span><font
face="TimesNewRomanPSMT">”</font></div>
<div><span style="font-family: TimesNewRomanPSMT;"><br>
</span></div>
<div><span style="font-family: TimesNewRomanPSMT;"><br>
</span></div>
<div><font face="TimesNewRomanPSMT">I’ll go along
with “counterparty,” - I called it “entity”</font></div>
<div><font face="TimesNewRomanPSMT"><br>
</font></div>
<div><font face="TimesNewRomanPSMT">- Mike</font></div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div>
<div>On May 9, 2014, at 6:07 PM, DAVID JOHNSON <<a
moz-do-not-send="true"
href="mailto:davidr.johnson@verizon.net">davidr.johnson@verizon.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">I think this is a false dichotomy.<br>
The proposal is not to have a multi-stakeholder operation
overseeing icann as a multi-stakeholder process.<br>
That would lead to a "turtles all the way up" absurdity.<br>
<br>
The problem is to come up with some specific set of promises
that ICANN could make, by contract, regarding what it will
and will not do.<br>
E.g., not use the monopoly control of the root to regulate
content.<br>
Or impose contract conditions not supported by consensus
among affected parties.<br>
<br>
The question is to whom this promise would be made -- and
would that counter party be appropriately trusted with
decisions on when to enforce it?<br>
That would be an easier question if we created a judicial
(arbitration) branch that could hear the case.<br>
<br>
Maybe it is not sufficient to allow only registries to
"bring the case" -- but the alternative would be to give
registrants standing.<br>
All this could be done by contract, without creating any new
fluffy free standing institutions.<br>
<br>
If we can agree on the list of core obligations we would
want an icann of the future to be bound by, surely we can
agree on some rules of "standing" re what groups can bring a
case to hold them to it.<br>
<br>
drj<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:discuss@1net.org">discuss@1net.org</a>
<a class="moz-txt-link-freetext" href="http://1net-mail.1net.org/mailman/listinfo/discuss">http://1net-mail.1net.org/mailman/listinfo/discuss</a></pre>
</blockquote>
<br>
</body>
</html>