I will not be able to attend the call since it directly overlaps with an ALAC call that I am chairing. Here are several comments that I would appreciate being considered as if I was on the call and raised my hand. Voting Mechanism: As mentioned on the CCWG call, If an AC/SO wants to withdraw from participating, there should not be a delay. If there is, their lack of voting should not count against the action. Otherwise they may effectively block the action by making it impossible or almost impossible to achieve sufficient votes. Alternatively, the counting method could take this into account (as I think Holly suggested in the chat). But what is harm in making withdrawal immediate? Community Forum. Perhaps add Board to para 3 in addition to non-participating ACs. Budget veto: I am still uncomfortable with the concept of there being two separate budgets, one for IANA and one for the rest of ICANN. Normally, from a fiscal point of view, there is only a single budget which encompasses everything. Surely the funds to be used for IANA come from the same revenue pot as the rest of the expenses. Do we have confirmation from ICANN FInance that the words we have there make sense? Related to this, at the start, we talk about a veto of the IANA budget and a veto of the ICANN budget (para 3) but in the rest of the document, we only talk about a single veto. Is the process repeated for each? We need some clarity here. Director Removal: Rarely can we convene a new teleconference and get all of the necessary people together in a 15 day window. Is what we are proposing possible, and what happens if the 15-day delay is not met (para 5). In section d, is the 3/4 vote of the "5" votes of the community mech, or 3/4 of whatever internal voting the AC/SO has? Para 7-d The 3/5 requirement seems to be lowering the threshold from other votes (according to the newly proposed vote-counting mechanism). Lastly, should we specify whether a replacing term counts against the 3-term limit on directors? Recall of entire Board: Is the NomCom prepared to name interim directors PRIOR to the vote? If the vote fails, that means they have compromised their secrecy of potential but not-yet-named candidates. Alan At 28/07/2015 05:21 AM, Jordan Carter wrote:

Dear CCWG members

Please find attached a number of papers up for discussion on today's call in about three hours - these are final drafts, the marked ups and background versions are on the Wiki at the link below.

Also attached is a summary noting what the key most recent changes have been.

I particularly draw your attention to the paper which starts 5A2 on voting power, updated following the WP1 call this morning and now allocating 5 votes per SO and AC, and with an opt-in mechanism proposed.

Speak with you soon,

Jordan

---------- Forwarded message ---------- From: Jordan Carter <<mailto:jordan@internetnz.net.nz>jordan@internetnz.net.nz> Date: 28 July 2015 at 21:20 Subject: Draft Agenda & Papers - WP1 Meeting #22 (28 July at 19h UTC) To: "<mailto:wp1@icann.org>wp1@icann.org" <<mailto:wp1@icann.org>wp1@icann.org>

Hi all

Here is the draft agenda and the documents for the WP1 call happening at 19-21h UTC on Tuesday 28 July 2015.

Also attached is the summary of issues.

Please read these documents before the call - the working method will be an "Are There Any Final Comments To Make/Did Anything Decided at CCWG Affect This Draft" approach...

[the reason for this is that our meeting finishes only 3 hrs before the absolute Freeze date for the

1. Review of Agenda.

2. Any outstanding issues from CCWG meeting of 28 July (12h-14h)

3. Final Review of the Following Documents (clean PDFs of "final drafts" attached - mark ups and Word versions to come on Wiki site at <<https://community.icann.org/display/acctcrosscomm/WP1+Draft+Documents>https://community.icann.org/display/acctcrosscomm/WP1+Draft+Documents> )

Fundamental Bylaws (3B)

Community Mechanism description (5A1) Community Mech - voting weights (5A2) -- NOTE an update to come yet from Bernie and Alan re quorums etc) Community Mech - ICANN community forum (5A3)

Comm Power - Budgets and Plans (5B1) Comm Power - Standard Bylaws (5B2) Comm Power - Removal of ICANN directors (5B3) Comm Power - Recall of ICANN Board (5B4)

Note: Steve's paper on incorporating AOC reviews into the ICANN bylaws (6-2) had agreement to incorporate the text on document disclosure etc on 27 July, so that paper is done and dusted. It's attached just so there is a complete collection here, but is not for discussion.

4. Next Task: Finalising responses to Public Comments from PC1

5. Any other matters

-- Jordan Carter

Chief Executive InternetNZ

+64-495-2118 (office) | <tel:%2B64-21-442-649>+64-21-442-649 (mob) Email: <mailto:jordan@internetnz.net.nz>jordan@internetnz.net.nz Skype: jordancarter

A better world through a better Internet

-- Jordan Carter

Chief Executive InternetNZ

+64-495-2118 (office) | +64-21-442-649 (mob) Email: <mailto:jordan@internetnz.net.nz>jordan@internetnz.net.nz Skype: jordancarter

A better world through a better Internet

Content-Type: application/pdf; name="3B-Fundamental-Bylaws-FinalDraft.pdf" Content-Disposition: attachment; filename="3B-Fundamental-Bylaws-FinalDraft.pdf" X-Attachment-Id: f_icn4k5a10

Content-Type: application/pdf; name="5A-Community-Mechanism-Descr-FinalDraft.pdf" Content-Disposition: attachment; filename="5A-Community-Mechanism-Descr-FinalDraft.pdf" X-Attachment-Id: f_icn4kcdt1

Content-Type: application/pdf; name="5A2-Community-Mechanism-Voting-PenultimateDraft.pdf" Content-Disposition: attachment; filename="5A2-Community-Mechanism-Voting-PenultimateDraft.pdf" X-Attachment-Id: f_icn4kh5c2

Content-Type: application/pdf; name="5A3-Comm-Mech-ICANNCommForum-FinalDraft.pdf" Content-Disposition: attachment; filename="5A3-Comm-Mech-ICANNCommForum-FinalDraft.pdf" X-Attachment-Id: f_icn4kuca3

Content-Type: application/pdf; name="5B1-Comm-Power-BudgetAndPlans-FinalDraft.pdf" Content-Disposition: attachment; filename="5B1-Comm-Power-BudgetAndPlans-FinalDraft.pdf" X-Attachment-Id: f_icn4l0ll4

Content-Type: application/pdf; name="5B2-Comm-Power-StandardBylaws-FinalDraft.pdf" Content-Disposition: attachment; filename="5B2-Comm-Power-StandardBylaws-FinalDraft.pdf" X-Attachment-Id: f_icn4l4q05

Content-Type: application/pdf; name="5B3-Comm-Power-RemovingDirectors-FinalDraft.pdf" Content-Disposition: attachment; filename="5B3-Comm-Power-RemovingDirectors-FinalDraft.pdf" X-Attachment-Id: f_icn4l8ih6

Content-Type: application/pdf; name="5B4-Comm-Power-RecallingICANNBoard-FinalDraft.pdf" Content-Disposition: attachment; filename="5B4-Comm-Power-RecallingICANNBoard-FinalDraft.pdf" X-Attachment-Id: f_icn4lcrq7

Content-Type: application/pdf; name="6-AOC-Reviews-in-Bylaws-FinalDraft.pdf" Content-Disposition: attachment; filename="6-AOC-Reviews-in-Bylaws-FinalDraft.pdf" X-Attachment-Id: f_icn4udzz8

Content-Type: application/pdf; name="2015-07-28-WP1-summary-to-CCWG.pdf" Content-Disposition: attachment; filename="2015-07-28-WP1-summary-to-CCWG.pdf" X-Attachment-Id: f_icn4uhzb9

_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community