January 2015 - lac-discuss-en

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by vanda＠uol.com.br 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: vanda(a)uol.com.br Alberto, I take APRA raise the matter of positions. I I personally think it's a healthy exercise and seek positions send to ALAC, regardless of having each its position and perante presenting 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 [[--Original text (es) http://mm.icann.org/transbot_archive/7d6b57031e.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by vanda＠uol.com.br 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: vanda(a)uol.com.br Already envimis comments and risks that I consider relevant to another email but I concordo with these two points Alex - discussion in LACRALO and regarding the ALS. 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/17/15, 20:00 "Alejandro Pisanty" <apisanty(a)gmail.com> wrote: > Alberto, > > Two weeks left. 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 calibrating > The > Way to enter discuss). > > T cul you consider to be the most important risk sistmico on > 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 >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 [[--Original text (es) http://mm.icann.org/transbot_archive/fba2b9904b.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by vanda＠uol.com.br 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: vanda(a)uol.com.br Ola friends, I hope 2015 estsiendo very happy for everyone! As was already discutindo estn other lists after September, is everything goes well, ICANN will face many challenges and must prepare for this. There are specific risks. - One as Alex says about governance com manutencin she is, without much interference from governments, but to its interests. - If we are to have an external governance IANA, I hope not, then the risks will grow much more. The interaction of the two governesses can be complex. A preventive analyze this situation s necessary. - Another risk is financial - I think that the entry of these million dollars (new gTLDs) can blind executives. This amount s Pontual.I do not think the new domains will have a long event in Soon, you as the resource box are now booked for the challenges of after September when other requirements demand Financial will appear. Precautionary measures should be taken in this sense. - See also a risk regarding the motivation of the community. Must always seek challenges and issues that encourage the participation of the community. Today I see a lot ICANN grow its staff. Which is not the way it will follow, because the road is written to walk and dizia one song, but a balance between the size of the staff and the demands of the community manter your interests idebe be taken into account. These my first thoughts. Hugs to all! 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. 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.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 [[--Original text (es) http://mm.icann.org/transbot_archive/5294ee408f.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 I forgot a point on the risk classification, which is synthetically the following: 1. Credits 2. Legal 3. Marketing / Prices 4. Strategy 5. Reputation Greetings! Alberto From: Alejandro Pisanty [mailto: apisanty(a)gmail.com] Posted on: Sunday, January 18, 2015 3:39 a.m. 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 Alberto, Thanks for taking this initiative, productive and concrete. I think the issue we can better develop risk is the change in the model of governance that point out about the change in the rules of decision making GAC; would increase from consensus to voting and will "rub off" the Board. As isolated and punctual element is important, but much more if it is associated with a change in culture to produce a departure from the more general consensus. How would order other / as representatives of organizations LACRALO the risks we have identified so far? How do would compare with other orders (financial, IT security, etc.) has pointed Alberto? Alejandro Pisanty 01/17/2015 22:35 GMT-06: 00 Alberto Soto <asoto(a)ibero-americano.org> : Alejandro and everyone. Discussion is always beneficial to bring these issues.I do not know if I could rely, very particular systemic risk in financial issues, 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 quickly understand and perhaps propose something, partially quote the charter of the Board Risk Committee as set out in 2009: "A: Monitoring risk management of ICANN as an organization, including the following: 1. Review and advise on ICANN policies, plans and related risk management programs; 2. Monitoring the effectiveness of risk management programs, including the management and control of operational risk; 3. The monitoring of exposure to significant non-financial risk to ICANN and the steps taken to monitor and control such exposures; 4. Keep informed about ICANN conditions and gaining familiarity with ICANN processes in order to identify potential risks and advise on future plans to address these risks, as appropriate; and 5. Review other areas appropriate risk concentration. B: Monitoring operational activities including reviewing the information and monitoring the effectiveness of the management of operational activities such as: 1. The effectiveness of the technology used by ICANN; 2. The adequacy of the policies of ICANN business continuity; and 3. Facing the changes in the business environment that may be important for ICANN operations. " In addition to this charter, we must bear in mind that the issue of risk has been divided into: - Credits - Legal - Marketing / Prices - Reputation With that maybe we could focus on A.3 and B. in three points. And suggest as risks: - System Safety ICANN: The hacking of time recently Whois systems - wiki - CZDS. What technology are you using? It hurt a lot the reputation of ICANN. - Change in Board voting system to assimilate it to the GAC. Relates to the B.2. but the results go against the system of multiple stakeholders. If the foundation is that the GAC meets less often, and until today was more effective system of Board of ICANN, the GAC meets once a year and more assimilated to ICANN. - When the ICG was created only to certain components of the multi-stakeholder model was taken into account.As far as we were concerned, was not expected to ALAC send a participatory report. The individual user to which we represent is not within business continuity ICANN, IANA before the transition? I hope there is participation, and although we can not make a formal report LACRALO, maybe we can send suggestions individually. I say we can not formally make them not only by time, but because there are those who understand that there is no need for LACRALO make propositions. Are discussing a procedure thereon. Best Regards Alberto Soto From: Alejandro Pisanty [mailto: apisanty(a)gmail.com <mailto:apisanty@gmail.com> ] Posted on: Saturday, January 17, 2015 10:01 pm 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 Alberto, two weeks left. Would not it be a topic suitable for LACRALO discussion? Although we do not produce a collective expression discussion could feed the individual views. I cause its inception proposed as a risk worth inclusion "unlimited expansion of At Large without accountability and effectiveness measures" ... (there are others, but this may be one that allows calibrate the way to enter discuss). Do you what you consider to be the most important systemic risk on which we could 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: 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 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 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr.Alejandro Pisanty Faculty of Chemistry UNAM University Av 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/> <http://www.avast.com/> Avast antivirus software scanned this email for viruses. 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 Faculty of Chemistry UNAM University Av 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 . . . . . . . . . . . . . . . . --- 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/b5f44c197f.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by apisanty＠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: apisanty(a)gmail.com Alberto, Thanks for taking this initiative, productive and concrete. I think the issue we can better develop is the exchange risk in the model of governance that point out about rule changes decision making GAC; happen from consensus to vote and "Rub off" the Board. As isolated and punctual element is important, but much more if associated with a change in culture to produce a departure from the consensus more general. How would order other / as representatives of organizations in the LACRALO risks that we have identified so far? How would compare with those of the other orders (financial, IT security, etc.) has pointed Alberto? Alejandro Pisanty 01/17/2015 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 Faculty of Chemistry UNAM University Av 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 . . . . . . . . . . . . . . . . _______________________________________________ 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/0fa0b42325.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 Alejandro and everyone. Discussion is always beneficial to bring these issues. I do not know if I could rely, very particular systemic risk in financial issues, 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 quickly understand and perhaps propose something, partially quote the charter of the Board Risk Committee as set out in 2009: "A: Monitoring risk management of ICANN as an organization, including the following: 1. Review and advise on ICANN policies, plans and related risk management programs; 2. Monitoring the effectiveness of risk management programs, including the management and control of operational risk; 3. The monitoring of exposure to significant non-financial risk to ICANN and the steps taken to monitor and control such exposures; 4. Keep informed about ICANN conditions and gaining familiarity with ICANN processes in order to identify potential risks and advise on future plans to address these risks, as appropriate; and 5. Review other areas appropriate risk concentration. B: Monitoring operational activities including reviewing the information and monitoring the effectiveness of the management of operational activities such as: 1. The effectiveness of the technology used by ICANN; 2. The adequacy of the policies of ICANN business continuity; and 3. Facing the changes in the business environment that may be important for ICANN operations. " In addition to this charter, we must bear in mind that the issue of risk has been divided into: - Credits - Legal - Marketing / Prices - Reputation With that maybe we could focus on A.3 and B. in three points. And suggest as risks: - System Safety ICANN: The hacking of time recently Whois systems - wiki - CZDS. What technology are you using? It hurt a lot the reputation of ICANN. - Change in Board voting system to assimilate it to the GAC. Relates to the B.2. but the results go against the system of multiple stakeholders.If the foundation is that the GAC meets less often, and until today was more effective system of Board of ICANN, the GAC meets once a year and more assimilated to ICANN. - When the ICG was created only to certain components of the multi-stakeholder model was taken into account. As far as we were concerned, was not expected to ALAC send a participatory report. The individual user to which we represent is not within business continuity ICANN, IANA before the transition? I hope there is participation, and although we can not make a formal report LACRALO, maybe we can send suggestions individually. I say we can not formally make them not only by time, but because there are those who understand that there is no need for LACRALO make propositions. Are discussing a procedure thereon. Best Regards Alberto Soto From: Alejandro Pisanty [mailto: apisanty(a)gmail.com] Posted on: Saturday, January 17, 2015 10:01 pm 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 Alberto, two weeks left. Would not it be a topic suitable for LACRALO discussion? Although we do not produce a collective expression discussion could feed the individual views. I cause its inception proposed as a risk worth inclusion "unlimited expansion of At Large without accountability and effectiveness measures" ... (there are others, but this may be one that allows calibrate the way to enter discuss). Do you what you consider to be the most important systemic risk on which we could 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: 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 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 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr.Alejandro Pisanty Faculty of Chemistry UNAM University Av 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 . . . . . . . . . . . . . . . . --- 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/f9f104afa2.html --]]

