January 2015 - lac-discuss-en

Re: [lac-discuss-en] ??????? = Utf-8 q REMINDER = 3A_Invitaci = C3 = B3n_Reuni = = utf-8 q = C3 = B3n _ / _ LACRALO_llamada_mensual _-_ Lunes_19_de_enero_de = = utf-8 q _2015_se_proporcionar = C3???? = A1_interpretaci = C3 = B3n _ / _ Portug? = =? utf-8? q? u = C3 = A9s? =
by amedinagomez＠gmail.com Jan. 19, 2015

Jan. 19, 2015

[[--Translated text (es -> en)--]] Subject: Re:??????? = Utf-8 q REMINDER = 3A_Invitaci = C3 = B3n_Reuni = = utf-8 q = C3 = B3n _ / _ LACRALO_llamada_mensual _-_ Lunes_19_de_enero_de = = utf-8 q _2015_se_proporcionar = C3???? = A1_interpretaci = C3 = B3n _ / _ Portug? = =? utf-8? q? u = C3 = A9s? = From: amedinagomez(a)gmail.com Good afternoon. I confirm attendance Best regard The 19 January 2015 12:41, <staff(a)atlarge.icann.org> i wrote: > > [[--Translated text (en -> es)--]] > > Asunto: RECORDATORIO: Invitación Reunión / LACRALO llamada mensual - > Lunes 19 de enero de 2015 se proporcionará interpretación / Portugués > Desde: staff(a)atlarge.icann.org > > > > Si necesita una línea de salida por favor póngase en contacto con > At-Large personal staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> > con su número preferido. > > > Si Necesita Una Llamada a su telefono, please PNGasa en contacto con el > personal de At-Large en staff(a)atlarge.icann.org <mailto: > staff(a)atlarge.icann.org> estafar Preferido su nmero. > > > > > Queridos todos, > > > > > > > La siguiente llamada LACRALO mensual está programada para el Lunes, 19 de > enero 2015 a las 2300 GMT. > > > > > > > Se proporcionará interpretación en portugués. > > > > > > > Para otras veces: > > > http://tinyurl.com/pjbcfkx > > > > > > > El proyecto de programa y de llamadas detalles están disponibles en: > > > https://community.icann.org/x/SoYQAw > > > > > > > Adobe Connect: > > > http://icann.adobeconnect.com/lacralo > > > > > > > ID de conferencia: > > > > > > > EN 1638 > > > ES 1738 > > > PT 5393 > > > > > > > Espacio de trabajo Wiki: > > > https://community.icann.org/x/NJQi > > > > > > > Por favor confirme su línea de salida y el número preferido de: > > > staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> > > > > > > > > > > > Gracias. > > > Saludos, > > > Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie > Peregrine y Terri Agnew > El personal de ICANN Política en apoyo de ALAC > E-mail: staff(a)atlarge.icann.org > <applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,% > 20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org > > > Facebook: www.facebook.com/icann.atlarge < > https://www.facebook.com/icann.atlarge> > Twitter:ICANN_AtLarge < https://twitter.com/ICANN_AtLarge> > > > > > > > _____________________________________________ > > > lac-discuss-en lista de correo > > > lac-discuss-en(a)atlarge-lists.icann.org <mailto: > lac-discuss-en(a)atlarge-lists.icann.org> > > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > > > > > > > > > > > > > > > > _______________________________________________ > > > [[--Original text (es) http://mm.icann.org/transbot_archive/ab72d86554.html --]]

1 0

REMINDER: Meeting Invitation/ LACRALO monthly call - Monday 19 January 2015/ Portuguese interpretation will be provided
by ICANN At-Large Staff Jan. 19, 2015

Jan. 19, 2015

Dear All, The next monthly LACRALO call is scheduled on Monday, 19 January 2015 at 2300 UTC. Portuguese interpretation will be provided. For other times: http://tinyurl.com/pjbcfkx The draft agenda (to be updated) and call details are available at: https://community.icann.org/x/SoYQAw Adobe Connect: http://icann.adobeconnect.com/lacralo Conference ID: EN 1638 ES 1738 PT 5393 Wiki workspace: https://community.icann.org/x/NJQi Please confirm your dial-out and preferred number to: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann.atlarge<https://www.facebook.com/icann.atlarge> Twitter: @ICANN_AtLarge<https://twitter.com/ICANN_AtLarge> _____________________________________________ lac-discuss-en mailing list lac-discuss-en(a)atlarge-lists.icann.org<mailto:lac-discuss-en@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en

1 1

Hallo, hola, olá to the new, more powerful Google Translate app
by Dev Anand Teelucksingh Jan. 19, 2015

Jan. 19, 2015

