<<<
Chronological Index
>>> <<<
Thread Index
>>>
Comments
- To: comments-ccwg-accountability-draft-proposal-04may15@xxxxxxxxx
- Subject: Comments
- From: "Sue Randel" <suerandel@xxxxxxxxxxxxxx>
- Date: Wed, 3 Jun 2015 23:44:49 +0200
<html><head></head><body><div style="font-family: Verdana;font-size:
12.0px;"><div>
<style type="text/css"><!--P { margin-bottom: 0.08in; }
--></style>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">I applaud
the work of the ccwg-accountability team and appreciate the opportunity to
comment.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">Your
proposal to replace the current US government backstop on IANA function
oversight by empowering ICANN's current membership structure is both simple
and efficient.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">The past few
years of mismanagement inside ICANN have demonstrated a necessity to place such
overriding powers outside of the management and board.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">Your
framework offers a mechanism to not only fix the problems of inexperienced or
mismatched (with mission/core values) management but to also shine a brighter
light on internal operations to improve much needed transparency.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">From the
inside looking out, ICANN's failures all seemed to be due to the general
lack of experience with the community and Internet governance diplomacy from
those at the helm.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">This has led
to multiple breaches and errors in judgment and short sighted decisions that
have caused the exodus of key talent from IANA operations and a "circle
the wagons", "hire only [inexperienced] friends",stop work,
"hide everything" disease in the organization - instead of
transparent and responsible operations.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">Current
articles on ICANN's strong push to get the IFO assigned to it forever
should give us all pause. This odd behavior is in line with what I had observed
inside.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">With the
ability to recall the board or dismiss individual board members as well as
directly effect board/management/staff decisions on strategic plans and budget,
the community will finally have an effective recourse to such self-serving
behavior.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">Furthermore,
enshrining a mechanism for the community to veto or approve ICANN's bylaws,
mission, commitments and core values is an excellent way to ensure ICANN only
attracts the right talent in the board and executive levels.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">Your
detailed work on the bylaws is most welcome as they have long needed updating
to align with what ICANN actually does and be strengthened to limit mission
creep...and to ensure ICANN's decisions are for public benefit - not just a
particular set of stakeholders or ICANN itself.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">I believe
your proposals made in the Report will solve the numerous problems extending up
and down the current and future management chains, ensuring accountability, and
going a long way to making the multstakeholder experiment succeed and become a
model for others.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">Now for the
Questions.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">1a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">1b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">2 I believe
the thresholds proposed are sufficient at this time.</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">3a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">3b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">4a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">4b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">5a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">5b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">6
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">7
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">8
YES</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">9
none</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">10 para 191
is reasonable as a start. We should have the ability to change later.</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">11a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">11b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">12a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">12b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">13a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">13b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">14a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">14b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">15a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">15b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">16a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">16b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">17a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">17b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">18a
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">18b
yes</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">19
none</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif,
serif">paragraphs:</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">406 Although
it may be out of scope, a 6th stress test category might be capture of root
zone by ITU or other body. As there is no legal or technical barrier to such an
event - only reputation and political (e.g. arising from para 499). Thus far
the US government has provided political cover from this. I see para 596
attempts to address but may be insufficient.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">452-454 PTI
should be forced to publish any audit results in full (e.g.SOC2) and have
separate legal advisors from ICANN. e.g., para 549.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">581, 657 -
and reputation loss that could lead to capture.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">585
YES!</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">613 From
past community discussions, if community driven, an "ICANN
foundation" may be a desirable outcome.</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">663
YES!</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">707,708
YES!</font></p>
<p style="margin-bottom: 0in"> </p>
<p style="margin-bottom: 0in"><font face="Liberation Serif,
serif">Regards,</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">Sue
Randel</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">Former
contracting staff in fear of retaliation.</font></p>
<p style="margin-bottom: 0in"><font face="Liberation Serif, serif">(A whistle
blower protection element in the Bylaws would force much greater transparency
into the organization as well.)</font></p>
<div> </div>
<div> </div>
</div></div></body></html>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|