ICANN Email Archives: [bc-gnso]

ICANN ICANN Email List Archives
[bc-gnso]

<<< Chronological Index >>> <<< Thread Index >>>
RE: [bc-gnso] update on CCWG -Accountability, regading Stress Tests

To: "Steve DelBianco" <sdelbianco@xxxxxxxxxxxxx>, bc-gnso@xxxxxxxxx
Subject: RE: [bc-gnso] update on CCWG -Accountability, regading Stress Tests
From: "Jimson Olufuye" <jolufuye@xxxxxxxxxxxxxxxx>
Date: Tue, 03 Feb 2015 06:56:30 -0700
<html><body><span style="font-family:Tahoma; color:#000066; 
font-size:12pt;"><div>Hi Steve,</div>
<div>&nbsp;</div>
<div>Thank you for the splendid work you're doing on our behalf in the CCWG on 
Accountability and for the info provided.</div>
<div>&nbsp;</div>
<div>Can it be assumed that the risks associated with force majeure 
and&nbsp;natural phenomenon like earthquake in a region or multiple regions are 
covered in Category&nbsp;I under "financial crisis specific to general global 
economy" or is it&nbsp;better expressed separately in the same category?</div>
<div>&nbsp;</div>
<div>Also, is it safe to add "uncoordinated" to the expressions in items 1 
(Change authority ...) &amp; 2 (Delegation authority...) of Category II to read 
"significant uncoordinated interference". My reason is that under normal 
circumstances, it is possible to have significant interference in the system 
provided they are authorised and they follow laid down procedures. However, it 
becomes an issue when the mechanism for orderly change has been removed thereby 
giving rise to an uncoordinated scenario.</div>
<div>&nbsp;</div>
<div>Hope the above make sense.</div>
<div>&nbsp;</div>
<div>Cheers,</div>
<div>&nbsp;</div>
<div>JO</div>
<div><BR>&nbsp;</div>
<div><BR></div>
<div><SPAN style="FONT-FAMILY: verdana, 
geneva">--------------------------------------------------------------</SPAN><BR><SPAN
 style="FONT-FAMILY: verdana, geneva">Jimson Olufuye, fncs, ficma, PRINCE2, 
CISA, PhD</SPAN><BR><SPAN style="FONT-FAMILY: verdana, geneva">CEO 
Kontemporary® </SPAN><BR><SPAN style="FONT-FAMILY: verdana, geneva">Chair, 
AfICTA</SPAN><BR><SPAN style="FONT-FAMILY: verdana, geneva">connecting African 
ICT players &amp; </SPAN><BR><SPAN style="FONT-FAMILY: verdana, geneva">... 
fulfilling the promise of the Digital Age for everyone in Africa.</SPAN><BR><A 
style="FONT-FAMILY: verdana, geneva" 
href="http://www.aficta.org/";>www.aficta.org</A><SPAN style="FONT-SIZE: 9pt; 
FONT-FAMILY: Verdana, Arial, Helvetica, sans-serif">&nbsp;</SPAN><BR><SPAN 
style="FONT-FAMILY: verdana, geneva"><a 
href="http://www.kontemporary.net.ng";>www.kontemporary.net.ng</a></SPAN><BR><SPAN
 style="FONT-FAMILY: verdana, geneva">M: +234 802 3183252</SPAN><BR><SPAN 
style="FONT-FAMILY: verdana, geneva">Skype: jolufuye</SPAN><BR><BR><SPAN 
style="FONT-FAMILY: verdana, geneva">This email is for the exclusive 
recipient/s and it may contain confidential materials. If you have received it 
and it is not meant for you, please alert me @ <a 
href="mailto:jolufuye@xxxxxxxxxxxxxxxx";>jolufuye@xxxxxxxxxxxxxxxx</a> or 
discard at once. Thank you.</SPAN></div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<BLOCKQUOTE id=replyBlockquote style="FONT-SIZE: 10pt; FONT-FAMILY: verdana; 
COLOR: black; PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px solid" 
webmail="1">
<DIV id=wmQuoteWrapper>-------- Original Message --------<BR>Subject: [bc-gnso] 
update on CCWG -Accountability, regading Stress Tests<BR>From: Steve DelBianco 
&lt;<a 
href="mailto:sdelbianco@xxxxxxxxxxxxx";>sdelbianco@xxxxxxxxxxxxx</a>&gt;<BR>Date:
 Sun, February 01, 2015 4:15 am<BR>To: BC List &lt;<a 