Google has updated the Google Translate app for iOS and Android devices The latest update offers powerful and impressive translation capabilities, First, Google Translate offers instant translation using your camera to recognize and to automatically overlay the translated text on the screen. (this is the technology from Word Lens which Google acquired some time ago). Instant translation currently works for translation from English to and from French, German, Italian, Portuguese, Russian and Spanish Note that the Google Translate app can still scan a photo taken from your phone and to get a translation of it in 36 languages. What's more interesting is the ability for your phone to capture audio from two speakers and have Google Translate speak a translated version so two speakers speaking different languages can communicate back and forth. See the 30 second YouTube video to see it in action http://youtu.be/jZII2ksensw This follows the release of Skype's Translator Preview last month (see http://blogs.skype.com/2014/12/15/skype-translator-preview-an-exciting-jour…) However Skype Translate Preview is not generally available (you have to register and you then may be offered to participate) ; Google Translate is available now for iOS and Android phones Read the full post on the Google Translate blog : http://googletranslate.blogspot.com/2015/01/hallo-hola-ola-to-new-more-powe… --- Dev Anand

1 0

Fwd: FW: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by aidanoblia＠gmail.com Jan. 19, 2015

Jan. 19, 2015

[[--Translated text (es -> en)--]] Subject: Fwd: FW: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks From: aidanoblia(a)gmail.com ---------- Forwarded message ---------- From: Aida Noblia <aidanoblia(a)gmail.com> Date: January 19, 2015, 13:14 Subject: Re: [lac-discuss-en] FW: [ALAC] Request for Board Risk Committee Feedback on Top 5 ICANN Enterprise Risks To: Alberto Soto <asoto(a)ibero-americano.org> tEstoy agreed to study the issue of risk is important for the work performed by ALS and in developing partiipación policies. There are many aspects that can refer the risks and each has its requirements. The risk involves the possibility of unfavorable conditions for operation of a system, and this is the Internet ecosystem.It has many branches and lots type risks, taking into account multiple components and situations Internet ecosystem, Alberto mentioned the safety, and Internet based is the proper functioning of the computer system, thereby which the authoritative word of computer we can say that there technical standards that relate to different aspects of the systems computer. (ISO, AENOR, NIST, etc ..) From the little that there are different families of standards for various aspects of a computer system.O Anyway, for the different parts that make up the computer system: a) physical part: local, machines, cables, networking, and input peripherals information output (keyboard, mouse, screen, etc) b) logical part: software: basic and applications, all matters relating to the programs and the security of data in the system, c) documentation from I was also considered a part of the computer system (Instructions for use of machines, operating software, programs, etc) d) User: which is an important element to consider within that system, and may be internal or external user, ie employees or officials and users outside the company. They must have different permissions for access to different parts of the system, according to their skills and needs. This On January 18, 2015, 13:20 Alberto Soto <asoto(a)ibero-americano.org> wrote: Forgot a point on the risk classification, which is synthetically > siguiente: > > 1. CrÃ©ditos > > 2. Legal > > 3. Marketing/precios > > 4. Estrategia > > 5. ReputaciÃ³n > > Saludos! > > > > Alberto > > > > De: Alejandro Pisanty [mailto:apisanty@gmail.com] > Enviado el: domingo, 18 de enero de 2015 03:39 a.m. > Para: Alberto Soto > CC: LACRALO EspaÃ±ol > Asunto: Re: [lac-discuss-es] RV: [ALAC] Board Risk Committee Request for > Feedback on Top 5 ICANN Enterprise Risks > > > > Alberto, > > > > gracias por tomar esta iniciativa, productiva y concreta. > > > > Pienso que el tema que mejor podemos desarrollar es el del riesgo de > cambio en el modelo de gobernanza que seÃ±alas alrededor del cambio en las > reglas de toma de decisiones del GAC; pasarÃa del consenso a la votaciÃ³n y > se "contagiarÃa" al Board. > > > > Como elemento aislado y puntual es importante, pero lo es mucho mÃ¡s si se > asocia a un cambio de cultura que produzca un alejamiento del consenso mÃ¡s > general. > > > > Â¿Como ordenarÃan otros/as representantes de organizaciones en LACRALO los > riesgos que hemos seÃ±alado hasta ahora? Â¿CÃ³mo los compararÃan con los de > otros Ã³rdenes (financiero, seguridad informÃ¡tica, etc.) que ha seÃ±alado > Alberto? > > > > Alejandro Pisanty > > > > 2015-01-17 22:35 GMT-06:00 Alberto Soto <asoto(a)ibero-americano.org>: > > Alejandro y todos. Siempre es beneficioso llevar a discusiÃ³n estos temas. > Yo no sÃ© si podrÃa invocar riesgo sistÃ©mico, muy particular de los temas > financieros, aunque reconozco que quizÃ¡s podrÃamos llegar a determinar un > riesgo que produzca un efecto cascada dentro de la organizaciÃ³n. > > Pero podemos proponer riesgos. > > > > Para que podamos entender y quizÃ¡s rÃ¡pidamente proponer algo, cito > parcialmente el chÃ¡rter del Board Risk Committee tal como fuera definido en > el 2009: > > > > âA: SupervisiÃ³n de la gestiÃ³n de riesgo de la ICANN como organizaciÃ³n, > incluyendo las siguientes actividades: > > > > 1. Revisar y asesorar sobre ICANN polÃticas, planes y programas > relacionados con la gestiÃ³n de riesgos; > > 2. Seguimiento de la eficacia de los programas de gestiÃ³n de > riesgos, incluida la gestiÃ³n y control del riesgo operacional; > > 3. La supervisiÃ³n de la exposiciÃ³n al riesgo no financiero > significativo para la ICANN y las medidas adoptadas para supervisar y > controlar dicha exposiciÃ³n; > > 4. Mantenerse informado sobre la ICANN condiciones y la obtenciÃ³n de > la familiaridad con la ICANN procesos con el fin de identificar los > posibles riesgos futuros y asesorar sobre los planes para hacer frente a > estos riesgos, segÃºn proceda; y > > 5. RevisiÃ³n de otras Ã¡reas de concentraciÃ³n del riesgo adecuada. > > > > B: SupervisiÃ³n de actividades operacionales, como la revisiÃ³n de la > informaciÃ³n y el seguimiento de la eficacia de la gestiÃ³n de las > actividades operacionales tales como: > > > > 1. La eficacia de la tecnologÃa utilizada por ICANN ; > > 2. La adecuaciÃ³n de la ICANN polÃticas de continuidad de negocios; y > > 3. Enfrentar los cambios en el entorno empresarial que pueda ser > importante para ICANN operaciones.â > > > > AdemÃ¡s de este chÃ¡rter, tenemos que tener en cuenta que la temÃ¡tica de > riesgos ha sido dividida en: > > - CrÃ©ditos > > - Legal > > - Marketing/precios > > - ReputaciÃ³n > > Con esto quizÃ¡s podrÃamos enfocarnos en A.3 y en B. en sus tres puntos. > > Y sugerirÃa como riesgos: > > > > - Seguridad en los sistemas de ICANN: El hackeo de hace poco > tiempo en los sistemas de Whois â wiki â CZDS. QuÃ© tecnologÃa estÃ¡n > utilizando? HiriÃ³ mucho la reputaciÃ³n de ICANN. > > - Cambio en el sistema de votaciÃ³n del Board para asimilarlo a > los del GAC. Tiene relaciÃ³n con el B.2. pero sus resultados van en contra > del sistema de mÃºltiples partes interesadas. Si el fundamento es que el GAC > se reÃºne menos veces, ya hasta hoy fue mÃ¡s efectivo el sistema del Board de > ICANN, que el GAC se reuna una vez mÃ¡s al aÃ±o y se asimile a ICANN. > > - Cuando se creÃ³ el ICG se tuvo en cuenta solo a determinados > componentes del modelo de mÃºltiples partes interesadas. En lo que a > nosotros respecta, no estaba previsto que ALAC enviara un informe > participativo. El usuario individual al cual representamos no estÃ¡ dentro > de la continuidad de negocios de ICANN, ante la transiciÃ³n IANA? > > > > Espero que haya participaciÃ³n, y aunque no podamos hacer un informe formal > de LACRALO, quizÃ¡s podamos enviar sugerencias individualmente. Digo que no > podamos hacerlos formalmente no solo por el tiempo, sino porque hay quienes > entienden que no hay necesidad de que LACRALO haga proposiciones. Se estÃ¡ > discutiendo un procedimiento al respecto. > > Saludos cordiales > > > > Alberto Soto > > > > > > De: Alejandro Pisanty [mailto:apisanty@gmail.com <mailto: > apisanty(a)gmail.com> ] > Enviado el: sÃ¡bado, 17 de enero de 2015 10:01 p.m. > Para: Alberto Soto > CC: LACRALO EspaÃ±ol > Asunto: Re: [lac-discuss-es] RV: [ALAC] Board Risk Committee Request for > Feedback on Top 5 ICANN Enterprise Risks > > > > Alberto, > > > > quedan dos semanas. Â¿No serÃa un tema apto para discusiÃ³n en LACRALO? > Aunque no produzcamos una expresiÃ³n colectiva la discusiÃ³n podrÃa alimentar > los puntos de vista individuales. > > > > Yo provocarÃa su inicio proponiendo como un riesgo digno de inclusiÃ³n > "expansiÃ³n ilimitada de At Large sin rendiciÃ³n de cuentas ni medidas de > efectividad"... (hay otros, pero Ã©ste puede ser uno que permita calibrar la > forma de entrar a discutirlos). > > > > Â¿TÃº cuÃ¡l consideras que sea el riesgo sistÃ©mico de mayor importancia sobre > el cual pudiÃ©ramos discutir de manera constructiva y eficaz? > > > > Saludos cordiales. > > > > Alejandro Pisanty > > > > On Sat, Jan 17, 2015 at 2:55 PM, Alberto Soto <asoto(a)ibero-americano.org > <mailto:asoto@ibero-americano.org> > wrote: > > Estimados, les pido por favor que si tienen alguna sugerencia sobre este > tema, la envÃen directamente al mail indicado. Queda poco tiempo. > Gracias y saludos cordiales > > Alberto Soto > > -----Mensaje original----- > De: alac-bounces(a)atlarge-lists.icann.org <mailto: > alac-bounces(a)atlarge-lists.icann.org> > [mailto:alac-bounces@atlarge-lists.icann.org <mailto: > alac-bounces(a)atlarge-lists.icann.org> ] En nombre de Alan Greenberg > Enviado el: sÃ¡bado, 17 de enero de 2015 01:03 p.m. > Para: ALAC > Asunto: Re: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN > Enterprise Risks > > If anyone has any thoughts on this, please forward and I will collate them > and send them in. > > Alan > > At 17/01/2015 10:10 AM, David Olive wrote: > > >Below is a note from the ICANN Board Risk Committee Co-Chairs. > > > >--------------------------------------------- > > > >Dear SO/AC/SG: > > > >The Board Risk Committee (BRC) is tasked to provide oversight and > >guidance into enterprise risk identification and remediation for ICANN. > >ICANN has developed a risk management framework and methodology that is > >used to identify, mitigate and monitor risks. > > > >The purpose of this email is to reach out to you, the SO/AC/SG > >Leadership, to ask your group to identify what it believes are the top > >five enterprise-wide risks to ICANN. This feedback process allows us to > >calibrate and evaluate risks identified internally with those > >identified by the community. > > > >We envision a response as an enumerated list of the top five enterprise > >risks that your SO or AC group believes ought to be ICANNâs top > >priorities. > > > >We ask to provide a written response via email by 5 February 2015. We > >anticipate discussion on these identified risks in the SO/AC > >Constituency meetings with the Board during ICANN 52 in Singapore. > >Please send all written responses directly to > ><mailto:Enterprise-Risk@ICANN.Org <mailto:Enterprise-Risk@ICANN.Org> > >Enterprise-Risk(a)ICANN.Org <mailto:Enterprise-Risk@ICANN.Org> . > > > >We understand that you may not have the time to develop a formal > >response from your SO or AC group. In that case, we would appreciate > >you providing us with your own personal views or those of a small > >sub-set of your SO or AC group, but please let us know if you have done > >so. We will iterate the process to improve it and comments on possible > >improvements are most welcome. > > > >Again, thank you in advance and we look forward to your input. > > > >Regards, > >Mike Silber & Ram Mohan > >ICANN Board Risk Committee Co-Chairs > > > > > > > >David A. Olive > >Vice President, Policy Development Support General Manager, ICANN > >Regional Headquarters âIstanbul Hakki Yeten Cad. Selenium Plaza No:10/C > >K:10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned > >Names and Numbers (ICANN) > > > >Direct Line: +90.212.999.6212 > >Mobile: + 1. 202.341.3611 > >Mobile: +90.533.341.6550 > >Email: <mailto:david.olive@icann.org <mailto:david.olive@icann.org> > > david.olive(a)icann.org <mailto:david.olive@icann.org> > >www.icann.org <http://www.icann.org> > > > _______________________________________________ > ALAC mailing list > ALAC(a)atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> > https://atlarge-lists.icann.org/mailman/listinfo/alac > > At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: > > https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA > C) > > > --- > El software de antivirus Avast ha analizado este correo electrÃ³nico en > busca de virus. > http://www.avast.com > > _______________________________________________ > lac-discuss-es mailing list > lac-discuss-es(a)atlarge-lists.icann.org <mailto: > lac-discuss-es(a)atlarge-lists.icann.org> > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > http://www.lacralo.org > > > > > > > > -- > > - - - - - - - - - - - - - - - - - - - - - - - - - - - > 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 > . . . . . . . . . . . . . . . . > > > > _____ > > > <http://www.avast.com/> > > <http://www.avast.com/> El software de antivirus Avast ha analizado este > correo electrÃ³nico en busca de virus. > www.avast.com > > <http://www.avast.com/> > > <http://www.avast.com/> > > > > <http://www.avast.com/> > > <http://www.avast.com/> -- > > <http://www.avast.com/> - - - - - - - - - - - - - - - - - - - - - - - - > - - - > 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 > . . . . . . . . . . . . . . . . > > > > --- > El software de antivirus Avast ha analizado este correo electrÃ³nico en > busca de virus. > http://www.avast.com > _______________________________________________ > lac-discuss-es mailing list > lac-discuss-es(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > http://www.lacralo.org > Aida Noblia - Aida Noblia _______________________________________________ lac-discuss-en mailing list lac-discuss-es(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es http://www.lacralo.org [[--Original text (es) http://mm.icann.org/transbot_archive/013724b2ff.html --]]

1 0

Fwd: FW: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by aidanoblia＠gmail.com Jan. 19, 2015

Jan. 19, 2015

