September 2012 - council - lists.icann.org

Fwd: Letter from the GNSO on the IRD-WG Final Report
by Stéphane Van Gelder 14 Sep '12

14 Sep '12

Councillors, FYI, as directed in yesterday's meeting. Thanks, Stéphane Début du message réexpédié : > De : Stéphane Van Gelder <stephane.vangelder(a)indom.com> > Objet : Letter from the GNSO on the IRD-WG Final Report > Date : 14 septembre 2012 15:26:24 HAEC > À : Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au>, Steve Crocker <steve(a)shinkuro.com> > Cc : Secretary <secretary(a)icann.org>, Patrik Fältström <paf(a)frobbit.se> > > Bruce, Steve, > > I am writing to you as respectively the GNSO's liaison to the Board and the Chairman of the Board. > > Please find attached a joint SSAC/GNSO letter forwarding you the final report of the internationalized registration data working group (also attached). > > Please share this with the Board. > > Thanks, > > Stéphane Van Gelder > Directeur Général / General manager > INDOM NetNames France > ---------------- > Registry Relations and Strategy Director > NetNames > T: +33 (0)1 48 01 83 51 > F: +22 (0)1 48 01 83 61 > >

1 0

GNSO Council resolutions 13 September 2012
by Glen de Saint Géry 14 Sep '12

14 Sep '12

Dear All, On 13 September 2012 the GNSO Council unanimously passed the following resolutions: Consent agenda: Resolved sending the IRD-WG letter from GNSO Council to ICANN Board. 13 September 2012 To: ICANN Board From: Chair of the GNSO Council and Chair of the SSAC Via: SSAC and GNSO Liaisons to the ICANN Board We hereby forward to you the Final Report of the Internationalized Registration Data Working Group (IRD-WG). The SSAC has approved the report. At its meeting on 27 June 2012 in Prague the GNSO Council passed a motion by which it approved the delivery of the report to the Board. In its motion the Council also agreed to review the recommendations in the Report and to provide to the Board its advice with regard to those recommendations that may have policy implications. As you may recall, on 26 June 2009 the ICANN Board of Directors approved a resolution (2009.06.26.18) requesting that the GNSO and the SSAC, in consultation with staff, convene an IRD-WG to study the feasibility and suitability of introducing display specifications to deal with the internationalization of registration data. In November 2010 the IRD-WG produced an Interim Report requesting community input on several questions relating to possible models for internationalizing Domain Name Registration Data. On 03 October the IRD-WG posted a draft Final Report in the Public Forum for comment for 45 days. After considering the comments received, the attached Final Report is the IRD-WG's response to the Board request regarding the feasibility and suitability of introducing display specifications to deal with the internationalized registration data. The Report contains the following recommendations: 1. To introduce submission and display specifications, ICANN staff should develop, in consultation with the community, a data model for domain registration data. The data model should specify the elements of the registration data, the data flow, and a formal data schema that incorporates the standards that the working group has agreed on for internationalizing various registration data elements. This data model should also include tagging information for language/scripts. 2. The GNSO Council and the SSAC should request a common Issue Report on translation and transliteration of contact information. The Issue Report should consider whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script. It should also consider who should bear the burden and who is in the best position to address these issues. The Issue Report should consider policy questions raised in the IRD-WG Final Report and should also recommend whether to start a policy development process (PDP) to address those questions. 3. ICANN staff should work with the community to identify a Domain Name Registration Data Access Protocol that meets the needs of internationalization, including 2 but not limited to the work products resulting from recommendations 1 and 2, and the requirements enumerated in the IRD-WG Final Report. 4. ICANN should take appropriate steps to require gTLD registries and registrars and persuade ccTLD registries and registrars to support the following standards: · Domain Names - both A-label and U-label forms during both submission and display for all domain names except nameservers; nameserver Names- require Alabel form, and optionally U-label form; · Telephone/fax- ITU-T E.123; Email-RFC 6531; Registration Status- Exact EPP status where applicable; Date and time - in UTC as specified in [RFC3339], with no offset from the zero meridian. The GNSO Council and the SSAC welcome comments from the Board concerning this report. Stéphane Van Gelder Chair, GNSO Council Patrik Fältström Chair, ICANN Security and Stability Advisory Committee Main agenda Resolved to adopt the revised GNSO Operating Procedures incorporating a consent agenda provision and updated voting results table and to adopt a technical change in proxy notification Whereas, the GNSO Council requested the Standing Committee on Improvements Implementation (SCI) on 20 February to formalize the process for a consent agenda with a view to including the consent agenda in the GNSO rules and procedures; Whereas the SCI deliberated on a process for a consent agenda and reached unanimous consensus on a proposed consent agenda provision for inclusion in the GNSO Operating Procedures; Whereas the voting results table included in the GNSO Operating Procedures required updating following the adoption of the revised GNSO Policy Development Process; Whereas the revised GNSO Operating Procedures, including the proposed consent agenda provision as well as the updated voting results table were put out for a minimum 21-day public comment period on 9 July 2012 (see http://www.icann.org/en/news/public-comment/gnso-operating-procedures-2012-…) as required by the ICANN Bylaws; Whereas as a result of the public comment period, no further changes were deemed necessary by the SCI; Whereas the GNSO Council also requested the SCI to review the current procedures in place for proxy voting; Whereas the SCI reviewed the current procedures in place and recommends that no changes are made to the proxy notification procedures in the GNSO Council Operating Procedures but instead requests that staff makes a technical change so that the proxy notification is sent to the GNSO Council list at the same time as it is sent to the Secretariat, which occurs when the form is submitted. RESOLVED The GNSO Council adopts the revised GNSO Operating Procedures including the new consent agenda provision and the updated voting results table (see http://gnso.icann.org/en/council/gnso-operating-procedures-redline-09jul12-…). The GNSO Council instructs ICANN staff to post the new version of the GNSO Operating Procedures (GOP), which becomes effective immediately upon adoption. The GNSO Council requests staff to make a technical change so that the proxy notification is sent to the GNSO Council list at the same time as it is sent to the Secretariat, which occurs when the form is submitted. 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

