- Ws2-hr - lists.icann.org

Re: [Ws2-hr] [CCWG-ACCT] Notes, for WS2 HR. Text.
by Rudolph Daniel Dec. 7, 2016

Dec. 7, 2016

ReferenceText : ICANN should also consider ensuring that it does not violate human rights in its operations. ICANN might consider instruments such as HRIA to carry out a preliminary assessment of the effect of its operations, however, this is up to the ICANN corporation to decide and implement. The results of such IAs should be incorporated in ICANN’s annual reporting. My thoughts on reading the above: Icann's operations policies are not subject to a policy development process ( PDP ), but community input is generally sought via public comment. If the SO s were to consider implementation of HRIA at the PDP level, maybe the ICANN Board should consider assessment and oversight of HRIA on its policies at the 'Process and Systems risk Committee' level. This board committee is currently responsible for the establishment and implementation of standards, controls, limits and guidelines related to risk assessment and risk management, including but not limited to financial, legal and operational risks and other risks concerning ICANN’s reputation and ethical standards. Therefore, respect for human Rights, becomes weaved into ICANN 's reputation and ethical standards and as it relates to the public interest. Such a move however would probably require board consideration of a HRIA appointment to the 'Process and Systems risk committee' & other implications not yet apparent. RD

1 0

Notes, recordings and transcript for WS2 Human Rights Subgroup Meeting # 15 | 6 December
by MSSI Secretariat Dec. 6, 2016

Dec. 6, 2016

Hello all, Please see the notes, recordings, and transcript for the CCWG Accountability WS2 Human Rights Subgroup Meeting #15 here; https://community.icann.org/x/s5PDAw A copy of the action items and notes may be found below. Thank you. With kind regards, Brenda Brewer, Projects & Operations Assistant Multistakeholder Strategy & Strategic Initiatives (MSSI) Internet Corporation for Assigned Names and Numbers (ICANN) Notes: (including relevant portions of the chat): 1. Administrivia Roll call, absentees, SoIs, etc * Audio Only: Cheryl Langdon-Orr, Kavouss Arasteh * Roll call will be taken from the AC room * No SOI updates. 2. Analysis and discussion on the progress of the drafting team working on the Human Rights Policy and Process Questions * Shared draft document in the AC room. * Link to Google doc: https://docs.google.com/document/d/1KJfmglI5wBib7T5hgIMMysO7x6J3Oi5NYwN4AIt… * Greg presented an overview of the document: * Left-hand column has the additional points that we were asked to work on * The right-hand column has early draft of responses. * Not a lot of work has been done on this until now. * Seeking feedback on this initial draft. * Niels: This work is different from the work on the FoI. a.The policies and frameworks, if any, that ICANN needs to develop or enhance in order to fulfill its commitment to respect Human Rights * Niels introduced the section. * David McAuley: this may be a little bit broad. There are things we could suggest. * Greg: We should identify policies or frameworks that need to be developed or enhanced. b. 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 and: Consider how the interpretation and implementation of this Bylaw will interact with existing and future ICANN policies and procedures. * Niels introduced the section * Greg: the questions and the answer don't really fit together. First have to answer the 1st question. Suggested implementations will have to be developed further downstream. * David: agrees with Greg. Should develop HR Impact Assessment. * Erich Schweighofer: A full Human Rights Impact Assessment (HRIA) seems to be a very long shot at c. Consider what effect, if any, this Bylaw will have on ICANN’s consideration of advice given by the Governmental Advisory Committee (GAC) * Niels: wondering where this question came from in WS1 * Greg: need to look into where it came from, but don't see a change needed. We may need to clarify our understanding of the point raised here. * David McAuley (RySG): I agree w/Greg and implication of Niels question - not sure where this question came from but think the comment is a good one. * To summarize, this document is a good start. We need to clarify the definitions and our understanding of the questions raised. 3. AoB * Javier asking what areas of human rights this subgroup is focusing on. * Niels: the subgroup is following instructions from the CCWG proposal, and now from the HR-FoI that was produced by this subgroup. * David asking that whenever we plan to do a reading, it be clearly noted in the meeting agenda. Documents Presented * Presentation Meeting 14.pdf<https://community.icann.org/download/attachments/63148979/Presentation%20Me…> * HumanRightsPolicyandProcessQuestions(1).pdf<https://community.icann.org/download/attachments/63148979/HumanRightsPolicy…>

1 0

Notes, recordings and transcript for WS2 Human Rights Subgroup Meeting #14 | 02 DEC 16
by MSSI Secretariat Dec. 3, 2016

Dec. 3, 2016

