March 2013 - EURO-Discuss - lists.icann.org

Re: [EURO-Discuss] IMPORTANT FY14 AC Budget Request Information and Deadlines
by Olivier MJ Crepin-Leblond March 14, 2013

March 14, 2013

Dear All, I am following-up on the message below to remind you of the deadline for FY14 requests from RALOs which is Monday 18 March 2013. When completing your templates, please remember to include deliverables and the rationale why ICANN should fund the activity. (and please make sure you show how the proposal ties up with the ICANN strategy) General Assemblies (GAs) As you know, the ALAC is going to submit a proposal for a second At-Large Summit (ATLAS2) to take place in FY14. The At-Large Summit would include a General Assembly for each of the RALOs. At this point in time, it is therefore redundant for RALOs to ask for a General Assembly this Financial Year. Internet Governance Forum (IGF) workshops Requests for workshops at the IGF will be dependent on the workshops being accepted by the MAG/IGF so make sure that you submit the requests for workshops in time for the IGF schedule, which shows a deadline for the preliminary call for workshop proposals on 22 March 2013. ExCom meeting Due to the shortening of the ICANN meeting week with the Board meeting now on Thursday, the ALAC will be submitting a request to support the ExCom and Liaisons for an extra night at the end of the ICANN Meetings in FY14 (Friday night) so that they may discuss follow-up items and plan strategy for the time between meetings, as it has customarily done on Friday afternoons when the Board meeting was on Friday morning. Finally, the At-Large Finance & Budget Sub-Committee will be holding a call to review *all* requests (and not only the Fast Track ones) on 20 March 2013. Kind regards, Olivier MJ Crépin-Leblond Chair of the FBSC On 07/03/2013 16:53, ICANN At-Large Staff wrote: > > Dear All, > > > > As requested on the Finance and Budget Sub-Committee (FBSC)/RALO > Leaders Call of Thursday, 28 February, please find the links to the > key documents for the FY14 AC/SO budget request process: > > > > · *At Large - FY14 Special Budget Request > <https://community.icann.org/display/projfinadhocws/At+Large+-+FY14+Special+…> > - Finance Department's Workspace for At-Large (includes FY14 AC budget > request template)* > > · *At-Large FY14 Budget Development Workspace > <https://community.icann.org/display/atlarge/At-Large+FY14+Budget+Developmen…>* > > · *FY14 SO-AC-SG Budget Processv1.xlsx > <https://community.icann.org/download/attachments/40174679/FY14+SO-AC-SG+Bud…>* > > · *FY14 Budget Process - Community Call - 17 Jan.pdf > <https://community.icann.org/download/attachments/40174679/FY14+Budget+Proce…>* > > · *FY14 Special Budget Request Guidelines.docx > <https://community.icann.org/download/attachments/40174679/FY14+Special+Budg…>* > > · *Template - SO-AC-SG FY14 Budget Request.docx > <https://community.icann.org/download/attachments/40174679/Template+-+SO-AC-…>* > > · *Community Additional Budget Request Criteria Matrix.xlsx > <https://community.icann.org/download/attachments/40174679/Community+Additio…>* > > > > *Instructions for submitting AC FY14 requests: * > > 1. Send your completed At-Large FY14 AC budget request template > to Olivier Crepin-Leblond (ocl(a)gih.com <mailto:ocl@gih.com>) and > At-Large staff ( staff(a)atlarge.icann.org > <mailto:staff@atlarge.icann.org>) *by 18 March 2013.* > > *2. *At-Large staff will post the completed At-Large FY14 AC > budget request templates to the *At-Large FY14 Budget Development > Workspace > <https://community.icann.org/display/atlarge/At-Large+FY14+Budget+Developmen…>* > > 3. The FBSC will review the completed At-Large FY14 AC budget > request templates during a call on 20 March 2013. > > 4. The FBSC will direct staff to submit the At-Large FY14 AC > budget requests for review by the ICANN Controller. > > 5. ICANN finance staff will confirm and validate your submission > by reviewing and posting your request in the dedicated wiki workspace > within 48 hours of its submission > > * * > > *Deadlines for the of FY14 budget request templates:* > > > > * *Deadline for RALOs to submit all FY14 AC requests to Olivier and > At-Large staff => 18 March 2013* > * *Early vote/decision by April => At-Large to submit to ICANN > Controller by 22 March 2013 **(please note that the early > vote/decision process is for budget requests with activities in > the first month of FY 14 (i.e., July 2013)* > * *Vote/decision by June => At-Large submit to ICANN Controller by > 29 April 2013* > > > > Please let At-Large staff know if you have any questions related to > the FY14 AC Budget Request process. > > > > Regards, > > Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie > Peregrine, and Julia Charvolen > > ICANN Policy Staff in support of the ALAC > > E-mail: staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> > > > > > > >

