<div dir="ltr">Eric,<div><br></div><div>I'm not sure why you appear to be limiting your inquiry to the "technical coordination of unique endpoint identifiers" and the IANA Function, narrowly construed. Or is your point that from that fairly narrow set of tasks, a broad variety of developments, innovations and other consequences have flowed, hopefully in the public interest (but certainly affecting the public interest.)?</div><div><br></div><div>On a separate note, the way I look at the whole "applicable law" point is that ICANN (like any person or entity) should be expected to act within the laws applicable to it. To put it another way, they shouldn't break the law. There is some validity to Dr. Lisse's point that this is both vague and self-evident, but it gives folks some comfort to say it in things like Articles of Incorporation (indeed, there's a certain level of requirement for statements like that in documents like that). The linkage between acting in the "public interest" and not breaking the law is somewhat cloudy. Many corporations (and people) do the latter without doing the former. And sometimes (e.g., the Pentagon Papers or (arguably, to some) Edward Snowden) do the former while failing to do the latter.</div><div><br></div><div>In any event, I do think there is some value in clarifying the concept of "public interest" in the context of ICANN, but I am not seeing the value in trying to create a linkage between that concept and the concept of "applicable law."</div><div><br></div><div>Greg Shatan</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;background-image:initial;background-repeat:initial"><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(23,54,93)">Gregory S. Shatan </span></b><b><span style="font-size:8pt;font-family:Symbol;color:rgb(23,54,93)">|</span></b><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(23,54,93)"> </span></b><b><span style="font-size:8pt;font-family:Arial,sans-serif;color:rgb(192,80,77)">Abelman Frayne & Schwab</span></b><span style="font-size:12pt;font-family:'Times New Roman',serif"></span></p><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;background-image:initial;background-repeat:initial"><b><span style="font-size:8pt;font-family:Arial,sans-serif;color:rgb(23,54,93)">666 Third Avenue </span></b><b><span style="font-size:8pt;font-family:Symbol;color:rgb(23,54,93)">|</span></b><b><span style="font-size:8pt;font-family:Arial,sans-serif;color:rgb(23,54,93)"> New York, NY 10017-5621</span></b><span style="font-size:12pt;font-family:'Times New Roman',serif"></span></p><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;background-image:initial;background-repeat:initial"><b><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy">Direct</span></b><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy"> </span><span style="font-size:8pt;font-family:Arial,sans-serif;color:rgb(17,85,204)"><a value="+12128859253" style="color:rgb(17,85,204)">212-885-9253</a> <b>| </b></span><b><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy">Main</span></b><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy"> </span><span style="font-size:8pt;font-family:Arial,sans-serif;color:rgb(17,85,204)"><a value="+12129499022" style="color:rgb(17,85,204)">212-949-9022</a></span><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u><u></u></span></p><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;background-image:initial;background-repeat:initial"><b><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy">Fax</span></b><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy"> </span><span style="font-size:8pt;font-family:Arial,sans-serif;color:rgb(17,85,204)"><a value="+12129499190" style="color:rgb(17,85,204)">212-949-9190</a> <b>|</b> </span><b><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy">Cell </span></b><span style="font-size:8pt;font-family:Arial,sans-serif;color:rgb(17,85,204)"><a value="+19178166428" style="color:rgb(17,85,204)">917-816-6428</a></span><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u><u></u></span></p><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;background-image:initial;background-repeat:initial"><b><i><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy"><a href="mailto:gsshatan@lawabel.com" style="color:rgb(17,85,204)" target="_blank">gsshatan@lawabel.com</a><u></u><u></u></span></i></b></p><p style="margin:0in 0in 0.0001pt;font-family:Calibri,sans-serif;background-image:initial;background-repeat:initial"><b><font>ICANN-related: <a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a> </font></b></p><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;background-image:initial;background-repeat:initial"><b><i><span style="font-size:8pt;font-family:Arial,sans-serif;color:navy"><a href="http://www.lawabel.com/" style="color:rgb(17,85,204)" target="_blank">www.lawabel.com</a></span></i></b></p></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Dec 18, 2014 at 2:54 PM, Eric Brunner-Williams <span dir="ltr"><<a href="mailto:ebw@abenaki.wabanaki.net" target="_blank">ebw@abenaki.wabanaki.net</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Malcolm,<br>
<br>
Earlier, you (and several others) offered several phrases containing some qualifier and the word "law" as useful language to add.<br>
<br>
My first point was to illustrate that neither "law" nor "contract" have much bearing on the set of activities usually referred to as the technical coordination of unique endpoint identifiers. Dr. Lisse made much the same point as did anyone else asking "which law?", and by now you've had a chance to see Becky Burr's comment.<br>
<br>
My second point, which I think you've missed or I expressed poorly, is that when we construe the IANA Function very narrowly, and informed only by the commentary of the IAB, e.g., RFC 2826, historically significant and broad reaching "public interest" consequences follow. Scripts other than Latin now form DNS labels throughout the namespaces, addresses are allocated according to some forms of equity of access, etc.<br>
<br>
Restated, the mere stewardship of unique endpoint identifiers and protocol parameters entails a significant public interest capability, and responsibility. This was true prior to 1998 when Dr. Postel held most the responsibility personally, and remains true after 1998 when these responsibilities began a process of institutionalization.<br>
<br>
I hope this clarifies my earlier note.<span class="im HOEnZb"><br>
<br>
Regards,<br>
Eric Brunner-Williams<br>
Eugene, Oregon<br>
<br></span><div class="HOEnZb"><div class="h5">
On 12/18/14 2:35 AM, Malcolm Hutty wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2014-12-17 21:20, Eric Brunner-Williams wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 12/17/14 8:53 AM, Malcolm Hutty wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Certainly I would regard it as being in the public interest that ICANN<br>
should discharge its functions properly, and in accordance with generally<br>
accepted principles of law.<br>
</blockquote>
<br>
Dear Malcolm,<br>
<br>
What "generally accepted principles of law" do you suggest apply to<br>
the management of protocol parameters?<br>
</blockquote>
<br>
[snip: other similar questions, that ultimately lead to:]<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
My point being that when the IANA Functions are as narrowly construed<br>
as we can sensibly make them, "public interest" and "generally<br>
accepted principles of law" are difficult to find points of<br>
association, let alone concordance.<br>
</blockquote>
<br>
Eric,<br>
<br>
I'm a bit surprised by the tone of your reply, which appears to signal a<br>
disagreement between us that I don't recognise in the argument itself.<br>
<br>
The main thrust of my intervention was to say that we should not make broad<br>
statements about the public interest and "generally accepted principles<br>
of international law" that could be construed to enlarge ICANN's role.<br>
<br>
Your intervention seems to be aligned with this.<br>
<br>
I am not a PIL expert, so I cannot guess what principles of PIL may be<br>
applicable to ICANN. There certainly are broad principles that I do<br>
believe are applicable to ICANN (including transparency, a rules-based approach,<br>
bottom-up multi-stakeholder policy-making, impartiality of treatment<br>
under the rules etc); some of these may be found in PIL too, or maybe not,<br>
I don't know.<br>
<br>
I do believe ICANN should apply only aspects of PIL as relevant<br>
to its existing mission, rather than reshaping its mission to pursue<br>
the multifarious goals of international public policy. On this may<br>
I take it we are agreed?<br>
<br>
Malcolm<br>
<br>
</blockquote>
<br></div></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-<u></u>Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/<u></u>listinfo/accountability-cross-<u></u>community</a><br>
</div></div></blockquote></div></div>