- ALAC-Announce - lists.icann.org

Performance Overview ALAC Members and Liaisons
by At-Large Staff Aug. 25, 2008

Aug. 25, 2008

Dear all, This document was attached as a PDF file to the email sent out last Friday on the upcoming ALAC elections. Unfortunately, it was saved under a different format in the mailing list archive and most subscribers were unable to open it. The configuration of the mailing list has now been changed and everybody should be able to see it. Regards, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

Global ALAC election process
by At-Large Staff Aug. 22, 2008

Aug. 22, 2008

Dear all, As you know, the ICANN annual meeting in Cairo will mark the end of the terms of: 1. One Member of the At-Large Advisory Committee from each Geographic Region; 2. The officers of the ALAC; 3. The Liaisons appointed by the ALAC To help ensure the elections for the open positions run smoothly, this email will provide you with an overview of the election process as it relates to the elections of Members of the At-Large Advisory Committee. You will find: * The general provisions governing the elections (ICANN By-laws and ALAC rules of procedures) * A suggestion for an election timetable for all regions * The regional provisions governing the elections (regional MoU and Operating Principles) * An overview of open ALAC positions General provisions governing the elections When the RALOs were formed in 2006 and 2007, the Memoranda of Understanding (MOU) and regional Operating Principles did not, with one exception, cover the voting process (nomination period, timing and other rules governing the elections) in any detail. Most regional instruments only say that the region is responsible for electing two out of the three regional ALAC positions, the third position being appointed by the NomCom. Given the lack of clear provisions on the election process in the regional instruments, one needs to turn to the ICANN by-laws, the Rules of Procedure of the RALOs (for those which have adopted RoPs), and to the extent RALOs who would otherwise not have specific rules for the conduct of elections, if they so desire the ALAC rules of procedure. The ICANN by-laws, which apply to all regions, do not cover the election process but make clear that the regional ALAC members will serve two-year terms starting at the conclusion of an annual ICANN meeting. The terms are staggered, meaning that one term will start in an odd-numbered year and one term will start in an even-numbered year: ICANN Bylaws: Article Xi, Section 2.4.c 1. The term of one member selected by each RALO shall begin at the conclusion of an ICANN annual meeting in an even-numbered year. 2. The term of the other member selected by each RALO shall begin at the conclusion of an ICANN annual meeting in an odd-numbered year. See: http://www.icann.org/en/general/bylaws.htm <http://www.icann.org/en/general/bylaws.htm> At-Large Advisory Committee Internal Rules of Procedure The ALAC rules of procedure, on the other hand, only contain rules that apply to the ALAC officer elections: 1. Call for election: no earlier than one month before the ICANN meeting and no later than three weeks before an ICANN meeting (rule 9) 2. Deadline for nominations: 14 days after election call (rule 9) 3. Acceptance period: Nomination must be accepted no later than 7 days after the nomination deadline and no later than 7 days before the start of an ICANN meeting (rule 9) See: https://st.icann.org/alac/index.cgi?rules_of_procedure <https://st.icann.org/alac/index.cgi?rules_of_procedure> (At-Large Advisory Committee Rules of Procedure) Suggested election procedure for ALAC representatives: Since the RALOs have few details about the procedure by which they elect their ALAC members, it is suggested that the election process for ALAC representatives use the procedure by which ALAC elects officers and liaisons: * Call for election: The regional Secretariat will make a call for election no later than seven weeks before the start of the annual ICANN meeting (14 September 2008) * Nomination Period: nominations shall be accepted for two weeks after the Secretariat calls for nominations (28 September 2008) * Acceptance deadline: the nominees need to accept their nomination no later than seven days after the nomination period ends (05 October 2008) * Election deadline: The election shall begin no later than one week after the end of the acceptance deadline (12 October 2008) and end not later than two weeks before the start of the annual ICANN meeting. (19 October 2008). In other words, votes would actually be cast between 12 to 19 October 2008) Voting Mechanism We would suggest that the online voting system used previously in various regions at www.bigpulse.com <http://www.bigpulse.com> (and which is used for all ALAC votes including for ALS Applications). The staff would administer these votes through the system, in all cases allowing independent verification via a URL located on the BigPulse servers which would provide the results of votes held. There are two regions NARALO and LACRALO which have adopted detailed Rules of Procedure for meetings. These RALOs may wish to use the elections procedures as specified in those RoPs, since they do provide clauses which allow online meetings to vote on various issues. Regional provisions governing the elections Various RALOs are at present speaking about the upcoming elections. A separate email communication follows this message that is tailored for each RALO, in hopes that this is useful in facilitating this process. AFRALO: a) Length of the nomination period: "a reasonable period shall be provided" (MOU:2.) b) Election date: not specified c) Additional provisions: one- year term, one vote per ALS (MOU:2) See: https://st.icann.org/afralo/index.cgi?mou_and_organising_documents <https://st.icann.org/afralo/index.cgi?mou_and_organising_documents To make sure that there will be staggered terms in all regions, it was decided that one of the current African ALAC positions shall be for two years and one should be for one years (see below for an overview of all open ALAC positions). In accordance with the ICANN bylaws, the terms of African ALAC representatives shall be set to two years. APRALO: a) Length of the nomination period: not specified b) Election date: not specified c) Additional provisions: "one vote per ALS" See: https://st.icann.org/asiapac/index.cgi?ralo_organising_documents <https://st.icann.org/asiapac/index.cgi?ralo_organising_documents EURALO: a) Length of the nomination period: not specified b) Election date: not specified c) Additional provisions: The European Mou says that ³The voting rights shall be determined by the EURALO.² (EURALO MoU, 5.4.1). According to the EURALO Bylaws, the European representatives elect the regional ALAC members at their General Assembly ( EURALO Bylaws, 11.10). The following rules govern the decisions of the GA: ³... each Member has one vote.² (11.4) whereas ³ Members of The Association shall consist of ...... organisations domiciled in Europe ........ which qualify as an ALS.² (EURALO Bylaws 4.1.) Additionally, the selected representatives must be members of different ALSes, must have their principal residence in different countries of the region and their nationalities must be different. To the extent possible, gender balance and regional balance within Europe shall be fostered.²(11.5 EURALO Bylaws). See: https://st.icann.org/euralo/index.cgi?ralo_organising_instruments <https://st.icann.org/euralo/index.cgi?ralo_organising_instruments> LACRALO: a) Length of the nomination period: not specified b) Election date: not specified c) Additional provisions: two-year terms, "no re-election", one vote per ALS (Operating Principles 8) Detailed provisions for elections and voting during meetings can be found under: https://st.icann.org/lacralo/index.cgi?ralo_organising_documents <https://st.icann.org/lacralo/index.cgi?ralo_organising_documents> It is up to the region to decide if it wishes to treat the election as if it were a meeting. NARALO: a) Length of the nomination period: 30 days (Operating Principles 11) Start of nomination period: on or before 1 July (OP 11) b) Election date: "sufficiently in advance of ICANN's annual meeting" (OP 11) c) Additional provisions: ALAC representatives may not serve more than two consecutive terms (OP 10) Detailed provisions for elections and voting during meetings can be found under: See: https://st.icann.org/naralo/index.cgi?ralo_organizing_documents <https://st.icann.org/naralo/index.cgi?ralo_organizing_documents> It is up to the region to decide if it wishes to treat the election as if it were a meeting. Open ALAC positions: AFRALO: Hawa Diakité¹s term expires after the annual ICANN meeting in 2008 APRALO: Izumi Aizu¹s term expires after the annual ICANN meeting in 2008 EURALO: Sébastien Bachollet¹s term expires after the annual ICANN meeting in 2008. Veronica Cretu stepped back from her position earlier this year. It is suggested that there shall be a call for somebody to replace her until the end of her term, which ends at the end of the ICANN annual meeting in 2009. LACRALO: José Ovidio Salgueiro¹s term expires after the annual ICANN meeting in 2008 NARALO: Beau Brendler¹s term expires after the annual ICANN meeting in Cairo Minimum Participation Requirements With respect to the Minimum Participation Requirements for Members of the At-Large Advisory Committee, the ALAC Rules of Procedure in Rule 21 is relevant. Rule 21.9 is of particular importance as it talks about the quantitative requirements. They are: A) Participation in at least 2/3 of the ALAC conference calls in any 6-month period B) Attending at least one physical meeting in any 9 month period C) Completing at least one feedback survey on At-Large issues in any 6 month period With regards rules A) and B) above, please find attached the attendance record for ALAC members and Liaisons. It covers the nine months preceding August 2008. The Staff will keep this up to date and publicly accessible. Regards, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

