August 2018 - ALAC - lists.icann.org

RECORDED / CALL FOR 2018-2019 ALT NOMINATIONS now open
by ICANN At-Large Staff Aug. 13, 2018

Aug. 13, 2018

Dear John, Thank you for your e-mail. Your nomination acceptance is recorded. Thank you. Kind Regards, Yeşim Nazlar From: John Laprise <jlaprise(a)gmail.com> Date: Monday, August 13, 2018 at 4:59 PM To: ICANN At-Large Staff <staff(a)atlarge.icann.org> Subject: [Ext] Re: [ALAC] [ALAC-Announce] CALL FOR 2018-2019 ALT NOMINATIONS now open I also accept the nomination. John On Mon, Aug 13, 2018, 5:02 AM Sebastien Bachollet <sebicann(a)bachollet.fr<mailto:sebicann@bachollet.fr>> wrote: Dear All, Thanks Holly for the nomination. After consulting with my fellow colleagues form Europe I accept this nomination. I will do my best to work with the other region representatives to the ALT under the leadership of our Chair Maureen. All the best SeB Le 8 août 2018 à 06:42, Holly Raiche <h.raiche(a)internode.on.net<mailto:h.raiche@internode.on.net>> a écrit : Folks My nominations: For Africa - Tijani Ben Jemma For Europe - Sebastien Bachollet For LACRALO - Ricardo Holmquist For NARALO - John Laprise Holly On 8 Aug 2018, at 8:41 am, ICANN At-Large Staff <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>> wrote: Dear All, Alan Greenberg, ALAC Chair, with the agreement of incoming Chair, Maureen Hilyard, has requested that a call for nominations be issued for the other four members of the next year's ALAC Leadership Team (ALT) from the four remaining regions: - Africa - Europe - Latin America and Caribbean Islands - North America The terms of the 2018-2019 ALT will begin at the end of the 2018 AGM until the end of the 2019 AGM. This selection is carried out in accordance with the ALAC Rules of Procedure Section 17.3 (RoPs - http://tinyurl.com/ALAC-RoP-2016-09 [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_ALAC-2DRoP-…>). Nominations may be made by any current ALAC Member. Nominees need not be an ALAC Member at the time of the nominations, but must have an expectation of being an ALAC Member after the completion of the upcoming Barcelona ICANN Meeting. Requirements for ALT members can be found in Section 6 of the ALAC RoPs. In short, ALT members are expected to attend all ALAC meetings, typically two ALT or ALT-related meetings per month, and be very responsive and thoughtful to e-mail requests and discussions. By mutual agreement, ALT members may take on additional roles. Vice-Chairs are expected to take on proportionally larger responsibilities. All ALT activities are carried out solely in English. The nomination period is now open and will close on Wednesday, 15 August 2018 at 23:59 UTC. Nominations need not be seconded. Nominations, other than self-nominations, must be accepted by Wednesday, 22 August 2018 at 23:59 UTC. Acceptance should be sent to the alac at atlarge-lists.icann.org [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…>. Staff will forward all acceptances to alac-announce at atlarge-lists.icann.org [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…>. In accordance with ALAC RoP 16.3, following the close of the nominations period and the acceptance or rejection of all nominations, candidates from regions where the position is not contested will be declared to have won by acclamation. If there are multiple candidates from any region, the candidates, in conjunction with the ALAC, will be given the opportunity to resolve the situation. Failing that, a secret vote of the ALAC will decide the winner. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__atlarge.icann.org_&d=Dw…> Facebook: facebook.com/icannatlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_icanna…> Twitter: @ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_ICANNAt…> _______________________________________________ ALAC-Announce mailing list ALAC-Announce(a)atlarge-lists.icann.org<mailto:ALAC-Announce@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac-announce [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…> At-Large Official Site: http://www.atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.atlarge.icann.org_&…> _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac [atlarge-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/display/atlarge/At-Large+Advisory+Committee+(AL… [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<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac [atlarge-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/display/atlarge/At-Large+Advisory+Committee+(AL… [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>

1 0

RECORDED / CALL FOR 2018-2019 ALT NOMINATIONS now open
by Yesim Nazlar Aug. 13, 2018

Aug. 13, 2018