Hello all, Please see the notes and details for the CCWG Accountability WS2 - Human Rights Subgroup Meeting #14 here: https://community.icann.org/x/ypXDAw A copy of the notes is also listed below. Thank you! Kind Regards, Yvette Guigneaux Multi-Stakeholder & Strategic Initiative Assistant ICANN | Internet Corporation for Assigned Names & Numbers 12025 Waterfront Drive, Playa Vista, CA 90094 yvette.guigneaux(a)icann.org<mailto:yvette.guigneaux@icann.org> | www.icann.org<http://www.icann.org/> Notes 1. Administrivia • Audio only: Leon Sanchez • No SOI updates • Nigel Roberts will no longer be co-rapporteur of this subgroup, as he couldn't make the time commitment anymore. • 10 working weeks till Copenhagen. • Next meeting Friday 19:00 UTC is an exception, will resume with regular schedule thereafter. 2. Analysis and discussion on the progress of the drafting team working on the new proposal for FoI • 2nd reading continued b.‘within the scope of other Core Values’ (with minor changes as per discussion last week) • Drafting team has worked on this section • Tatiana presented the revised text proposed by the drafting team • The openning bracket before "finally" is a mistake and will be removed. • David asking to clarify what the revision is about. • Tatiana indicated that the revision was about "legal hierarchy". • Greg indicated that the compromise proposed is the use of the work "standing' instead of "legal", ie "no standing hierarchy". • No further comments from the group. c.‘respecting’ • Greg read the section on "respecting" • No further comments from the group d. ‘internationally recognized human rights’ • Greg read the section on "internationally recognized human rights" • Greg indicated that "International" should not be capitalized • Andrew asked: "not applicable" in a legal sense? • Greg: not applicable in any sense • Group agrees with Greg's explanation • Kavouss: international law should not interfere with applicable law • Greg: this is covered by the section "Furthermore, depending on the jurisdiction etc." as well as the next section. • David McAuley (RySG): it seems clear to me that national legislation is addressed in what Greg just read • Niels suggests moving to next section. e. ‘as required by applicable law’ • Tatiana read the section on "as required by applicable law" • No changes were made here • No comments from the group f. ‘This Core Value does not create, and shall not be interpreted to create, any obligation on ICANN outside its Mission or beyond obligations found in applicable law’ • Greg read the section • No changes made • No comments from the group g. ‘‘This Core Value does not obligate ICANN to enforce its human rights obligations or the human rights obligations of other parties, against other parties’ (with minor changes as per discussion last week) • Greg read the section • Kavouss: "other parties against other parties" doesn't seem correct, suggest changing to "one party against other" • Greg agrees that the use of repetitive "other parties" is somewhat confusing. Suggest "one party against other parties" or " a party against other parties" • David McAuley (RySG): The language is inelegant but in bylaws as I recall • Jorge Cancio (GAC Switzerland): it is very much like the Bylaws text - I'll defer to native speakers here... • Andrew Mack: of a party against others sounds best • Niels ten Oever proposes: This part of the bylaw draws the clear line between “respect” for human rights as a Core Value and any attempt to extend the Bylaw into requiring ICANN to enforce the human rights obligations of ICANN or any other party against other parties. • Group agrees with Niels text. • 2nd reading now finalized • Need to discuss next steps: do we want to share this part of the work with the plenary now, or prefer to work on the other document first? • Cheryl suggests sending this part to the plenary. • Group votes to decide whether to send or wait. QUorum in favor of sending the FoI to the plenary for discussion • ACTION (Niels): will take care of sending the FoI to the plenary 3. AOB • Leon congratulated the subgroup for the progress made.

1 0

Proposed agenda meeting November 22 - 19:00 UTC
by Niels ten Oever Dec. 2, 2016

Dec. 2, 2016

Dear all, I hope this email finds you well. Please find underneath and attached the proposed agenda. 1. Administrivia Roll call, absentees, SoIs, etc 2. Analysis and discussion on the progress of the drafting team working on the new proposal for FoI 1st reading continued f. ‘This Core Value does not create, and shall not be interpreted to create, any obligation on ICANN outside its Mission or beyond obligations found in applicable law’ g. ‘‘This Core Value does not obligate ICANN to enforce its human rights obligations or the human rights obligations of other parties, against other parties’ 2nd reading a.‘within the scope of its Mission’ b.‘within the scope of other Core Values’ (with minor changes as per discussion last week) c.‘respecting’ d. ‘internationally recognized human rights’ e. ‘as required by applicable law’ 3. AOB Please find also attached the current version of the working document. It can also be found here: https://docs.google.com/document/d/1ZJ02NHeKt9krBGd9V4q54_gl_RPcWGA9d8-WuV_… I hope that the people who brought up issues with the text under 'b.‘within the scope of other Core Values’' can check whether the current text works according to their suggestions, same with 'c.‘respecting’'. If not, it would be highly appreciated if people could suggest new text either on the google doc or on this list. All the 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