1 0

Re: [EURO-Discuss] [ALAC] Draft ALAC Rules of Procedure & Upcoming Teleconference Review Meeting
by Wolf Ludwig March 12, 2013

March 12, 2013

Hello, as raised already on the EURALO list by my mail from 21 Feb 2013 (without any feedback so far), EURALO supports the idea of having a full and inclusive At-Large community discussion on the Electorate – as sort of a continuation of our best practice from autumn 2010 to allow the RALO Chair (as part of the electorate) a guided or directed vote based on the (majority) will of his/her community. This means, there is one RALO at least supporting Avri’s demarche. BTW, I couldn't leave this comment on your blog on At-Large suffrage mentioned below, Avri. Best, Wolf Avri Doria wrote Tue, 12 Mar 2013 07:53: >Hi, > >Thank you very much for this invitation. > >It reads, however, like this is a done deal and that no discussion is to be expected because people worked hard to bring this before the ALAC. As someone who observed much of the work waiting for the right opportunity to bring up an issue, I agree they worked long and hard, even if it did seem to be somewhat an insular process that was not completely open. > >As many of you know I have been requesting consideration of Clause 18.10, the electorate for Seat 15 on the Board, ever since the last selection; a selection whose process was never, to my knowledge, reviewed post-selection. While I understand that a discussion is planned on At-Large suffrage (the definition of voting rights) at the Beijing meeting, am I to understand that discussion of this issue is still out of scope at this point in the approval of these procedures? If so, I would like to point out that as someone who followed the entire process waiting for the time when this would be discussed by ROP or its sub-teams, it never did get a fair share of that work time, and was always pushed off with 'this is not the time' or 'well it is too late we are just about done now'. > >Yet I did receive the guarantee at the end of the process that this would be subjected to community discussion before the next vote for Seat 15. And I understand that this guarantee was sent on to the ALAC. I asked for the language in 18.10 to be bracketed until such a discussion was held and was refused with a certain amount of derision about this not being the ITU - though perhaps there are some things that can be learned from the ITU and the ability to bracket controversial language. I ask again that this language be bracketed until such time as a full community discussion on At-Large suffrage can be held. > >As an ALS member, who is active in At-Large activities, I would like to understand the timeline and the process that will be used for a complete At-Large discussion, which includes the ALSes and their members, before the next vote so that we do not find ourselves 'too late' yet again when it comes time for this (s)election. > >I have written a blog on At-Large suffrage that can be found at: >https://community.icann.org/display/~avri.doria/At-Large+suffrage*+request+… > >Thank you, > >Avri Doria > > >On 12 Mar 2013, at 01:00, Heidi Ullrich wrote: > >> On behalf of Olivier Crepin-Leblond, Chair of the ALAC, and Cheryl Langdon-Orr, Chair of the At-Large Rules of Procedure Working Group, please see the important note below regarding an upcoming ALAC Meeting to review the revised ALAC Rules of Procedure (RoPs): >> >> ** >> >> Dear All, >> >> As per a previous discussion and agreement of the ALAC on 22 January 2013, the ALAC will be holding a single purpose teleconference call to discuss the proposed version of their NEW Rules of Procedure (RoPs) before a Call to Vote to Ratify and Adopt these (or not) which is to be conducted online and prior to the 46th ICANN Meeting to be held in Beijing 7-11 April 2013. >> >> This special meeting of the ALAC, which is open to all members of the At-Large Community, especially RALO Leadership and ALS members, is now announced. This call will be held on Tuesday, 19 March 2013 at 2100 UTC (2100 UTC =1400 PDT, 1700 EDT, 2200 CET, 5am Hong Kong (+1 Day) and 8am Sydney (+1 Day). The Wiki page for this meeting is found at https://community.icann.org/x/WpVwAg. >> >> FR and ES interpretation has been confirmed for this meeting. >> >> All Members of the ALAC and members of the At-Large Community are requested to RSVP their attendance at this call to At-Large Staff (staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>) indicating if they will be joining one of the interpreted channels. >> >> The 15 Members of the ALAC are encouraged to place any comments they have in the COMMENTS section of the meeting page (see: https://community.icann.org/x/WpVwAg) or e-mail to the ALAC Working List ( alac(a)atlarge-lists.icann.org<mailto:alac@atlarge-lists.icann.org>), particularly if they will not be able to attend this meeting. >> >> Members of the At-Large Community who wish to have any input or comments on these proposed new RoPs considered at this meeting should send these contributions to one of the ALAC Members from their Region or via email to the Chair of the Rules of Procedure Working Group, Cheryl Langdon-Orr (langdonorr(a)gmail.com<mailto:langdonorr@gmail.com>). >> >> >> Background on these proposed new ALAC RoPs and opportunity for final ALAC review: >> >> This final version of the new ALAC RoP (see: https://community.icann.org/x/VoYi and attached) is the product of an extensive process carried out by some 33 members of the At-Large Community (ALAC Members, formal Regional representatives as well as individual ALS and RALO members of the At-Large Community who volunteered to the ALAC Metrics and RoP Review WG(s). >> >> These volunteers have, in face-to-face and teleconference meetings of the Working Group (WG) as a whole and of the new Rules section Drafting Teams (DTs), committed well over 500 person-hours in review of the current RoPs and support material including previous versions, discussion of all rules merits, and in drafting of and editing this new Rules proposed text. A summary of who participated in the various RoP meetings can be found at: https://community.icann.org/x/SgoQAg. >> >> In addition, and unfortunately difficult to measure and capture, is an extraordinary amount of time spent by the WG's Drafting Teams (DTs) leadership and section pen-holders (noting each DT was in itself, like the RoP Review WG as a whole, a deliberately regionally balanced group) and even more hours and effort again contributed by several current and previously serving ALAC Members during the final stages of integration and editing of the version you are presented with here. >> >> The majority of the ALAC has been directly involved with the Rules of Procedure WG and DTs' activities and in several cases served as Leads and/or Pen-Holders for the discussion and drafting, and therefore it is unexpected and doubtful that any significant or substantial omissions or edits will be proposed for discussion either at or before the conference call. Also it is recognised that the ALAC has at its regular meetings been continually appraised of the progress of this Rules Review and also that all business of the Review WG/DTs has been done in an open and transparent manner with archives and records being held and publicly available on the relevant ALAC wiki pages. >> >> It must also be noted by the ALAC as a whole and by the wider At-Large Community in general, that virtually every concept and issue relating to these proposed new ALAC RoPs was discussed extensively, prior to any drafting, and often reviewed line by line, mostly over several visits / revisits at several meetings. Anything that was even slightly controversial or where people had differing views was debated and in virtually all cases, what has ended up in these Rules has a strong consensus of those working on the original drafting team and the final reviewers. >> >> It is also important to note that several of the 'Adjunct Documents' referred to in these new Rules are not as yet completely finalised nor have they been reviewed (as such) by the ALAC. However, they are all to be drawn from existing ALAC policy and practices and will be shortly available. The vote for the adoption of these new ALAC RoPs does not need to be delayed until they are prepared and circulated, but rather the new RoPs will not come into effect until those Adjunct Documents are all approved by the ALAC. >> >> Specific details on the ALAC vote plans and procedures relating to these new ALAC Rules will be discussed during this special ALAC meeting on 19 March 2013, but it is our hope that the vote can commence shortly after the ALAC monthly call on 26 March 2013. >> >> Regards, >> Cheryl Langdon-Orr and Olivier Crepin-Leblond >> 11 March 2013 >> >> ** >> >> Kind Regards, >> Heidi >> >> >> Heidi Ullrich >> Director for At-Large >> Internet Corporation for Assigned Names and Numbers (ICANN) >> Telephone: + 1 (310) 578 - 8647 >> Fax: +1 (310) 823 - 8649 >> Cell/Mobile: +1 (310) 437 - 3956 >> >> <DRAFT-RoP-v64.pdf>_______________________________________________ >> 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… > EuroDIG Secretariat http://www.eurodig.org/ mobile +41 79 204 83 87 Skype: Wolf-Ludwig EURALO - ICANN's Regional At-Large Organisation http://euralo.org Profile on LinkedIn http://ch.linkedin.com/in/wolfludwig

