<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] FW: Conduct at ICANN Meetings
- To: GNSO Council List <council@xxxxxxxxxxxxxx>
- Subject: [council] FW: Conduct at ICANN Meetings
- From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
- Date: Wed, 4 May 2016 14:06:51 +0000
- Accept-language: en-US
- Authentication-results: gnso.icann.org; dkim=none (message not signed) header.d=none;gnso.icann.org; dmarc=none action=none header.from=godaddy.com;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureservernet.onmicrosoft.com; s=selector1-godaddy-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=owoMSJ3ZONs0OZ561gAwo0WtY+bL8XCLLjmz4JDGQTA=; b=E4gU09nOfYQENhotzMQh7pV+TW4NYvf5kDWtvOYRXpB7n/fmZXlNtH0/KrQ1Nmxc2kOzaX+ioybFF+JLuzJ5kfmXs83LwyVzs9oG2Dz1IUSidAlnVJbmznontyPmCBJyvv3pco3GVJMQJhF9LRYBG8bkgskYA+hmkVvPt4DrW/o=
- In-reply-to: <C90DB0C8-BD82-4D26-8B75-A33D7DB7AB49@icann.org>
- List-id: council@xxxxxxxxxxxxxx
- References: <C90DB0C8-BD82-4D26-8B75-A33D7DB7AB49@icann.org>
- Sender: owner-council@xxxxxxxxxxxxxx
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:23
- Thread-index: AQHRpguGV826lfbmhkKtG7pBOn5eLJ+ofFQA
- Thread-topic: Conduct at ICANN Meetings
- User-agent: Microsoft-MacOutlook/14.5.6.150930
Council Colleagues -
Please see the note below from David Olive, regarding conduct / harassment at
ICANN events. Thanks to all who worked on this, either via the Council or your
SG/C contributions. I expect there will be a need for additional volunteers as
this process moves forward.
Thanks-
J.
From: David Olive <david.olive@xxxxxxxxx<mailto:david.olive@xxxxxxxxx>>
Date: Wednesday, May 4, 2016 at 8:47
Subject: Conduct at ICANN Meetings
Dear Community Leaders:
Thank you for continuing to provide ICANN with your and your respective group's
(SO/AC/SG/Constituency/RALO) input concerning the appropriate approach for
ICANN's development of standards, policies and processes regarding allegations
of harassment at future ICANN meetings. It would seem that most community
groups prefer the third option that I had suggested following our last call on
12 April, i.e.:
"Do not convene a formal group, but leave it to each community
(SO/AC/SG/Constituency/RALO) and individual participants to provide suggestions
to, and comment on possible recommendations from, the Board as a result of
further Board discussions and expert consultations on the topic."
The Business Constituency (BC), in supporting this option, nevertheless
suggested refining it such that the process will be for ICANN staff, in
consultation with experts, to draft recommendations that are posted for public
comments. Following a review of public comments received, the proposal will be
sent to the Board for its approval.
If there are no objections, ICANN will proceed along the lines of the third
option as refined by the BC. We will also inform the Board that this is the
community's preference.
A number of specific exemplars that can be looked at by ICANN in drafting the
proposal has been provided by various Community leaders and members, either as
part of group calls on the topic or individually. These include:
· The Ada Initiative:
https://adainitiative.org/continue-our-work/ada-initiative-event-anti-harassment-policy/
· The IETF (Internet Engineering Task Force):
https://www.ietf.org/iesg/statement/ietf-anti-harassment-policy.html
· The Internet Governance Forum:
http://www.intgovforum.org/cms/aboutigf/igf-code-of-conduct
· The NTEN (Nonprofit Technology Network) :
http://www.nten.org/ntc/about-the-ntc/code-of-conduct/
· RIPE (Réseaux IP Européens):
https://ripe72.ripe.net/on-site/code-of-conduct/
· The United Nations and its specialized agencies' anti-harassment staff
policies (some of these are collected here:
http://www.ficsa.org/component/sobipro/?task=download.file&fid=37.1329&sid=1266&Itemid=0
In addition, the GNSO Chair and Vice Chairs sent a letter on behalf of the GNSO
Council to Akram Atallah, our President and CEO, on 27 April 2016. The letter
suggested a number of considerations to be taken into account in developing an
anti-harassment policy and procedure for the Community. A copy of the letter
can be viewed at:
http://gnso.icann.org/en/correspondence/bladel-to-atallah-25apr16-en.pdf.
I expect that these, and other similar resources, will provide a starting point
for ICANN to begin work on a draft proposal, for which we will seek expert
advice as recommended by the Community, as well as Community input. The Board
is expected to discuss this matter during its workshop in Amsterdam on 13-15
May 2016.
In addition, and in parallel, the Board is looking at enhancements to the
language in ICANN's Expected Standards of Behavior, so as to ensure an overall
awareness that ICANN does not condone harassment or other inappropriate conduct
by or directed at members of the Community.
Thank you.
With best regards,
David
David A. Olive
Senior Vice President, Policy Development Support
General Manager, ICANN Regional Headquarters -Istanbul
Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349 Fulya, Besiktas, Istanbul
Internet Corporation for Assigned Names and Numbers (ICANN)
Direct Line: +90.212.999.6212
Mobile: + 1. 202.341.3611
Mobile: +90.533.341.6550
Email: david.olive@xxxxxxxxx<mailto:david.olive@xxxxxxxxx>
www.icann.org
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|