- ALAC - lists.icann.org

Re: [ALAC] Fwd: A CWG to develop an IANA stewardship transition proposal
by Olivier MJ Crepin-Leblond Sept. 25, 2014

Sept. 25, 2014

Dear Tijani, thank you for your follow-up. I do not know whether observers need to register with the ALAC. They might quite openly follow or stop following the discussion. No doubt we'll have a few designated observed from the IANA Issues WG. We'll discuss this point on the IANA Issues WG shortly. Kindest regards, Olivier On 25/09/2014 07:23, Tijani BEN JEMAA wrote: > Thank you Olivier for this. > > AFRALO has already appointed its representative. > Besides the 5 At-Large members of the CWG, we need perhaps to identify the > observers from our side. You said earlier that all members of the IANA > Issues WG would be observers, but you need to know who wants to be observer > from this pool. > > > > > -----Message d'origine----- > De : alac-bounces(a)atlarge-lists.icann.org > [mailto:alac-bounces@atlarge-lists.icann.org] De la part de Olivier MJ > Crepin-Leblond > Envoyé : mercredi 24 septembre 2014 18:46 > À : alac Working List > Objet : [ALAC] Fwd: A CWG to develop an IANA stewardship transition proposal > > Dear all, > > please be so kind to find an update on the CWG to develop and IANA > Stewardship Transition Proposal. > > Our own status update: at the moment 3 out of 5 RALOs have provided the name > of their proposed candidate for this CWG, all candidates coming from the > pool of volunteers currently part of the At-Large IANA Issues WG. As soon as > I receive the feedback from the two missing RALOs, NARALO & AFRALO, I shall > ask for consensus from the ALAC and if such consensus is reached, I'll > forward the details as per the process below. > > Kind regards, > > Olivier MJ Crépin-Leblond > ALAC Chair > > > -------- Forwarded Message -------- > Subject: A CWG to develop an IANA stewardship transition proposal > Date: Wed, 24 Sep 2014 17:16:31 +0100 > From: Jonathan Robinson <jonathan.robinson(a)ipracon.com> > To: Heather.Dryden(a)ic.gc.ca, 'Olivier MJ Crepin-Leblond' <ocl(a)gih.com>, > Patrik Fältström <paf(a)frobbit.se> > CC: Byron Holland <byron.holland(a)cira.ca>, Bart Boswinkel > <bart.boswinkel(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, > olof.nordling(a)icann.org > > > > Dear Colleagues, > > > > Please see attached. > > > Thank-you. > > > > Jonathan > > > > > > Jonathan Robinson > > Chair > > ICANN GNSO Council > > > > jonathan.robinson(a)ipracon.com <mailto:jonathan.robinson@ipracon.com> > > Tel: +44 (0)20 7993 6103 > > skype: jonathan.m.r > > > > > > > > > > --- > Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. > http://www.avast.com > >

1 0

Fwd: A CWG to develop an IANA stewardship transition proposal
by Olivier MJ Crepin-Leblond Sept. 24, 2014

Sept. 24, 2014

Dear all, please be so kind to find an update on the CWG to develop and IANA Stewardship Transition Proposal. Our own status update: at the moment 3 out of 5 RALOs have provided the name of their proposed candidate for this CWG, all candidates coming from the pool of volunteers currently part of the At-Large IANA Issues WG. As soon as I receive the feedback from the two missing RALOs, NARALO & AFRALO, I shall ask for consensus from the ALAC and if such consensus is reached, I'll forward the details as per the process below. Kind regards, Olivier MJ Crépin-Leblond ALAC Chair -------- Forwarded Message -------- Subject: A CWG to develop an IANA stewardship transition proposal Date: Wed, 24 Sep 2014 17:16:31 +0100 From: Jonathan Robinson <jonathan.robinson(a)ipracon.com> To: Heather.Dryden(a)ic.gc.ca, 'Olivier MJ Crepin-Leblond' <ocl(a)gih.com>, Patrik Fältström <paf(a)frobbit.se> CC: Byron Holland <byron.holland(a)cira.ca>, Bart Boswinkel <bart.boswinkel(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, olof.nordling(a)icann.org Dear Colleagues, Please see attached. Thank-you. Jonathan Jonathan Robinson Chair ICANN GNSO Council jonathan.robinson(a)ipracon.com <mailto:jonathan.robinson@ipracon.com> Tel: +44 (0)20 7993 6103 skype: jonathan.m.r

1 0

Fwd: RE: Joint SO-AC-SG-C Submission on ICANN's Enhancing ICANN Accountabitliy Plan -- Clarifying Questions
by Olivier MJ Crepin-Leblond Sept. 24, 2014

Sept. 24, 2014

Dear ALAC members, following up on my earlier message to the list concerning the ICANN Enhancing Accountability Plan, as well as my update on today's ALAC call, please be so kind to find a proposal from the Registry Constituency with a follow-up set of points. Since the ALAC has not so far drafted any text for the Public Comment period which we have displayed on https://community.icann.org/x/7g3xAg may I suggest that we consider supporting the points made below? As the closing date for this public comment is this Saturday, I would ideally like to hear your concerns in the next 24H and if there are no objections, it would be worth considering conducting an ALAC vote on a Statement that takes those points. Looking forward to your kind feedback. Best regards, Olivier MJ Crépin-Leblond ALAC Chair -------- Forwarded Message -------- Subject: RE: Joint SO-AC-SG-C Submission on ICANN's Enhancing ICANN Accountabitliy Plan -- Clarifying Questions Date: Mon, 22 Sep 2014 13:57:23 +0000 From: Drazek, Keith <kdrazek(a)verisign.com> To: Quick update. Per my note below, here are the RySG’s proposed procedural adjustments related to #2 below. This is also still under discussion, but I wanted to share. The proposed plan requires further procedural clarification regarding the final stage of ICANN Board acceptance, referral or rejection of consensus recommendations delivered by community via Coordinating Group (CG). We include the following as procedural enhancements that would enhance confidence and predictability: 1. The process must assume that the Board will accept all community recommendations delivered by the Coordinating Group (CG) unless a legal conflict is identified and confirmed by independent experts chosen by the community. 2. There will be regular checkpoints between the CG and the ICANN Board, Staff and General Counsel to identify any procedural or legal concerns prior to delivery of recommendation. 3. In the unlikely event the Board cannot accept a recommendation it may not simply reject it. It must send it back to the CG for further engagement. 4. Referral of any recommendation back to the CG shall require a unanimous Board vote. 5. Any referral must take place within a reasonable timeframe to allow for dialogue and resolution and to prevent conflict with the 9/2015 target date for IANA stewardship transition. 6. All Board meetings, teleconferences, discussions and email on the Accountability issue must be open, including exchanges with the ICANN General Council, the Board liaison, Staff liaison and other ICANN staff. I welcome your views on the above. Regards, Keith *From:*Drazek, Keith *Sent:* Monday, September 22, 2014 10:30 AM *To:* Byron Holland; Heather Dryden; tony holmes; Michele Neylon :: Blacknight; elisa.cooper(a)markmonitor.com; krosette(a)cov.com; rafik.dammak(a)gmail.com; William Drake; Jonathan Robinson; Patrik Fältström; liman(a)netnod.se; Olivier MJ Crepin-Leblond *Subject:* Fwd: Joint SO-AC-SG-C Submission on ICANN's Enhancing ICANN Accountabitliy Plan -- Clarifying Questions Hi everyone, I'm sure you're all reviewing and assessing ICANN's response to our September 3 letter. As you know, the public comment deadline is this coming Saturday, so time is very short to submit any recommended adjustments to ICANN's proposed process on Enhancing ICANN Accountability. I feel strongly that the only chance we, the community, have to constructively amend this process is to stick together and continue to present a united front...as we have for the last 2 months. The RySG is working to finalize the few key adjustments or clarifications we think are necessary for our support of (and trust in) the process. Our current thinking is included below for your consideration. Can you please respond to this message and share your respective group's plans and your preliminary views? Can we try to align our recommendations to come up with another joint statement, or at least identify a baseline of recommendations that would receive full support? Following ICANN's response to our September 3 letter, here are the RySG's current views (still under discussion): 1. The 7 Advisors must be advisory only. We welcome the use of expert advisors to inform the work of the Coordinating Group and the Community Working Group, but they should not participate in determining consensus. These advisors are being hand-picked by a group of 4 individuals who were hand-picked by the ICANN CEO. I'm sure everyone recalls that their original plan was to have the Board's Governance Committee appoint the advisors directly and the original cutoff for nominations was September 10. We believe the appointment of these experts is, at least in part, designed to narrow the scope of the community's discussions and recommendation. As such, they should be limited to only providing advice and not be permitted to dilute the community's influence in the Coordinating Group or its role in recommending the final accountability enhancements. If they are advisory only, the community's SO-AC-SG representatives will retain appropriate influence or control over the eventual recommendation. 2. There must be a predictable and agreed-to process for handling any instance where the Board does not accept a consensus recommendation from the Coordinating Group. ICANN's response saying that the Board's interests are the same as the community interests completely misses the fact that their fiduciary responsibility is to the California-based not-for-profit corporation first, and to the community's interests second. As such, we the community need to have confidence in the end-game scenario where the ICANN General Counsel's office tells the Board it cannot or should not accept a consensus recommendation from the Coordinating Group. Ideally this situation will not arise, but we need to prepare for it and have confidence that the Board will not simply be able to reject or selectively accept the CG's recommendations. We are still working on the details of a recommended process, but it will be similar to the proposed language that was edited out from our September 3 letter (because it was a recommendation and not a question). I believe these are the two most critical adjustments we will require to be able to support ICANN staff's proposed process. We originally called for a traditional CCWG and that call was rejected by ICANN because, apparently, a CCWG did not easily allow for the participation of external parties. They also wanted to bring in the external experts as discussed above. Setting aside their motivations for doing so, we believe these two adjustments are critical for establishing a process we can trust. I hope we can come to a common position on fixing this process. I'm sure we're all ready to begin the substantive work of identifying meaningful accountability enhancements. Regards, Keith

4 7

ICANN 51 LA Meeting Matters for IDN WG
by Rinalia Abdul Rahim Sept. 24, 2014

Sept. 24, 2014

Dear At-Large IDN Working Group, As we get closer to the LA meeting, there are a few things that require some attention. 1. IDN WG meeting in LA - Is there a particular topic that you would like discussed? If yes, please propose on this list. - Would you like to receive an update from ICANN staff on the status of Universal Acceptance as well as Root Zone Label Generation Rules projects during the At-Large IDN WG meeting? 2. New Co-Chair - As I am about to begin my official term on the ICANN board, it is appropriate that I step down as Co-Chair of the At-Large IDN WG. I shall continue my focus on IDN matters within the work of the board. - Please nominate suitable candidates who are interested and ready to serve as co-chair of the IDN WG to work together with Edmon Chung in moving the At-Large IDN agenda forward. Thank you. Best regards, Rinalia

2 1

Music Night at ICANN LA: Songsters Needed
by Glenn McKnight Sept. 23, 2014

Sept. 23, 2014

Looking for any ALAC members who are interested in attending Music Night and interested in creating an adhoc music group. Need some props, name for the group, song selection etc. Let me know. Glenn Glenn McKnight mcknight.glenn(a)gmail.com skype gmcknight twitter gmcknight .

1 0

Los Angeles Meeting Registration
by Olivier MJ Crepin-Leblond Sept. 23, 2014

Sept. 23, 2014

Hello everyone, just a quick note to remind you all to register for the ICANN meeting. Having registered in past meetings, it will probably take you less than a minute since all your information will be on file. Kind regards, Olivier

1 0

Preparation of questions for Los Angeles: GSE // GAC // Public Forum
by Olivier MJ Crepin-Leblond Sept. 23, 2014

Sept. 23, 2014

Dear ALAC members, following up on my appeal on the ALAC call, we need to define topics and questions in preparation of our meetings with the Sally Costerton from the Global Stakeholder Engagement Team as well as with the GAC and also topics which the ALAC would suggest for the ICANN meeting Thursday afternoon Public Forum. Questions or topics for the Global Stakeholder Engagement Team: https://community.icann.org/x/GQDxAg Topics of discussion with the GAC: https://community.icann.org/x/IwDxAg Public Forum Topics: https://community.icann.org/x/JQDxAg Please make suggestions on the WIKI by commenting on those pages. Kind regards, Olivier MJ Crépin-Leblond ALAC Chair

1 0

Call for Membership of the ATLAS II Implementation Taskforce
by Heidi Ullrich Sept. 23, 2014

Sept. 23, 2014

Dear All, Olivier Crépin-Leblond, Chair of the ALAC, has requested a call for membership of the ATLAS II Implementation Taskforce Workspace<https://community.icann.org/display/atlarge/ATLAS+II+Implementation+Taskfor…> (ATLAS II IT!). The mission of this ad-hoc At-Large group is to facilitate the implementation of the recommendations stated in the ATLAS II Declaration<https://community.icann.org/download/attachments/48338039/ATLAS-II-Declarat…>. As such it will ensure that implementation of all of the ATLAS II recommendations are completed in a timely manner. Please note that this membership is open to all members of the At-Large community. Please either indicate your interest by commenting on the ATLAS II Implementation Taskforce Workspace<https://community.icann.org/display/atlarge/ATLAS+II+Implementation+Taskfor…> or by writing At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> by 23.59 UTC on Friday, 3 October 2014. 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<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann.atlarge<https://www.facebook.com/icann.atlarge> Twitter: @ICANN_AtLarge<https://twitter.com/ICANN_AtLarge>

4 3

Re: [ALAC] Call for Membership of the ATLAS II Implementation Taskforce
by Alan Greenberg Sept. 22, 2014

Sept. 22, 2014

Please add me. Alan At 22/09/2014 02:05 PM, Heidi Ullrich wrote: >Dear All, >Olivier Crépin-Leblond, Chair of the ALAC, has >requested a call for membership of the ATLAS II >Implementation Taskforce >Workspace<https://community.icann.org/display/atlarge/ATLAS+II+Implementation+Taskfor…> >(ATLAS II IT!). >The mission of this ad-hoc At-Large group is to >facilitate the implementation of the >recommendations stated in the ATLAS II >Declaration<https://community.icann.org/download/attachments/48338039/ATLAS-II-Declarat…>. >As such it will ensure that implementation of >all of the ATLAS II recommendations are completed in a timely manner. >Please note that this membership is open to all >members of the At-Large community. >Please either indicate your interest by >commenting on the ATLAS II Implementation >Taskforce >Workspace<https://community.icann.org/display/atlarge/ATLAS+II+Implementation+Taskfor…> >or by writing At-Large staff at: >staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> >by 23.59 UTC on Friday, 3 October 2014. > >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<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto: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 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

Next Steps for Positions of ALT Member from APRALO and ALAC Liaison to the GNSO
by ICANN At-Large Staff Sept. 20, 2014

Sept. 20, 2014

Dear All, Please note that the ALT decided during its September 16th meeting that the two candidates for the position of ALT Member from APRALO and the two candidates for the position of ALAC Liaison to the GNSO should have an opportunity to confirm that they meet the requirements and are prepared to fulfill the responsibilities of the positions, and to present any other statement that they believe ALAC Members should be aware of before making a decision. The responses are available on the following two workspaces: 1) 2015 APRALO ALT Candidate Questions and Answers Workspace<https://community.icann.org/display/atlarge/2015+APRALO+ALT+Candidate+Quest…> and 2) 2015 ALAC Liaison to the GNSO Candidate Questions and Answers Workspace<https://community.icann.org/display/atlarge/2015+ALAC+Liaison+to+the+GNSO+C…>. The deadline for the responses is 24 September at 23:59 UTC. The ALAC voting process will begin on 29 September at 00:00 UTC and close on 3 October at 23:59 UTC. 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<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann.atlarge<https://www.facebook.com/icann.atlarge> Twitter: @ICANN_AtLarge<https://twitter.com/ICANN_AtLarge>

1 0