- cc-humanrights - lists.icann.org

Re: [cc-humanrights] cc-humanrights Digest, Vol 19, Issue 1
by Corinne Cath June 1, 2016

June 1, 2016

Dear all, Thanks for sharing this Niels. It is really great and the artist has clearly listened to our concerns (and compliments). The end result is stunning. Best, On Wed, Jun 1, 2016 at 5:16 PM, <cc-humanrights-request(a)icann.org> wrote: > Send cc-humanrights mailing list submissions to > cc-humanrights(a)icann.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mm.icann.org/mailman/listinfo/cc-humanrights > or, via email, send a message with subject or body 'help' to > cc-humanrights-request(a)icann.org > > You can reach the person managing the list at > cc-humanrights-owner(a)icann.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cc-humanrights digest..." > > > Today's Topics: > > 1. infographic ICANN & Human Rights v0.3 pls comment > (Niels ten Oever) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 1 Jun 2016 18:16:02 +0200 > From: Niels ten Oever <niels(a)article19.org> > To: Human Rights <cc-humanrights(a)icann.org> > Subject: [cc-humanrights] infographic ICANN & Human Rights v0.3 pls > comment > Message-ID: <574F0A42.1070103(a)article19.org> > Content-Type: text/plain; charset="utf-8" > > Dear all, > > Please find a new version of the vizualization of ICANN and Human Rights > based on all your great inputs. > > The fact that this draft got several really good discussions going here > gives me high hopes for what this can do outside of this mailinglist! > > Please comment again to make it even better! > > Cheers, > > Niels > > PS Avri, it would be really great if you have the time to propose text > for the AGB points you made. >

2 1

Fwd: FW: ICANN and Human Rights meeting in Helsinki
by Niels ten Oever May 30, 2016

May 30, 2016

Dear all, We did not get a meeting slot for the CCWP HR in Helsinki. So we could present out work (very shortly) in the joint meeting with the GAC WG HRIL, which is only 45 minutes in total, or we could think of other possibilities. Any thoughts? Maybe we can have an informal coordination meeting on Sunday evening in Helsinki? Best, Niels -------- Forwarded Message -------- Subject: FW: ICANN and Human Rights meeting in Helsinki Date: Mon, 30 May 2016 08:19:13 +0000 From: Maryam Bakoshi <maryam.bakoshi(a)icann.org> To: Niels ten Oever <niels(a)digitaldissidents.org> Please find below. Many thanks, -- Maryam Bakoshi Secretariat Support - NCSG, NCUC, NPOC Internet Corporation for Assigned Names and Numbers (ICANN) Email: maryam.bakoshi(a)icann.org <mailto:maryam.bakoshi@icann.org> Mobile: +44 7737 698036 Skype: maryam.bakoshi.icann From: Glen de Saint Gery <Glen(a)icann.org <mailto:Glen@icann.org>> Date: Friday, 27 May 2016 at 21:05 To: Rafik Dammak <rafik.dammak(a)gmail.com <mailto:rafik.dammak@gmail.com>> Cc: Maryam Bakoshi <maryam.bakoshi(a)icann.org <mailto:maryam.bakoshi@icann.org>>, Glen de Saint Gery <Glen(a)icann.org <mailto:Glen@icann.org>> Subject: ICANN and Human Rights meeting in Helsinki Dear Rafik, You requested an ICANN and Human Rights <#ICANN_HR>meeting on */ /*any day/time, but preferably Tuesday 28 June 15:15 – 16:45 in Helsinki. Unfortunately with the very compressed meeting schedule and the available space there just has not been any place to fit this meeting in at any time. I am really sorry about this but perhaps you could try and meet in Hyderabad where the meeting will be considerably longer and the conference space larger. Together with the Council leadership and the ICANN Meeting Staff all possibilities have been examined and we regret that we cannot satisfy your request. Thank you for understanding. Kind regards, Glen Glen de Saint Géry GNSO Secretariat *gnso.secretariat(a)gnso.icann.org <mailto:gnso.secretariat@gnso.icann.org>* *http://gnso.icann.org <http://gnso.icann.org/>*

1 0

Comment for the "Streamlined Approach" (?) Text
by Seth Johnson May 29, 2016

May 29, 2016