Dear Sébastien, Thank you for your e-mail. Your nomination acceptance is recorded. Thank you. Kind Regards, Yeşim Nazlar From: Sebastien Bachollet <sebicann(a)bachollet.fr> Date: Monday, August 13, 2018 at 1:02 PM To: Holly Raiche <h.raiche(a)internode.on.net> Cc: Sebastien Bachollet <sebicann(a)bachollet.fr>, ICANN At-Large Staff <staff(a)atlarge.icann.org>, "alac(a)atlarge-lists.icann.org" <alac(a)atlarge-lists.icann.org>, Alan Greenberg <alan.greenberg(a)mcgill.ca>, "alac-announce(a)atlarge-lists.icann.org" <alac-announce(a)atlarge-lists.icann.org> Subject: [Ext] Re: [ALAC] [ALAC-Announce] CALL FOR 2018-2019 ALT NOMINATIONS now open Dear All, Thanks Holly for the nomination. After consulting with my fellow colleagues form Europe I accept this nomination. I will do my best to work with the other region representatives to the ALT under the leadership of our Chair Maureen. All the best SeB Le 8 août 2018 à 06:42, Holly Raiche <h.raiche(a)internode.on.net<mailto:h.raiche@internode.on.net>> a écrit : Folks My nominations: For Africa - Tijani Ben Jemma For Europe - Sebastien Bachollet For LACRALO - Ricardo Holmquist For NARALO - John Laprise Holly On 8 Aug 2018, at 8:41 am, ICANN At-Large Staff <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>> wrote: Dear All, Alan Greenberg, ALAC Chair, with the agreement of incoming Chair, Maureen Hilyard, has requested that a call for nominations be issued for the other four members of the next year's ALAC Leadership Team (ALT) from the four remaining regions: - Africa - Europe - Latin America and Caribbean Islands - North America The terms of the 2018-2019 ALT will begin at the end of the 2018 AGM until the end of the 2019 AGM. This selection is carried out in accordance with the ALAC Rules of Procedure Section 17.3 (RoPs - http://tinyurl.com/ALAC-RoP-2016-09 [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_ALAC-2DRoP-…>). Nominations may be made by any current ALAC Member. Nominees need not be an ALAC Member at the time of the nominations, but must have an expectation of being an ALAC Member after the completion of the upcoming Barcelona ICANN Meeting. Requirements for ALT members can be found in Section 6 of the ALAC RoPs. In short, ALT members are expected to attend all ALAC meetings, typically two ALT or ALT-related meetings per month, and be very responsive and thoughtful to e-mail requests and discussions. By mutual agreement, ALT members may take on additional roles. Vice-Chairs are expected to take on proportionally larger responsibilities. All ALT activities are carried out solely in English. The nomination period is now open and will close on Wednesday, 15 August 2018 at 23:59 UTC. Nominations need not be seconded. Nominations, other than self-nominations, must be accepted by Wednesday, 22 August 2018 at 23:59 UTC. Acceptance should be sent to the alac at atlarge-lists.icann.org [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…>. Staff will forward all acceptances to alac-announce at atlarge-lists.icann.org [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…>. In accordance with ALAC RoP 16.3, following the close of the nominations period and the acceptance or rejection of all nominations, candidates from regions where the position is not contested will be declared to have won by acclamation. If there are multiple candidates from any region, the candidates, in conjunction with the ALAC, will be given the opportunity to resolve the situation. Failing that, a secret vote of the ALAC will decide the winner. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__atlarge.icann.org_&d=Dw…> Facebook: facebook.com/icannatlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_icanna…> Twitter: @ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_ICANNAt…> _______________________________________________ ALAC-Announce mailing list ALAC-Announce(a)atlarge-lists.icann.org<mailto:ALAC-Announce@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac-announce [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…> At-Large Official Site: http://www.atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.atlarge.icann.org_&…> _______________________________________________ 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…

1 0

Re: [ALAC] What to cover re GDPR in the HIT sessions?
by Maureen Hilyard Aug. 10, 2018

Aug. 10, 2018

