April 2012 - council - lists.icann.org

Re: 2 questions about our Council agenda
by Stéphane Van Gelder 10 Apr '12

10 Apr '12

John, Thanks for your questions. I am copying the Council list. On item 3, that is a discussion for the meeting itself. This agenda item stems from the Council's decision, taken in CR, to delay on this PDP. We are acting on that decision. On item 5, this was proposed by one of the VCs. It is a question being asked. Once again, I would suggest that we not preempt the very discussion we are trying to have by starting it now, but instead have it during the call. If there is no topic here, then that is what our minutes for the meeting will say and we can all move on. But the Council may welcome the chance to discuss this. Stéphane Le 10 avr. 2012 à 17:40, <john(a)crediblecontext.com> a écrit : > Gentlemen, > > With regard to: > > Item 3: Thick Whois Policy Development Process (PDP)10 minutes) > The GNSO Council initiated a PDP at its meeting on 14 March. However, considering other circumstances, the GNSO Council is of the view that the next steps in this PDP (formation of a drafting team to develop a charter) is not timely and that it may be preferable to delay until the .COM negotiations have been completed. This motion provides for that delay. > > The BC argued that the motion would muddy the waters with regard to the RAA negotiations, but we were unconvincing. How does this conflate with the .com contract now? When did that happen? > > With regard to: > > Item 5: GNSO Council comment on .COM contract renewal (10 minutes) > In its announcement on the .COM contract renewal dated 27 March 2012 (http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm) ICANN states that the question of transitioning a large existing registry to thick WHOIS has been recognised by the GNSO as raising operational and other issues that require further discussion and consideration (http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm). > So Council discussions are being cited as the rationale for the fact that the 2012 .COM contract contains no obligations on the registry operator to switch to a thick WHOIS format. Considering the debate that went on at Council level on this issue, the Council may deem this to be a misrepresentation of the truth. If so, the Council may then wish to draft a statement outlining this and direct the Chair to send it to the Board. > > How did this get on the agenda? Are we responding in a fit of pique? It seems we are leapfrogging the public comment period. > > Cheers, > > John Berard > Founder > Credible Context > 58 West Portal Avenue, #291 > San Francisco, CA 94127 > m: 415.845.4388

1 0

A point on the Motion to Request an Issue Report on the protection of names and acronyms of IGOs
by john＠crediblecontext.com 07 Apr '12

07 Apr '12

Thomas, I did not want to react quickly to your motion, but now that I have had a chance to think about, I do have a request. Is there a chance you'd consider recalling the motion? Here's why I ask. I think your motion is premature and counter to the sentiment in the letter Stephane sent to the Board on behalf of the GNSO Council with regard to the request from the IGO lawyers. You will note that the letter spoke to the proper path of policy and that, if the Board were to get advice from the GAC that affected policy, it would then be referred to the Council. This motion, even by it merely being posted to our agenda, let alone going to a vote, makes us look schizophrenic. I don't want to look schizophrenic. I would like to let our initial plan progress. I would be more than happy to talk about it. Cheers, John Berard Founder Credible Context 58 West Portal Avenue, #291 San Francisco, CA 94127 m: 415.845.4388 -------- Original Message -------- Subject: [council] Motion to Request an Issue Report on the protection of names and acronyms of IGOs From: Thomas Rickert <rickert(a)anwaelte.de> Date: Wed, April 04, 2012 11:02 am To: "<council(a)gnso.icann.org> GNSO" <council(a)gnso.icann.org> Stéphane, all,please find below a motion that I had already announced in Costa Rica. Best regards, Thomas Motion to Request an Issue Report on the protection of names and acronyms of IGOs Whereas the ICANN Board has granted protection for the Red Cross and the IOC until the GNSO and GAC develop policy advice based on the global interest in its resolution of June 20, 2011 (2011.06.20.01); Whereas a drafting team of the GNSO Council was established to look at additional top and second level protections for the IOC and the Red Cross/Red Crescent movement in the current round of new gTLDs in response to a GAC proposal based on the June 20, 2011 Board resolution; Whereas the drafting team is limited to reviewing only top and second level protections for the IOC and Red Cross/Red Crescent Movement; Whereas the GNSO Council and the GAC were asked in the letter dated March 11, 2012 by the ICANN Board to provide policy advice in response to a letter dated December 13, 2011 from intergovernmental Organizations on the protection of additional International Governmental Organization (IGO) names and acronyms both on the top and second level; Whereas it is possible that more organizations might request special protection both at the top as well as at the second level for the first and subsequent rounds of applications for generic TLDs. THEREFORE BE IT: Resolved, the GNSO Council requests an Issue Report on protection of names and acronyms of IGOs at the top and second level for all new gTLDs. *** Thomas Rickert, Attorney at Law Managing Partner, Schollmeyer & Rickert Rechtsanwaltsgesellschaft mbH www.anwaelte.de Director Names & Numbers, eco Association of the German Internet Industry www.eco.de

