[CCWG-ACCT] inconsistency in bylaws spotted
Schaefer, Brett
Brett.Schaefer at heritage.org
Tue Apr 26 11:00:44 UTC 2016
The existing text states that approval of all the Chartering Organizations is required. So the purpose of this addition is to clarify that the Chairs may forward a proposal to the Board even if all of the Chartering Organizations do not approve it?
From the Charter:
Supplemental Draft Proposal
In the event that one or more of the participating SO’s or AC’s do(es) not adopt one or more of the recommendation(s) contained in the Draft Proposal(s), the Co-Chairs of the CCWG-Accountability shall be notified accordingly. This notification shall include at a minimum the reasons for the lack of support and a suggested alternative that would be acceptable, if any. The CCWG-Accountability may, at its discretion, reconsider, post for public comments and/or submit to the chartering organizations a Supplemental Draft Proposal, which takes into accounting the concerns raised.
Following submission of the Supplemental Draft Proposal, the chartering organizations shall discuss and decide in accordance with its own rules and procedures whether to adopt the recommendations contained in the Supplemental Draft Proposal. The Chairs of the chartering organizations shall notify the Co-Chairs of the CCWG- Accountability of the result of the deliberations as soon as feasible.
Submission Board Report
After receiving the notifications from all chartering organizations as described above, the Co-Chairs of the CCWG-Accountability shall, within 10 working days after receiving the last notification, submit to the Chair of the ICANN Board of Directors and Chairs of all the chartering organizations the CCWG-Accountability Board Report, which shall include at a minimum:
1. a) The (Supplemental) Proposal as adopted by the CCWG-Accountability; and
2. b) The notifications of the decisions from the chartering organizations
3. c) Documentation of the process that was followed, including, but not limited to documenting the
process of building consensus within the CCWG-Accountability and public consultations.
In the event one or more of the chartering organizations do(es) not support (parts of) the (Supplemental) Proposal(s), the Board Report shall also clearly indicate the part(s) of the (Supplemental) Final Proposal(s) which are fully supported and the parts which not, and which of the chartering organizations dissents, to the extent this is feasible.
________________________________
Brett Schaefer
Jay Kingham Senior Research Fellow in International Regulatory Affairs
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy
The Heritage Foundation
214 Massachusetts Avenue, NE
Washington, DC 20002
202-608-6097
heritage.org<http://heritage.org/>
On Apr 25, 2016, at 7:12 PM, Greg Shatan <gregshatanipc at gmail.com<mailto:gregshatanipc at gmail.com>> wrote:
Holly and All,
I'm concerned that by reverting to the language in the Proposal, we are perpetuating the language that led to confusion in the first place. It should be clear that this is a "business as usual" process of Chartering Organization review of a CCWG-Accountability consensus recommendations, just as was done with the Proposal. i would suggest adding the following clarifying language:
“(a) The Core Value set forth in Section 1.2(b)(viii) shall have no force or effect unless and until a framework of interpretation for human rights (“FOI-HR”) is approved by (i) the CCWG-Accountability as a consensus recommendation in Work Stream 2 (including Chartering Organizations’ approval as set forth in the CCWG-Accountability Charter), and (ii) each of the CCWG-Accountability’s chartering organizations and (iii) the Board (in the case of the Board, using the same process and criteria used by the Board to consider the Work Stream 1 Recommendations).”
I look forward to your thoughts.
Greg
On Mon, Apr 25, 2016 at 3:48 PM, Gregory, Holly <holly.gregory at sidley.com<mailto:holly.gregory at sidley.com>> wrote:
Dear CCWG-Accountability,
We have been following this email stream and in re-reading the language of the Bylaws we understand how the language could be misread to call for a standard higher than what is intended. Therefore we propose that a clarification would be helpful. Specifically, to remove any confusion and help assure that the Bylaws are read in a manner that is consistent with the proposal, we recommend the following clarifying change to Section 27.3:
“(a) The Core Value set forth in Section 1.2(b)(viii) shall have no force or effect unless and until a framework of interpretation for human rights (“FOI-HR”) is approved by (i) the CCWG-Accountability as a consensus recommendation in Work Stream 2 (including Chartering Organizations’ approval), and (ii) each of the CCWG-Accountability’s chartering organizations and (iii) the Board (in the case of the Board, using the same process and criteria used by the Board to consider the Work Stream 1 Recommendations).”
If you agree, we recommend that you include this in the CCWG’s public comment.
Kind regards,
Holly
HOLLY J. GREGORY
Partner and Co-Chair
Corporate Governance & Executive Compensation Practice Group
Sidley Austin LLP
787 Seventh Avenue
New York, NY 10019
+1 212 839 5853<tel:%2B1%20212%20839%205853>
holly.gregory at sidley.com<mailto:holly.gregory at sidley.com>
www.sidley.com<http://www.sidley.com/>
[http://www.sidley.com/files/upload/signatures/SA-autosig.png]<http://www.sidley.com/> SIDLEY AUSTIN LLP
From: accountability-cross-community-bounces at icann.org<mailto:accountability-cross-community-bounces at icann.org> [mailto:accountability-cross-community-bounces at icann.org<mailto:accountability-cross-community-bounces at icann.org>] On Behalf Of McAuley, David
Sent: Monday, April 25, 2016 2:12 PM
To: Dr. Tatiana Tropina; accountability-cross-community at icann.org<mailto:accountability-cross-community at icann.org>
Subject: Re: [CCWG-ACCT] inconsistency in bylaws spotted
In my personal opinion, I think Tatiana was correct in observing that there can be different interpretations in this respect.
I respectfully don’t think we can now say that decision making regarding the FoI in WS2 is simply based on the charter. The charter set WS1 in motion and in WS1 we specifically agreed that the HR bylaw will not enter into force until, among other things, an FoI is developed as a consensus WS2 recommendation “(including Chartering Organizations’ approval)” – we cannot delete that quoted bylaw language as it means something.
Here is what the draft bylaw-language in the proposal provides:
“Within its Core Values, ICANN will commit to respect internationally recognized Human Rights as required by applicable law. This provision does not create any additional obligation for ICANN to respond to or consider any complaint, request, or demand seeking the enforcement of Human Rights by ICANN. This Bylaw provision will not enter into force until (1) a Framework of Interpretation for Human Rights (FOI-HR) is developed by the CCWG-Accountability as a consensus recommendation in Work Stream 2 (including Chartering Organizations’ approval) and (2) the FOI-HR is approved by the ICANN Board using the same process and criteria it has committed to use to consider the Work Stream 1 recommendations.”
If that requires further clarity it seems to me that it will need to be developed in WS2 given that our charge now is to see if the bylaws draft tracks the final proposal. In this respect it appears to do so.
David McAuley
From: accountability-cross-community-bounces at icann.org<mailto:accountability-cross-community-bounces at icann.org> [mailto:accountability-cross-community-bounces at icann.org] On Behalf Of Dr. Tatiana Tropina
Sent: Sunday, April 24, 2016 4:42 PM
To: accountability-cross-community at icann.org<mailto:accountability-cross-community at icann.org>
Subject: Re: [CCWG-ACCT] inconsistency in bylaws spotted
Hi all,
I certainly understand that there can be different interpretations of the intent of the report.
The item (ii) of the bylaw in the report says: "consensus recommendation in Work Stream 2 (including Chartering Organizations’ approval)".
We have even have different thresholds for consensus in the report itself, which one is applicable here? What is the process for reaching this consensus? The same as for WS1? Then we might need a reference to WS1 may be? Furthermore: will everything developed in the WS2 require a full consensus and approval of all COs? I read the chapter in the bylaws about WS2 and it refers to the process and charter of WS1. No requirement for full consensus or approval of the all the COs there. Why does not HR bylaw refer to the previous section in the bylaw that specifically outlines the requirements for Ws, but introduces the approval of all COs instead? I don't mind this, but the clarification seems to be necessary.
Is there already a definition of consensus for the purpose of the WS2 and if yes, is it the same that has been introduced for HR FOI in HR bylaw text? This is my question.
If the answer is "yes" - then there is no inconsistency. However, I agree with Niels that this should be clarified, so we all will be on the same page.
Cheers
Tanya
On 24/04/16 20:44, Seun Ojedeji wrote:
Hi,
Are you saying that the bylaw text is different from the intent of the report as I don't think that is the case. The report indeed required approval of the CO which was rightly reflected as item ii in the bylaw text.
I therefore think the bylaw text is consistent with the intent of the report.
Regards
Sent from my LG G4
Kindly excuse brevity and typos
On 24 Apr 2016 7:01 p.m., "Niels ten Oever" <lists at nielstenoever.net<mailto:lists at nielstenoever.net>> wrote:
Dear all,
I hope this email finds you well. Upon re-reading the bylaw text I came
across the following issue which does not seem to be in accordance with
what we agreed in WS1.
The CCWG report says where it comes to Human Rights:
[ccwg report]
“Within its Core Values, ICANN will commit to respect internationally
recognized
Human Rights as required by applicable law. This provision does not
create any
additional obligation for ICANN to respond to or consider any
complaint, request,
or demand seeking the enforcement of Human Rights by ICANN. This Bylaw
provision will not enter into force until (1) a Framework of
Interpretation for Human
Rights (FOI-HR) is developed by the CCWG-Accountability as a consensus
recommendation in Work Stream 2 (including Chartering Organizations’
approval)
and (2) the FOI-HR is approved by the ICANN Board using the same
process and
criteria it has committed to use to consider the Work Stream 1
recommendations.”
[/ccwg report]
But when I look at the bylaw text it says:
[proposed bylaw]
The Core Value set forth in Section 1.2(b)(viii) shall have no force or
effect unless and until a framework of interpretation for human rights
(“FOI-HR”) is approved by (i) the CCWG-Accountability as a consensus
recommendation in Work Stream 2, (ii) each of the CCWG-Accountability’s
chartering organizations and (iii) the Board (in the case of the Board,
using the same process and criteria used by the Board to consider the
Work Stream 1 Recommendations).
[/proposed bylaw]
Now it is explicitly required that all Chartering Organizations approve
the Framework of Interpretation, whereas during WS1 it was agreed that
for WS2 we would use exactly the same process of approval as for WS1.
What makes this even more divergent is that this clause is only added
for Human Rights in the proposed bylaws and not for any other bylaw.
Whereas there was no exceptional procedure for human rights discussed
for WS2.
What I propose is to refer to the charter of the CCWG on Accountability
for the decision making of all processes in WS2 (including the decision
making on the FoI on Human Rights) and not create separate or new
requirements or processes.
All the best,
Niels
--
Niels ten Oever
Head of Digital
Article 19
www.article19.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.article19.org&d=CwMFAg&c=Od00qP2XTg0tXf_H69-T2w&r=1-1w8mU_eFprE2Nn9QnYf01XIV88MOwkXwHYEbF2Y_8&m=CW0HijJt950Jj0TnSs0Uu9zc0aeHn-COr3a24oHd6IM&s=NcvlJyYsf1dukFULmFMt12-UJRg0HtYLbYCN8XiVDjo&e=>
PGP fingerprint 8D9F C567 BEE4 A431 56C4
678B 08B5 A0F2 636D 68E9
_______________________________________________
Accountability-Cross-Community mailing list
Accountability-Cross-Community at icann.org<mailto:Accountability-Cross-Community at icann.org>
https://mm.icann.org/mailman/listinfo/accountability-cross-community<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMFAg&c=Od00qP2XTg0tXf_H69-T2w&r=1-1w8mU_eFprE2Nn9QnYf01XIV88MOwkXwHYEbF2Y_8&m=CW0HijJt950Jj0TnSs0Uu9zc0aeHn-COr3a24oHd6IM&s=Ke7m0Wc1WOPvT-zpltBPQ4xvdcoE_ZdB2l0cdHhY7go&e=>
_______________________________________________
Accountability-Cross-Community mailing list
Accountability-Cross-Community at icann.org<mailto:Accountability-Cross-Community at icann.org>
https://mm.icann.org/mailman/listinfo/accountability-cross-community<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMFAg&c=Od00qP2XTg0tXf_H69-T2w&r=1-1w8mU_eFprE2Nn9QnYf01XIV88MOwkXwHYEbF2Y_8&m=CW0HijJt950Jj0TnSs0Uu9zc0aeHn-COr3a24oHd6IM&s=Ke7m0Wc1WOPvT-zpltBPQ4xvdcoE_ZdB2l0cdHhY7go&e=>
****************************************************************************************************
This e-mail is sent by a law firm and may contain information that is privileged or confidential.
If you are not the intended recipient, please delete the e-mail and any attachments and notify us
immediately.
****************************************************************************************************
_______________________________________________
Accountability-Cross-Community mailing list
Accountability-Cross-Community at icann.org<mailto:Accountability-Cross-Community at icann.org>
https://mm.icann.org/mailman/listinfo/accountability-cross-community<https://mm.icann.org/mailman/listinfo/accountability-cross-community>
_______________________________________________
Accountability-Cross-Community mailing list
Accountability-Cross-Community at icann.org<mailto:Accountability-Cross-Community at icann.org>
https://mm.icann.org/mailman/listinfo/accountability-cross-community
More information about the Accountability-Cross-Community
mailing list