The GDPR topics prioritised by the ALAC differed to those proposed by NCSG and the BC and will get swamped in the consolidated discussion if we dont at least mention our key interest areas and at least have someone on the panel. You might suggest that. On Sat, 11 Aug 2018 6:27 am Alan Greenberg <alan.greenberg(a)mcgill.ca> wrote: > Yes, I understood, but since that list came out: > > - several of the original sessions were merged > > - they are looking for input as to whether to merge them further or not > > - we need to decide where the non-GDPR sessions fit in the priority by > Monday > > Alan > > -- > Sent from my mobile. Please excuse brevity and typos. > > On August 10, 2018 11:39:07 AM EDT, Maureen Hilyard < > maureen.hilyard(a)gmail.com> wrote: >> >> Hi Alan >> >> This was only to discuss the GDPR session.. Donna asked for a preference >> rather than dealing with 7 topics in one session as had originally been >> suggested. It would still be helpful to Donna to give her an idea of the >> priority areas of interest from the ALAC as she has requested. The BC has >> already proposed a preference and so should we. >> >> So far the separate topics of interest to the ALAC are (in priority >> order): >> 1. Public interest impact >> 2. WHOIS data users >> 3. Post GDPR >> 4. Understanding RDAP >> >> Other topics for other sessions are still up for discussion. >> >> On Sat, 11 Aug 2018 12:48 am Alan Greenberg <alan.greenberg(a)mcgill.ca> >> wrote: >> >>> Please note that the list here is no longer the one being discussed. >>> This was GDPR-related only and there are other options. I will forward the >>> new one. Some topics have already been merged, and there is a proposal for >>> a further merger. >>> >>> Alan >>> >>> At 10/08/2018 04:21 AM, Maureen Hilyard wrote: >>> >>> Thank you Tijani >>> >>> I will put you down for the combined session as well >>> >>> M >>> >>> On Fri, Aug 10, 2018 at 8:18 PM, Tijani BEN JEMAA < >>> tijani.benjemaa(a)benjemaa.com> wrote: Maureen, The proposed combination >>> of topics 1, 2, 8, 9 and 13 makes a lot of sens for me since they are >>> overlapping / related, and can be done in 120 minutes session in my >>> opinion. Donna gave a good dispatching that may be improved. >>> If we call Â« Topic 0 Â» this combined session (including topics 1, 2, >>> 8, 9 and 13), I will then propose: Topic 0 Topic 3 Topic 12 If the >>> combination is not accepted, then I will rank my preferences as follow: Topic >>> 3 Topic 9 Topic 12 ----------------------------------------------------------------------------- >>> Tijani BEN JEMAA Executive Director Mediterranean Federation of >>> Internet Associations (FMAI) Phone: +216 98 330 114 +216 52 >>> 385 114 >>> ----------------------------------------------------------------------------- >>> >>> Le 10 aoÃ»t 2018 Ã 08:42, Maureen Hilyard < maureen.hilyard(a)gmail.com> >>> a Ã©crit : >>> Hi Seun >>> The document came from Donna Austin who is coordinating the GDPR >>> sessions. >>> The option you have selected is a combination of the topics 1,2, 8, 9, >>> 13 - that Donna gave as an option and our top 3 items are included in this >>> list, >>> But they are all big items, can 5 topics be covered in one session? >>> As soon as I get these ALAC priorities organised (and anyone on this >>> list can respond), I will pass it on to Alan who can provide an >>> appropriate response to send to Donna on our behalf by Tuesday's meeting. >>> >>> M >>> On Fri, Aug 10, 2018 at 6:24 PM, Seun Ojedeji <seun.ojedeji(a)gmail.com > >>> wrote: Hello Maureen, >>> I don't know who wrote the attached document but I like the first option >>> which suggests a combination of a couple of related topics and that would >>> be my preference. >>> Regards >>> Sent from my mobile Kindly excuse brevity and typos >>> On Fri, 10 Aug 2018, 01:53 Maureen Hilyard, < maureen.hilyard(a)gmail.com> >>> wrote: Hi all >>> Attached is a list of topics from which the SO/AC chairs are considering >>> a final list for inclusion into ICANN63 HIT slots. >>> Can you send me what you consider would be your top 2-3 topics? Not >>> possible to cover everything. Id like to survey what the ALAC considers >>> should be our suggested list (within the next 2-3 days?) >>> >>> M >>> >>> >>> >>> *Austin, Donna via SOAC-Leaders-ICANNMeeting-Planning* >>> >>> >>> >>> Aug 8 (2 days ago) to SOAC-Leaders-I. Hi Everyone Following on from >>> the Planning Committee Meeting last week, where I agreed that I would reach >>> out to those that submitted GDPR related topic proposals to see if we could >>> find a way to rationalize these sessions in some way, unfortunately I have >>> to report that I have not had much success. I reached out to those that had >>> submitted the GDPR related sessions to see if there was some way that we >>> could consolidate five of the proposed topics (see attached), but have yet >>> to receive any response so Iâ€™ll put this down to â€˜that time of yearâ€™. >>> Understanding that there is some urgency to resolve this to enable us to >>> move forward with the planning for Barcelona I have attached the proposal >>> that I developed. I also contacted Bruce Tonkin to see if he would be >>> available to moderate/facilitate a consolidated session and he is available >>> if that is something folks want to consider. I also spoke to Tanzie >>> and there is some flexibility in the schedule, for example, it might be >>> possible to schedule a 2 hour session on Wednesday from 10.00 to 12.00, but >>> my strong preference would be to have a 90 minute session as I think 2 >>> hours is probably too much. Perhaps another option, if those that submitted >>> the proposals donâ€™t want to combine their sessions, is to allocate 30 >>> minute slots (that would mean cutting one of the sessions). Of course that >>> doesnâ€™t really help overcome the problem of reducing the number of Topic >>> Proposals to fit the number of slots available. In thinking about the >>> meeting schedule from a holistic perspective, itâ€™s my personal opinion >>> that 7 sessions devoted to GDPR is too many. Thereâ€™s no doubt that it is >>> a â€˜hot topicâ€™, but we should be mindful that there are a number of >>> other efforts and issues that also require some air time as well and with >>> limited time available we should be respectful of the large number of >>> community members that will be attending the meeting that may have no >>> interest in the topic. Iâ€™m not sure what our next steps are for >>> winnowing down the Topic Proposals. Perhaps Tanzie can remind us. Thanks >>> everyone. Donna >>> _______________________________________________ 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… >>> >>> >>> _______________________________________________ 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… >>> >>> >>> _______________________________________________ >>> 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… >>> ) >>> >>

