<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>Oh yes!!!<br>
-- <br>
Sent from my mobile. Please excuse brevity and typos.<br><br><div class="gmail_quote">On February 14, 2018 6:41:28 PM EST, Evan Leibovitch <evanleibovitch@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="auto">Understood, and thanks for the clarification. <div dir="auto"><br></div><div dir="auto">Perhaps the idea of warming against selective austerity might make it into the ALAC response in any case. <br><div dir="auto"><br><div data-smartmail="gmail_signature" dir="auto">- Evan (on mobile) </div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Feb 14, 2018 6:23 PM, "Alan Greenberg" <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Evan, please note that this proposal is not from ICANN Organization
(current name for staff) or the Board. It is from a number of the
community members of the CCWG-Accountability group looking at
recommendation to make to the AC/SOs and the Board.<br><br>
Alan<br><br>
At 14/02/2018 01:54 PM, Evan Leibovitch wrote:<br>
<blockquote type="cite" class="m_6346202628808241217cite">Fully agree. It is astounding
that ICANN wants to consider growing its bureaucracy just as budgets are
shrinking. <br><br>
Perhaps our advice should encourage the Board and senior staff to show
leadership to its community as it moves to an increasing culture of
austerity. Before ICANN asks its volunteers to sacrifice (through reduced
support and/or increased workload) it should engage in some of its own.
<br><br>
(Also funny how ICANN wants to take diversity seriously only AFTER it has
set in place policies - on gTLD expansion and the concept of domains as
rental property, for instance - that can't really be undone even if a
newly-diverse community disagrees with that path.) <br><br>
- Evan<br><br>
<br>
On Feb 14, 2018 12:46 PM, "Kan Kaili"
<<a href="mailto:kankaili@gmail.com" target="_blank">kankaili@gmail.com</a>>
wrote:<br>
<dl>
<dd><font size="2">Hi,<br>
</font>
</dd><dd> <br>
</dd><dd><font size="2">I fully agree with the comments initiated by Alan and
the points by Maureen, Holly and others.<br>
</font>
</dd><dd> <br>
</dd><dd><font size="2">That is, ALAC should issue a statement against
establishing this office. I believe comments of Holly, Maureen and
others would suffice as the main body of the statement.<br>
</font>
</dd><dd> <br>
</dd><dd><font size="2">Kaili<br>
</font>
</dd><dd> <br>
</dd><dd> <br>
</dd><dd> <br>
<dl>
<dd>----- Original Message ----- <br>
</dd><dd>From: <a href="mailto:maureen.hilyard@gmail.com" target="_blank">Maureen
Hilyard</a> <br>
</dd><dd>To: <a href="mailto:h.raiche@internode.on.net" target="_blank">Holly Raiche</a>
<br>
</dd><dd>Cc: <a href="mailto:alac@atlarge-lists.icann.org" target="_blank">ALAC</a> ;
<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">Alan Greenberg</a> <br>
</dd><dd>Sent: Wednesday, February 14, 2018 9:19 AM<br>
</dd><dd>Subject: Re: [ALAC] IMPORTANT: PAPER ON OFFICE OF DIVERSITY
PUBLIC COMMENTS<br><br>
</dd><dd>+1 Holly<br><br>
</dd><dd>On Tue, Feb 13, 2018 at 3:07 PM, Holly Raiche
<<a href="mailto:h.raiche@internode.on.net" target="_blank">
h.raiche@internode.on.net</a>> wrote:<br>
<dl>
<dd>Folks <br><br>
</dd><dd>Part of me absolutely supports any moves that support
diversity. At one point in my life, I headed up the Equal
Opportunity Unit in the Aust. Broadcasting Corporation so diversity was
my job. <br>
</dd><dd>Putting that aside, I have serious doubts about the concept in this
context. <br><br>
</dd><dd>If they talking about just ICANN staff, there is already an ICANN HR
function that would (or should) be charged with addressing the issue.
<br><br>
</dd><dd>If they talking about the various organisations that attend the
SOs/ACs? I have even more concern. Just for starters, it is up to
each SO/AC - and then individual members within each SO/AC as to who
participates. Is ICANN seriously going to tell GAC members that some of
them must send more women representatives/more Asian members/more members
from non-English speaking backgrounds? And who is going to tell
each registry/registrar whom they can send to represent them!
<br><br>
</dd><dd>If the idea is to have diversity in the make-up of ICANN committees,
I would hope the first basis for selection is qualifications for the
task.<br><br>
</dd><dd>In short, I support Alan’s comments. If the concept is
diversity WITHIN ICANN staff, it is covered by HR. Otherwise, I
have real doubts about the concept, other than - at best -it could be
just a score card. <br><br>
</dd><dd>Holly<br><br>
<br><br>
<br>
</dd><dd>On 14 Feb 2018, at 11:18 am, Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>
> wrote:<br><br>
<blockquote type="cite" class="m_6346202628808241217cite">
<dd>I would like to call your attention to this paper that was just
circulated by the CCWG-Accountability WS2 on Diversity.<br><br>
</dd><dd>The ALAC was silent on the question of an Office of Diversity (OOD)
that was mentioned in the draft recommendations (see
<a href="https://community.icann.org/x/Z5tEB" target="_blank">
https://community.icann.org/x/<wbr>Z5tEB</a>)<br><br>
</dd><dd>As important as diversity is, I find it troublesome that ICANN might
be dedicating more bureaucracy to it. As I noted in my recent comments on
the Specific Reviews Operating Standards (
<a href="https://mm.icann.org/pipermail/comments-reviews-standards-17oct17/2018q1/000008.html" target="_blank">
https://mm.icann.org/<wbr>pipermail/comments-reviews-<wbr>standards-17oct17/2018q1/<wbr>000008.html</a>
), I find that for the best of reasons, ICANN is building more and more
complex process, rules and bureaucracy. At a time when it is clear we are
going to have increasing budget constraint, this must be controlled. If
we consider issues such as this as sacred , then we will see more and
more other more discretionary budgets cut (and I am predicting that if we
don't change our philosophy, budget issues will get MUCH worse).<br>
<br>
</dd><dd>According to the original recommendations document (
<a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-draft-recs-diversity-26oct17-en.pdf" target="_blank">
https://www.icann.org/en/<wbr>system/files/files/ccwg-acct-<wbr>ws2-draft-recs-diversity-<wbr>26oct17-en.pdf</a>
): The role of this office would be to independently support, record and
keep track of issues including complaints from the community on diversity
issues within the organization.<br><br>
</dd><dd>I presume that by "organization" the document means all of
ICANN (ICANN Organization as the staff are now known, the volunteer
community and the Board). For ICANN Organization, I see this as falling
directly under Human Resources and the Complaints Officer. For the
volunteer part of ICANN, and the Board, I think it quite reasonable to
keep records but that does not warrant a staffed office. Selection of
volunteers is not done centrally, and complaints presumably should go to
the Ombudsman.<br><br>
</dd><dd>Should the ALAC issue a further statement on this? And if so,
what are your views?<br><br>
</dd><dd>Alan<br><br>
<br>
<blockquote type="cite" class="m_6346202628808241217cite">
<dd>From: Bernard Turcotte
<<a href="mailto:turcotte.bernard@gmail.com" target="_blank">
turcotte.bernard@gmail.com</a>><br>
</dd><dd>Date: Mon, 12 Feb 2018 14:28:23 -0500<br>
</dd><dd>To: ws2-diversity
<<a href="mailto:ws2-diversity@icann.org" target="_blank">ws2-diversity@icann.org</a>
><br>
</dd><dd>Subject: [Ws2-diversity] CCWG-Accountability-WS2-<wbr>Diversity - PAPER ON
OFFICE OF DIVERSITY PUBLIC COMMENTS<br><br>
</dd><dd>All,<br><br>
</dd><dd>As promised at the last meeting of the diversity sub-group please
find below and attached the document prepared by Fiona and Rafik on this
topic.<br><br>
</dd><dd>Bernard Turcotte<br>
</dd><dd>ICANN Staff Support to the CCWG-Accountability-WS2<br><br>
</dd><dd>For Fiona and Rafik.<br><br>
<div align="center">
</div></dd><dd>DIVERISTY SUB-GROUP<br>
</dd></blockquote></dd></blockquote></dd></dl></dd></dl></dd></dl></blockquote></div>
<br>
<div align="center"><br>
<dd> <br>
</dd></div>
<br>
<div align="center">
<dd>PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS<br>
</dd></div>
<br>
<dd> <br><br>
</dd><dd>Preamble:<br>
<br>
</dd><dd> <br>
<br>
</dd><dd>The Diversity sub-group presented a report for public comments that
presented diversity at ICANN identified by a number of elements by which
diversity may be characterized, measured and reported. The report was
informed by feedback from ICANN Supporting Organization(SO)/Advisory
Committee (AC)/groups through a Diversity Questionnaire. In the report
the Sub-group proposes a number of recommendations by which ICANN may
define, measure, report, support and promote diversity. It also indicated
that there was a lack of consensus on the establishment on an office of
diversity and sought to receive public comments on the position of the
office of diversity. <br><br>
</dd><dd> <br><br>
</dd><dd>Summary of Responses from Public Comments:<br>
<br>
</dd><dd>
</dd><dd>Total of 15 comments <br>
</dd><dd>
<ul>
<ul>
<li>6 had no comments on an office of diversity
</li><li>3 supported an office of diversity or a panel
</li><li>3 supported an office of diversity
</li><li>3 rejected the notion of an office of diversity.
</li></ul>
</ul><br>
</dd><dd>
</dd><dd>Breakdown by major categories <br>
</dd><dd>
<ul>
<ul>
<li>7 SO/ACs/Board (those which will have to approve the WS2 final
report):
</li></ul>
</ul><br>
</dd><dd>
<ul>
<ul>
<ul>
<li>4 had no comments
</li><li>3 Rejected the notion of an office of diversity
</li></ul>
</ul>
</ul><br>
</dd><dd>
<ul>
<ul>
<li>2 Governments:
</li></ul>
</ul><br>
</dd><dd>
<ul>
<ul>
<ul>
<li>1 had no comments on an office of diversity
</li><li>1 supported an office of diversity
</li></ul>
</ul>
</ul><br>
</dd><dd>
<ul>
<ul>
<li>6 Individuals/Associations:
</li></ul>
</ul><br>
</dd><dd>
<ul>
<ul>
<ul>
<li>1 had no comments on an office of diversity
</li><li>3 supported an office of diversity or a panel
</li><li>2 supported an office of diversity
</li></ul>
</ul>
</ul><br>
</dd><dd> <br><br>
</dd><dd> <br><br>
</dd><dd>Summary of Positions relating to the OOD from Public Comments:<br>
<br>
</dd><dd> <br>
<br>
</dd><dd>1. Establishment of an office of
diversity or a panel similar to what is proposed in the Ombuds
recommendations.<br><br>
</dd><dd>2. Establishment of an office of
diversity<br><br>
</dd><dd>3. Rejection of an office of diversity
in favour of staff performing this work. <br><br>
</dd><dd> <br><br>
</dd><dd>Required Actions:<br>
<br>
</dd><dd>The Sub-group on diversity does not have one solid position from the
public comments but has instead received a number of options that need to
be discussed further and weighed in order to determine how oversight of
diversity can be pursued. <br><br>
</dd><dd> <br><br>
</dd><dd>Content-Type: application/pdf; name="Office Of Diversity
OptionsV1.2.pdf"<br>
</dd><dd>Content-Disposition: attachment; <br>
</dd><dd>
filename="Office Of Diversity OptionsV1.2.pdf"<br>
</dd><dd>X-Attachment-Id: f_jdkm12g20<br>
</dd><dd>X-Microsoft-Exchange-<wbr>Diagnostics:<br>
</dd><dd>
1;YQXPR0101MB1589;27:<wbr>5Mxd449bwS/HOp/<wbr>iuqOwk4pTsHsOLwp4Urd2lAQC+<wbr>LxH4sZOpA5H5EWy2W2rBs7gToTigha<wbr>GdY2nGhYw4nbnkMhHj+<wbr>A5OHljcCMG4yzy5c5s6+66WnCi//<wbr>rOuNRtAQcG<br>
</dd><dd>X-Microsoft-Antispam-Message-<wbr>Info:<br>
</dd><dd>
ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6<wbr>QwBeeGtAqZw+OgOzfrvYEk+<wbr>AotEDu2+rNWAMq6958Jvp+c+<wbr>glyW7W4EQn8cXBw9UBrowrCZ+<wbr>P5ytgQVR8nbfFnqRajG4VJuLLwZc60<wbr>22IzI09Frtk3p2uxpg==<br>
<br>
</dd><dd>Content-Type: text/plain; charset="us-ascii"<br>
</dd><dd>Content-Transfer-Encoding: 7bit<br>
</dd><dd>Content-Disposition: inline<br>
</dd><dd>X-Microsoft-Exchange-<wbr>Diagnostics:<br>
</dd><dd>
1;YQXPR0101MB1589;27:<wbr>5Mxd449bwS/HOp/<wbr>iuqOwk4pTsHsOLwp4Urd2lAQC+<wbr>LxH4sZOpA5H5EWy2W2rBs7gToTigha<wbr>GdY2nGhYw4nbnkMhHj+<wbr>A5OHljcCMG4yzy5c5s6+66WnCi//<wbr>rOuNRtAQcG<br>
</dd><dd>X-Microsoft-Antispam-Message-<wbr>Info:<br>
</dd><dd>
ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6<wbr>QwBeeGtAqZw+OgOzfrvYEk+<wbr>AotEDu2+rNWAMq6958Jvp+c+<wbr>glyW7W4EQn8cXBw9UBrowrCZ+<wbr>P5ytgQVR8nbfFnqRajG4VJuLLwZc60<wbr>22IzI09Frtk3p2uxpg==<br>
<br>
</dd><dd>______________________________<wbr>_________________<br>
</dd><dd>Ws2-diversity mailing list<br>
</dd><dd><a href="mailto:Ws2-diversity@icann.org" target="_blank">Ws2-diversity@icann.org</a>
<br>
</dd><dd>
<a href="https://mm.icann.org/mailman/listinfo/ws2-diversity" target="_blank">
https://mm.icann.org/mailman/<wbr>listinfo/ws2-diversity</a></dd></blockquote>
<dd><Office Of Diversity
OptionsV1.2.pdf>______________<wbr>______________________________<wbr>___<br>
</dd><dd>ALAC mailing list<br>
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
</dd><dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org" target="_blank">http://www.atlarge.icann.org</a>
<br>
</dd><dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a>
</dd><br><br>
<dd>______________________________<wbr>_________________<br>
</dd><dd>ALAC mailing list<br>
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
</dd><dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org" target="_blank">http://www.atlarge.icann.org</a>
<br>
</dd><dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a>
<br><br>
</dd><br>
<hr>
<dd>______________________________<wbr>_________________<br>
</dd><dd>ALAC mailing list<br>
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
</dd><dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org" target="_blank">http://www.atlarge.icann.org</a>
<br>
</dd><dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a>
<br><br>
</dd><br>
<dd>______________________________<wbr>_________________<br>
</dd><dd>ALAC mailing list<br>
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
</dd><dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org" target="_blank">http://www.atlarge.icann.org</a>
<br>
</dd><dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a>
<br>
</dd></div>
</div>
</blockquote></div></body></html>