- ALAC - lists.icann.org

Re: [ALAC] Nominating Committee ALAC Requirements Document
by Alan Greenberg Dec. 8, 2014

Dec. 8, 2014

Thanks. I was going to take out the reference to when the teleconference is but felt that keeping it may reduce the surprise level for new members. But on rethinking it, if the timing does change (and it already is not on Tuesday for some parts of the world), we have a worse situation, So I agree with you and will remove the reference to when the monthly call occurs. Alan At 08/12/2014 08:15 AM, Eduardo Diaz wrote: >Alan: > >My comments are included in the attached document. > >-ed > >On Mon, Dec 8, 2014 at 1:56 AM, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >The Nominating Committee has a document describing what the ALAC >does and the requirements and expectations for people applying for >LAC positions. This year the NomCom will be selecting ALAC Members >for Africa, Latin America / Caribbean Islands and Asia/Australia/Pacific). > >The document has not been revised since 2010, and I think it >important that we update it. I should have attended to this earlier, >but unfortunately the other issues we are working on seem to have >taken precedence. > >So we are now VERY late. Attached is the current version that has >been used 2010-2014 and one I have edited for use this coming year. > >I would appreciate all ALAC members (or past ALAC members) quickly >looking at this and letting me know what I have omitted or got wrong. > >In particular I would appreciate your experience regarding how many >hours per month we should realistically say is expected. We used to >have 20-26 and I changes that to the simpler 25. My rationale is: >- Monthly ALAC call: 2 >- e-mail: 30 minutes per day = 15 >- participation in various WG, drafting, webinars: 2 hours per week = 8 > >Even if you don't make any other changes, please comment on what >YOUR experience is regarding the number of weeks for a normal >(non-ALT, non-Liaison) ALAC Member. > >Sorry for the rush, but I need to get this sent in by mid-week, so >please don't put this off. > >Alan >_______________________________________________ >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… > > > > >-- >NOTICE: This email may contain information which is confidential >and/or subject to legal privilege, and is intended for the use of >the named addressee only. If you are not the intended recipient, you >must not use, disclose or copy any part of this email. If you have >received this email by mistake, please notify the sender and delete >this message immediately. >Content-Type: >application/vnd.openxmlformats-officedocument.wordprocessingml.document; > name="NomCom - ALAC Candidate Criteria-2015-v01- REV by ED.docx" >Content-Disposition: attachment; > filename="NomCom - ALAC Candidate Criteria-2015-v01- REV by ED.docx" >X-Attachment-Id: f_i3fv3diy2

2 1

Re: [ALAC] Drafting Team to fix ALAC ALS certification process
by Beran Gillen - Yahoo Dec. 7, 2014

Dec. 7, 2014

I second that nomination. Beran "There is nothing more difficult to arrange and more dangerous to carry through than initiating change..." Machiavelli Sent from my iPhone > On 6 Dec 2014, at 21:42, Tijani BEN JEMAA <tijani.benjemaa(a)planet.tn> wrote: > > Dear Alan, > > > > I nominate Fatimata Seye Sylla to be part of this drafting team. > > > > -------------------------------------------------------------------------------- > > Tijani BEN JEMAA > > Executive Director > > Mediterranean Federation of Internet Associations (FMAI) > > Phone: + 216 41 649 605 > > Mobile: + 216 98 330 114 > > Fax: + 216 70 853 376 > > -------------------------------------------------------------------------------- > > > > > > > > -----Message d'origine----- > De : alac-bounces(a)atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] De la part de Alan Greenberg > Envoyé : dimanche 30 novembre 2014 23:23 > À : ALAC > Objet : [ALAC] Drafting Team to fix ALAC ALS certification process > > > > As discussed on the ALAC call last week, I am calling for a few > > volunteers to form the ALS Certification Process Drafting team to > > revise the ALS certification process as documented in > > http://tinyurl.com/ALAC-RoP-AdjDoc4-2013-07, under the section > > "Certification process for At-Large Structures (ALS)", steps 3-6. > > > > Note that this is NOT the larger review of ALS criteria and > > expectations, but simply a process to ensure that our rules are > > practical, make sense, and are actually followed. > > > > Members need not be current ALAC Members or RALO leadership, but > > should be very familiar with the processes currently being followed. > > > > Please reply to this list, or directly to me copying Staff. > > > > Alan > > > > > > > > _______________________________________________ > > 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… > > > > > _____ > > > <http://www.avast.com/> Image supprimée par l'expéditeur. > > Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection Antivirus avast! <http://www.avast.com/> est active. > > > > > > --- > Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. > http://www.avast.com > _______________________________________________ > ALAC mailing list > ALAC(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/alac > > At-Large Online: http://www.atlarge.icann.org > ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…

