[Party1] WP1: Draft 5, with all Affirmation Reviews implemented as Bylaws changes

[Steve DelBianco]

Regarding Kavouss’ point about the ATRT assessing the 'effectiveness of the GAC’.
A deeper read of ICANN bylaws tells me that ‘effectiveness’ is part of what the structural reviews are about.   So while these structural reviews don’t actually assess the effectiveness of the GNSO, CCNSO, etc., they do make recommendations about how to improve the effectiveness.  (see bylaws below)

Section 4. PERIODIC REVIEW OF ICANN STRUCTURE AND OPERATIONS

1. The Board shall cause a periodic review of the performance and operation of each Supporting Organization, each Supporting Organization Council, each Advisory Committee (other than the Governmental Advisory Committee), and the Nominating Committee by an entity or entities independent of the organization under review. The goal of the review, to be undertaken pursuant to such criteria and standards as the Board shall direct, shall be to determine (i) whether that organization has a continuing purpose in the ICANN structure, and (ii) if so, whether any change in structure or operations is desirable to improve its effectiveness.

From: Steve DelBianco
Date: Wednesday, March 4, 2015 at 5:27 PM
To: Jordan Carter, "wp1 at icann.org<mailto:wp1 at icann.org>"
Cc: Matthew Shears, Fiona Asonga, ACCT-Staff
Subject: WP1: Draft 5, with all Affirmation Reviews implemented as Bylaws changes

Draft v5 (attached) reflects the discussion/suggestions from our call on 4-Mar-2015.

From: Steve DelBianco
Date: Monday, March 2, 2015 at 3:56 PM
To: Jordan Carter, "wp1 at icann.org<mailto:wp1 at icann.org>"
Cc: Matthew Shears, Fiona Asonga, ACCT-Staff
Subject: WP1: Draft 4, with all Affirmation Reviews implemented as Bylaws changes

here’s an updated doc for Matthew, Fiona, and me, where we are importing the Affirmation of Commitments Reviews into the ICANN Bylaws.  The last 2 pages of this doc show proposed bylaws language for all 4 reviews.

Matthew Shears also has draft language regarding other commitments from AoC that should be considered for import into ICANN bylaws.

Best,
Steve


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/wp1/attachments/20150304/bc45c956/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Draft 1- AoC Accountability Mechanisms [Steve v5].pdf
Type: application/pdf
Size: 146688 bytes
Desc: Draft 1- AoC Accountability Mechanisms [Steve v5].pdf
URL: <http://mm.icann.org/pipermail/wp1/attachments/20150304/bc45c956/Draft1-AoCAccountabilityMechanismsStevev5-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/applefile
Size: 433 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/wp1/attachments/20150304/bc45c956/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Draft 1- AoC Accountability Mechanisms [Steve v5].doc
Type: application/msword
Size: 60416 bytes
Desc: Draft 1- AoC Accountability Mechanisms [Steve v5].doc
URL: <http://mm.icann.org/pipermail/wp1/attachments/20150304/bc45c956/Draft1-AoCAccountabilityMechanismsStevev5-0001.doc>