5 September 1300 UTC: Board Liaison Candidates Presentation
by At-Large Staff Aug. 22, 2008

Aug. 22, 2008

Dear all, We would like to invite you to a conference call with the ALAC Board Liaison candidates. Following a short introduction of the candidates, Wendy Seltzer and Beau Brendler will be available to answer your questions. The conference will be Friday September 5th from 1300 UTC to 1400 UTC . There will be simultaneous interpretation into French and Spanish. Participants are requested to provide their comments or questions in advance, to the extent possible, at the following URL by using the Comment¹ button at the top of the page: https://st.icann.org/alac/index.cgi?board_liaison_candidates_presentation You may also find participation instructions and the curricula vitae of the candidates on this page. Regards, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

New Fast Track IDN microsite available on icann.org
by At-Large Staff Aug. 21, 2008

Aug. 21, 2008

Dear Community: Today ICANN have announced the creation of a new topic area on the ICANN site, for Fast Track IDN ccTLD related information. It can be found at: http://www.icann.org/en/topics/idn/fast-track/ This area will capture all activities in relation to the policy and implementation of the fast-track process. We hope you find it useful and for those concerned with IDNs, we hope this is a useful bookmark to add. -- Regards, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

Nominating Committee Appointments by ALAC for 2009 - IMPORTANT DEADLINE APPROACHING
by Nick Ashton-Hart Aug. 19, 2008