1 0

Re: [ALAC] Drafting Team to fix ALAC ALS certification process
by Tijani BEN JEMAA Dec. 6, 2014

Dec. 6, 2014

Dear Alan, I nominate Fatimata Seye Sylla to be part of this drafting team. -------------------------------------------------------------------------------- Tijani BEN JEMAA Executive Director Mediterranean Federation of Internet Associations (FMAI) Phone: + 216 41 649 605 Mobile: + 216 98 330 114 Fax: + 216 70 853 376 -------------------------------------------------------------------------------- -----Message d'origine----- De : alac-bounces(a)atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] De la part de Alan Greenberg Envoyé : dimanche 30 novembre 2014 23:23 À : ALAC Objet : [ALAC] Drafting Team to fix ALAC ALS certification process As discussed on the ALAC call last week, I am calling for a few volunteers to form the ALS Certification Process Drafting team to revise the ALS certification process as documented in http://tinyurl.com/ALAC-RoP-AdjDoc4-2013-07, under the section "Certification process for At-Large Structures (ALS)", steps 3-6. Note that this is NOT the larger review of ALS criteria and expectations, but simply a process to ensure that our rules are practical, make sense, and are actually followed. Members need not be current ALAC Members or RALO leadership, but should be very familiar with the processes currently being followed. Please reply to this list, or directly to me copying Staff. Alan _______________________________________________ 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… _____ <http://www.avast.com/> Image supprimée par l'expéditeur. Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection Antivirus avast! <http://www.avast.com/> est active. --- Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. http://www.avast.com

1 0

Drafting Team to fix ALAC ALS certification process
by Alan Greenberg Dec. 3, 2014

Dec. 3, 2014

As discussed on the ALAC call last week, I am calling for a few volunteers to form the ALS Certification Process Drafting team to revise the ALS certification process as documented in http://tinyurl.com/ALAC-RoP-AdjDoc4-2013-07, under the section "Certification process for At-Large Structures (ALS)", steps 3-6. Note that this is NOT the larger review of ALS criteria and expectations, but simply a process to ensure that our rules are practical, make sense, and are actually followed. Members need not be current ALAC Members or RALO leadership, but should be very familiar with the processes currently being followed. Please reply to this list, or directly to me copying Staff. Alan

11 12

Many Webinars on IANA Stewardship Transition? Why? Which ones to attend?
by Olivier MJ Crepin-Leblond Dec. 3, 2014

Dec. 3, 2014

