<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I like the linking of <span id="OLK_SRC_BODY_SECTION">“relevant
principles of international law and international conventions”
This does at least try to put a broad emphasis on how many
signatories there are to the convention. Perhaps even "relevant
principles of international law and conventions" ? I know it is
a little word smithing, but a world of bilateral agreements worry
me. I am also happy with "applicable local law".<br>
<br>
Paul<br>
</span><br>
<div class="moz-cite-prefix">On 7/30/15 4:39 AM, Burr, Becky wrote:<br>
</div>
<blockquote cite="mid:D1DE95B8.38FD9%25becky.burr@neustar.biz"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<div>
<div>The change was to clarify that ICANN has subjected itself
to international law – which includes conventions, etc.
This language is exactly the language that is in the
Articles of Incorporation. I’m happy to put applicable in
front of everything</div>
<div><br>
</div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; "><span style="font-size: 9pt;
font-family: Arial, sans-serif;">J. Beckwith Burr<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; "><b><span style="font-size: 9pt;
font-family: Arial, sans-serif; color: rgb(6, 134,
88);">Neustar, Inc. /</span></b><span
style="font-size: 9pt; font-family: Arial, sans-serif;"> Deputy
General Counsel and Chief Privacy Officer<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; "><span style="font-size: 9pt;
font-family: Arial, sans-serif;">1775 Pennsylvania
Avenue NW, Washington, DC 20006<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; "><span style="font-size: 9pt;
font-family: Arial, sans-serif; color: rgb(6, 134, 88);">Office</span><span
style="font-size: 9pt; font-family: Arial, sans-serif;">:
+ 1.202.533.2932 <span style="color: rgb(6, 134, 88); "> Mobile</span>:
+1.202.352.6367 <span style="color: rgb(6, 134, 88); ">/ <a
moz-do-not-send="true"
href="mailto:becky.burr@neustar.biz" style="color:
purple; "><a class="moz-txt-link-abbreviated" href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a></a> /
<a class="moz-txt-link-abbreviated" href="http://www.neustar.biz">www.neustar.biz</a></span></span></p>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Greg Shatan <<a
moz-do-not-send="true" href="mailto:gregshatanipc@gmail.com"><a class="moz-txt-link-abbreviated" href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a></a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, July
29, 2015 at 2:36 PM<br>
<span style="font-weight:bold">To: </span>Becky Burr <<a
moz-do-not-send="true" href="mailto:becky.burr@neustar.biz"><a class="moz-txt-link-abbreviated" href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a></a>><br>
<span style="font-weight:bold">Cc: </span>Paul Twomey <<a
moz-do-not-send="true"
href="mailto:Paul.Twomey@argopacific.com"><a class="moz-txt-link-abbreviated" href="mailto:Paul.Twomey@argopacific.com">Paul.Twomey@argopacific.com</a></a>>,
"<a moz-do-not-send="true" href="mailto:wp2@icann.org">wp2@icann.org</a>"
<<a moz-do-not-send="true" href="mailto:wp2@icann.org">wp2@icann.org</a>>,
Malcolm Hutty <<a moz-do-not-send="true"
href="mailto:malcolm@linx.net">malcolm@linx.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [WP2] By
law change on international law WAS Re: IRP provider
appointment Was: updated documents from this morning<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">Article 4
currently reads:</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><span
style="color: rgb(51, 51, 51); font-family: helvetica,
arial, sans-serif; font-size: 16px; line-height:
22.3999996185303px;"> The Corporation shall operate
for the benefit of the Internet community as a whole,
carrying out its activities in conformity with
relevant principles of international law and
applicable international conventions and local law
and, to the extent appropriate and consistent with
these Articles and its Bylaws, through open and
transparent processes that enable competition and open
entry in Internet-related markets.</span><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><span
style="color: rgb(51, 51, 51); font-family: helvetica,
arial, sans-serif; font-size: 16px; line-height:
22.3999996185303px;"><br>
</span></div>
<div class="gmail_default"><font face="verdana,sans-serif"
color="#333333"><span
style="line-height:22.3999996185303px">It seems that
we moved the word "applicable" so that it no longer
applies "international conventions and local law"
and now only applies to "local law." I can't recall
the rationale for this change. Based on Paul's
email, I'm concerned that it is not a change for the
better. Any idea why we made this change, and it
what it was supposed to accomplish? If we don't
have a good reason to make the change, I suggest we
should not make it. If it was a concern about
ambiguity, then I suggest we put "applicable" in
front of both "international conventions" and "local
law."</span></font></div>
<div class="gmail_default"><font
face="monospace,monospace" color="#333333" size="4"><span
style="line-height:22.3999996185303px"><br>
</span></font></div>
<div class="gmail_default"><font face="verdana,sans-serif"
color="#333333"><span
style="line-height:22.3999996185303px">Greg</span></font></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 29, 2015 at 2:27 PM,
Burr, Becky <span dir="ltr">
<<a moz-do-not-send="true"
href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div>Good question. The reference to
international law and conventions has been in
the Articles of Incorporation from day 1,
however. I think if we take out the comma and
make it “relevant principles of international
law and international conventions” that reduces
the potential problem. But international
information security is only within ICANN’s
mission if it relates to DNS security and
stability</div>
<div><br>
</div>
<div><br>
</div>
<div>
<p class="MsoNormal" style="margin-left:0in"><span
style="font-size: 9pt; font-family: Arial,
sans-serif;">J. Beckwith Burr</span></p>
<p class="MsoNormal" style="margin-left:0in"><b><span
style="font-size: 9pt; font-family: Arial,
sans-serif; color: rgb(6, 134, 88);">Neustar,
Inc. /</span></b><span style="font-size:
9pt; font-family: Arial, sans-serif;"> Deputy
General Counsel and Chief Privacy Officer</span></p>
<p class="MsoNormal" style="margin-left:0in"><span
style="font-size: 9pt; font-family: Arial,
sans-serif;">1775 Pennsylvania Avenue NW,
Washington, DC 20006</span></p>
<p class="MsoNormal" style="margin-left:0in"><span
style="font-size: 9pt; font-family: Arial,
sans-serif; color: rgb(6, 134, 88);">Office</span><span
style="font-size: 9pt; font-family: Arial,
sans-serif;">:
<a moz-do-not-send="true"
href="tel:%2B%201.202.533.2932"
value="+12025332932" target="_blank">+
1.202.533.2932</a> <span
style="color:rgb(6,134,88)"> Mobile</span>:
<a moz-do-not-send="true"
href="tel:%2B1.202.352.6367"
value="+12023526367" target="_blank">+1.202.352.6367</a> <span
style="color:rgb(6,134,88)">/ <a
moz-do-not-send="true"
href="mailto:becky.burr@neustar.biz"
style="color:purple" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a></a> /
<a moz-do-not-send="true"
href="http://www.neustar.biz"
target="_blank">www.neustar.biz</a></span></span></p>
</div>
</div>
<div><br>
</div>
<span>
<div
style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium
none;BORDER-LEFT:medium
none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df
1pt solid;BORDER-RIGHT:medium
none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Paul
Twomey <<a moz-do-not-send="true"
href="mailto:Paul.Twomey@argopacific.com"
target="_blank">Paul.Twomey@argopacific.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday,
July 29, 2015 at 2:04 PM<br>
<span style="font-weight:bold">To: </span>"<a
moz-do-not-send="true"
href="mailto:wp2@icann.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:wp2@icann.org">wp2@icann.org</a></a>"
<<a moz-do-not-send="true"
href="mailto:wp2@icann.org" target="_blank">wp2@icann.org</a>>,
Becky Burr <<a moz-do-not-send="true"
href="mailto:becky.burr@neustar.biz"
target="_blank">becky.burr@neustar.biz</a>>,
Malcolm Hutty <<a moz-do-not-send="true"
href="mailto:malcolm@linx.net" target="_blank">malcolm@linx.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re:
By law change on international law WAS Re: [WP2]
IRP provider appointment Was: updated documents
from this morning<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div class="h5">While I do not think this is
exactly the sort of agreement about which
I am positing, I would draw your attention
to the recent China-Russian declaration of
April 30.
<br>
<br>
A rough translation is attached. <span><font
face="Helvetica,Arial,sans-serif"><br>
<br>
</font></span><big><small><span>The
official announcement that is on the
Russian government web site says:<br>
<br>
"The directive approves a draft
Russian-Chinese intergovernmental
agreement on cooperation in ensuring
international information security
(hereinafter, the Agreement).<br>
The Agreement aims to create a legal
and organisational framework for
Russian-Chinese cooperation in
promoting international information
security.<br>
The Agreement identifies the
principal threats and determines the
main areas, principles, forms and
mechanisms of cooperation in this
area.<br>
The Russian Foreign Ministry has
been tasked with conducting talks
with the Chinese side and, after
coming to terms, signing this
Agreement on behalf of the Russian
Government.<br>
The Agreement reflects Russia’s
interests and position regarding the
provision of international
information security and
consolidates Russian-Chinese
strategic partnership, and its
signing will help to promote
mutually beneficial cooperation
between Russia and China."<br>
<br>
<br>
<u><b>Three main issues in the
agreement</b></u><br>
<br>
1. the document is signed, because
the parties are concerned about
using the ICT for “undermining the
sovereignty and the security of the
states, and interference in their
internal affairs… destabilization
of internal political and
social-economic environment…”
<br>
2. The two governments confirm that
"the national sovereignty and the
international norms and regulations,
result from this sovereignty, are
defining the countries' behavior
within the framework of their
activities, connected to the use of
ICT and the jurisdiction of the
nation states over the information
infrastructure on their territories,
as well as the state has a sovereign
right to define and to implement
governmental policy, related to the
information-telecommunication
network "Internet" (everywhere in
the original they call it like
that), including security,<br>
3. The two governments aim at
creating a multilateral, democratic
and transparent international system
for management of the
information-telecommunication
network ‘Internet’ with the purpose
of internationalization of the
management of the Internet, and to
make sure states have equal rights
to participate in this process,
including democratic management
(governance) of the Internet core
resources and their fair
distribution.</span>.</small></big><br>
<br>
<br>
Previously such agreements have been of
significance for ICANN as part of the
political environment in which it has to
operate. But it has been committed to its
global mission. Is the amendment to the
bylaws inadvertantly making it an internal
governance matter for ICANN?<br>
<br>
<br>
Paul<br>
<br>
<br>
<div>On 7/30/15 3:55 AM, Paul Twomey
wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">+1 to Malcolm's comment on
how much has been achieved.<br>
<br>
I am sorry that I was not able to attend
Paris, but may I ask a question about
the amendment including international
conventions in:<br>
<p
style="margin-top:10.0pt;margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;text-indent:0in"><span
style="font-family: 'Avenir Book';"
lang="EN-US">1.<span> </span>In
performing its Mission, ICANN
must operate in a manner consistent
with its Bylaws for the benefit of
the Internet community as a whole,
carrying out its activities in
conformity with relevant principles
of international law, international
conventions, and applicable local
law and through open and transparent
processes that enable competition
and open entry in Internet-related
markets. Specifically, ICANN’s
action must:</span></p>
<br>
Did the group consider the situation
where two or more authoritarian
countries sign an international
statement or convention recognizing that
the DNS in their countries can only be
coordinated by their country
institutions or worse recognizing that
it can only be done by multilateral
organizations etc. Would this
constitute an "international convention"
- a much less universal term than
"international law" - and hence would
ICANN be bound by this bylaw to
recognize this? Hence not be able to
run a complete Root Zone in the IANA,
not be able to enter into registrar
contracts for registrars in those
countries etc.<br>
<br>
Paul <br>
<br>
<div>On 7/29/15 8:25 PM, Malcolm Hutty
wrote:<br>
</div>
<blockquote type="cite">
<pre>Becky,
These papers looks very good, and shows how much we have achieved. We
seem to be just about done, so congratulations.
I can find on the paper just one note of disagreement still being
recorded, relating to the appointment of the IRP Provider.
* Greg had proposed that the appointment process be conducted by ICANN
and the community jointly.
* I had said I thought that this was likely to be unworkable, and that
it would be sufficient to have ICANN consult the community on the terms
of the tender process, but selection itself should be by ICANN.
Where did we get to on this? I remember a back-and-forth between me and
Greg on this list, but don't remember it being discussed by the group.
-> If it hasn't been decided by WP2 collectively, may I ask that you
test the group's opinion as to whether they prefer my approach or Greg's?
-> If it has been decided and I just missed it, and the collective view
was to prefer Greg's proposal, you may remove the footnote noting my
disagreement: it is not my view that this is such a serious issue that I
would want to preserve my objection as a minority statement to go into
the Final Report for Public Comment.
Kind Regards,
Malcolm.
</pre>
</blockquote>
<br>
</div>
</div>
<pre cols="72"><div><div class="h5">--
Dr Paul Twomey
Managing Director
Argo P@cific
US Cell: <a moz-do-not-send="true" href="tel:%2B1%20310%20279%202366" value="+13102792366" target="_blank">+1 310 279 2366</a>
Aust M: <a moz-do-not-send="true" href="tel:%2B61%20416%20238%20501" value="+61416238501" target="_blank">+61 416 238 501</a></div></div><a moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.argopacific.com&d=AwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=0Dua7zZ-GfZGRCTgHMU-Nhicu-7Io2ciyfGYx4BAo9M&s=hx-su6o6R9sNfHQEgP0kLzBz41uvluLIOP3eo1Mofqk&e=" target="_blank">www.argopacific.com</a></pre>
</blockquote>
<br>
<pre cols="72"><span class="">--
Dr Paul Twomey
Managing Director
Argo P@cific
US Cell: <a moz-do-not-send="true" href="tel:%2B1%20310%20279%202366" value="+13102792366" target="_blank">+1 310 279 2366</a>
Aust M: <a moz-do-not-send="true" href="tel:%2B61%20416%20238%20501" value="+61416238501" target="_blank">+61 416 238 501</a></span><a moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.argopacific.com&d=AwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=0Dua7zZ-GfZGRCTgHMU-Nhicu-7Io2ciyfGYx4BAo9M&s=hx-su6o6R9sNfHQEgP0kLzBz41uvluLIOP3eo1Mofqk&e=" target="_blank">www.argopacific.com</a></pre>
</div>
</div>
</span></div>
<br>
_______________________________________________<br>
WP2 mailing list<br>
<a moz-do-not-send="true" href="mailto:WP2@icann.org">WP2@icann.org</a><br>
<a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_wp2&d=AwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=4LtMP6cAkktdfs1_7JKpJKlqba6xaDNtmQ5M97SWNC4&s=cvTwYWhLqZq64MBYoXYMZ4iPUHOggWKsNRGfGzMGlSc&e="
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/wp2</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dr Paul Twomey
Managing Director
Argo P@cific
US Cell: +1 310 279 2366
Aust M: +61 416 238 501
<a class="moz-txt-link-abbreviated" href="http://www.argopacific.com">www.argopacific.com</a></pre>
</body>
</html>