2 1

Updated GNSO COuncil agenda 12 April 2012 at 11:00 UTC
by Glen de Saint Géry 06 Apr '12

06 Apr '12

Dear All, Please find the updated Agenda for GNSO Council Meeting – 12 April 2012 at 11:00 UTC. http://gnso.icann.org/meetings/agenda-council-12apr12-en.htm There is no consent agenda and an item has been added to: Item 9: Any Other Business (5 minutes) 9.1 Announcement on the new GNSO website (Marika Konings) Thank you. Kind regards, Glen Please consult the Wiki agenda for the latest updates: https://community.icann.org/display/gnsocouncilmeetings/Agenda+12+April+2012 The motions before Council are posted on page: https://community.icann.org/display/gnsocouncilmeetings/Motions+12+April+20… This agenda was established according to the GNSO Council Operating Procedures approved 22 September 2011 for the GNSO Council and updated. http://gnso.icann.org/council/gnso-operating-procedures-16dec11-en.pdf For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Times 11:00 UTC<http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+Meeti…> Coordinated Universal Time 11:00 UTC 04:00 Los Angeles; 07:00 Washington; 12:00 London; 13:00 Paris; 20:00 Tokyo Dial-in numbers will be sent individually to Council members. Councilors should notify the GNSO Secretariat in advance if a dial out call is needed. GNSO Council meeting audiocast http://stream.icann.org:8000/gnso.m3u Item 1: Administrative matters (10 minutes) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Draft Minutes of the GNSO Emergency Meeting 26 March 2012 http://gnso.icann.org/mailing-lists/archives/council/msg12873.html to be approved on 12 April 2012-04-04 Draft Minutes of the GNSO Public meeting 14 March 2012 To be approved on 1.5. GNSO Pending Projects List http://gnso.icann.org/meetings/pending-projects-list.pdf · Review main changes. · Comments and/or questions. Item 2: Consent agenda (5 minutes) A consent agenda item is being added as a standard agenda item to provide for a simplified process to obtain Council approval on specific tasks. • no items on the consent agenda Item 3: Thick Whois Policy Development Process (PDP)10 minutes) The GNSO Council initiated a PDP at its meeting on 14 March. However, considering other circumstances, the GNSO Council is of the view that the next steps in this PDP (formation of a drafting team to develop a charter) is not timely and that it may be preferable to delay until the .COM negotiations have been completed. This motion provides for that delay. Refer to motion 1: https://community.icann.org/display/gnsocouncilmeetings/Motions+12+April+20… 3.2 Reading of the motion (Stéphane van Gelder) 3.3 Discussion 3.3 Vote Item 4: Request an Issue Report on the protection of names and acronyms of IGOs Refer to motions 2 & 3: https://community.icann.org/display/gnsocouncilmeetings/Motions+12+April+20… 4.1 Reading of motion 2 (Thomas Rickert) 4.2 Discussion 4.3 Vote 4.4 Reading of motion 3 (Mary Wong) 4.5 Discussion 4.6 Vote Item 5: GNSO Council comment on .COM contract renewal (10 minutes) In its announcement on the .COM contract renewal dated 27 March 2012 (http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm) ICANN states that the question of transitioning a large existing registry to thick WHOIS has been recognised by the GNSO as raising operational and other issues that require further discussion and consideration (http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm). So Council discussions are being cited as the rationale for the fact that the 2012 .COM contract contains no obligations on the registry operator to switch to a thick WHOIS format. Considering the debate that went on at Council level on this issue, the Council may deem this to be a misrepresentation of the truth. If so, the Council may then wish to draft a statement outlining this and direct the Chair to send it to the Board. 5.1 Discussion 5.2 Next steps Item 6: Uniformity of reporting (10 minutes) In its meeting on 6 October 2011, the GNSO Council resolved to request ‘the ICANN Compliance Department to report on existing systems, to report and track violations and/or complaints; improvements / changes made since the RAPWG Report or foreseen in the near future, and: identify gaps and any improvements that might be desirable but not foreseen at this stage. Further consideration of this Meta Issue, including the recommendations and considerations of the RAP WG in this regard, is deferred pending receipt of such information from the ICANN Compliance Department’. On 18 March, ICANN's Compliance Department submitted its report (see http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-un…). The Council is expected to review the report and discuss possible next steps, including the recommendations and considerations of the RAP WG in this regard. Refer to report: http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-un… 6.1 Discussion 6.2 Next steps Item 7: Update on RAA Final Issue Report and Status of Negotiations (10 minutes) Staff will provide a brief overview of the Final Issue Report on the RAA Amendments and the Status Report on the RAA negotiations, and discuss the next steps for the GNSO Council. 7.1 Update (Margie Milam) 7.2 Discussion Item 8: Update on the new PDP (10 minutes) In December 2011, the ICANN Board adopted, on the recommendation of the GNSO Council, the revised GNSO Policy Development Process. This session is to introduce the revised GNSO PDP and explain its new features in detail. Introduction to Revised Policy Development Process (PDP) http://gnso.icann.org/correspondence/intro-revised-gnso-pdp-14mar12-en.pdf 8.1 Update (Marika Konings) 8.2 Discussion Item 9: Any Other Business (5 minutes) 9.1 Announcement on the new GNSO website (Marika Konings) Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting‟s adjournment. In exceptional circumstances,announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Local time between March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 11:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 04:00 New York/Washington DC, USA (EDT) UTC-5+1DST 07:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 08:00 Montevideo, Uruguay (UYT<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 08:00 London, United Kingdom (BST) UTC+1DST 12:00 Abuja,Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 12:00 Tunis, Tunisia (CET) UTC+1+0DST 12:00 Bonn, Germany (CEST) UTC+1+1DST 13:00 Paris, France (CEST) UTC+1+1DST 13:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 14:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> ) UTC+5+0DST 16:00 Hong Kong, China (HKT ) UTC+8+0DST 19:00 Tokyo, Japan (JST<http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 20:00 Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> ) UTC+12+1DST 23:00 ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of October 2012, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Motion to Request an Issue Report on the protection of names and acronyms of IGOs
by Thomas Rickert 06 Apr '12