3 3

Co-Rapporteur stepping down
by Niels ten Oever Nov. 30, 2016

Nov. 30, 2016

Dear all, With sadness I am forwarding you the message I've received from Nigel underneath. Please join me in thanking Nigel for the work he has done for the subgroup as co-rapporteur. Luckily we can still benefit from his contributions as a participants in this subgroup. Best, Niels---------- Forwarded message ---------- From: Nigel Roberts <nigel(a)channelisles.net> Date: 29 Nov 2016 15:04 Subject: WS HR Group To: Niels ten Oever <lists(a)nielstenoever.net> Cc: > Administrative .. > > It's with a sense of regret and inevitability that I hereby notify you > that I have to step down from co-rapporteurship of the group. > > Whilst I am very happy to continue as a participant, and provide written > input, I have keenly felt the obligation to attend the teleconferences > which have been a big time constraint coupled with my work and personal > obligations. > > Taking this action will allow me to concentrate on content over the form > of meeting attendance. > > I trust you understand. > > If you need any help, however, please don't hesitate to ask. > > Kind regards > > > > N > > PS: Please feel free to forward this to the list . . > > > > > On 25/11/16 11:47, Niels ten Oever wrote: > > Dear all, > > > > With ICANN staff I have been trying to arrange our meeting days for the > > coming time. Unfortunately we were not able to secure our normal meeting > > date for next week, so next week we will be meeting on Friday December 2 > > 1900 UTC. > > > > For most of the other days we have been able to secure our default > > Tuesday 1900 UTC, sorry for the inconvenience. > > > > Invites will be sent out by staff on Monday. > > > > I hope you're all having a great weekend. > > > > Best, > > > > Niels > >

1 0

Meeting next week on Friday instead of Tuesday (19:00 UTC)
by Niels ten Oever Nov. 25, 2016

Nov. 25, 2016

Dear all, With ICANN staff I have been trying to arrange our meeting days for the coming time. Unfortunately we were not able to secure our normal meeting date for next week, so next week we will be meeting on Friday December 2 1900 UTC. For most of the other days we have been able to secure our default Tuesday 1900 UTC, sorry for the inconvenience. Invites will be sent out by staff on Monday. I hope you're all having a great weekend. 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

Notes, recordings and transcript for WS2 Human Rights Subgroup Meeting # 13 | 22 November
by MSSI Secretariat Nov. 23, 2016

Nov. 23, 2016

Hello all, Please see the notes, recordings, and transcript for the CCWG Accountability WS2 Human Rights Subgroup Meeting #13 here; https://community.icann.org/x/lI7DAw A copy of the action items and notes may be found below. Thank you. With kind regards, Brenda Brewer MSSI Projects & Operations Assistant ICANN - Internet Corporation for Assigned Names and Numbers Action Items · ACTION (David McAuley): have the questions being distributed to our list, just to keeping track of themAction Items · ACTION (Drafting team) come up with new proposal for 2nd reading. · ACTION (drafting team): come up with new proposal Notes 1. Administrivia | Roll call, absentees, SoIs, etc. · No audio only. · No SOI updates · No updates to agenda · Legal questions now submitted to ICANN Legal ACTION (David McAuley): have the questions being distributed to our list, just to keeping track of them 2. Analysis and discussion on the progress of the drafting team working on the new proposal for FoI 1st reading continued f. ‘This Core Value does not create, and shall not be interpreted to create, any obligation on ICANN outside its Mission or beyond obligations found in applicable law’ * Avri: The interpretation here seems stronger than the initial text. * Greg: I don't see that as stronger. * Jorge Cancio (GAC Switzerland): this sentence is about "obligations" - it does not prevent ICANN from "taking HR into account" beyond that * Group approves this interpretation. g. ‘‘This Core Value does not obligate ICANN to enforce its human rights obligations or the human rights obligations of other parties, against other parties’ · Kavouss: second part ("or coerce third parties" ) is not quite clear - could we define the language being used ("third parties": who are these)? · David: agrees, there appears to be a disconnect between the 1st and 2nd part · Greg: implicitely refers back to Ruggie's principle · Tatiana Tropina: so I don't think anyone argues about concepts but just about the clarity of this text · David: I think the problem starts with the use of the word "impose" · Kavouss: "of those third parties" also needs to be clarified · Avri: does it mean that there should be compliance of contracted parties? · Jorge Cancio (GAC Switzerland): "without prejudice to what is stated elsewhere"? · Niels ten Oever: Maybe this: This part of the bylaw draws the clear line between “respect” for human rights as a Core Value and any attempt to extend the Bylaw into requiring ICANN to take enforcement action to any other party or ask other parties to take enforcement action. · ACTION (Drafting team) come up with new proposal for 2nd reading. 2nd reading · Kavouss: suggest we wait till next meeting before we do the 2nd reading. · Niels: 1st reading was done during last meeting, there was time between the 2 readings. a.‘within the scope of its Mission’ · agreement from the group b.‘within the scope of other Core Values’ (with minor changes as per discussion last week) · Kavouss: replace "described" by "stipulated" · Greg: we don't nee "legal" before "hierarchy" in the last paragraph · Jorge: hierarchy could be moral, pragmatical etc. This is a legal test, so it should be a "legal hierarchy", · Greg: I disagree that it's a legal balancing test. · Tatiana: I agree, it's not a legal test, and there is no hierarchy between core values. · Jorge: why are we reopening this discussion? if so, there are other I could reopen too. · Tatiana: We could say that there is no pre-existing hierarchy, or no predetermined hierarchy. · Kavouss Arasteh: Retention or otherwise of term"Legal" does not create any problem .However, it retention may give the impression that there are other types of hierarchy than legal,thus I suggest to remove it ACTION (drafting team): come up with new proposal c.‘respecting’ · Not discussed d. ‘internationally recognized human rights’ · Not discussed e. ‘as required by applicable law’ · Not discussed 3. AOB