[[--Translated text (es -> en)--]] Subject: Fwd: FW: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks From: aidanoblia(a)gmail.com ---------- Forwarded message ---------- From: Aida Noblia <aidanoblia(a)gmail.com> Date: January 19, 2015, 13:20 Subject: Re: [lac-discuss-en] FW: [ALAC] Request for Board Risk Committee Feedback on Top 5 ICANN Enterprise Risks To: Alberto Soto <asoto(a)ibero-americano.org> I suffered a risk: it slipped an email unfinished .. Do not know if this is interest as this know much computer. All of the above would be regarding technological security is vital to the system name Domain. It can also be seen from the standpoint of the safety of data: in particular whois personal data, as there is already a team studying this topic. Other aspects were mentioned by Vanda and agree that can be useful and Alejandro mentioned a special theme regarding rules regarding statements by consensus or majority. I have not clear this issue in terms of the potential risks, but it might be interesting to analyze, as regards decisions and declarations. Regards On January 19, 2015, 13:14 Aida Noblia <aidanoblia(a)gmail.com> wrote: tEstoy agreed to study the issue of risk is important for > el trabajo que realizan las ALS y su partiipación en el desarrollo de > políticas. Hay muchos aspectos a los que se pueden referir los riesgos y > cada uno tiene sus requisitos. El riesgo implica la posibilidad de > situaciones desfavorables para el funcionamiento de un sistema, y esto es > el ecosistema de Internet. Tiene muchas derivaciones y hay mucho tipo de > riesgos, teniendo en cuenta las múltiples componentes y situaciones del > ecosistema de internet, Alberto mencionó la seguridad tecnológica, y la > base de Internet es el buen funcionamiento del sistema informático, con lo > cual la palabra autorizada de los informáticos nos podrá decir que existen > normas técnicas que refieren a los distintos aspectos de los sistemas > informáticos. (ISO, AENOR, NIST, etc..) De lo poco que se hay distintas > familias de normas para distintos aspectos de un sistema informático. O > sea, para las distintas partes que componen el sistema informático: a) > parte física: locales, máquinas, cables, redes, periféricos de entrada y de > salida de información ( teclado, mouse, pantalla, etc) b) parte lógica: > software: de base y aplicativos , todo lo relativo a los programas y a la > seguridad de los datos contenidos en el sistema , c) la documentación desde > lo que yo se también es considerada una parte del sistema informático > (instrucciones de uso de máquinas, de funcionamiento de software, > programas, etc) d) el usuario: que es un importante elemento a considerar > dentro de ese sistema, y puede ser usuario externo o interno, es decir, > empleados o funcionarios y usuarios externos a la empresa. Ellos deben > tener diferentes permisos para acceso a diferentes partes del sistema, > según sus competencias y necesidades. Todo esto > > El 18 de enero de 2015, 13:20, Alberto Soto <asoto(a)ibero-americano.org> > escribió: > > Olvidé un punto en la clasificación de riesgos, que sintéticamente es la >> siguiente: >> >> 1. Créditos >> >> 2. Legal >> >> 3. Marketing/precios >> >> 4. Estrategia >> >> 5. Reputación >> >> Saludos! >> >> >> >> Alberto >> >> >> >> De: Alejandro Pisanty [mailto:apisanty@gmail.com] >> Enviado el: domingo, 18 de enero de 2015 03:39 a.m. >> Para: Alberto Soto >> CC: LACRALO Español >> Asunto: Re: [lac-discuss-es] RV: [ALAC] Board Risk Committee Request for >> Feedback on Top 5 ICANN Enterprise Risks >> >> >> >> Alberto, >> >> >> >> gracias por tomar esta iniciativa, productiva y concreta. >> >> >> >> Pienso que el tema que mejor podemos desarrollar es el del riesgo de >> cambio en el modelo de gobernanza que señalas alrededor del cambio en las >> reglas de toma de decisiones del GAC; pasaría del consenso a la votación y >> se "contagiaría" al Board. >> >> >> >> Como elemento aislado y puntual es importante, pero lo es mucho más si se >> asocia a un cambio de cultura que produzca un alejamiento del consenso más >> general. >> >> >> >> ¿Como ordenarían otros/as representantes de organizaciones en LACRALO los >> riesgos que hemos señalado hasta ahora? ¿Cómo los compararían con los de >> otros órdenes (financiero, seguridad informática, etc.) que ha señalado >> Alberto? >> >> >> >> Alejandro Pisanty >> >> >> >> 2015-01-17 22:35 GMT-06:00 Alberto Soto <asoto(a)ibero-americano.org>: >> >> Alejandro y todos. Siempre es beneficioso llevar a discusión estos temas. >> Yo no sé si podría invocar riesgo sistémico, muy particular de los temas >> financieros, aunque reconozco que quizás podríamos llegar a determinar un >> riesgo que produzca un efecto cascada dentro de la organización. >> >> Pero podemos proponer riesgos. >> >> >> >> Para que podamos entender y quizás rápidamente proponer algo, cito >> parcialmente el chárter del Board Risk Committee tal como fuera definido en >> el 2009: >> >> >> >> “A: Supervisión de la gestión de riesgo de la ICANN como organización, >> incluyendo las siguientes actividades: >> >> >> >> 1. Revisar y asesorar sobre ICANN políticas, planes y programas >> relacionados con la gestión de riesgos; >> >> 2. Seguimiento de la eficacia de los programas de gestión de >> riesgos, incluida la gestión y control del riesgo operacional; >> >> 3. La supervisión de la exposición al riesgo no financiero >> significativo para la ICANN y las medidas adoptadas para supervisar y >> controlar dicha exposición; >> >> 4. Mantenerse informado sobre la ICANN condiciones y la obtención >> de la familiaridad con la ICANN procesos con el fin de identificar los >> posibles riesgos futuros y asesorar sobre los planes para hacer frente a >> estos riesgos, según proceda; y >> >> 5. Revisión de otras áreas de concentración del riesgo adecuada. >> >> >> >> B: Supervisión de actividades operacionales, como la revisión de la >> información y el seguimiento de la eficacia de la gestión de las >> actividades operacionales tales como: >> >> >> >> 1. La eficacia de la tecnología utilizada por ICANN ; >> >> 2. La adecuación de la ICANN políticas de continuidad de negocios; y >> >> 3. Enfrentar los cambios en el entorno empresarial que pueda ser >> importante para ICANN operaciones.” >> >> >> >> Además de este chárter, tenemos que tener en cuenta que la temática de >> riesgos ha sido dividida en: >> >> - Créditos >> >> - Legal >> >> - Marketing/precios >> >> - Reputación >> >> Con esto quizás podríamos enfocarnos en A.3 y en B. en sus tres puntos. >> >> Y sugeriría como riesgos: >> >> >> >> - Seguridad en los sistemas de ICANN: El hackeo de hace poco >> tiempo en los sistemas de Whois – wiki – CZDS. Qué tecnología están >> utilizando? Hirió mucho la reputación de ICANN. >> >> - Cambio en el sistema de votación del Board para asimilarlo a >> los del GAC. Tiene relación con el B.2. pero sus resultados van en contra >> del sistema de múltiples partes interesadas. Si el fundamento es que el GAC >> se reúne menos veces, ya hasta hoy fue más efectivo el sistema del Board de >> ICANN, que el GAC se reuna una vez más al año y se asimile a ICANN. >> >> - Cuando se creó el ICG se tuvo en cuenta solo a determinados >> componentes del modelo de múltiples partes interesadas. En lo que a >> nosotros respecta, no estaba previsto que ALAC enviara un informe >> participativo. El usuario individual al cual representamos no está dentro >> de la continuidad de negocios de ICANN, ante la transición IANA? >> >> >> >> Espero que haya participación, y aunque no podamos hacer un informe >> formal de LACRALO, quizás podamos enviar sugerencias individualmente. Digo >> que no podamos hacerlos formalmente no solo por el tiempo, sino porque hay >> quienes entienden que no hay necesidad de que LACRALO haga proposiciones. >> Se está discutiendo un procedimiento al respecto. >> >> Saludos cordiales >> >> >> >> Alberto Soto >> >> >> >> >> >> De: Alejandro Pisanty [mailto:apisanty@gmail.com <mailto: >> apisanty(a)gmail.com> ] >> Enviado el: sábado, 17 de enero de 2015 10:01 p.m. >> Para: Alberto Soto >> CC: LACRALO Español >> Asunto: Re: [lac-discuss-es] RV: [ALAC] Board Risk Committee Request for >> Feedback on Top 5 ICANN Enterprise Risks >> >> >> >> Alberto, >> >> >> >> quedan dos semanas. ¿No sería un tema apto para discusión en LACRALO? >> Aunque no produzcamos una expresión colectiva la discusión podría alimentar >> los puntos de vista individuales. >> >> >> >> Yo provocaría su inicio proponiendo como un riesgo digno de inclusión >> "expansión ilimitada de At Large sin rendición de cuentas ni medidas de >> efectividad"... (hay otros, pero éste puede ser uno que permita calibrar la >> forma de entrar a discutirlos). >> >> >> >> ¿Tú cuál consideras que sea el riesgo sistémico de mayor importancia >> sobre el cual pudiéramos discutir de manera constructiva y eficaz? >> >> >> >> Saludos cordiales. >> >> >> >> Alejandro Pisanty >> >> >> >> On Sat, Jan 17, 2015 at 2:55 PM, Alberto Soto <asoto(a)ibero-americano.org >> <mailto:asoto@ibero-americano.org> > wrote: >> >> Estimados, les pido por favor que si tienen alguna sugerencia sobre este >> tema, la envíen directamente al mail indicado. Queda poco tiempo. >> Gracias y saludos cordiales >> >> Alberto Soto >> >> -----Mensaje original----- >> De: alac-bounces(a)atlarge-lists.icann.org <mailto: >> alac-bounces(a)atlarge-lists.icann.org> >> [mailto:alac-bounces@atlarge-lists.icann.org <mailto: >> alac-bounces(a)atlarge-lists.icann.org> ] En nombre de Alan Greenberg >> Enviado el: sábado, 17 de enero de 2015 01:03 p.m. >> Para: ALAC >> Asunto: Re: [ALAC] Board Risk Committee Request for Feedback on Top 5 >> ICANN >> Enterprise Risks >> >> If anyone has any thoughts on this, please forward and I will collate them >> and send them in. >> >> Alan >> >> At 17/01/2015 10:10 AM, David Olive wrote: >> >> >Below is a note from the ICANN Board Risk Committee Co-Chairs. >> > >> >--------------------------------------------- >> > >> >Dear SO/AC/SG: >> > >> >The Board Risk Committee (BRC) is tasked to provide oversight and >> >guidance into enterprise risk identification and remediation for ICANN. >> >ICANN has developed a risk management framework and methodology that is >> >used to identify, mitigate and monitor risks. >> > >> >The purpose of this email is to reach out to you, the SO/AC/SG >> >Leadership, to ask your group to identify what it believes are the top >> >five enterprise-wide risks to ICANN. This feedback process allows us to >> >calibrate and evaluate risks identified internally with those >> >identified by the community. >> > >> >We envision a response as an enumerated list of the top five enterprise >> >risks that your SO or AC group believes ought to be ICANN’s top >> >priorities. >> > >> >We ask to provide a written response via email by 5 February 2015. We >> >anticipate discussion on these identified risks in the SO/AC >> >Constituency meetings with the Board during ICANN 52 in Singapore. >> >Please send all written responses directly to >> ><mailto:Enterprise-Risk@ICANN.Org <mailto:Enterprise-Risk@ICANN.Org> >> >Enterprise-Risk(a)ICANN.Org <mailto:Enterprise-Risk@ICANN.Org> . >> > >> >We understand that you may not have the time to develop a formal >> >response from your SO or AC group. In that case, we would appreciate >> >you providing us with your own personal views or those of a small >> >sub-set of your SO or AC group, but please let us know if you have done >> >so. We will iterate the process to improve it and comments on possible >> >improvements are most welcome. >> > >> >Again, thank you in advance and we look forward to your input. >> > >> >Regards, >> >Mike Silber & Ram Mohan >> >ICANN Board Risk Committee Co-Chairs >> > >> > >> > >> >David A. Olive >> >Vice President, Policy Development Support General Manager, ICANN >> >Regional Headquarters –Istanbul Hakki Yeten Cad. Selenium Plaza No:10/C >> >K:10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned >> >Names and Numbers (ICANN) >> > >> >Direct Line: +90.212.999.6212 >> >Mobile: + 1. 202.341.3611 >> >Mobile: +90.533.341.6550 >> >Email: <mailto:david.olive@icann.org <mailto:david.olive@icann.org> > >> david.olive(a)icann.org <mailto:david.olive@icann.org> >> >www.icann.org <http://www.icann.org> >> > >> _______________________________________________ >> ALAC mailing list >> ALAC(a)atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> >> https://atlarge-lists.icann.org/mailman/listinfo/alac >> >> At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: >> >> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA >> C) >> >> >> --- >> El software de antivirus Avast ha analizado este correo electrónico en >> busca de virus. >> http://www.avast.com >> >> _______________________________________________ >> lac-discuss-es mailing list >> lac-discuss-es(a)atlarge-lists.icann.org <mailto: >> lac-discuss-es(a)atlarge-lists.icann.org> >> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es >> >> http://www.lacralo.org >> >> >> >> >> >> >> >> -- >> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - >> 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 >> . . . . . . . . . . . . . . . . >> >> >> >> _____ >> >> >> <http://www.avast.com/> >> >> <http://www.avast.com/> El software de antivirus Avast ha analizado >> este correo electrónico en busca de virus. >> www.avast.com >> >> <http://www.avast.com/> >> >> <http://www.avast.com/> >> >> >> >> <http://www.avast.com/> >> >> <http://www.avast.com/> -- >> >> <http://www.avast.com/> - - - - - - - - - - - - - - - - - - - - - - - - >> - - - >> 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 >> . . . . . . . . . . . . . . . . >> >> >> >> --- >> El software de antivirus Avast ha analizado este correo electrónico en >> busca de virus. >> http://www.avast.com >> _______________________________________________ >> lac-discuss-es mailing list >> lac-discuss-es(a)atlarge-lists.icann.org >> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es >> >> http://www.lacralo.org >> > > > > -- > Aida Noblia > Aida Noblia - Aida Noblia _______________________________________________ lac-discuss-en mailing list lac-discuss-es(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es http://www.lacralo.org [[--Original text (es) http://mm.icann.org/transbot_archive/8d4e919bd9.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by asoto＠ibero-americano.org Jan. 19, 2015