(apologies for cross posting) Dear all, you will have seen the announcements for various Webinars this week and next week on the IANA Stewardship Transition. There are many of them. Here is a short note to make sense of all of these Webinars: *Webinars of the CWG on Naming Related Functions Public Consultation on Draft Transition Proposal*: - 3 December from 7:00 – 8:30 UTC - 4 December from 12:30 – 14:00 UTC - 4 December from 16:00 – 17:30 UTC These Webinars are repeats of each other and are organised and Chaired by the Community Working Group (CWG) which is presenting a first draft of the Naming Communities input to the IANA Stewardship Transition process. This Webinar will be used to explain the contents of the First Draft of the Proposal. This will really help in understanding the draft which is currently under Public Comment from 1 to 22 December 2014. I highly recommend you attend at least one of them. Details on how to join are given in the message at the bottom of this email. ------ *Capacity Building Program Webinar #1:** **- Wednesday 3 December 2014 13:00 - 14:00 UTC** **IANA Functions (standards, Numbering and Naming) - Patrik Fältström* Are you interested in this topic but do not know where to start? This Webinar is for you! Indeed, this Webinar is a great introduction about all of the IANA Functions, introduced by the Chairman of the ICANN Security and Stability Advisory Committee. He is an expert! If you are interested in what is probably one of the key topics for the year and want to learn about it, then do not miss this Webinar! Tell people in your ALS! Tell anyone who is interested! Watch, listen, learn and ask questions - that's what this Webinar is about. The draft Agenda and call details are on: https://community.icann.org/x/2zrxAg *------ Capacity Building Program Webinar #2:** **- Wednesday 10 December 2014 21:00 - 22:30 UTC** **IANA Naming Issues by IANA Issues WG* This Webinar will have the members of the At-Large IANA Naming Issues working group explain the proposed ALAC response to the Public Comment period that has opened on 1 December and will close on 22 December 2014. This is your chance ask any questions about the proposed response and to comment on it too! However, we highly recommend that you attend the above capacity building Webinar before to better understand the issues and at least one of the three CWG Webinars above to learn about the CWG's First Draft. Call details for this Webinar will be sent out in due course. Reserve the time slot now! Kind regards, Olivier On 02/12/2014 08:05, ICANN At-Large Staff wrote: > > To view the original post, please > see: https://www.icann.org/news/announcement-3-2014-12-01-en > > > WEBINAR: Cross Community Working Group (CWG) On Naming Related > Functions Public Consultation on Draft Transition Proposal > > Following the request of the National Telecommunications and > Information Administration (NTIA) forICANN to "convene a > multistakeholder process to develop a plan to transition the U.S. > government stewardship role" with regard to the IANA Functions and > related root zone management, a Cross Community Working Group (CWG) > was tasked with developing a consolidated transition proposal for the > elements of the IANA Functions relating to the Domain Name System > (DNS). The CWG has now published its draft transition proposal > for public comment > <https://www.icann.org/public-comments/cwg-naming-transition-2014-12-01-en>. > Comments can be submitted until 22 December at 23:59 UTC. > > In order to brief the community on the contents on this draft > transition proposal and encourage community feedback, the CWG will be > organizing three identical webinars at different times to facilitate > participation across time zones. The webinars will take place on: > > * *3 December from 7:00 – 8:30 UTC *(time zone converter here > <http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) > * *4 December from 12:30 – 14:00 UTC *(time zone converter here > <http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) > * *4 December from 16:00 – 17:30 UTC *(time zone converter here > <http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) > > ------------------------------------------------------------------------ > > /Webinar Details & How to Attend/ > > The webinars will be run in an Adobe Connect room > <https://icann.adobeconnect.com/cwgiana/>. If you are interested in > attending the webinar and would like to receive dial-in details, > please send an email to grace.abuhamad(a)icann.org > <mailto:grace.abuhamad@icann.org> and indicate which day / time you > would like to attend the webinar. Please note that the webinar will be > conducted in English and will be recorded and transcribed. > Subsequently the transcripts will be translated in the 5 UN languages > and posted on the CWG Wiki here <https://community.icann.org/x/SIEHAw>. > > ------------------------------------------------------------------------ > > /The Draft Transition Proposal/ > > The CWG structured its draft transition proposal based on > the IANA Stewardship Transition Coordination Group (ICG) Request for > Proposals. These are: > > 1 Description of Community's Use of IANA Functions > 2A Existing, Pre-Transition Arrangements – Policy Sources > 2B Existing, Pre-Transition Arrangements – Oversight and > Accountability > 3 Proposed Post-Transition Oversight and Accountability Arrangements > 4 Transition Implications > 5 NTIA Requirements > 6 Community Process > > Sections 1, 2A and 2B describe the current situation. > > Section 3, which is the heart of the transition proposal, is still a > work in progress as not all details have been ironed out as of the > publication of this consultation. Although lacking some details, the > information provided in this section should be sufficiently detailed > to allow the communities to comment on all key components. In summary, > section 3 proposes the creation of 4 new entities to replace the > current NTIAarrangements. These are: > > 1. *Contract Co.* – This primary function of this entity (likely a > non-profit corporation) is to be signatory to the contract with > the IANA Functions Operator. This entity should be lightweight and > have little or no staff. > 2. *Multistakeholder Review Team (MRT)* – The MRT would be a > multi-stakeholder body with formally selected representatives from > all of the relevant communities (exact composition TBD). The > operation of the MRT would be based on the concept of maximum > public transparency. The responsibilities of the MRT will include: > * Developing the detailed contract terms for the agreement > between Contract Co. and theIANA Functions Operator, based on > the key contract terms proposed as part of this proposal and > set forth as Annex 3 > * Making key decisions for Contract Co. (e.g., whether or not to > enter into a rebidding (RFP) process for the operation of > the IANA Naming Functions) > * Conducting the IANA Functions Operator Budget Review > * Addressing any escalation issues raised by the Customer > Standing Committee (CSC) including the possibility of engaging > in enforcement > * Performing certain elements of administration (including > periodic performance reviews) currently set forth in > the IANA Functions Contract and currently being carried out by > theNTIA > * Managing a re-contracting or rebidding (RFP) process for the > operation of the IANAFunctions, both as an enforcement option > and as part of a regular rebidding procedure > The CWG is in the process of discussing whether there is an > additional enforcement role for the MRT related to policy > implementation by the IANA Functions Operator; specifically, > whether the MRT should be able to commence a proceeding before the > Independent Appeals Panel. > 3. *Customer Standing Committee (CSC)* – While the exact composition > is still to be determined, the CSC would primarily be made up of a > number of representatives of registry operators, > including ccTLD and gTLD registries. Input from the CSC would feed > into and inform the work of the MRT. It is possible that the CSC > would also include additional individuals with relevant expertise > and/or liaisons (or representatives) from other SO/ACs. The CSC > would: > * Work with the MRT to establish Service Levels and Performance > Indicators for the performance of the IANA Naming Functions > * Receive reports from the IANA Functions Operator including > regular performance reports. > * Review these reports against established service levels and > escalate any significant issues to the MRT > 4. *Independent Appeals Panel (IAP)* – The CWG recommends that > all IANA actions which affect the Root Zone or Root > Zone WHOIS database be subject to an independent and binding > appeals panel. The Appeals Mechanism should also cover any policy > implementation actions that affect the execution of changes to > the Root Zone File or Root Zone WHOIS and how relevant policies > are applied. This need not be a permanent body, but rather could > be handled the same way as commercial disputes are often resolved, > through the use of a binding arbitration process using an > independent arbitration organization (e.g., ICDR, ICC, AAA) or a > standing list of qualified people under rules promulgated by such > an organization. > > Sections 4, 5 and 6 are currently in development and are directly > dependent on the final choices that will be made for section 3. > > For further details, you are encouraged the review the draft > transition proposal in its entirety, availablehere > <https://community.icann.org/x/SoEHAw>. > > ------------------------------------------------------------------------ > > /Further information/ > > For further information about the CWG's work, please > see https://community.icann.org/x/37fhAg. > > For further information about the ICG and the IANA Stewardship > Transition, please seehttps://www.icann.org/stewardship. > > > > _______________________________________________ > 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

