June 2016 - ALAC - lists.icann.org

ALS Criteria and Expectations
by Alan Greenberg July 8, 2016

July 8, 2016

Please find attached, the document for discussion at the ALS Criteria and Expectations session at 10:45 on Monday. If you will be attending the Outreach & Engagement session, please ensure that someone from your region will be at the ALS meeting to present your views. Alan

6 6

Board Resolutions from 25 and 27 June Meetings
by Rinalia Abdul Rahim June 30, 2016

June 30, 2016

FYI 25 June 2016 https://www.icann.org/resources/board-material/resolutions-2016-06-25-en 27 June 2016 https://www.icann.org/resources/board-material/resolutions-2016-06-27-en Approved Board Resolutions | Regular Meeting of the ICANN Board 25 Jun 2016 1. *Consent Agenda: <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#1>* 1. *Thank You from Security and Stability Advisory Committee <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#1.a>* - *Rationale for Resolution 2016.06.25.01 <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#1.…>* 2. *Main Agenda: <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2>* 1. *Approval of Board Meeting Minutes <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.a>* 2. *Delegation of the бг ("bg") domain representing Bulgaria in Cyrillic script to Imena.BG Plc (Names.BG Plc) <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.b>* - *Rationale for Resolutions 2016.06.25.03 – 2016.06.25.04 <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.…>* 3. *FY17 Operating Plan and Budget <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.c>* - *Rationale for Resolution 2016.06.25.05 <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.…>* 4. *Consideration of Independent Review Panel's Final Declaration in the Donuts Inc. v. ICANN IRP <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.d>* - *Rationale for Resolutions 2016.06.25.06 – 2016.06.25.09 <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.…>* 5. *Independent Review of the Generic Names Supporting Organization Final Report and Recommendations <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.e>* - *Rationale for Resolutions 2016.06.25.10 – 2016.06.25.15 <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.…>* 6. *Revised Expected Standards of Behavior <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.f>* - *Rationale for Resolution 2016.06.25.16 <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.…>* 7. *New gTLD Program: Reviews and Future Path <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.g>* 8. *Review of .HOTEL Application Status <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.h>* Approved Board Resolutions | Regular Meeting of the ICANN Board 27 Jun 2016 1. *Main Agenda: <https://www.icann.org/resources/board-material/resolutions-2016-06-27-en#1>* 1. *FY17 Update to the Five-Year Operating Plan <https://www.icann.org/resources/board-material/resolutions-2016-06-27-en#1.a>* - *Rationale for Resolution 2016.06.27.01 <https://www.icann.org/resources/board-material/resolutions-2016-06-27-en#1.…>* Best regards, Rinalia

1 0

Proposed Amendments to Base New gTLD Registry Agreement Workspace
by Olivier MJ Crepin-Leblond June 28, 2016

June 28, 2016