(Reposting with a subject topic more relevant to the specific suggestion I put in this commentary.) You should be careful from the outset when you use language about ICANN to define the parameters of the project. The title of what we're doing can and should be stated the way you have, but what we're doing entails understanding what happens to human rights (of all kinds, not just treaty-based ones) in the transition. Though the FOI must be scoped to ICANN and the By-laws, the matter involves a broader view, considering the issue with reference to the surrounding context and where we are ending up in the transition. Even if ICANN has very appropriately declared it has no governmental authority and doesn't enforce human rights, our task includes making clear what happens when we move away from *that* one government as the "host," to "all the governments" (understanding that *extremely* amorphously). It's important to remember that the nature of the issue of human rights isn't necessarily structurally wedded to ICANN structures, so we can't accidentally let it be treated that way. Addressing the issue of human rights should mean addressing how we understand human rights to be referenced with respect to *what the transition means* for human rights. This can be done very well by commenting on the nature of "standard of review" and how the transition to a "more international" legal basis for rights affects that. That would be my comment on the document(s?) we've seen so far. In the "streamlined approach" one, I would say add a point observing that peoples in individual countries (or federal unions, as we just saw with the Safe Harbor Agreement in the EU) have very strong rights that have to be recognized. (As we start out, I think we can and should set aside the tangentially related matter some have raised elsewhere, of CA as the legal locus for ICANN's incorporation. That's only one notion of the issue of jurisdiction, and for that matter isn't particularly relevant to human rights, certainly given that I presume we all see the human rights issue the way I just described it -- working more from understanding how things work as we move to the "all the governments" international context. It can be considered in the jurisdiction discussion, and is vaguely relevant to rights in another sense -- ICANN as a "person" and its member[s] holding rights that relate to a US state in the "US federal republic of republics.") Seth On Thu, May 26, 2016 at 10:40 AM, Niels ten Oever <niels(a)article19.org> wrote: > Hi all, > > Thank you very much for your great comments. This is going to be quite a > long email, so brace yourself ;) > > 1. > - "HUMAN RIGHTS IN INTERNET GOVERNANCE DISCUSSION" > This is indeed too broad. This should be: > 'Scoping the relation between ICANN and Human Rights' > > 2. Glossary > Let's try the glossary at the bottom and HR principles on top. > > 3. > We should have a disclaimer text on top or at the bottom indicating that > 'this is a preliminary scoping, pending a full Human Rights Impact > Assessment' > > 4. > I would not drag in the European Court of Human Rights, I am afraid this > will make matter only more complicated. But let me know what you all think. > > 5. > I am hesitant to use the work 'ecosystem', because it goes back to the > thinking of Buckminster Fuller which implies that the system is > 'natural' and therefore 'evident' and 'inescapable'. Therefore I am a > bit hesistant of using these terms. (This all gets much better discussed > in the beautiful BBC documentary by Adam Curtis: 'all watched over by > machines of loving grace') > > 6. > I have made an initial idea for the rights dendogram (and principles), > let me know what you think, or Giulia could have a first go at it: > > **On top** > Human Rights principles: > * Inherent - human rights derive from the humanity of each person. > * Universal - all human beings have the same human rights. > * Inalienable - human rights cannot be given up. > * Indivisible - there are no conflicts between rights and no priorities > among rights. There will be situations or occasions where rights must > be balanced and prudent decisions taken about how all rights can best be > protected and promoted > * Interdependent and Interrelated - the enjoyment and fulfilment of any > right depends on the enjoyment and fulfilment of other rights. > * Equality and Non-discrimination: All individuals are equal as human > beings and by virtue of the inherent dignity of each human person > * Participation and Inclusion: All people have the right to participate > in and access information relating to the decision-making processes that > affect their lives and well-being. > * Accountability and Rule of Law: States and other duty-bearers are > answerable for the observance of human rights. In this regard, they have > to comply with the legal norms and standards enshrined in international > human rights instruments. > > > **Dendogram 2** > First Generation: > - Universal Declaration of Human Rights > > Second Generation: > - International Covenant on Civil and Political Rights (ICCPR) 1966 > - International Covenant on Economic, Social and Cultural Rights > (ICESCR) 1966 > - International Convention on the Elimination of All Forms of Racial > Discrimination (ICERD) 1965 > - Convention on the Elimination of All Forms of Discrimination Against > Women (CEDAW) 1979 > - Convention on the Rights of Persons with Disabilities (CRPD) 2006 > > Guidelines: > UN Guiding Principles on Business and Human Rights (2011) > UN Global Compact (2000) > > 7. There should be no space between WHO and IS (so WHOIS) > > 8. After DNSSEC we should perhaps also add: Implementation of DANE > > 9. Gender / Race / Diversity issues probably could be renamed as: > Participation, Inclusion, Equality and Non-Discrimination > > and we can add to the final column: > - participation by people with a disability in ICANN process (including > meetings) > - anti-harassment policy > > 10. I think all DIDP, DCND and IDNs should not be named as accronyms, > but rather fully written down. > > 11. Addition to the glossary: > DNSSEC = Domain Name System Security Extensions > IGO = Intergovernmental Organization > INGO = International Non-Governmental Organziation > RPM = Rights Protection Mechanism (as related to Intellectual Property > Rights) > > I think IP adress can be remove > > 12. Inline repsonses to Avri's great e-mail (thanks!): > > > On 05/22/2016 04:01 PM, avri doria wrote: >> Hi, >> >> I like the mindmap way of looking at this. Also allows for each of the >> end nodes to go into more detail without needing to show that detail all >> the time. Is the mindmap file available and is further work planned on >> it? Is it in one of those environments that allows for cooperative >> online work? > > Unfortunately not, it is made by a designer, but it would be great if a > volunteer wants to reproduce this as (online) mindmap. > >> Or is this only an Article 19 proposal as the file name >> indicates. > > Nope, this work was initially started by Marilia, then first images were > produced by APC, finally I took over the baton because others were > focused on other work. Once this is approved by the CCWP it is, as > everything here, a product of the CCWP HR. >> >> Some points on the content of the chart. >> >> - On new gTLD you may want to add something about gTLD and developing >> economies under economic, social (and what happened to cultural) rights. >> I.e. new gTLD program comes under this category as well. >> > > Indeed, we should add cultural so it reads: > 'Economic, social and cultural rights', but gTLDs are mentioned under > freedom of association, right? It also say 'community based TLDs'. You > think we should elaborate. > >> - under FoA and new gTLDs, you may want to consider two branches, one >> dealing with the existing program, in which case the AGB of 2012, as an >> implementation of the policy of 2007, is an issue. For new gTLD, the >> AGB, as an implementation is not the starting point, but the >> reevaluation of the GNSO Policy of 2007 and its implementation will be >> the issue. This is similar to what was done for FoE. >> > > > I am having a hard time understanding how the Applicant Guidebook (AGB) > implementation and revisioning is done. Could someone with more > understanding of this suggest a vizualization (wording of branches)? > >> - under FoA, is the structure of ICANN internal working structure for >> the community at all an additional consideration? >> > > Sure, how shall we word it? > >> - under gender and diversity, is the ombudsman the only consideration? >> What about the new policies such as the one that is being proposed in >> https://www.icann.org/public-comments/expected-standards-revisions-2016-05-… >> > > Adressed above and added a few. > > > So I hope this helps, with this I'll ask Giulia to make a new version, > but keep your comments and text suggestions coming! > > Best, > > Niels > > > > > >> >> avri >> >> >> On 21-May-16 06:07, Niels ten Oever wrote: >>> Dear colleagues, >>> >>> Attached a second draft visualization made by the designer, as always, >>> looking forward to your comments! >>> >>> What text is missing? What more would you like to be in here? >>> >>> I was thinking (maybe too much, maybe not), we could maybe also do a >>> dendogram based on rights. With the UDHR at the bottom, the ICCPR and >>> the ICESCR coming from that and then all the smaller treaties following >>> that, and finally of course the Ruggie Principles and the Global >>> compact. This might build on the work done by Tatiana and Aarti on >>> relevant frameworks? It defintely needs some research and lawyer touch :) >>> >>> Curious to hear what you all think! >>> >>> Best, >>> >>> Niels >>> >>> >>> _______________________________________________ >>> cc-humanrights mailing list >>> cc-humanrights(a)icann.org >>> https://mm.icann.org/mailman/listinfo/cc-humanrights >> >> >> >> >> _______________________________________________ >> cc-humanrights mailing list >> cc-humanrights(a)icann.org >> https://mm.icann.org/mailman/listinfo/cc-humanrights >> > > > _______________________________________________ > cc-humanrights mailing list > cc-humanrights(a)icann.org > https://mm.icann.org/mailman/listinfo/cc-humanrights >

