[cc-humanrights] FoI discussion
Motoko Aizawa
motoko.aizawa at ihrb.org
Tue May 17 13:02:51 UTC 2016
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 at 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 at 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-to-Respect-Human-Rights.pdf
> >
> > 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.pdf
> >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 at icann.org
> > <mailto:cc-humanrights-request at icann.org>> wrote:
> >
> > Send cc-humanrights mailing list submissions to
> > cc-humanrights at icann.org <mailto:cc-humanrights at 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 at icann.org
> > <mailto:cc-humanrights-request at icann.org>
> >
> > You can reach the person managing the list at
> > cc-humanrights-owner at icann.org
> > <mailto:cc-humanrights-owner at 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 at icann.org
> > <mailto:maryam.bakoshi at icann.org>>
> > To: Human Rights <cc-humanrights at icann.org
> > <mailto:cc-humanrights at icann.org>>, ICANN Policy Calendar
> > <PolicyCalendar at icann.org <mailto:PolicyCalendar at icann.org>>
> > Cc: matteo lucchetti <matluc at hotmail.com
> > <mailto:matluc at hotmail.com>>, Herb Waye
> > <herb.waye at icann.org <mailto:herb.waye at icann.org>>, Niels
> > ten Oever <niels at digitaldissidents.org
> > <mailto:niels at digitaldissidents.org>>
> > Subject: [cc-humanrights] REMINDER: CCWP ICANN and Human Rights |
> > Tuesday 17 May 2016 | 13:00 UTC
> > Message-ID:
> >
> > <7ddc6bc5d2dc4231aa07c4ea65fcedc9 at PMBX112-E1-VA-2.PEXCH112.ICANN.ORG
> > <mailto:
> 7ddc6bc5d2dc4231aa07c4ea65fcedc9 at 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 at icann.org
> > <mailto:maryam.bakoshi at icann.org><mailto:maryam.bakoshi at icann.org
> > <mailto:maryam.bakoshi at icann.org>>
> > Mobile: +44 7737 698036 <tel:%2B44%207737%20698036>
> > Skype: maryam.bakoshi.icann
> >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
> > <
> http://mm.icann.org/pipermail/cc-humanrights/attachments/20160516/86c9d81c/attachment.html
> >
> > -------------- next part --------------
> > A non-text attachment was scrubbed...
> > Name: not available
> > Type: text/calendar
> > Size: 8651 bytes
> > Desc: not available
> > URL:
> > <
> http://mm.icann.org/pipermail/cc-humanrights/attachments/20160516/86c9d81c/attachment.ics
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > cc-humanrights mailing list
> > cc-humanrights at icann.org <mailto:cc-humanrights at icann.org>
> > https://mm.icann.org/mailman/listinfo/cc-humanrights
> >
> >
> > End of cc-humanrights Digest, Vol 18, Issue 5
> > *********************************************
> >
> >
> >
> >
> > --
> > Corinne Cath
> >
> >
> > 'The management of normality is hard work'
> >
> >
> >
> > _______________________________________________
> > cc-humanrights mailing list
> > cc-humanrights at icann.org
> > https://mm.icann.org/mailman/listinfo/cc-humanrights
> >
>
>
> _______________________________________________
> cc-humanrights mailing list
> cc-humanrights at icann.org
> https://mm.icann.org/mailman/listinfo/cc-humanrights
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cc-humanrights/attachments/20160517/eea941bb/attachment-0001.html>
More information about the cc-humanrights
mailing list