Dear ALAC members, I am currently looking at the public consultation on "Proposed Amendments to Base New gTLD Registry Agreement" https://community.icann.org/x/uBiOAw Reading through the material that was made available, it appears that the issue of Dotless Domains is coming up again. The ALAC went on record in 2012 which helped encourage the Board to prohibit dotless domains. The ALAC Statement, which you can find on https://atlarge.icann.org/advice_statements/7661 In that Statement, the ALAC supported the SSAC advice in SAC053 which recommended the prohibition of dotless domains. The Board agreed with this and in the "current" round of new gTLDs, this prohibition took place. I have checked with Julie Hammer, our SSAC Liaison, whether the SSAC has changed its advice since SAC053. She has assured me that this was NOT the case. To summarize the concern, the proposed RA amendment creates a possible path to approval of dotless domains using the RSEP process, which has the potential to circumvent the existing prohibition. In further details: * On May 31, ICANN posted proposed amendments to the New gTLD Registry Agreement for public comment <https://www.icann.org/public-comments/proposed-amend-new-gtld-agreement-201…>. These amendments have been under discussion between the Registries Stakeholder Group (RySG) and ICANN for 18 months. The public comment period closes on July 13 and there is a cross-community session scheduled at 10:30 a.m. on Tuesday in Helsinki. * In 2012 and 2013, the SSAC <https://www.icann.org/en/system/files/files/sac-053-en.pdf>, IAB <https://www.iab.org/documents/correspondence-reports-documents/2013-2/iab-s…>, ALAC <http://atlarge-lists.icann.org/pipermail/alac/attachments/20130611/2e639e17…>_,_ GAC <http://archive.icann.org/en/meetings/durban2013/bitcache/GAC%20Communiqu%c3…>, and the ICANN Board <https://www.icann.org/resources/board-material/resolutions-new-gtld-2013-08…> all recognized the risk posed by any introduction of dotless domains in new gTLDs. * In August 2013, the ICANN Board’s New gTLD Program Committee (NGPC) voted <https://www.icann.org/resources/board-material/resolutions-new-gtld-2013-08…> to prohibit dotless domains. * The proposed New gTLD Registry Agreement (RA) amendments include a change in Exhibit A (Approved Services) related to dotless domains. While it states appropriately that dotless domains are not permitted, it intentionally or inadvertently introduces a new path for approval of dotless domains via the Registry Services Evaluation Process (RSEP). The relevant language is below: o (Note: The above language effectively does not allow, among other things, the inclusion of DNS resource records that would enable a dotless domain name (e.g., apex A, AAAA, MX records) in the TLD zone.) If Registry Operator wishes to place any DNS resource record type or class into its TLD DNS service (other than those listed in Sections 1.1 or 1.2 above), it must describe in detail its proposal and submit a Registry Services Evaluation Process (RSEP) request. This will be evaluated per RSEP to determine whether the service would create a risk of a meaningful adverse impact on security or stability of the DNS. Registry Operator recognizes and acknowledges that a service based on the use of less-common DNS resource records and/or classes in the TLD zone, even if approved, might not work as intended for all users due to lack of software support. * The explanatory notes accompanying the proposed amended RA do not explain why this change creating a path to approval of dotless domains has been included, and there has been no change in the position of the ICANN Board, IAB, SSAC, GAC or ALAC on this issue. Unlike the previously stated positions of those entities, ICANN’s explanatory notes are silent. How and why was this language included in the proposed amendment? It appears to be pointless to propose a path to try and circumvent such a clearly established prohibition. * Using the RSEP process in this manner risks demoting any future evaluation of registry proposals on dotless domains to ICANN staff without appropriate policy work and/or community consideration. * Introduction of this proposed use of RSEP is inappropriate and it should be removed. In light of the ICANN Board’s August 2013 resolution and the significant security and stability concerns raised by the IAB and SSAC, dotless domains should instead receive the same treatment in the New gTLD RA as Wildcarding, which is explicitly prohibited in Section 2.2. I look forward to your feedback and hope that the ALAC will make a Statement about this issue in response to the Public Consultation on Proposed Amendments to Base New gTLD Registry Agreement. Perhaps should we include in our Statement a direct question to the SSAC asking whether their advice has changed? This way, they would be able to respond to the public record accordingly. Kindest regards, Olivier MJ Crépin-Leblond

5 5

Re: [ALAC] [EURO-Discuss] [lac-discuss-es] [At-Large] Milestone: The Number of At-Large Structures Reach 200!
by Nigel Hickson June 27, 2016

June 27, 2016