06 Apr '12

Stéphane, all, please find below a motion that I had already announced in Costa Rica. Best regards, Thomas Motion to Request an Issue Report on the protection of names and acronyms of IGOs Whereas the ICANN Board has granted protection for the Red Cross and the IOC until the GNSO and GAC develop policy advice based on the global interest in its resolution of June 20, 2011 (2011.06.20.01); Whereas a drafting team of the GNSO Council was established to look at additional top and second level protections for the IOC and the Red Cross/Red Crescent movement in the current round of new gTLDs in response to a GAC proposal based on the June 20, 2011 Board resolution; Whereas the drafting team is limited to reviewing only top and second level protections for the IOC and Red Cross/Red Crescent Movement; Whereas the GNSO Council and the GAC were asked in the letter dated March 11, 2012 by the ICANN Board to provide policy advice in response to a letter dated December 13, 2011 from intergovernmental Organizations on the protection of additional International Governmental Organization (IGO) names and acronyms both on the top and second level; Whereas it is possible that more organizations might request special protection both at the top as well as at the second level for the first and subsequent rounds of applications for generic TLDs. THEREFORE BE IT: Resolved, the GNSO Council requests an Issue Report on protection of names and acronyms of IGOs at the top and second level for all new gTLDs. *** Thomas Rickert, Attorney at Law Managing Partner, Schollmeyer & Rickert Rechtsanwaltsgesellschaft mbH www.anwaelte.de Director Names & Numbers, eco Association of the German Internet Industry www.eco.de

5 5

Draft Agenda for GNSO Council Meeting – 12 April 2012 at 11:00 UTC
by Glen de Saint Géry 06 Apr '12

06 Apr '12

