- Bc-gnso - lists.icann.org

ALERTS from the Secretariat: Approved July 2012 - June 2015 Strategic Plan Posted
by Benedetta Rossi May 21, 2012

May 21, 2012

Dear BC Members, Please find below an ICANN announcement on the approved 2012-2015 Strategic Plan. Thank you, Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org https://www.icann.org/en/news/announcements/announcement-3-18may12-en.htm Approved July 2012 - June 2015 Strategic Plan Posted 18 May 2012 Based upon the Board Resolutions <https://www.icann.org/en/groups/board/documents/resolutions-06may12-en.htm>resulting from the recent Special Meeting of the Board of Directors held in Amsterdam on 6 May 2012, the adopted 2012-2015 Strategic Plan <https://www.icann.org/en/about/planning/strategic/strategic-plan-2012-2015-…>[PDF, 864 KB] is now posted. 2012-2015 Strategic Plan * English <https://www.icann.org/en/about/planning/strategic/strategic-plan-2012-2015-…> [PDF, 864 KB] * العربية - coming soon * 中文- coming soon * Français - coming soon * Español - coming soon * Русский - coming soon During the Special Meeting of the Board of Directors held in Amsterdam the Board approved the July 2012-June 2015 Strategic Plan, and directed the President and CEO to move forward with the Internationalization survey and community-based operational planning process based on the strategic objectives as set forth in the plan. The aspects of the 2012-2015 Strategic Plan that cover the expansion of ICANN's international presence and engagement efforts are deferred pending further direction from the Board. Rationale for Resolution 2012.05.06.06 To remain accountable to the global Internet community, the Board is taking this action to allow for community input on the further planning for ICANN's international presence and engagement. There has been a community survey on these items, and a paper will be produced that will be the subject of public comment and discussion. In addition, continued work towards these efforts as set forth in the 2011-2014 Strategic Plan is not prudent, therefore those portions of the 2011-2014 Strategic Plan are deferred. After review of these inputs, and as appropriate to respond to inputs, initiatives to expand ICANN's international presence and engagement may be updated within the 2012-2015 Strategic Plan, and included within the 2012-2013 Operating Plan. In order to allow for the 2012-2013 operational planning cycle to proceed, the Board approves the 2012-2015 Strategic Plan. While there will likely be a fiscal impact as a result of this work, the fiscal impact of undertaking the survey and review process is minimal. Further, the deferral of current initiatives within the 2011-2012 Operating Plan regarding the further allocation or reallocation of staff and resources that relate to ICANN's international presence and engagement prior to the Prague Meeting will preserve resources from having to be reallocated as necessary after this review is complete. This action is not expected to have any impact on the security or the stability of the DNS. This version of the Strategic Plan includes extensive community feedback, including a 45-day Public Comment period (10.3.11 – 11.17.11). Many thanks to the Community for its continued support and input. ICANN's Strategic Plan is a three-year rolling, annually updated strategic planning process and feeds in to the larger ICANN planning process as the adopted Strategic Plan guides the development of the FY13 Operating Plan and Budget.

1 0

ALERTS from the Secretariat: Pre-Prague ICANN Policy Update Webinar Invitation
by Benedetta Rossi May 17, 2012

May 17, 2012

Dear BC Members, Please find below an ICANN announcement regarding the Pre-Prague Policy Update Webinar Invitation. If you would like to attend this webinar please follow the instructions in the announcement and RSVP to the GNSO Secretariat to receive the dial in information. Thank you, Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org http://www.icann.org/en/news/announcements/announcement-2-16may12-en.htm Pre-Prague ICANN Policy Update Webinar Invitation 16 May 2012 *In order to participate, please RSVP via email to the GNSO Secretariat** *(***gnso.secretariat(a)gnso.icann.org <mailto:gnso.secretariat@gnso.icann.org>**) to receive the call details.* Whether you plan to participate in the upcoming ICANN meeting in Prague remotely or in person, you're invited to an update on the background and current status of each major policy issue currently under discussion in ICANN. The ICANN Policy Staff will provide a briefing on *Thursday 14 June at 12.00 UTC and Thursday 14 June at 19.00 UTC*, summarizing policy issues across the different ICANN Supporting Organizations, namely the Generic Names Supporting Organization (GNSO), Country Code Names Supporting Organization (ccNSO) and Address Supporting Organization (ASO). Amongst other topics, updates will be provided on: * Inter-Registrar Transfer Policy * WHOIS * RAA Improvements * Consumer Choice, Competition and Innovation * Study Group on Use of Names for Countries and Territories * Framework of Interpretation Working Group for the delegation and re-delegation of ccTLDs * Joint DNS Security and Stability Analysis Working Group * Participation and Engagement activities in Prague In addition, staff will provide a briefing on the ALAC's activities related to current policy development issues of the Supporting Organizations. The two sessions are duplicates, scheduled to accommodate different time zones. Each session, scheduled to run for 90 minutes, will be conducted in English only. The meeting will be run in Adobe Connect with a slide presentation along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may be submitted using the chat function of Adobe Connect. If you are not able to participate in either of the live sessions, the recording of the session will be made available shortly after the meeting. The policy staff is always available to answer any questions that you email to policy-staff(a)icann.org <mailto:policy-staff@icann.org>. In order to participate, please RSVP via email to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org <mailto:gnso.secretariat@gnso.icann.org>) to receive the call details. Please indicate which call you would like to join, Thursday at 13.00 UTC or Thursday at 20.00 UTC (to convert those times into your local time, see: http://www.timeanddate.com/worldclock/fixedform.html) We will send you an e-mail reminder before the event with log-in and dial-in details. Please DO NOT RSVP to any other ICANN staff members e-mail address.

