<html>
<body>
Alejandro, <br><br>
This was one of the most extensive debates, first in San Juan, and then
online, that I can recall in At-Large. And quite reasonably since this
may have significant effect on the users whose interests we represent.
The Wiki printout runs 18 pages. There were at least 4 draft statements
prior to the final one. The issue was then debated during the ALAC
meeting on 27 March, and the decision was made to go with a short and
clear statement which identified a number of issues and needs. <br><br>
I drafted the final version and passed it by the ALAC and regional
leaders. Despite a very tight timeline, I received confirmation of
support from 10 of the remaining 14 ALAC members (including all three
from LACRALO) prior to submission.<br><br>
There was no conscious decision to exclude those words. I drafted what I
thought was reasonable at the time, and no one suggested any edits.
Although the there is no explicit reference to ALSes, it was well
understood by all in the discussion that this was a path we would follow
once we have access to the right materials.<br><br>
Starting from a position with a large split in the community, we ended up
with what I hope is an excellent statement that has wide support and one
that I believe will have significant impact. It exemplifies what At-Large
can do when there is an important issue at hand and it is one we should
all be proud of.<br><br>
Alan<br><br>
At 04/04/2018 11:22 PM, Alejandro Pisanty wrote:<br>
<blockquote type=cite class=cite cite="">Alan,<br><br>
so why was this elided from the draft resolution?<br><br>
Alejandro Pisanty<br><br>
On Wed, Apr 4, 2018 at 9:55 PM, Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
> wrote:<br>
<dl>
<dd>Alejandro,<br><br>
<dd>The text of the comment does not reference "ALS", but it
does reference "users". Exactly how we plan to use the
tools and documents we are asking for is not a critical part of the
comment. What we are asking for is.<br><br>
<dd>If we can get the tools and documents we are asking for, it will then
be up to us (and hopefully other parts of the ICANN community as well) to
use them. In our case, dissemination through our networks of ALSes and
individual members will be one of the critical paths.<br><br>
<dd>Using the At-Large network to spread the word about the KSK Rollover
has already been the subject of several discussions with the Office of
the Chief Technology Officer going back several months.<br>
<br>
<dd>Regards, Alan<br><br>
<dd>At 04/04/2018 02:13 PM, Alejandro Pisanty wrote:<br><br>
<dl>
<dd>[[--Translated text (es -> en)--]]<br><br>
<br>
<dd>Subject: Voto ALAC sobre KSK<br>
<dd>Desde:Alejandro Pisanty
<<a href="mailto:apisanty@gmail.com">apisanty@gmail.com</a>><br><br>
<dd>Colleagues,<br><br>
<dd>
inhttps://<a href="http://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Plan+to+Restart+the+Root+Key+Signing+Key+%28KSK%29+Rollover+Process">
community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Plan+to+Restart+the+Root+Key+Signing+Key+%28KSK%29+Rollover+Process</a>
you can see what ALAC will put to the vote to express the opinion of the
users about the KSK process, which as we all know is the rotation of the
"keys" of the PKI system (public key cryptography) of the
DNSSEC system that protects the system of domain names (DNS) against some
significant attacks.<br><br>
<dd>The text does not include the proposal that we made here in LACRALO
that the ALSs assume a role in the dissemination of this process among
ISPs, other providers, civil society, technical community and governments
within our reach. Moreover, said text was included in a preliminary
version and eliminated in the final. Eliminating the co-responsibility of
the ALS puts us again in the role of petitioners who do not contribute
with their own decision to the security, stability and robustness of the
DNS, the primary responsibility of ICANN.<br><br>
<dd>For this reason, I call on our ALAC representatives to insist on the
inclusion of this text and, if it is not achieved, vote against the
approval of the proposed text. Consider this proposal as a formal motion
and proceed in abbreviated time so that it can be decided before the ALAC
vote. If these times are not possible, be ex post-facto as a
protest.<br><br>
<dd>Alejandro Pisanty<br><br>
<dd>-<br>
<dd>- - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro
Pisanty Faculty of Chemistry UNAM
<a href="https://maps.google.com/?q=Av.Universidad+3000&entry=gmail&source=g">
Av.Universidad 3000</a>, 04510 Mexico DF Mexico + 52-1-5541444475 FROM
ABROAD +525541444475 FROM MEXICO SMS +525541444475
Blog:<a href="http://pisanty.blogspot.com">http://pisanty.blogspot.com</a>
LinkedIn:
<a href="http://www.linkedin.com/in/pisanty">
http://www.linkedin.com/in/pisanty</a> Join the UNAM group on LinkedIn,
<a href="http://www.linkedin.com/e/gis/22285/4A106C0C8614">
http://www.linkedin.com/e/gis/22285/4A106C0C8614</a> Twitter:
<a href="http://twitter.com/apisanty">http://twitter.com/apisanty</a>
---- >> Join ISOC Mexico,
<a href="http://www.isoc.org">http://www.isoc.org</a>. . . . . . . . . .
. . . . . . LinkedIn:
<a href="http://www.linkedin.com/in/pisanty">
http://www.linkedin.com/in/pisanty</a> Join the UNAM group on LinkedIn,
<a href="http://www.linkedin.com/e/gis/22285/4A106C0C8614">
http://www.linkedin.com/e/gis/22285/4A106C0C8614</a> Twitter:
<a href="http://twitter.com/apisanty">http://twitter.com/apisanty</a>
---- >> Join ISOC Mexico, http: //
<a href="http://www.isoc.org">www.isoc.org</a> . . . . . . . . . . . . .
. .Join the UNAM group on LinkedIn,
<a href="http://www.linkedin.com/e/gis/22285/4A106C0C8614">
http://www.linkedin.com/e/gis/22285/4A106C0C8614</a> Twitter:
<a href="http://twitter.com/apisanty">http://twitter.com/apisanty</a>
---- >> Join ISOC Mexico,
<a href="http://www.isoc.org">http://www.isoc.org</a>. . . . . . . . . .
. . . . . . Twitter:
<a href="http://twitter.com/apisanty">http://twitter.com/apisanty</a>
---- >> Join ISOC Mexico, http<br>
<dd> ://<a href="http://www.isoc.org">www.isoc.org</a>. . . . . . .
. . . . . . . . . ---- >> Join ISOC Mexico,
<a href="http://www.isoc.org">http://www.isoc.org</a> . . . . . . . . . .
. . . . . .<br><br>
<dd>[[--Original text (es)<br>
<dd>Translated by transbot 2.18-2.04<br>
<dd><a href="http://mm.icann.org/transbot_archive/03e31507e2.html">
http://mm.icann.org/transbot_archive/03e31507e2.html</a><br>
<dd>--]]<br>
<dd>_______________________________________________<br>
<dd>lac-discuss-en mailing list<br>
<dd><a href="mailto:lac-discuss-en@atlarge-lists.icann.org">
lac-discuss-en@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en</a><br>
<br>
</dl><br>
</dl><br><br>
<br>
-- <br>
- - - - - - - - - - - - - - - - - - - - - - - - - - -<br>
Dr. Alejandro Pisanty<br>
Facultad de Química UNAM<br>
Av. Universidad 3000, 04510 Mexico DF Mexico<br>
+52-1-5541444475 FROM ABROAD<br>
+525541444475 DESDE MÉXICO SMS +525541444475<br>
Blog:
<a href="http://pisanty.blogspot.com">http://pisanty.blogspot.com</a><br>
LinkedIn:
<a href="http://www.linkedin.com/in/pisanty">
http://www.linkedin.com/in/pisanty</a><br>
Unete al grupo UNAM en LinkedIn,
<a href="http://www.linkedin.com/e/gis/22285/4A106C0C8614">
http://www.linkedin.com/e/gis/22285/4A106C0C8614</a><br>
Twitter:
<a href="http://twitter.com/apisanty">http://twitter.com/apisanty</a><br>
---->> Unete a ISOC Mexico,
<a href="http://www.isoc.org">http://www.isoc.org</a><br>
. . . . . . . . .
. . . . . . .</blockquote></body>
</html>