2 3

joint session GAC WG HRIL & CCWP HR on Thursday 15:00 - 15:45 in Helsinki ICANN56
by Niels ten Oever May 28, 2016

May 28, 2016

Hi all, We've requested a joint CCWP HR & GAC WG HRIL session on Thursday 15:00 - 15:45 during the ICANN meeting. With thanks to the GAC WG HRIL c0-chairs who filed the request. All the best, Niels

1 0

Fwd: [CCWG-ACCT] U.S. Senate Committee on Commerce, Science, and Transportation Full Hearing on 24 May 2016
by Seth Johnson May 24, 2016

May 24, 2016

FYI ---------- Forwarded message ---------- From: Seth Johnson <seth.p.johnson(a)gmail.com> Date: Tue, May 24, 2016 at 5:46 PM Subject: Re: [CCWG-ACCT] U.S. Senate Committee on Commerce, Science, and Transportation Full Hearing on 24 May 2016 To: Sivasubramanian M <isolatedn(a)gmail.com> Cc: Accountability Cross Community <accountability-cross-community(a)icann.org>, "ianatransition(a)icann.org" <ianatransition(a)icann.org> On Tue, May 24, 2016 at 2:07 PM, Sivasubramanian M <isolatedn(a)gmail.com> wrote: <SNIP> > Even while continuing to be in the California Jurisdiction, the > Accountability design requires to be one that would move ICANN governance > as farther away from California Courts as possible. Could there be an > Accountability design that could take ICANN governance away from lawyers > (no disrespect intended) but towards a balanced and inherently just > framework? Could there be a "soft enough" or "loose" oversight/observation > by the NTIA at least until Workstream 2 and other Accountability processes > place together such a self-contained framework for global public interest? > > In many ways, a soft interim role for the US Government, or a short delay > would actually ensure that the transition details are gracefully accepted by > the whole world. It should be noted that this is essentially the role the NTIA has been simulating thus far. They've sort of/supposedly handed it off a bit already by creating ICANN. Then sort of/supposedly the processes are private as much as possible, and NTIA only acts in the most circumspect way when it appears prudent. The premise in that story of the transition is that privatizing under ICANN (via corporate statute in a certain jurisdiction/CA) does the job that's needed. I would hold that a just framework like you describe would have to be examined, including in relation to that premise, in WS2 whatever happens re NTIA's role. My guess is the political impetus is to going cold turkey. But what I would say is that you may still have to work on addressing what's going to happen by putting up a strong effort in WS2. Jurisdiction and rights are in that discussion. To my reckoning, what's been done is the ICANN internal stuff. There's more happening though, and that's what you need to be attentive to. Seth > Sivasubramanian M > > > > > > > > > -- > Sivasubramanian M > > _______________________________________________ > Accountability-Cross-Community mailing list > Accountability-Cross-Community(a)icann.org > https://mm.icann.org/mailman/listinfo/accountability-cross-community >

1 0

Re: [cc-humanrights] cc-humanrights Digest, Vol 18, Issue 10
by Corinne Cath May 24, 2016

May 24, 2016

