[WP1] V1 for PC2 Report - Community Powers - Standard Bylaws

[Jordan Carter]

Hi all

Please find attached some marked up text from Izumi, who has prepared us
for our discussion on the community power of rejecting changes to the
standard ICANN bylaws.

The notes below from Izumi summarise what has changed, and highlight some
issues for discussion.

This item is on our agenda for the 13 July call.

best,
Jordan


Attached is how I have reflected the community feedback for 2nd Public
Comment on Standard ByLaws changes.

There were not many changes needed but a few points which needs the CCWG to
have further discussions.
See [Further Discussions] for more details.


*[Status of Proposed CCWG response/approach to resolution (Developed by
WP1)]*

Based on "WP1 Summaries by Question" from the Public Comments. No specific
comments on this area observed at ICANN53.
https://community.icann.org/display/acctcrosscomm/First+Public+Comment+Review

* CCWG will consider extending the community review period from 2 weeks to
a longer timeframe TBD
   --> "2 weeks" deleted but alternative TBD

* CCWG will continue to explore and explain member structure
   --> Not reflected: needs to fix the model first

* CCWG will consider lowering the vote threshold from 3/4 to 2/3
   --> Reflected

* CCWG will consider mechanisms for limiting procedural impasse and
possible delays
   --> Not reflected: Needs discussions

* CCWG will consider a cap on the number of times this power can be
utilized. Further clarification needed
   --> Reflected


*[Further Discussions]*

* CCWG will consider extending the community review period from 2 weeks to
a longer timeframe TBD
   - CCWG needs to agree on the alternative
   - Alternative options expressed from the public comment:
     a) 30 days
     b) 60 days
     c) The end of the next ICANN meeting that begins no sooner than one
month after the Board posts notice of adoption
     d) Prior to such changes becoming effective

* CCWG will continue to explore and explain member structure
   - Requested to explain how Member status can be created and maintained
without undue costs, complexity, or liability (325)
   - Needs an explanation once the mechanism is fixed
   - Need confirmation with lawyers on how to respond

* CCWG will consider mechanisms for limiting procedural impasse and
possible delays
   - Needs to consider alternatives to two weeks, in balance with this point
   - Needs to consider whether putting limits on the number of times for
this power to be ultilized is sufficient

* CCWG will consider a cap on the number of times this power can be
utilized.
   - Reflected but needs to confirm whether there are no concerns

* How to address comment (341)
   - Which requests to increase composition of SOs/ACs other than ccNSO and
GAC
   - Out of scope to consider it at a part of this work but needs to
consider how to respond


-- 
Jordan Carter

Chief Executive
*InternetNZ*

04 495 2118 (office) | +64 21 442 649 (mob)
jordan at internetnz.net.nz
Skype: jordancarter

*A better world through a better Internet *
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/wp1/attachments/20150713/0ec68ddb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2015-07-13 Draft for 2nd Report - Community Power 5-3 - Standard Bylaws.pdf
Type: application/pdf
Size: 33416 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/wp1/attachments/20150713/0ec68ddb/2015-07-13Draftfor2ndReport-CommunityPower5-3-StandardBylaws-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2015-07-13 Draft for 2nd Report - Community Power 5-3 - Standard Bylaws.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 18453 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/wp1/attachments/20150713/0ec68ddb/2015-07-13Draftfor2ndReport-CommunityPower5-3-StandardBylaws-0001.docx>