July 2013 - ALAC - lists.icann.org

Re: [ALAC] ALAC E-mail Guide - for review
by Alan Greenberg July 27, 2013

July 27, 2013

At 24/07/2013 05:05 PM, Evan Leibovitch wrote: >My feedback. And mine, with the reminder that this guide is documenting what we have now, not what we may want to morph them into. Does anyone else have any comments? > * There IMO needs to be more distinction between the functions > and scope of the At-Large list vis. the ALAC list. Not sure what the issue is confusing those two lists. > * At very least, the At-Large list needs to be re-ordered near > the top. Where it is it seems out-of-place and almost as an afterthought. The order in this document has no real meaning. I ordered them based on the progression of ALAC -> RALO -> At-Large, but have not real stake in what order they are in. > * No mention in the Announce list of how unaffiliated members > (in regions that allow this) are accommodated. Do they have to self-subscribe? That is the way it is now. I suppose the Unaffiliated NARALO member should be subscribed by staff. Unaffiliated members could be as well, but that is not a thing that we have done in the past or now. Since they do not have an "ALS" list of their own, certainly something that we could do (but we in NARALO need to clean up that entire unaffiliated process, so I will presume it will wait for that to happen). > * The change from ExCom to "Leadership Team" is new, and needs > to be announced (and perhaps discussed) separately The list is still called ExCom and that is how it is documented. The comment notes that it will likely change at some point after the new RoP are in place. Presumably once the new RoP goes into effect and we start using the new name, appropriate announcements will be made. > * The regional lists' info don't say much about the treatment of > RALO non-members. Does everyone have the same privileges, including > possibly the overpowering by outsiders of discussions amongst RALO members? I have never heard of any such rules in any of the RALO lists (perhaps ignorance on my part) but presume if there were any, they would be RALO-initiated. In light of recent experiences, we probably should add something regarding the what level of Authority the RALO Chair has over list. > * Does a single code of conduct govern all lists, or are there > different codes for each list? The RoP talks about a Code of Conduct for all At-Large electronic communications platforms including e-mail. I presume that a RALO could add additional rules, but I have never heard of such an occurrence. Alan >- Evan > > >On 24 July 2013 16:28, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Forgot to add, the draft Guide is also on the wiki at ><https://community.icann.org/x/kIYi>https://community.icann.org/x/kIYi. Alan > >At 24/07/2013 11:21 AM, Alan Greenberg wrote: >You will recall that one of the documents referred to by our new >Rules of Procedure is the ALAC E-mail Guide. This documents >describes our basic e-mail lists and also says which lists (or other >means of communications) are to be used in relation to selection >processes as well as removal/recall processes. >Please review the attached document. My intent was, like the various >Adjunct Documents, to have it mirror our current practices. Changes >may well be needed, but that can be done once we have all of the >documents and the new Rules of Procedure in place. > >In our earlier discussions, the intent was to not include the RALO >Discuss lists here, but since staff must subscribe people to them at >critical times, I would suggest that we include them here to allow >us to capture all mandatory subscription rules in one place. >Once any errors are corrected, I will move that it be adopted. >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… > > >_______________________________________________ >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… > > > > >-- >Evan Leibovitch >Toronto Canada >Em: evan at telly dot org >Sk: evanleibovitch >Tw: el56

2 1

Re: [ALAC] ALAC E-mail Guide - for review
by Alan Greenberg July 24, 2013

July 24, 2013

Forgot to add, the draft Guide is also on the wiki at https://community.icann.org/x/kIYi. Alan At 24/07/2013 11:21 AM, Alan Greenberg wrote: >You will recall that one of the documents referred to by our new >Rules of Procedure is the ALAC E-mail Guide. This documents >describes our basic e-mail lists and also says which lists (or other >means of communications) are to be used in relation to selection >processes as well as removal/recall processes. > >Please review the attached document. My intent was, like the various >Adjunct Documents, to have it mirror our current practices. Changes >may well be needed, but that can be done once we have all of the >documents and the new Rules of Procedure in place. > >In our earlier discussions, the intent was to not include the RALO >Discuss lists here, but since staff must subscribe people to them at >critical times, I would suggest that we include them here to allow >us to capture all mandatory subscription rules in one place. > >Once any errors are corrected, I will move that it be adopted. > >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…