3 2

Re: [ALAC] What to cover re GDPR in the HIT sessions?
by Alan Greenberg Aug. 10, 2018

Aug. 10, 2018

Please note that the list here is no longer the one being discussed. This was GDPR-related only and there are other options. I will forward the new one. Some topics have already been merged, and there is a proposal for a further merger. Alan At 10/08/2018 04:21 AM, Maureen Hilyard wrote: >Thank you Tijani > >I will put you down for the combined session as well > >M > >On Fri, Aug 10, 2018 at 8:18 PM, Tijani BEN >JEMAA ><<mailto:tijani.benjemaa@benjemaa.com>tijani.benjemaa(a)benjemaa.com> wrote: >Maureen, >The proposed combination of topics 1, 2, 8, 9 >and 13 makes a lot of sens for me since they are >overlapping / related, and can be done in 120 >minutes session in my opinion. Donna gave a good >dispatching that may be improved. >If we call Â« Topic 0 Â» this combined session >(including topics 1, 2, 8, 9 and 13), I will then propose: >Topic 0 >Topic 3 >Topic 12 >If the combination is not accepted, then I will >rank my preferences as follow: >Topic 3 >Topic 9 >Topic 12 > >----------------------------------------------------------------------------- >Tijani BEN JEMAA >Executive Director >Mediterranean Federation of Internet Associations (FMAI) >Phone: +216 98 330 114 > +216 52 385 114 >----------------------------------------------------------------------------- > >>Le 10 aoÃ»t 2018 Ã 08:42, Maureen Hilyard >><<mailto:maureen.hilyard@gmail.com>maureen.hilyard(a)gmail.com> a Ã©crit : >>Hi Seun >>The document came from Donna Austin who is coordinating the GDPR sessions. >>The option you have selected is a combination >>of the topics 1,2, 8, 9, 13 - that Donna gave >>as an option and our top 3 items are included in this list, >>But they are all big items, can 5 topics be covered in one session? >>As soon as I get these ALAC priorities >>organised (and anyone on this list can >>respond), I will pass it on to Alan who can >>provide an appropriate response to send >>to Donna on our behalf by Tuesday's meeting. >> >>M >>On Fri, Aug 10, 2018 at 6:24 PM, Seun Ojedeji >><<mailto:seun.ojedeji@gmail.com>seun.ojedeji(a)gmail.com> wrote: >>Hello Maureen, >>I don't know who wrote the attached document >>but I like the first option which suggests a >>combination of a couple of related topics and that would be my preference. >>Regards >>Sent from my mobile >>Kindly excuse brevity and typos >>On Fri, 10 Aug 2018, 01:53 Maureen Hilyard, >><<mailto:maureen.hilyard@gmail.com>maureen.hilyard(a)gmail.com> wrote: >>Hi all >>Attached is a list of topics from which the >>SO/AC chairs are considering a final list for inclusion into ICANN63 HIT slots. >>Can you send me what you consider would be your >>top 2-3 topics? Not possible to cover >>everything. Id like to survey what the ALAC >>considers should be our suggested list (within the next 2-3 days?) >> >>M >> >> >> >> >>Austin, Donna via SOAC-Leaders-ICANNMeeting-Planning >> >> >> >> >> >>Aug 8 (2 days ago) >>to SOAC-Leaders-I. >>Hi Everyone >> >>Following on from the Planning Committee >>Meeting last week, where I agreed that I would >>reach out to those that submitted GDPR related >>topic proposals to see if we could find a way >>to rationalize these sessions in some way, >>unfortunately I have to report that I have not >>had much success. I reached out to those that >>had submitted the GDPR related sessions to see >>if there was some way that we could consolidate >>five of the proposed topics (see attached), but >>have yet to receive any response so Iâll put >>this down to âthat time of yearâ. >>Understanding that there is some urgency to >>resolve this to enable us to move forward with >>the planning for Barcelona I have attached the proposal that I developed. >> >>I also contacted Bruce Tonkin to see if he >>would be available to moderate/facilitate a >>consolidated session and he is available if >>that is something folks want to consider. >> >>I also spoke to Tanzie and there is some >>flexibility in the schedule, for example, it >>might be possible to schedule a 2 hour session >>on Wednesday from 10.00 to 12.00, but my strong >>preference would be to have a 90 minute session >>as I think 2 hours is probably too much. >>Perhaps another option, if those that submitted >>the proposals donât want to combine their >>sessions, is to allocate 30 minute slots (that >>would mean cutting one of the sessions). Of >>course that doesnât really help overcome the >>problem of reducing the number of Topic >>Proposals to fit the number of slots available. >> >>In thinking about the meeting schedule from a >>holistic perspective, itâs my personal >>opinion that 7 sessions devoted to GDPR is too >>many. Thereâs no doubt that it is a âhot >>topicâ, but we should be mindful that there >>are a number of other efforts and issues that >>also require some air time as well and with >>limited time available we should be respectful >>of the large number of community members that >>will be attending the meeting that may have no interest in the topic. >> >>Iâm not sure what our next steps are for >>winnowing down the Topic Proposals. Perhaps Tanzie can remind us. >> >>Thanks everyone. >> >>Donna >>_______________________________________________ >>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 >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