Jan. 19, 2015

[[--Translated text (es -> en)--]] Subject: Re: RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks From: asoto(a)ibero-americano.org Dear Alfredo, comes well your knowledge of Risk Management. Please, if you can see the issues we have raised risk or other risk issue you consider ICANN to see it from your technical standpoint. Thank You! Alberto Soto From: Alfredo Lopez [mailto: alfredolopezh(a)gmail.com] Posted on: Monday, January 19, 2015 12:33 am To: Alberto Soto CC: LACRALO Spanish Subject: Re: [lac-discuss-en] FW: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks Dear Alberto, according to my experience and based on research we are doing with the CiberTIcs group of the Autonomous University of Colombia; which takes into account the Risk Management, I bring to the question asked about the main risks faced by SMBs in Bogota 01/17/2015 14:55 GMT-06: 00 Alberto Soto <asoto(a)ibero-americano.org <mailto:asoto@ibero-americano.org> >: I estimate, please ask them if they have any suggestions on this subject, sent directly to the indicated mail. Time is short. Thanks and best regards Alberto Soto ----- Original Message ----- From: alac-bounces(a)atlarge-lists.icann.org <mailto:alac-bounces@atlarge-lists.icann.org> [Mailto: alac-bounces(a)atlarge-lists.icann.org <mailto:alac-bounces@atlarge-lists.icann.org> ] On behalf of Alan Greenberg Posted on: Saturday, January 17, 2015 1:03 pm To: ALAC Subject: Re: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks If anyone has any thoughts on This, por favor forward and I will collate them and send them in. Alan 01/17/2015 At 10:10 a.m., David Olive wrote: > Below is a note from the ICANN Board Risk Committee Co-Chairs. > > --------------------------------------------- > > Dear SO / AC / SG: > > The Board Risk Committee (BRC) is tasked to Provide oversight and > Guidance into enterprise risk identification and remediation for ICANN. > ICANN has developed a risk management framework and metodología That Is > Used to Identify, mitigate and monitor Risks. > > The purpose of esta email is to reach out to you, the SO / AC / SG > Leadership, to ask your group to identify identity factotum believes it what are the top > Five enterprise-wide Risks to ICANN. This feedback process Allows us to > Calibrate and evaluate- internally With Those Identified Risks > Identified by the community. > > We envision a response as an enumerated list of the top five enterprise > Risks That your SO or AC group factotum believes ought to be ICANN's top > Priorities. > > We ask to Provide a written response via email by 5 February 2015. We > Anticipate discussion on in Original Identified Risks in the SO / AC > Constituency meetings With The Board During ICANN 52 in Singapore. > Please send all written responses Directly to > <mailto:Enterprise-Risk@ICANN.Org <mailto:Enterprise-Risk@ICANN.Org> > Enterprise-Risk(a)ICANN.Org <mailto:Enterprise-Risk@ICANN.Org> . > > We Understand that you 'the May not have any time to Develop a Formal > Response from your SO or AC group. In That case, we would appreciate > Reviews us with you providing your own views or staff Those of a small > Sub-set of your SO or AC group, but please let us know if you Have Done > So. We will iterate the process to improve increase it and comments on possible > Improvements are most welcome. > > Again, thank you in advance and we look forward to your input. > > Regards, > Mike Silber & Ram Mohan > ICANN Board Risk Committee Co-Chairs > > > > David A. Olive > Vice President, Policy Development Support General Manager, ICANN > Regional Headquarters -istanbul Hakki Yeten Cad.Selenium Plaza No: 10 / C > K: 10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned > Names and Numbers (ICANN) > > Direct Line: +90.212.999.6212 <tel:%2B90.212.999.6212> > Mobile: + 1 202.341.3611 <tel:%2B%201.%20202.341.3611> > Mobile: +90.533.341.6550 <tel:%2B90.533.341.6550> > Email: <mailto:david.olive@icann.org <mailto:david.olive@icann.org> > David.olive(a)icann.org <mailto:david.olive@icann.org> > Www.icann.org <http://www.icann.org> > _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA C) --- Avast antivirus software scanned this email for viruses. http://www.avast.com _______________________________________________ lac-discuss-en mailing list lac-discuss-es(a)atlarge-lists.icann.org <mailto:lac-discuss-es@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es http://www.lacralo.org - Best Regard, Alfredo López Hernández The auguries of peace, we will receive in abundance in these last days of the year, encourage us to devise new ways to build in 2015 a country in peace and social justice. --- Avast antivirus software scanned this email for viruses. http://www.avast.com _______________________________________________ lac-discuss-en mailing list lac-discuss-es(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es http://www.lacralo.org [[--Original text (es) http://mm.icann.org/transbot_archive/9c05f26ae0.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by alfredolopezh＠gmail.com Jan. 19, 2015

Jan. 19, 2015

