June 2017 - ALAC - lists.icann.org

Revised agenda - Wrap Up Part 2
by Alan Greenberg June 29, 2017

June 29, 2017

Please note the revised agenda for the Wrap Up 2. If anyone has any other issues to be discussed related to future action (2c), please let me know. 1. Discussion on Topics before the Board with Rinalia Abdul Rahim, Board Director selected by At-Large and León Sánchez, incoming Board Director selected by At-Large (13:30-14:00) 2. ALAC Actions & Preparation (13:30-14:00) a) ALS decertifications b) Empowered Community Approval of Fundamental Bylaw Change c) Other actions - To be determined 3. Discussion on CCWG - Auction Proceeds (14:00-14:15) 4. ATLAS III - Starting a discussion on planning (14:15-14:30) 4. Debrief on ICANN 59 (14:30-15:00)

2 1

Fwd: COE/ICANN Meeting on Data Protection
by Olivier MJ Crépin-Leblond June 28, 2017

June 28, 2017

FYI --- this is something which might be of interest to you. -------- Forwarded Message -------- Subject: COE/ICANN Meeting on Data Protection Date: Wed, 28 Jun 2017 11:23:05 +0000 From: KIMPIAN Peter <Peter.KIMPIAN(a)coe.int> To: KIMPIAN Peter <Peter.KIMPIAN(a)coe.int> Dear All, On behalf of Data Protection Unit of the Council of Europe we wanted to inform you on a short ad-hoc meeting on our last paper we prepared for public comments on Whois conflict with Privacy Law (see in attachment). Some of you already asked for more information and background on that, therefore, thanks to ICANN staff we can offer you this opportunity tomorrow from 10:00 in Pavillon S8 to have an informal discussion on the issues raised in the document. We would be honoured by your or your interested colleague(s) presence at the meeting. Best regards, Peter *From:*Nigel Hickson [mailto:nigel.hickson@icann.org] *Sent:* mardi 27 juin 2017 16:29 *To:* KIMPIAN Peter *Subject:* FW: EMS Request Summary Peter Here is room booking. Best Nigel *From: *ICANN EMS <no-reply(a)icann.org <mailto:no-reply@icann.org>> *Date: *Tuesday, 27 June 2017 at 16:23 *To: *Nigel Hickson <nigel.hickson(a)icann.org <mailto:nigel.hickson@icann.org>>, Dierdre Sidjanski <dierdre.sidjanski(a)icann.org <mailto:dierdre.sidjanski@icann.org>> *Subject: *EMS Request Summary ICANN59 Johannesburg Sandton Convention Centre 161 Maude Street Sandton 2196 South Africa Sign Up Room Booking Confirmation *Department* *Reservation 4921* Nigel Hickson Governmental Engagement - 0410 Belgium Event Name: COE/ICANN Meeting on Data Protection Phone: +41799519625 Email Address nigel.hickson(a)icann.org <mailto:nigel.hickson@icann.org> Session Facilitator Nigel Hickson Phone: +41799519625 Alt Email Address: nigel.hickson(a)icann.org <mailto:nigel.hickson@icann.org> Event Type: Private/Not Posted Status: Web Confirmed Estimated Attendance: 0 *bookings* *Quantity* *Price* *Amount* *_Thursday, June 29, 2017_* *10:00 AM - 11:00 AM COE/ICANN Meeting on Data Protection (Web Confirmed) Pavilion S8* Boardroom for 23

6 5

Re: [ALAC] [ALAC-LT] Process for deciding on wether to issue a Public Comment Statement
by Alan Greenberg June 22, 2017

June 22, 2017