Draft Agenda for GNSO Council Meeting – 12 April 2012 This agenda was established according to the GNSO Council Operating Procedures approved 22 September 2011 for the GNSO Council and updated. http://gnso.icann.org/council/gnso-operating-procedures-16dec11-en.pdf For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Times 11:00 UTC<http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+Meeti…> Coordinated Universal Time 11:00 UTC 04:00 Los Angeles; 07:00 Washington; 12:00 London; 13:00 Paris; 20:00 Tokyo Dial-in numbers will be sent individually to Council members. Councilors should notify the GNSO Secretariat in advance if a dial out call is needed. GNSO Council meeting audiocast http://stream.icann.org:8000/gnso.m3u Item 1: Administrative matters (10 minutes) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Draft Minutes of the GNSO Emergency Meeting 26 March 2012 http://gnso.icann.org/mailing-lists/archives/council/msg12873.html to be approved on 12 April 2012-04-04 Draft Minutes of the GNSO Public meeting 14 March 2012 To be approved on 1.5. GNSO Pending Projects List http://gnso.icann.org/meetings/pending-projects-list.pdf · Review main changes. · Comments and/or questions. Item 2: Consent agenda (5 minutes) A consent agenda item is being added as a standard agenda item to provide for a simplified process to obtain Council approval on specific tasks. Item 3: Thick Whois Policy Development Process (PDP)10 minutes) The GNSO Council initiated a PDP at its meeting on 14 March. However, considering other circumstances, the GNSO Council is of the view that the next steps in this PDP (formation of a drafting team to develop a charter) is not timely and that it may be preferable to delay until the .COM negotiations have been completed. This motion provides for that delay. Refer to motion 1: https://community.icann.org/display/gnsocouncilmeetings/Motions+12+April+20… 3.2 Reading of the motion (Stéphane van Gelder) 3.3 Discussion 3.3 Vote Item 4: Request an Issue Report on the protection of names and acronyms of IGOs Refer to motions 2 & 3: https://community.icann.org/display/gnsocouncilmeetings/Motions+12+April+20… 4.1 Reading of motion 2 (Thomas Rickert) 4.2 Discussion 4.3 Vote 4.4 Reading of motion 3 (Mary Wong) 4.5 Discussion 4.6 Vote Item 5: GNSO Council comment on .COM contract renewal (10 minutes) In its announcement on the .COM contract renewal dated 27 March 2012 (http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm) ICANN states that the question of transitioning a large existing registry to thick WHOIS has been recognised by the GNSO as raising operational and other issues that require further discussion and consideration (http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm). So Council discussions are being cited as the rationale for the fact that the 2012 .COM contract contains no obligations on the registry operator to switch to a thick WHOIS format. Considering the debate that went on at Council level on this issue, the Council may deem this to be a misrepresentation of the truth. If so, the Council may then wish to draft a statement outlining this and direct the Chair to send it to the Board. 5.1 Discussion 5.2 Next steps Item 6: Uniformity of reporting (10 minutes) In its meeting on 6 October 2011, the GNSO Council resolved to request ‘the ICANN Compliance Department to report on existing systems, to report and track violations and/or complaints; improvements / changes made since the RAPWG Report or foreseen in the near future, and: identify gaps and any improvements that might be desirable but not foreseen at this stage. Further consideration of this Meta Issue, including the recommendations and considerations of the RAP WG in this regard, is deferred pending receipt of such information from the ICANN Compliance Department’. On 18 March, ICANN's Compliance Department submitted its report (see http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-un…). The Council is expected to review the report and discuss possible next steps, including the recommendations and considerations of the RAP WG in this regard. Refer to report: http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-un… 6.1 Discussion 6.2 Next steps Item 7: Update on RAA Final Issue Report and Status of Negotiations (10 minutes) Staff will provide a brief overview of the Final Issue Report on the RAA Amendments and the Status Report on the RAA negotiations, and discuss the next steps for the GNSO Council. 7.1 Update (Margie Milam) 7.2 Discussion Item 8: Update on the new PDP (10 minutes) In December 2011, the ICANN Board adopted, on the recommendation of the GNSO Council, the revised GNSO Policy Development Process. This session is to introduce the revised GNSO PDP and explain its new features in detail. Introduction to Revised Policy Development Process (PDP) http://gnso.icann.org/correspondence/intro-revised-gnso-pdp-14mar12-en.pdf 8.1 Update (Marika Konings) 8.2 Discussion Item 9: Any Other Business (5 minutes) Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting‟s adjournment. In exceptional circumstances,announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Local time between March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 11:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 04:00 New York/Washington DC, USA (EDT) UTC-5+1DST 07:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 08:00 Montevideo, Uruguay (UYT<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 08:00 London, United Kingdom (BST) UTC+1DST 12:00 Abuja,Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 12:00 Tunis, Tunisia (CET) UTC+1+0DST 12:00 Bonn, Germany (CEST) UTC+1+1DST 13:00 Paris, France (CEST) UTC+1+1DST 13:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 14:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> ) UTC+5+0DST 16:00 Hong Kong, China (HKT ) UTC+8+0DST 19:00 Tokyo, Japan (JST<http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 20:00 Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> ) UTC+12+1DST 23:00 ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of October 2012, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