[[--Translated text (es -> en)--]] Subject: Re: RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks From: alfredolopezh(a)gmail.com Dear Alberto, according to my experience and based on a research we are doing with the group CiberTIcs Autonomous University of Colombia; which takes into account Management Risks, I want to contribute to the issue raised about the major risks faced by SMBs in Bogota 01/17/2015 14:55 GMT-06: 00 Alberto Soto <asoto(a)ibero-americano.org> : > Estimados, les pido por favor que si tienen alguna sugerencia sobre este > tema, la envÃen directamente al mail indicado. Queda poco tiempo. > Gracias y saludos cordiales > > Alberto Soto > > -----Mensaje original----- > De: alac-bounces(a)atlarge-lists.icann.org > [mailto:alac-bounces@atlarge-lists.icann.org] En nombre de Alan Greenberg > Enviado el: sÃ¡bado, 17 de enero de 2015 01:03 p.m. > Para: ALAC > Asunto: Re: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN > Enterprise Risks > > If anyone has any thoughts on this, please forward and I will collate them > and send them in. > > Alan > > At 17/01/2015 10:10 AM, David Olive wrote: > > >Below is a note from the ICANN Board Risk Committee Co-Chairs. > > > >--------------------------------------------- > > > >Dear SO/AC/SG: > > > >The Board Risk Committee (BRC) is tasked to provide oversight and > >guidance into enterprise risk identification and remediation for ICANN. > >ICANN has developed a risk management framework and methodology that is > >used to identify, mitigate and monitor risks. > > > >The purpose of this email is to reach out to you, the SO/AC/SG > >Leadership, to ask your group to identify what it believes are the top > >five enterprise-wide risks to ICANN. This feedback process allows us to > >calibrate and evaluate risks identified internally with those > >identified by the community. > > > >We envision a response as an enumerated list of the top five enterprise > >risks that your SO or AC group believes ought to be ICANNâs top > >priorities. > > > >We ask to provide a written response via email by 5 February 2015. We > >anticipate discussion on these identified risks in the SO/AC > >Constituency meetings with the Board during ICANN 52 in Singapore. > >Please send all written responses directly to > ><mailto:Enterprise-Risk@ICANN.Org>Enterprise-Risk(a)ICANN.Org. > > > >We understand that you may not have the time to develop a formal > >response from your SO or AC group. In that case, we would appreciate > >you providing us with your own personal views or those of a small > >sub-set of your SO or AC group, but please let us know if you have done > >so. We will iterate the process to improve it and comments on possible > >improvements are most welcome. > > > >Again, thank you in advance and we look forward to your input. > > > >Regards, > >Mike Silber & Ram Mohan > >ICANN Board Risk Committee Co-Chairs > > > > > > > >David A. Olive > >Vice President, Policy Development Support General Manager, ICANN > >Regional Headquarters âIstanbul Hakki Yeten Cad. Selenium Plaza No:10/C > >K:10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned > >Names and Numbers (ICANN) > > > >Direct Line: +90.212.999.6212 > >Mobile: + 1. 202.341.3611 > >Mobile: +90.533.341.6550 > >Email: <mailto:david.olive@icann.org>david.olive(a)icann.org > >www.icann.org > > > _______________________________________________ > ALAC mailing list > ALAC(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/alac > > At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: > > https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA > C) > > > --- > El software de antivirus Avast ha analizado este correo electrÃ³nico en > busca de virus. > http://www.avast.com > > _______________________________________________ > lac-discuss-es mailing list > lac-discuss-es(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > http://www.lacralo.org > * Best Regards, Alfredo López HernándezQue omens of peace, receive in abundance in these last days of the year, we incentivize devise new ways to build in 2015 a country in peace and social justice. * [[--Original text (es) http://mm.icann.org/transbot_archive/6f63814915.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by asoto＠ibero-americano.org Jan. 18, 2015

Jan. 18, 2015

[[--Translated text (es -> en)--]] Subject: Re: RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks From: asoto(a)ibero-americano.org Thanks for the Ftima aclaracin, interpretmal I transcript in reunin, my apologies: Fatima: Also as Carlton says, I repeat to be clarified, we must analyze if having or not this procedure. Now I surgiesto to see if it is really necessary to have it or not or if you have to have a regulated procedure for the case that at some when we need it. Thanks and regards Alberto Soto From: Fatima Cambronero [mailto: fatimacambronero(a)gmail.com] Posted on: Sunday, January 18, 2015 7:43 pm To: Alberto Soto CC: Vanda Scartezini; Alejandro Pisanty; LACRALO Espaol Subject: Re: [lac-discuss-en] FW: [ALAC] Request for Board Risk Committee Feedback on Top 5 ICANN Enterprise Risks Alberto, A aclaracin: NO said that perhaps now would not have submitted (in this draft proposal on which we are working). I said, considering that in the Webinar where we discussed the topic some members of LACRALO protested saying that it was not necessary have a procedure for LACRALO issues statements, we should analyze at this point if it was the will of all LACRALO or may not have that procedure. It was a question that opened to all. Also manifestque in my opinion, was preferable to have a regulated and accepted procedure for LACRALO issues statements, although perhaps then never we use; is good to have in case at some when we need it. Again I clarify what manifesten said Webinar: I llevpor written in this proposal what venamos doing in practice (without having a regulated process) especially during the earlier periods in LACRALO. They asked me to write it, I did, and put at the disposal of all LACRALO ququeran decide to do, whether to accept it. Nothing more. Now that ARE draft hands of all to modify, correct, improve or not I accept. I hope these explanations serve to avoid creating confusion by assigning words or phrases that were said. Best regards, Fatima Cambronero On January 18, 2015, 19:30, Alberto Soto <asoto(a)ibero-americano.org <mailto:asoto@ibero-americano.org> > Wrote: Dear Vanda, is what we have proposed in the webinar da January 5, with the proposal submitted Fatima Cambronero bean. But some deberamos do not think dalcaraciones, but only send Feedback Received.Ftima manifestsus doubts about its proposicin saying that perhaps now would not have presented. I think that s, which tendramos to send to whoever needed the opinin LACRALO LACRALO are opinions requested or generated within LACRALO. And tendramos to have a simple, try to bring clarity and achieve greater participation for that emission of opinion. Best Regards Alberto Soto ----- Original Message ----- From: Vanda Scartezini [mailto: vanda(a)uol.com.br <mailto:vanda@uol.com.br> ] Posted on: Sunday, January 18, 2015 2:45 pm To: Alberto Soto; Alejandro Pisanty CC: LACRALO Espaol Subject: Re: [lac-discuss-en] FW: [ALAC] Request for Board Risk Committee Feedback on Top 5 ICANN Enterprise Risks Alberto, I take APRA raise the matter of positions. I personally think is a healthy exercise seek positions and send them to ALAC, regardless of having each its position and present perante ICANN. Hugs Vanda Scartezini Polo Consultores Associados Av.Paulista 1159, 1004 cj 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. On 1/18/15, 1:38, "Alejandro Pisanty" <apisanty(a)gmail.com <mailto:apisanty@gmail.com> > Wrote: > Alberto, > > Thank you for taking this initiative, productive and concrete. > > I think the issue we can better develop risk is > Change > In the model of governance that sealas about rule changes > Decision making GAC; pass from consensus to votaciny is > "Infect" the Board. > > As isolated and punctual element is important, but it is much more if > Associated with a change in culture to produce a departure from the consensus ms > General. > > As ordered other / as representatives of organizations in the LACRALO > Sealado risks that we have so far?How to compare them with those of > Other orders (financial, computer safety, etc.) has pointed > Alberto? > > Alejandro Pisanty > > 01.17.2015 22:35 GMT-06: 00 Alberto Soto <asoto(a)ibero-americano.org <mailto:asoto@ibero-americano.org> >: > >> Alejandro and everyone. It is always beneficial to carry these discussion >> Issues. >> I do not ssi may invoke risk sistmico very particular topics >> Financial, although I admit that maybe We could get to determine >> A >> Risk to produce a cascading effect within the organization. >> >> But we can propose risks. >> >> >> >> So we can understand and quizsrpidamente I propose something, quote >> Partially chrter Risk Committee of Board as outside Defined >> >> 2009: >> >> >> >> A: supervision of risk management of ICANN as an organization, >> Including the following activities: >> >> >> >> 1.Review and advise on ICANN policies, plans and programs >> Related to risk management; >> >> 2. Monitoring the effectiveness of programs for management of >> Risks, including operational risk control gestiny; >> >> 3. The supervision of non-financial risk exposure >> Significant for ICANN and the steps taken to monitor and >> Control such exposure; >> >> 4. Keep informed about ICANN conditions and obtencin >> Familiarity with ICANN processes in order to identify >> Possible futures and advise on plans to address risks >> These risks, according applicable; and >> >> 5. revision of other areas of appropriate risk concentration. >> >> >> >> B: supervision of operational activities including the revision of the >> Informaciny monitoring the effectiveness of the management of the >> Operational activities such as: >> >> >> >> 1.The effectiveness of the technology used by ICANN; >> >> 2. FITNESS ICANN policies of continuity >> Business; and >> >> 3. Facing the changes in the business environment that can be ICANN >> important operations. >> >> >> >> Chrter addition to this, we have to consider the temtica of >> Risks has been divided into: >> >> - Credits >> >> - Legal >> >> - Marketing / Prices >> >> - REPUTATION >> >> This Could we maybe focus on A.3 and B. on three points. >> >> And will suggest such risks: >> >> >> >> - System Safety ICANN: The hack recently >> Time systems CZDS Whois wiki. Qutecnologa estn >> Using? Hirimucho the reputation of ICANN. >> >> - Change in the Board Voting system to assimilate to >> The GAC. Has relationship with B.2. but their results are in >> Against >> System of multiple stakeholders. If the foundation is that the >> GAC >> Is rene fewer times, and until today was more effective system >> Board of >> ICANN, the GAC ms meets once per year and is assimilated to ICANN. >> >> - When ICG creel took into account only certain >> Model components multiple stakeholders. As to >> We are concerned, was not expected to ALAC sent a report >> Participatory. The individual user which represent non est >> Within >> Business Continuity ICANN, IANA before the transition? >> >> >> >> I hope you participation, and although we can not make a report Formal >> >> LACRALO, perhaps we can send suggestions individually.I say >> No >> We can formally make them not only by time, but because there >> About >> Understand that there is no need for LACRALO make propositions. Are >> Est >> Discussing a procedure thereon. >> >> Best Regards >> >> >> >> Alberto Soto >> >> >> >> >> >> * From: * Alejandro Pisanty [mailto: apisanty(a)gmail.com <mailto:apisanty@gmail.com> ] >> * Sent: * saturday, January 17, 2015 10:01 pm >> * To: * Alberto Soto >> * CC: * LACRALO Espaol >> * Subject: * Re: [lac-discuss-en] FW: [ALAC] Board Risk Committee Request >> For Feedback on Top 5 ICANN Enterprise Risks >> >> >> >> Alberto, >> >> >> >> Get two weeks. There will be a topic suitable for discussion in LACRALO? >> Although we do not produce a collective expression the discussion may >> Feed >> Individual points of view. >> >> >> >> I provoke its inception proposed as a risk worth inclusion >> "At Large unlimited expansion without accountability or measures >> Effectiveness "... (there are others, but ste may be one that allows >> Calibrate >> Way to enter discuss). >> >> >> >> T cul consider to be the most important risk sistmico >> About >> Which pudiramos argue constructively and effectively? >> >> >> >> Best regards. >> >> >> >> Alejandro Pisanty >> >> >> >> On Sat, Jan 17, 2015 at 2:55 PM, Alberto Soto >> <asoto(a)ibero-americano.org <mailto:asoto@ibero-americano.org> > >> Wrote: >> >> Dear, please ask if you have any suggestions on this >> Subject, enven directly to mail indicated. Time is short. >> Thanks and best regards >> >> Alberto Soto >> >> ----- Original Message ----- >> From: alac-bounces(a)atlarge-lists.icann.org <mailto:alac-bounces@atlarge-lists.icann.org> >> [Mailto: alac-bounces(a)atlarge-lists.icann.org <mailto:alac-bounces@atlarge-lists.icann.org> ] On behalf of Alan Greenberg >> >> Sent: I saturday, January 17, 2015 1:03 pm >> To: ALAC >> Subject: Re: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN >> >> Enterprise Risks >> >> If anyone has any thoughts on This, por favor forward and I will collate >> Them >> And send them in. >> >> Alan >> >> At 01/17/2015 10:10 a.m., David Olive wrote: >> >>> Below is a note from the ICANN Board Risk Committee Co-Chairs. >>> >>> --------------------------------------------- >>> >>> Dear SO / AC / SG: >>> >>> The Board Risk Committee (BRC) is tasked to Provide oversight and >>> Guidance into enterprise risk identification and remediation for ICANN. >>> ICANN has developed a risk management framework and metodología That Is >>> Used to Identify, mitigate and monitor Risks. >>> >>> The purpose of esta email is to reach out to you, the SO / AC / SG >>> Leadership, to ask your group to identify identity factotum believes it what are the top >>> Five enterprise-wide Risks to ICANN. This feedback process Allows us to >>> Calibrate and evaluate- internally With Those Identified Risks >>> Identified by the community. >>> >>> We envision a response as an enumerated list of the top five enterprise >>> Risks That your SO or AC group factotum believes ought to be ICANNs top >>> Priorities. >>> >>> We ask to Provide a written response via email by 5 February 2015. We >>> In Original anticipate discussion on Risks Identified in the SO / AC >>> Constituency meetings With The Board During ICANN 52 in Singapore. >>> Please send all written responses Directly to >>> <mailto:Enterprise-Risk@ICANN.Org <mailto:Enterprise-Risk@ICANN.Org> > Enterprise-Risk(a)ICANN.Org <mailto:Enterprise-Risk@ICANN.Org> . >>> >>> We Understand that you 'the May not have any time to Develop a Formal >>> Response from your SO or AC group. In That case, we would appreciate >>> Reviews us with you providing your own views or staff Those of a small >>> Sub-set of your SO or AC group, but please let us know if you Have Done >>> So. We will iterate the process to improve increase it and comments on possible >>> Improvements are most welcome. >>> >>> Again, thank you in advance and we look forward to your input. >>> >>> Regards, >>> Mike Silber & Ram Mohan >>> ICANN Board Risk Committee Co-Chairs >>> >>> >>> >>> David A. Olive >>> Vice President, Policy Development Support General Manager, ICANN >>> Regional Headquarters Istanbul Hakki Yeten Selenium Square Cad. No: 10 / C >>> K: 10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned >>> Names and Numbers (ICANN) >>> >>> Direct Line: +90.212.999.6212 >>> Mobile: + 1.202.341.3611 >>> Mobile: +90.533.341.6550 >>> Email: <mailto:david.olive@icann.org <mailto:david.olive@icann.org> > David.olive(a)icann.org <mailto:david.olive@icann.org> >>> Www.icann.org <http://www.icann.org> >>> >> _______________________________________________ >> ALAC mailing list >> ALAC(a)atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> >> https://atlarge-lists.icann.org/mailman/listinfo/alac >> >> At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: >> >> >> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+( >> ALA >> C) >> >> >> --- >> Avast antivirus software scanned this e-mail in >> For viruses. >> Http://www.avast.com >> >> _______________________________________________ >> Lac-discuss-en mailing list >> Lac-discuss-es(a)atlarge-lists.icann.org <mailto:lac-discuss-es@atlarge-lists.icann.org> >> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es >> >> Http://www.lacralo.org >> >> >> >> >> >> - >> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - >> Dr. Alejandro Pisanty >> Faculty of Chemistry UNAM >> Av. Universidad 3000, 04510 Mexico DF Mexico >> + 52-1-5541444475 FROM ABROAD >> FROM MEXICO SMS +525541444475 +525541444475 >> Blog: http://pisanty.blogspot.com >> LinkedIn: http://www.linkedin.com/in/pisanty >> Join the LinkedIn group UNAM, >> Http://www.linkedin.com/e/gis/22285/4A106C0C8614 >> Twitter: http://twitter.com/apisanty >> ---- >> Join ISOC Mexico, http://www.isoc.org >>. . . . . . . . . . . . . . . . >> >> ------------------------------ >> >> <http://www.avast.com/> >> >> Avast antivirus software scanned this e-mail in >> For viruses. >> Www.avast.com <http://www.avast.com> >> >> > > > - > - - - - - - - - - - - - - - - - - - - - - - - - - - - > 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 >. . . . . . . . . . . . . . . . >_______________________________________________ >lac-discuss-es mailing list >lac-discuss-es(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > Http://www.lacralo.org --- Avast antivirus software scanned this e-mail in search virus. http://www.avast.com _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/44312b69c6.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by fatimacambronero＠gmail.com Jan. 18, 2015