1 0

ALERTS From the Secretariat: Independent Objector for New gTLD Program Selected
by Benedetta Rossi May 16, 2012

May 16, 2012

Dear BC Members, Please find below an ICANN announcement regarding the selection of the Independent Objector for the new gTLD Program. Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org http://www.icann.org/en/news/announcements/announcement-14may12-en.htm Independent Objector for New gTLD Program Selected 14 May 2012 ICANN is delighted to announce that Professor Alain Pellet has agreed to serve as the Independent Objector for the New Generic Top-level domain program. The Independent Objector will act solely in the interests of the public who use the global Internet. Professor Pellet's credentials and experience are an ideal fit for this key role. He is a highly regarded professor and practitioner of law and has represented governments as Counsel and Advocate in the International Court of Justice in many significant and well-known cases. He is widely published and holds several significant honors. ICANN's formal search for an Independent Objector began with the posting of a Request for Proposals in November 2011. We also advertised, utilized the services of a global recruiting firm and welcomed word-of-mouth recommendations. Numerous candidates were interviewed and considered throughout the search process. Acting solely in the best interests of global Internet users, the Independent Objector may lodge Limited Public Interest and Community objections in cases where no other objection is made to an application that the Independent Objector deems to be objectionable. More information about the Independent Objector role can be found in the new gTLD Applicant Guidebook <http://newgtlds.icann.org/en/applicants/agb>. More information about Professor Pellet, including his curriculum vitae, can be found at: http://www.alainpellet.eu <http://www.alainpellet.eu/> We are honored by Professor's Pellet's agreement to participate in ICANN and this program. <http://gnso.icann.org>

1 0

ALERTS from the Secretariat: Ratification of Global Policy Proposal for Post Exhaustion IPv4 Allocation Mechanisms by the IANA
by Benedetta Rossi May 16, 2012

May 16, 2012

Dear BC Members, Please find below an ICANN announcement on the Ratification of Global Policy Proposal for Post IPv4 Allocation Mechanisms by the IANA. Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org http://www.icann.org/en/news/announcements/announcement-15may12-en.htm Ratification of Global Policy Proposal for Post Exhaustion IPv4 Allocation Mechanisms by the IANA 15 May 2012 The ICANN Board has ratified the Global Policy Proposal for Post Exhaustion IPv4 Allocation Mechanisms by the IANA as sent by the Address Supporting Organization (ASO) Council to the ICANN Board on 13 March 2012. The proposal was posted for public comment from 14 March 2012 through 4 April 2012, during which time no comments were submitted. The Global Policy allows the Regional Internet Registries to return IPv4 address space to an IANA-managed pool from which equal parts will be allocated to all five RIRs in a deterministic manner on a regular schedule, once triggered. http://www.icann.org/en/news/in-focus/global-addressing/allocation-ipv4-pos…. ICANN staff will be taking all necessary steps to implement the Global Policy.

1 0

.COM Renewal Comments
by Elisa Cooper May 15, 2012

May 15, 2012

