Hi Avri,
SOs are only empowered to make recommendations on the subject matter of the SO, i.e. only on gTLDs, ccTLDs or Numbers.
Agree.
We assrt our right to comment on other stuff, but there is no bylaws indication of this empowerment.
Who is we?
It is only the ACs that are empowered to advise on any issue having to do with ICANN.
Agreed. So that means that the non-contracting party bits of GNSO are only empowered to comment on gTLD matters, doesn’t it? Assuming that is correct then it seems to me that in respect to 'ICANN’s general well being’ we should not draw a distinction between ACs and SOs. SOs and ACs are empowered to comment on 'ICANN’s general well being’ with authority/weight and bits of the SOs and ACs are entitled to comment (as is anyone as an individual) but not with the same authority and weight as comments on SOs and ACs as a whole. Does that make sense? Cheers, Chris
On 28 Jul 2015, at 22:35 , Avri Doria <avri@acm.org> wrote:
Hi,
By the same token, in the tradional understanding of ICANN, SOs are only empowered to make recommendations on the subject matter of the SO, i.e. only on gTLDs, ccTLDs or Numbers. We assrt our right to comment on other stuff, but there is no bylaws indication of this empowerment.
It is only the ACs that are empowered to advise on any issue having to do with ICANN.
Should we limit the votes of SOss if these votes are not in their specific areas of responsibility?
The issues that we may be voting on are about the general well being of ICANN. And to me that seems to be equally in the bailiwick of all the ACSO.
avri
Note I do not speak for NCSG in the CCWG, Robin does.
On 28-Jul-15 12:55, Robin Gross wrote:
I still believe that ACs should remain in an advisory role and not additionally have votes. We seem to be fundamentally changing the roles of ICANN's constituent parts in ways that clearly have not been fully examined. The SO's are charged with making policy and ACs are charged with advising the board in ICANN's existing structure, but we will be eliminating that barrier in many cases with this mechanism, with SO's giving away most of this power to ACs. Even if we could find consensus in such a re-balancing and re-assignment of roles (and I'm not sure we can), I don't see how Congress or the NTIA could accept such a massive reformulation and subversion of the SO's interests. Advisory Committees are "advisory" and we should not change that through this process, despite the crushing pressure to go along for a fast transition.
Robin
On Jul 28, 2015, at 2: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* <jordan@internetnz.net.nz <mailto:jordan@internetnz.net.nz>> Date: 28 July 2015 at 21:20 Subject: Draft Agenda & Papers - WP1 Meeting #22 (28 July at 19h UTC) To: "wp1@icann.org <mailto:wp1@icann.org>" <wp1@icann.org <mailto: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> )
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) | +64-21-442-649 <tel:%2B64-21-442-649> (mob) Email: jordan@internetnz.net.nz <mailto: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: jordan@internetnz.net.nz <mailto:jordan@internetnz.net.nz> Skype: jordancarter
/A better world through a better Internet /
<3B-Fundamental-Bylaws-FinalDraft.pdf><5A-Community-Mechanism-Descr-FinalDraft.pdf><5A2-Community-Mechanism-Voting-PenultimateDraft.pdf><5A3-Comm-Mech-ICANNCommForum-FinalDraft.pdf><5B1-Comm-Power-BudgetAndPlans-FinalDraft.pdf><5B2-Comm-Power-StandardBylaws-FinalDraft.pdf><5B3-Comm-Power-RemovingDirectors-FinalDraft.pdf><5B4-Comm-Power-RecallingICANNBoard-FinalDraft.pdf><6-AOC-Reviews-in-Bylaws-FinalDraft.pdf><2015-07-28-WP1-summary-to-CCWG.pdf>_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org <mailto:Accountability-Cross-Community@icann.org> https://mm.icann.org/mailman/listinfo/accountability-cross-community
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community