Jan. 18, 2015

[[--Translated text (es -> en)--]] Subject: Re: RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks From: fatimacambronero(a)gmail.com Alberto, A aclaracin: NO I said maybe now he had not submitted (a This draft proposal on which we are working). I said, considering that in the Webinar where we discussed the topic some members of LACRALO protested saying that it was not necessary have a procedure for LACRALO issues statements, we should analyze at this point if it was the will of all LACRALO or may not have that procedure. It was a question that opened to all. Also manifestque in my opinion, was preferable to have a regulated and accepted procedure for LACRALO issues statements, although perhaps then never we use; is good to have in case at some when we need it. Again I clarify what manifesten said Webinar: I llevpor written in this proposal what venamos doing in practice (without having a regulated process) especially during the earlier periods in LACRALO. They asked me to write it, I did, and put at the disposal of all LACRALO to decide ququeran do, whether to accept it. Nothing more. Now this comp ARE hands of all to modify, correct, improve it or not accept it. I hope these explanations serve to avoid creating confusion by assigning words or phrases that were said. Best regards, Fatima Cambronero On January 18, 2015, 19:30, Alberto Soto <asoto(a)ibero-americano.org> i wrote: > Estimada Vanda, es lo que hemos propuesto en el webinar del día 5 de enero, > con la propuesta que Fatima Cambronero había presentado. Pero hay quienes > piensan que no deberíamos hacer dalcaraciones, sino solo enviar las > opiniones recibidas. Fátima manifestó sus dudas respecto de su proposición > diciendo que quizás ahora no lo hubiera presentado. > Yo opino que sí, que tendríamos que enviar a quien sea necesario la opinión > de LACRALO, sean opiniones solicitadas a LACRALO o generadas dentro de > LACRALO. Y tendríamos que tener un procedimiento sencillo, que trate de > poner claridad y lograr mayor participación para esa emisión de opinión. > Saludos cordiales > > Alberto Soto > > -----Mensaje original----- > De: Vanda Scartezini [mailto:vanda@uol.com.br] > Enviado el: domingo, 18 de enero de 2015 02:45 p.m. > Para: Alberto Soto; Alejandro Pisanty > CC: LACRALO Español > Asunto: Re: [lac-discuss-es] RV: [ALAC] Board Risk Committee Request for > Feedback on Top 5 ICANN Enterprise Risks > > Alberto, aprovecho apra levantar la cuestión de posiciones. Yo > personalmente > creo que es un ejercicio saludable buscar posiciones y enviarlas a ALAC, > independientemente de tener cada cual su position y presentarlas perante > ICANN. > Abrazos > Vanda Scartezini > Polo Consultores Associados > Av. Paulista 1159, cj 1004 > 01311-200- Sao Paulo, SP, Brazil > Land Line: +55 11 3266.6253 > Mobile: + 55 11 98181.1464 > Sorry for any typos. > > > > > > > On 1/18/15, 1:38, "Alejandro Pisanty" <apisanty(a)gmail.com> wrote: > > >Alberto, > > > >gracias por tomar esta iniciativa, productiva y concreta. > > > >Pienso que el tema que mejor podemos desarrollar es el del riesgo de > >cambio > >en el modelo de gobernanza que señalas alrededor del cambio en las reglas > >de toma de decisiones del GAC; pasaría del consenso a la votación y se > >"contagiaría" al Board. > > > >Como elemento aislado y puntual es importante, pero lo es mucho más si se > >asocia a un cambio de cultura que produzca un alejamiento del consenso más > >general. > > > >¿Como ordenarían otros/as representantes de organizaciones en LACRALO los > >riesgos que hemos señalado hasta ahora? ¿Cómo los compararían con los de > >otros órdenes (financiero, seguridad informática, etc.) que ha señalado > >Alberto? > > > >Alejandro Pisanty > > > >2015-01-17 22:35 GMT-06:00 Alberto Soto <asoto(a)ibero-americano.org>: > > > >> Alejandro y todos. Siempre es beneficioso llevar a discusión estos > >>temas. > >> Yo no sé si podría invocar riesgo sistémico, muy particular de los temas > >> financieros, aunque reconozco que quizás podríamos llegar a determinar > >>un > >> riesgo que produzca un efecto cascada dentro de la organización. > >> > >> Pero podemos proponer riesgos. > >> > >> > >> > >> Para que podamos entender y quizás rápidamente proponer algo, cito > >> parcialmente el chárter del Board Risk Committee tal como fuera > >>definido en > >> el 2009: > >> > >> > >> > >> ³A: Supervisión de la gestión de riesgo de la ICANN como organización, > >> incluyendo las siguientes actividades: > >> > >> > >> > >> 1. Revisar y asesorar sobre ICANN políticas, planes y programas > >> relacionados con la gestión de riesgos; > >> > >> 2. Seguimiento de la eficacia de los programas de gestión de > >> riesgos, incluida la gestión y control del riesgo operacional; > >> > >> 3. La supervisión de la exposición al riesgo no financiero > >> significativo para la ICANN y las medidas adoptadas para supervisar y > >> controlar dicha exposición; > >> > >> 4. Mantenerse informado sobre la ICANN condiciones y la obtención > >> de la familiaridad con la ICANN procesos con el fin de identificar los > >> posibles riesgos futuros y asesorar sobre los planes para hacer frente a > >> estos riesgos, según proceda; y > >> > >> 5. Revisión de otras áreas de concentración del riesgo adecuada. > >> > >> > >> > >> B: Supervisión de actividades operacionales, como la revisión de la > >> información y el seguimiento de la eficacia de la gestión de las > >> actividades operacionales tales como: > >> > >> > >> > >> 1. La eficacia de la tecnología utilizada por ICANN ; > >> > >> 2. La adecuación de la ICANN políticas de continuidad de > >>negocios; y > >> > >> 3. Enfrentar los cambios en el entorno empresarial que pueda ser > >> importante para ICANN operaciones.² > >> > >> > >> > >> Además de este chárter, tenemos que tener en cuenta que la temática de > >> riesgos ha sido dividida en: > >> > >> - Créditos > >> > >> - Legal > >> > >> - Marketing/precios > >> > >> - Reputación > >> > >> Con esto quizás podríamos enfocarnos en A.3 y en B. en sus tres puntos. > >> > >> Y sugeriría como riesgos: > >> > >> > >> > >> - Seguridad en los sistemas de ICANN: El hackeo de hace poco > >> tiempo en los sistemas de Whois wiki CZDS. Qué tecnología están > >> utilizando? Hirió mucho la reputación de ICANN. > >> > >> - Cambio en el sistema de votación del Board para asimilarlo a > >> los del GAC. Tiene relación con el B.2. pero sus resultados van en > >>contra > >> del sistema de múltiples partes interesadas. Si el fundamento es que el > >>GAC > >> se reúne menos veces, ya hasta hoy fue más efectivo el sistema del > >>Board de > >> ICANN, que el GAC se reuna una vez más al año y se asimile a ICANN. > >> > >> - Cuando se creó el ICG se tuvo en cuenta solo a determinados > >> componentes del modelo de múltiples partes interesadas. En lo que a > >> nosotros respecta, no estaba previsto que ALAC enviara un informe > >> participativo. El usuario individual al cual representamos no está > >>dentro > >> de la continuidad de negocios de ICANN, ante la transición IANA? > >> > >> > >> > >> Espero que haya participación, y aunque no podamos hacer un informe > >>formal > >> de LACRALO, quizás podamos enviar sugerencias individualmente. Digo que > >>no > >> podamos hacerlos formalmente no solo por el tiempo, sino porque hay > >>quienes > >> entienden que no hay necesidad de que LACRALO haga proposiciones. Se > >>está > >> discutiendo un procedimiento al respecto. > >> > >> Saludos cordiales > >> > >> > >> > >> Alberto Soto > >> > >> > >> > >> > >> > >> *De:* Alejandro Pisanty [mailto:apisanty@gmail.com] > >> *Enviado el:* sábado, 17 de enero de 2015 10:01 p.m. > >> *Para:* Alberto Soto > >> *CC:* LACRALO Español > >> *Asunto:* Re: [lac-discuss-es] RV: [ALAC] Board Risk Committee Request > >> for Feedback on Top 5 ICANN Enterprise Risks > >> > >> > >> > >> Alberto, > >> > >> > >> > >> quedan dos semanas. ¿No sería un tema apto para discusión en LACRALO? > >> Aunque no produzcamos una expresión colectiva la discusión podría > >>alimentar > >> los puntos de vista individuales. > >> > >> > >> > >> Yo provocaría su inicio proponiendo como un riesgo digno de inclusión > >> "expansión ilimitada de At Large sin rendición de cuentas ni medidas de > >> efectividad"... (hay otros, pero éste puede ser uno que permita > >>calibrar la > >> forma de entrar a discutirlos). > >> > >> > >> > >> ¿Tú cuál consideras que sea el riesgo sistémico de mayor importancia > >>sobre > >> el cual pudiéramos discutir de manera constructiva y eficaz? > >> > >> > >> > >> Saludos cordiales. > >> > >> > >> > >> Alejandro Pisanty > >> > >> > >> > >> On Sat, Jan 17, 2015 at 2:55 PM, Alberto Soto > >><asoto(a)ibero-americano.org> > >> wrote: > >> > >> Estimados, les pido por favor que si tienen alguna sugerencia sobre este > >> tema, la envíen directamente al mail indicado. Queda poco tiempo. > >> Gracias y saludos cordiales > >> > >> Alberto Soto > >> > >> -----Mensaje original----- > >> De: alac-bounces(a)atlarge-lists.icann.org > >> [mailto:alac-bounces@atlarge-lists.icann.org] En nombre de Alan > >>Greenberg > >> Enviado el: sábado, 17 de enero de 2015 01:03 p.m. > >> Para: ALAC > >> Asunto: Re: [ALAC] Board Risk Committee Request for Feedback on Top 5 > >>ICANN > >> Enterprise Risks > >> > >> If anyone has any thoughts on this, please forward and I will collate > >>them > >> and send them in. > >> > >> Alan > >> > >> At 17/01/2015 10:10 AM, David Olive wrote: > >> > >> >Below is a note from the ICANN Board Risk Committee Co-Chairs. > >> > > >> >--------------------------------------------- > >> > > >> >Dear SO/AC/SG: > >> > > >> >The Board Risk Committee (BRC) is tasked to provide oversight and > >> >guidance into enterprise risk identification and remediation for ICANN. > >> >ICANN has developed a risk management framework and methodology that is > >> >used to identify, mitigate and monitor risks. > >> > > >> >The purpose of this email is to reach out to you, the SO/AC/SG > >> >Leadership, to ask your group to identify what it believes are the top > >> >five enterprise-wide risks to ICANN. This feedback process allows us to > >> >calibrate and evaluate risks identified internally with those > >> >identified by the community. > >> > > >> >We envision a response as an enumerated list of the top five enterprise > >> >risks that your SO or AC group believes ought to be ICANN¹s top > >> >priorities. > >> > > >> >We ask to provide a written response via email by 5 February 2015. We > >> >anticipate discussion on these identified risks in the SO/AC > >> >Constituency meetings with the Board during ICANN 52 in Singapore. > >> >Please send all written responses directly to > >> ><mailto:Enterprise-Risk@ICANN.Org>Enterprise-Risk(a)ICANN.Org. > >> > > >> >We understand that you may not have the time to develop a formal > >> >response from your SO or AC group. In that case, we would appreciate > >> >you providing us with your own personal views or those of a small > >> >sub-set of your SO or AC group, but please let us know if you have done > >> >so. We will iterate the process to improve it and comments on possible > >> >improvements are most welcome. > >> > > >> >Again, thank you in advance and we look forward to your input. > >> > > >> >Regards, > >> >Mike Silber & Ram Mohan > >> >ICANN Board Risk Committee Co-Chairs > >> > > >> > > >> > > >> >David A. Olive > >> >Vice President, Policy Development Support General Manager, ICANN > >> >Regional Headquarters Istanbul Hakki Yeten Cad. Selenium Plaza No:10/C > >> >K:10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned > >> >Names and Numbers (ICANN) > >> > > >> >Direct Line: +90.212.999.6212 > >> >Mobile: + 1. 202.341.3611 > >> >Mobile: +90.533.341.6550 > >> >Email: <mailto:david.olive@icann.org>david.olive(a)icann.org > >> >www.icann.org > >> > > >> _______________________________________________ > >> ALAC mailing list > >> ALAC(a)atlarge-lists.icann.org > >> https://atlarge-lists.icann.org/mailman/listinfo/alac > >> > >> At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: > >> > >> > >> > https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+( > >>ALA > >> C) > >> > >> > >> --- > >> El software de antivirus Avast ha analizado este correo electrónico en > >> busca de virus. > >> http://www.avast.com > >> > >> _______________________________________________ > >> lac-discuss-es mailing list > >> lac-discuss-es(a)atlarge-lists.icann.org > >> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > >> > >> http://www.lacralo.org > >> > >> > >> > >> > >> > >> -- > >> > >> - - - - - - - - - - - - - - - - - - - - - - - - - - - > >> 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 > >> . . . . . . . . . . . . . . . . > >> > >> > >> ------------------------------ > >> <http://www.avast.com/> > >> > >> El software de antivirus Avast ha analizado este correo electrónico en > >> busca de virus. > >> www.avast.com > >> > >> > > > > > >-- > >- - - - - - - - - - - - - - - - - - - - - - - - - - - > > 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 > >. . . . . . . . . . . . . . . . > >_______________________________________________ > >lac-discuss-es mailing list > >lac-discuss-es(a)atlarge-lists.icann.org > >https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > > >http://www.lacralo.org > > > > --- > El software de antivirus Avast ha analizado este correo electrónico en > busca de virus. > http://www.avast.com > > _______________________________________________ > lac-discuss-es mailing list > lac-discuss-es(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > http://www.lacralo.org > * Fatima Cambronero * Attorney-Argentina Phone: +54 9351 5282 668 Twitter:facambronero Skype: fatima.cambronero _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/304c51d8bc.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by asoto＠ibero-americano.org Jan. 18, 2015