1 0

Re: [ALAC] Drafting Team to fix ALAC ALS certification process
by Alan Greenberg Dec. 2, 2014

Dec. 2, 2014

Noted. Thanks. Alan At 02/12/2014 05:01 PM, Fatimata Seye Sylla wrote: >I will be happy to participate. >Fatimata >On Dec 1, 2014 1:51 AM, "Alan Greenberg" ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >As discussed on the ALAC call last week, I am calling for a few >volunteers to form the ALS Certification Process Drafting team to >revise the ALS certification process as documented in ><http://tinyurl.com/ALAC-RoP-AdjDoc4-2013-07>http://tinyurl.com/ALAC-RoP-AdjDoc4-2013-07, >under the section "Certification process for At-Large Structures >(ALS)", steps 3-6. > >Note that this is NOT the larger review of ALS criteria and >expectations, but simply a process to ensure that our rules are >practical, make sense, and are actually followed. > >Members need not be current ALAC Members or RALO leadership, but >should be very familiar with the processes currently being followed. > >Please reply to this list, or directly to me copying Staff. > >Alan > > >_______________________________________________ >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

Call for Members and Participants in the ALAC Finance and Budget Subcommittee
by Alan Greenberg Dec. 2, 2014

Dec. 2, 2014

As discussed on the ALAC call last week, I am calling for volunteers for the ALAC Finance and Budget Subcommittee (FBSC) There will be two Members per region: - One ALAC member to be selected by the region's ALAC members. - One Member representing the RALO. This will normally be a RALO Chair, Vice-Chair (if the region has such an officer defined) or Secretariat. A RALO may choose someone else to be their official representative, as long as that person is both involved in the selection and preparation of that regions's budget requests, and is empowered to act on behalf of the region on the FBSC. Additional Participants are welcome. It is expected that the FBSC will be meeting in the 2nd week of December, so appointment should be made as soon as possible. The current CROPP RT which is composed partly of members of the current FBSC will continue to act on behalf of the ALAC until such time that it is formally reconstituted. Please send the names of those who are selected to sit on the FBSC to staff(a)atlarge.icann.org. Alan

