<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] Re: [CCWG-ACCT] A message from the Co-Chairs
- To: Phil Corwin <psc@xxxxxxxxxxx>, "Paul McGrady (Policy)" <policy@xxxxxxxxxxxxxxx>, "'GNSO Council List'" <council@xxxxxxxxxxxxxx>
- Subject: Re: [council] Re: [CCWG-ACCT] A message from the Co-Chairs
- From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
- Date: Tue, 23 Feb 2016 23:40:42 +0000
- Accept-language: en-US
- Authentication-results: vlaw-dc.com; dkim=none (message not signed) header.d=none;vlaw-dc.com; dmarc=none action=none header.from=godaddy.com;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureservernet.onmicrosoft.com; s=selector1-godaddy-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=brUBKzRbGG+9T9n/3EBEPv42POTH66bKXJK8a3AGGdE=; b=KUK0MtaN3BwlTQ/EMVamhUwavofYwSEcX2ZmxTppSmdDI/DbW5Ycv5+jZjNMXHokFiXNJlraMpoLa2gdQpwvbTTK93l7H/maIF5G2jY0M+mos81vO5GgSrob0Ikd+bvVTfXLRK3qg6dsmhGqFmBjY/4CyEGR4ufAEA39nqa77xU=
- In-reply-to: <8E84A14FB84B8141B0E4713BAFF5B84E1E06294D@Exchange.sierracorporation.com>
- List-id: council@xxxxxxxxxxxxxx
- References: <100BE3BA-F799-42F7-95E6-01C9EA70EEF1@sanchez.mx> <D2ED28CC.AF069%jbladel@godaddy.com> <05a601d16d7d$cecebd50$6c6c37f0$@paulmcgrady.com> <0a9b01d16e85$62bd3d90$2837b8b0$@paulmcgrady.com> <8E84A14FB84B8141B0E4713BAFF5B84E1E06294D@Exchange.sierracorporation.com>
- Sender: owner-council@xxxxxxxxxxxxxx
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:23
- Thread-index: AQHRa3Rm+z7UMEjUzkmo0cjBrVfMLp8zz9EAgARU4QCAAg8pgIAAFi4A//+hoIA=
- Thread-topic: [council] Re: [CCWG-ACCT] A message from the Co-Chairs
Thanks, Phil. I expect the same, full publication within the next 48 hours.
J.
From: Phil Corwin <psc@xxxxxxxxxxx<mailto:psc@xxxxxxxxxxx>>
Date: Tuesday, February 23, 2016 at 17:18
To: "Paul McGrady (Policy)"
<policy@xxxxxxxxxxxxxxx<mailto:policy@xxxxxxxxxxxxxxx>>, James Bladel
<jbladel@xxxxxxxxxxx<mailto:jbladel@xxxxxxxxxxx>>, GNSO Council List
<council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: RE: [council] Re: [CCWG-ACCT] A message from the Co-Chairs
The CCWG Co-Chairs have decided that polling on last night’s call justified the
removal of the controversial clause 2 in section 72 of Annex 2.
Final report is to be distributed today, and revised Appendix A in 48 hours.
So we will have everything well in advance of the 2/29 Council call.
Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/cell
Twitter: @VlawDC
"Luck is the residue of design" -- Branch Rickey
From: owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Paul McGrady (Policy)
Sent: Tuesday, February 23, 2016 4:59 PM
To: 'James M. Bladel'; 'GNSO Council List'
Subject: RE: [council] Re: [CCWG-ACCT] A message from the Co-Chairs
James,
Has there been any further word from CCWG-ACCT?
Best,
Paul
Paul D. McGrady, Jr.
policy@xxxxxxxxxxxxxxx<mailto:policy@xxxxxxxxxxxxxxx>
+1-312-558-5963
From:owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Paul McGrady (Policy)
Sent: Monday, February 22, 2016 08:32 AM
To: 'James M. Bladel'; 'GNSO Council List'
Subject: RE: [council] Re: [CCWG-ACCT] A message from the Co-Chairs
I’m concerned about waiving the document cut off if the “last chance to waive
red flags” ethos remains. I thought that would be a difficult ethos to connect
with in the first place, but as this drags out, it seems even more arbitrary.
In other words, I’m for keeping the Feb 29th session, so long as I am not told
later that my stakeholders missed their window to raise issues because they
weren’t raised on the 29th.
Best,
Paul
From:owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of James M. Bladel
Sent: Friday, February 19, 2016 8:23 PM
To: GNSO Council List
Subject: [council] Re: [CCWG-ACCT] A message from the Co-Chairs
Colleagues -
Please see below. The CCWG will not publish today, which is the document
cut-off for our Special Session on 29 FEB.
I’m open to proposals that we either (a) waive the document cut off for this
document, and proceed with the Special Session, or (b) cancel the Special
Session. I tend to favor the first approach, but will defer to the sentiment
of the group on this. Any thoughts from the Council on this?
On our call Thursday we noted that we would not want our first exposure to the
CCWG Report was in Marrakesh. Today’s development makes this scenario more
likely. In response, I think we should prepare to repurpose additional
sessions (potentially Sunday, Tuesday and Wednesday) in Morocco for this work.
But we will have a clearer picture next week.
Stay tuned.
Thanks—
J.
From:
<accountability-cross-community-bounces@xxxxxxxxx<mailto:accountability-cross-community-bounces@xxxxxxxxx>>
on behalf of León Felipe Sánchez Ambía
<leonfelipe@xxxxxxxxxx<mailto:leonfelipe@xxxxxxxxxx>>
Date: Friday, February 19, 2016 at 18:19
To: Accountability Cross Community
<accountability-cross-community@xxxxxxxxx<mailto:accountability-cross-community@xxxxxxxxx>>
Cc: "ACCT-Staff (acct-staff@xxxxxxxxx<mailto:acct-staff@xxxxxxxxx>)"
<acct-staff@xxxxxxxxx<mailto:acct-staff@xxxxxxxxx>>
Subject: [CCWG-ACCT] A message from the Co-Chairs
Dear all,
As you are aware, we intended to publish our Final Report today (19 February
2016) for Chartering Organization consideration. We are ready to do so, except
for one issue where we would like to consider options as a full group.
There is, still, ongoing discussion on the issue of thresholds for Board
removal in Recommendation #2, which raised concerns in our report after we came
to a compromise on Board consideration of GAC Advice (Recommendation #11).
Since then, we have tried to propose compromise text that would be acceptable
by different groups (c.f. the 12 February and 17 February drafts, posted at
https://community.icann.org/x/iw2AAw).
We received comments on this issue, and in some cases, minority statements,
from members and participants in the ALAC, GAC, GNSO, and the Board. Earlier
today, ICANN Chairman, Steve Crocker, posted a note, apparently on behalf of
the Icann Board, outlining Board concerns with the latest attempt at compromise
text proposed on 17 February:
http://mm.icann.org/pipermail/accountability-cross-community/2016-February/011056.html.
While these last minute interventions are deeply disappointing for those of us
who worked extremely hard, within the group and within their respective
communities, to build bridges and promote compromise, our main target and duty
remains to achieve a stable level of consensus, respecting the bottom-up,
multistakeholder nature of the process.
It is fortunate that the Board provided this input before we published the
report, since it enables us to assess the potential consequences of a Board
disagreement later in the process.
We believe this issue must be discussed before sending our Final Report to
Chartering Organizations. At the very least, we would like the opportunity to
discuss a way forward and process as full group on next Tuesday’s
CCWG-Accountability call at 06:00 UTC. There are many options and directions
the group can take at this stage, each with different implications and
considerations, and these options should be discussed as a group.
Until the Tuesday call, let’s keep open channels of communication on our
mailing list and work towards a solution. We will also reach out to the
Chartering Organizations to inform them of the change in our schedule.
As co-chairs, we renew our call upon every Member, upon every Participant, our
call upon community leaders especially in the ICANN Board, in the GNSO and in
the GAC to step away from confronting each other, to engage constructively and
recognize each other’s value to the multistakeholder model. If you believe that
the multistakeholder model can deliver, now is the time to act accordingly.
Thank you,
Thomas, León, Mathieu
CCWG-Accountability Co-Chairs
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7303 / Virus Database: 4533/11679 - Release Date: 02/22/16
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|