2 1

ALAC E-mail Guide - for review
by Alan Greenberg July 24, 2013

July 24, 2013

You will recall that one of the documents referred to by our new Rules of Procedure is the ALAC E-mail Guide. This documents describes our basic e-mail lists and also says which lists (or other means of communications) are to be used in relation to selection processes as well as removal/recall processes. Please review the attached document. My intent was, like the various Adjunct Documents, to have it mirror our current practices. Changes may well be needed, but that can be done once we have all of the documents and the new Rules of Procedure in place. In our earlier discussions, the intent was to not include the RALO Discuss lists here, but since staff must subscribe people to them at critical times, I would suggest that we include them here to allow us to capture all mandatory subscription rules in one place. Once any errors are corrected, I will move that it be adopted. Alan

1 0

MoU with RIRs
by Holly Raiche July 24, 2013

July 24, 2013

Hi Everyone I had a brief conversation with Paul Wilson, Chair of the NRO (and Director Generao of ApNIC) and the APNIC External Relations Program Director - who was keen to follow up on the meeting with RIRs - and something more concrete in the way of a relationship between APNIC and APRALO. So while I will follow up with him, I'd like examples of other RIR/RALO relationships - particularly the LACRALO MoU - what does it provide? AAny and all information is welcome so that I can provide the sort of examples that will put the APNIC/APRALO relationship on a better footing Holly

8 17

Call for Volunteers: GNSO Policy & Implementation Working Group
by Alan Greenberg July 18, 2013

July 18, 2013

<http://gnso.icann.org/en/announcements/announcement-18jul13-en.htm>http://gnso.icann.org/en/announcements/announcement-18jul13-en.htm Call for Volunteers: GNSO Policy & Implementation Working Group In brief The Generic Names Supporting Organization (GNSO) Council seeks volunteers to serve on a Working Team that has been tasked to address a number of issues that have been raised in the context of the recent discussions on policy & implementation that affect the GNSO. What This Working Group Will Do The Working Group is tasked to provide the GNSO Council with a set of recommendations on: 1. A set of principles that would underpin any GNSO policy and implementation related discussions, taking into account existing GNSO Operating Procedures. 2. A process for developing gTLD policy, perhaps in the form of "Policy Guidance", including criteria for when it would be appropriate to use such a process (for developing policy other than "Consensus Policy") instead of a GNSO Policy Development Process; 3. A framework for implementation related discussions associated with GNSO Policy Recommendations; 4. Criteria to be used to determine when an action should be addressed by a policy process and when it should be considered implementation, and; 5. Further guidance on how GNSO Implementation Review Teams, as defined in the PDP Manual, are expected to function and operate. For further details on the charter, please see <http://gnso.icann.org/en/drafts/policy-implementation-charter-04jul13-en.pdf>http://gnso.icann.org/en/drafts/policy-implementation-charter-04jul13-en.pdf. How This Working Group Will Work ICANN Working Groups use transparent, open processes. The meetings of this WG will be recorded, and the recordings will be available to the public. The mailing list for the Working Group will be archived publicly. Working Group members are expected to submit Statements of Interest (SOI). The group will collaborate using a public workspace. The Working Group is expected to follow the <http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf>GNSO Working Group Guidelines. How to Join The GNSO Council invites all interested parties to put forward their names so they can be added to the WG mailing list. The WG will be open to anyone interested to join. Community members who wish to be invited to join the group should contact the <mailto:gnso.secretariat@icann.org?subject=Application%20to%20Join%20Policy%20and%20Implementation%20WG>GNSO secretariat (<mailto:gnso.secretariat@icann.org>gnso.secretariat(a)icann.org) Background Mainly as a result of discussions stemming from implementation related issues of the new gTLD program, there is increased focus on which topics call for policy and which call for implementation work, including which processes should be used, at what time and how diverging opinions should be acted upon. In order to facilitate these discussions, ICANN Staff developed a draft framework for community discussion that identifies a number of steps and criteria that might facilitate dealing with similar questions in the future. The paper identifies a number of questions that the community may want to consider further in this context, as well as a couple of suggested improvements that could be considered in the short term. While developing a bright-line rule as to what is policy or implementation may not be possible, the hope is that by developing clear processes and identifying clear roles and responsibilities for the different stakeholders, it will become easier to deal with these issues going forward and allow for broad participation and involvement. Following several discussions by the GNSO Council on this topic, the GNSO Council has now formed a Working Group which has been tasked to provide concrete recommendations on how to address some of these issues from a GNSO perspective.