Good afternoon; Superb indeed; congratulations. Here is to another 200! Best Nigel From: <euro-discuss-bounces(a)atlarge-lists.icann.org<mailto:euro-discuss-bounces@atlarge-lists.icann.org>> on behalf of "mario.ale1(a)gmail.com<mailto:mario.ale1@gmail.com>" <mario.ale1(a)gmail.com<mailto:mario.ale1@gmail.com>> Date: Friday 24 June 2016 00:22 To: Capda Capda <capdasiege(a)gmail.com<mailto:capdasiege@gmail.com>> Cc: LACRALO discussion list <lac-discuss-en(a)atlarge-lists.icann.org<mailto:lac-discuss-en@atlarge-lists.icann.org>>, "lac-discuss-es(a)atlarge-lists.icann.org<mailto:lac-discuss-es@atlarge-lists.icann.org>" <lac-discuss-es(a)atlarge-lists.icann.org<mailto:lac-discuss-es@atlarge-lists.icann.org>>, "alac(a)atlarge-lists.icann.org<mailto:alac@atlarge-lists.icann.org>" <alac(a)atlarge-lists.icann.org<mailto:alac@atlarge-lists.icann.org>>, "euro-discuss(a)atlarge-lists.icann.org<mailto:euro-discuss@atlarge-lists.icann.org>" <euro-discuss(a)atlarge-lists.icann.org<mailto:euro-discuss@atlarge-lists.icann.org>>, "afri-discuss(a)atlarge-lists.icann.org<mailto:afri-discuss@atlarge-lists.icann.org>" <afri-discuss(a)atlarge-lists.icann.org<mailto:afri-discuss@atlarge-lists.icann.org>>, Antonio Medina Gómez <amedinagomez(a)gmail.com<mailto:amedinagomez@gmail.com>>, "alac-announce(a)atlarge-lists.icann.org<mailto:alac-announce@atlarge-lists.icann.org>" <alac-announce(a)atlarge-lists.icann.org<mailto:alac-announce@atlarge-lists.icann.org>>, APRALO m <apac-discuss(a)atlarge-lists.icann.org<mailto:apac-discuss@atlarge-lists.icann.org>>, "at-large(a)atlarge-lists.icann.org<mailto:at-large@atlarge-lists.icann.org>" <at-large(a)atlarge-lists.icann.org<mailto:at-large@atlarge-lists.icann.org>>, "na-discuss(a)atlarge-lists.icann.org<mailto:na-discuss@atlarge-lists.icann.org>" <na-discuss(a)atlarge-lists.icann.org<mailto:na-discuss@atlarge-lists.icann.org>> Subject: Re: [EURO-Discuss] [lac-discuss-es] [At-Large] Milestone: The Number of At-Large Structures Reach 200! Congratulations to all dedicated volunteers and outstanding staff coordinating the outreach activities. Best Mario Sent from my iPhone On Jun 23, 2016, at 5:14 PM, Capda Capda <capdasiege(a)gmail.com<mailto:capdasiege@gmail.com>> wrote: Hi all, Congratulations to everyone who worked hard in the outreach necessary to reach this milestone! Lively encouragementto the entire ALS community for this performance. Best, 2016-06-23 22:26 GMT+02:00 Antonio Medina Gómez <amedinagomez(a)gmail.com<mailto:amedinagomez@gmail.com>>: Una gran noticia!!! Ya son 200 las organizaciones que constituyen la comunidad At-Large. La Asociación Colombiana de Usuarios de Internet, ACUI, registra con satisfacción esta buena nueva. Cordial saludo El 23/06/2016 14:17, "ICANN At-Large Staff" <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>> escribió: Dear All, Today, on 23 June 2016, we celebrate an exciting milestone in the history of the At-Large Community – the At-Large Advisory Committee (ALAC) has accredited the 200th organization as an At-Large Structure (ALS). From the Arctic to the Cook Islands, ALSes form the basis of the At-Large community, which represents the best interests of Internet users in ICANN’s multistakeholder model. Across the world’s five geographic regions, 92 countries and territories now have ALSes, with 42 ALSes in Africa, 44 in Asia Pacific, 37 in Europe, 50 in Latin America and the Caribbean Islands, and 27 in North America. Since September 2003 when the first ALS, the Internet Society Italy Chapter, was accredited, the At-Large Community has seen a steady increase of ALSes. In the past five years, the At-Large Community has gained approximately 14 ALSes each year. An ALS is a wholly independent organization from ICANN. Whether it is an Internet-related consumer rights groups or an academic organization, ALSes share the passion in furthering the development of Information and Communication Technologies and contributing to policy activities that influence the technical coordination of the Domain Name Systems. In fact, about 33% ALSes are Internet Society Chapters. The ALS accreditation process recognizes that these groups meet ICANN’s criteria for involving individual Internet users at the local or issue level, as well as for promoting individuals’ understanding of and participation in ICANN. Within ICANN, they actively contribute to policy advice development activities and play a key role in ICANN’s regional outreach strategies and civil society engagement. They work to ensure that the Internet continues to serve the global public interest. To learn more about ALSes, please visit: https://atlarge.icann.org/alses. <image001.png> Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar 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> _______________________________________________ lac-discuss-es mailing list lac-discuss-es(a)atlarge-lists.icann.org<mailto:lac-discuss-es@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es http://www.lacralo.org _______________________________________________ At-Large mailing list At-Large(a)atlarge-lists.icann.org<mailto:At-Large@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large Official Site: http://atlarge.icann.org -- Michel TCHONANG LINZE Coordinateur Général Coordonnateur Régional Afrique Centrale Réseau Panafricain Société Civile (ACSIS) ÉVÈNEMENTS SUR LES TIC : * ICANN56 du 27 au 30 juin 2016 à Helsinki - Finlande * UNCTAD 14 du 17 au 22 juillet 2016 à Nairobi - Kenya * Symposium TIC AFRIQUE du 02 au 05 Août 2016 à Yaoundé - CAMEROUN * 3èmeréunion de la Commission d'études 1&2 de l'UIT-D<http://www.itu.int/net4/ITU-D/CDS/sg/blkmeetings.asp?lg=2&sp=2014&blk=14384> du 19- 23 et du 26- 30 septembre 2016, Suisse- Genève * Réunion groupe des experts TIC (EGH et EGTI) du 04 au 07/10/2016 à Genève -Suisse * 11ème FGI du 06 au 09 Décembre 2016 à Guadalajara au Mexique CAPDA (Consortium d'Appui aux Actions pour la Promotion et le Développement de l'Afrique) BP : 15 151 DOUALA - CAMEROUN Tél. : (237) 67775-39-63 / 24212-9493 Email : capdasiege(a)gmail.com<mailto:capdasiege@gmail.com> _______________________________________________ lac-discuss-es mailing list lac-discuss-es(a)atlarge-lists.icann.org<mailto:lac-discuss-es@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es http://www.lacralo.org

