[lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
vanda at uol.com.br
vanda at uol.com.br
Sun Jan 18 17:40:00 UTC 2015
[[--Translated text (es -> en)--]]
Subject: Re: RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
From: vanda at 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 at 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 at 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 at 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 at 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 at atlarge-lists.icann.org
>> [Mailto: alac-bounces at 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 at ICANN.Org> Enterprise-Risk at 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 at icann.org> david.olive at icann.org
>>> Www.icann.org
>>>
>> _______________________________________________
>> ALAC mailing list
>> ALAC at 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 at 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 at 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
--]]
More information about the lac-discuss-en
mailing list