1 0

Prague Schedule / Tuesday 16 October 2012
by At-Large Staff July 17, 2013

July 17, 2013

Dear All, Please find hereafter the At-Large schedule for tomorrow, Tuesday 16 October 2012 with all remote participation details listed on the ICANN Schedule: Wiki Agenda page: http://tinyurl.com/9h95fo6 ICANN Schedule: http://toronto45.icann.org/full-schedule Meeting Room Map: http://toronto45.icann.org/files/meetings/toronto2012/45-Toronto-VenueMap-3O ct12.png * 07:00 - 08:00 NARALO Capacity Building Session 2 Regatta Room http://toronto45.icann.org/node/34285 * 08:00 - 09:00 Joint NARALO / Fellows Meeting 2 Frontenac http://toronto45.icann.org/node/34283 * 08:30 09:30: Meeting with ICANN Board Metro East http://toronto45.icann.org/node/34289 * 10:00 - 11:00: At-Large Capacity Building: Next Steps Regatta http://toronto45.icann.org/node/34307 * 11:00 13:00: ALAC Policy Discussion Part 1 Regatta http://toronto45.icann.org/node/34313 13:00 - 14:00 LUNCH break * 14:00 16:00: ALAC Policy Discussion Part 2 Regatta http://toronto45.icann.org/node/34327 * 16:00 - 17:00: Registrant Rights and Responsibilities Working Group Regatta http://toronto45.icann.org/node/34353 * 17:00 18:00: At-Large Outreach Sub-Committee Meeting Regatta http://toronto45.icann.org/node/34361 General Meetings: Please refer to full Schedule: http://prague44.icann.org/full-schedule Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, and Nathalie Peregrine ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org

4 14

Fwd: [gnso-igo-ingo] ICRC/IFRC Letter to ICANN Board
by Alan Greenberg July 15, 2013

July 15, 2013

FYI, A letter from the International Committee of the Red Cross was sent to the ICANN Board and senior staff. <http://www.icann.org/en/news/correspondence/daccord-gelata-to-atallah-et-al…>http://www.icann.org/en/news/correspondence/daccord-gelata-to-atallah-et-al… The letter is asking the Board for permanent protection (instead of what the Board has done to date, provide protection pending the completion of the GNSO PDP) and adds the names of 189 national societies (in English and their official natural languages). They are also re-surfacing the strings-contained(RedCross-tsunami) and confusingly similar (RedKross) at both the top level (controversial but easy to implement) and 2nd level (almost impossible to implement). Alan

1 0

At-Large Multistakeholder Policy Roundtable in Durban @ ICANN 47
by Rinalia Abdul Rahim July 9, 2013

July 9, 2013