Dear all, On the basis of our discussions, I have taken another stab at the FOI. This time sending you a pretty bare-back version, with a lot of text that still needs to be filled in/defined, preferably by someone with more legal skills than myself. The purpose of this Framework of Interpretation (FOI) is to give a framework for applying human rights principles and clarifying the language in recommendation 6 on human rights, to ensure that ICANN respects internationally recognized human rights. In order to do so, this document has two sections. The first section is a glossary that provides an overview of the different terms used in the bylaw language and how to interpret them. The second section gives a broader overview of which human rights instruments might be applicable, how ICANN can stay within its scope, why a Human Rights Impact Assessment (HRIA) might be useful, which additional policies and frameworks ICANN might need to develop, how these new frameworks should be discussed and drafted to ensure broad multistakeholder involvement, and how ICANN impacts human rights. *Glossary: * The bylaw text makes use of the following concepts that need further clarification, which is given below. To respect human rights: To respect human rights means that [enter text]. Internationally recognized human rights means [enter text]. Applicable law means [enter text]. Not to enforce means [enter text]. Not going out of ICANN’s scope means [e.g. no enforcement + enter text] [Did I forget things? – please feel free to add] *Overview:* Which specific Human Rights conventions or other instruments, if any, should be used by ICANN in interpreting and implementing the Human Rights Bylaw: United nations declaration of human rights (UDHR) http://www.un.org/en/universal-declaration-human-rights/ Ruggie Principles: http://www.ohchr.org/Documents/Publications/GuidingPrinciplesBusinessHR_EN.… ICT sector guide for implementing Ruggie Principles http://shiftproject.org/sites/default/files/ECHRSG.ICT_.pdf International Covenant on Civil and Political Rights (IPCR) http://www.ohchr.org/en/professionalinterest/pages/ccpr.aspx International Covenant on Economic, Social and Cultural Rights http://www.ohchr.org/EN/ProfessionalInterest/Pages/CESCR.aspx [what else? Please feel free to add] Which policies and frameworks, if any, does ICANN needs to develop or enhance in order to fulfill its commitment to respect Human Rights: [enter text]. Consistent with ICANN’s existing processes and protocols, consider how these new frameworks should be discussed and drafted to ensure broad multistakeholder involvement in the process: [enter text]. Where does ICANN’s work impacts human right: [enter text]. How to measure this potential impact: [enter text]. Hope this is useful, Best, On Tue, May 17, 2016 at 2:03 PM, <cc-humanrights-request(a)icann.org> wrote: > Send cc-humanrights mailing list submissions to > cc-humanrights(a)icann.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mm.icann.org/mailman/listinfo/cc-humanrights > or, via email, send a message with subject or body 'help' to > cc-humanrights-request(a)icann.org > > You can reach the person managing the list at > cc-humanrights-owner(a)icann.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cc-humanrights digest..." > > > Today's Topics: > > 1. Re: FoI discussion (Motoko Aizawa) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 17 May 2016 09:02:51 -0400 > From: Motoko Aizawa <motoko.aizawa(a)ihrb.org> > To: Niels ten Oever <niels(a)article19.org> > Cc: Human Rights <cc-humanrights(a)icann.org> > Subject: Re: [cc-humanrights] FoI discussion > Message-ID: > < > CAByCGFRRNeu4s5O5q9WwJN-wMR99zS7EMBAo4mva3nEBvS-6pA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Apologies in advance that I will not be on the call today. Re the FoI, I > agree that less is more. In terms of the four bullets, I would offer the > first two bullet points instead. I do agree that less is more. Motoko > > > - What it means for ICANN to respect human rights > - What is outside the scope of ICANN's responsibility to respect human > rights (e.g., no enforcement) > > - Reference to applicable instruments > - Whether other documents are needed in addition to the bylaw (e.g. > HR > policy > > > > > *Motoko Aizawa | Managing Director USA* > *M* +1 202 763 1503 *|**S* MotokoSkype11 *I* *W* www.ihrb.org *I T* *@ > <haley.st.dennis(a)ihrb.org>**IHRB* > *Bogot*? *| **Brussel**s * *| **Geneva* *| **London* *|** Nairobi* *| > **Washington > D.C.* *|* *Yangon* > > On Tue, May 17, 2016 at 6:45 AM, Niels ten Oever <niels(a)article19.org> > wrote: > > > Dear Corinne, > > > > Thanks for your great work, it might help to have a bit of background in > > to the discussion that we extensively had in CCWG WP4 on this. There was > > no clear agreement whatsoever on using the Ruggie Principles, so > > assuming we will might ruffle some feathers. > > > > Next to that we might need think whether it would be necessary to go > > this deep and far at all. Maybe an FoI could simply be an explanatory > > report to the bylaw which explains: > > - What does it mean to respect > > - What does it mean to not enforce > > - Reference to applicable instruments > > - Whether other documents are needed in addition to the bylaw > > (e.g. HR > > policy > > > > I think that less might be more. > > > > Happy to discuss on the call and hear what other people think. > > > > Best, > > > > Niels > > > > > > > > Niels ten Oever > > Head of Digital > > > > Article 19 > > www.article19.org > > > > PGP fingerprint 8D9F C567 BEE4 A431 56C4 > > 678B 08B5 A0F2 636D 68E9 > > > > On 05/17/2016 11:59 AM, Corinne Cath wrote: > > > Dear all, > > > > > > I have been working on the FOI - and developed some completely new text > > > on the basis of your suggestions, which you can find below. > > > > > > I have focused on the Ruggie principles as the standard for ICANN to > > > uphold. I assume this is still open for discussion, but for the time > > > being (or unless Tatiana, Aarti or Vidushi tell me that I have no > > > business making these kinds of decisions as a none-lawyer ;) I am > > > focusing on Ruggie. > > > > > > However, I am running into some troubles trying to actually flesh out > > > what steps should be taken to ensure the interpretation of the Ruggie > > > principles happens as we believe will best ensure ICANN's commitment to > > > respect human rights. > > > > > > Right now I combined text from the HRIA document, the research done > > > < > > > http://www.ihrb.org/pdf/reports/2015-11-17-ICANN-Corporate-Responsibility-t… > > > > > > by Article 19 and the guiding principles > > > <http://www.ohchr.org/Documents/Publications/HR.PUB.12.2_En.pdf>for > the > > > Ruggie principles. But I feel like I am going in circles, and > suggesting > > > in the FOI that we need the development of other policies and > > > procedures. Which I don't think is the best way forward. > > > > > > If anyone has any thoughts now, or on the call later today that would > be > > > much appreciated! > > > > > > Best, > > > > > > > > > *FOI Version 3 * > > > > > > > > > > > > The purpose of this Framework of Interpretation (FOI) is to give a > > > framework for applying human rights principles to ensure that ICANN > > > respects internationally recognized human rights. The most appropriate > > > principles to set as the standard in the case of ICANN are the UN > > > Guiding Principleson Business and Human Rights, also known as the > Ruggie > > > principles. These principles present a set of guidelines for States and > > > companies to ?protect, respect, and remedy? human rights abuses > > > committed in business operations. Their unique tailoring to businesses > > > makes them a good fit for ICANN. The word respect in this case refers > to > > > companies? responsibility to avoid infringing on the human rights of > > > others and should address adverse human rights impacts with which they > > > are involved (Guiding principle 11, > > > < > > > http://www.ohchr.org/Documents/Publications/GuidingPrinciplesBusinessHR_EN.… > > >for > > > implementing the Ruggie Principles). > > > > > > > > > > > > The overall Ruggie principles has three tiers: > > > > > > 1. State responsibility to protect against human rights abuses by third > > > entities, including businesses through policies, regulation and > > > adjudication. > > > > > > 2. Corporate responsibility to respect human rights, in which > businesses > > > are asked to practice due diligence (see definition below) to avoid > > > infringing on the rights of others and address instances of adverse > > > impact in which they are involved. > > > > > > 3. Access to effective remedy for victims, both judicial and > > non-judicial. > > > > > > > > > > > > This framework of interpretation develops a set of guiding principles > > > based on those presented by the UN for the Ruggie principles and > > > specifically focused on the second tier: the corporate responsibility > to > > > respect human rights. > > > > > > > > > *Corporate responsibility to respect human rights:* > > > > > > In addition to an explicit human rights commitment, companies need to > > > adopt a due diligence approach to their business processes. Due > > > diligence in the case of human rights refers to the: ?An ongoing risk > > > management process?in order to identify, prevent, mitigate and account > > > for how [a company] addresses its adverse human rights impacts. It > > > includes four key steps: assessing actual and potential human rights > > > impacts; integrating and acting on the findings; tracking responses; > and > > > communicating about how impacts are addressed.? (UN Ruggie Principles). > > > > > > In practice this mean companies need to have in place on-going > processes > > > that identify potential human rights abuses, that allow them to respond > > > in a timely fashion with measures to prevent these abuses. These > > > processes can also identify ongoing human rights abuses, and as such, > > > need to include procedures to remedy those. Keeping in mind that this > > > framework of interpretation 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. > > > > > > Based on this information the following steps should be taken to ensure > > > proper interpretation of the Ruggie Principles: > > > > > > > > > _Phase 1: Human rights impact analysis_ > > > > > > a.) A planning and scoping phase that includes scoping of (i) ICANN?s > > > business activities to understand the scale and type of ICANN?s > > > operations, and (ii) the human rights context of ICANN?soperation to > > > understand the human rights topics in the particular ICANN operational > > > context. > > > > > > > > > b.) Data collection and baseline phase: additional data gathering to > > > better understand the key human rights areas identified in phase > a, > > > through further research, as well as interviews and stakeholder > > > engagement. > > > > > > > > > c.) Impact analysis: systematically identify any human rights impacts > of > > > ICANN operations and to assess their severity against the Ruggie > > Principles. > > > > > > > > > d.) Present an impact analysis matrix. > > > > > > > > > > > > _Phase 2: Mitigation and prevention system for human rights abuses_ > > > > > > a.) Manage and mitigate impact by applying a mitigation hierarchy that > > > first focuses on prevention, and where not possible applies mitigation > > > strategies.This includes finding ways to exercise leverage to address > > > impacts in collaboration with third parties, including business > > > partners, stakeholders, government agencies etc. > > > > > > > > > b.) Clearly establish roles and responsibility, allocate resources and > > > establish performance indicators, milestones and deadlines to be > > > followed. > > > > > > > > > > > > _Phase 3: Presentation of findings _ > > > > > > a.) Present the responses to the issues identified on an on going > basis. > > > > > > > > > > > > _Phase 4: Reporting and evaluation_ > > > > > > a.) Reporting publically on progress periodically. > > > > > > > > > b.) Develop mechanism to feed these results back into phase 2. > > > > > > > > > c.) ICANN board and management should carry out a comprehensive (and > > > preferably an external) process of review and evaluation of its Policy > > > and Management Plan/System after three to five years of implementation. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, May 16, 2016 at 10:44 PM, <cc-humanrights-request(a)icann.org > > > <mailto:cc-humanrights-request@icann.org>> wrote: > > > > > > Send cc-humanrights mailing list submissions to > > > cc-humanrights(a)icann.org <mailto:cc-humanrights@icann.org> > > > > > > To subscribe or unsubscribe via the World Wide Web, visit > > > https://mm.icann.org/mailman/listinfo/cc-humanrights > > > or, via email, send a message with subject or body 'help' to > > > cc-humanrights-request(a)icann.org > > > <mailto:cc-humanrights-request@icann.org> > > > > > > You can reach the person managing the list at > > > cc-humanrights-owner(a)icann.org > > > <mailto:cc-humanrights-owner@icann.org> > > > > > > When replying, please edit your Subject line so it is more specific > > > than "Re: Contents of cc-humanrights digest..." > > > > > > > > > Today's Topics: > > > > > > 1. REMINDER: CCWP ICANN and Human Rights | Tuesday 17 May 2016 | > > > 13:00 UTC (Maryam Bakoshi) > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Mon, 16 May 2016 21:08:54 +0000 > > > From: Maryam Bakoshi <maryam.bakoshi(a)icann.org > > > <mailto:maryam.bakoshi@icann.org>> > > > To: Human Rights <cc-humanrights(a)icann.org > > > <mailto:cc-humanrights@icann.org>>, ICANN Policy Calendar > > > <PolicyCalendar(a)icann.org <mailto:PolicyCalendar@icann.org > >> > > > Cc: matteo lucchetti <matluc(a)hotmail.com > > > <mailto:matluc@hotmail.com>>, Herb Waye > > > <herb.waye(a)icann.org <mailto:herb.waye@icann.org>>, Niels > > > ten Oever <niels(a)digitaldissidents.org > > > <mailto:niels@digitaldissidents.org>> > > > Subject: [cc-humanrights] REMINDER: CCWP ICANN and Human Rights | > > > Tuesday 17 May 2016 | 13:00 UTC > > > Message-ID: > > > > > > < > 7ddc6bc5d2dc4231aa07c4ea65fcedc9(a)PMBX112-E1-VA-2.PEXCH112.ICANN.ORG > > > <mailto: > > 7ddc6bc5d2dc4231aa07c4ea65fcedc9(a)PMBX112-E1-VA-2.PEXCH112.ICANN.ORG>> > > > Content-Type: text/plain; charset="iso-8859-1" > > > > > > Dear All, > > > > > > > > > Please find below participation details for CCWP ICANN and Human > > > Rights on Tuesday 17 May 2016 at 13:00 UTC > > > > > > > > > Adobe Connect: https://icann.adobeconnect.com/ncsg/ > > > > > > > > > Full list of Time Zones: http://tinyurl.com/z6pcbrq > > > > > > > > > Time in some other locations: > > > > > > > > > Sydney: Tuesday, 17 May 2016, 23:00 > > > Tokyo: Tuesday, 17 May 2016, 22:00 > > > Beijing: Tuesday, 17 May 2016, 21:00 > > > Moscow: Tuesday, 17 May 2016, 16:00 > > > New Delhi: Tuesday, 17 May 2016, 18:30 > > > Paris: Tuesday, 17 May 2016, 15:00 > > > Buenos Aires: Tuesday, 17 May 2016, 10:00 > > > New York: Tuesday, 17 May 2016, 09:00 > > > Los Angeles: Tuesday, 17 May 2016, 06:00 > > > > > > > > > Agenda: TBC > > > > > > > > > Passcodes/Pin codes: > > > Participant passcode: HR > > > > > > For security reasons, the passcode will be required to join the > > > conference. > > > > > > Dial in numbers: > > > Country Toll Numbers Freephone/ > > > Toll Free Number > > > > > > > > > ARGENTINA 0800-777-0519<tel:0800-777-0519> > > > AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 > > > AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 > > > AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 > > > AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 > > > AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 > > > AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 > > > AUSTRIA 43-1-92-81-113 0800-005-259 > > > BELGIUM 32-2-400-9861 0800-3-8795 > > > BRAZIL 0800-7610651<tel:0800-7610651> > > > CHILE 1230-020-2863 > > > CHINA CHINA A: 86-400-810-4789 10800-712-1670 > > > CHINA CHINA B: 86-400-810-4789 10800-120-1670 > > > COLOMBIA 01800-9-156474 > > > CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 > > > DENMARK 45-7014-0284 8088-8324 > > > ESTONIA 800-011-1093 > > > FINLAND 358-9-5424-7162 0-800-9-14610 > > > FRANCE LYON: 33-4-26-69-12-85 080-511-1496 > > > FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 > > > FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 > > > GERMANY 49-69-2222-20362 > > 0800-664-4247<tel:0800-664-4247> > > > GREECE 30-80-1-100-0687 00800-12-7312 > > > HONG KONG 852-3001-3863 800-962-856 > > > HUNGARY 06-800-12755 > > > INDIA INDIA A: 000-800-852-1268 > > > INDIA INDIA B: 000-800-001-6305 > > > INDIA INDIA C: 1800-300-00491 > > > INDONESIA 001-803-011-3982 > > > IRELAND 353-1-246-7646 1800-992-368 > > > ISRAEL 1-80-9216162 > > > ITALY MILAN: 39-02-3600-6007 800-986-383 > > > JAPAN OSAKA: 81-6-7739-4799<tel:81-6-7739-4799> > > 0066-33-132439 > > > JAPAN TOKYO: 81-3-5539-5191<tel:81-3-5539-5191> > > 0066-33-132439 > > > LATVIA 8000-3185 > > > LUXEMBOURG 352-27-000-1364 > > > MALAYSIA 1-800-81-3065 > > > MEXICO 001-866-376-9696 > > > NETHERLANDS 31-20-718-8588 > > 0800-023-4378<tel:0800-023-4378> > > > NEW ZEALAND 64-9-970-4771 0800-447-722 > > > NORWAY 47-21-590-062 800-15157 > > > PANAMA 011-001-800-5072065 > > > PERU 0800-53713 > > > PHILIPPINES 63-2-858-3716 > > > POLAND 00-800-1212572 > > > PORTUGAL 8008-14052 > > > RUSSIA 8-10-8002-0144011 > > > SAUDI ARABIA 800-8-110087 > > > SINGAPORE 65-6883-9230 800-120-4663 > > > SLOVAK REPUBLIC 421-2-322-422-25 > > > SOUTH AFRICA 080-09-80414 > > > SOUTH KOREA 82-2-6744-1083 00798-14800-7352 > > > SPAIN 34-91-414-25-33 800-300-053 > > > SWEDEN 46-8-566-19-348 0200-884-622 > > > SWITZERLAND 41-44-580-6398 0800-120-032 > > > TAIWAN 886-2-2795-7379 00801-137-797 > > > THAILAND 001-800-1206-66056 > > > UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 > > > UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 > > > UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 > > > UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 > > > UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 > > > URUGUAY 000-413-598-3421 > > > USA 1-517-345-9004 866-692-5726 > > > VENEZUELA 0800-1-00-3702 > > > > > > > > > Restrictions may exist when accessing freephone/toll free numbers > > > using a mobile telephone. > > > > > > > > > Many thanks, > > > -- > > > Maryam Bakoshi > > > Secretariat ?Support - NCSG, NCUC, NPOC > > > Internet Corporation for Assigned Names and Numbers (ICANN) > > > > > > > > > Email: maryam.bakoshi(a)icann.org > > > <mailto:maryam.bakoshi@icann.org><mailto:maryam.bakoshi@icann.org > > > <mailto:maryam.bakoshi@icann.org>> > > > Mobile: +44 7737 698036 <tel:%2B44%207737%20698036> > > > Skype: maryam.bakoshi.icann > > > > > >