1 0

Re: [ALAC] Explanation of RoP Director voting alternatives
by Alan Greenberg June 26, 2016

June 26, 2016

Tijani, can you please say what exactly the issue is. I see no reason not to proceed is it is possible to address your concern in the time we have. All that is being proposed is clear naming of the organization we already have. These proposed RoP changes have bee out for comment for three weeks now. Alan At 26/06/2016 04:19 AM, tijani.benjemaa(a)topnet.tn wrote: >Alan, > >Yes, of course, I want it to be clearly defined, but after deeper >reflection. As you know, we will have to modify our RoP to comply with >the bylaws change, so, lets take our time and make it more systematic. > >----------------------------------------------------------------------------- >Tijani BEN JEMAA >Executive Director >Mediterranean Federation of Internet Associations (FMAI) >Phone: +216 98 330 114 > +216 52 385 114 >----------------------------------------------------------------------------- > >Le 26 juin 2016 Ã 10:24, Alan Greenberg <alan.greenberg(a)mcgill.ca> a Ã©crit : > >Tijani, when I distributed the revisions, I said "If there is any >serious objection to these changes that cannot be readily adjusted, >they will be withdrawn to not delay the changes to Section 19." > >I stand by that. If there is substantive concern with the changes >unrelated to the Director Selection that cannot be quickly addressed, >then they will be withdrawn. > >However, in relation to the section 3.5 that you are referring to, >there are no operational changes being proposed. As Chair, I have >chosen to invite certain people to the ALT meetings (they are after >all generally open meetings!) and I have also in a few cases asked >some people to participate in the rare in camera confidential >discussions. The proposed changes ONLY add the nomenclature of >"advisor" so that we have clarity when referring to the ALT exactly >who is and is not included. Without the change it has often been >unclear whether the Liaisons to ICANN bodies are or are not included >in the definition of the ALT. > >The inclusion of some past Chairs is at the discretion of the current >Chair, and whether they are referenced in a formal definition does not >alter whether they are included in a particular meeting or not. > >If there is a general feeling within the ALAC that we should not >clarify the definition, then it will be withdrawn. > >Alan > >At 26/06/2016 01:59 AM, tijani.benjemaa(a)topnet.tn wrote: > >Dear Alan, > >I read again the proposal for update of the RoP, and found that it is >not adequate to make the modifications that are not necessary for the >Board Director Selection at this time because we didnÃ¢ÂÂt have time to >discuss them deeply, and because there is no urgency in making those >modifications. > >I especially thought about the proposal to include the former ALAC >Chairs in the ALT as advisors. This will have as a consequence the >number of advisors growing each time we change the ALAC Chair. And >also, if we are seeking advices, why donÃ¢ÂÂt also include the former >Board members such as Jean Jacques, Vanda and Sebastien? > >So, I propose to make the proposed modifications related to the >selection of the Board member selected by At-Large only, leaving the >remaining modifications to deeper reflection before adopting them. > >----------------------------------------------------------------------------- >Tijani BEN JEMAA >Executive Director >Mediterranean Federation of Internet Associations (FMAI) >Phone: +216 98 330 114 > +216 52 385 114 >----------------------------------------------------------------------------- > >

