[PC-NCSG] Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
David Cake
dave
Fri Feb 6 08:57:28 EET 2015
I?d add as risks:
- lack of confidence in the domain name system as adequately protecting consumer security and privacy leading to widespread adoption of alternative mechanisms.
- over reliance on commercial gTLD profits as driving ICANNs planning and growth, leading to planning that is not focussed on ICANNs core mission.
- alternative, external, policy discussion outside ICANN community due to lack of engagement - for example, ICANNs fate being part of US congressional politics is an example of this form of risk
Cheers
David
On 6 Feb 2015, at 2:00 pm, Rafik Dammak <rafik.dammak at gmail.com> wrote:
> Hi everyone,
>
> thanks for the input, I will try to frame all those comments somehow :)
>
> Rafik
>
> 2015-02-06 11:08 GMT+09:00 William Drake <wjdrake at gmail.com>:
> Well, that would certainly qualify as an ?enterprise-wide? risk :-)
>
> BD
>
>> On Feb 6, 2015, at 3:43 AM, Sam Lanfranco <Lanfran at yorku.ca> wrote:
>>
>> I have not answered the query yet but I would offer (pro bono) the following outstanding risk: "Persistent failure to learn"
>>
>>
>> On 2015-02-04 11:46 AM, Rudi Vansnick wrote:
>>> I?m fully with you Stephanie ?
>>>
>>> Too often we are getting these queries with no good background definition of what will be done with what we supply to them ?
>>> As last NCPH I?m still waiting for any response from my proposals ? how long does that have to take ? forever ? or never ?
>>>
>>>
>>> Rudi Vansnick
>>> Chair Non-for-Profit Operational Concerns Constituency (NPOC)
>>> www.npoc.org
>>>
>>> rudi.vansnick at npoc.org
>>> Tel : +32 (0)9 329 39 16
>>> Mobile : +32 (0)475 28 16 32
>>>
>>>
>>>
>>>> Op 4-feb.-2015, om 17:18 heeft Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> het volgende geschreven:
>>>>
>>>> i keep repeating myself. It is nonsense to ask us all for our top five risks, without giving us the framework they are using to assess risk. Garbage in, garbage out. They should know better.
>>>> Stephanie Perrin
>>>> On 2015-02-04 7:43, Rafik Dammak wrote:
>>>>> Hi everyone,
>>>>>
>>>>> any help on this. after sending the topic to board for the joint meeting, I got the question what are the top 5 entreprise risks pertaining to NCSG.
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>> 2015-01-19 9:06 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>>>>> Hi,
>>>>>
>>>>> we are asked to give input about top 5 ICANN entreprise risks and we should provide this by 5th February (few days before the singapore meeting)
>>>>>
>>>>> Rafik
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: David Olive <david.olive at icann.org>
>>>>> Date: 2015-01-18 0:10 GMT+09:00
>>>>> Subject: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks
>>>>> To: "byron.holland at cira.ca" <byron.holland at cira.ca>, "jonathan.robinson at ipracon.com" <jonathan.robinson at ipracon.com>, "louie at louie.net" <louie at louie.net>, "thomas.schneider at bakom.admin.ch" <thomas.schneider at bakom.admin.ch>, "alan.greenberg at mcgill.ca" <alan.greenberg at mcgill.ca>, "patrik at frobbit.se" <patrik at frobbit.se>, "tsinha at umd.edu" <tsinha at umd.edu>, "liman at netnod.se" <liman at netnod.se>, "Metalitz, Steven" <met at msk.com>, "Elisa.Cooper at markmonitor.com" <Elisa.Cooper at markmonitor.com>, "tonyarholmes at btinternet.com" <tonyarholmes at btinternet.com>, "rafik.dammak at gmail.com" <rafik.dammak at gmail.com>, "william.drake at uzh.ch" <william.drake at uzh.ch>, "rudi.vansnick at isoc.be" <rudi.vansnick at isoc.be>, "Michele at blacknight.com" <Michele at blacknight.com>, "kdrazek at Verisign.com" <kdrazek at verisign.com>
>>>>> Cc: "mike.silber at icann.org" <mike.silber at icann.org>, "rmohan at afilias.info" <rmohan at afilias.info>
>>>>>
>>>>>
>>>>> 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 Enterprise-Risk at 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: david.olive at icann.org
>>>>> www.icann.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> PC-NCSG mailing list
>>>>> PC-NCSG at ipjustice.org
>>>>> http://mailman.ipjustice.org/listinfo/pc-ncsg
>>>>
>>>> _______________________________________________
>>>> PC-NCSG mailing list
>>>> PC-NCSG at ipjustice.org
>>>> http://mailman.ipjustice.org/listinfo/pc-ncsg
>>>
>>>
>>>
>>> _______________________________________________
>>> PC-NCSG mailing list
>>> PC-NCSG at ipjustice.org
>>> http://mailman.ipjustice.org/listinfo/pc-ncsg
>>
>> _______________________________________________
>> PC-NCSG mailing list
>> PC-NCSG at ipjustice.org
>> http://mailman.ipjustice.org/listinfo/pc-ncsg
>
>
> _______________________________________________
> PC-NCSG mailing list
> PC-NCSG at ipjustice.org
> http://mailman.ipjustice.org/listinfo/pc-ncsg
>
>
> _______________________________________________
> PC-NCSG mailing list
> PC-NCSG at ipjustice.org
> http://mailman.ipjustice.org/listinfo/pc-ncsg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ipjustice.org/pipermail/pc-ncsg/attachments/20150206/6a025a54/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.ipjustice.org/pipermail/pc-ncsg/attachments/20150206/6a025a54/attachment-0001.sig>
More information about the NCSG-PC
mailing list