4 4

Fwd: ICANN Finalizes Process for Requests for Release of Two-Character ASCII Labels
by Carlton Samuels Dec. 2, 2014

Dec. 2, 2014

FYI ============================== Carlton A Samuels Mobile: 876-818-1799 *Strategy, Planning, Governance, Assessment & Turnaround* ============================= [image: ICANN] <http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2014-12-01-en ------------------------------ ICANN Finalizes Process for Requests for Release of Two-Character ASCII Labels 1 December 2014 As previously announced, ICANN has been working towards developing a process to permit registries to request the release of two-character ASCII labels at the second-level for registration to 3rd parties and activation in the DNS pursuant to Section 2 of Specification 5. That process is now final and available. For all *digit/digit, letter/digit and digit/letter two-character ASCII labels*, because this category has been determined not to raise significant security, stability or competition concerns and has received no objections from governments, country code top-level domain managers, and members of the technical community or rights holders, ICANN has authorized their release for all registries: - Authorization for the Release of All Digit/Digit, Letter/Digit and Digit/Letter Two-Character ASCII Labels at the Second-Level Authorization <https://www.icann.org/en/system/files/files/spec5-amend-two-char-01dec14-en…> [PDF, 142 KB] Accordingly, registries are not required to submit any individual request for release of any digit/digit, letter/digit or digit/letter two-character ASCII label, and may immediately make such labels available for third party registration and activation in the DNS. Registries seeking to release *letter/letter two-character ASCII labels* at the second-level will continue to follow a transparent process as recommended by the Government Advisory Committee (GAC). 1. Registry operator submits a request to ICANN to release one or more letter/letter two-character ASCII label(s). 2. ICANN reviews the request and posts it for comment for 30 days. 3. ICANN notifies the GAC of the request and the comment period. 4. If there are no relevant and reasoned objections to the request, ICANN will approve the letter/letter ASCII label(s) request within 7-10 calendar days of the close of the 30-day public posting period. In accordance to Section 6 of Specification 5 of the Registry Agreement, a list of reserved names for this section are still subject to the reservation requirements and will not be available for release at this time. To learn more about the Authorization Process for Release of Two-Character ASCII Labels at the second level, and to obtain the form for "Request for Release of Letter/Letter Two-Character ASCII Labels at the Second Level," please click here <https://www.icann.org/resources/two-character-labels>. ICANN will communicate in writing its approval of any such request, if and to the extent appropriate. ICANN's Registry Services and Engagement team looks forward to implementing these processes to allow registries and their registrants access to two-character SLDs, and thanks the community for its input. # # # Media Contact *Gwen Carlson* Director, GDD Communications Los Angeles, CA *Tel:* +1 310 578 8653 *Email:* gwen.carlson(a)icann.org About ICANN *ICANN's mission is to ensure a stable, secure and unified global Internet. To reach another person on the Internet you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN coordinates these unique identifiers across the world. Without that coordination we wouldn't have one global Internet. ICANN was formed in 1998. It is a not-for-profit public-benefit corporation with participants from all over the world dedicated to keeping the Internet secure, stable and interoperable. It promotes competition and develops policy on the Internet's unique identifiers. ICANN doesn't control content on the Internet. It cannot stop spam and it doesn't deal with access to the Internet. But through its coordination role of the Internet's naming system, it does have an important impact on the expansion and evolution of the Internet. For more information please visit:* *www.icann.org* <https://www.icann.org/>