What to cover re GDPR in the HIT sessions?
by Maureen Hilyard Aug. 10, 2018

Aug. 10, 2018

Hi all Attached is a list of topics from which the SO/AC chairs are considering a final list for inclusion into ICANN63 HIT slots. Can you send me what you consider would be your top 2-3 topics? Not possible to cover everything. Id like to survey what the ALAC considers should be our suggested list (within the next 2-3 days?) M Austin, Donna via SOAC-Leaders-ICANNMeeting-Planning [image: Attachments]Aug 8 (2 days ago) to SOAC-Leaders-I. Hi Everyone Following on from the Planning Committee Meeting last week, where I agreed that I would reach out to those that submitted GDPR related topic proposals to see if we could find a way to rationalize these sessions in some way, unfortunately I have to report that I have not had much success. I reached out to those that had submitted the GDPR related sessions to see if there was some way that we could consolidate five of the proposed topics (see attached), but have yet to receive any response so I’ll put this down to ‘that time of year’. Understanding that there is some urgency to resolve this to enable us to move forward with the planning for Barcelona I have attached the proposal that I developed. I also contacted Bruce Tonkin to see if he would be available to moderate/facilitate a consolidated session and he is available if that is something folks want to consider. I also spoke to Tanzie and there is some flexibility in the schedule, for example, it might be possible to schedule a 2 hour session on Wednesday from 10.00 to 12.00, but my strong preference would be to have a 90 minute session as I think 2 hours is probably too much. Perhaps another option, if those that submitted the proposals don’t want to combine their sessions, is to allocate 30 minute slots (that would mean cutting one of the sessions). Of course that doesn’t really help overcome the problem of reducing the number of Topic Proposals to fit the number of slots available. In thinking about the meeting schedule from a holistic perspective, it’s my personal opinion that 7 sessions devoted to GDPR is too many. There’s no doubt that it is a ‘hot topic’, but we should be mindful that there are a number of other efforts and issues that also require some air time as well and with limited time available we should be respectful of the large number of community members that will be attending the meeting that may have no interest in the topic. I’m not sure what our next steps are for winnowing down the Topic Proposals. Perhaps Tanzie can remind us. Thanks everyone. Donna

8 10

Re: [ALAC] [GTLD-WG] [CPWG] Message to RALO liaisons to WT5
by Yrjö Länsipuro Aug. 9, 2018

Aug. 9, 2018