href="mailto:bc-gnso@xxxxxxxxx";>bc-gnso@xxxxxxxxx</a>&gt;<BR><BR>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)">
<DIV>
<DIV>As your CSG rep on the <A 
href="https://community.icann.org/display/acctcrosscomm/CCWG+on+Enhancing+ICANN+Accountability";
 target=_blank>CCWG – Accountability</A>, I’m trying to maintain momentum on 
contingencies/stress tests (<A 
href="https://community.icann.org/display/acctcrosscomm/ST-WP+--+Stress+Test+Work+Party";
 target=_blank>ST-WP</A>). &nbsp; As discussed, we start with the consolidated 
doc we developed in Frankfurt.&nbsp;</DIV></DIV></DIV><SPAN 
id=OLK_SRC_BODY_SECTION style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, 
sans-serif; COLOR: rgb(0,0,0)">
<DIV style="WORD-WRAP: break-word; FONT-SIZE: 16px; FONT-FAMILY: Calibri, 
sans-serif; COLOR: rgb(0,0,0); -webkit-nbsp-mode: space; -webkit-line-break: 
after-white-space">
<DIV>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)"><BR></DIV>
<BLOCKQUOTE style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; 
BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0px; PADDING-TOP: 0px; 
PADDING-LEFT: 0px; MARGIN: 0px 0px 0px 40px; BORDER-LEFT: medium none; 
PADDING-RIGHT: 0px">
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)">On page 1, added excerpt from our charter, regarding our required 
deliverables for Stress Testing.&nbsp;</DIV>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)"><BR></DIV>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)">On page 2, added a table showing how the original 25 stress tests 
mapped to the 5 consolidated categories. &nbsp; This captures the narrative and 
consequences developed by Work Team 4.</DIV>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)"><BR></DIV>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif"><SPAN 
style="COLOR: rgb(0,0,0)">On page 4, added Enterprise-Wide Risks identified by 
the ICANN Board Risk Committee (27-Jan-2015). &nbsp; The chairs asked us 
compare to our list and see if changes are suggested. &nbsp; I mapped these 
items to our 5 stress test categories, noting in </SPAN><FONT 
color=#ff0000>red</FONT>&nbsp;those that are not covered. 
&nbsp;</DIV></BLOCKQUOTE></DIV></DIV></SPAN>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)"><BR></DIV>
<BLOCKQUOTE style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; 
BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0px; PADDING-TOP: 0px; 
PADDING-LEFT: 0px; MARGIN: 0px 0px 0px 40px; BORDER-LEFT: medium none; 
PADDING-RIGHT: 0px">
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)">One ‘risk’ identified by ICANN’s board really caught my 
eye:&nbsp;</DIV>
<BLOCKQUOTE style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; 
BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0px; PADDING-TOP: 0px; 
PADDING-LEFT: 0px; MARGIN: 0px 0px 0px 40px; BORDER-LEFT: medium none; 
PADDING-RIGHT: 0px">
<DIV><FONT color=#ff0000 face=Calibri,sans-serif>Perception of failure to 
implement and help achieve a global multi-stakeholder distributed IG ecosystem 
according to the widely accepted Net Mundial 
Principles</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE><SPAN id=OLK_SRC_BODY_SECTION 
style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(0,0,0)">
<DIV style="WORD-WRAP: break-word; FONT-SIZE: 16px; FONT-FAMILY: Calibri, 
sans-serif; COLOR: rgb(0,0,0); -webkit-nbsp-mode: space; -webkit-line-break: 
after-white-space">
<DIV>
<BLOCKQUOTE style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; 
BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0px; PADDING-TOP: 0px; 
PADDING-LEFT: 0px; MARGIN: 0px 0px 0px 40px; BORDER-LEFT: medium none; 
PADDING-RIGHT: 0px">
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, 
sans-serif"></DIV></BLOCKQUOTE></DIV></DIV></SPAN>
<BLOCKQUOTE style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; 
BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0px; PADDING-TOP: 0px; 
PADDING-LEFT: 0px; MARGIN: 0px 0px 0px 40px; BORDER-LEFT: medium none; 
PADDING-RIGHT: 0px">
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)">On the CCWG call, I flagged this as far outside ICANN’s mission and 
an example of top-down scope-creep by management.</DIV></BLOCKQUOTE>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)"><BR></DIV><SPAN id=OLK_SRC_BODY_SECTION style="FONT-SIZE: 16px; 
FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(0,0,0)">
<DIV style="WORD-WRAP: break-word; FONT-SIZE: 16px; FONT-FAMILY: Calibri, 
sans-serif; COLOR: rgb(0,0,0); -webkit-nbsp-mode: space; -webkit-line-break: 
after-white-space">
<DIV>
<BLOCKQUOTE style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; 
BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0px; PADDING-TOP: 0px; 
PADDING-LEFT: 0px; MARGIN: 0px 0px 0px 40px; BORDER-LEFT: medium none; 
PADDING-RIGHT: 0px">
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif">2 risks that are 
not explicitly listed in our categories include loss of confidence in M-S model 
as practiced by iCANN, and lack of capacity to accommodate new stakeholders. 
&nbsp; I think we can add those to categories IV and V. 
&nbsp;</DIV></BLOCKQUOTE>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)"><BR></DIV>
<DIV><FONT face=Calibri,sans-serif>Before we get to Singapore, we should draft 
another action item from the chairs: &nbsp;</FONT><FONT 
face=Calibri,sans-serif><B>Add a specific contingency. &nbsp;</B>&nbsp;I think 
of this as e</FONT>xample application of stress test against recommended 
accountability mechanisms. &nbsp;Could do this after we have sufficient 
consensus around accountability mechanisms to evaluate. &nbsp;Alternatively, we 
could perform stress test analysis on the Requirements we developed in 
Frankfurt. &nbsp;<B style="FONT-FAMILY: Calibri, 
sans-serif">&nbsp;</B></DIV></DIV></DIV></SPAN>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: Calibri, sans-serif; COLOR: 
rgb(0,0,0)"><BR></DIV><SPAN id=OLK_SRC_BODY_SECTION style="FONT-SIZE: 16px; 
FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(0,0,0)">
<DIV style="WORD-WRAP: break-word; FONT-SIZE: 16px; FONT-FAMILY: Calibri, 
sans-serif; COLOR: rgb(0,0,0); -webkit-nbsp-mode: space; -webkit-line-break: 
after-white-space">
<DIV>
<DIV>—Steve</DIV>
<DIV><BR></DIV></DIV>
<DIV>
<DIV>
<DIV>
<DIV>—</DIV>
<DIV>
<DIV>Steve DelBianco</DIV>
<DIV>Executive Director</DIV>
<DIV>NetChoice</DIV>
<DIV><A href="http://www.netchoice.org/"; 
target=_blank>http://www.NetChoice.org</A>&nbsp;and&nbsp;<A 
href="http://blog.netchoice.org/"; 
target=_blank>http://blog.netchoice.org</A></DIV>
<DIV>+1.202.420.7482</DIV></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV></DIV></DIV></DIV></DIV></SPAN></DIV></BLOCKQUOTE></span></body></html>
<<< Chronological Index >>> <<< Thread Index >>>
Privacy Policy | Terms of Service | Cookies Policy