[lac-discuss-es] RV: [ALAC-Announce] CALL FOR COMMENTS: ALAC Statement on the Proposed Bylaws Changes Regarding the Technical Liaison Group



Colegas,

el asunto de la consulta a la que se refiere este mensaje es de importancia 
relativamente alta. Trata de las modificaciones que se están proponiendo a las 
reglas aplicables al Grupo de Enlace Técnico (Technical Liaison Group o TLG). 
Estas modificaciones remueven a la persona de enlace del TLG de las decisiones 
del Board y otros espacios. 

Como consecuencia, el contacto del Board con la tecnología se diluye y vuelve 
demasiado indirecto.

Les pregunto si están Uds. de acuerdo en que LACRALO emita una opinión al ALAC, 
e instruya a nuestros/as representantes a defenderla con su voto contra las 
modificaciones propuestas, en los términos que describo de inmediato. La 
alternativa que debemos proponer es que se siga estudiando el tema con una 
solución alterna que haga efectivo al TLG sin removerlo de su función actual. 
El texto que propongo ya lo subí como comentario en la página de ALAC y dice:

"I do not think this reform is going in a good direction. It makes the 
relationship of the Board with the technical community much more tenuous and 
indirect. 
 
ALAC as an Interrnet users representation (or voice, at least) should be 
concerned that the Board may advance more in its debates and decisions without 
necessary technical views before actually soliciting them, instead of having 
the Technical Liaison Group's voice as one more when decisions are being 
shaped, since the early stages. 
 
We run the risk of privileging representation and diversity in the composition 
of the Board while sacrificing the soundness of its decisions.
 
The technical liaison acts not only as described - "watchdog" acting as a 
backstop against decisions which could be technically wrong – but also can push 
for more creative solutions to problems. It is not only the knowledge of the 
technology's constraints but the creativity based on the deep awareness of its 
potential that we could all be losing.
 
By removing the liaison instead of fixing it, we may be supporting an act of 
throwing away the baby with the bathwater. Let's not."

Quedo atento a sus comentarios y en su momento en función de ellos solicitaré 
acción de la Presidencia y la Secretaría.

Alejandro Pisanty


- - - - - - - - - - - - - - - - - - - - - - - - - - -
     Dr. Alejandro Pisanty
Facultad de Química UNAM
Av. Universidad 3000, 04510 Mexico DF Mexico



+52-1-5541444475 FROM ABROAD

+525541444475 DESDE MÉXICO SMS +525541444475
Blog: http://pisanty.blogspot.com
LinkedIn: http://www.linkedin.com/in/pisanty
Unete al grupo UNAM en LinkedIn, 
http://www.linkedin.com/e/gis/22285/4A106C0C8614
Twitter: http://twitter.com/apisanty
---->> Unete a ISOC Mexico, http://www.isoc.org
.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .

________________________________________
Desde: alac-announce-bounces@xxxxxxxxxxxxxxxxxxxxxxx 
[alac-announce-bounces@xxxxxxxxxxxxxxxxxxxxxxx] en nombre de ICANN At-Large 
Staff [staff@xxxxxxxxxxxxxxxxx]
Enviado el: sábado, 23 de noviembre de 2013 06:42
Hasta: alac-announce@xxxxxxxxxxxxxxxxxxxxxxx
Asunto: [ALAC-Announce] CALL FOR COMMENTS: ALAC Statement on the Proposed 
Bylaws Changes Regarding the Technical Liaison Group

Dear All,

Olivier Crépin-Leblond, Chair of the ALAC, has asked that a call for comments 
be made on the draft "ALAC Statement on the Proposed Bylaws Changes Regarding 
the Technical Liaison Group<https://community.icann.org/x/_xmfAg>" in 
preparation for the start of the ALAC ratification process.

The current draft can be found on the At-Large Proposed Bylaws Changes 
Regarding the Technical Liaison Group 
Workspace<https://community.icann.org/x/_xmfAg>.

Please submit any comments on the workspace using the comments function by 
06-Dec-2013 23:59 UTC.

A vote is to commence after comments have been collected.

Regards,

Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie 
Peregrine and Julia Charvolen
ICANN Policy Staff in support of ALAC
E-mail: staff@xxxxxxxxxxxxxxxxx<mailto:staff@xxxxxxxxxxxxxxxxx>
_______________________________________________