<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] FW: CCWG Final report for your consideration
- To: "James M. Bladel" <jbladel@xxxxxxxxxxx>, "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>, "Johan Helsingius" <julf@xxxxxxxx>
- Subject: Re: [council] FW: CCWG Final report for your consideration
- From: "Edward Morris" <egmorris1@xxxxxxxxx>
- Date: Thu, 25 Feb 2016 10:59:39 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toast.net; s=smartermail; h=references:in-reply-to:x-originating-ip:content-type:mime-version :message-id:reply-to:date:subject:to:from; bh=TEw3I6cGSlNa4D0irisg8yB+c8zD5THwmKJZkxavbD0=; b=mdWnz/+8MD0J79CF2c0GKKlom/KGQB9mfveouY9LQICE8GkYE6BYauibigjBHcmSZ GBt8NXT5/OJ7+xoHit9Si+UBge9OSyXXMLgFfsBsQwqsgFvaR4Kap/aTy+l4y5oHu LXzkPGlR6RNSGdMCpXoWtCFBB1upDoDBMVl1SvnJk=
- Domainkey-signature: a=rsa-sha1; c=nofws; q=dns; d=toast.net; s=smartermail; h=received:from:to:subject:date:reply-to:message-id:mime-version :content-type:x-originating-ip:in-reply-to:references; b=ILy0FWqlLD0MTPKaCG3VonDsNKJ6hIxUUxKW9590BvaunaD3pDAgYP2/LKICuTHNI 6DTB5n3+Le5U6mXNx2Nhtq1QrvDx9V/dUETRM+6cspTWJ8AqGAeUy2hbMNxDpemyH zXM37YJ1kqbqSLinEHNnbaBYNYK6kTI3C6zSnkcwM=
- In-reply-to: <56CF1E43.7050709@julf.com>
- List-id: council@xxxxxxxxxxxxxx
- References: <13201F1D-1CB2-473C-A284-65081474F66C@sanchez.mx> <D2F24A2B.AFB24%jbladel@godaddy.com> <0b8001d16f34$80cbafb0$82630f10$@paulmcgrady.com> <263EE96C7DADD44CB3D5A07DBD41D0E88F89B8A9@bne3-0001mitmbx.corp.mit> <56CF194E.8090403@julf.com> <D2F47864.B0152%jbladel@godaddy.com> <56CF1E43.7050709@julf.com>
- Reply-to: egmorris1@xxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
Hi Julf,
> Also (and looking for Bruce, Keith, Phil or others to confirm this), I
> believe this change only applies to community effort to spill the entire
> board, and would not apply to the mechanisms for recall of a single board
> member.
Could it be used repeatedly to spill the entire board,
one member at a time?
- I'm not Bruce, Keith or Phil, but I can confirm that this does not apply to
removal of individual Board members.
My principle problem with what happened was not with the specific substantive
issue but rather with the way it was raised. Seven and one half hours before a
review period on the day before we were to release the Final Report Steve
Crocker dropped the post on us that prompted the crisis. That the community did
not tell the Board to reserve their comment for the appropriate time (most of
which was in the past, some of which was in the future) or manner as envisioned
in the Charter was and is a problem for me. Accountability rules are nice but
if the Board is allowed by the community to ignore the timelines, rules and
procedures of the group in charge of developing future Accountability
procedures, why should anyone think the community will not allow the Board to
do the same in the future with those procedures?
The actual "battle" was over the text in red, below, which was deleted:
The CCWG-Accountability also recommends that in a situation where the GAC
may not participate as a Decisional Participant because the Community Power is
proposed to be used to challenge the Board's implementation of GAC consensus
advice and the threshold is set at four in support, the power will still be
validly exercised if three are in support and no more than one objects, with
the following exception:
Where the power to be exercised is recalling the entire Board for implementing
GAC advice, the reduced threshold would apply only either after an IRP has
found that, in implementing GAC advice, the Board acted inconsistently with the
ICANN Bylaws, or
(1) if the IRP is not available to challenge the Board action in question.
If the Empowered Community has brought such an IRP and does not prevail, the
Empowered Community may not exercise its power to recall the entire the Board
solely on the basis of the matter decided by the IRP. It may, however, exercise
that power based on other grounds.
Best,
Ed
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|