1 0

FW: My suggestions for tweaking HR Sub-Team questions after yesterday's Legal team call
by McAuley, David Nov. 22, 2016

Nov. 22, 2016

Below is the copy of the mail I sent to Leon re HR questions - I had noted some clarifications to what legal team was considering and Leon asked me to take a pass at clarifying. David From: McAuley, David Sent: Friday, November 18, 2016 9:43 AM To: 'ccwg-accountability5(a)icann.org' Subject: My suggestions for tweaking HR Sub-Team questions after yesterday's Legal team call Hi Leon and legal team, Here are the question we addressed yesterday with respect to the HR sub-team: 1. What is the definition ICANN legal uses for 'applicable law'? 2. What does the term "Respect" mean according to the bylaws (in relation to Core Values)? 3. What is the relationship between core values and commitments in general; and the HR core value and commitments in particular? 4. How does the balancing progress between core values, as described in the bylaws, take place? Is it documented? On the call I noted some comments in the nature of clarification and Leon asked if I would suggest some revisions on list and here below are my thoughts. First, however, two important points. One, I will separately send a copy of this memo to Niels ten Oever, one of the rapporteurs of the HR Sub-Team who is handling this matter for the sub-team. I will ask Niels to contact us through Leon rather quickly if he has any issue with any of this. And, two, recall that I am a member of the HR Sub-team and have taken an active position on the nature of "respect" and the meaning of "applicable law" in the team. There are other views than mine and they have been reasonably expressed - the discussion is not ended. So I come at this with a point of view, nonetheless I have endeavored to make these "tweaked" questions fair and in keeping with the questions originally posed by Niels. Here is how I suggest we handle these questions and forward them to ICANN legal: 1. With respect to ICANN legal's understanding of the definition of "applicable law": a. Has ICANN legal developed an understanding of the meaning of the term "applicable law"? b. If so, does that understanding apply in the context of the new bylaw at Article 1.2(b)(viii)? c. Would the following definition of "applicable law," currently under consideration by the CCWG WS2 Sub-Team on Human Rights, be consistent with either or both of those?: a. <Quote>: Applicable law refers to the body of law that binds ICANN at any given time, in any given circumstance and in any relevant jurisdiction. It consists of statutes, rules, regulations, etcetera, as well as judicial opinions, where appropriate. It is a dynamic concept inasmuch as laws, regulations, etcetera, change over time. Applicable law can have disparate impacts on ICANN around the globe: for example, if ICANN employs personnel in different jurisdictions then it must observe the appropriate labour laws in those various locales. Applicable law is thus a large body of law that eludes our ability to catalogue, but it is ascertainable in the context of a specific question or issue. <Quote> d. Please share the applicable understanding(s). 2. With respect to questions 2 through 4 above I suggest we leave the questions as they are but introduce each of them with this phrase: "In the view of ICANN legal,". Best regards, David David McAuley International Policy Manager Verisign Inc. 703-948-4154

5 6

OECD HR guidlines
by avri doria Nov. 16, 2016

Nov. 16, 2016

