[CCWG-ACCT] RES: [Blog] Launching Work Stream 2 in Helsinki

Thu Jun 23 15:59:21 UTC 2016

The agenda link is showing up as a "mailto" link (i.e., clicking it opens
up an email,not the agenda).  This should be fixed.  The document can be
found at https://community.icann.org/pages/viewpage.action?pageId=59643308

There is still no breakdown of which Lightning Talks may strike when.  This
would be good to have even if it could change.

Greg

On Thu, Jun 23, 2016 at 11:46 AM, Thomas Rickert <thomas at rickert.net> wrote:

> All,
> We have asked for the language in the footnote to be aligned with the
> language of the report. We apologize for not being precise. It was not our
> intention to jump the gun and predetermine the outcome of our discussions.
>
> Best,
> Thomas
>
> Am 23.06.2016 um 17:25 schrieb Pedro Ivo Ferraz da Silva <
> pedro.ivo at itamaraty.gov.br>:
>
> Dear all,
>
>
>
> In the same vein as our colleagues below, I am having a hard time in
> identifying in our WS1 report any statement that leads to the conclusion
> put forth by our co-Chairs.
>
>
>
> In our report (annex 12, attached for reference), we have agreed that:
>
>
>
> ·         Jurisdiction is a multi-layered issue (para. 29);
>
> ·         The main issues that need to be investigated within Work Stream
> 2 relate to the influence that ICANN´s existing jurisdiction may have on
> the actual operation of policies and accountability mechanisms (para. 30);
> and
>
> ·         This refers *primarily* to the process for the settlement of
> disputes within ICANN, involving the choice of jurisdiction and of the
> applicable laws, but *not necessarily* the location where ICANN is
> incorporated (para. 30)
>
>
>
> Although the last sentence puts a focus on settlement of disputes, it does
> by no means exclude other subjects from WS2 discussion (that is why the
> adverb "primarily" was used). Moreover, it is clear that although the same
> sentence indicates that the location where ICANN is incorporated may not be
> essential, it is an issue that should not be neglected (that is why "not
> necessarily" was used).
>
>
>
> Finally, I can't even find any textual reference in the WS1 report that
> would hint at the conclusion "Expanding the list of jurisdictions
> identified in ICANN’s contracts".
>
>
>
> That being said, I find it very unfortunate that our co-Chairs jump into
> conclusions that do not find a basis in our report and otherwise have not
> been discussed  within the CCWG (either F2F or in the list). Hopefully our
> meeting this Sunday will allow us to have that discussion and agree on
> statements to be then properly conveyed to the community as a truly CCWG
> consensus.
>
>
>
> Regards,
>
>
>
> Secretário Pedro Ivo Ferraz da Silva
>
> Divisão da Sociedade da Informação (DI)
>
> Ministério das Relações Exteriores - Brasil
>
> T: + 55 61 2030-6609
>
>
>
> Secretary Pedro Ivo Ferraz da Silva
>
> Division of Information Society (DI)
>
> Ministry of External Relations - Brazil
>
> T: + 55 61 2030-6609
>
>
>
>
>
>
>
> -----Mensagem original-----
> De: accountability-cross-community-bounces at icann.org [
> mailto:accountability-cross-community-bounces at icann.org
> <accountability-cross-community-bounces at icann.org>] Em nome de
> Jorge.Cancio at bakom.admin.ch
> Enviada em: quinta-feira, 23 de junho de 2016 12:16
> Para: gurcharya at gmail.com
> Cc: accountability-cross-community at icann.org
> Assunto: Re: [CCWG-ACCT] [Blog] Launching Work Stream 2 in Helsinki
>
>
>
> +1
>
>
>
> Von meinem iPhone gesendet
>
>
>
> Am 23.06.2016 um 16:44 schrieb Guru Acharya <
> gurcharya at gmail.com<mailto:gurcharya at gmail.com>>:
>
>
>
> Hi,
>
>
>
> I am confused anout the scoping of WS2 on jurisdiction. Request you to
> point me to the transcripts where it was decided that "ICANN's
> jurisdiction, place of incorporation and headquarters location are not
> within the scope of Work Stream 2 deliberations."
>
>
>
> On Thursday, 23 June 2016, Hillary Jett <
> hillary.jett at icann.org<mailto:hillary.jett at icann.org>> wrote:
>
> All,
>
>
>
> Please find below the pre-ICANN56 meeting blog from the co-Chairs.
>
>
>
> Thanks,
>
> Hillary
>
>
>
> Original link:
> https://www.icann.org/news/blog/launching-work-stream-2-in-helsinki
>
>
>
> Launching Work Stream 2 in Helsinki
>
>
>
> It has been a momentous month for the ICANN community. On behalf of the
> Cross Community Working Group on Enhancing ICANN Accountability
> (CCWG-Accountability), we welcome the U.S. Government report<
> https://www.ntia.doc.gov/report/2016/iana-stewardship-transition-proposal-assessment-report>
> that our recommendations meet their requirements. We are actively engaged
> in the prep work needed for a timely implementation of these new
> accountability mechanisms into ICANN’s ecosystem.
>
>
>
> Looking ahead, our ongoing work to advance ICANN’s accountability is not
> complete. The CCWG-Accountability identified nine additional areas where
> community, staff and Board accountability can be improved. These target
> areas, recognized as Work Stream 2, are outlined in Recommendation #12<
> https://community.icann.org/pages/viewpage.action?pageId=58723723&preview=/58723723/58725532/Annex%2012%20-%20FINAL.pdf>
> of the Work Stream 1 Report.
>
>
>
> To launch Work Stream 2, the CCWG-Accountability will be holding a
> full-day face-to-face meeting in Helsinki on the Sunday before ICANN56 (26
> June 2016). All Work Stream 2 topics<
> https://community.icann.org/pages/viewpage.action?pageId=58723723&preview=/58723723/58725532/Annex%2012%20-%20FINAL.pdf>
> will be covered during the session. The full agenda can be found
> here<javascript:_e(%7B%7D,'cvml','https://community.icann.org/x/rBWOAw'
> );>.
>
>
>
> The topics that will be discussed are:
>
> •         Additional transparency considerations
>
> •         Diversity across ICANN
>
> •         Clarifying the lines of accountability for ICANN staff
>
> •         A work plan to enhance accountability of Supporting
> Organizations and Advisory Committees
>
> •         A Framework of Interpretation on respecting human rights within
> ICANN’s limited mission and scope
>
> •         Expanding the list of jurisdictions identified in ICANN’s
> contracts, for purposes of resolving contractual disputes [1]<
> https://www.icann.org/news/blog/launching-work-stream-2-in-helsinki#_ftn1>
>
> •         Role and function of the Ombudsman
>
> •         Guidelines for good faith conduct in ICANN Board member removal
> discussions
>
> •         Engagement process between a complainant and ICANN prior to an
> Independent Review Process
>
>
>
> We encourage all members, participants and interested observers that are
> not attending ICANN56 to follow along with our discussions via our Adobe
> Room<https://icann.adobeconnect.com/hel56-halla>. In addition, we will be
> circulating notes on each of the topics to the publicly archived<
> http://mm.icann.org/pipermail/accountability-cross-community/>
> CCWG-Accountability mailing list to serve as the base of our discussions
> moving forward.
>
>
>
> If you are interested in debating these Work Stream 2 topics and want to
> become a participant or observer of the CCWG-Accountability, please send an
> email to
> acct-staff at icann.org<javascript:_e(%7B%7D,'cvml','acct-staff at icann.org')
> <acct-staff at icann.org%3cjavascript:_e(%7B%7D,'cvml','acct-staff at icann.org')>
> ;>.
>
>
>
> For those of you who will be joining us in Helsinki, safe travels and we
> look forward to seeing you soon!
>
>
>
>
>
> CCWG-Accountability co-Chairs,
>
>
>
> Thomas Rickert, León Sanchez, Mathieu Weill
>
>
>
> ________________________________
>
>
>
> [1]<
> https://www.icann.org/news/blog/launching-work-stream-2-in-helsinki#_ftnref1>
> ICANN's jurisdiction, place of incorporation and headquarters location are
> not within the scope of Work Stream 2 deliberations.
>
>
>
> _______________________________________________
>
> 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
>
> _______________________________________________
>
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
>
> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>
> <Annex 12 - FINAL-Revised.pdf>
>
> _______________________________________________
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>
>
> _______________________________________________
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20160623/5c13f6bc/attachment.html>