BC Members, Per the Member's Call last Friday, please find below brief comments regarding the renewal of the .COM contract: The BC supports VeriSign's continued operation of the .COM Registry. However, we strongly urge ICANN to take this opportunity to require the maintenance of Thick Whois by VeriSign for the .COM Registry. We believe that requiring all Registries to comply with Thick Whois is an important first step in improving Whois. The BC has previously stated the importance of timely, unrestricted, and public access to complete and accurate Whois information. While the BC recognizes that Thick Whois does not improve accuracy, it does address the requirements for timely, unrestricted and public access of Whois information. The BC expects that other ongoing ICANN projects will improve Whois accuracy and responses by privacy/proxy services to relay / reveal requests. In particular, we expect improvements to result from: - current negotiations on the Registrar Accreditation Agreement (RAA); - implementation of SAC 051 recommendations (link<http://www.icann.org/en/news/public-comment/sac-051-draft-roadmap-18feb12-e…>); and - policy development indicated by results of five pending Whois studies (link<%20http:/gnso.icann.org/issues/whois/studies%20>). Rapporteur for this Discussion Draft: Elisa Cooper These comments are due Thursday, May 17th. The comments are in line with our stated position, however, please let me know if you have any additions, or edits as soon as possible. Best, Elisa Elisa Cooper Director of Product Marketing MarkMonitor 208 389 5779 PH

7 10

Preparation for Prague Meeting
by Benedetta Rossi May 15, 2012

May 15, 2012

Dear BC Members, In preparation for the upcoming ICANN meeting in Prague, can you please provide me with the following information: 1. Arrival/Departure dates 2. Hotel Name 3. Extra guests 4. Contact details whilst traveling Thank you ever so much, -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org

2 1

Clarification
by Michael D. Palage May 14, 2012

May 14, 2012

Hello All, I am a little confused by the wording "[w]e believe that requiring all Registries to comply with Thick Whois." How does one "comply" with thick whois? Registries such as .NAME, .TEL and now .CAT "operate" their registry by collecting Thick whois data, but comply with national privacy laws in how they provide access to that data set. Having worked with a large number of new gTLD applicants with a variety of business models, I think the BC needs to be a little more careful in how we word our statements so they scale in a future world of thousands of new gTLDs. Therefore, I would recommend that we change the phrase "comply with" to "have direct access to." Best regards, Michael

2 2

Re: [bc-gnso] RE: .COM Renewal Comments
by martinsutton＠hsbc.com May 14, 2012

May 14, 2012

Elisa, I'm supportive of these comments. Thank you, Martin Martin Sutton Manager, Group Fraud Risk and Intelligence Ph: ++44 (0)20 7991 8074 Mob: ++44 (0)777 4556680 Sent from my BlackBerry ********************************* HSBC Holdings plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England number 617987 ********************************* ----- Original Message ----- From: Elisa Cooper [Elisa.Cooper(a)markmonitor.com] Sent: 14/05/2012 16:17 GMT To: "'Bc GNSO list ' (bc-gnso(a)icann.org)" <bc-gnso(a)icann.org> Subject: [bc-gnso] RE: .COM Renewal Comments With minor updates highlighted in blue from Marilyn Cade: The BC supports VeriSign's continued operation of the .COM Registry. However, we strongly urge ICANN to take this opportunity to require the maintenance of Thick Whois by VeriSign for the .COM Registry. We believe that requiring all Registries to comply with Thick Whois is an important first step in improving Whois. The BC has previously stated the importance of timely, unrestricted, and public access to complete and accurate Whois information. While the BC recognizes that Thick Whois does not directly improve accuracy, it does contribute to addressing the need for timely, unrestricted and public access of Whois information. The BC expects that other ongoing ICANN projects will improve Whois accuracy and responses by privacy/proxy services to relay/reveal requests. In particular, we expect improvements to result from: - current negotiations on the Registrar Accreditation Agreement (RAA); - implementation of SAC 051 recommendations (http://www.icann.org/en/news/public-comment/sac-051-draft-roadmap-18feb12-e…) ; and - policy development indicated by results of five pending Whois studies (http://gnso.icann.org/issues/whois/studies) Rapporteur for this Discussion Draft: Elisa Cooper Best, Elisa Elisa Cooper Director of Product Marketing MarkMonitor 208 389-5779 PH From: Elisa Cooper Sent: Sunday, May 13, 2012 8:23 PM To: 'Bc GNSO list ' (bc-gnso(a)icann.org) Subject: .COM Renewal Comments BC Members, Per the Member's Call last Friday, please find below brief comments regarding the renewal of the .COM contract: The BC supports VeriSign's continued operation of the .COM Registry. However, we strongly urge ICANN to take this opportunity to require the maintenance of Thick Whois by VeriSign for the .COM Registry. We believe that requiring all Registries to comply with Thick Whois is an important first step in improving Whois. The BC has previously stated the importance of timely, unrestricted, and public access to complete and accurate Whois information. While the BC recognizes that Thick Whois does not improve accuracy, it does address the requirements for timely, unrestricted and public access of Whois information. The BC expects that other ongoing ICANN projects will improve Whois accuracy and responses by privacy/proxy services to relay / reveal requests. In particular, we expect improvements to result from: - current negotiations on the Registrar Accreditation Agreement (RAA); - implementation of SAC 051 recommendations (link<http://www.icann.org/en/news/public-comment/sac-051-draft-roadmap-18feb12-e…>); and - policy development indicated by results of five pending Whois studies (link<%20http:/gnso.icann.org/issues/whois/studies%20>). Rapporteur for this Discussion Draft: Elisa Cooper These comments are due Thursday, May 17th. The comments are in line with our stated position, however, please let me know if you have any additions, or edits as soon as possible. Best, Elisa Elisa Cooper Director of Product Marketing MarkMonitor 208 389 5779 PH ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This E-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return E-mail. Internet communications cannot be guaranteed to be timely secure, error or virus-free. The sender does not accept liability for any errors or omissions.

1 0

ALERTS From the Secretariat: Period of 10-20 May 2012: Public Comment Periods Approaching Closing Date
by Benedetta Rossi May 11, 2012

May 11, 2012

Dear BC Members, Please find below an ICANN announcement regarding Public Comment Periods Approaching closing date. Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org http://www.icann.org/en/news/announcements/announcement-10may12-en.htm Period of 10-20 May 2012: Public Comment Periods Approaching Closing Date 10 May 2012 The Following Public Comment periods are approaching their *Comment or Reply Period Close* dates, *May 10-20 2012*. As a member of the ICANN community, your timely feedback is critical to our accountability and transparency efforts. For your convenience, we have included direct links below to comments that will soon close. During the Reply period for Public Comments, participants should only address previous comments submitted and new posts concerning the topic should not be introduced. When constructing Replies, contributors are asked to cite the original poster's name, comment date, and any particular text that is pertinent. Please note that comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once that period ends. For more information please refer to the ICANN Public Comments page at: http://www.icann.org/en/news/public-comment *Title* *Comment Period Close Date [UTC Time]* *Reply Period Close Date [UTC Time]* Security, Stability & Resiliency of the DNS Review Team (SSR RT) - Draft Report <http://www.icann.org/en/news/public-comment/ssrt-draft-report-15mar12-en.htm> Extended to 15 April 2012 [23:59] Extended to 14 May 2012 [23:59] Fake Renewal Notices Report <http://www.icann.org/en/news/public-comment/fake-renewal-notices-report-21m…> 20 April 2012 [23:59] 11 May 2012 [23:59] .com Registry Agreement Renewal <http://www.icann.org/en/news/public-comment/com-renewal-27mar12-en.htm> 26 April 2012 [23:59] 17 May 2012 [23:59] .post Agreement Amendment <http://www.icann.org/en/news/public-comment/post-amendment-2012-09apr12-en.…> 9 May 2012 [23:59] 30 May 2012 [23:59] <http://gnso.icann.org>

1 0

ALERTS From the Secretariat: Updated GNSO Council Agenda 10 May 2012 at 15:00 UTC
by Benedetta Rossi May 9, 2012

May 9, 2012

Dear BC Members, Please find below the updated GNSO Council Agenda for the meeting taking place on 10 May 2012 Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org Dear All, Please find the updated agenda for the GNSO Council Meeting 10 May 2012 at 15:00 UTC.*(*Other times may be found at:** http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+meeti… <http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+meeti…>) Three items have been added to _Item 9: Any Other Business (15 minutes)_ 9.1 Discussion on recent Board announcement to alter ICANN meeting Friday schedule. 9.2 Discussion on ALAC proposal for ICANN Academy. 9.3 URS update in draft budget - should the Council write to the Board to request that it be involved? (intro from Staff). Please let me know if you have any questions. Thank you. Kind regards, Glen The agenda is posted on page http://gnso.icann.org/meetings/agenda-council-10may12-en.htm the Wiki agenda (for the latest updates) is posted on page: https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Meetin… The motion before Council is posted on page: https://community.icann.org/display/gnsocouncilmeetings/Motions+10+May+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 <https://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://www.timeanddate.com/worldclock/fixedtime.html?msg=Council+meting+&is…> 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: Draft Minutes of the GNSO Council meeting 12 April 2012 approved on 30 April 2012. http://gnso.icann.org/meetings/minutes-council-12apr12-en.htm <http://gnso.icann.org/meetings/minutes-council-12apr12-en.htm> 1.5. GNSO Pending Projects List http://gnso.icann.org/meetings/pending-projects-list.pdf <https://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: Best practices for addressing abusive registrations (15 minutes)_*__ Following the recommendation of the Registration Abuse Policies (RAP) 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. The discussion paper recommended the creation of two Working Groups, one to establish the framework for best practices and one to propose candidate best practices to address the abusive registration of domain names. The Council must now consider a motion to set up a drafting team to create the charter for these groups. Refer to motion 1[https://community.icann.org/display/gnsocouncilmeetings/Motions+10+May+20… 3.2 Reading of the motion (Zahid Jamil) 3.3 Discussion 3.3 Vote *_Item 4: 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 <https://gnso.icann.org/correspondence/intro-revised-gnso-pdp-14mar12-en.pdf> 4.1 Update (Marika Konings) 4.2 Discussion *_Item 5: International Olympics Committee /Red Cross Names Drafting Team (IOC/RC DT) (15 minutes)_*__ On September 14, 2011, the GAC submitted a proposal to the GNSO Council to protect IOC and RC marks at the top and second level for all new gTLDs. At its March 26 meeting, the GNSO Council approved the IOC/RC DT's recommendations (see resolution passed by the Council here http://gnso.icann.org/resolutions#20120326-1 <https://gnso.icann.org/resolutions#20120326-1>). However, these recommendations did not contain any proposals with regard to the protection of these marks at the second level. On April 10, 2012, the Board established the New gTLD Program Committee and granted it all of the powers of the Board to exercise Board-level authority for any and all issues that may arise relating to the New gTLD Program. The Committee met on 10 April 2012 and resolved not to update the New gTLD Applicant Guidebook at this time (see http://www.icann.org/en/groups/board/documents/prelim-report-new-gtld-10apr…) On April 12, 2012, the GNSO Council approved a motion requesting an Issue Report on protection of names and acronyms of IGOs at the top and second level for all new gTLDs. In the light of both the Board decision and the decision by the Council to request an Issue Report on the protection of names and acronyms at the top and second level for all new gTLDs , this discussion item aims to determine whether the Council should (i) continue the IOC/RC DT to recommend a complete response to the GAC proposal at the second level, (ii) disband the IOC/RC DT and prepare a response to the GAC proposal on its own, (iii) disband the IOC/RC DT until the potential new PDP progresses and delay any response to the GAC, or (iv) whether new instructions should be given to the DT. 5.1 Discussion 5.2 Next Steps *_Item 6: Update on the Joint Supporting Organisations/Advisory Committee on New gTLD Applicant Support Working Group( JAS WG) (15 minutes)_*__ This item aims to provide the Council with a status update on the JAS WG so that next steps for the group can be determined. 6.1 WG update from Staff (Kurt Pritz) 6.2 Discussion 6.3 Next steps *_Item 7: Synthesis of WHOIS Service Requirements - The WHOIS Access recommendation (5 minutes)_*__ The WHOIS access recommendation was considered as part of the consent agenda at the Council's 16 February 2012 meeting. At that meeting, the ISP constituency requested that the proposal to end this work be removed from the consent agenda and considered as part of the GNSO's main agenda. A further suggestion was suggested that constituency/stakeholder members work with Staff to identify a path forward and that the topic be further discussed at the Costa Rica meetings. This agenda item is to determine what next steps, if any, should be planned for this project item. 7.1 Update from Staff/ISP (Marika Konings, Wolf-Ulrich Knoben) 7.2 Discussion 7.3 Next steps *_Item 8: Update on the Internationalised Registration Data WG (10 minutes)_*__ The IRD submitted its final report to the GNSO Council and SSAC on March 3, 2012 for review and approval. However, SSAC has recommend some substantial changes and more work may now be needed by the IRD before its final report can be considered. This agenda item is to provide an update on these latest developments in the IRD WG's work to the Council. 8.1 WG update from Staff (Steve Sheng) 8.2 Discussion *_Item 9: Any Other Business (15 minutes)_*__ 9.1 Discussion on recent Board announcement to alter ICANN meeting Friday schedule. 9.2 Discussion on ALAC proposal for ICANN Academy. 9.3 URS update in draft budget - should the Council write to the Board to request that it be involved? (intro from Staff). *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: 1. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. 2. 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. 3. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. 4. 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. 5. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. 6. 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. 7. 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. 8. 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. 9. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, 10. 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. 11. 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. 12. 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 <https://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. 1. Initiate a Policy Development Process (PDP); 2. Approve a PDP recommendation; 3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; 4. 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 ---------------------------------------------------------------------------- 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 <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