2 1

Proposed motion for next council meeting on Best Practices wrt RAP
by Zahid Jamil 05 Apr '12

05 Apr '12

Dear Councillors, I would like to move the following motion for the next meeting: "Motion to create a drafting team to develop the charters for two Working Groups on the Creation of non-binding Best Practices to help Registrars and Registries address the Abusive Registrations of Domain Names Whereas, following the recommendation of the Registration Abuse Policies Working Group, the GNSO Council requested a discussion paper on the creation of non-binding best practices to help registrars and registries address the abusive registrations of domain names in accordance with the Registration Abuse Policies Working Group Final Report; Whereas, ICANN Staff submitted the discussion paper to the GNSO Council on 28 September 2011 (see http://gnso.icann.org/issues/rap/discussion-paper-rap-best-practices-28sep1…); Whereas the GNSO Council discussed the discussion paper at its working session at the ICANN meeting in Dakar and a public workshop was organized; Whereas the GNSO Council identified the issue as a priority topic at its wrap up session at the ICANN meeting in Dakar; Whereas, the discussion paper recommended the creation of two Working Groups, namely one GNSO Working Group to establish the framework for best practices and one Cross-Community Technical Group to propose candidate best practices to address the abusive registration of domain names. NOW THEREFORE, BE IT: Resolved, that the GNSO Council hereby approves the formation of a GNSO drafting team which will be responsible for developing the Charters for the two Working Groups to address the creation of non-binding best practices to help registrars and registries address the Abusive Registrations of Domain Names as identified above; Resolved, the drafting team will consider the discussion paper prepared by ICANN Staff well as the discussions of the GNSO Council on the discussion paper and the public workshops on this topic as part of its deliberations and development of the Charters; Resolved further, that [Name] shall serve as the GNSO Council Liaison for this drafting team." Best regards, Zahid Jamil Barrister-at-law Jamil & Jamil Barristers-at-law 219-221 Central Hotel Annexe Merewether Road, Karachi. Pakistan Cell: +923008238230 Tel: +92 21 5680760 / 5685276 / 5655025 Fax: +92 21 5655026 www.jamilandjamil.com Notice / Disclaimer This message contains confidential information and its contents are being communicated only for the intended recipients . If you are not the intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete it from your system. The contents above may contain/are the intellectual property of Jamil & Jamil, Barristers-at-Law, and constitute privileged information protected by attorney client privilege. The reproduction, publication, use, amendment, modification of any kind whatsoever of any part or parts (including photocopying or storing it in any medium by electronic means whether or not transiently or incidentally or some other use of this communication) without prior written permission and consent of Jamil & Jamil is prohibited. Sent from my iPad

2 2

Hotel Booking Links Now Open for ICANN's 2012 Meetings in Prague and Toronto
by Glen de Saint Géry 04 Apr '12

04 Apr '12

http://www.icann.org/en/news/announcements/announcement-2-03apr12-en.htm Hotel Booking Links Now Open for ICANN's 2012 Meetings in Prague and Toronto 3 April 2012 ICANN recently opened the hotel booking link and conference registration<http://www.registration123.com/ICANN/PR44/> link for its upcoming 44th public meeting to be held 24-29 June 2012 in Prague, Czech Republic at the Hilton Prague Hotel. Additional information about the meeting, as well as ICANN group hotel rates is now available on the Prague Meeting Website<http://prague44.icann.org/>. ICANN's 45th public meeting will be held 14-19 October 2012 in Toronto, Canada at The Westin Harbour Castle Toronto Hotel. ICANN group hotel rates are available. Reservations can now be made through the ICANN Meetings Website<http://meetings.icann.org/icann45>. More information about supporting hotels, transportation, and the meeting agenda for both Prague and Toronto will be posted as it becomes available. ICANN meetings are held three times each year in different regions of the globe to enable attendees from around the world to participate in person. These meetings are free for anyone who wishes to attend, and offer a variety of sessions such as workshops, open forums, and working meetings on the development and implementation of Internet policies. We also offer several tools for remote participation such as streaming live audio and video, chatrooms, and online question boxes. * Make reservations at The Westin Harbour Castle Toronto Hotel<http://meetings.icann.org/icann45> * Make reservations at The Hilton Prague Hotel<http://prague44.icann.org/venue> Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Fwd: [soac-discussion] Globalization Survey Reminder
by Stéphane Van Gelder 04 Apr '12