Dear Members of the At-Large Community, Please join us for the upcoming At-Large Multistakeholder Policy Roundtable in Durban (on site or via remote participation). Program information is indicated below and attached. Best regards, Rinalia *AT-LARGE MULTISTAKEHOLDER POLICY ROUNDTABLE * *@ ICANN 47 [Durban, South Africa]* Date: 15 July 2013 (Monday) Time: 14:00-16:00 Meeting Room: Hall 2AB http://durban47.icann.org/node/39645 * **New gTLDs: Addressing Consumer and Public Interest Concerns* ICANN’s new generic Top Level Domain (gTLD) Program will dramatically expand the Top Level Domain Space. The program carries benefits for end users and registrants in terms of increasing choice and competition, but it also raises a range of consumer and public interest concerns. These concerns include consumer safety and trust, multilingual access to gTLDs via internationalized scripts, rights issues related to the protection of trademarks, non-registered marks and geographic names, as well as barriers to program participation for stakeholders in the developing world. The At-Large Multistakeholder Policy Roundtable will highlight these issues and explore the adequacy of policies and mechanisms meant to address them. Discussion Questions: 1. What are the consumer and public interest concerns in relation to the new gTLD program? 2. Are the policies and mechanisms that have been developed to address these concerns adequate? 3. What more needs to be done to address these concerns effectively? Co-Chair: · Olivier Crepin-Leblond (Chair, At-Large Advisory Committee) · Rinalia Abdul Rahim (Executive Committee Member, At-Large Advisory Committee & Convenor, At-Large Multistakeholder Policy Roundtable) * * *Lead Discussants* Consumer Perspective – Holly Raiche (Chair, At-Large Registrant Rights and Responsibilities Working Group & Board Member, Australian Communications Consumers Action Network) * * Public Interest and Government Perspective – Peter Nettlefold (Vice Chair, ICANN Governmental Advisory Committee & GAC Lead on New gTLDs) Business Users Perspective – Zahid Jamil (Executive Committee Member, ICANN Business Constituency & Member, GNSO Council) Consumer Trust, Choice and Competition Perspective – Steve DelBianco (Executive Director, NetChoice & Vice-Chair for Policy Coordination, ICANN Business Constituency) Intellectual Property Rights & IDN Perspective – Hong Xue (Director, Institute for Internet Policy and Law, Beijing Normal University & Member, ccNSO Council) Community - Indigenous Groups’ Perspective - Karaitiana Taiuru (Chair, New Zealand Maori Internet Society) * * Community - Geographic Names Perspective – Olga Cavalli (Representative of Argentina to the Governmental Advisory Committee & Director, South School on Internet Governance) Developing Country Perspective – Tijani Ben Jemaa (Executive Committee Member, At-Large Advisory Committee & Vice-Chair, African Regional At-Large Organization) * * ICANN Compliance Perspective - Maguy Serad (Vice-President, Contractual Compliance Services, ICANN) Participation: This roundtable is open. Members of the following ICANN community are especially invited to attend - ICANN At-Large community, ICANN Advisory Committees, ICANN Supporting Organizations, ICANN Board and ICANN Staff. * * END* *

3 2

Mention on CircleID
by Carlton Samuels July 9, 2013

July 9, 2013

Our friend Stephane van Gelder has commented on our gripe to the Board re the response -or lack thereof - to specific SSAC Advisories pertaining Security and Stability; SAC046, SAC053, SAC057 advisory. http://www.circleid.com/posts/20130709_technical_impact_of_new_gtlds_are_we… -Carlton ============================== Carlton A Samuels Mobile: 876-818-1799 *Strategy, Planning, Governance, Assessment & Turnaround* =============================

1 0

First draft of comments on the IGO-INGO name protection WG report
by Alan Greenberg July 9, 2013

July 9, 2013

The first draft of a general comment and answers to the questions posed by the PDP WG has been posted to the Wiki at https://community.icann.org/x/hTR-Ag. I worked on this with Evan, so he should be in agreement, but he has not yet gotten back to me with a formal "all ok" due to other issues and travel preparation. The statement is generally in line with previous ALAC statements on the issues, although the tone is a bit softer on the issue of top-level protection of names (but not acronyms), where we do not see the need for blocking protection, but in most cases, it would not cause harm either (with the exceptions clearly noted). To fully understand the answers, you need to at least look at the full form of the questions at http://gnso.icann.org/en/issues/igo-ingo-initial-response-form-20jun13-en.d… and preferably the entire report at http://gnso.icann.org/en/issues/igo-ingo-initial-14jun13-en.pdf. The comment period closes on 17 July. Alan

1 0