- ALAC - lists.icann.org

IMPORTANT: PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS
by Alan Greenberg Feb. 19, 2018

Feb. 19, 2018

I would like to call your attention to this paper that was just circulated by the CCWG-Accountability WS2 on Diversity. The ALAC was silent on the question of an Office of Diversity (OOD) that was mentioned in the draft recommendations (see https://community.icann.org/x/Z5tEB) 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 (https://mm.icann.org/pipermail/comments-reviews-standards-17oct17/2018q1/00…) 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). According to the original recommendations document (https://www.icann.org/en/system/files/files/ccwg-acct-ws2-draft-recs-divers…) 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. 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. Should the ALAC issue a further statement on this? And if so, what are your views? Alan >From: Bernard Turcotte <turcotte.bernard(a)gmail.com> >Date: Mon, 12 Feb 2018 14:28:23 -0500 >To: ws2-diversity <ws2-diversity(a)icann.org> >Subject: [Ws2-diversity] CCWG-Accountability-WS2-Diversity - PAPER >ON OFFICE OF DIVERSITY PUBLIC COMMENTS > >All, > >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. > >Bernard Turcotte >ICANN Staff Support to the CCWG-Accountability-WS2 > >For Fiona and Rafik. > >DIVERISTY SUB-GROUP > > > >PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS > > > >Preamble: > > > >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. > > > >Summary of Responses from Public Comments: > > > * Total of 15 comments > > > * 6 had no comments on an office of diversity > * 3 supported an office of diversity or a panel > * 3 supported an office of diversity > * 3 rejected the notion of an office of diversity. > > > * Breakdown by major categories > > > * 7 SO/ACs/Board (those which will have to approve the WS2 final report): > > > * 4 had no comments > * 3 Rejected the notion of an office of diversity > > > * 2 Governments: > > > * 1 had no comments on an office of diversity > * 1 supported an office of diversity > > > * 6 Individuals/Associations: > > > * 1 had no comments on an office of diversity > * 3 supported an office of diversity or a panel > * 2 supported an office of diversity > > > > > >Summary of Positions relating to the OOD from Public Comments: > > > >1. Establishment of an office of diversity or a panel similar >to what is proposed in the Ombuds recommendations. > >2. Establishment of an office of diversity > >3. Rejection of an office of diversity in favour of staff >performing this work. > > > >Required Actions: > >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. > > > >Content-Type: application/pdf; name="Office Of Diversity OptionsV1.2.pdf" >Content-Disposition: attachment; > filename="Office Of Diversity OptionsV1.2.pdf" >X-Attachment-Id: f_jdkm12g20 >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:5Mxd449bwS/HOp/iuqOwk4pTsHsOLwp4Urd2lAQC+LxH4sZOpA5H5EWy2W2rBs7gToTighaGdY2nGhYw4nbnkMhHj+A5OHljcCMG4yzy5c5s6+66WnCi//rOuNRtAQcG >X-Microsoft-Antispam-Message-Info: > >ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6QwBeeGtAqZw+OgOzfrvYEk+AotEDu2+rNWAMq6958Jvp+c+glyW7W4EQn8cXBw9UBrowrCZ+P5ytgQVR8nbfFnqRajG4VJuLLwZc6022IzI09Frtk3p2uxpg== > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:5Mxd449bwS/HOp/iuqOwk4pTsHsOLwp4Urd2lAQC+LxH4sZOpA5H5EWy2W2rBs7gToTighaGdY2nGhYw4nbnkMhHj+A5OHljcCMG4yzy5c5s6+66WnCi//rOuNRtAQcG >X-Microsoft-Antispam-Message-Info: > >ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6QwBeeGtAqZw+OgOzfrvYEk+AotEDu2+rNWAMq6958Jvp+c+glyW7W4EQn8cXBw9UBrowrCZ+P5ytgQVR8nbfFnqRajG4VJuLLwZc6022IzI09Frtk3p2uxpg== > >_______________________________________________ >Ws2-diversity mailing list >Ws2-diversity(a)icann.org >https://mm.icann.org/mailman/listinfo/ws2-diversity

13 18

SUMMARY: IMPORTANT: PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS
by Alan Greenberg Feb. 19, 2018

Feb. 19, 2018

Thanks for the active discussion on this. I have asked Evin to move the discussion to an At-Large policy page and that is now done - https://community.icann.org/x/-Ra8B. All of the e-mail messages here have been inserted in a lead-in comment. Please make any further comments there. To summarize, there is a reasonable strong position being formulated: We strongly and passionately believe in diversity (and have some pride in beleiving that we do play our part), but do not believe that we need a formal Office of Diversity. I believe that we must reply to the WS2 group. Please respond (on the wiki) with whether you believe we need a formal statement, or if you wish me to reply summarizing our discussion? Alan At 13/02/2018 07:18 PM, Alan Greenberg wrote: >I would like to call your attention to this paper that was just >circulated by the CCWG-Accountability WS2 on Diversity. > >The ALAC was silent on the question of an Office of Diversity (OOD) >that was mentioned in the draft recommendations (see >https://community.icann.org/x/Z5tEB) > >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 ( >https://mm.icann.org/pipermail/comments-reviews-standards-17oct17/2018q1/00… >), 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). > >According to the original recommendations document ( >https://www.icann.org/en/system/files/files/ccwg-acct-ws2-draft-recs-divers… >): 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. > >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. > >Should the ALAC issue a further statement on this? And if so, what >are your views? > >Alan > > >>From: Bernard Turcotte <turcotte.bernard(a)gmail.com> >>Date: Mon, 12 Feb 2018 14:28:23 -0500 >>To: ws2-diversity <ws2-diversity(a)icann.org> >>Subject: [Ws2-diversity] CCWG-Accountability-WS2-Diversity - PAPER >>ON OFFICE OF DIVERSITY PUBLIC COMMENTS >> >>All, >> >>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. >> >>Bernard Turcotte >>ICANN Staff Support to the CCWG-Accountability-WS2 >> >>For Fiona and Rafik. >> >>DIVERISTY SUB-GROUP >> >> >> >>PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS >> >> >> >>Preamble: >> >> >> >>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. >> >> >> >>Summary of Responses from Public Comments: >> >> >> * Total of 15 comments >> >> >> * 6 had no comments on an office of diversity >> * 3 supported an office of diversity or a panel >> * 3 supported an office of diversity >> * 3 rejected the notion of an office of diversity. >> >> >> * Breakdown by major categories >> >> >> * 7 SO/ACs/Board (those which will have to approve the WS2 >> final report): >> >> >> * 4 had no comments >> * 3 Rejected the notion of an office of diversity >> >> >> * 2 Governments: >> >> >> * 1 had no comments on an office of diversity >> * 1 supported an office of diversity >> >> >> * 6 Individuals/Associations: >> >> >> * 1 had no comments on an office of diversity >> * 3 supported an office of diversity or a panel >> * 2 supported an office of diversity >> >> >> >> >> >>Summary of Positions relating to the OOD from Public Comments: >> >> >> >>1. Establishment of an office of diversity or a panel similar >>to what is proposed in the Ombuds recommendations. >> >>2. Establishment of an office of diversity >> >>3. Rejection of an office of diversity in favour of staff >>performing this work. >> >> >> >>Required Actions: >> >>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. >> >> >> >>Content-Type: application/pdf; name="Office Of Diversity OptionsV1.2.pdf" >>Content-Disposition: attachment; >> filename="Office Of Diversity OptionsV1.2.pdf" >>X-Attachment-Id: f_jdkm12g20 >>X-Microsoft-Exchange-Diagnostics: >> >>1;YQXPR0101MB1589;27:5Mxd449bwS/HOp/iuqOwk4pTsHsOLwp4Urd2lAQC+LxH4sZOpA5H5EWy2W2rBs7gToTighaGdY2nGhYw4nbnkMhHj+A5OHljcCMG4yzy5c5s6+66WnCi//rOuNRtAQcG >>X-Microsoft-Antispam-Message-Info: >> >>ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6QwBeeGtAqZw+OgOzfrvYEk+AotEDu2+rNWAMq6958Jvp+c+glyW7W4EQn8cXBw9UBrowrCZ+P5ytgQVR8nbfFnqRajG4VJuLLwZc6022IzI09Frtk3p2uxpg== >> >>Content-Type: text/plain; charset="us-ascii" >>Content-Transfer-Encoding: 7bit >>Content-Disposition: inline >>X-Microsoft-Exchange-Diagnostics: >> >>1;YQXPR0101MB1589;27:5Mxd449bwS/HOp/iuqOwk4pTsHsOLwp4Urd2lAQC+LxH4sZOpA5H5EWy2W2rBs7gToTighaGdY2nGhYw4nbnkMhHj+A5OHljcCMG4yzy5c5s6+66WnCi//rOuNRtAQcG >>X-Microsoft-Antispam-Message-Info: >> >>ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6QwBeeGtAqZw+OgOzfrvYEk+AotEDu2+rNWAMq6958Jvp+c+glyW7W4EQn8cXBw9UBrowrCZ+P5ytgQVR8nbfFnqRajG4VJuLLwZc6022IzI09Frtk3p2uxpg== >> >>_______________________________________________ >>Ws2-diversity mailing list >>Ws2-diversity(a)icann.org >>https://mm.icann.org/mailman/listinfo/ws2-diversity >Content-Type: application/pdf; name="Office Of Diversity OptionsV1.2.pdf" >Content-Disposition: attachment; filename="Office Of Diversity >OptionsV1.2.pdf" >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:rF0hK9YDxr/fnsMsNuNSADzsRaQwoPF0Xay/5HZPxXGANP7YgzPg4wrHzDQXV3qNOHmztVhpwnAbYhpjxLvGkNVJUUhhh0N8EEBqRY9KmxB6MomvWvXzlwey6dITm1KQ >X-Microsoft-Antispam-Message-Info: > cHoY5eOkHwgGK+QQ1zgR2LXQ7vmm2jhapVD5L7i/Wh4B4ZchskxnHwUvcZcIMcKa > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:rF0hK9YDxr/fnsMsNuNSADzsRaQwoPF0Xay/5HZPxXGANP7YgzPg4wrHzDQXV3qNOHmztVhpwnAbYhpjxLvGkNVJUUhhh0N8EEBqRY9KmxB6MomvWvXzlwey6dITm1KQ >X-Microsoft-Antispam-Message-Info: > cHoY5eOkHwgGK+QQ1zgR2LXQ7vmm2jhapVD5L7i/Wh4B4ZchskxnHwUvcZcIMcKa > >_______________________________________________ >ALAC mailing list >ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: http://www.atlarge.icann.org >ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…

1 0

Re: [ALAC] FW: Fwd: Cherine Chalaby to Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017
by Alan Greenberg Feb. 18, 2018

Feb. 18, 2018

I agree that it would have to be staff-led, but there would likely need to be volunteer involvement. If we could flesh this out a bit, we could include it as part of the At-Large improvements implementation. I suspect monthly might be pushing thisg. We could also do it irregularly when there are sufficient updates or when particular input is required. The last thing we want to do is publish a newsletter that people quickly decide had no real content and thuse decide to ignore it in the future. Alan At 17/02/2018 11:48 AM, Maureen Hilyard wrote: >A monthly ALAC newsletter would be a good idea, >based on the outcomes of our monthly call - that >not many non-ALAC or RALO leaders attend. But >while RALO newsletters could focus on what is >happening in their regions, the ALAC newsletter >could focus on more high-level issues and >looking at what the ALAC thinking is at the >moment with regards to these issues. Only briefs >- we don't want to bore people to death, but giving them the hightlights. > >Of course this would have to be a staff >responsibility because I can't see anyone having >the time to add that to their ALAC and day jobs. > >M > >On Fri, Feb 16, 2018 at 6:35 AM, Vanda >Scartezini <<mailto:vanda@scartezini.org>vanda(a)scartezini.org> wrote: > >Our region also have one for all ICANN related >issues in the region not only LACRALO, but also >LACNIC, LACTLDs, LACNOG , IGFS around and related.. > >I guess an ALAC newsletter shall have links to >all othere regional newsletter in order to >promote our work that I continue to see as quite >ignored by ICANNâs community outside Ralos > >Kisses > >From: ALAC ><<mailto:alac-bounces@atlarge-lists.icann.org>alac-bounces(a)atlarge-lists.icann.org> >on behalf of Judith Hellerstein ><<mailto:judith@jhellerstein.com>judith(a)jhellerstein.com> >Date: Tuesday, February 13, 2018 at 20:35 >To: Vanda Scartezini <<mailto:vanda@scartezini.org>vanda(a)scartezini.org> >Cc: 'ALAC List' ><<mailto:alac@atlarge-lists.icann.org>alac(a)atlarge-lists.icann.org> >Subject: Re: [ALAC] FW: Fwd: Cherine Chalaby to >Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017 > > > >Hi all > >Naralo has a newsletter and this is good info for our newsletter > > > >Best > >Judith > >Sent from my iPhone > ><mailto:Judith@jhellerstein.com>Judith(a)jhellerstein.com > >Skype ID:Judithhellerstein > > >On Feb 13, 2018, at 2:47 PM, Vanda Scartezini ><<mailto:vanda@scartezini.org>vanda(a)scartezini.org> wrote: > >Sorry I have responded just to Holly. > >Kisses to all. > > > >Vanda Scartezini > >Polo Consultores Associados > ><https://maps.google.com/?q=Av.+Paulista+1159&entry=gmail&source=g>Av. >Paulista 1159, cj 1004 > >01311-200- Sao Paulo, SP, Brazil > >Land Line: <tel:+55%2011%203266-6253>+55 11 3266.6253 > >Mobile: <tel:+55%2011%2098181-1464>+ 55 11 98181.1464 > >Sorry for any typos. > > > >From: Vanda Scartezini <<mailto:vanda@scartezini.org>vanda(a)scartezini.org> >Date: Tuesday, February 13, 2018 at 17:45 >To: Holly Raiche <<mailto:h.raiche@internode.on.net>h.raiche(a)internode.on.net> >Subject: Re: [ALAC] Fwd: Cherine Chalaby to Alan >Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017 > > > >You right Holy, as I am reading from your >comments looks like we still not promoting well >our work. May be helpful to create newsletter >and send once at each 2-3 months resuming all >the work was done in all Ralos and ALAC itself >to the Board, GÃ¶ran and directory and all AC/SOs âbaordâmembers. > >Kisses > >Vanda Scartezini > >Polo Consultores Associados > ><https://maps.google.com/?q=Av.+Paulista+1159&entry=gmail&source=g>Av. >Paulista 1159, cj 1004 > >01311-200- Sao Paulo, SP, Brazil > >Land Line: <tel:+55%2011%203266-6253>+55 11 3266.6253 > >Mobile: <tel:+55%2011%2098181-1464>+ 55 11 98181.1464 > >Sorry for any typos. > > > > > > > > > > > >From: ALAC ><<mailto:alac-bounces@atlarge-lists.icann.org>alac-bounces(a)atlarge-lists.icann.org> >on behalf of Holly Raiche ><<mailto:h.raiche@internode.on.net>h.raiche(a)internode.on.net> >Date: Monday, February 12, 2018 at 20:04 >To: Javier Rua <<mailto:javrua@gmail.com>javrua(a)gmail.com> >Cc: 'ALAC List' ><<mailto:alac@atlarge-lists.icann.org>alac(a)atlarge-lists.icann.org>, >Alan Greenberg <<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> >Subject: Re: [ALAC] Fwd: Cherine Chalaby to Alan >Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017 > > > >Folks > > > >Yes, we will ned some staff support. But one >thing we can easily do is that, when we respond >to PDPs, in the response, include in an >introductory paragraph what we are saying - not >that difficult. And maybe point out to Cherine >that we already have a policy page (thanks to >Ariel) where what we have said is organised by >various topics - a start at least. > > > >Holly > > > > > >On 13 Feb 2018, at 2:50 am, Javier Rua ><<mailto:javrua@gmail.com>javrua(a)gmail.com> wrote: > > > > >âThe Board also looks forward to discussing >this issue further with the ALAC and GAC at the >ICANN61 meeting in San Juan, Puerto Rico.â > > > >One, some or all the âissuesâ touched upon in the Joint Statement? > > > > > > > >Javier RÃºa-Jovet > > > ><tel:+1%20787-396-6511>+1-787-396-6511 > >twitter: @javrua > >skype: javier.rua1 > ><https://www.linkedin.com/in/javrua>https://www.linkedin.com/in/javrua > > > > >On Feb 12, 2018, at 11:40 AM, Evan Leibovitch ><<mailto:evan@telly.org>evan(a)telly.org> wrote: > >"The Board also encourages the ALAC to continue >to lead by example in producing materials that >ensure effective and equal participation by all >stakeholders, and would encourage the ALAC to >include executive summaries on statements, >advisories, and other materials issued by the ALAC." > > > >How noble. Will the Board sufficiently resource >the ALAC to produce such materials and additional content? > > > >What the Board wants -- anywhere in ICANN, >they're able to get if it's sufficiently resourced. > > > >- Evan > > > >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: <http://www.atlarge.icann.org/>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > > > >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac >At-Large Online: ><http://www.atlarge.icann.org>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:eqDqhO9I/luauwvh0LPMdSn1/xm2vsPjQKEk0lgQ3v9M7E3BgXOTgzwGJluhS9r1D5P1UI+WNdPMF/7nowAKqWM3MxRJAGUd5iqhMDN8TZ8WYWAG3RcmrmcuQ6gLqsXp >X-Microsoft-Antispam-Message-Info: > >Cghv+DH0ORPSET06Rl0xVuVy2ShXzSQcwfUbBkWuDcs8wIp5S/l7ZLTBJXO8kygXVTZWlg2xia1dIpdIIxdUTjpKrlt4ufTIj8Yyf7vzjlQsw3XNvtgaNg/xegp/IrXRWUHGo/O1rHogCuJAZ0cGBsr7XEzFSeqUkVaN0ctr7lc= > >_______________________________________________ >ALAC mailing list >ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: http://www.atlarge.icann.org >ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…

5 4

DECISION: Consensus Call: GNSO gTLD PDP WT5 Co-Leader
by Alan Greenberg Feb. 18, 2018

Feb. 18, 2018

This Consensus Call has now closed and Javier Rúa-Jovet is named Co-Leader of the WT on Geonames as TLDs. Alan >Date: Sun, 11 Feb 2018 22:37:08 -0500 >To: ALAC-Internal <alac-internal(a)atlarge-lists.icann.org> >From: Alan Greenberg <alan.greenberg(a)mcgill.ca> >Subject: Consensus Call: GNSO gTLD PDP WT5 Co-Leader > >As discussed in earlier e-mails and during the >In Camera session on the last ALAC Monthly >Conference Call, in light of the resignation of >Christopher Wilkinson as Co-leader of WT5, I am >making a recommendation to the ALAC on a replacement. > >Following discussions with the ALT and with >possible candidates, I would like to recommend >to the ALAC that Javier Rúa-Jovet be appointed as the ALAC Co-Leader of WT5. > >Javier is a Member of WT5, and has agreed to >take on this new responsibility. He fully >understands his role in trying to have the WT, >with the participation of the GNSO, ccNSO GAC >and ALAC (among others), come to an equitable solution. > >I hope that he has the full support of the ALAC >in this difficult role, and that those of us who >are active in WT5 will be available to help him in any capacity. > >With this message, I am initiating a Consensus >Call of the ALAC to appoint Javier Rúa-Jovet as >the ALAC-selected Co-Leader of the GNSO gTLD PDP WT5 on Geonames as TLDs. > >The Consensus Call will end at 23:59 UTC on Thursday, 15 February, 2018. > >If there are any questions of comments, please >direct them to either this list or to me directly. > >Although messages indicating support are >welcome, they are not necessary. This Consensus >Call will be deemed to have succeeded in the >absence of significant opposition (greater than >20% as specified by ALAC RoP 12.3.3.1). > >This message should be considered confidential >until the formal results are announced. > >Alan

1 0

ALAC Newsletter? (was Re: FW: Fwd: Cherine Chalaby to Alan Greenberg ...)
by Evan Leibovitch Feb. 18, 2018

Feb. 18, 2018

[ Note: I seem to be blocked from the ALAC list but am receiving this thread through personal CCs. Thank you for that.] The beginning of this thread talked about the Board asking for executive summaries of its commentaries. Somehow this has morphed into doing an ALAC newsletter along the lines of what is now done by NARALO and ICANN's Latin American community. I suggest caution. First, be sure there is an audience. It should be possible to collect statistics to see how many hits have been on the NARALO and other existing newsletters. We're already doing such policy debriefs in webinar form (such as this week's Ottawa readout -- how well was that attended by the intended audience?) What's the point of spending all this volunteer effort to write something that nobody will read (and arguably is already being done)? Second, what is the newsletter's purpose? - To introduce ALAC to an outside audience? - To create in-depth summaries of issues to enable ALSs and individual participants to give informed policy feedback to ALAC? - To provide a summary of ALAC positions taken (which is what the Board has asked for)? Each of these choices requires very different choices of content and maybe even different writers. It also requires someone to be already deeply involved within ALAC policy to be able to describe the "what is ALAC thinking right now" subject matter that Maureen suggested. Is there a good supply of such specialized writers eager to help? Lastly, ICANN At-Large is full of really good ideas that simply die when their champions leave, or when advocates for such good ideas presume that "someone else" will do it, and in a volunteer body such assumptions can be dangerous. This is especially so if there is a commitment to a schedule of future activity. While ICANN is going into austerity mode when it comes to finances, At-Large seems to be in the midst of a lengthy austerity mode regarding volunteer talent. The number of person-hours available for ALAC projects, especially those that require good awareness of ICANN's issues and ALAC's stances on them, is very small. Is it reasonable to channel such resources into a newsletter that nobody outside ALAC has asked for, rather than into the original research and analysis that ALAC so badly needs? - Evan

3 2

FW: Fwd: Cherine Chalaby to Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017
by Vanda Scartezini Feb. 18, 2018

Feb. 18, 2018

Sorry I have responded just to Holly. Kisses to all. Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, cj 1004 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. From: Vanda Scartezini <vanda(a)scartezini.org> Date: Tuesday, February 13, 2018 at 17:45 To: Holly Raiche <h.raiche(a)internode.on.net> Subject: Re: [ALAC] Fwd: Cherine Chalaby to Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017 You right Holy, as I am reading from your comments looks like we still not promoting well our work. May be helpful to create newsletter and send once at each 2-3 months resuming all the work was done in all Ralos and ALAC itself to the Board, Göran and directory and all AC/SOs “baord”members. Kisses Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, cj 1004 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. From: ALAC <alac-bounces(a)atlarge-lists.icann.org> on behalf of Holly Raiche <h.raiche(a)internode.on.net> Date: Monday, February 12, 2018 at 20:04 To: Javier Rua <javrua(a)gmail.com> Cc: 'ALAC List' <alac(a)atlarge-lists.icann.org>, Alan Greenberg <alan.greenberg(a)mcgill.ca> Subject: Re: [ALAC] Fwd: Cherine Chalaby to Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017 Folks Yes, we will ned some staff support. But one thing we can easily do is that, when we respond to PDPs, in the response, include in an introductory paragraph what we are saying - not that difficult. And maybe point out to Cherine that we already have a policy page (thanks to Ariel) where what we have said is organised by various topics - a start at least. Holly On 13 Feb 2018, at 2:50 am, Javier Rua <javrua(a)gmail.com<mailto:javrua@gmail.com>> wrote: “The Board also looks forward to discussing this issue further with the ALAC and GAC at the ICANN61 meeting in San Juan, Puerto Rico.” One, some or all the “issues” touched upon in the Joint Statement? Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua On Feb 12, 2018, at 11:40 AM, Evan Leibovitch <evan(a)telly.org<mailto:evan@telly.org>> wrote: "The Board also encourages the ALAC to continue to lead by example in producing materials that ensure effective and equal participation by all stakeholders, and would encourage the ALAC to include executive summaries on statements, advisories, and other materials issued by the ALAC." How noble. Will the Board sufficiently resource the ALAC to produce such materials and additional content? What the Board wants -- anywhere in ICANN, they're able to get if it's sufficiently resourced. - Evan _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org<http://www.atlarge.icann.org/> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…

6 8

Re: [ALAC] IMPORTANT: PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS
by Alan Greenberg Feb. 17, 2018

Feb. 17, 2018

That is correct. But the issue has been raised again in the subgroup, and that is why I raised it here. Alan At 16/02/2018 01:45 PM, Dev Anand Teelucksingh wrote: >As a FYI, the ICANN Board responded during the public comment period >last month ><http://mm.icann.org/pipermail/comments-accountability-diversity-26oct17/att…>http://mm.icann.org/pipermail/comments-accountability-diversity-26oct17/att… > >saying that the office will not be established given lack of consensus >and budget constraints. > >Dev Anand

1 0

Fwd: Cherine Chalaby to Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017
by Alan Greenberg Feb. 16, 2018

Feb. 16, 2018

Response to the joint ALAC/GAC Advice Alan >To: Alan Greenberg <alan.greenberg(a)mcgill.ca> >Subject: [Correspondence] Cherine Chalaby to >Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017 >Date: Sat, 10 Feb 2018 00:16:53 +0000 > >Dear Alan Greenberg, > >Please find the attached letter from Cherine >Chalaby in response to the joint GAC-ALAC >statement of 2 November 2017 âEnabling >inclusive, informed, and meaningful participation at ICANNâ. > >You may expect this letter to be posted shortly >to the ICANN Correspondence page: ><https://www.icann.org/resources/pages/correspondence>https://www.icann.org/resources/pages/correspondence. > >With warm regards, > >Wendy Profit >ICANN Manager, Board Operations >12025 Waterfront Drive, Suite 300 >Los Angeles, CA 90094

7 11

Re: [ALAC] [Ext] Re: ACTION: ALL - Identification of ICANN 61 At-Large Leadership Meeting Topics and Guest Speakers
by Satish Babu Feb. 16, 2018

Feb. 16, 2018

This matter is sufficiently important for us to put out a coordinated response. Pls let us know how the RALOs can help in putting such a response together. satish On Feb 16, 2018 6:34 PM, "Glenn McKnight" <mcknight.glenn(a)gmail.com> wrote: Hi Eduardo I think discussing he CROP after he period for comment is closed is like closing the barn door after the cows are out of the barn. We need to provide community feedback on why this program has merit. Daniel started a google doc for us to provide a metered response. I have asked the CROP RT who are the most involved with CROP to arrange a skype call as well. I will send you an invite to the google doc to edit Thanks g Glenn McKnight NARALO Secretariat mcknight.glenn(a)gmail.com skype gmcknight twitter gmcknight 289-830 6259 . On Thu, Feb 15, 2018 at 10:02 PM, Eduardo Diaz <eduardodiazrivera(a)gmail.com> wrote: > Thanks for the info. Did not know that. > > In any case, I think it should be a good topic to discuss. > > -ed > > On Thu, Feb 15, 2018 at 11:01 PM Heidi Ullrich <Heidi.Ullrich(a)icann.org> > wrote: > >> Hi Eduardo, >> >> >> >> Just a note that the public comment period for the draft FY19 budget >> <https://www.icann.org/public-comments/fy19-budget-2018-01-19-en> closes >> on 8 March. So the comment period will have already closed by the time the >> ALAC meets. >> >> >> >> Kind regards, >> >> Heidi >> >> >> >> >> >> *From:* Eduardo Diaz [mailto:eduardodiazrivera@gmail.com] >> *Sent:* Thursday, February 15, 2018 6:52 PM >> *To:* ICANN At-Large Staff <staff(a)atlarge.icann.org> >> *Cc:* alac(a)atlarge-lists.icann.org; Alan Greenberg ( >> alan.greenberg(a)mcgill.ca) <alan.greenberg(a)mcgill.ca> >> *Subject:* [Ext] Re: [ALAC] ACTION: ALL - Identification of ICANN 61 >> At-Large Leadership Meeting Topics and Guest Speakers >> >> >> >> Lets talk about CROP and the Onboarding and the fact that by cutting >> these programs areICANN org is sending a signal to the community that >> outreach efforts are not the priority. >> >> >> >> -ed >> >> On Thu, Feb 15, 2018 at 7:35 PM ICANN At-Large Staff < >> staff(a)atlarge.icann.org> wrote: >> >> Dear All, >> >> >> >> With ICANN 61 approaching fast, we would like to ask you to let Alan and >> At-Large staff know of any topics you would like to have discussed during >> the ALAC and Regional Leader Meetings. >> >> >> >> In addition, please let us know of any guest speakers, from the community >> and from ICANN staff, that you would like to invite to speak with the ALAC >> and Regional Leaders. >> >> >> >> Please could you let us know by end of day Wednesday, 21 February? >> >> >> >> Thanks! >> >> >> >> Kind regards, >> >> >> >> ICANN Policy Staff in support of the At-Large Community >> >> E-mail: staff(a)atlarge.icann.org >> >> Website: atlarge.icann.org[atlarge.icann.org] >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> >> >> >> Facebook: facebook.com/icann[facebook.com] >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> >> atlarge[facebook.com] >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> >> >> Twitter: @[twitter.com] >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> >> ICANNAtLarge[twitter.com] >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> >> >> [image: image001.png] >> >> >> >> _______________________________________________ >> ALAC mailing list >> ALAC(a)atlarge-lists.icann.org >> >> https://atlarge-lists.icann.org/mailman/listinfo/alac[atlarg >> e-lists.icann.org] >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…> >> >> At-Large Online: http://www.atlarge.icann.org[atlarge.icann.org] >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.atlarge.icann.org&d…> >> ALAC Working Wiki: https://community.icann.org/di >> splay/atlarge/At-Large+Advisory+Committee+(ALAC)[community.icann.org] >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> >> >> > _______________________________________________ > ALAC mailing list > ALAC(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/alac > > At-Large Online: http://www.atlarge.icann.org > > ALAC Working Wiki: https://community.icann.org/di > splay/atlarge/At-Large+Advisory+Committee+(ALAC) > _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ Advisory+Committee+(ALAC)

1 0

ACTION: ALL - Identification of ICANN 61 At-Large Leadership Meeting Topics and Guest Speakers
by ICANN At-Large Staff Feb. 16, 2018

Feb. 16, 2018

Dear All, With ICANN 61 approaching fast, we would like to ask you to let Alan and At-Large staff know of any topics you would like to have discussed during the ALAC and Regional Leader Meetings. In addition, please let us know of any guest speakers, from the community and from ICANN staff, that you would like to invite to speak with the ALAC and Regional Leaders. Please could you let us know by end of day Wednesday, 21 February? Thanks! Kind regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png]

5 5