2 2

Addendum to RoP Revision
by Alan Greenberg June 26, 2016

June 26, 2016

Please find attached an addendum to the RoP revision. There are two parts. 1. A clarification sentence added to Paragraph 19.11.3 2. The full text to be inserted for Paragraph 19.11.4 representing the four options described in the RoP revision. Alan

1 0

Re: [ALAC] Explanation of RoP Director voting alternatives
by tijani.benjemaa＠topnet.tn June 26, 2016

June 26, 2016

Alan, Yes, of course, I want it to be clearly defined, but after deeper reflection. As you know, we will have to modify our RoP to comply with the bylaws change, so, lets take our time and make it more systematic. ----------------------------------------------------------------------------- Tijani BEN JEMAA Executive Director Mediterranean Federation of Internet Associations (FMAI) Phone: +216 98 330 114 +216 52 385 114 ----------------------------------------------------------------------------- Le 26 juin 2016 à 10:24, Alan Greenberg <alan.greenberg(a)mcgill.ca> a écrit : Tijani, when I distributed the revisions, I said "If there is any serious objection to these changes that cannot be readily adjusted, they will be withdrawn to not delay the changes to Section 19." I stand by that. If there is substantive concern with the changes unrelated to the Director Selection that cannot be quickly addressed, then they will be withdrawn. However, in relation to the section 3.5 that you are referring to, there are no operational changes being proposed. As Chair, I have chosen to invite certain people to the ALT meetings (they are after all generally open meetings!) and I have also in a few cases asked some people to participate in the rare in camera confidential discussions. The proposed changes ONLY add the nomenclature of "advisor" so that we have clarity when referring to the ALT exactly who is and is not included. Without the change it has often been unclear whether the Liaisons to ICANN bodies are or are not included in the definition of the ALT. The inclusion of some past Chairs is at the discretion of the current Chair, and whether they are referenced in a formal definition does not alter whether they are included in a particular meeting or not. If there is a general feeling within the ALAC that we should not clarify the definition, then it will be withdrawn. Alan At 26/06/2016 01:59 AM, tijani.benjemaa(a)topnet.tn wrote: Dear Alan, I read again the proposal for update of the RoP, and found that it is not adequate to make the modifications that are not necessary for the Board Director Selection at this time because we didnât have time to discuss them deeply, and because there is no urgency in making those modifications. I especially thought about the proposal to include the former ALAC Chairs in the ALT as advisors. This will have as a consequence the number of advisors growing each time we change the ALAC Chair. And also, if we are seeking advices, why donât also include the former Board members such as Jean Jacques, Vanda and Sebastien? So, I propose to make the proposed modifications related to the selection of the Board member selected by At-Large only, leaving the remaining modifications to deeper reflection before adopting them. ----------------------------------------------------------------------------- Tijani BEN JEMAA Executive Director Mediterranean Federation of Internet Associations (FMAI) Phone: +216 98 330 114 +216 52 385 114 -----------------------------------------------------------------------------

1 0

Re: [ALAC] Explanation of RoP Director voting alternatives
by Alan Greenberg June 26, 2016

June 26, 2016

