<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Colleagues,<br>
<br>
I would like to suggest that our human rights language include
something along the lines of:
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
"no religious test shall ever be required as a qualification to
any office or public trust."<br>
<br>
The source is Article VI of the Constitution of the United States.<br>
<br>
Eric Brunner-Williams<br>
Eugene, Oregon<br>
<br>
<br>
On 11/5/15 8:53 AM, Eric Brunner-Williams wrote:<br>
</div>
<blockquote cite="mid:563B8991.9010809@abenaki.wabanaki.net"
type="cite">Colleagues, <br>
<br>
Some will recall that when the Government of Egypt, then going
through crisis, directed the ISPs within its jurisdiction to
withdraw their respective prefix announcements, affecting a series
of changes to the global routing database communicated via BGP4,
which took Egypt "off-line", that the Corporation did something. <br>
<br>
It announced that the one remaining authoritative server for the
.eg zone which remained globally accessible would, if its data
"expired" before the Government of Egypt directed the ISPs within
its jurisdiction to re-announce their respective prefix
announcements, again affecting changes to the global routing
database communicated via BGP4, putting Egypt back "on-line",
refresh the zone date of the one remaining authoritative server
for the .eg zone, so that the pre-existing data for the entire .eg
zone would not be discarded. <br>
<br>
In effect, the Corporation guaranteed the continuous existence of
zone data and correctness of resolution, independent of the
express intent of the (then) Government of Egypt, because ... <br>
<br>
And there is where we have the possibility of writing in the human
rights rational for keeping the .eg data from expiry. It could be
the rights of Egyptians to continuity and correctness of
resolution withing the .eg zone, or the global right to continuity
and correctness of resolution of any zone, including the .eg zone,
or possibly even further reaching, conditions upon the abilities
of state actors to access the global routing database. <br>
<br>
Next, at the Santa Monica meeting, which I was able to attend in
person, I pointed out that we (Amadeu, myself, ... Vint, ...) had
no idea in 2005 that a "cultural and linguistic application" by a
Catalan NGO would trigger a vast amount of text generation in
Catalan in the namespace delegated to the Catalan NGO. I said
something along the lines of "access to namespaces is something
the Corporation has direct control over", with the implication
that the use of local language, and so the infrastructure which
reasonably facilitates that use, is a human right, protected and
promoted by the Corporation. <br>
<br>
And here too is where we have the possibility of writing in the
human rights rational for the IDN program, with all its warts and
bells and whistles. <br>
<br>
Are there other ways to approach human rights protection and
promotion by ICANN? It seems likely to me, but these are things
we've done, the Corporation has done with the full knowledge and
consent of the Community, and are rather central to the mission of
the Corporation -- continuous correct routing and resolution, and
identifiers in languages other than US English. <br>
<br>
Eric Brunner-Williams <br>
Eugene, Oregon <br>
_______________________________________________ <br>
Accountability-Cross-Community mailing list <br>
<a class="moz-txt-link-abbreviated"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<br>
<a class="moz-txt-link-freetext"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
<br>
<br>
<br>
</blockquote>
<br>
</body>
</html>