Fwd: ICANN Finance / Summary and Analysis for FY13 draft Operating Plan and Budget
by Stéphane Van Gelder 14 Sep '12

14 Sep '12

Councillors, FYI. Stéphane Van Gelder Directeur Général / General manager INDOM NetNames France ---------------- Registry Relations and Strategy Director NetNames T: +33 (0)1 48 01 83 51 F: +22 (0)1 48 01 83 61 Début du message réexpédié : > De : "Xavier J. Calvez" <xavier.calvez(a)icann.org> > Objet : ICANN Finance / Summary and Analysis for FY13 draft Operating Plan and Budget > Date : 14 septembre 2012 01:38:29 HAEC > À : "lesley(a)nominet.org.uk" <lesley(a)nominet.org.uk>, Heather <Heather.Dryden(a)ic.gc.ca>, 'Stéphane Van Gelder' <stephane.vangelder(a)indom.com>, "jcurran(a)arin.net" <jcurran(a)arin.net>, 'Louie ' <louie(a)louie.net>, Olivier Crepin-Leblond <ocl(a)gih.com>, Patrik Fältström <patrik(a)frobbit.se>, "junsec(a)wide.ad.jp" <junsec(a)wide.ad.jp>, Steven Metalitz <met(a)msk.com>, Marilyn Cade <marilynscade(a)hotmail.com>, "tonyarholmes(a)btinternet.com" <tonyarholmes(a)btinternet.com>, Robin Gross <robin(a)ipjustice.org>, "dave(a)difference.com.au" <dave(a)difference.com.au>, Alain Berranger <alain.berranger(a)gmail.com>, "matt.serlin(a)markmonitor.com" <matt.serlin(a)markmonitor.com>, "dmaher(a)pir.org" <dmaher(a)pir.org> > Cc : CHERIE STUBBS <cherstubbs(a)aol.com>, KEITH DRAZEK <kdrazek(a)Verisign.com>, CHUCK GOMES <cgomes(a)Verisign.com>, Paul Diaz <pdiaz(a)pir.org>, Karla Valente <karla.valente(a)icann.org>, "Xavier J. Calvez" <xavier.calvez(a)icann.org>, Aba Diakite <aba.diakite(a)icann.org>, Janice Douma Lange <janice.lange(a)icann.org>, Gisella Gruber <Gisella.Gruber(a)icann.org>, "Maya S. Reynolds" <maya.reynolds(a)icann.org> > > To all SO, AC and SG leaders, > > After the posting of the draft Operating Plan and Budget Public Comment responses last May, the ICANN Finance team was asked by several community members to relook at some of those ICANN responses provided as well as complete responses that came to us after 8 June. We do apologize for the delay but here is the link to the Summary and Analysis of the FY13 Ops Plan and Budget Public Comment responses. > You will find the completed summary within the Report of Public Comments (see the attached PDF for responses only). > Thank you again for all your support. > > Sincerely, > Xavier > > Xavier Calvez > ICANN Internet Corporation for Assigned Names and Numbers > > CFO > Office: +1 (310) 301-5838 > Cell: +1 (805) 312-0052 > E-fax: +1 (310) 957-2348 > > 12025 Waterfront Drive, Suite 300 > Los Angeles, CA 90094-2536