04 Apr '12

Councillors, FYI. Stéphane Début du message réexpédié : > De : Kurt Pritz <kurt.pritz(a)icann.org> > Objet : [soac-discussion] Globalization Survey Reminder > Date : 3 avril 2012 20:56:00 HAEC > À : "soac-discussion(a)icann.org" <soac-discussion(a)icann.org> > Cc : David Olive <david.olive(a)icann.org>, Robert Hoggarth <robert.hoggarth(a)icann.org>, Jamie Hedlund <jamie.hedlund(a)icann.org> > > Dear ICANN Leader: > > Thank you for communicating the availability of the ICANN Globalization Survey to your community earlier this month. We are getting a fairly good general response from community members. In our experience, reminder notes can improve survey responses; so will you please send out a reminder and encourage all members of your community to review and complete the survey document? > > Responses will be carefully considered and will impact ICANN’s planning efforts going forward. Now is an excellent time to play a role in that planning process. > > Thus far, nearly 500 community members have viewed or started the survey, and approximately 100 (representing all six UN languages and all five ICANN regions) have completed the document. > > Some respondents have advised us thatthey’d like to see the full survey before going to the link so that they can prepare their answers ahead of time. I am attaching a Word Format document of the survey in English that you can forward. The on-line survey is available in all six UN languages. > > The survey link at http://questionpro.com/t/AHB7OZM7Lx will remain open through 22 April 2012. Any personal encouragement you can offer to increase survey completion would be most appreciated. > > Thanks very much for helping promote this effort. We hope that many more members of your community will participate. Call me if I can help. > > Best regards, > > Kurt Pritz

1 0

Draft GNSO Council minutes 26 March 2012
by Glen de Saint Géry 03 Apr '12

03 Apr '12

Dear Councillors, Please find the draft minutes of the GNSO Council meeting held on 26 March 2012. "If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting." on 12 April 2012. " Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

ICANN Nominating Committee Extends Deadline for Statements of Interest to 16 April 2012
by Glen de Saint Géry 02 Apr '12

02 Apr '12

http://www.icann.org/en/news/announcements/announcement-30mar12-en.htm ICANN Nominating Committee Extends Deadline for Statements of Interest to 16 April 2012 30 March 2012 In order to provide additional time for candidates to apply, ICANN's 2012 Nominating Committee (NomCom) has extended the deadline for Statements of Interest until 16 April 2012 at 23:59 UTC. The 2012 NomCom is actively seeking qualified candidates for the following key positions within ICANN: * Three members of the Board of Directors of ICANN * Two At Large Advisory Committee (ALAC) representatives (one each from the European and North American regions) * One member of the Council of the Generic Names Supporting Organization (GNSO) * One member of the Council of the Country-Code Names Supporting Organization (ccNSO) More information about the positions is available at: http://nomcom.icann.org/positions-2012.htm Statements of Interest for the positions described above can be submitted through an on-line application form at http://nomcom.icann.org/apply or by contacting nomcom2012(a)icann.org<mailto:nomcom2012@icann.org>. Applications will be considered in confidence and should be received by 16 April 2012 for full consideration. Selections will be announced by early September 2012. Successful candidates will take up their positions following ICANN's Annual Meeting in October 2012. The 2012 NomCom began its work in October 2011 after the ICANN Annual Meeting in Dakar, Senegal, and has since then organized outreach events in multiple locations. The NomCom holds regular conference calls to plan and follow-up its work. More information regarding the Nominating Committee can be found at: http://nomcom.icann.org/ Candidate recommendations, questions or comments may also be emailed to nomcom2012(a)icann.org<mailto:nomcom2012@icann.org>. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0