Hi, During our last call, Markus spoke of the OECD guidelines for Multinational enterprises. I got the pointer for the doc from him and extracted the relevant pages. They are attached. avri --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 1

Notes, recordings and transcript for WS2 Human Rights Subgroup Meeting #12 | 15NOV16
by MSSI Secretariat Nov. 15, 2016

Nov. 15, 2016

Hello all, Please see the notes and details for the CCWG Accountability WS2 - Human Rights Subgroup Meeting #12 here; https://community.icann.org/x/jI7DAw The notes are also listed below. Thank you! Kind Regards, Yvette Guigneaux Multi-Stakeholder & Strategic Initiative Assistant ICANN | Internet Corporation for Assigned Names & Numbers 12025 Waterfront Drive, Playa Vista, CA 90094 yvette.guigneaux(a)icann.org<mailto:yvette.guigneaux@icann.org> | www.icann.org<http://www.icann.org/> Notes Human Rights Meeting #12 (15 November @ 19:00 UTC) Notes (including relevant parts of chat): 1. Administrivia · Apologies: Anne Aikman-Scalese, Matthew Shears, Tatiana Tropina · Roll call will be taken from AC room. · No audio only participants. · 3 open questions to ICANN legal. ACTION (Staff): follow-up with ICANN Legal - Karen: Answers will be provided next week. · Cheryl Langdon-Orr (CLO): small update to SOI mine is yet to reflect my new role as ALAC Liaison to the GNSO Council update later today · David McAuley: I think I will need to update my SOI as well as I am taking over as Rapporteur of IRP IoT - not sure if that will require a new SOI but should mention it here just in case 2. Analysis and discussion on the progress of the drafting team working on the new proposal for FoI a.‘within the scope of its Mission’ · "core value" should be capitalized · David McAuley: My comment - this section appears fine · No other comments from the group on this section. b.‘within the scope of other Core Values’ · Discussed the balancing process: · avri doria: In this balancing can a core value be violated? · The FoI says: "The result of a balancing-test cannot cause ICANN to violate any Commitment, as Commitments are binding." · David McAuley: where one core value is honored another might be partially honored or not honored in a balancing test it seems. · Chris LaHatte: the usual test for breaches of human rights is one of proportionality. · Jorge Cancio (GAC Switzerland): Normally in a balancing test you need to address each and every factor (here each core value) and motivate how this is done and with what result. · John Laprise: So, on a given decision/issue. could the community demand of ICANN an explanation of how a particular core value was weighed/applied/respected? · Pending response from ICANN legal on how the balancing works · Jorge Cancio (GAC Switzerland): Let's also wait for ICANN Legal and their take on how commitments and core values are meant to work together · Might require additional text, after responses are received from Legal ICANN. · Suggestion to change "cannot" into "may not" / ""should not" / "shall not" / "must not" . "Must not" is retained, to be further discussed on the list if necessary. · Suggestion to add references next to quotations. c.‘respecting’ · No comments from the group. d. ‘internationally recognized human rights’ · No comments from the group. e. ‘as required by applicable law’ · Daniel Appelman: When read with the "respecting" explanation, this implies that ICANN has no obligation to respect human rights except where national laws directly place ICANN under those obligations. · avri doria: David does that not make this meaningless? or rather it just says forget about HR, just obey the law? · Jorge Cancio (GAC Switzerland): I had similar concerns to those expressed by Avri. But I feel the Core Value not only restricts ICANN to avoid violating HR. It also brings with it a positive element to be guided by internationally recognised human rights in its actions · Greg Shatan: The point is to abide by the laws but still respect Human Rights. · Daniel Appelman: ICANN respecting human rights "as required by applicable law" makes little sense when the next section says that mostly only States are required to respect human rights. · avri doria: if there is no law protecting a hr, do we still need to care about the hr. · David McAuley: it's not a matter of not caring, but a matter of observing the law · Erich Schweighofer: ICANN's policies should respect human rights ... but implementation may conflict with applicable law. Sad but reality, contradictions have to be solved by HR institutions. · Jorge: other areas of the FoI cover the obligation of ICANN to respect HR. · Markus: suggestion to refer to the OECD guidelines. f. ‘This Core Value does not create, and shall not be interpreted to create, any obligation on ICANN outside its Mission or beyond obligations found in applicable law’ · not discussed g. ‘‘This Core Value does not obligate ICANN to enforce its human rights obligations or the human rights obligations of other parties, against other parties’ · not discussed 3. AOB · WIll continue this reading on the list and next week. · Action Items ACTION (Staff): follow-up with ICANN Legal - Karen: Answers will be provided next week.

1 0