1 0

Re: [cc-humanrights] cc-humanrights Digest, Vol 18, Issue 5
by Corinne Cath May 17, 2016

May 17, 2016

Dear all, I have been working on the FOI - and developed some completely new text on the basis of your suggestions, which you can find below. I have focused on the Ruggie principles as the standard for ICANN to uphold. I assume this is still open for discussion, but for the time being (or unless Tatiana, Aarti or Vidushi tell me that I have no business making these kinds of decisions as a none-lawyer ;) I am focusing on Ruggie. However, I am running into some troubles trying to actually flesh out what steps should be taken to ensure the interpretation of the Ruggie principles happens as we believe will best ensure ICANN's commitment to respect human rights. Right now I combined text from the HRIA document, the research done <http://www.ihrb.org/pdf/reports/2015-11-17-ICANN-Corporate-Responsibility-t…> by Article 19 and the guiding principles <http://www.ohchr.org/Documents/Publications/HR.PUB.12.2_En.pdf>for the Ruggie principles. But I feel like I am going in circles, and suggesting in the FOI that we need the development of other policies and procedures. Which I don't think is the best way forward. If anyone has any thoughts now, or on the call later today that would be much appreciated! Best, *FOI Version 3 * The purpose of this Framework of Interpretation (FOI) is to give a framework for applying human rights principles to ensure that ICANN respects internationally recognized human rights. The most appropriate principles to set as the standard in the case of ICANN are the UN Guiding Principles on Business and Human Rights, also known as the Ruggie principles. These principles present a set of guidelines for States and companies to ‘protect, respect, and remedy’ human rights abuses committed in business operations. Their unique tailoring to businesses makes them a good fit for ICANN. The word respect in this case refers to companies’ responsibility to avoid infringing on the human rights of others and should address adverse human rights impacts with which they are involved (Guiding principle 11, <http://www.ohchr.org/Documents/Publications/GuidingPrinciplesBusinessHR_EN.…> for implementing the Ruggie Principles). The overall Ruggie principles has three tiers: 1. State responsibility to protect against human rights abuses by third entities, including businesses through policies, regulation and adjudication. 2. Corporate responsibility to respect human rights, in which businesses are asked to practice due diligence (see definition below) to avoid infringing on the rights of others and address instances of adverse impact in which they are involved. 3. Access to effective remedy for victims, both judicial and non-judicial. This framework of interpretation develops a set of guiding principles based on those presented by the UN for the Ruggie principles and specifically focused on the second tier: the corporate responsibility to respect human rights. *Corporate responsibility to respect human rights:* In addition to an explicit human rights commitment, companies need to adopt a due diligence approach to their business processes. Due diligence in the case of human rights refers to the: “An ongoing risk management process…in order to identify, prevent, mitigate and account for how [a company] addresses its adverse human rights impacts. It includes four key steps: assessing actual and potential human rights impacts; integrating and acting on the findings; tracking responses; and communicating about how impacts are addressed.” (UN Ruggie Principles). In practice this mean companies need to have in place on-going processes that identify potential human rights abuses, that allow them to respond in a timely fashion with measures to prevent these abuses. These processes can also identify ongoing human rights abuses, and as such, need to include procedures to remedy those. Keeping in mind that this framework of interpretation 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. Based on this information the following steps should be taken to ensure proper interpretation of the Ruggie Principles: *Phase 1: Human rights impact analysis* a.) A planning and scoping phase that includes scoping of (i) ICANN’s business activities to understand the scale and type of ICANN’s operations, and (ii) the human rights context of ICANN’s operation to understand the human rights topics in the particular ICANN operational context. b.) Data collection and baseline phase: additional data gathering to better understand the key human rights areas identified in phase a, through further research, as well as interviews and stakeholder engagement. c.) Impact analysis: systematically identify any human rights impacts of ICANN operations and to assess their severity against the Ruggie Principles. d.) Present an impact analysis matrix. *Phase 2: Mitigation and prevention system for human rights abuses* a.) Manage and mitigate impact by applying a mitigation hierarchy that first focuses on prevention, and where not possible applies mitigation strategies. This includes finding ways to exercise leverage to address impacts in collaboration with third parties, including business partners, stakeholders, government agencies etc. b.) Clearly establish roles and responsibility, allocate resources and establish performance indicators, milestones and deadlines to be followed. *Phase 3: Presentation of findings * a.) Present the responses to the issues identified on an on going basis. *Phase 4: Reporting and evaluation* a.) Reporting publically on progress periodically. b.) Develop mechanism to feed these results back into phase 2. c.) ICANN board and management should carry out a comprehensive (and preferably an external) process of review and evaluation of its Policy and Management Plan/System after three to five years of implementation. On Mon, May 16, 2016 at 10:44 PM, <cc-humanrights-request(a)icann.org> wrote: > Send cc-humanrights mailing list submissions to > cc-humanrights(a)icann.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mm.icann.org/mailman/listinfo/cc-humanrights > or, via email, send a message with subject or body 'help' to > cc-humanrights-request(a)icann.org > > You can reach the person managing the list at > cc-humanrights-owner(a)icann.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cc-humanrights digest..." > > > Today's Topics: > > 1. REMINDER: CCWP ICANN and Human Rights | Tuesday 17 May 2016 | > 13:00 UTC (Maryam Bakoshi) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 16 May 2016 21:08:54 +0000 > From: Maryam Bakoshi <maryam.bakoshi(a)icann.org> > To: Human Rights <cc-humanrights(a)icann.org>, ICANN Policy Calendar > <PolicyCalendar(a)icann.org> > Cc: matteo lucchetti <matluc(a)hotmail.com>, Herb Waye > <herb.waye(a)icann.org>, Niels ten Oever < > niels(a)digitaldissidents.org> > Subject: [cc-humanrights] REMINDER: CCWP ICANN and Human Rights | > Tuesday 17 May 2016 | 13:00 UTC > Message-ID: > < > 7ddc6bc5d2dc4231aa07c4ea65fcedc9(a)PMBX112-E1-VA-2.PEXCH112.ICANN.ORG> > Content-Type: text/plain; charset="iso-8859-1" > > Dear All, > > > Please find below participation details for CCWP ICANN and Human Rights on > Tuesday 17 May 2016 at 13:00 UTC > > > Adobe Connect: https://icann.adobeconnect.com/ncsg/ > > > Full list of Time Zones: http://tinyurl.com/z6pcbrq > > > Time in some other locations: > > > Sydney: Tuesday, 17 May 2016, 23:00 > Tokyo: Tuesday, 17 May 2016, 22:00 > Beijing: Tuesday, 17 May 2016, 21:00 > Moscow: Tuesday, 17 May 2016, 16:00 > New Delhi: Tuesday, 17 May 2016, 18:30 > Paris: Tuesday, 17 May 2016, 15:00 > Buenos Aires: Tuesday, 17 May 2016, 10:00 > New York: Tuesday, 17 May 2016, 09:00 > Los Angeles: Tuesday, 17 May 2016, 06:00 > > > Agenda: TBC > > > Passcodes/Pin codes: > Participant passcode: HR > > For security reasons, the passcode will be required to join the conference. > > Dial in numbers: > Country Toll Numbers Freephone/ > Toll Free Number > > > ARGENTINA 0800-777-0519<tel:0800-777-0519> > AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 > AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 > AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 > AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 > AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 > AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 > AUSTRIA 43-1-92-81-113 0800-005-259 > BELGIUM 32-2-400-9861 0800-3-8795 > BRAZIL 0800-7610651<tel:0800-7610651> > CHILE 1230-020-2863 > CHINA CHINA A: 86-400-810-4789 10800-712-1670 > CHINA CHINA B: 86-400-810-4789 10800-120-1670 > COLOMBIA 01800-9-156474 > CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 > DENMARK 45-7014-0284 8088-8324 > ESTONIA 800-011-1093 > FINLAND 358-9-5424-7162 0-800-9-14610 > FRANCE LYON: 33-4-26-69-12-85 080-511-1496 > FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 > FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 > GERMANY 49-69-2222-20362 0800-664-4247<tel:0800-664-4247> > GREECE 30-80-1-100-0687 00800-12-7312 > HONG KONG 852-3001-3863 800-962-856 > HUNGARY 06-800-12755 > INDIA INDIA A: 000-800-852-1268 > INDIA INDIA B: 000-800-001-6305 > INDIA INDIA C: 1800-300-00491 > INDONESIA 001-803-011-3982 > IRELAND 353-1-246-7646 1800-992-368 > ISRAEL 1-80-9216162 > ITALY MILAN: 39-02-3600-6007 800-986-383 > JAPAN OSAKA: 81-6-7739-4799<tel:81-6-7739-4799> 0066-33-132439 > JAPAN TOKYO: 81-3-5539-5191<tel:81-3-5539-5191> 0066-33-132439 > LATVIA 8000-3185 > LUXEMBOURG 352-27-000-1364 > MALAYSIA 1-800-81-3065 > MEXICO 001-866-376-9696 > NETHERLANDS 31-20-718-8588 0800-023-4378<tel:0800-023-4378> > NEW ZEALAND 64-9-970-4771 0800-447-722 > NORWAY 47-21-590-062 800-15157 > PANAMA 011-001-800-5072065 > PERU 0800-53713 > PHILIPPINES 63-2-858-3716 > POLAND 00-800-1212572 > PORTUGAL 8008-14052 > RUSSIA 8-10-8002-0144011 > SAUDI ARABIA 800-8-110087 > SINGAPORE 65-6883-9230 800-120-4663 > SLOVAK REPUBLIC 421-2-322-422-25 > SOUTH AFRICA 080-09-80414 > SOUTH KOREA 82-2-6744-1083 00798-14800-7352 > SPAIN 34-91-414-25-33 800-300-053 > SWEDEN 46-8-566-19-348 0200-884-622 > SWITZERLAND 41-44-580-6398 0800-120-032 > TAIWAN 886-2-2795-7379 00801-137-797 > THAILAND 001-800-1206-66056 > UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 > UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 > UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 > UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 > UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 > URUGUAY 000-413-598-3421 > USA 1-517-345-9004 866-692-5726 > VENEZUELA 0800-1-00-3702 > > > Restrictions may exist when accessing freephone/toll free numbers using a > mobile telephone. > > > Many thanks, > -- > Maryam Bakoshi > Secretariat ?Support - NCSG, NCUC, NPOC > Internet Corporation for Assigned Names and Numbers (ICANN) > > > Email: maryam.bakoshi(a)icann.org<mailto:maryam.bakoshi@icann.org> > Mobile: +44 7737 698036 > Skype: maryam.bakoshi.icann > >

4 3

REMINDER: CCWP ICANN and Human Rights | Tuesday 17 May 2016 | 13:00 UTC
by Maryam Bakoshi May 17, 2016

May 17, 2016

Dear All, Please find below participation details for CCWP ICANN and Human Rights on Tuesday 17 May 2016 at 13:00 UTC Adobe Connect: https://icann.adobeconnect.com/ncsg/ Full list of Time Zones: http://tinyurl.com/z6pcbrq Time in some other locations: Sydney: Tuesday, 17 May 2016, 23:00 Tokyo: Tuesday, 17 May 2016, 22:00 Beijing: Tuesday, 17 May 2016, 21:00 Moscow: Tuesday, 17 May 2016, 16:00 New Delhi: Tuesday, 17 May 2016, 18:30 Paris: Tuesday, 17 May 2016, 15:00 Buenos Aires: Tuesday, 17 May 2016, 10:00 New York: Tuesday, 17 May 2016, 09:00 Los Angeles: Tuesday, 17 May 2016, 06:00 Agenda: TBC Passcodes/Pin codes: Participant passcode: HR For security reasons, the passcode will be required to join the conference. Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519<tel:0800-777-0519> AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL 0800-7610651<tel:0800-7610651> CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247<tel:0800-664-4247> GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 JAPAN OSAKA: 81-6-7739-4799<tel:81-6-7739-4799> 0066-33-132439 JAPAN TOKYO: 81-3-5539-5191<tel:81-3-5539-5191> 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 MALAYSIA 1-800-81-3065 MEXICO 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378<tel:0800-023-4378> NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 POLAND 00-800-1212572 PORTUGAL 8008-14052 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 Restrictions may exist when accessing freephone/toll free numbers using a mobile telephone. Many thanks, -- Maryam Bakoshi Secretariat Support - NCSG, NCUC, NPOC Internet Corporation for Assigned Names and Numbers (ICANN) Email: maryam.bakoshi(a)icann.org<mailto:maryam.bakoshi@icann.org> Mobile: +44 7737 698036 Skype: maryam.bakoshi.icann

1 0

Proposed Agenda
by Niels ten Oever May 17, 2016

May 17, 2016

Dear all, I hope you're all looking forward to our call, please find a proposed agenda underneath: 1. Welcome and agenda bashing 2. Update SG1 - visualization - research 3. Update SG2 - CCWG WS process - Bylaw comments - FoI - SO/AC consensus ? draft here: https://is.gd/TIXIfr 4. Update SG3 - agreement of ToR ? If so, share with Maryam and on list - need to review working mode? 5. What documents can we look forward to agree on before Helsinki 6. AOB - Requested a 60 minute session in Helsinki Looking forward to discuss. Best, Niels -- Niels ten Oever Head of Digital Article 19 www.article19.org PGP fingerprint 8D9F C567 BEE4 A431 56C4 678B 08B5 A0F2 636D 68E9

1 0

Invitation: REMINDER: CCWP ICANN and Human Rights | Tuesday 17 May 20... @ Tue May 17, 2016 6:30pm - 7:30pm (am.i.swati@gmail.com)
by am.i.swati＠gmail.com May 17, 2016

May 17, 2016

You have been invited to the following event. Title: REMINDER: CCWP ICANN and Human Rights | Tuesday 17 May 2016 | 13:00 UTC When: Tue May 17, 2016 6:30pm – 7:30pm India Standard Time Where: https://icann.adobeconnect.com/ncsg/ Calendar: am.i.swati(a)gmail.com Who: * am.i.swati(a)gmail.com - organizer * lee.hibbard(a)coe.int * herb.waye(a)icann.org * nigel.hickson(a)icann.org * cc-humanrights(a)icann.org * jorge.cancio(a)bakom.admin.ch * mlattouf(a)agip.com * stefania.milan(a)eui.eu * gisella.gruber(a)icann.org * terri.agnew(a)icann.org * rballeste(a)stu.edu * nathalie.peregrine(a)icann.org * jean-jacques.sahel(a)icann.org * lauren.allison(a)icann.org * chris.lahatte(a)icann.org * megan.richards(a)ec.europa.eu * niels(a)digitaldissidents.org * grace.abuhamad(a)icann.org * matluc(a)hotmail.com * glen(a)icann.org * el2752(a)att.com * michele(a)blacknight.com * policycalendar(a)icann.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=Y2hobTJlYjNja3JqNGJiN… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account cc-humanrights(a)icann.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0