<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Another fork of the thread.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">"Kleinwächter, Wolfgang"</b> <span dir="ltr"><<a href="mailto:wolfgang.kleinwaechter@medienkomm.uni-halle.de">wolfgang.kleinwaechter@medienkomm.uni-halle.de</a>></span><br>Date: Fri, Mar 27, 2015 at 7:13 AM<br>Subject: Re: [CCWG-ACCT] RES: Cochairs Statement - Istanbul (23-24 March 2015)<br>To: Kieren McCarthy <<a href="mailto:kierenmccarthy@gmail.com">kierenmccarthy@gmail.com</a>>, Jacob Malthouse <<a href="mailto:jacob@bigroom.ca">jacob@bigroom.ca</a>><br>Cc: Accountability Cross Community <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br><br><br>BTW, FIFA and IOC operate under Swiss legislation. Did it help?<br>
<br>
And for historians: The Geneva Option for the A Root Server was discussed within the Framework of the IAHC gTLD MoU (1997).<br>
<br>
<br>
Wolfgang<br>
<br>
<br>
<br>
<br>
-----Ursprüngliche Nachricht-----<br>
Von: <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> im Auftrag von Kieren McCarthy<br>
Gesendet: Fr <a href="tel:27.03.2015%2000" value="+12703201500">27.03.2015 00</a>:42<br>
An: Jacob Malthouse<br>
Cc: Accountability Cross Community<br>
Betreff: Re: [CCWG-ACCT] RES: Cochairs Statement - Istanbul (23-24 March 2015)<br>
<div><div class="h5"><br>
I do get the sense that a jurisdictional discussion is going to be a waste of valuable time at this point, especially when it comes to ICANN.<br>
<br>
<br>
<br>
<br>
There may be good sense in moving an IANA Contract Co. to Geneva at some future point (if that's the way this all goes) but to try to do so now when a transition requires U.S. Government sign off seems reckless and/ or pointless. <br>
<br>
<br>
<br>
<br>
It may be worth shifting to the other coast (Virginia would be pro ICANN) as a way to stop ICANN monkeying around with California law arguments, but with independent legal advice that blocking effort should also disappear.<br>
<br>
<br>
<br>
<br>
But realistically we are going to end up with a U.S. solution. Why bother pretending otherwise?<br>
<br>
<br>
<br>
<br>
I recall the previous two times the community looked at this whole issue. In fact I recall flying around the world and chewing up inordinate amounts of time on it (Geneva, Montevideo, can't remember where else). No one ever believed it would really happen and no one really cared that much either, except maybe the Russians. <br>
<br>
<br>
<br>
<br>
It's navel gazing frankly and I'd rather see more time spent on real accountability measures.<br>
<br>
<br>
<br>
<br>
Kieren<br>
<br>
<br>
<br>
<br>
<br>
<br>
-<br>
[sent through phone]<br>
<br>
On Thu, Mar 26, 2015 at 11:24 AM, Jacob Malthouse <<a href="mailto:jacob@bigroom.ca">jacob@bigroom.ca</a>><br>
wrote:<br>
<br>
> I'm no lawyer, but as a layperson thinking about whether ICANN should stay<br>
> based in California or another jurisdiction, it strikes me that the only<br>
> way to think about this is by considering California law (or attorney<br>
> general's office) as a final accountability mechanism, and by then<br>
> exploring that via a stress test and/or then comparing it to other<br>
> jurisdictions. It makes me wonder if the attorney general of California<br>
> involved in this effort at all? Could they be? Perhaps as part of the<br>
> stress-testing.<br>
> Along those lines, even if you made an IRP binding on all parties, you'd<br>
> still have to explore what happens if an entity to tried to go to court<br>
> regardless, and then where that ends up via the courts.<br>
> I don't have a sense of cost/benefit here, other than California seems to<br>
> have a reputation for having a lot of lawsuits (for better or worse) and<br>
> those lawsuits tend to be expensive - though maybe not more so than<br>
> anywhere else in the USA - so it gets back to the question of whether we<br>
> have an accessible redress mechanism if ICANN is based in California vs<br>
> elsewhere in the USA vs elsewhere.<br>
> Looking at the litigation documents page, it looks like ICANN has been sued<br>
> pretty much all over the USA (<br>
> <a href="https://www.icann.org/resources/pages/governance/litigation-en" target="_blank">https://www.icann.org/resources/pages/governance/litigation-en</a>), which<br>
> might be seen as a reason to keep it based in the US, as over time the<br>
> precedents should help provide an additional layer of security against<br>
> improper lawsuits, whereas if you move it you'd be starting from scratch<br>
> presumably.<br>
> Best, Jacob.<br>
> Jacob Malthouse<br>
> Co-founder & Director, Big Room Inc.<br>
> <a href="tel:778-960-6527" value="+17789606527">778-960-6527</a><br>
> <a href="http://www.bigroom.ca" target="_blank">www.bigroom.ca</a><br>
> On 26 March 2015 at 09:48, Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>> wrote:<br>
>> Phil,<br>
>><br>
</div></div>>> That is not old ground, but rather ground we are now working diligently..<br>
<span class="">>><br>
>> The CCWG discussed how to bring all 4 AoC reviews into the bylaws this<br>
>> week in Istanbul. The 5th draft proposal is here<br>
</span>>> <<a href="https://community.icann.org/download/attachments/52888421/Draft%201-%20AoC%20Accountability%20Mechanisms%20%5BSteve%20v5%5D.pdf?version=1&modificationDate=1425509039000&api=v2" target="_blank">https://community.icann.org/download/attachments/52888421/Draft%201-%20AoC%20Accountability%20Mechanisms%20%5BSteve%20v5%5D.pdf?version=1&modificationDate=1425509039000&api=v2</a>>,<br>
<span class="">>> and I will update soon with suggestions that surfaced this week.<br>
>><br>
>> The AoC is presently in full effect, so Review 9.3 will begin this year<br>
>> and staff is planning for it. You should count on that review beginning<br>
>> soon.<br>
>><br>
>> As for registries disclosing wholesale prices, I think you know that an<br>
</span>>> independent group would compile that data *without* identifying the<br>
>> registry.<br>
<div><div class="h5">>><br>
>> -<br>
>> Steve<br>
>><br>
>> From: Phil Buckingham<br>
>> Date: Thursday, March 26, 2015 at 12:35 PM<br>
>> To: Steve DelBianco, 'Jordan Carter', 'Greg Shatan'<br>
>> Cc: 'Accountability Cross Community'<br>
>> Subject: RE: [CCWG-ACCT] RES: Cochairs Statement - Istanbul (23-24 March<br>
>> 2015)<br>
>><br>
>> Steve,<br>
>><br>
>><br>
>><br>
>> I am sorry I'm playing catch up, having not been in Istanbul.<br>
>><br>
>><br>
>><br>
>> So what is the status on the AOC requirements, particular regarding 9.3 (<br>
>> I think) - the review of Round 1 of the gTLD programme.<br>
>><br>
>><br>
>><br>
>> As I am sure you are aware, as a fellow partipicant on the Implementation<br>
>> Advisory Group , Consumer Choice , Consumer Trust and Competition , that<br>
>> yesterday ICANN announced that a company had been selected to conduct<br>
>> (two) economic studies, to start immediately.<br>
>><br>
>> The implications are huge for the new TLD Registries as they will have to<br>
>> disclose internal pricing of registrations and, quite frankly, most are not<br>
>> operationally ready.<br>
>><br>
>><br>
>><br>
>> One assumes that 9.3 would be an automatic transfer into the expanded<br>
>> ICANN bylaws.<br>
>><br>
>><br>
>><br>
>> Sorry, if I am going over old ground, already agreed in Istanbul.<br>
>><br>
>><br>
>><br>
>> Regards,<br>
>><br>
>><br>
>><br>
>> Phil<br>
>><br>
>><br>
>><br>
>> Phil Buckingham<br>
>><br>
>> CEO, Dot Advice Limited<br>
>><br>
>><br>
>><br>
>><br>
>><br>
</div></div>>> *From:* <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> [<br>
>> mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><br>
>> <<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>>] *On Behalf Of *Steve<br>
>> DelBianco<br>
>> *Sent:* 26 March 2015 15:13<br>
>> *To:* Jordan Carter; Greg Shatan<br>
>> *Cc:* Accountability Cross Community<br>
>> *Subject:* Re: [CCWG-ACCT] RES: Cochairs Statement - Istanbul (23-24<br>
<span class="">>> March 2015)<br>
>><br>
>><br>
>><br>
>> Keep in mind that either ICANN or NTIA may cancel the AoC<br>
</span>>> <<a href="https://www.icann.org/resources/pages/affirmation-of-commitments-2009-09-30-en?routing_type=path" target="_blank">https://www.icann.org/resources/pages/affirmation-of-commitments-2009-09-30-en?routing_type=path</a>><br>
<span class="">>> with just 120 days notice. That's why we created Stress Test #14, which<br>
</span>>> suggests the need to bring AoC commitments and Reviews into ICANN Bylaws..<br>
>><br>
>><br>
>><br>
>> *Stress Test #14: *ICANN or NTIA choose to terminate the Affirmation of<br>
<span class="">>> Commitments. (AoC) ICANN would no longer be held to its Affirmation<br>
>> commitments, including the conduct of community reviews and required<br>
>> implementation of review team recommendations.<br>
>><br>
>><br>
>><br>
</span>>> *Existing Accountability Measures:*<br>
<span class="">>><br>
>> The AoC can be terminated by either ICANN or NTIA with 120 days notice.<br>
>><br>
>> As long as NTIA controls the IANA contract, ICANN feels pressure to<br>
>> maintain the AoC.<br>
>><br>
>> But as a result of IANA stewardship transition, ICANN would no longer have<br>
>> the IANA contract as external pressure from NTIA to maintain the AoC .<br>
>><br>
>><br>
>><br>
</span>>> *Proposed Accountability Measures:*<br>
<span class="">>><br>
>> One proposed mechanism is community challenge to a board decision, such<br>
>> as referral to an Independent Review Panel (IRP) with the power to issue a<br>
>> binding decision. If ICANN canceled the AoC, the IRP mechanism could<br>
>> enable reversal of that decision.<br>
>><br>
>><br>
>><br>
>> Another proposed measure is to import AoC provisions into the ICANN<br>
>> bylaws, and dispense with the bilateral AoC with NTIA. Bylaws would be<br>
>> amended to include AoC commitments 3, 4, 7, and 8, plus the 4 periodic<br>
>> reviews required in paragraph 9, or other provisions that are deemed<br>
>> essential by the community.<br>
>><br>
>><br>
>><br>
>> If ICANN's board proposed to amend the AoC provisions added to the bylaws,<br>
>> another proposed measure would empower the community to veto that proposed<br>
>> bylaws change.<br>
>><br>
>><br>
>><br>
>> See all stress tests here<br>
</span>>> <<a href="https://community.icann.org/download/attachments/52232556/Applying%20Stress%20Tests%20%5BDraft%20v8%5D.pdf?version=1&modificationDate=1426877855000&api=v2" target="_blank">https://community.icann.org/download/attachments/52232556/Applying%20Stress%20Tests%20%5BDraft%20v8%5D.pdf?version=1&modificationDate=1426877855000&api=v2</a>><br>
<span class="">>> .<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> -<br>
>><br>
>> Steve DelBianco<br>
>><br>
>> Executive Director<br>
>><br>
>> NetChoice<br>
>><br>
</span>>> <a href="http://www.NetChoice.org" target="_blank">http://www.NetChoice.org</a> <<a href="http://www.netchoice.org/" target="_blank">http://www.netchoice.org/</a>> and<br>
>> <a href="http://blog.netchoice.org" target="_blank">http://blog.netchoice.org</a><br>
>><br>
>> <a href="tel:%2B1.703.615.6206" value="+17036156206">+1.703.615.6206</a><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> *From: *Jordan Carter<br>
>> *Date: *Thursday, March 26, 2015 at 10:37 AM<br>
>> *To: *Greg Shatan<br>
>> *Cc: *Accountability Cross Community<br>
>> *Subject: *Re: [CCWG-ACCT] RES: Cochairs Statement - Istanbul (23-24<br>
<div><div class="h5">>> March 2015)<br>
>><br>
>><br>
>><br>
>> Thanks Greg, Phil.<br>
>><br>
>><br>
>><br>
>> I am confident we are aware in the CCWG that we can't unilaterally amend<br>
>> the AOC. However, it is also clear that we can choose which bits we propose<br>
>> to incorporate in the ICANN Bylaws. Not incorporating some bits has no<br>
>> effect on the existing agreement between ICANN and the United States<br>
>> government.<br>
>><br>
>><br>
>><br>
>> I would note that in respect of the jurisdiction conversation, we have a<br>
>> multistakeholder process at work in designing this transition.<br>
>><br>
>><br>
>><br>
>> If the question of a "sealed for all time" jurisdiction question derails<br>
>> the transition - either by meaning the community can't accept ICANN being<br>
>> locked in California forever and thus declines to agree a transition, or<br>
>> the United States not accepting a transition that doesn't include that lock<br>
>> - then that will be the outcome of the multistakeholder process. The NTIA<br>
>> did not define perpetual U.S. presence as a requirement for the transition,<br>
>> after all.<br>
>><br>
>><br>
>><br>
>> Certainly I hope that this dilemma does not prove to be a breakdown point.<br>
>><br>
>><br>
>><br>
>> I say all the above as an individual who thinks the California<br>
>> jurisdiction works just fine for everything we need to do now, and can<br>
>> foresee for the future.<br>
>><br>
>><br>
>><br>
>> best,<br>
>><br>
>> Jordan<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On 26 March 2015 at 16:26, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>> wrote:<br>
>><br>
>> I second Phil's email and hope that some clarity can be brought to those<br>
>> unable to participate in the entire CCWG meeting.<br>
>><br>
>><br>
>><br>
>> I also want to remind the CCWG that ICANN cannot unilaterally amend the<br>
>> Affirmation of Commitments. The AoC can only be amended by mutual consent<br>
>> of the parties. The U.S. jurisdictional requirement will be there until<br>
>> amended by the parties, or the AoC is terminated. If we want to get into<br>
>> discussing terminating the AoC, that is a whole other discussion, and an<br>
>> immense step to consider.<br>
>><br>
>><br>
>><br>
>> Greg Shatan<br>
>><br>
>><br>
>><br>
>> On Thu, Mar 26, 2015 at 10:08 AM, Phil Corwin <<a href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a>> wrote:<br>
>><br>
>> I see from the post below that this issue of ICANN's future jurisdiction<br>
>> has become "a most delicate matter" and remains unresolved and subject to<br>
>> further discussion within the CCWG.<br>
>><br>
>><br>
>><br>
>> This is a pivotal and very important issue, as the accountability<br>
>> mechanisms are being designed (with the assistance of two outside law<br>
>> firms) to be consistent with California law and may not operate effectively<br>
>> within another legal jurisdiction context. Further, if there is not a<br>
>> commitment to remain within US jurisdiction for the foreseeable future (as<br>
>> CEO Chehade pledged in Congressional testimony last month) it will raise<br>
>> significant political barriers to NTIA approval of and Congressional<br>
>> acquiescence to a final transition and accountability package.<br>
>><br>
>><br>
>><br>
>> For those of us unable to participate remotely in all the CCWG discussions<br>
>> earlier this week, it would be most appreciated if more specificity could<br>
>> be provided as soon as possible as to what the various perspectives are on<br>
>> this matter and how it is proposed to resolve them, since the final<br>
>> determination would seem to be a rather binary decision - either the AOC<br>
>> provision committing to US jurisdiction is incorporated within the Bylaws,<br>
>> or it is not.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
</div></div>>> *Philip S. Corwin, Founding Principal*<br>
>><br>
>> *Virtualaw LLC*<br>
>><br>
>> *1155 F Street, NW*<br>
>><br>
>> *Suite 1050*<br>
>><br>
>> *Washington, DC 20004*<br>
>><br>
>> *<a href="tel:202-559-8597" value="+12025598597">202-559-8597</a> <<a href="tel:202-559-8597" value="+12025598597">202-559-8597</a>>/Direct*<br>
>><br>
>> *<a href="tel:202-559-8750" value="+12025598750">202-559-8750</a> <<a href="tel:202-559-8750" value="+12025598750">202-559-8750</a>>/Fax*<br>
>><br>
>> *<a href="tel:202-255-6172" value="+12022556172">202-255-6172</a> <<a href="tel:202-255-6172" value="+12022556172">202-255-6172</a>>/cell*<br>
>><br>
>><br>
>><br>
>> *Twitter: @VlawDC*<br>
>><br>
>><br>
>><br>
>> *"Luck is the residue of design" -- Branch Rickey*<br>
>><br>
>><br>
>><br>
>> *From:* <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> [mailto:<br>
>> <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>] *On Behalf Of *Thomas<br>
>> Rickert<br>
>> *Sent:* Thursday, March 26, 2015 6:22 AM<br>
>> *To:* Pedro Ivo Ferraz da Silva<br>
>> *Cc:* Accountability Cross Community<br>
>> *Subject:* Re: [CCWG-ACCT] RES: Cochairs Statement - Istanbul (23-24<br>
<span class="">>> March 2015)<br>
>><br>
>><br>
>><br>
>> Dear Pedro,<br>
>><br>
>> you are correct. We should have mentioned that we discussed it. As this is<br>
>> a most delicate matter and since we agree we would suggest language to<br>
>> frame the next steps (you will remember we had not agreed on concrete<br>
>> language), I suggest we use the next upcoming opportunity to share the<br>
>> progress with the community when we have an agreed language on the matter.<br>
>><br>
>><br>
>><br>
>> Thanks for your understanding and for your thoughtful contributions during<br>
>> the meeting.<br>
>><br>
>><br>
>><br>
>> Best,<br>
>><br>
>> Thomas<br>
>><br>
>><br>
>><br>
>> Am 26.03.2015 um 11:17 schrieb Pedro Ivo Ferraz da Silva <<br>
>> <a href="mailto:pedro.ivo@itamaraty.gov.br">pedro.ivo@itamaraty.gov.br</a>>:<br>
>><br>
>><br>
>><br>
>> Dear Alice, CCWG-colleagues,<br>
>><br>
>><br>
>><br>
>> Thanks for the links. I just regret the fact that the CoChairs have missed<br>
>> to refer to the important debate the CCWG has held with respect to the way<br>
>> moving forward on the issue of jurisdiction. As Mathieu Weill mentioned<br>
>> during the second day, this is one of the main issues of concern of<br>
>> individuals outside this group and I believe the community deserved at<br>
>> least to be briefly informed about this subject.<br>
>><br>
>><br>
>><br>
>> Regards,<br>
>><br>
>><br>
>><br>
>> Pedro<br>
>><br>
>><br>
</span>>> ------------------------------<br>
>><br>
>> *De:* <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> [<br>
<span class="">>> <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>] em nome de Alice Jansen<br>
>> [<a href="mailto:alice.jansen@icann.org">alice.jansen@icann.org</a>]<br>
</span>>> *Enviado:* quarta-feira, 25 de março de 2015 12:13<br>
>> *Para:* <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><br>
>> *Assunto:* [CCWG-ACCT] Cochairs Statement - Istanbul (23-24 March 2015)<br>
<span class="">>> Dear all,<br>
>><br>
>> This is to inform you that the CoChairs statement (pasted below) may be<br>
>> found at: <a href="https://www.icann.org/news/announcement-2015-03-25-en" target="_blank">https://www.icann.org/news/announcement-2015-03-25-en</a><br>
>><br>
>> A video interview with CoChair Thomas Rickert is also available - see:<br>
>> <a href="https://www.youtube.com/watch?v=vVof6v0MguE" target="_blank">https://www.youtube.com/watch?v=vVof6v0MguE</a><br>
>><br>
>> These links will be added to your wiki pages.<br>
>><br>
>> Thanks,<br>
>><br>
>> Best regards<br>
>><br>
>> Alice<br>
>><br>
>><br>
>> CCWG-Accountability Co-Chairs Statement Istanbul, 25 March 2015 | Thomas<br>
>> Rickert, León Sánchez & Mathieu Weill<br>
>><br>
>> Members and participants of the Cross Community Working Group on<br>
>> Enhancing ICANN Accountability (CCWG-Accountability)<br>
</span>>> <<a href="https://community.icann.org/display/acctcrosscomm/CCWG+on+Enhancing+ICANN+Accountability" target="_blank">https://community.icann.org/display/acctcrosscomm/CCWG+on+Enhancing+ICANN+Accountability</a>> met<br>
<span class="">>> in Istanbul, Turkey, on 23-24 March 2015.<br>
>><br>
>> The meeting<br>
</span>>> <<a href="https://community.icann.org/pages/viewpage.action?pageId=52890276" target="_blank">https://community.icann.org/pages/viewpage.action?pageId=52890276</a>> was<br>
<span class="">>> attended in-person by 42 members and participants. A number of participants<br>
</span>>> and observers joined the meeting remotely using the virtual meeting room..<br>
>> Three Advisors<br>
>> <<a href="https://community.icann.org/display/acctcrosscomm/Advisors" target="_blank">https://community.icann.org/display/acctcrosscomm/Advisors</a>> also<br>
<span class="">>> participated.<br>
>><br>
>> Guided by the four basic building blocks<br>
</span>>> <<a href="https://community.icann.org/display/acctcrosscomm/Building+Blocks" target="_blank">https://community.icann.org/display/acctcrosscomm/Building+Blocks</a>> identified<br>
<span class="">>> at ICANN 52 in Singapore, the group further discussed and refined<br>
>> accountability mechanisms that need to be either implemented or, at least,<br>
>> committed to before the transition of the IANA stewardship can take place.<br>
>><br>
>> The meeting made progress on three main areas:<br>
>><br>
>> · Enhancing ICANN's Mission and Core Values;<br>
>><br>
>> · Strengthening the existing independent review process;<br>
>><br>
>> · Mechanisms for community empowerment.<br>
>><br>
>> Specifically, the group discussed changes that should be made to the<br>
>> Mission and Core Values inICANN's Bylaws. For example, the group discussed<br>
>> how key provisions of the Affirmation of Commitments<br>
</span>>> <<a href="https://www.icann.org/en/about/agreements/aoc/affirmation-of-commitments-30sep09-en.htm" target="_blank">https://www.icann.org/en/about/agreements/aoc/affirmation-of-commitments-30sep09-en.htm</a>> (AoC)<br>
<div><div class="h5">>> could be reflected into the Bylaws.<br>
>><br>
>> Additionally, the group worked on strengthening the existing independent<br>
>> review process suggesting improvements to its accessibility and<br>
>> affordability, and discussed process design including establishment of a<br>
>> standing panel with binding outcomes and panel composition (diversity<br>
>> etc.). The IRP panel decisions would be guided by ICANN's Mission and Core<br>
>> Values.<br>
>><br>
>> With regards to mechanisms for community empowerment, the group identified<br>
>> powers and associated mechanisms including the ability to:<br>
>><br>
>> · recall the ICANN Board of Directors;<br>
>><br>
>> · approve or prevent changes to the ICANN Bylaws, Mission and<br>
>> Core Values;<br>
>><br>
>> · reject Board decisions on Strategic Plan and budget, where the<br>
>> Board has failed to appropriately consider community input.<br>
>><br>
>> The CCWG-Accountability supported the concept of a Fundamental Bylaw that<br>
>> would provide additional robustness to key provisions. The Fundamental<br>
>> Bylaw would apply to:<br>
>><br>
>> · the mission;<br>
>><br>
>> · the independent review process;<br>
>><br>
>> · the power to veto Bylaw changes;<br>
>><br>
>> · new community powers such as recall of the Board and the right<br>
>> of the community to veto certain Board actions.<br>
>><br>
>> Changes to the Fundamental Bylaws would require high standards for<br>
>> approval by the community.<br>
>><br>
>> The notion of an empowered community involved discussion of community<br>
>> representation, i.e. who constitutes the community. The<br>
>> CCWG-Accountability is also aware that to wield these new powers, the<br>
>> community, however it is constituted, must itself meet high standards of<br>
>> accountability. ICANN's accountability would also be enhanced by ensuring<br>
>> its operations and processes are more globally inclusive.<br>
>><br>
>> The group has engaged two law firms to provide independent legal advice<br>
>> and confirm feasibility of the suggested frameworks. The firms are Adler &<br>
>> Colvin and Sidley & Austin.<br>
>><br>
>> As work progresses, all recommendations will be subject to the stress<br>
>> tests against contingencies already identified. The stress test methodology<br>
</div></div>>> has been successfully tested against the draft accountability mechanisms..<br>
<span class="">>><br>
>> The CCWG-Accountability is confident that their proposed mechanisms will<br>
>> satisfy the needs of the CWG-Stewardship1<br>
</span>>> <<a href="https://www.icann.org/news/announcement-2015-03-25-en#_ftn1" target="_blank">https://www.icann.org/news/announcement-2015-03-25-en#_ftn1</a>> as they<br>
<span class="">>> look to stronger accountability protections. The CCWG-Accountability and<br>
>> CWG-Stewardship Co-Chairs met to update and fully brief each other on the<br>
>> progress made so far. They outlined key areas of accountability that the<br>
>> CCWG-Accountability Co-Chairs considered are most relevant for the current<br>
>> and ongoing work of the CWG-Stewardship. The CCWG-Accountability Co-Chairs<br>
>> will brief the CWG-Stewardship in the opening part of their face-to-face<br>
>> meeting on Thursday, 26 March.<br>
>><br>
</span>>> *Next Steps:*<br>
<span class="">>><br>
>> The CCWG-Accountability will continue refining its recommendations. The<br>
>> community is expected to provide feedback during a public comment period to<br>
>> be held before ICANN 53, Buenos Aires meeting. The results of the public<br>
>> comment period will inform further deliberations during that meeting.<br>
>><br>
>> The group is developing an engagement plan to ensure its proposals are<br>
>> widely known and understood, and to encourage comprehensive response to<br>
>> proposals during the public comment period.<br>
>><br>
>> The CCWG-Accountability Co-Chairs recognize the outstanding volunteer work<br>
>> that has produced these substantive proposals in a very short period of<br>
>> time. The community's effort has been exceptional.<br>
>><br>
</span>>> *About the CCWG-Accountability*<br>
<span class="">>><br>
>> The CCWG-Accountability was established to ensure that ICANN's<br>
>> accountability and transparency commitments to the global Internet<br>
>> community are maintained and enhanced in the absence of the historical<br>
>> relationship with the U.S. Government.<br>
>><br>
>> The group has divided its work into two work streams (WS):<br>
>><br>
>> · WS1 is focused on identifying mechanisms<br>
>> enhancing ICANN accountability that must be in place or committed to within<br>
>> the timeframe of the IANA Stewardship Transition;<br>
>><br>
>> · WS2 is focused on addressing accountability topics for which a<br>
>> timeline for developing solutions and full implementation may extend beyond<br>
>> the IANA Stewardship Transition.<br>
>><br>
>> The CCWG-Accountability consists of 177 people<br>
</span>>> <<a href="https://community.icann.org/pages/viewpage.action?pageId=50823970" target="_blank">https://community.icann.org/pages/viewpage.action?pageId=50823970</a>>,<br>
>> organized as 26 members<br>
>> <<a href="https://community.icann.org/pages/viewpage.action?pageId=50823968" target="_blank">https://community.icann.org/pages/viewpage.action?pageId=50823968</a>>,<br>
<span class="">>> appointed by and accountable to chartering organizations, 151 participants<br>
</span>>> <<a href="https://community.icann.org/pages/viewpage.action?pageId=50823968" target="_blank">https://community.icann.org/pages/viewpage.action?pageId=50823968</a>>, who<br>
<span class="">>> participate as individuals, and 46 mailing list observers<br>
</span>>> <<a href="https://community.icann.org/display/acctcrosscomm/Mailing+List+Observers" target="_blank">https://community.icann.org/display/acctcrosscomm/Mailing+List+Observers</a>>.<br>
<span class="">>> The group also includes one ICANN Board liaison, one ICANN staff<br>
>> representative, and one former ATRT member who serves as a liaison. In<br>
>> addition, there are 4 ICG members who participate in the<br>
>> CCWG-Accountability, including two who serve as liaisons between the two<br>
>> groups.<br>
</span>>> Seven Advisors <<a href="https://www.icann.org/news/announcement-2014-12-17-en" target="_blank">https://www.icann.org/news/announcement-2014-12-17-en</a>> have<br>
<span class="">>> also been appointed to contribute research and advice, and to bring<br>
>> perspectives on global best practices to enrich the CCWG-Accountability<br>
>> discussion.<br>
>> The CCWG-Accountability is an open group: anyone interested in the work of<br>
>> the CCWG-Accountability, can join as a participant or observers.<br>
>> Participants or observers may be from a chartering organization, from a<br>
>> stakeholder group or organization not represented in the<br>
>> CCWG-Accountability or currently active within ICANN, or self-appointed.<br>
>><br>
>> For more information on the CCWG-Accountability or to view meeting<br>
>> archives and draft documents, please refer to their dedicated wiki<br>
</span>>> <<a href="https://community.icann.org/display/acctcrosscomm/CCWG+on+Enhancing+ICANN+Accountability" target="_blank">https://community.icann.org/display/acctcrosscomm/CCWG+on+Enhancing+ICANN+Accountability</a>><br>
<span class="">>> .<br>
>><br>
>> A video interview with CCWG-Accountability Co-Chair Thomas Rickert can be<br>
</span>>> seen here <<a href="https://www.youtube.com/watch?v=vVof6v0MguE" target="_blank">https://www.youtube.com/watch?v=vVof6v0MguE</a>>.<br>
>> ------------------------------<br>
>><br>
>> 1 <<a href="https://www.icann.org/news/announcement-2015-03-25-en#_ftnref1" target="_blank">https://www.icann.org/news/announcement-2015-03-25-en#_ftnref1</a>> Cross<br>
<span class="">>> Community Working Group (CWG) to Develop an IANA Stewardship Transition<br>
>> Proposal on Naming Related Functions<br>
>><br>
>> _______________________________________________<br>
>> Accountability-Cross-Community mailing list<br>
>> <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
>> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
>><br>
>><br>
</span>>> ------------------------------<br>
<span class="">>><br>
>> No virus found in this message.<br>
>> Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br>
>> Version: 2015.0.5751 / Virus Database: 4306/9294 - Release Date: 03/13/15<br>
>> Internal Virus Database is out of date.<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Accountability-Cross-Community mailing list<br>
>> <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
>> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Accountability-Cross-Community mailing list<br>
>> <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
>> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Jordan Carter<br>
>><br>
>> Chief Executive<br>
</span>>> *InternetNZ*<br>
<span class="">>><br>
>> 04 495 2118 (office) | <a href="tel:%2B64%2021%20442%20649" value="+6421442649">+64 21 442 649</a> (mob)<br>
>> <a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a><br>
>> Skype: jordancarter<br>
>><br>
</span>>> *A better world through a better Internet *<br>
<div class="HOEnZb"><div class="h5">>><br>
>> _______________________________________________<br>
>> Accountability-Cross-Community mailing list<br>
>> <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
>> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
>><br>
>><br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</div></div></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#17365d">Gregory S. Shatan </span></b><b><span style="font-size:8.0pt;font-family:Symbol;color:#17365d">ï</span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#17365d"> </span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#c0504d">Abelman
Frayne & Schwab</span></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#365f91">Partner</span></b><span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#4f81bd"> </span></b></span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#4f81bd">| IP |
Technology | Media | Internet</span></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#17365d">666 Third Avenue | New York, NY 10017-5621</span></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Direct</span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> <span> </span></span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-885-9253<span> </span><b>|<span> </span></b></span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Main</span></b><span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> </span></span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-949-9022</span><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Fax</span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> <span> </span></span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-949-9190<span> </span><b>|</b><span> </span></span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Cell<span> </span></span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">917-816-6428</span><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><i><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"><a href="mailto:gsshatan@lawabel.com" target="_blank">gsshatan@lawabel.com</a></span></i></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">ICANN-related:<span> </span><i><a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a></i></span></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><i><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"><a href="http://www.lawabel.com/" target="_blank">www.lawabel.com</a></span></i></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p></div></div>
</div>