1 0

Re: [ALAC] Call for Members and Participants in the ALAC Finance and Budget Subcommittee
by Alan Greenberg Dec. 1, 2014

Dec. 1, 2014

Eduardo and Glenn. I indicated on the ALAC Call that it was my intent to Chair the FBSC but not be the ALAC Member from NA. That leaves the two of you. Please decide who will be playing that wole and let me and Staff know. Regards, Alan At 30/11/2014 09:11 PM, Alan Greenberg wrote: >As discussed on the ALAC call last week, I am calling for volunteers >for the ALAC Finance and Budget Subcommittee (FBSC) > >There will be two Members per region: >- One ALAC member to be selected by the region's ALAC members. >- One Member representing the RALO. This will normally be a RALO >Chair, Vice-Chair (if the region has such an officer defined) or >Secretariat. A RALO may choose someone else to be their official >representative, as long as that person is both involved in the >selection and preparation of that regions's budget requests, and is >empowered to act on behalf of the region on the FBSC. > >Additional Participants are >welcome. > > >It is expected that the FBSC will be meeting in the 2nd week of >December, so appointment should be made as soon as possible. > >The current CROPP RT which is composed partly of members of the >current FBSC will continue to act on behalf of the ALAC until such >time that it is formally reconstituted. > >Please send the names of those who are selected to sit on the FBSC >to staff(a)atlarge.icann.org. > >Alan

1 0

Re: [ALAC] [ALAC-Announce] CALL FOR COMMENTS: ICANN Draft Five-Year Operating Plan (Version 1 FY2016-FY2020)
by Olivier MJ Crepin-Leblond Nov. 26, 2014

Nov. 26, 2014

Dear All, further to the call for volunteers below and to the discussion on the ALAC call earlier this week, please be so kind to find a link to a recent Webinar by ICANN Finance which will help you read through the ICANN Draft Five-Year Operating Plan: https://icann.adobeconnect.com/p92ip2vdq8e/ Also - please find attached, the Powerpoint Presentation used during that session. Kind regards, Olivier On 21/11/2014 16:15, ICANN At-Large Staff wrote: > Dear All, > > Alan Greenberg, Chair of the ALAC, has asked that a call for comments > be made on the ICANN Draft Five-Year Operating Plan (Version 1 > FY2016-FY2020) <https://community.icann.org/x/izTxAg>. > > Please submit any comments on the At-Large ICANN Draft Five-Year > Operating Plan Workspace <https://community.icann.org/x/izTxAg> using > the comments function. > > Regards, > > Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie > Peregrine and Terri Agnew > ICANN Policy Staff in support of ALAC > E-mail: staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> > Facebook: www.facebook.com/icann.atlarge > <https://www.facebook.com/icann.atlarge> > Twitter: @ICANN_AtLarge <https://twitter.com/ICANN_AtLarge> > > > > _______________________________________________ > 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

1 1