1 0

Draft ALAC Rules of Procedure & Upcoming Teleconference Review Meeting
by Heidi Ullrich March 12, 2013

March 12, 2013

On behalf of Olivier Crepin-Leblond, Chair of the ALAC, and Cheryl Langdon-Orr, Chair of the At-Large Rules of Procedure Working Group, please see the important note below regarding an upcoming ALAC Meeting to review the revised ALAC Rules of Procedure (RoPs): ** Dear All, As per a previous discussion and agreement of the ALAC on 22 January 2013, the ALAC will be holding a single purpose teleconference call to discuss the proposed version of their NEW Rules of Procedure (RoPs) before a Call to Vote to Ratify and Adopt these (or not) which is to be conducted online and prior to the 46th ICANN Meeting to be held in Beijing 7-11 April 2013. This special meeting of the ALAC, which is open to all members of the At-Large Community, especially RALO Leadership and ALS members, is now announced. This call will be held on Tuesday, 19 March 2013 at 2100 UTC (2100 UTC =1400 PDT, 1700 EDT, 2200 CET, 5am Hong Kong (+1 Day) and 8am Sydney (+1 Day). The Wiki page for this meeting is found at https://community.icann.org/x/WpVwAg. FR and ES interpretation has been confirmed for this meeting. All Members of the ALAC and members of the At-Large Community are requested to RSVP their attendance at this call to At-Large Staff (staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>) indicating if they will be joining one of the interpreted channels. The 15 Members of the ALAC are encouraged to place any comments they have in the COMMENTS section of the meeting page (see: https://community.icann.org/x/WpVwAg) or e-mail to the ALAC Working List ( alac(a)atlarge-lists.icann.org<mailto:alac@atlarge-lists.icann.org>), particularly if they will not be able to attend this meeting. Members of the At-Large Community who wish to have any input or comments on these proposed new RoPs considered at this meeting should send these contributions to one of the ALAC Members from their Region or via email to the Chair of the Rules of Procedure Working Group, Cheryl Langdon-Orr (langdonorr(a)gmail.com<mailto:langdonorr@gmail.com>). Background on these proposed new ALAC RoPs and opportunity for final ALAC review: This final version of the new ALAC RoP (see: https://community.icann.org/x/VoYi and attached) is the product of an extensive process carried out by some 33 members of the At-Large Community (ALAC Members, formal Regional representatives as well as individual ALS and RALO members of the At-Large Community who volunteered to the ALAC Metrics and RoP Review WG(s). These volunteers have, in face-to-face and teleconference meetings of the Working Group (WG) as a whole and of the new Rules section Drafting Teams (DTs), committed well over 500 person-hours in review of the current RoPs and support material including previous versions, discussion of all rules merits, and in drafting of and editing this new Rules proposed text. A summary of who participated in the various RoP meetings can be found at: https://community.icann.org/x/SgoQAg. In addition, and unfortunately difficult to measure and capture, is an extraordinary amount of time spent by the WG's Drafting Teams (DTs) leadership and section pen-holders (noting each DT was in itself, like the RoP Review WG as a whole, a deliberately regionally balanced group) and even more hours and effort again contributed by several current and previously serving ALAC Members during the final stages of integration and editing of the version you are presented with here. The majority of the ALAC has been directly involved with the Rules of Procedure WG and DTs' activities and in several cases served as Leads and/or Pen-Holders for the discussion and drafting, and therefore it is unexpected and doubtful that any significant or substantial omissions or edits will be proposed for discussion either at or before the conference call. Also it is recognised that the ALAC has at its regular meetings been continually appraised of the progress of this Rules Review and also that all business of the Review WG/DTs has been done in an open and transparent manner with archives and records being held and publicly available on the relevant ALAC wiki pages. It must also be noted by the ALAC as a whole and by the wider At-Large Community in general, that virtually every concept and issue relating to these proposed new ALAC RoPs was discussed extensively, prior to any drafting, and often reviewed line by line, mostly over several visits / revisits at several meetings. Anything that was even slightly controversial or where people had differing views was debated and in virtually all cases, what has ended up in these Rules has a strong consensus of those working on the original drafting team and the final reviewers. It is also important to note that several of the 'Adjunct Documents' referred to in these new Rules are not as yet completely finalised nor have they been reviewed (as such) by the ALAC. However, they are all to be drawn from existing ALAC policy and practices and will be shortly available. The vote for the adoption of these new ALAC RoPs does not need to be delayed until they are prepared and circulated, but rather the new RoPs will not come into effect until those Adjunct Documents are all approved by the ALAC. Specific details on the ALAC vote plans and procedures relating to these new ALAC Rules will be discussed during this special ALAC meeting on 19 March 2013, but it is our hope that the vote can commence shortly after the ALAC monthly call on 26 March 2013. Regards, Cheryl Langdon-Orr and Olivier Crepin-Leblond 11 March 2013 ** Kind Regards, Heidi Heidi Ullrich Director for At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: + 1 (310) 578 - 8647 Fax: +1 (310) 823 - 8649 Cell/Mobile: +1 (310) 437 - 3956

1 0

Material for review by the ALAC regarding objection statements to 4 new gTLD applications
by Dev Anand Teelucksingh March 9, 2013

March 9, 2013

Dear All, Here is a summary of the information available for review by the ALAC regarding the RALO advice on the objection statements on community grounds to 4 new gTLD applications. Many of this information were linked on the Friday March 8 2013 ALAC's call (https://community.icann.org/x/8JNwAg) but are repeated here for reference. All of the wiki pages with the objection statements against : - applicant "DotHealth, LLC" for the ".HEALTH" string (https://community.icann.org/x/t4xwAg) - applicant "Goose Fest, LLC" for the ".HEALTH" string (https://community.icann.org/x/v4xwAg) - applicant "dot Health Limited" for the ".HEALTH" string (https://community.icann.org/x/xYxwAg) - applicant "Afilias Limited" for the ".HEALTH" string (https://community.icann.org/x/y4xwAg) have been updated with - links to applicants' Public Interest Commitments (PICs) - correspondence received by the gTLD Review Group over the past 48 hours, including * letters from individual applicants, * letters of support for objections from organisations and emails from the WHO clarifying issues raised on the NARALO list. With many of the correspondence received (even today), directed at the objection statement against Stable Tone Limited" for the "健康" string, the wiki page at https://community.icann.org/x/0YxwAg was also updated, for reference, even though this is no longer under ALAC's consideration, as per RALO advice. Also, there was discussion by the RALOs on the applicants and the objection statements and can be reviewed on the RALO mailing list archives: NARALO: http://atlarge-lists.icann.org/pipermail/na-discuss/2013-March/thread.html APRALO: http://atlarge-lists.icann.org/pipermail/apac-discuss/2013/thread.html LACRALO: https://community.icann.org/x/Q5FwAg (wiki page) gTLD Review Group List archives : http://mm.icann.org/pipermail/newgtldrg/ (for reference, but again all correspondence regarding the applications and objection statements have been posted on the individual wiki pages) Also, the objection statements are on community objection grounds. The community objection grounds page at https://community.icann.org/x/QgkQAg lists the 4 tests as specified in the Applicant GuideBook that the objection statement must meet for the objection to prevail. Also for useful reading on community objection grounds: Circle ID article: "Thinking Carefully About New gTLD Objections: Community (3 of 4)" http://www.circleid.com/posts/20130219_thinking_carefully_about_new_gtld_ob… Independent Objector's (IO) comments on controversial applications: http://www.independent-objector-newgtlds.org/english-version/the-independen… The IO comments shows the reasoning behind his decisions as to whether to file objections on community or limited public interest concerns. Kind Regards, Dev Anand Teelucksingh gTLD RG chair

1 0

CALL FOR COMMENTS: At-Large Beijing Communications Department Questions
by ICANN At-Large Staff March 8, 2013

March 8, 2013

Dear All, The At-Large Beijing Communications Department Questions Workspace<https://community.icann.org/x/e4U3Ag> has been created. Please note that this workspace will be used to gather the At-Large's questions for the Communications Department during the Beijing Meeting. Please submit any comments on the workspace using the comments function by 15 Mar at 23:59 UTC. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

1 0

CALL FOR COMMENTS: At-Large Beijing Global Stakeholder Engagement Questions
by ICANN At-Large Staff March 8, 2013

March 8, 2013

Dear All, The At-Large Beijing Global Stakeholder Engagement Questions Workspace<https://community.icann.org/x/eYU3Ag> has been created. Please note that this workspace will be used to gather the At-Large's questions for the Global Partnerships Department during the Beijing Meeting. Please submit any comments on the workspace using the comments function by 15 Mar at 23:59 UTC. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

1 0

CALL FOR COMMENTS: At-Large Beijing ICANN Board Questions
by ICANN At-Large Staff March 8, 2013

March 8, 2013

Dear All, The At-Large Beijing ICANN Board Questions Workspace<https://community.icann.org/x/d4U3Ag> has been created. Please note that this workspace will be used to gather the At-Large's questions for the ICANN Board during the Beijing Meeting. Please submit any comments on the workspace using the comments function by 15 Mar at 23:59 UTC. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

1 0

CALL FOR COMMENTS: At-Large Beijing GAC Questions
by ICANN At-Large Staff March 8, 2013

March 8, 2013

Dear All, The At-Large Beijing GAC Questions Workspace<https://community.icann.org/x/doU3Ag> has been created. Please note that this workspace will be used to gather the At-Large's questions for the GAC during the Beijing Meeting. Please submit any comments on the workspace using the comments function by 15 Mar at 23:59 UTC. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

1 0

Summary of RALO advice to the ALAC regarding the 5 objection statements to new gTLD applications
by Dev Anand Teelucksingh March 7, 2013

March 7, 2013

Dear All, As per the process by which the ALAC can object to a new gTLD application, (see one page PDF at http://bit.ly/how-ALAC-files-objection-to-new-gTLD ), RALOs have submitted advice to the ALAC on the objection statements on community grounds to 5 new gTLD applications. These objection statements were prepared by the gTLD Review Group (gTLD RG) based on the outcomes of its review and discussion of comments received by February 8, 2013 (see http://atlarge-lists.icann.org/pipermail/at-large/2013q1/009493.html) The 5 applications and objection statements, including the comments received by the gTLD RG on the applications can be found on the workspace at https://community.icann.org/x/soxwAg with 5 separate wiki pages for each new gTLD application, the objection statement and the comments received by the gTLD RG. The RALO's advice to the ALAC were in the form of answers to the 5 questions listed at https://community.icann.org/x/t45wAg with the possible answers of either * Yes, support the filing of the objection statement by the ALAC against applicant, * No, NOT support the filing of the objection statement by the ALAC against applicant OR * Abstain Objection statements NOT supported by at least three RALOs will not be considered by the ALAC. For those objection statements that are supported by three or more RALOs, the ALAC will decide whether to file such objection statements to the Dispute Resolution Service Provider (DRSP) before the end of the objection period on March 13, 2013. Summary of RALO advice: 3 out of 5 RALOs supported the filing of the objection statement by the ALAC against applicant "DotHealth, LLC" for the ".HEALTH" string (https://community.icann.org/x/t4xwAg) 3 out of 5 RALOs supported the filing of the objection statement by the ALAC against applicant "“Goose Fest, LLC" for the ".HEALTH" string (https://community.icann.org/x/v4xwAg) 3 out of 5 RALOs supported the filing of the objection statement by the ALAC against applicant "dot Health Limited" for the ".HEALTH" string (https://community.icann.org/x/xYxwAg) 3 out of 5 RALOs supported the filing of the objection statement by the ALAC against applicant "Afilias Limited" for the ".HEALTH" string ( https://community.icann.org/x/y4xwAg ) 1 out of 5 RALOs supported the filing of the objection statement by the ALAC support the filing of the objection statement by the ALAC against applicant "Stable Tone Limited" for the ".健康" (jiankang) string Therefore, the ALAC will have to consider the filing of the objection statement against: - applicant "DotHealth, LLC" for the ".HEALTH" string (https://community.icann.org/x/t4xwAg) - applicant "“Goose Fest, LLC" for the ".HEALTH" string (https://community.icann.org/x/v4xwAg) - applicant "dot Health Limited" for the ".HEALTH" string (https://community.icann.org/x/xYxwAg) - applicant "Afilias Limited" for the ".HEALTH" string ( https://community.icann.org/x/y4xwAg) As the objection statement against the applicant "Stable Tone Limited" for the for the ".健康" (jiankang) string failed to get RALO support, this statement will not be considered by the ALAC. An ALAC meeting to consider the advice by the RALOs is scheduled for Friday March 8 2013 https://community.icann.org/x/8JNwAg Kind Regards, Dev Anand Teelucksingh gTLD RG chair

2 1

Re: [EURO-Discuss] IMPORTANT: At-Large Objection Statements posted for RALO review - deadline for RALO advice to ALAC is now March 6 2013
by Dev Anand Teelucksingh March 7, 2013

March 7, 2013

Dear All, Please note that the objection statement against the applicant "dot Health Limited" for the ".health" string (https://community.icann.org/x/xYxwAg) and the objection statement against the applicant "Stable Tone Limited" for the "健康" ("jiankang") string (https://community.icann.org/x/0YxwAg) was updated on March 1 2013 to remove incorrect references to other applicants in these statements. The updated objection statements can be found on the respective wiki pages. On the gTLD RG call with the RALO officers on February 28 2013, an abstain option was added, instead of just a "Yes" or "No" answer for RALO. The RALO advice to the ALAC requires answers to the 5 questions listed at https://community.icann.org/x/t45wAg Finally, given clarification by ICANN's new gTLD staff as to the process by which funding from ICANN is made available to the ALAC, the RALO's answers to the 5 questions at https://community.icann.org/x/t45wAg can be sent to the ALAC by March 6 2013, 23:59 UTC. Kind Regards, Dev Anand Teelucksingh On Tue, Feb 26, 2013 at 3:06 PM, ICANN At-Large Staff <staff(a)atlarge.icann.org> wrote: > Dear All, > > Please see an important message being sent on behalf of Dev Anand Teelucksingh, Chair of the At-Large new gTLD Review Group: > > ** > Dear All, > > As per the process by which the ALAC can object to a new gTLD application, (see one page PDF at http://bit.ly/how-ALAC-files-objection-to-new-gTLD ), the new gTLD Review Group (gTLD RG) have posted objection statements on community grounds to 5 new gTLD applications for Regional At-Large Organisation (RALO) review and advice to the ALAC. > > The gTLD RG drafted the statements based on the outcomes of its review and discussion of comments received by February 8, 2013 (see http://atlarge-lists.icann.org/pipermail/at-large/2013q1/009493.html) > > All of the objection statements are on community objection grounds. The community objection grounds page at https://community.icann.org/x/QgkQAg lists four tests that would enable the Dispute Resolution Service Provider hearing the objection to determine whether there is substantial opposition from a significant portion of the community to which the string may be > targeted. Note also that ALL four tests must be met for the objection to prevail. > > The 5 applications and objection statements, including the comments received by the gTLD RG on the applications can be found on the workspace at https://community.icann.org/x/soxwAg with 5 separate wiki pages for each new gTLD application, the objection statement and the comments received by the gTLD RG. Members of At-Large are invited to discuss and post questions or comments on these wiki pages. > > All RALOs must review EACH of the 5 gTLD applications and the associated information (objection statement, comments) on the wiki pages and decide if the objection statement drafted by the gTLD RG group supports the criterion for community objection. > > The RALO cannot modify any of the 5 objection statements, but must advise the ALAC as to whether the RALO EITHER: > 1) supports the objection statement being filed by the ALAC against the new gTLD application OR > 2) NOT support the objection statement being filed by the ALAC against the new gTLD application. > > This advice for each of the 5 objection statements must be sent to the ALAC by March 5, 2013, 23:59 UTC so that the ALAC can review the RALO advice before the end of the objection period on March 13, 2013. > > A conference call is tentatively scheduled on Thursday, February 28, 2013 (exact time will be confirmed by At-Large Staff) is being planned for RALO officers with the gTLD RG members to provide an overview of the process and to answer any questions they may have as to what is expected by the RALOs as per the process by which the ALAC can object to a new > gTLD application. At-Large members are welcome to attend this call. > > Kind regards, > Dev Anand Teelucksingh > > ** > > Regards, > > Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine, and Julia Charvolen > ICANN Policy Staff in support of the ALAC > E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

7 8