February 2018 - ALAC - lists.icann.org

Suggested revision of At-Large Policy Development template
by Alan Greenberg May 13, 2018

May 13, 2018

It has been pointed out to me that the template we use has a space for "First Draft" and then "Final Draft". This works for issues that do not generate a lot of dialogue and revision of the statement. For such statements, there is no specific place to post the revised version(s). Simply changing the first draft does not really work, because then we are left with Wiki comments on that draft that refer back to something that is no longer there (unless you go to the trouble of finding the correct earlier version). I suggest that we change the title from "FIRST DRAFT SUBMITTED" to "DRAFT STATEMENTS" and add instructions saying that if multiple draft versions are posted, old versions should remain, with the newer version posted at the top of the box, prefixed with the date posted and author, and separated from earlier versions by a horizontal line. That way we have a full history of the draft evolution. Does anyone see a reason not to do this? Alan

7 7

Chair's blog on preview for Board's workshop
by León Felipe Sánchez Ambía March 2, 2018

March 2, 2018

Dear all, I hope this email finds you all well. As we come closer to holding our meeting in San Juan, Puerto Rico, Cherine has published a post on ICANN’s blog offering an overview of what the Board and its Committees will be up to in this year’s second workshop. You can read the blogpost here: https://www.icann.org/news/blog/chair-s-blog-a-preview-of-the-puerto-rico-b… <https://www.icann.org/news/blog/chair-s-blog-a-preview-of-the-puerto-rico-b…> I hope to see many of you soon in Puerto Rico and wish all those attending the meeting a safe travel. Best regards, León

3 2

Re: [ALAC] [CCWG-ACCT] CCWG-Accountability-WS2-Plenary-20180228- Documents
by Cheryl Langdon-Orr Feb. 28, 2018

Feb. 28, 2018

Happy to read this to the record On Feb 28, 2018 07:35, "Alan Greenberg" <alan.greenberg(a)mcgill.ca> wrote: I will not be able to attend the CCWT-ACCT Plenary on 28 February 2018. Please ensure that this message is either read into the record or otherwise considered during the deliberations on Diversity. I note that the Diversity Recommendations being considered do not include one to create an ICANN Office of Diversity (OoD). There was an extensive discussion on diversity and an OoD within the ALAC over the past weeks. As one might expect from such a regionally based organization, the ALAC strongly supports diversity in all of its forms, and to say we are (collectively) passionate about diversity does not fully convey our feelings. However, every person who contributed to the discussion (and that was a majority of ALAC members and other community leaders) felt that there is no need for an OoD, and to create one would needlessly increase bureaucracy and cost without any real benefit. There was support for ICANN organization to consider diversity among its staff but that should be handled within Human Resources. In summary, the ALAC would not support creating an OoD. Alan Greenberg CCWG-ACCT Member and Chair, ALAC _______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community(a)icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community

1 0

Re: [ALAC] [CCWG-ACCT] CCWG-Accountability-WS2-Plenary-20180228- Documents
by Alan Greenberg Feb. 27, 2018

Feb. 27, 2018

I will not be able to attend the CCWT-ACCT Plenary on 28 February 2018. Please ensure that this message is either read into the record or otherwise considered during the deliberations on Diversity. I note that the Diversity Recommendations being considered do not include one to create an ICANN Office of Diversity (OoD). There was an extensive discussion on diversity and an OoD within the ALAC over the past weeks. As one might expect from such a regionally based organization, the ALAC strongly supports diversity in all of its forms, and to say we are (collectively) passionate about diversity does not fully convey our feelings. However, every person who contributed to the discussion (and that was a majority of ALAC members and other community leaders) felt that there is no need for an OoD, and to create one would needlessly increase bureaucracy and cost without any real benefit. There was support for ICANN organization to consider diversity among its staff but that should be handled within Human Resources. In summary, the ALAC would not support creating an OoD. Alan Greenberg CCWG-ACCT Member and Chair, ALAC

1 0

ACTION: ALL - ALAC Questions to the Board at ICANN 61
by ICANN At-Large Staff Feb. 26, 2018

Feb. 26, 2018

Dear All, Board Support staff have requested that the ALAC send their questions to be asked during the ICANN 61 Board meeting with the ALAC. Alan Greenberg has asked that the ALAC and Regional Leaders suggest questions for the Board on the At-Large Board Questions at ICANN 61 Workspace (see: https://community.icann.org/display/atlarge/At-Large+Board+Questions+at+ICA…) by Monday, 26 February in order for the ALAC to review them during their monthly call on Tuesday, 27 February. Please add any suggested questions either directly to the workspace or using the comments function. The Workspace also contains the questions that the Board is asking all the AC/SOs. 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]

2 1

Proposed ALAC Mailing list membership change
by Alan Greenberg Feb. 22, 2018

Feb. 22, 2018

The At-Large mailing lists are governed by the ALAC E-mail Guide (<http://tinyurl.com/ALAC-E-MailGuide-Sept2013>http://tinyurl.com/ALAC-E-MailGuide-Sept2013) which Augments the ALAC Rules of Procedure (<http://tinyurl.com/ALAC-RoP-2016-09>http://tinyurl.com/ALAC-RoP-2016-09) The guide specifies who is to be a member of the ALAC list, and allows the ALAC to make additions. Several years ago, when Avri was co-chairing a WG, we added her to the list. I would like to propose that we similarly add Jonathan Zuck as the new Chair of Our gTLD group, and co-chair of the Consolidated Policy WG (CPWG). Moreover, I would like to propose that as new WG Chairs are found, we do the same. I also propose that next time we revise this document, that we add a provision for all such volunteers who are not otherwise members of the list, also extending the courtesy of keeping them on the list after they leave the position (as we do with past ALAC Members and Regional Leaders, and as we have with Avri. Comments please. I will open a Consensus Call on this shortly. Alan

7 6

Policy WGs
by Alan Greenberg Feb. 20, 2018

Feb. 20, 2018

You will recall that on the last ALAC call, we discussed the structure of our policy WGs. The intent was to have our three currently largely inactive WGs revived, but in the form of mailing lists only. They are the New gTLD WG, the Registration Issues WG and the ICANN Evolution WG. Jonathan Zuck had volunteered to run the New gTLD WG. We will also set up a new WG which would be the merger of these three (and any other policy groups we may form). It would have a mailing list consisting of the union of the others, and would be the WG under which an conference calls or webinars are held, and its mailing list would not only announce such meetings, but would also be used to raise specific issues (from one of the subsidiary WG) when it was felt they needed the attention of the wider At-Large Community. In the interest of time, the naming of this group was deferred at the time. I have instructed Staff to call it the At-Large Consolidated Policy WG (CPWG) as this is a self-explanatory and relatively simple name. The mailing list is being set up and tested and hopefully will be ready to go live shortly. Alan

2 2

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