1 0

MP3 recording GNSO Council teleconference, Thursday, 13 September 2012
by Glen de Saint Géry 13 Sep '12

13 Sep '12

[To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 13 September, 2012 at: http://audio.icann.org/gnso/gnso-council-20120913-en.mp3 on page http://gnso.icann.org/en/calendar/#sep Happy listening! 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

Consumer Metrics Draft Motion
by john＠crediblecontext.com 13 Sep '12

13 Sep '12

All, Here is the motion I intend to offer for consideration in Toronto. It is short enough and the time long enough that we might even be able to put it on the consent agenda for the meeting. Call me an optimist. Cheers, John Berard Founder Credible Context 58 West Portal Avenue, #291 San Francisco, CA 94127 m: 415.845.4388

1 0

Fwd: GNSO Council Abstention Notification Form [#100]
by Glen de Saint Géry 13 Sep '12

13 Sep '12

FYI Envoyé de mon iPhone Début du message transféré : Expéditeur: ICANN <no-reply(a)wufoo.com<mailto:no-reply@wufoo.com>> Date: 13 septembre 2012 05:34:54 HAEC Destinataire: "gnso.secretariat(a)icann.org<mailto:gnso.secretariat@icann.org>" <gnso.secretariat(a)icann.org<mailto:gnso.secretariat@icann.org>> Objet: GNSO Council Abstention Notification Form [#100] Répondre à: "no-reply(a)wufoo.com<mailto:no-reply@wufoo.com>" <no-reply(a)wufoo.com<mailto:no-reply@wufoo.com>> Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.org<mailto:robin@ipjustice.org> Date Prepared: * Wednesday, September 12, 2012 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Wendy Seltzer is unable to attend the GNSO Council Meeting on 13 September 2012, so Rafik Dammak will hold Wendy's proxy vote for that meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * all Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, September 14, 2012 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * Rafik Dammak

1 0

new gTLD slides for the webinar on batching
by Bruce Tonkin 12 Sep '12

12 Sep '12

Hello All, Here are the slides for the webinar on batching that was presented today. Regards, Bruce Tonkin

1 0

Proposed GNSO Council Agenda & Draft schedule for GNSO weekend working sessions Toronto
by Glen de Saint Géry 12 Sep '12

12 Sep '12

Dear Councillors, Please find the latest updated proposed agenda for the GNSO Council meeting on Thursday, 13 September 2012 with the attached draft schedule for the GNSO weekend working sessions in Toronto. Please let me know if you have any questions. Thank you. Kind regards, Glen Agenda for the GNSO Council Meeting 13 September 2012 http://gnso.icann.org/en/meetings/agenda-council-13sep12-en.htm and on the Wiki https://community.icann.org/display/gnsocouncilmeetings/Agenda+13+September… Council motion https://community.icann.org/display/gnsocouncilmeetings/Motions+13+Septembe… Last Updated: 12 September 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 15:00 UTC<http://tinyurl.com/bojlrbx> http://tinyurl.com/bojlrbx Coordinated Universal Time 15:00 UTC 08:00 Los Angeles; 11:00 Washington; 16:00 London; 17:00 Paris; 00: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: Minutes of the GNSO Council meeting 20 July 2012<http://gnso.icann.org/en/meetings/minutes-council-20jul12-en.htm> approved on 22 August 2012. 1.5. GNSO Pending Projects List http://gnso.icann.org/meetings/pending-projects-list.pdf * Review main changes. * Comments and/or questions. Item 2: Motion to adopt the revised GNSO Operating Procedures incorporating a consent agenda provision and updated voting results table and to adopt a technical change in proxy notification (5 minutes)<https://community.icann.org/display/gnsocouncilmeetings/Motions+13+Septembe…> Following the Council's request, the Standing Committee on Improvements Implementation (SCI) has worked on a process for formalising the consent agenda, updated the voting results table and reviewed the current procedures for proxy voting. These are now being presented for Council approval. 2.1 Update<http://gnso.icann.org/en/issues/rap/comments-rap-uniformity-of-reporting-30…> from SCI Chair (Wolf-Ulrich Knoben) 2.2 Discussion. 2.3 Vote. Item 3: 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. 3.1 Approve proposed IRD-WG letter from GNSO Council to ICANN Board<http://gnso.icann.org/en/correspondence/van-gelder-faltstrom-to-icann-board…>. Item 4: RAP recommendation on Uniformity of Reporting 10 minutes) At its meeting on 6 October, the GNSO Council requested the ICANN Compliance Department to report on existing systems to report and track violations and/or complaints; improvements made since the RAPWG Report or foreseen in the near future, and: indentify gaps and any improvements that might be desirable but not foreseen at this stage. The ICANN Compliance Team submitted its report on 18 March and presented it to the GNSO Council at its meeting on 12 April. Refer to the report http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-un… The Council must now decide what next steps to take, if any. 4.1 Update<http://gnso.icann.org/en/issues/rap/comments-rap-uniformity-of-reporting-30…> from Mikey O'Connor. 4.2 Discussion. 4.3 Nest steps. Item 5: Whois Review Team Final Report (10 minutes) At its July 20, 2012 meeting, the Council created a small group to draft a letter in response to ICANN Board resolved #2012.06.23.26 (see Board resolution (http://www.icann.org/en/groups/board/documents/resolutions-23jun12-en.htm#5). The August 31, 2012 deadline set by the Board for receiving input proved too short for the Council, and on August 30, 2012 GNSO Chair Stéphane Van Gelder sent Chairman of the ICANN Board Steve Crocker and Interim ICANN CEO Akram Attalah a letter<http://gnso.icann.org/en/node/33821> informing them that the Council would hopefully be providing further input very soon. A draft has been proposed by the group. The Council must now decide whether to send this draft as-is or not. 5.1 Update from group (Brian Winterfeldt) 5. 2 Discussion 5. 3 Next steps. Item 6: Fake Renewal Notices (10 minutes) The GNSO Council requested that a small group prepare a request for information concerning Fake Renewal Notices for the Registrar Stakeholder Group to help inform its deliberations on the Registration Abuse Policies Working Group (RAP WG) Recommendation on Fake Renewal Notices (#2). Once the drafting team submitted its report to the GNSO Council and the comment period was completed, the GNSO Council requested the Drafting Team to review the comments received, update the report if deemed appropriate and report back accordingly. The DT has reviewed the comments received and submitted its updated report to the GNSO Council on 21 June 2012 (see http://gnso.icann.org/issues/frn/fake-renewal-notices-updated-report-20jun1…) and the DT Chair presented this report to the Council at the July 20 meeting. At that meeting, the Council opted to have further consultations with the Registrar Stakeholder Group to find out what solutions the Registrars can offer to deal with bad actors and return to the Council with proposals for options, or solutions, or next steps on this issue. This agenda item is an update on those consultations. 6.1 Update<http://gnso.icann.org/en/issues/frn/cole-to-gnso-council-11sep12-en.pdf> from RrSG (Mason Cole) 6.2 Discussion 6.3 Next steps Item 7: Final Issue Report on Protection of International Organizations (10 minutes) The Preliminary Issue Report on the protection of international organization names requested by the GNSO Council on 12 April was published and a public comment forum was opened on 4 June. http://gnso.icann.org/issues/intl-org-names-prelim-issue-report-04jun12-en.… The GNSO Drafting Team is evaluating possible recommendations to protect the Red Cross and IOC names at the second level and staff has now published the Final Issue Report, since the Public Comment forum has closed. This item is an overview of that report and an examination of possible next steps. 7.1 Update from Staff (Brian Peck) 7.2 Discussion 7.3 Next steps Item 8: Impact of new gTLDs on ICANN's structure (10 minutes) The new gTLD program will have a significant impact on the functioning of ICANN and its structure. The Board has called for an in-depth community discussion to identify early the corresponding challenges and possible evolutions. A call has been put out for the community to share a one-pager on this topic to gather preliminary views and help prepare a dedicated session in Toronto. The GNSO Council has expressed a desire to respond to this call and a small group has been created to draft a response. Although the Board has called for a response by September 10, this is not a hard deadline so the Council will now consider whether to approve the proposed response. 8.1 Update on draft response<http://gnso.icann.org/en/drafts/van-gelder-to-de-la-chapelle-13sep12-en.pdf> (Thomas Rickert) 8.2 Discussion 8.3 Call to approve sending response to the Board Item 9: Overview of schedule for Toronto (10 minutes) As usual, work is ongoing on preparing the GNSO's work schedule for the upcoming ICANN international meeting. This includes the GNSO's weekend working sessions and Wednesday's Open Council Meeting. 9.1 Update on Toronto agenda (Wolf-Ulrich Knoben) 9.2 Discussion and review of any amendments to agenda Item 10: Toronto GAC High Level Meeting (15 minutes) The GAC is organizing a High Level Meeting on October 15 in Toronto. The agenda for this meeting includes an exchange with SO/AC leadership. Following a clarification request by the GNSO leadership, the GAC leadership has given the following explanation on its expectations for the meeting: "I would recommend preparation of Qs and lining up speakers in advance. I trust that the GNSO leadership will work with the GAC, as well as my Canadian colleagues, to find a balance between the differing cultures of the GNSO, and senior officials and politicians unfamiliar with the ICANN environment, to have a positive and productive exchange to reinforce and improve the multi-stakeholder model." The Council should therefore plan for this meeting and discuss possible questions it may want to raise. 10.1 Introduction and overview of meeting (Stéphane Van Gelder) 10.2 Discussion Item11: Consumer Metrics Advice Letter to the ICANN Board (10 minutes) The advice letter was drafted in response to an ICANN Board resolution asking for definitions and metrics that will be used to evaluate the gTLD expansion program in a post-launch review required under the Affirmation of Commitments<http://www.icann.org/en/documents/affirmation-of-commitments-30sep09-en.htm> [1]<http://gnso.icann.org/en/meetings/agenda-council-13sep12-en.htm#footer-note>. Since the AOC did not define the terms or measures of competition, consumer trust and consumer choice, the ICANN Board resolved in December 2010 (ICANN Board resolution<http://www.icann.org/en/minutes/resolutions-10dec10-en.htm#6>) to request advice from the ALAC<http://www.atlarge.icann.org/correspondence/statement-cci-final-advice-08se…>, GAC, GNSO and ccNSO on establishing the definition, measures, and three year targets for those measures, for competition, consumer trust and consumer choice. After nearly a year of WG deliberation, public sessions or updates at the Dakar, Costa Rica, and Prague meetings, and a review of public comments submitted by the community, the Consumer Metric WG submitted its final version of the Advice Letter to the GNSO Council on 17 August 2012 for its consideration. http://gnso.icann.org/en/issues/cctc/cctc-final-advice-letter-17aug12-en.pdf http://gnso.icann.org/en/issues/cctc/cctc-next-steps-17aug12-en.pdf Upon the GNSO Council's deliberation and acceptance, the Advice Letter will be sent to the ICANN Board for their consideration. 11.1 Update from John Berard (WG Liaison) and Berry Cobb (Staff). 11.2 Discussion. 11.3 Next steps. Item 12: Management of work (10 minutes) Recent discussions on the Council list have raised concerns about the volume of documents published prior to an ICANN meeting and how these can best be managed by the volunteer community that makes up the GNSO Council as it struggles to read a substantial amount of reports and other documents in order to better inform its own decision making processes with regards to policy. 12.1 Discussion Item 13: 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 15:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 08:00 New York/Washington DC, USA (EDT) UTC-5+1DST 11:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 12:00 Montevideo, Uruguay (UYT<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 12:00 London, United Kingdom (BST) UTC+1DST 16:00 Abuja,Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 16:00 Tunis, Tunisia (CET) UTC+1+0DST 16:00 Bonn, Germany (CEST) UTC+1+1DST 17:00 Paris, France (CEST) UTC+1+1DST 17:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 18:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html>) UTC+5+0DST 20:00 Beijing/Hong Kong, China (HKT) UTC+8+0DST 23:00 Tokyo, Japan (JST<http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 00:00 Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html>) UTC+12+0DST 03:00 next day ---------------------------------------------------------------------------- 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 and http://tinyurl.com/bojlrbx ________________________________ [1]<http://gnso.icann.org/en/meetings/agenda-council-13sep12-en.htm#note> Affirmation of Commitments: http://www.icann.org/en/documents/affirmation-of-commitments-30sep09-en.htm 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

Updates GNSO Council agenda 13 September 2012
by Glen de Saint Géry 12 Sep '12

12 Sep '12

Dear Councillors, The GNSO Council agenda posted at http://gnso.icann.org/en/meetings/agenda-council-13sep12-en.htm and on the Wiki https://community.icann.org/display/gnsocouncilmeetings/Agenda+13+September… has been updated with the following links: Item 2: Motion to adopt the revised GNSO Operating Procedures incorporating a consent agenda provision and updated voting results table and to adopt a technical change in proxy notification (5 minutes) https://community.icann.org/display/gnsocouncilmeetings/Motions+13+Septembe… Item 6: Fake Renewal Notices (10 minutes) The GNSO Council requested that a small group prepare a request for information concerning Fake Renewal Notices for the Registrar Stakeholder Group to help inform its deliberations on the Registration Abuse Policies Working Group (RAP WG) Recommendation on Fake Renewal Notices (#2). 6.1 Update from RrSG (Mason Cole) http://gnso.icann.org/en/issues/frn/cole-to-gnso-council-11sep12-en.pdf Item 8: Impact of new gTLDs on ICANN's structure (10 minutes) The new gTLD program will have a significant impact on the functioning of ICANN and its structure. The Board has called for an in-depth community discussion to identify early the corresponding challenges and possible evolutions. 8.1 Update on draft response (Thomas Rickert) http://gnso.icann.org/en/drafts/van-gelder-to-de-la-chapelle-13sep12-en.pdf Please let me know if you have any questions. Thank you so very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

FW: GNSO Council Abstention Notification Form [#99]
by Glen de Saint Géry 12 Sep '12

12 Sep '12

fyi Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org From: ICANN [mailto:no-reply@wufoo.com] Sent: mercredi 12 septembre 2012 21:46 To: gnso.secretariat(a)icann.org Subject: GNSO Council Abstention Notification Form [#99] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.org<mailto:robin@ipjustice.org> Date Prepared: * Wednesday, September 12, 2012 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Wolfgang Kleinwachter is unable to attend the GNSO Council Meeting on 13 September 2012. William Drake will hold Wolf's proxy for the meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * all Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, September 14, 2012 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * William Drake

1 0