Tijani, when I distributed the revisions, I said "If there is any serious objection to these changes that cannot be readily adjusted, they will be withdrawn to not delay the changes to Section 19." I stand by that. If there is substantive concern with the changes unrelated to the Director Selection that cannot be quickly addressed, then they will be withdrawn. However, in relation to the section 3.5 that you are referring to, there are no operational changes being proposed. As Chair, I have chosen to invite certain people to the ALT meetings (they are after all generally open meetings!) and I have also in a few cases asked some people to participate in the rare in camera confidential discussions. The proposed changes ONLY add the nomenclature of "advisor" so that we have clarity when referring to the ALT exactly who is and is not included. Without the change it has often been unclear whether the Liaisons to ICANN bodies are or are not included in the definition of the ALT. The inclusion of some past Chairs is at the discretion of the current Chair, and whether they are referenced in a formal definition does not alter whether they are included in a particular meeting or not. If there is a general feeling within the ALAC that we should not clarify the definition, then it will be withdrawn. Alan At 26/06/2016 01:59 AM, tijani.benjemaa(a)topnet.tn wrote: >Dear Alan, > >I read again the proposal for update of the RoP, and found that it is >not adequate to make the modifications that are not necessary for the >Board Director Selection at this time because we didnât have time to >discuss them deeply, and because there is no urgency in making those >modifications. > >I especially thought about the proposal to include the former ALAC >Chairs in the ALT as advisors. This will have as a consequence the >number of advisors growing each time we change the ALAC Chair. And >also, if we are seeking advices, why donât also include the former >Board members such as Jean Jacques, Vanda and Sebastien? > >So, I propose to make the proposed modifications related to the >selection of the Board member selected by At-Large only, leaving the >remaining modifications to deeper reflection before adopting them. > >----------------------------------------------------------------------------- >Tijani BEN JEMAA >Executive Director >Mediterranean Federation of Internet Associations (FMAI) >Phone: +216 98 330 114 > +216 52 385 114 >-----------------------------------------------------------------------------

1 0

Explanation of RoP Director voting alternatives
by tijani.benjemaa＠topnet.tn June 26, 2016

June 26, 2016

Dear Alan, I read again the proposal for update of the RoP, and found that it is not adequate to make the modifications that are not necessary for the Board Director Selection at this time because we didn’t have time to discuss them deeply, and because there is no urgency in making those modifications. I especially thought about the proposal to include the former ALAC Chairs in the ALT as advisors. This will have as a consequence the number of advisors growing each time we change the ALAC Chair. And also, if we are seeking advices, why don’t also include the former Board members such as Jean Jacques, Vanda and Sebastien? So, I propose to make the proposed modifications related to the selection of the Board member selected by At-Large only, leaving the remaining modifications to deeper reflection before adopting them. ----------------------------------------------------------------------------- Tijani BEN JEMAA Executive Director Mediterranean Federation of Internet Associations (FMAI) Phone: +216 98 330 114 +216 52 385 114 -----------------------------------------------------------------------------

1 0

Fwd: VOTE RESULT: Appointment of the ALAC Liaison to the GAC
by Alan Greenberg June 25, 2016

June 25, 2016