1 0

Re: [lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by apisanty＠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: apisanty(a)gmail.com Alberto, two weeks left. Would not it be a topic suitable for LACRALO discussion? Although we do not produce a collective expression could feed discussion the individual views. I cause its inception proposed as a risk worth inclusion "At Large unlimited expansion without accountability or measures effectiveness "... (there are others, but this may be one that allows calibrate the way in to discuss). Do you what you consider to be the most important systemic risk on which could discuss constructively and effectively? Best regards. 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 Faculty of Chemistry UNAM University Av 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 . . . . . . . . . . . . . . . . _______________________________________________ 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/ffdfa15f02.html --]]

1 0

FW: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
by asoto＠ibero-americano.org Jan. 17, 2015

Jan. 17, 2015

[[--Translated text (es -> en)--]] Subject: FW: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks From: asoto(a)ibero-americano.org I estimate, please ask them if they 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 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 ICANNs 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> 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 > _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/09eea16d5c.html --]]

1 0

Internet Number IANA Community Stewardship Proposal Submitted to the ICG
by asoto＠ibero-americano.org Jan. 16, 2015

Jan. 16, 2015

[[--Translated text (es -> en)--]] Subject: Internet Number IANA Community Stewardship Proposal Submitted to the ICG From: asoto(a)ibero-americano.org Dear, in ms link below, podrn see the document Community Internet numbers through her RIR IANA Consolidated Stewardship Proposal (CRISP), sends the Co-ordination Group of the Transition Custody of the IANA functions (ICG), on schedule (15 January). I suggest reading. Best Regards Alberto Soto http://goo.gl/j9J06i --- Avast antivirus software scanned this e-mail for viruses. http://www.avast.com _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/1ebba84d09.html --]]

1 0

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

Jan. 15, 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

2 1