Jan. 18, 2015

[[--Translated text (es -> en)--]] Subject: Re: RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks From: asoto(a)ibero-americano.org Dear Vanda, is what we have proposed in the webinar da January 5, with the proposal submitted Fatima Cambronero bean. But some deberamos do not think dalcaraciones, but only send Feedback Received. Ftima manifestsus doubts about its proposicin saying that perhaps now would not have presented. I think that s, which tendramos to send to whoever needed the opinin LACRALO LACRALO are opinions requested or generated within LACRALO. And tendramos to have a simple, try to bring clarity and achieve greater participation for that emission of opinion. Best Regards Alberto Soto ----- Original Message ----- From: Vanda Scartezini [mailto: vanda(a)uol.com.br] Posted on: Sunday, January 18, 2015 2:45 pm To: Alberto Soto; Alejandro Pisanty CC: LACRALO Espaol Subject: Re: [lac-discuss-en] FW: [ALAC] Request for Board Risk Committee Feedback on Top 5 ICANN Enterprise Risks Alberto, I take APRA raise the matter of positions. I personally think is a healthy exercise seek positions and send them to ALAC, regardless of having each its position and present perante ICANN. Hugs Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, 1004 cj 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. On 1/18/15, 1:38, "Alejandro Pisanty" <apisanty(a)gmail.com> wrote: > Alberto, > > Thank you for taking this initiative, productive and concrete. > > I think the issue we can better develop risk is > Change > In the model of governance that sealas about rule changes > Decision making GAC; pass from consensus to votaciny is > "Infect" the Board. > > As isolated and punctual element is important, but it is much more if > Associated with a change in culture to produce a departure from the consensus ms > General. > > As ordered other / as representatives of organizations in the LACRALO > Sealado risks that we have so far? How to compare them with those of > Other orders (financial, computer safety, etc.) has pointed > Alberto? > > Alejandro Pisanty > > 01.17.2015 22:35 GMT-06: 00 Alberto Soto <asoto(a)ibero-americano.org> : > >> Alejandro and everyone. It is always beneficial to carry these discussion >> Issues. >> I do not ssi may invoke risk sistmico very particular topics >> Financial, although I admit that maybe We could get to determine >> A >> Risk to produce a cascading effect within the organization. >> >> But we can propose risks. >> >> >> >> So we can understand and quizsrpidamente I propose something, quote >> Partially chrter Risk Committee of Board as outside Defined >> >> 2009: >> >> >> >> A: supervision of risk management of ICANN as an organization, >> Including the following activities: >> >> >> >> 1. Review and advise on ICANN policies, plans and programs >> Related to risk management; >> >> 2. Monitoring the effectiveness of programs for management of >> Risks, including operational risk control gestiny; >> >> 3. The supervision of non-financial risk exposure >> Significant for ICANN and the steps taken to monitor and >> Control such exposure; >> >> 4.Stay informed about ICANN conditions and obtencin >> Familiarity with ICANN processes in order to identify >> Possible futures and advise on plans to address risks >> These risks, according applicable; and >> >> 5. revision of other areas of appropriate risk concentration. >> >> >> >> B: supervision of operational activities including the revision of the >> Informaciny monitoring the effectiveness of the management of the >> Operational activities such as: >> >> >> >> 1. The effectiveness of the technology used by ICANN; >> >> 2. FITNESS ICANN policies of continuity >> Business; and >> >> 3.Addressing changes in the business environment that can be ICANN >> important operations. >> >> >> >> Chrter addition to this, we have to consider the temtica of >> Risks has been divided into: >> >> - Credits >> >> - Legal >> >> - Marketing / Prices >> >> - REPUTATION >> >> This Could we maybe focus on A.3 and B. on three points. >> >> And will suggest such risks: >> >> >> >> - System Safety ICANN: The hack recently >> Time systems CZDS Whois wiki. Qutecnologa estn >> Using? Hirimucho the reputation of ICANN. >> >> - Change in the Board Voting system to assimilate to >> The GAC. Has relationship with B.2. but their results are in >> Against >> System of multiple stakeholders.If the foundation is that the >> GAC >> Is rene fewer times, and until today was more effective system >> Board of >> ICANN, the GAC ms meets once per year and is assimilated to ICANN. >> >> - When ICG creel took into account only certain >> Model components multiple stakeholders. As to >> We are concerned, was not expected to ALAC sent a report >> Participatory. The individual user which represent non est >> Within >> Business Continuity ICANN, IANA before the transition? >> >> >> >> I hope you participation, and although we can not make a report Formal >> >> LACRALO, perhaps we can send suggestions individually. I say >> No >> We can formally make them not only by time, but because there >> About >> Understand that there is no need for LACRALO make propositions. Are >> Est >> Discussing a procedure thereon. >> >> Best Regards >> >> >> >> Alberto Soto >> >> >> >> >> >> * From: * Alejandro Pisanty [mailto: apisanty(a)gmail.com] >> * Sent: * saturday, January 17, 2015 10:01 pm >> * To: * Alberto Soto >> * CC: * LACRALO Espaol >> * Subject: * Re: [lac-discuss-en] FW: [ALAC] Board Risk Committee Request >> For Feedback on Top 5 ICANN Enterprise Risks >> >> >> >> Alberto, >> >> >> >> Get two weeks. There will be a topic suitable for discussion in LACRALO? >> Although we do not produce a collective expression the discussion may >> Feed >> Individual points of view. >> >> >> >> I provoke its inception proposed as a risk worth inclusion >> "At Large unlimited expansion without accountability or measures >> Effectiveness "... (there are others, but ste may be one that allows >> Calibrate >> Way to enter discuss). >> >> >> >> T cul consider to be the most important risk sistmico >> About >> Which pudiramos argue constructively and effectively? >> >> >> >> Best regards. >> >> >> >> Alejandro Pisanty >> >> >> >> On Sat, Jan 17, 2015 at 2:55 PM, Alberto Soto >> <asoto(a)ibero-americano.org> >> Wrote: >> >> Dear, please ask if you have any suggestions on this >> Subject, enven directly to mail indicated. Time is short. >> Thanks and best regards >> >> Alberto Soto >> >> ----- Original Message ----- >> From: alac-bounces(a)atlarge-lists.icann.org >> [Mailto: alac-bounces(a)atlarge-lists.icann.org] On behalf of Alan Greenberg >> >> Sent: I saturday, January 17, 2015 1:03 pm >> To: ALAC >> Subject: Re: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN >> >> Enterprise Risks >> >> If anyone has any thoughts on This, por favor forward and I will collate >> Them >> And send them in. >> >> Alan >> >> At 01/17/2015 10:10 a.m., David Olive wrote: >> >>> Below is a note from the ICANN Board Risk Committee Co-Chairs. >>> >>> --------------------------------------------- >>> >>> Dear SO / AC / SG: >>> >>> The Board Risk Committee (BRC) is tasked to Provide oversight and >>> Guidance into enterprise risk identification and remediation for ICANN. >>> ICANN has developed a risk management framework and metodología That Is >>> Used to Identify, mitigate and monitor Risks. >>> >>> The purpose of esta email is to reach out to you, the SO / AC / SG >>> Leadership, to ask your group to identify identity factotum believes it what are the top >>> Five enterprise-wide Risks to ICANN.This feedback process Allows us to >>> Calibrate and evaluate- internally With Those Identified Risks >>> Identified by the community. >>> >>> We envision a response as an enumerated list of the top five enterprise >>> Risks That your SO or AC group factotum believes ought to be ICANNs top >>> Priorities. >>> >>> We ask to Provide a written response via email by 5 February 2015. We >>> In Original anticipate discussion on Risks Identified in the SO / AC >>> Constituency meetings With The Board During ICANN 52 in Singapore. >>> Please send all written responses Directly to >>> <mailto:Enterprise-Risk@ICANN.Org> Enterprise-Risk(a)ICANN.Org. >>> >>> We Understand that you 'the May not have any time to Develop a Formal >>> Response from your SO or AC group. In That case, we would appreciate >>> Reviews us with you providing your own views or staff Those of a small >>> Sub-set of your SO or AC group, but please let us know if you Have Done >>> So. We will iterate the process to improve increase it and comments on possible >>> Improvements are most welcome. >>> >>> Again, thank you in advance and we look forward to your input. >>> >>> Regards, >>> Mike Silber & Ram Mohan >>> ICANN Board Risk Committee Co-Chairs >>> >>> >>> >>> David A. Olive >>> Vice President, Policy Development Support General Manager, ICANN >>> Regional Headquarters Istanbul Hakki Yeten Selenium Square Cad. No: 10 / C >>> K: 10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned >>> Names and Numbers (ICANN) >>> >>> Direct Line: +90.212.999.6212 >>> Mobile: + 1 202.341.3611 >>> Mobile: +90.533.341.6550 >>> Email: <mailto:david.olive@icann.org> david.olive(a)icann.org >>> Www.icann.org >>> >> _______________________________________________ >> ALAC mailing list >> ALAC(a)atlarge-lists.icann.org >> https://atlarge-lists.icann.org/mailman/listinfo/alac >> >> At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: >> >> >> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+( >> ALA >> C) >> >> >> --- >> Avast antivirus software scanned this e-mail in >> For viruses. >> Http://www.avast.com >> >> _______________________________________________ >> Lac-discuss-en mailing list >> Lac-discuss-es(a)atlarge-lists.icann.org >> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es >> >> Http://www.lacralo.org >> >> >> >> >> >> - >> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - >> Dr. Alejandro Pisanty >> Faculty of Chemistry UNAM >> Av. Universidad 3000, 04510 Mexico DF Mexico >> + 52-1-5541444475 FROM ABROAD >> FROM MEXICO SMS +525541444475 +525541444475 >> Blog: http://pisanty.blogspot.com >> LinkedIn: http://www.linkedin.com/in/pisanty >> Join the LinkedIn group UNAM, >> Http://www.linkedin.com/e/gis/22285/4A106C0C8614 >> Twitter: http://twitter.com/apisanty >> ---- >> Join ISOC Mexico, http://www.isoc.org >>. . . . . . . . . . .. . . . . >> >> ------------------------------ >> >> <http://www.avast.com/> >> >> Avast antivirus software scanned this e-mail in >> For viruses. >> Www.avast.com >> >> > > > - > - - - - - - - - - - - - - - - - - - - - - - - - - - - > 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 >. . . . . . . . . . . . . . . . >_______________________________________________ >lac-discuss-es mailing list >lac-discuss-es(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > >http://www.lacralo.org Avast antivirus software scanned this e-mail for viruses. http://www.avast.com _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/21f86a2f32.html --]]

1 0