I would like to congratulate Yrjö and welcome him to this new role. Alan >From: ICANN At-Large Staff <staff(a)atlarge.icann.org> >To: <alac-announce(a)atlarge-lists.icann.org> >Date: Fri, 24 Jun 2016 09:41:50 +0000 >Subject: [ALAC-Announce] VOTE RESULT: >Appointment of the ALAC Liaison to the GAC > > >Dear All, > >Alan Greenberg, Chair of the ALAC, has asked >that the following message be distributed. > >============================ > >During the ICANN55 meeting in Marrakech, the >ALAC proposed to the Governmental Advisory >Committee (GAC) that the two groups exchange >Liaisons. The ALAC had long discussed the >possibility of this happening, and it was with >great pleasure that the GAC agreed in principle. > >More recently we have had formal approval to >appoint our Liaison. There was a consensus >within the ALAC that we should not delay and >should have an appointment in time for the >ICANN56 Helsinki meeting. Because of the short >time-frame, the ALAC requested that the ALAC >Leadership Team (the ALT, with one ALAC Member >from each of the five regions) make a >recommendation to the ALAC on who to appoint for >the interim period from now until the end of the >ICANN Annual General Meeting, ICANN57, scheduled >to be held in Hyderabad India in November 2016. > >The ALT recommended that YrjÃ¶ LÃ¤nsipuro, be >appointed. YrjÃ¶ is a very well respected member >of the At-Large Community, having served us in a >number of capacities and now being the EURALO >delegate to the Nominating Committee. Prior to >his involvement in At-Large, YrjÃ¶ served on the >GAC representing Finland. Accordingly, he is >very well versed on both sides of this new role. > >The ALAC has now voted and I am delighted to >report that YrjÃ¶ has been appointed as the >Liaison to the GAC for the interim period until the end of ICANN57. > >Over the coming months, the ALAC will issue a >Call for Nominations for the position for the 2016-2017 ICANN year. > >The formal results of the ALAC vote follow. > >Alan Greenberg >Chair, ALAC > >============================= > >Kindly note that the vote held by the ALAC on >the proposed ratification of the ALAC Liaison to the GAC is now closed. > >Motion: > >Whereas the ALAC proposed to the Governmental >Advisory Committee (GAC) that the two groups exchange Liaisons; > >Whereas the GAC has agreed; > >Whereas there is insufficient time to enter into >a formal nomination, evaluation and selection process; > >Whereas the ALAC decided by consensus that the >ALAC Leadership Team (ALT) should recommend a >person to fill the role of Liaison from the ALAC >to the GAC on an interim basis; > >Whereas the ALT has unanimously recommended that >YrjÃ¶ LÃ¤nsipuro fill that role in consideration >of his experience as a GAC Member as well as the >many other roles he has played within ICANN and At-Large. > >Therefore: > >The ALAC ratifies this recommendation and >appoints YrjÃ¶ LÃ¤nsipuro as the ALAC Liaison to >the GAC for a period beginning immediately and >ending at the conclusion of the ICANN 57 meeting >currently scheduled to be held in Hyderabad India, 03-09 November 2016. > >As at Poll close: Thursday 23 June 2016 23:59 UTC >Number of voters: 13 Â· Group size: 15 Â· Percentage voted: 86.67 >Ranked by votes >Rank >Options ID >Options >Votes >% >1 >15841057 >Yes >11 >84.62 >2 >15841059 >Abstain >2 >15.38 >3 >15841058 >No >0 >0.00 > >To confirm, YrjÃ¶ LÃ¤nsipuro will assume the >ALAC Liaison to the GAC position for a period >beginning immediately and ending at the >conclusion of the ICANN57 meeting currently >scheduled to be held in Hyderabad India, 03-09 November 2016. > >You may view the result independently under ><https://www.bigpulse.com/pollresults?code=5733ItbWTRyIFMSVPGN75i78>https://www.bigpulse.com/pollresults?code=5733ItbWTRyIFMSVPGN75i78 > > >Heidi Ullrich, Silvia Vivanco, Ariel Liang, >Gisella Gruber, Nathalie Peregrine, Terri Agnew and YeÅim Nazlar >ICANN Policy Staff in support of the At-Large Community >E-mail: <mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org >Website: <https://atlarge.icann.org/>atlarge.icann.org >Facebook: ><https://www.facebook.com/icannatlarge>facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge >Twitter: ><https://twitter.com/ICANNAtLarge>@<https://twitter.com/ICANNAtLarge>ICANNAtLarge > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;SN1PR0301MB2030;9:hcOKEyFeZmVDZ3DElt0Tu9Ihs5L3oZx/7si63gSoioZX/8y+lHZeHr0zhEozMHLV8ARTKEMixtwmsA5Fehsdz3JXPl9Idrw38Mm0RnXNcG3QeWmSKghgyjBeWhqpeIbPb03GCNlAJ2A3R9Lu43micdzHkH8Yn1idjJgpJeXQDwbhjB/GiqH7Wc0fK92AHqBz > >_______________________________________________ >ALAC-Announce mailing list >ALAC-Announce(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac-announce > >At-Large Official Site: http://www.atlarge.icann.org

8 7