Aug. 19, 2008

Dear At-Large ALS Representatives: Please be reminded that the deadline for forwarding a list of one or more proposed candidates from each region for the Nominating Committee appointments which are appointed each year by the At-Large Advisory Committee is fast approaching - it is one week from today, 24th August 2008. Your region may nominate the incumbent, or may propose new names, or a combination of both. Any region which does not propose a name or names for consideration will likely find that the ALAC resolves to reappoint the incumbent, all of whom are eligible for reappointment. Below you will find the email from Cheryl sent to the public working ALAC list on this subject on 15th August 2008. ---- Further to our Agenda Item and discussion on August 12th regarding this issue, (unfortunately not all RALO's were able to be represented at this meeting) here is the details and clarification of what each RALO is requested to attend to regarding the appointment or reappointment of our ALAC representatives on the Nominating Committee for 2009:- The Bylaws of ICANN in Article VII, s2(6) (http://www.icann.org/en/general/bylaws.htm#VII) the At-Large Advisory Committee selects five voting members of the Nominating Committee. Each serves a one year term, however, each may be re-appointed for an additional one year term Per Article VII, s3(1). Per Article XI,S2(4)(b), the five appointees must be "one citizen of a country within each of the five Geographic Regions..." With respect to how the ALAC is to appoint the five NomCom members, Article XI, S2(4(e) requires that the ALAC "shall, after consultation with each RALO, annually appoint five voting delegates..." The Nominating Committee Chair has asked that the ALAC appointments be made known to the NomCom by the end of August 2008. Those appointed last year are all eligible for reappointment, should they agree to serve, and are maintained as the recommended nominee from each RALO then each RALO is requested to send a confirmation note regarding this to the Chair of the ALAC and the ALAC has agreed to endorse their reappointment for 2009. Should any RALO require or desire further specific information (drawn from my teleconference meeting with the NomCom ;eadership on the 13th) I am more than willing to provide this by either email or telecom; please let me know if you wish me do so when and how. TIMELINE AND PROCESS Not later than 25th August, each RALO shall provide to the ALAC a name or names of candidates that are citizens of a country within their Geographic Region, as required by Articles as referenced above. The ALAC will then vote on those names provided (providing they are not the name of the incumbent in which case they will be endorsed) to select one name from within the list submitted by each RALO, unless only one name is provided, in which instance that person will be automatically selected. As Chair I will then convey the results to the Chair of the Nominating Committee no later than close of business Pacific Time August 31st REQUIREMENTS OF NOMCOM MEMBERS When forwarding names for consideration for appointment, each RALO is advised to ensure that those selected meet the requirements as specified in Article VII, s4, as follows: Delegates to the ICANN Nominating Committee shall be: 1. Accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and with experience and competence with collegial large group decision-making; 2. Persons with wide contacts, broad experience in the Internet community, and a commitment to the success of ICANN; 3. Persons whom the selecting body is confident will consult widely and accept input in carrying out their responsibilities; 4. Persons who are neutral and objective, without any fixed personal commitments to particular individuals, organizations, or commercial objectives in carrying out their Nominating Committee responsibilities; 5. Persons with an understanding of ICANN's mission and the potential impact of ICANN's activities on the broader Internet community who are willing to serve as volunteers, without compensation other than the reimbursement of certain expenses; and 6. Persons who are able to work and communicate in written and spoken English. Finally as a result of the discussion during our August meeting after my recent conversation with the NomCom leadership, it is envisaged that we will receive feedback on the performance metrics of the 2009 NomCom appointees from the ALAC during the Mexico meeting in 2009 for use in our ongoing information and future advice. Cheryl Langdon-Orr (CLO) cheryl(a)hovtek.com.au -- Regards, Nick Ashton-Hart Director for At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Main Tel: +33 (450) 40 46 88 USA DD: +1 (310) 578-8637 Fax: +41 (22) 594-85-44 Mobile: +41 (79) 595 54-68 email: nick.ashton-hart(a)icann.org Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart

1 0

26 Agosto 1300 UTC: reunión de información sobre la suplantación de nombres en los ataques de phishing
by At-Large Staff Aug. 19, 2008

Aug. 19, 2008

Hola a todos, Les queremos invitar a una reunión de información organizada por Dave Piscitello del comité de asesores de seguridad y estabilidad de ICANN (Security and Stability Advisory Committee (SSAC)) sobre la suplantación de nombres en los ataques de phishing (Registrar Impersonation in Phishing Attacks). La reunión será el 26 de Agosto a las 1300 UTC. Lo interpretará simultaneamente en lengua española y francesa así como una grabación de audio. Véase la página web de este reunión telefónica para ver las instrucciones de participación y el boletín del SSAC sobre este tema. Tambien hay un enlace para asistir a la presentación en Adobe Connect. https://st.icann.org/alac/index.cgi?registrar_impersonation_in_phishing_atta cks ¿Que es la suplantación de nombres en los ataques de phishing? El atacante se hace pasar por un registrador de nombres de dominio y envía una correspondencia esperada o no a un cliente del registrador (un registrante) sobre un asunto relacionado con el nombre de dominio. Como ejemplos de correspondencia esperada podríamos mencionar: una notificación del vencimiento pendiente del registro de un nombre de dominio, un mensaje promocional enviado por correo electrónico, una notificación para informar al registrante sobre un problema en la administración de una cuenta o, en general, cualquier tipo de correspondencia que requiera o reclame la atención inmediata del cliente. Sin embargo, la correspondencia es falsa. El atacante crea un sitio web que es engañosamente similar al sitio del registrador a fin de inducir al cliente a tener acceso a su cuenta de administración de dominio y a que le revele inadvertidamente las credenciales de su cuenta. El atacante utilizará las credenciales que obtuvo del cliente para tener acceso a la cartera de nombres de dominio del cliente, alterar la información del sistema de nombres de dominio de esa cuenta y utilizar los dominios para secundar otros ataques. Cordialmente, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

26 aout 1300 UTC: Présentation sur l¹usurpation d¹identité des bureaux d¹enregistrement lors d¹attaques d¹hameçonnage
by At-Large Staff Aug. 19, 2008

Aug. 19, 2008

Bonjour à tous, Nous aimerions vous inviter à une réunion d'information organisé par Dave Piscitello de la division Sécurité et Stabilité du Comité Consultatif (Security and Stability Advisory Committe (SSAC)) d'ICANN sur l l¹usurpation d¹identité des bureaux d¹enregistrement lors d¹attaques d¹hameçonnage (Registrar Impersonation in Phishing Attacks). La réunion sera le 26 août à 1300 UTC. La session sera enregistrée et il y aura une interprétation simultanée en français et en espagnol. Veuillez s¹il vous plait trouver ci-dessous la page de cette réunion avec les instructions de participation et le bulletin du SSAC sur le sujet. Vous y trouverez aussi un lien pour suivre la presentation sur Adobe Connect. https://st.icann.org/alac/index.cgi?registrar_impersonation_in_phishing_att acks Qu¹est-ce que c¹est l¹usurpation d¹identité des bureaux d¹enregistrement lors d¹attaques d¹hameçonnage ? Un pirate usurpe l¹identité d¹un bureau d¹enregistrement de noms de domaine et envoie à un client de ce bureau (un registrant) un message attendu ou prévisible au sujet d'un nom de domaine. Il peut s¹agir, par exemple, d¹un avis d¹expiration de l¹enregistrement d¹un nom de domaine, d¹un e-mail promotionnel, d¹un avis informant le registrant d¹un problème de gestion de son compte ou, plus généralement, de tout message qui requiert l¹attention immédiate d¹un client. Cependant, ce message est un faux : l¹hameçonneur crée un site Web frauduleux, similaire à celui du bureau d¹enregistrement, pour inciter le client à accéder à son compte de gestion du domaine concerné et à révéler involontairement ses informations d¹identification à l¹hameçonneur. Ce dernier utilise les informations d¹identification du client ainsi obtenues pour accéder au portefeuille de noms de domaine du client, modifier les informations DNS des noms de domaine de ce compte et utiliser les domaines pour lancer d¹autres attaques. Cordialement, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

26 August 1300 UTC: Briefing Session on Registrar Impersonation in Phishing Attacks
by At-Large Staff Aug. 19, 2008

Aug. 19, 2008

Dear all, We would like to invite you to a briefing attended by Dave Piscitello from the Security and Stability Advisory Committee (SSAC) on Registrar Impersonation in Phishing Attacks. The briefing will be on August 26th at 1300 UTC. The meeting will be recorded and there will be simultaneous interpretation in French and Spanish. Please find the SSAC Advisory on Registrar Impersonation and participation instructions on the meeting page. There is also a link to follow this presentation using Adobe Connect. https://st.icann.org/alac/index.cgi?registrar_impersonation_in_phishing_atta cks What is Registrar Impersonation in Phishing Attacks? The attacker impersonates a domain name registrar and sends an expected or anticipated correspondence to a registrar¹s customer (a registrant) regarding a domain name related matter. Examples of expected correspondence include a notice of pending expiration of a domain name registration, a promotional email, a notice informing the registrant of an account management issue, or generally, any correspondence that requires or encourages a customer¹s immediate attention. The correspondence, however, is bogus. The phisher creates a web site that is deceptively similar to the registrar¹s site to induce the customer into accessing his domain management account and unwittingly disclose his account credentials to the phisher. The phisher will use the customer¹s captured credentials to access the customer¹s domain name portfolio, alter DNS information of domain name(s) in that account and use the domains to abet additional attacks. Regards, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

August 2008 Policy Update Now Available
by At-Large Staff Aug. 19, 2008

Aug. 19, 2008

The ICANN Policy Update for August 2008 was published a few days ago it contains brief summaries of issues being addressed by the ICANN community's bottom-up policy development structure, as well as information on related policy development activities. The ICANN Policy Staff provides monthly updates in response to requests from the community for periodic summaries of ICANN's policy work. The goal of the Policy Update is to maximize transparency and encourage broad community participation in ICANN's policy development activities. The Spanish and French editions will be announced when the translations are completed. You may sign up to receive the update in English, French, or Spanish at http://www.icann.org/en/newsletter/ Contents 1. YOUR COMMENTS NEEDED ON POLICY ISSUES <http://www.icann.org/en/topics/policy/update-aug08.htm#1> 2. ICANN POLICY INFORMATION AT YOUR FINGERTIPS <http://www.icann.org/en/topics/policy/update-aug08.htm#2> 3. IMPROVING THE GNSO AND ASSIGNING COUNCIL SEATS <http://www.icann.org/en/topics/policy/update-aug08.htm#3> 4. WHOIS TO STUDY OR NOT TO STUDY? <http://www.icann.org/en/topics/policy/update-aug08.htm#4> 5. MAKING IT EASIER TO TRANSFER DOMAINS BETWEEN REGISTRARS <http://www.icann.org/en/topics/policy/update-aug08.htm#5> 6. HOW SHOULD WE DEAL WITH FAST FLUXING CYBERCRIMINALS? <http://www.icann.org/en/topics/policy/update-aug08.htm#6> 7. DOMAIN NAME FRONT RUNNING IF IT'S PREVALENT, WHAT SHOULD BE DONE ABOUT IT? <http://www.icann.org/en/topics/policy/update-aug08.htm#7> 8. INTERNATIONALIZNG COUNTRY CODE TOP LEVEL DOMAINS <http://www.icann.org/en/topics/policy/update-aug08.htm#8> 9. IS IT TIME TO RE-CONSIDER ICANN'S GEOGRAPHIC REGIONS? <http://www.icann.org/en/topics/policy/update-aug08.htm#9> 10. CCNSO WELCOMES .DZ, .AM <http://www.icann.org/en/topics/policy/update-aug08.htm#10> 11. CCNSO IMPROVEMENT PLAN UNDERWAY <http://www.icann.org/en/topics/policy/update-aug08.htm#11> 12. AT-LARGE INVOLVEMENT IN ICANN CONTINUES TO GROW <http://www.icann.org/en/topics/policy/update-aug08.htm#12> 13. AT-LARGE BRINGING AN INDIVIDUAL USER PERSPECTIVE TO POLICY DEVELOPMENT <http://www.icann.org/en/topics/policy/update-aug08.htm#13> 14. AT-LARGE ELECTIONS AND APPOINTMENTS <http://www.icann.org/en/topics/policy/update-aug08.htm#14> 15. NEW GLOBAL ASN POLICY TO BE IMPLEMENTED, FUTURE OF GLOBAL IPV4 POLICY UNCLEAR <http://www.icann.org/en/topics/policy/update-aug08.htm#15> 16. SSAC WORKING ON DNSSEC STATUS REPORT <http://www.icann.org/en/topics/policy/update-aug08.htm#16> 17. SSAC ANALYZES PHISHING <http://www.icann.org/en/topics/policy/update-aug08.htm#17> 18. SSAC REPORTS AND ADVISORIES AT A GLANCE <http://www.icann.org/en/topics/policy/update-aug08.htm#18> Links to additional information are included and readers are encouraged to go beyond these brief summaries to learn more about the ICANN community's work. As always, the Policy Staff welcomes comments and suggestions on how to improve its policy communications efforts. Please send these comments to policy-staff(a)icann.org. -- Regards, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0

20 August 1300 UTC: Discussion of At-Large Travel and the New Travel Procedure
by At-Large Staff Aug. 18, 2008

Aug. 18, 2008

Dear all, We would like to invite you to a discussion on the new travel policy for At-Large this Wednesday, 20 August at 1300 UTC. There has been quite a bit of discussion about the new Travel Procedures for Volunteers announced on 13th August ( http://www.icann.org/en/announcements/announcement-13aug08-en.htm) This procedure changes considerably the travel support for the community and for At-Large in particular. The call is to discuss the new approach and its impact on At-Large with Denise Michel, VP Policy Development, and Doug Brent, COO. There will be no interpretation for this call. Spanish and French speakers are encouraged to join the Adobe Connect channel for this meeting and submit their questions in the chat room. You can also use the comment button on the meeting page below to send your question in advance. Further details are available at: https://st.icann.org/alac/index.cgi?icann_travel_procedure_for_volunteers Please note that there will be a briefing session on the Draft RAA Amendments following this meeting at 1400 UTC. Regards, Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul ICANN At-Large Staff email: staff(a)atlarge.icann.org

1 0