[lac-discuss-en] = iso-8859-1 == q 3A_De CONVOCATORIA_DE_COMENTARIOS = iso-8859-1 q = claraci F3n_de_Trusted_ == F3n_de_ALAC_sobre_la_Revisi = iso-8859-1 q = F3n_de_la_Comunidad_en_la_Zona_Ra = Representation????? EDz_? == iso-8859-1? q? DNSSEC_clave_de_firma_Ceremonias? =

[aidanoblia at gmail.com]

[[--Translated text (es -> en)--]]

 Subject: Re: = iso-8859-1 == q 3A_De CONVOCATORIA_DE_COMENTARIOS = iso-8859-1 q = claraci F3n_de_Trusted_ == F3n_de_ALAC_sobre_la_Revisi = iso-8859-1 q = F3n_de_la_Comunidad_en_la_Zona_Ra = Representation????? EDz_? == iso-8859-1? q? DNSSEC_clave_de_firma_Ceremonias? = 
 From: aidanoblia at gmail.com

 Dear Ftima: 




 I agree with the draft Salanieta, with comments 
 Olivier made unless the issue of financiacin, which agree 
 Alexander. 


 The word "sacred" report Salanieta if ESTN may agree 
 be changed to "solemn" because it is a solemnity and 
 compliance is an essential requirement in the process of KSK.


 Responsibility regarding the control of TCR, which mentions 
 Alejandro on the guarantee of transparency, accountability, and 
 defense of Internet users, and is set as the GenRich 
 Item 9 of the affirmation of commitment between the Department of Commerce 
 U.S. and ICANN, (the first document cited by Salanieta). 


 Also, around the same procedure Ceremony is a guarantee of 
 transparency and protection of users. There is a strict control and 
 detailed in the Declaration of DNSSEC practices of the procedure, 
 accreditation of entry of persons, etc., for the operator of the Area 
 Raz (TCR), your responsibilities are established and each of the steps 
 you must follow what is proper documents governing the 
 security at these levels of reason. 


 There are also prerequisites for the selection and appointment of 
 TCR funciny instructions for cases that can be separated 
 from office for failure.That's part of the process technician, the 
 the company Verisign, a specialist in the field is responsible. 


 As for the number of TCR, understand that it is reasonable as it is postulated 
 for the position, must know and accept their demands were 
 According selected rules and monitored compliance with requirements and 
 estprevisto that of the 21 selected will only designated some 
 for the two ceremonies conducted simultaneously at different 
 places in 4 opportunities each year. The amount will cover ms 
 possible contingencies. 


 In relacina financiacin see important maintain strict 
 independence estcontrolando procedure, among whom are 
 designed to control the process and who are responsible for 
 same, between these last ICANN. This, in addition to exposing and Alejandro 
 there are many whose travel costs that perhaps podray 
 must do without, given the possibility of participacina distance, 
 that is not the case of the TCR, which have to be physically present. 




 By the time I could not climb the commentary wiki 


 Greetings to all 






 Ada 








 On February 2, 2014, 18:10, Alejandro Pisanty <apisanty at gmail.com> wrote: 


> Fátima,
>
> mil gracias por este mensaje. El proceso descrito - firmado de "llaves"
> criptográficas que están en la base de la confiabilidad de DNSSEC - es de
> gran importancia.
>
> En el espacio de ALAC se ha formulado un borrador de texto al que he hecho
> los siguientes comentarios:
>
> "The statement should be expanded to the recognition of the unique
> combination the key-signing and TCRs make of broad participation,
> transparency and accountability in order to serve the central function of
> preserving and enhancing the stability, security and resilience of the DNS,
> thus engendering widespread trust.
>
>
> I do not believe ALAC should propose any increase in processes;
> streamlining should be the direction.
>
>
> As for support for TCRs, a statement that acting as a TCR should be
> cost-neutral for those not supported by firms or other entities should
> suffice. A statement in very restrained terms would go counter to the
> possibility that the draft be read as suggesting the poorly warranted
> creation of yet another source of travel funds."
>
>
> Me permito presentar una moción a favor de que este texto sea considerado
> representativo de la opinión de LACRALO.
>
>
> Alejandro Pisanty
>
>
> 2014-01-31 <fatimacambronero at gmail.com>:
>
> >
> > [[--Translated text (en -> es)--]]
> >
> >  Asunto: Fwd: CONVOCATORIA DE COMENTARIOS: Declaración de ALAC sobre la
> > Revisión de Trusted Representación de la Comunidad en la Zona Raíz DNSSEC
> > clave de firma Ceremonias
> >  De: fatimacambronero at gmail.com
> >
> >  FYI,
> >
> >
> >
> >
> >  ---------- Mensaje reenviado ----------
> >  De: ICANN At-Large <staff at atlarge.icann.org>
> >  Fecha: 2014-01-31
> >  Asunto: [ALAC-Anuncie] SOLICITUD DE COMENTARIOS: Declaración de ALAC
> > sobre la revisión del
> >  Representación de la Comunidad de confianza en la Zona Raíz DNSSEC clave
> > de firma Ceremonias
> >  Para: &quot;alac-announce at atlarge-lists.icann.org&quot; &lt;
> >  alac-announce at atlarge-lists.icann.org&gt;
> >
> >
> >
> >
> >  Queridos todos,
> >
> >
> >  Olivier Crepin-Leblond, Presidente de la ALAC, ha pedido que un llamado
> a
> > la
> >  los comentarios se harán en el proyecto de &quot;Declaración de ALAC
> > sobre el examen de confianza
> >  Representación de la Comunidad en la Zona Raíz DNSSEC clave de firma
> > Ceremonias &lt;
> >  https://community.icann.org/x/nge6Ag>"
> >  Proceso de ratificación de ALAC.
> >
> >
> >  El proyecto actual, así como información adicional sobre el comentario
> > público,
> >  se puede encontrar en el At-Large Revisión de Trusted Comunidad
> > Representación en
> >  Zona Raíz DNSSEC clave de firma Ceremonias Espacio de trabajo &lt;
> >  https://community.icann.org/x/nge6Ag>.
> >
> >
> >  Por favor, envíe cualquier comentario sobre el área de trabajo
> utilizando
> > la función de comentarios por
> >  7-Febrero-2014 23:59
> >
> >
> >  Saludos,
> >
> >
> >  Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie
> >  Peregrine y Julia Charvolen
> >  El personal de ICANN Política en apoyo de ALAC
> >  E-mail: staff at atlarge.icann.org <mailto:staff at atlarge.icann.org>
> >  _______________________________________________
> >
> >
> >



[[--Original text (es)
http://mm.icann.org/transbot_archive/f1f744368c.html
--]]