November 2012 - ALAC - lists.icann.org

Fwd: MOTION TO RECOMMEND PROTECTIONS IN THE FIRST ROUND OF NEW GTLDS FOR CERTAIN RED CROSS/RED CRESCENT (RCRC) AND INTERNATIONAL OLYMPIC COMMITTEE (IOC) NAMES
by Alan Greenberg Nov. 8, 2012

Nov. 8, 2012

FYI. Alan >From: "Neuman, Jeff" <Jeff.Neuman(a)neustar.us> >To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> >Date: Wed, 7 Nov 2012 14:42:01 -0500 >Subject: [council] MOTION TO RECOMMEND PROTECTIONS IN THE FIRST >ROUND OF NEW GTLDS FOR > CERTAIN RED CROSS/RED CRESCENT (RCRC) AND INTERNATIONAL OLYMPIC COMMITTEE > (IOC) NAMES > >All, > >On behalf of the IOC/RCRC Drafting Team, I am pleased to present the >following motion which was supported by the Drafting Team. For the >record, I will note that the recommendations were not supported by >the Non-Commercial Stakeholder Group and Thomas Rickert, but were >supported by the Registries Stakeholder Group, the, Intellectual >Property Constituency, Business Constituency and ISP Constituency, >the representative from the ALAC, and those representatives from the >International Olympic Committee and the Red Cross/Red Crescent. The >Registrars Stakeholder group did not participate on the Drafting Team. > >Thanks. >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > >MOTION TO RECOMMEND PROTECTIONS IN THE FIRST ROUND OF NEW GTLDS FOR >CERTAIN RED CROSS/RED CRESCENT (RCRC) AND INTERNATIONAL OLYMPIC >COMMITTEE (IOC) NAMES > >Made by: Jeff Neuman >Seconded by: > >WHEREAS: > >The Board Resolution 2011.06.20.01, authorized "the President and >CEO to implement the new gTLD program which includes . . . >incorporation of text concerning protection for specific requested >Red Cross and IOC names for the top level only during the initial >application round, until the GNSO and GAC develop policy advice >based on the global public interest, . . ." >(<http://www.icann.org/en/groups/board/documents/resolutions-20jun11-en.htm>http://www.icann.org/en/groups/board/documents/resolutions-20jun11-en.htm) > >The IOC/RC Drafting Team established [Date] by the GNSO Council has >considered a number of different options with respect to protections >of both the IOC and the RCRC terms in response to the GAC proposal >to provide permanent protection for such terms including at the >second level in new gTLDS; > >The solution proposed by the IOC/RC Drafting Team, to initiate a PDP >and to provide temporary reservation of the exact match IOC/RC >names, was posted for public comment on 28 September 2012 and closed >on 9 November 2012; > >The GNSO has now [Date] initiated a policy development process (PDP) >to evaluate possible protections for certain international >organization names in all gTLDs, including, specifically, whether to >recommend policies to protect IOC/RCRC names; and > >Therefore, the IOC/RC Drafting Team recommends that the GNSO Council >recommend to the Board that it adopt the second recommendation of >the IOC/RC Drafting Team, providing for temporary reservation of the >exact match IOC/RC names, prior to the delegation of the first >round of new gTLDs. > >NOW THEREFORE, BE IT RESOLVED: > >That the GNSO Council adopts the IOC/RC Drafting Team's >recommendation to temporarily reserve the exact match of IOC and >RCRC second level domain names listed in Section 2.2.1.2.3 of the >Applicant Guidebook and per the GAC recommendation of 14 September >2011pending the outcome of the recently launched policy development >process involving International Governmental and Non-governmental >Organizations. > >That the GNSO Council thanks the members of the IOC/RC Drafting Team >for their efforts in producing these recommendations, and hereby >disbands the IOC/RC Drafting Team; and > >That the Chair of the GNSO Council is authorized to forward these >recommendations to the ICANN Board. > > >Jeffrey J. Neuman >Neustar, Inc. / Vice President, Business Affairs >46000 Center Oak Plaza, Sterling, VA 20166 >Office: +1.571.434.5772 Mobile: +1.202.549.5079 Fax: >+1.703.738.7965 / ><mailto:jeff.neuman@neustar.biz>jeff.neuman(a)neustar.biz / www.neustar.biz >

1 0

Fwd: Motion to Adopt IGO-INGO PDP WG Charter for Submission to the Council
by Alan Greenberg Nov. 8, 2012

Nov. 8, 2012

FYI. Alan >From: Lanre Ajayi <lanre(a)pinet.com.ng> >To: <council(a)gnso.icann.org> >Subject: [council] Motion to Adopt IGO-INGO PDP WG Charter for >Submission to the Council >Date: Wed, 7 Nov 2012 23:34:23 +0100 > >To the GNSO Council, > >On behalf of the IGO-INGO Protection PDP WG Charter Drafting Team, I >am pleased to present the following motion and draft WG Charter >(attached) which was approved by the Drafting Team. > >Motion to approve the Charter for the IGO-INGO Protection PDP Working Group > >Made by: Lanre Ajayi >Seconded by: > >Whereas > >On 17 October 2012 the GNSO Council initiated a Policy Development >Process (PDP) on the protection of certain IGO and INGO names in all >gTLDs, and decided to create a PDP Working Group for the purposes of >fulfilling the requirements of the PDP; > >Following a call for volunteers, a drafting team was formed and its >members have developed a charter for consideration by the GNSO Council; > >The GNSO Council has reviewed the charter submitted by the drafting team. > >NOW THEREFORE, BE IT RESOLVED, > >The GNSO Council approves the charter and appoints [Name] as the >GNSO Council Liaison to the IGO-INGO Protection PDP Working Group. > >The GNSO Council further directs that the work of IGO-INGO >Protection PDP Working Group be initiated no later then 14 days >after the approval of this motion. Until such time as the WG can >select a chair and that chair can be confirmed by the GNSO Council, >the GNSO Council Liaison shall act as interim chair. > >Charter [ATTACHED]

1 0

ALAC/At-Large Mailing Lists
by Alan Greenberg Nov. 2, 2012

Nov. 2, 2012

While working on the Rules of Procedure, it became obvious that we needed a document describing the various ALAC mailing lists giving a summary of their usage and describing who must of should be subscribed. This list will not include RALO lists or the multitude of working group and committee lists Currently there are five such lists. All are archived and are publicly viewable except as noted. ALAC - General ALAC list used for the majority of ALAC e-mail interactions. Originally only ALAC members, RALO leadership, formal Liaisons selected by the ALAC, Liaisons to the ALAC, At-Large Board member and Staff were on it. More recently, it has included (either by accident or intentionally), selected former ALAC member, selected former RALO leadership, and others. (I am using the term "formal Liaisons" to refer to the ccNSO, GNSO and SSAC Liaisons - those to other ICANN or external bodies.) ALAC-Internal - Used for things that we do not want to be publicly viewable. Most commonly, this is travel arrangements, social plans and occasionally semi-confidential issues or issues where we want targeted ALAC feedback. Membership is similar to the ALAC list, but no "others" ALAC-ExCom - Publicly viewable list for the ALAC ExCom. Membership is traditionally ExCom members, formal Liaisons appointed by the ALAC, and Staff. More recently a few others were added. ALAC-Announce - General list for announcements. Only ICANN staff and the ALAC Chair (I think) have sending privileges. This list includes pretty much everyone in the ALAC list plus about 175 others. At-Large - General public list. This list has Most but not all of those onthe ALAC list (missing about 10 ALAC members and RALO leadership) plus about 160 others. ALAC-Announce and At-Large membership overlaps. There are 98 people on both lists (about 1/3 of which are ALAC/RALO Leadership), 126 just ALAC-Announce and 98 just At-Large For mail sent to lists from senders not on the lists, there are four possible outcomes, it goes through, it is held for moderation, it bounces or it is discarded without a reject message (moderation requires staff action). Based on a test, I believe that for the ALAC list, such messages are discarded, for the ALAC-Internal list, such mail bounces, and for the ExCom it is moderated. Not sure about the two larger lists. My suggestions for going forward are: ALAC - Membership for ALAC, RALO Leadership, formal Liaisons appointed by the ALAC, Board member and Staff - Membership for Liaisons appointed TO the ALAC - Perhaps membership to WG Chairs if not already included above - Membership for past holders of above categories (my preference, or could be receive only - see below) ALAC-Internal - Membership for ALAC, RALO Leadership, formal Liaisons appointed by the ALAC, Board member and Staff ALAC-ExCom (with a new name mapping to the ALAC Leadership Team name used in the new RoP) - Members of the ExCom, formal Liaisons appointed by the ALAC, Board member and Staff I think we need to discuss the ALAC-Announce and At-Large lists further. I am not at all sure we need two lists for this. I suggest we create two additional lists that "shadow" the ALAC and ExCom lists. That is, subscription open to all and they receive all messages that got to the ALAC and ExCom lists. This allows those who want to follow the discussions to receive them without the inconvenience of having to go to the archive. This is equivalent to adding the to the lists in receive-only mode, but since we have had regular problems ensuring that the membership of the ALAC and ExCom lists is correct, having a shadow list would be a lot cleaner. Please let me know what you think about these issues. Alan

4 7

Reminder: At-Large Toronto Meeting Reports
by Olivier MJ Crepin-Leblond Nov. 2, 2012

Nov. 2, 2012

Please be so kind to find the Reporting Page for all of the meetings you attend at ICANN 45 in Toronto. https://community.icann.org/x/cRAQAg Please fill this table as you attend meetings which are not At-Large meetings. As mentioned at the end of the Sunday working session, it is *really* important that you fill these in order to provide a good overview of the matters discussed in other sessions for those who have not been able to attend. Many thanks, Olivier

2 1