Dear Kaili, Thank you for your suggestion. I'm resending the message to the ALAC list. Best, Yrjö ________________________________ From: Yrjö Länsipuro <yrjo_lansipuro(a)hotmail.com> Sent: Thursday, August 9, 2018 12:58 PM To: Maureen Hilyard; Ali Hussein; carlosaguirre62(a)hotmail.com; mmoll(a)ca.inter.net; cpwg(a)icann.org; euro-discuss(a)atlarge-lists.icann.org Cc: Alan Greenberg; John Laprise; staff(a)atlarge.icann.org; ocl(a)gih.com Subject: Re: [GTLD-WG] [CPWG] Message to RALO liaisons to WT5 Dear all, At Maureen's suggestion, I'm sending to you, for your comments, a table showing the draft recommendations discussed at the WT5 meeting yesterday (8 August) and the responses from Greg Shatan from GNSO (see below). At the meeting, the main issue was whether country and territory names (long and short names) should be reserved (a) in all languages, as in the 2012 AGB or (b) in the six UN languages and the official languages of the country in question. (Recommendations #3 and #4) Even though it was pointed out that the "all languages" provision didn't cause problems in the 2012 round, there was an emerging consensus that it is unrealistic if taken literally (there are about 6 500 languages in thr world). On the other had, it was noted that the six UN languages reflect the world as it was right after WWII, and important international languages are not included. Also, languages listed as "official" in the countries of the world (eg., in the UN database https://unstats.un.org/unsd/geoinfo/geonames/ <https://unstats.un.org/unsd/geoinfo/geonames/> don't cover all languages widely spoken in them. A view was expressed that all languages by which communities in a country designate that country should be covered. On three-letter codes covered by recommendation #2, there is a GAC advice from 2016 that asks the community not to rush into a removal of the Applicant Guidebook protection of ISO 3166-1 alpha-3 codes, as this move could have political ramifications https://gacweb.icann.org/display/GACADV/2016-06-30+Use+of+3-letter+codes+in… There is clearly a need for compromise solutions, and we could make a valuable contribution in proposing "something in between". Please comment within the time frame of a week, as Maureen suggests. Best, Yrjö ________________________________ From: Maureen Hilyard <maureen.hilyard(a)gmail.com> Sent: Thursday, August 9, 2018 10:06 AM To: Greg Shatan Cc: Yrjö Länsipuro; CPWG; Alan Greenberg; Ali Hussein; John Laprise Subject: Re: [GTLD-WG] [CPWG] Message to RALO liaisons to WT5 Thank you so much Greg. Thats a great starting point that RALO reps can send out to our members for any further inputs. Should be interesting to see what we get back. Very much appreciated. Yrjo shall we time frame these responses to be returned in a week (?) so that we can all look over what we've got? Maureen On Thu, 9 Aug 2018 1:42 pm Greg Shatan <gregshatanisoc(a)gmail.com<mailto:gregshatanisoc@gmail.com>> wrote: Maureen, Here are my reactions to the first set of proposed recommendations discussed today in WT5. As you can see I support, most -- but not all -- of the current proposed recommendations. Perhaps we can use this as a jumping-off point in some fashion. PROPOSED RECOMMENDATIONS G. SHATAN RESPONSE RECOMMENDATION #1: All two-character letter-letter ASCII combinations for existing and future country codes. I am willing to support this recommendation, in order to preserve the unique character of 2-character letter-letter ASCII codes as ccTLDs. This should not extend to any two-character codes involving numbers or non-ASCII characters. First, these are not within our remit (see WT2). Second, they do not share the unique character that letter-letter codes have. RECOMMENDATION #2: Reserved and unavailable for delegation: * alpha-3 code listed in the ISO 3166-1 standard. I do not support this recommendation as written. There is no history of alpha-3 codes being used as country identifiers in the top level domain name space. In many cases, the alpha-3 codes do not have a special connection to the country listed, other than its use in the alpha-3 list. Furthermore, at least 49 alpha 3 codes have other substantial meanings: as words in English or another language, as an abbreviation with a commonly understood meaning (e.g., BRB), are already in use (COM) or could be confusing if used geographically (e.g., NIC). RECOMMENDATION #3: Reserved and unavailable for delegation: * Long-form name listed in the ISO 3166-1 standard in the official language(s) of the country and the official UN languages. I am willing to support this recommendation for long-form names in the official language(s) of the country and the official UN languages. I would not support a recommendation to reserve long form names in all languages. RECOMMENDATION #4: Reserved and unavailable for delegation: * Short-form name listed in the ISO 3166-1 standard in the official languages of the country and the official UN languages. Same as Recommendation 3. RECOMMENDATION #5: Reserved and unavailable for delegation: * Short- or long-form name associated with a code that has been designated as “exceptionally reserved” by the ISO 3166 Maintenance Agency. This needs to be clarified, and the list of names provided to the group. If these are country or territory names, they should already be covered in 3 and 4. If these are not country or territory names, they should be reviewed and discussed as a group (if possible) or on a case-by-case basis. RECOMMENDATION #6: A country and territory name which is reserved and unavailable for delegation: * separable component of a country name designated on the “Separable Country Names List.” This list is included as an appendix to the 2012 Applicant Guidebook. * The Work Track recommends narrowing reserved names to official languages of the country and the official UN languages. This involves (i) country names comprised of multiple compounded parts (e.g., Bosnia and Herzegovina) and (ii) Countries commonly known by a smaller constituent part than the short-form name listed in the ISO 3166-1 standard (e.g., (Netherlands) Antilles). I am willing to support this, consistent with my view on 3 and 4 above. RECOMMENDATION #7: Reserved and unavailable for delegation: * permutation or transposition of any of the names included in items (i) through (v). Permutations include removal of spaces, insertion of punctuation, and addition or removal of grammatical articles like “the.” A transposition is considered a change in the sequence of the long or short–form name, for example, “RepublicCzech” or “IslandsCayman.” Permutations should apply only to long and short form country and territory names and NOT to alpha 2 or alpha 3 letter codes. I am willing to support permutations for long and short country names and the separable components (i.e., 3, 4 and 6 above). I do not support permutations for alpha 2 or 3 letter codes. RECOMMENDATION #8: Reserved and unavailable for delegation: * name by which a country is commonly known, as demonstrated by evidence that the country is recognized by that name by an intergovernmental or treaty organization. Needs further review. Do we have examples where this was invoked, or any other examples? Greg On Wed, Aug 8, 2018 at 1:04 PM Maureen Hilyard <maureen.hilyard(a)gmail.com<mailto:maureen.hilyard@gmail.com>> wrote: Does anyone from this ALAC group disagree with the proposals in the WT5 consensus document on the policy considerations? We could use this as a starter for discussion to present to the WT5 co-Chairs. On Tue, Aug 7, 2018 at 6:57 AM, Yrjö Länsipuro <yrjo_lansipuro(a)hotmail.com<mailto:yrjo_lansipuro@hotmail.com>> wrote: > Dear fellow RALO WT5 liaisons, > > > > An action item from the ALAC call 24 April asks me to take the initiative > to develop a common ALAC position on geographic names in the subsequent > gTLD procedures. During that call, Alan suggested that this effort > could involve the five RALO liaisons to the WT5 and other interested > people, and mentioned also CPWG. > > > > I have not acted so far on this AI, because in my view, our only > meaningful contribution to the WT5 process would be to suggest compromises > to its most difficult issues, including names of non-capital cities, > which WT5 has spent most of its time on, mostly engaged in a fruitless > dispute between the extremes. The atmosphere so far might not have been > conducive for discussing compromise proposals... > > > > However, at ICANN62, there finally was a push by co-chairs for “meeting > in the middle”, especially concerning non-capital cities, and for "seeking > convergence on principles." See slides of the 28 June session: > https://static.ptbl.co/static/attachments/179943/1530207670<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstatic.pt…>. > pdf?1530207670 > <https://static.ptbl.co/static/attachments/179943/1530207670.pdf?1530207670<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstatic.pt…>> > > > > Now might be the time for an ALAC contribution along the lines that Alan > has often repeated: there should be no big winners and big losers in the WT > 5. In others words, a compromise, something in the middle. > > > > That’s why I’m asking for your thoughts, ideas and suggestions on how we > could facilitate finding compromises in the WT5, especially on the issue of > non-capital cities. This is late in the day in the life of WT5, so please > react soon. After an email exchange, we could ask the staff to arrange a > call, if necessary. I’m also asking CPWG to take note of this effort, the > results of which I hope could be presented to CPWG soon. > > > Yrjö > > > > > > _______________________________________________ CPWG mailing list CPWG(a)icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.…> _______________________________________________ GTLD-WG mailing list GTLD-WG(a)atlarge-lists.icann.org<mailto:GTLD-WG@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fatlarge-l…> Working Group direct URL: https://community.icann.org/display/atlarge/New+GTLDs<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity…>

2 1

ALAC Statement regarding EPDP
by Alan Greenberg Aug. 9, 2018

Aug. 9, 2018

Yesterday, the EPDP Members were asked to present a 1-3 minute summary of their groups position in regard to the EPDP. The following is the statement agreed to by me, Hadia, Holly and Seun. 1. The ALAC believes that the EPDP MUST succeed and will be working toward that end. 2. We have a support structure that we are organizing to ensure that what we present here is understood by our community and has their input and support. 3. The ALAC believes that individual registrants are users and we have regularly worked on their behalf (as in the PDP that we initiated to protect registrant rights when their domains expire), if registrant needs differ from those of the 4 billion Internet users who are not registrants, those latter needs take precedence. We believe that GDPR and this EPDP are such a situation. 4. Although some Internet users consult WHOIS and will not be able to do so in some cases going forward, our main concern is access for those third parties who work to ensure that the Internet is a safe and secure place for users and that means that law enforcement, cybersecurity researchers, those combatting fraud in domain names, and others who help protect users from phishing, malware, spam, fraud, DDoS attacks and such can work with minimal reduction in access to WHOIS data. All within the constraints of GDPR of course.

12 20

RECORDED / CALL FOR 2018-2019 ALT NOMINATIONS now open
by Yesim Nazlar Aug. 8, 2018

Aug. 8, 2018

Dear Holly, Thank you for your e-mail. Your nominations have been recorded. Thank you. Kind Regards, Yeşim Nazlar From: Holly Raiche <h.raiche(a)internode.on.net> Date: Wednesday, August 8, 2018 at 7:42 AM To: ICANN At-Large Staff <staff(a)atlarge.icann.org> Cc: "alac(a)atlarge-lists.icann.org" <alac(a)atlarge-lists.icann.org>, "alac-announce(a)atlarge-lists.icann.org" <alac-announce(a)atlarge-lists.icann.org>, "Alan Greenberg (alan.greenberg(a)mcgill.ca)" <alan.greenberg(a)mcgill.ca> Subject: [Ext] Re: [ALAC-Announce] CALL FOR 2018-2019 ALT NOMINATIONS now open Folks My nominations: For Africa - Tijani Ben Jemma For Europe - Sebastien Bachollet For LACRALO - Ricardo Holmquist For NARALO - John Laprise Holly On 8 Aug 2018, at 8:41 am, ICANN At-Large Staff <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>> wrote: Dear All, Alan Greenberg, ALAC Chair, with the agreement of incoming Chair, Maureen Hilyard, has requested that a call for nominations be issued for the other four members of the next year's ALAC Leadership Team (ALT) from the four remaining regions: - Africa - Europe - Latin America and Caribbean Islands - North America The terms of the 2018-2019 ALT will begin at the end of the 2018 AGM until the end of the 2019 AGM. This selection is carried out in accordance with the ALAC Rules of Procedure Section 17.3 (RoPs - http://tinyurl.com/ALAC-RoP-2016-09 [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_ALAC-2DRoP-…>). Nominations may be made by any current ALAC Member. Nominees need not be an ALAC Member at the time of the nominations, but must have an expectation of being an ALAC Member after the completion of the upcoming Barcelona ICANN Meeting. Requirements for ALT members can be found in Section 6 of the ALAC RoPs. In short, ALT members are expected to attend all ALAC meetings, typically two ALT or ALT-related meetings per month, and be very responsive and thoughtful to e-mail requests and discussions. By mutual agreement, ALT members may take on additional roles. Vice-Chairs are expected to take on proportionally larger responsibilities. All ALT activities are carried out solely in English. The nomination period is now open and will close on Wednesday, 15 August 2018 at 23:59 UTC. Nominations need not be seconded. Nominations, other than self-nominations, must be accepted by Wednesday, 22 August 2018 at 23:59 UTC. Acceptance should be sent to the alac at atlarge-lists.icann.org [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…>. Staff will forward all acceptances to alac-announce at atlarge-lists.icann.org [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…>. In accordance with ALAC RoP 16.3, following the close of the nominations period and the acceptance or rejection of all nominations, candidates from regions where the position is not contested will be declared to have won by acclamation. If there are multiple candidates from any region, the candidates, in conjunction with the ALAC, will be given the opportunity to resolve the situation. Failing that, a secret vote of the ALAC will decide the winner. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__atlarge.icann.org_&d=Dw…> Facebook: facebook.com/icannatlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_icanna…> Twitter: @ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_ICANNAt…> _______________________________________________ ALAC-Announce mailing list ALAC-Announce(a)atlarge-lists.icann.org<mailto:ALAC-Announce@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac-announce [atlarge-lists.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.…> At-Large Official Site: http://www.atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.atlarge.icann.org_&…>

1 0

2018 Nominating Committee Announces Selections
by sandra hoferichter Aug. 3, 2018

Aug. 3, 2018

https://www.icann.org/news/announcement-2-2018-08-02-en Best Sandra (Note: This message was sent from my iPhone - I apologise for any misspelling.)

1 0