Seun, you are correct. This was a message that I sent to the ALT list for their thoughts before going further, but on my answer to Oliver, I inadvertently added the ALAC list. Everything is included here is you. The original message is the text which has 3 revision bars. The history is that in replying to the At-Large Review draft recommendation on abolishing the ALT, I realized that there was one relatively small example of the ALT actually making decisions, and that was if there was a public comment that was announced before an ALT meeting, the ALT might decide that no comment was warranted. This would be reported at the following ALAC meeting. There would still be time to reverse the decision if there was a will, but I realized that we were reporting the "decision" to not submit a statement, and that if fact, it should really have been an ALT "recommendation". If the ALAC ever did decide to draft a statement in such a situation, the delay between the ALT meeting and the ALAC meeting would result in a pretty short period in which to draft the statement. So I decided we should immediately tell the ALAC instead of waiting. Along with documenting a bunch of ICANN processes, staff is also documenting the AC decision process, so getting that right prompted me to start this thread now instead of at some later time. The bulk of the suggested process is just the status quo, documented. Hope this help, Alan At 22/06/2017 01:36 PM, Seun Ojedeji wrote: >Hello Alan, > >This seem like a discussion happening somewhere >else and ALAC list just got copied in one of the responses. > >Perhaps this was in error? If no then it may be >good to have a background on this (assuming you >require feedback from the members of alac working list. > >Overall based on the subject of the thread and >the content there-of, I think it's a good thing to consider. > >Regards > >On 21 Jun 2017 4:07 PM, "Alan Greenberg" ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Thanks Olivier. See further comments below. > >At 21/06/2017 03:23 AM, Olivier MJ CrÃÂ©pin-Leblond wrote: >>Dear Alan, >> >>thanks for launching this important discussion. >>Please be so kind to find my responses interspersed in your text: >> >>On 20/06/2017 05:49, Alan Greenberg wrote: >>>Going forward, I would like to suggest the >>>following process be followed. Note that there are several questions embedded. >>> >>>- When a new PC is posted (or for other reason >>>we may need to do a statement), a brief >>>message should be sent by Staff to the normal >>>ALAC list saying that a new PC (or other) is >>>open giving the subject and asking for input >>>(to be sent to the same list) on whether we >>>need to issue a statement, why, and offers to participate in the process. >> >>What is the "normal" ALAC list? Is this the >>ALAC working list or is this the At-Large >>worldwide list? Or ALAC announce? If the >>former, then you are willingly restricting the >>ability for calling for a Statement, to the 15 >>member ALAC plus regional leads plus a flurry >>of other people - but are effectively taking >>out of the equation the rest of the At-Large >>Community. Except if this call for input is related to the RALOs. > ><mailto:alac@atlarge-lists.icann.org>alac(a)atlarge-lists.icann.org, >the standard working ALAC list that also >includes most past ALAC members and regional >leaders is what I meant. The wider community was >to be consulted once we decided to actually do a statement. > >However, since I wrote this, I found out that >once the wiki space is created, we already send >a message to ALAC-Announce (ALAC, regional >leaders, ALS reps), so we will continue to do that. > >But also see my previous message about sending >too many messages to that list... > > > > >>>- If there is an ALAC meeting soon, their will >>>be a discussion on whether to issue a statement. >> >>Excellent. >> >>> >>>- If there is an ALT soon, the issue will be discussed during that meeting. >> >>Excellent. >> >>> >>>- If there is neither within a week or less, >>>then the ALT needs to consider the issue by e-ail or Skype. >> >>I agree with the ALT being most active, thus >>being able to consider the issue. >> >>> >>>- If it is not obvious from the subject >>>whether a statement is necessary, someone from >>>the ALT or Advisors must review the >>>documentation and make a recommendation generally within a week. >>> >>>- Once an ALT decision is taken, a message >>>should be sent to the ALAC list by Staff >>>saying that the ALT is recommending that there >>>be no statement issued and that anyone who >>>disagrees should quickly state why they >>>thought a statement is needed (ie why user >>>input is required in this case) and identify >>>who is willing to work on the statement. >> >>I understand the intent. Does this change the >>nature of the ALT? I am asking this because if >>the ALT is formally solicited to make a >>recommendation, could this be seen as a top >>down process for deciding if a Statement is to be drafted? > >Just the opposite. Currently the ALT often >decides to not do a statement and that is that. >Now I am treating this as a recommendation to >the ALAC with an opportunity for ALAC members (and others) to disagree. > > > >>>- QUESTION: Once a decision is taken either by >>>the ALAC during a meeting, or by the ALAC by >>>accepting the ALT recommendation, do we need >>>to (or want to) send out a message to >>>ALAC-Announce that eith no statement will be >>>issued, or asking for input if a statement is warranted? >> >>How else would you communicate with the wider At-Large membership? > >As in my previous e-mail in response to Leon, my >question is really how many checkpoints along >the way do we keep them informed. > > > >>>- QUESTION: I think that this entire process >>>can largely be handled by Staff, but I think >>>that there should be an ALT member who takes >>>responsibility. Who is willing to 5take this on? >> >>That's of course only if you decide that it is >>the ALT' job to make decisions on this. Could >>you not appoint a policy tracking person on the >>ALAC, irrespective of whether they are ALT or not? > >ALT member is to shepherd the process and make >sure it keeps moving. No formal decisions >involved. It could well be a non-ALT ALAC >member, but I was trying to keep this simple. > >Thanks for the detailed questions. Alan > > >>Kindest regards, >> >>Olivier > >_______________________________________________ >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…

1 0

Re: [ALAC] [ALAC-LT] Process for deciding on wether to issue a Public Comment Statement
by Alan Greenberg June 22, 2017

June 22, 2017

Thanks Olivier. See further comments below. At 21/06/2017 03:23 AM, Olivier MJ CrÃ©pin-Leblond wrote: >Dear Alan, > >thanks for launching this important discussion. >Please be so kind to find my responses interspersed in your text: > >On 20/06/2017 05:49, Alan Greenberg wrote: >>Going forward, I would like to suggest the >>following process be followed. Note that there are several questions embedded. >> >>- When a new PC is posted (or for other reason >>we may need to do a statement), a brief message >>should be sent by Staff to the normal ALAC list >>saying that a new PC (or other) is open giving >>the subject and asking for input (to be sent to >>the same list) on whether we need to issue a >>statement, why, and offers to participate in the process. > >What is the "normal" ALAC list? Is this the ALAC >working list or is this the At-Large worldwide >list? Or ALAC announce? If the former, then you >are willingly restricting the ability for >calling for a Statement, to the 15 member ALAC >plus regional leads plus a flurry of other >people - but are effectively taking out of the >equation the rest of the At-Large Community. >Except if this call for input is related to the RALOs. alac(a)atlarge-lists.icann.org, the standard working ALAC list that also includes most past ALAC members and regional leaders is what I meant. The wider community was to be consulted once we decided to actually do a statement. However, since I wrote this, I found out that once the wiki space is created, we already send a message to ALAC-Announce (ALAC, regional leaders, ALS reps), so we will continue to do that. But also see my previous message about sending too many messages to that list... >>- If there is an ALAC meeting soon, their will >>be a discussion on whether to issue a statement. > >Excellent. > >> >>- If there is an ALT soon, the issue will be discussed during that meeting. > >Excellent. > >> >>- If there is neither within a week or less, >>then the ALT needs to consider the issue by e-ail or Skype. > >I agree with the ALT being most active, thus being able to consider the issue. > >> >>- If it is not obvious from the subject whether >>a statement is necessary, someone from the ALT >>or Advisors must review the documentation and >>make a recommendation generally within a week. >> >>- Once an ALT decision is taken, a message >>should be sent to the ALAC list by Staff saying >>that the ALT is recommending that there be no >>statement issued and that anyone who disagrees >>should quickly state why they thought a >>statement is needed (ie why user input is >>required in this case) and identify who is willing to work on the statement. > >I understand the intent. Does this change the >nature of the ALT? I am asking this because if >the ALT is formally solicited to make a >recommendation, could this be seen as a top down >process for deciding if a Statement is to be drafted? Just the opposite. Currently the ALT often decides to not do a statement and that is that. Now I am treating this as a recommendation to the ALAC with an opportunity for ALAC members (and others) to disagree. >>- QUESTION: Once a decision is taken either by >>the ALAC during a meeting, or by the ALAC by >>accepting the ALT recommendation, do we need to >>(or want to) send out a message to >>ALAC-Announce that eith no statement will be >>issued, or asking for input if a statement is warranted? > >How else would you communicate with the wider At-Large membership? As in my previous e-mail in response to Leon, my question is really how many checkpoints along the way do we keep them informed. >>- QUESTION: I think that this entire process >>can largely be handled by Staff, but I think >>that there should be an ALT member who takes >>responsibility. Who is willing to 5take this on? > >That's of course only if you decide that it is >the ALT' job to make decisions on this. Could >you not appoint a policy tracking person on the >ALAC, irrespective of whether they are ALT or not? ALT member is to shepherd the process and make sure it keeps moving. No formal decisions involved. It could well be a non-ALT ALAC member, but I was trying to keep this simple. Thanks for the detailed questions. Alan >Kindest regards, > >Olivier

3 3

Re: [ALAC] Fwd: [SOAC-Leaders] Informed and Active Domain Name Registrants are Essential for a Secure and Stable DNS - ICANN by Akram Atallah
by Alan Greenberg June 22, 2017

June 22, 2017

Seun, what do you mean by suggesting that "this started off with the significant registrant base within ICANN (At-Large/NCSG)"? I do agree that in the past, there have been regular suggestions that At-Large take on the responsibility of helping registrants and I too am glad that such an unrealistic approach is no longer on the tabble. Alan At 22/06/2017 12:38 PM, Seun Ojedeji wrote: >Good to read indeed. I for one will like to see >this started off with the significant registrant >base within ICANN (At-Large/NCSG). > >Good that it seem ICANN who has the resources >has now seen to need for registrant >education/awareness. Hopefully these reduces the >effort always put in explaining that volunteers >like At-Large can't campion these; the >organisation should by utilising At-Large as a >resource base to achieving their goal. > >Overall am glad it's now an organisational >task/goal and not an expectation arbitrarily put on atlarge. > >Regards > >On 21 Jun 2017 4:06 PM, "Alan Greenberg" ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >This is encouraging news, and about time that >ICANN took an interest in registrants. I have asked for more information. > >Alan > >>From: David Olive <<mailto:david.olive@icann.org>david.olive(a)icann.org> >>To: SOAC Leaders <<mailto:soac-leaders@icann.org>soac-leaders(a)icann.org> >>Date: Wed, 21 Jun 2017 09:21:53 +0000 >> >>Informed and Active Domain Name Registrants are >>Essential for a Secure and Stable DNS >>Throughout all of our work, we endeavor to >>serve the global public interest, domain name >>registrants and end-users of the Internet by >>ensuring a secure and stable domain name system >>(DNS), all while promoting trust, choice, and >>competition in the industry. Domain name >>registrants are an integral component of the >>DNS; they are the entities or individuals that >>have acquired the right to use a domain name >>for a period of time via an agreement with a registrar or reseller. >>Domain name registrants have important >><https://www.icann.org/resources/pages/benefits-2013-09-16-en>rights, >>which include the right to access information >>from their registrar regarding the processes >>for registering, managing, transferring, >>renewing, and restoring domain name >>registrations. They also have important >><https://www.icann.org/resources/pages/benefits-2013-09-16-en>responsibilities, >>which include providing accurate contact >>information for publication in the >><https://whois.icann.org/en>WHOIS directory, >>notifying registrars of any changes in contact >>information, and promptly responding to >>requests from registrars about information >>relating to their domain name registration. >> >>Recently, the ICANN organization formed a >>cross-functional team that regularly interacts >>with registrants, and began discussing >>opportunities for collaboration with registrars >>to increase registrant knowledge and awareness. >>We're committed to providing domain name >>registrants with up-to-date information about >>their rights and obligations, the domain name >>ecosystem and how to navigate it, and the ICANN >>policies that affect them. One initial step >>that we are taking this week is the >>introduction of >><https://www.icann.org/resources/pages/domain-name-registrants-2017-06-20-en>new >>web pages on ICANN.org dedicated to information >>relevant to domain name registrants. These new >>pages, which will initially be a compilation of >>existing content from across ICANN.org, will be >>updated on an ongoing basis and evolve over >>time to provide content and information written >>specifically for domain name registrants. >> >>What's next? >>The ICANN Global Domains Division (GDD) >>recently added a new staff member, Brian >>Gutterman, Program Manager, Registrant >>Services, reporting to Trang Nguyen, Senior >>Director, Strategic Programs, who will lead our >>efforts to educate and inform domain name >>registrants and engage with registrars, the >>ICANN community, and any other parties that are supporting registrants. >>We will publish regular blogs and educational >>materials written for domain name registrants, >>which will be aimed at helping them better >>understand the ICANN policies that affect them, >>their role in the DNS, and the role of the >>ICANN organization and our contracted parties. >>For example, an internal data analysis revealed >>common issues and questions received from >>registrants regarding the WHOIS Data Reminder >>Policy (WDRP) and the recently updated Transfer >>Policy. Our initial focus will include >>developing and publishing educational materials on these topics. >> >>As we learn more, we'll share relevant >>information and materials with registrars and >>others for their own work supporting domain >>name registrants. The ICANN Global Support >>Center (GSC) and compliance teams have >>identified common issues and problems that >>registrants face. We will share this >>information with registrars and others, in >>addition to collaborating with ICANN community >>members, to encourage and support registrants' >>participation in ICANN processes. >> >>Our collective goal is to guide domain name >>registrants as they navigate policy matters >>impacting the domain name industry and help >>them become fully informed participants of the DNS and its ecosystem. >> >>We welcome >><https://www.icann.org/resources/pages/customer-support-2015-06-22-en#global…>feedback >>from all stakeholders on this effort, and >>invite the ICANN community and most >>importanntly domain name registrants >>themselvees to help us shaape this work >>moving forward. Updates and new content will be >>posted regularly on the new registrant section >>of the ICANN.org website. We look forward to working with you! >> >> >> >>David A. Olive >>Senior Vice President >>Policy Development Support >>Managing Director >>ICANN Regional Office Istanbul< >>Internet Corporation for Assigned Names and Numbers (ICANN) >> >>Direct Line: <tel:+90.212.999.6212>+90.212.999.6212 >>Mobile: <tel:+%201.%20202.341.3611>+ 1. 202.341.3611 >>Mobile: <tel:+90.533.341.6550>+90.533.341.6550 >> >><https://www.icann.org/news/blog/informed-and-active-domain-name-registrants…>https://www.icann.org/news/blog/informed-and-active-domain-name-registrants… >> > >_______________________________________________ >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…

2 1

Fwd: [SOAC-Leaders] Informed and Active Domain Name Registrants are Essential for a Secure and Stable DNS - ICANN by Akram Atallah
by Alan Greenberg June 22, 2017

June 22, 2017

This is encouraging news, and about time that ICANN took an interest in registrants. I have asked for more information. Alan >From: David Olive <david.olive(a)icann.org> >To: SOAC Leaders <soac-leaders(a)icann.org> >Date: Wed, 21 Jun 2017 09:21:53 +0000 > >Informed and Active Domain Name Registrants are >Essential for a Secure and Stable DNS >Throughout all of our work, we endeavor to serve >the global public interest, domain name >registrants and end-users of the Internet by >ensuring a secure and stable domain name system >(DNS), all while promoting trust, choice, and >competition in the industry. Domain name >registrants are an integral component of the >DNS; they are the entities or individuals that >have acquired the right to use a domain name for >a period of time via an agreement with a registrar or reseller. >Domain name registrants have important ><https://www.icann.org/resources/pages/benefits-2013-09-16-en>rights, >which include the right to access information >from their registrar regarding the processes for >registering, managing, transferring, renewing, >and restoring domain name registrations. They >also have important ><https://www.icann.org/resources/pages/benefits-2013-09-16-en>responsibilities, >which include providing accurate contact >information for publication in the ><https://whois.icann.org/en>WHOIS directory, >notifying registrars of any changes in contact >information, and promptly responding to requests >from registrars about information relating to their domain name registration. > >Recently, the ICANN organization formed a >cross-functional team that regularly interacts >with registrants, and began discussing >opportunities for collaboration with registrars >to increase registrant knowledge and awareness. >We're committed to providing domain name >registrants with up-to-date information about >their rights and obligations, the domain name >ecosystem and how to navigate it, and the ICANN >policies that affect them. One initial step that >we are taking this week is the introduction of ><https://www.icann.org/resources/pages/domain-name-registrants-2017-06-20-en>new >web pages on ICANN.org dedicated to information >relevant to domain name registrants. These new >pages, which will initially be a compilation of >existing content from across ICANN.org, will be >updated on an ongoing basis and evolve over time >to provide content and information written >specifically for domain name registrants. > >What's next? >The ICANN Global Domains Division (GDD) recently >added a new staff member, Brian Gutterman, >Program Manager, Registrant Services, reporting >to Trang Nguyen, Senior Director, Strategic >Programs, who will lead our efforts to educate >and inform domain name registrants and engage >with registrars, the ICANN community, and any >other parties that are supporting registrants. >We will publish regular blogs and educational >materials written for domain name registrants, >which will be aimed at helping them better >understand the ICANN policies that affect them, >their role in the DNS, and the role of the ICANN >organization and our contracted parties. For >example, an internal data analysis revealed >common issues and questions received from >registrants regarding the WHOIS Data Reminder >Policy (WDRP) and the recently updated Transfer >Policy. Our initial focus will include >developing and publishing educational materials on these topics. > >As we learn more, we'll share relevant >information and materials with registrars and >others for their own work supporting domain name >registrants. The ICANN Global Support Center >(GSC) and compliance teams have identified >common issues and problems that registrants >face. We will share this information with >registrars and others, in addition to >collaborating with ICANN community members, to >encourage and support registrants' participation in ICANN processes. > >Our collective goal is to guide domain name >registrants as they navigate policy matters >impacting the domain name industry and help them >become fully informed participants of the DNS and its ecosystem. > >We welcome ><https://www.icann.org/resources/pages/customer-support-2015-06-22-en#global…>feedback >from all stakeholders on this effort, and invite >the ICANN community and most importanntly >domain name registrants themselves to help us >shaape this work moving forward. Updates and new >content will be posted regularly on the new >registrant section of the ICANN.org website. We >look forward to working with you! > > > >David A. Olive >Senior Vice President >Policy Development Support >Managing Director >ICANN Regional Office Istanbul< >Internet Corporation for Assigned Names and Numbers (ICANN) > >Direct Line: <tel:+90.212.999.6212>+90.212.999.6212 >Mobile: <tel:+%201.%20202.341.3611>+ 1. 202.341.3611 >Mobile: <tel:+90.533.341.6550>+90.533.341.6550 > ><https://www.icann.org/news/blog/informed-and-active-domain-name-registrants…>https://www.icann.org/news/blog/informed-and-active-domain-name-registrants…

10 11

Re: [ALAC] INVITATION TO BE OUR SPECIAL GUESTS AT THE ICANN INFORMATION BOOTH
by Aziz Hilali June 21, 2017

June 21, 2017

Dear Vanda, AFRALO asked ICANN to put at its disposal a stand whose aim is to make the exhibition of the 46 African ALSes who will be present in Jboug. This will allow their representatives to meet together and to meet the community of ICANN. This will give them also the opportunity to showcase their local activities. We have many requests from our ALS's representatives to take in charge the animation of the booth and we try to make a balanced distribution among them.In consultation with AFRALO colleagues, we will be able to offer you two slots on the booth schedule to make activities of DNS Women. We will try also announce the schedule of these slots at our different AFRALO activities so that the African women (There will be 8) can join you at the booth during these slots. We will also try according to the different activities above how we can find a moment to give you the floor to talk about the DNS Women. Thank you for your understanding. Best Regards Aziz Le Mardi 20 juin 2017 15h13, Vanda Scartezini <vanda(a)scartezini.org> a écrit : I added my time to AFRALO booth since I would like to talk with many women I can from Africa. Be at the booth will be great for DNS WOMEN to keep in touch with African Women. ICANN helped the DNS Women with flyers, bottoms, website and translations and I will take with me the DNS Women banner to put at side to attract women to this booth. Also taking flyers and bottoms to distribute to African Women about DNS WOMEN Entrepreneur Project Kisses to all and safe trip to Johannesburg. See you there. 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. HAPPY 2017! From: <alac-bounces(a)atlarge-lists.icann.org> on behalf of Alan Greenberg <alan.greenberg(a)mcgill.ca> Date: Thursday, June 15, 2017 at 17:14 To: Tijani BEN JEMAA <tijani.benjemaa(a)topnet.tn> Cc: 'ALAC List' <alac(a)atlarge-lists.icann.org> Subject: Re: [ALAC] INVITATION TO BE OUR SPECIAL GUESTS AT THE ICANN INFORMATION BOOTH Isn't that just what I said?? > >I forwarded a message about the ICANN booth, pointing out that a few At-Large people were listed (mis-spelling Sarah's name - unless there are other Sarah Kiden and Ricardo Holmquists who are not part of At-Large). ANd I then also pointed to the AFRALO booth sign-up sheet. > >Alan > >At 15/06/2017 11:38 AM, Tijani BEN JEMAA wrote: > >Alan, there are 2 different booths, one of them is AFRALO booth. It is different from the ICANN 59 one. >> >>----------------------------------------------------------------------------- >>Tijani BEN JEMAA >>Executive Director >>Mediterranean Federation of Internet Associations (FMAI) >>Phone: +216 98 330 114 >> +216 52 385 114 >>----------------------------------------------------------------------------- >> >> >> >>Le 13 juin 2017 à 23:43, Alan Greenberg <alan.greenberg(a)mcgill.ca > a écrit : >>> >>>FYI. >>> >>>I see that Sara and a few other At-Large folks are already signed up for this. >>> >>>For the AFRALO Booth, see https://docs.google.com/spreadsheets/d/1XYYdfsZxIUIlfbygknwUDaMDqiCDOHuxUE6… . >>> >>>Alan >>> >>> >>>From: Deborah Escalera <deborah.escalera(a)icann.org> >>>>Subject: INVITATION TO BE OUR SPECIAL GUESTS AT THE ICANN INFORMATION BOOTH >>>>Date: Tue, 13 Jun 2017 21:04:28 +0000 >>>> >>>>Hello, I know everyone is busy prepping for the Meeting but I want to make you aware that there will be an ICANN Information Booth at this Policy Forum. Respecting that this is a 4 day meeting and no one will have much â€œfreeâ€� time, our Newcomer Program will be in full swing at the Booth to help ensure our Newcomers are getting the most out of their experience at ICANN59. As always, it would be beneficial to have the presence of seasoned ICANN Community members on hand to share their knowledge and stories with the group, so as has become our practice, we would like to offer 1-2 slots during the week to each our Community group should time allow…even 30 minutes. When signing up, please be aware that there are other activities taking place at the Booth which you can see by peeking in on the other tabs on this google doc link. Thank you for your cooperation. >>>> >>>>https://docs.google.com/spreadsheets/d/19YZZ3PikMmx1mVHPl-B3wz4loQG-pcs1Ffv… >>>> >>>> >>>>Deborah Escalera >>>> >>>>Next Generation Program Manager >>>>Development and Public Responsibility Dept., ICANN >>>>Direct Line: +1 310 578 8681 >>>>Mobile: +1 310 433 4861 >>>>E-mail: deborah.escalera(a)icann.org >>>> >>>> >>>>One World. One Internet. >>>><10fa1c9d.jpg> >>>> >>>>Content-Type: image/png; name="image001.png" >>>>Content-Description: image001.png >>>>Content-Disposition: inline; filename="image001.png"; size=5437; >>>> creation-date="Tue, 13 Jun 2017 21:04:28 GMT"; >>>> modification-date="Tue, 13 Jun 2017 21:04:28 GMT" >>>>Content-ID: <image001.png(a)01D2E44D.F8637CD0> >>>>X-Microsoft-Exchange-Diagnostics: >>>> 1;DM5PR03MB2714;27:tM8VqspZiHmlPi4a80+QIBwGczzxzuTfa4V11QrZ4UkvHcUHTx2wAQ09jR3aI8bmro4YRNjHb32DLPBkFmXeUrJNrmVLephuKCi117aMd9H7ohsv/rS9gTPf0lPl3crNJUhFaW10q73OSQ/hh8o8/w== >>>>X-Microsoft-Antispam-Mailbox-Delivery: >>>> ex:0;auth:0;dest:I;ENG:(400001000100)(400125000095)(20160513016)(520000050)(520002050)(750028)(701014)(400001001128)(400125100095)(400001002128)(400125200095); >>>> _______________________________________________ >>>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…

2 1

Fwd: INVITATION TO BE OUR SPECIAL GUESTS AT THE ICANN INFORMATION BOOTH
by Alan Greenberg June 20, 2017

June 20, 2017

FYI. I see that Sara and a few other At-Large folks are already signed up for this. For the AFRALO Booth, see https://docs.google.com/spreadsheets/d/1XYYdfsZxIUIlfbygknwUDaMDqiCDOHuxUE6…. Alan >From: Deborah Escalera <deborah.escalera(a)icann.org> >Subject: INVITATION TO BE OUR SPECIAL GUESTS AT THE ICANN INFORMATION BOOTH >Date: Tue, 13 Jun 2017 21:04:28 +0000 > >Hello, I know everyone is busy prepping for the >Meeting but I want to make you aware that there >will be an ICANN Information Booth at this >Policy Forum. Respecting that this is a 4 day >meeting and no one will have much âfreeâ >time, our Newcomer Program will be in full swing >at the Booth to help ensure our Newcomers are >getting the most out of their experience at >ICANN59. As always, it would be beneficial to >have the presence of seasoned ICANN Community >members on hand to share their knowledge and >stories with the group, so as has become our >practice, we would like to offer 1-2 slots >during the week to each our Community group >should time alloweven 30 minutes. When signing >up, please be aware that there are other >activities taking place at the Booth which you >can see by peeking in on the other tabs on this >google doc link. Thank you for your cooperation. > ><https://docs.google.com/spreadsheets/d/19YZZ3PikMmx1mVHPl-B3wz4loQG-pcs1Ffv…>https://docs.google.com/spreadsheets/d/19YZZ3PikMmx1mVHPl-B3wz4loQG-pcs1Ffv… > > >Deborah Escalera > >Next Generation Program Manager >Development and Public Responsibility Dept., ICANN >Direct Line: +1 310 578 8681 >Mobile: +1 310 433 4861 >E-mail: <mailto:deborah.escalera@icann.org>deborah.escalera(a)icann.org > > >One World. One Internet. >id:image001.png@01D2BDDF.15981210 > > >Content-Type: image/png; name="image001.png" >Content-Description: image001.png >Content-Disposition: inline; filename="image001.png"; size=5437; > creation-date="Tue, 13 Jun 2017 21:04:28 GMT"; > modification-date="Tue, 13 Jun 2017 21:04:28 GMT" >Content-ID: <image001.png(a)01D2E44D.F8637CD0> >X-Microsoft-Exchange-Diagnostics: > >1;DM5PR03MB2714;27:tM8VqspZiHmlPi4a80+QIBwGczzxzuTfa4V11QrZ4UkvHcUHTx2wAQ09jR3aI8bmro4YRNjHb32DLPBkFmXeUrJNrmVLephuKCi117aMd9H7ohsv/rS9gTPf0lPl3crNJUhFaW10q73OSQ/hh8o8/w== >X-Microsoft-Antispam-Mailbox-Delivery: > >ex:0;auth:0;dest:I;ENG:(400001000100)(400125000095)(20160513016)(520000050)(520002050)(750028)(701014)(400001001128)(400125100095)(400001002128)(400125200095); >

4 6

New Public Comment: GNSO Operating Procedures and ICANN Bylaws
by ICANN At-Large Staff June 20, 2017

June 20, 2017

Dear All, This is to let you know that the Public Comment on the GNSO Operating Procedures and ICANN Bylaws<https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en> has now gone live. Public comment will end on 10 August 2017 23:59 UTC. Please post directly on this ALAC Work mailing list if: * You believe the ALAC should or should not issue a Statement (please provide your rationale) * You would like to volunteer to participate in the process of developing a Statement on behalf of the ALAC * You have other input for this public comment The wiki workspace for this public comment is https://community.icann.org/x/uFjwAw. All pertinent resources can also be found there. 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>

1 0

SAC097 SSAC Advisory Regarding the Centralized Zone Data Service (CZDS) and Registry Operator Monthly Activity Reports
by Julie Hammer June 18, 2017

June 18, 2017

Hi Everyone, Please note that the following SSAC Report has been published: SAC097: SSAC Advisory Regarding the Centralized Zone Data Service (CZDS) and Registry Operator Monthly Activity Reports The Centralized Zone Data Service (CZDS) was introduced about 3 years ago to provide standardization and easy, reliable operations for participants who have a requirement to access top level domain (TLD) zone files to perform Domain Name System (DNS) research, security research, and anti-abuse operations. The CZDS has often succeeded in these goals. However, some community members have documented problems where the CZDS does not deliver on these objectives. Policy and process difficulties have prevented subscribers from gaining and then maintaining reliable access to zone files.This Report highlights access problems which have been experienced and recommends to the ICANN Board actions which ICANN Staff could take to remediate the difficulties. This Report is attached and can also be found on the SSAC Reports <https://www.icann.org/groups/ssac/documents> webpage. Cheers, Julie

1 0