May 2012 - Bc-gnso - lists.icann.org

Policy calendar for 5-Mar-2012 BC member call
by Steve DelBianco Sept. 10, 2012

Sept. 10, 2012

Here is the latest BC policy calendar, for use during our 5-Mar-2012 BC member call. Channel 1. BC participation in ICANN Public Comment process: ICANN Public Comment page is here<http://www.icann.org/en/news/public-comment> 1. FY 13 budget framework (reply comments close 26-Mar) Chris Chaplow is managing BC comments. Filed initial comments here<http://forum.icann.org/lists/op-budget-fy2013/msg00003.html>. 2. Defensive Applications for new gTLDs (reply<http://forum.icann.org/lists/newgtlds-defensive-applications/> comments close 20-Mar) BC filed comments here<http://forum.icann.org/lists/newgtlds-defensive-applications/msg00022.html>. 3. Bylaw changes on GNSO policy development process ( reply comments close 23-Mar) 4. Draft roadmap to implement SAC 51 protocol for WHOIS (initial comments close 18-Mar) 5. IDN Variant Issues Project plan (initial comments close 18-Mar) 6. WHOIS Policy Review Team (AoC) Draft Report (comments close 18-Mar) Elisa Cooper is managing BC comments. 7. Initial Report on Universal Acceptance of IDN TLDs (initial comments close 23-Mar) 8. IRTP-B PDP on WHOIS status messages (initial comments close 25-Mar) 9. Interim report on ccTLD re-delegation requests (initial comments close 30-Mar) 10. Draft Advice on definitions & targets for Consumer Trust, Choice, and Competition in new gTLD program (initial comments close 3-Apr) (link to advice<http://gnso.icann.org/drafts/cctc-draft-advice-letter-22feb12-en.pdf> ) 11. Status report on protecting Red Cross & Olympics at top-level and 2nd-level (link<http://www.icann.org/en/news/announcements/announcement-2-02mar12-en.htm>) (initial comment opens 2-Mar) Note: BC members are encouraged to submit individual / company comments. The BC selects topics on which to submit official positions based on member interest. --- Channel 2. Support for discussion and votes of our representatives on GNSO Council John Berard and Zahid Jamil, BC Councilors GNSO Project Status available here<http://gnso.icann.org/meetings/pending-projects-list.pdf> Agenda for Council meeting in Costa Rica has not yet been published. (link<http://gnso.icann.org/meetings/agenda-council-14mar12-en.htm>) John and Zahid can update us on possible motions, including something on UDRP providers. --- Channel 3. Supporting discussion and voting on policy matters before the Commercial Stakeholders Group (CSG) Elisa Cooper, CSG Liaison, and Marilyn Cade (alternate) Messages for meeting with ICANN Board on 13-Mar --- Channel 4. BC statements and responses during public meetings (outreach events, public forum, etc.) Affirmation review team for Whois (Susan Kawaguchi, Lynn Goodendorf, Bill Smith) Affirmation review team for SSR (Security, Stability, & Resilience) (Jeff Brueggeman) Remaining implementation work for gTLD expansion plan, incl BC requests for specific improvements (here<http://forum.icann.org/lists/newgtlds-defensive-applications/msg00022.html>)

2 7

FY13 Operating Plan and Budget Comment
by Chris Chaplow June 11, 2012

June 11, 2012

Dear BC Members, Please find attached comments that I have submitted on the FY13 Operating Plan and Budget. We anticipate that the BC and the CSG will submit more detailed comments in the reply round which opens tomorrow until the 15th June. I have asked a lot of clarification questions and drawn on material from our Framework Budget submission as I dont think it was adequately addressed at that time. I think we should focus on the 25 individual project comments in the reply round. Best regards, Chris Chaplow Managing Director Andalucia.com S.L. Avenida del Carmen 9 Ed. Puertosol, Puerto Deportivo 1ª Planta, Oficina 30 Estepona, 29680 Malaga, Spain Tel: + (34) 952 897 865 Fax: + (34) 952 897 874 E-mail: <mailto:chris@andalucia.com> chris(a)andalucia.com Web: <http://www.andalucia.com/> www.andalucia.com Information about Andalucia, Spain.

3 6

Draft GNSO Council Agenda 7 June 2012
by Benedetta Rossi May 31, 2012

May 31, 2012

Dear BC Members, Please find below the draft GNSO Council Agenda for the call taking place on June 7th 2012 at 8 pm UTC. 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 draft agenda for the GNSO Council Meeting 7 June 2012 which is also posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Agenda+07+June+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 20:00 UTC <http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+Meeti…>_ http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+Meeti… <http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+Meeti…> Coordinated Universal Time 20:00 UTC 13:00 Los Angeles; 16:00 Washington; 21:00 London; 22:00 Paris; 05:00 Tokyo next day 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 10 May 2012 approved on 28 May 2012. http://gnso.icann.org/meetings/minutes-council-10may12-en.htm 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. 2.1GAC/GNSO Issues Related to International Olympic Committee (IOC) & Red Cross (RC) Names Drafting Team. Approve sending of note to GAC. *_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. This motion was deferred from the May 10, 2012 meeting. Refer to motion 1 https://community.icann.org/display/gnsocouncilmeetings/Motions+10+May+2012 3.1 Reading of the motion (Zahid Jamil) 3.2 Discussion 3.3 Vote*__* *_Item 4: _**_WHOIS Access recommendation (10 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. A motion has been made to consider next steps. Refer to motion 2 https://community.icann.org/display/gnsocouncilmeetings/Motions+07+June+2012 4.1 Reading of the motion (Wolf-Ulrich Knoben) 4.2 Discussion 4.3 Vote *__* *_Item 5: Outreach Task Force (OTF) (10 minutes)_* The Council has set up a drafting team to develop a charter for an OTF. A motion to approve that charter did not pass when made at the Dakar meeting. A second motion was made at the December 15, 2011 meeting and was not seconded, which meant it was not considered. In Costa Rica, the Council decided to form a group to discuss options on how to proceed. This is an update item on the work of that group. 5.1 Update from (X Y) 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 RrSG to help inform its deliberations on the RAP WG Recommendation on Fake Renewal Notices (#2). The drafting team submitted its report <http://gnso.icann.org/issues/frn/fake-renewal-notices-report-06mar12-en.pdf> to the GNSO Council on 6 March. Following a presentation of the report to the GNSO Council at the ICANN Meeting in Costa Rica, the GNSO Council decided to put the report out for public comment. A public comment forum was opened (see http://www.icann.org/en/news/public-comment/fake-renewal-notices-report-21m…) and has now closed. The Council is now expected to consider next steps. 6.1 Public comment forum submissions overview (Marika Konings) Report of Public Comments on Fake Renewal Notices <http://www.icann.org/en/news/public-comment/report-comments-fake-renewal-no…> 6.2 Discussion 6.3 Next steps *_Item 7: Uniformity of Reporting _**_(10 minutes) _* *__* To help inform its consideration of the RAPWG Recommendation on Uniformity of Reporting, 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: identify gaps and any improvements that might be desirable but not foreseen at this stage. The ICANN Compliance Team submitted its report <http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-un…> on 18 March and presented it to the GNSO Council at its meeting on 12 April. ICANN Staff also provided a background presentation on the RAP WG Recommendation (see https://gnso.icann.org/node/30809) The GNSO Council is now expected to consider next steps, if any. 7.1 Discussion 7.2 Next steps *__* *_Item 8:_**_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. This was discussed at the May 10, 2012 Council meeting but as Kurt was unable to attend, the Council felt another discussion point was needed on this subject. Also, a number of questions were asked by the Council during its previous meeting and it was felt that it would be useful to get responses from Kurt to them. 8.1 WG update from Staff, and answers to Council questions (Kurt Pritz) 8.2 Discussion 8.3 Next steps *__* *_Item 9: _**_Update on the Internationalised Registration Data (IRD) Working Group (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. 9.1 WG update from Staff <https://gnso.icann.org/correspondence/status-update-ird-wg-final-report-sli…> (Steve Sheng) 9.2 Discussion *_Item 10: _**_UDRP Domain Locking WG (5 minutes)_* As per the GNSO WG Guidelines, the Chairs of a WG need to be confirmed by the GNSO Council. The Council may wish to note that Michele Neylon (Proposed Chair) and Alan Greenberg (Proposed Vice-Chair) were selected with unanimous support from the Working Group. 10.1 WG update from Staff (Marika Konings) 10.2 Council approval of proposed WG Chair and VC. *_Item 11: _**_Consumer Metrics WG (5 minutes)_* The Consumer Metrics WG has prepared a draft advice document for discussion in Prague in order to finalise the document before sending it to the Council. As part of that process, the WG would like to solicit the GAC's input. A letter http://gnso.icann.org/issues/cci-draft-letter-gnso-to-gac-23may12-en.pdf has been drafted for the Council Chair to send to the GAC Chair. The Council must decide whether to send that letter. 11.1 WG update from Council Liaison (Rosemary Sinclair) 11.2 Council approval of sending proposed letter. *_Item 12: 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 20:00 ---------------------------------------------------------------------------- California, USA (PDT <http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 13:00 New York/Washington DC, USA (EDT) UTC-5+1DST 16:00 – next day Buenos Aires, Argentina (ART <http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 17:00 Montevideo, Uruguay (UYT <http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 17:00 London, United Kingdom (BST) UTC+1DST 21:00 Abuja,Nigeria (WAT <http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 21:00 Tunis, Tunisia (CET) UTC+1+0DST 21:00 Bonn, Germany (CEST) UTC+1+1DST 22:00 Paris, France (CEST) UTC+1+1DST 22:00 Ramat Hasharon, Israel(IST <http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 23:00 Karachi, Pakistan (PKT <http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html>) UTC+5+0DST 01:00 – next day Beijing/Hong Kong, China _(HKT_ ) UTC+8+0DST 04:00 – next day Tokyo, Japan (JST <http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 05:00 – next day Wellington, New Zealand (NZDT <http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html>) UTC+12+0DST 08: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 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

Expanding the Internet domain space - Google Anouncement
by Chris Chaplow May 31, 2012

May 31, 2012

In 2016, its estimated that almost half of the worlds population will be online, yet <http://www.verisigninc.com/assets/domain-name-brief-march2012.pdf> nearly 50 percent of the websites we visit are found in the .com <http://en.wikipedia.org/wiki/Top-level_domain> top-level domain(TLD), which was among the first TLDs created in 1984. Despite the great opportunities the web has enabled for people around the world, there is still a lingering question about the diversity of the domain space (given that the number of generic TLDs has only increased by 14 in the last 28 years). In 2008, ICANN announced a program to expand the number of generic TLDs (think .com, .org, .edu), developed through its bottom-up, multi-stakeholder process, in which we participate. Given this expansion process, we decided to submit applications for new TLDs, which generally fall into four categories: · Our trademarks, like .google · Domains related to our core business, like .docs · Domains that will improve user experience, such as .youtube, which can increase the ease with which YouTube channels and genres can be identified · Domains we think have interesting and creative potential, such as .lol We want to make the introduction of new generic TLDs a good experience for web users and site owners. So we will: · Make security and abuse prevention a high priority · Work with all ICANN-accredited registrars · Work with brand owners to develop sensible rights protection mechanisms that build upon ICANNs requirements Were just beginning to explore this potential source of innovation on the web, and we are curious to see how these proposed new TLDs will fare in the existing TLD environment. By opening up more choices for Internet domain names, we hope people will find options for more diverseand perhaps shortersignposts in cyberspace. Posted by Vint Cerf, Chief Internet Evangelist <http://googleblog.blogspot.com.es/2012/05/expanding-internet-domain-space.h tml> http://googleblog.blogspot.com.es/2012/05/expanding-internet-domain-space.ht ml Chris Chaplow Managing Director Andalucia.com S.L. Avenida del Carmen 9 Ed. Puertosol, Puerto Deportivo 1ª Planta, Oficina 30 Estepona, 29680 Malaga, Spain Tel: + (34) 952 897 865 Fax: + (34) 952 897 874 E-mail: <mailto:chris@andalucia.com> chris(a)andalucia.com Web: <http://www.andalucia.com/> www.andalucia.com Information about Andalucia, Spain.

1 0

ALERTS: Notice of Extension of ICANN Comment Period: ICANN Draft FY13 Operating Plan and Budget until 8 June 2012, with the reply period closing on June 15th 2012
by Benedetta Rossi May 31, 2012

May 31, 2012

Dear BC Members, Please find below the notice of extension od ICANN's Comment Period for the ICANN draft FY13 Op Plan & Budget until 8th of June 2012, with a reply closing date on June 15th 2012. 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-29may12-en.htm Notice of Extension of ICANN Comment Period: ICANN Draft FY13 Operating Plan and Budget 29 May 2012 * Français <http://www.icann.org/fr/news/announcements/announcement-01may12-fr.htm> * Español <http://www.icann.org/es/news/announcements/announcement-01may12-es.htm> * Русский <http://www.icann.org/ru/news/announcements/announcement-01may12-ru.htm> * 简体中文 <http://www.icann.org/zh/news/announcements/announcement-01may12-zh.htm> * العربية <http://www.icann.org/ar/news/announcements/announcement-01may12-ar.htm> http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm In response to comments made by community members regarding time required to complete quantitative comments on the ICANN draft FY13 Operating Plan and Budget, ICANN has extended this public comment period until 8 June 2012, with the reply period closing on June 15th 2012. 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

ALERTS from the Secretariat: The TLD Application System, or TAS, has now closed.
by Benedetta Rossi May 31, 2012

May 31, 2012

Dear BC Members, Please find below the ICANN announcement regarding the the TAS closing. 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-30may12-en.htm New gTLD Update by Akram Atallah, COO 30 May 2012 The TLD Application System, or TAS, has now closed. As of 23.00 GMT/UTC today, with one hour remaining before the system closed, just over 1900 applications had been submitted in TAS. We will reconcile all payments and submitted applications, and will release the final numbers when the applied-for domain names are published. As we said yesterday, our target date for publishing the list of applied-for domain names is 13 June 2012. We thank all applicants and the ICANN community for their support throughout the application process.

1 0

ALERTS From the Secretariat: REMINDER: WHOIS Technical Requirements Survey Webinar 1 June 2012, at 13:00 & 20:00 UTC
by Benedetta Rossi May 31, 2012

May 31, 2012

Dear BC Members, Please find below the ICANN announcement regarding the upcoming WHOIS Technical Requirements Survey Webinar, taking place tomorrow June 1st 2012 @ 1 pm UTC & 8 pm UTC. If you wish to participate in this webinar, please follow the RSVP instructions marked in the announcement below. Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org *WHOIS Technical Requirements **Survey Webinar*** 23 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.* The Generic Names Supporting Organization (GNSO) Council's WHOIS Survey Working Group (WSWG) requests community input on a draft WHOIS Technical Requirements Survey, to assess the content of the survey before releasing it for public solicitation. In parallel with the Public Comment period, the Working Group is hosting two webinar sessions to brief the community on the background of this effort and to solicit input from experts on technical requirements for a new WHOIS protocol, in particular people knowledgeable about technical aspects of WHOIS who can help assess if the survey asks the right questions and in the right style to elicit useful and clear technical feedback. The Working Group seeks specific suggestions on changes to language and questions that will make it clearer for experts to complete. Members of the Working Group will provide a briefing on *Friday 1 June at 13.00 UTC **and**Friday 1 June at 20.00 UTC*, summarizing the purpose of this effort and reviewing the work called for in the Working Group's charter. *13:00 UTC click on this link*: *http://tinyurl.com/85s8fou* *20:00 UTC click on this link* *http://tinyurl.com/7qydxhm* The webinars will also review the sections of the survey as they relate to the proposed technical requirements outlined in the GNSO WHOIS Service Requirement Report - http://gnso.icann.org/issues/whois/whois-service-requirements-final-report-… that was prepared by Staff at the GNSO Council's request in July 2010. The two sessions are duplicates, scheduled to accommodate different time zones. Each session, scheduled to run for 60 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 the 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, Friday at 13.00 UTC or Friday 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. 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

ALERTS from the Secretariat: WHOIS Technical Requirements Survey - Draft - Request for community input
by Benedetta Rossi May 31, 2012

May 31, 2012

Dear BC Members, Please find below the ICANN announcement regarding the WHOIS Technical Requirements Survey Draft. The comment period opened yesterday (May 30th 2012) and will close on June 20th 2012, as per the announcement below. Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org *Public Comment Box Link:* http://www.icann.org/en/news/public-comment/draft-whois-requirements-survey… WHOIS Technical Requirements Survey - Draft Comment/Reply Periods ^(*) Important Information Links *Comment Open:* 30 May 2012 *Comment Close:* 20 June 2012 *Close Time (UTC):* 23:59 Public Comment Announcement <http://www.icann.org/en/news/announcements/announcement-30may12-en.htm> *Reply Open:* 20 June 2012 To Submit Your Comments (Forum) <mailto:draft-whois-requirements-survey@icann.org> *Reply Close:* 16 July 2012 View Comments Submitted <http://forum.icann.org/lists/draft-whois-requirements-survey/> *Close Time (UTC):* 23:59 Report of Public Comments Brief Overview *Originating Organization:* GNSO Council – WHOIS Survey Working Group *Categories/Tags:* Policy Processes *Purpose (Brief):* The Generic Names Supporting Organization (GNSO) Council's WHOIS Survey Working Group (WSWG) requests community input on the draft WHOIS Technical Requirements Survey. The Working Group is soliciting input from experts on technical requirements for a new WHOIS protocol, in particular people knowledgeable about technical aspects of WHOIS who can help assess if the survey asks the right questions and in the right style to elicit technical feedback. The Working Group seeks specific suggestions on changes to language and questions that will make it clearer for experts to complete. *Current Status:* This Public Comment solicitation represents an opportunity for the community to share perspectives on the proposed draft WHOIS Technical Requirements Survey. In parallel, the WSWG will conduct a Webinar to promote the survey and solicit additional feedback. *Next Steps:* The WSWG will consider the comments received as part of their deliberations and creation of the final version of the WHOIS Requirements Survey. Upon submission to the GNSO Council, the survey will be announced and released for community participation. The survey will be available for 30 days. Afterwards, the WSWG will compile, analyze and report on the survey results to produce a final report outlining possible WHOIS Technical requirements. *Staff Contact:* Liz Gasster *Email:* policy.staff(a)icann.org <mailto:policy.staff@icann.org?subject=More%20information%20on%20the%20WHOIS%20Technical%20Requirements%20Survey%20-%20Draft%20public%20comment%20period> Detailed Information *Section I: Description, Explanation, and Purpose* The WHOIS Survey Working Group produced a draft survey of WHOIS Technical Requirements at the request of the GNSO Council Resolution (http://gnso.icann.org/resolutions#20111006-1) The Working Group is seeking community feedback on the draft, which will be considered by GNSO Council and later released to the community for participation in the WHOIS survey. The Survey can be accessed here: http://icann.isoc.ug/whoissurvey/?sid=71483 The Working Group will accept community feedback via the public comment forum. Additionally, users of the survey will see a free-form text dialogue box at the bottom of each section of the survey. Users may use this space to provide specific feedback with respect to the questions loaded for that section. If you use this feature, be sure to include your identity so that we may relate your response to the public comment review process. *Section II: Background* The Working Group aims to draft, implement, and analyze the results of a survey measuring the level of support for various technical requirements outlined in the GNSO WHOIS Service Requirement Report (http://gnso.icann.org/issues/whois/whois-service-requirements-final-report-…, 633 KB]). The WHOIS Survey Working Group will produce a Report to be delivered to the GNSO Council describing the results of the survey and recommendations for next steps for the GNSO Council's consideration concerning the WHOIS service requirements. *Section III: Document and Resource Links* 1.WHOIS Requirements Survey - http://icann.isoc.ug/whoissurvey/?sid=71483 2.WSWG Charter - http://gnso.icann.org/issues/whois/charter-wswg-06oct11-en.pdf[PDF, 476 KB] 3.WSWG Wiki - https://community.icann.org/display/WSDT/WHOIS+Survey+Working+Group+-+Home 4.GNSO WHOIS Service Requirement Report - http://gnso.icann.org/issues/whois/whois-service-requirements-final-report-…, 633 KB] *Section IV: Additional Information* None /(*) 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 this period lapses./

1 0

Motions upcoming GNSO Council Call - June 7th 2012
by Benedetta Rossi May 31, 2012

May 31, 2012

Dear Members, As previously mentioned the Council agenda has not yet been released, but please find below the motions for the call. Once the agenda is released I will forward it to BC Members for your convenience. Thank you, -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org https://community.icann.org/display/gnsocouncilmeetings/Motions+07+June+2012 Motions 07 June 2012 * * Ajouté parde saint gery <https://community.icann.org/display/%7Eglen>, modifié parde saint gery <https://community.icann.org/display/%7Eglen>le mai 31, 2012 (afficher les modifications <https://community.icann.org/pages/diffpages.action?pageId=30345100&original…>)Translate <https://community.icann.org/display/gnsocouncilmeetings/Motions+07+June+201…> * 1. 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 *Made by: Zahid Jamil* *Seconded by: Carlos Aguirre* *Deferred from the 10 May 2012 GNSO Council meeting to the next Council meeting on 7 June 2012, by Yoav Keren on request of the Registrar Stakeholder Group for the reason that the Registrar**Stakeholder Group needed more time to discuss the motion.* 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. 2*Motion to Address Whois Access as Recommended by the Registration Abuse Policies Working Group Made by: Wolf-Ulrich Knoben* *Seconded by: John Berard * Whereas the Registration Abuse Policies (RAP) Working Group submitted its report to the GNSO Council on 29 May 2010 (seehttp://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf) Whereas the GNSO Council reviewed the report and its recommendations and formed an Implementation Drafting Team to draft a proposed approach with regard to the recommendations contained in the Registration Abuse Policies Working Group Final Report; Whereas the Registration Abuse Policies Implementation Drafting Team submitted its proposed response to the GNSO Council on 15 November 2010 (seehttp://gnso.icann.org/correspondence/rap-idt-to-gnso-council-15nov10-en.…) Whereas on 3 February 2011 (seehttp://gnso.icann.org/resolutions/#201102) the GNSO Council requested feedback from ICANN Compliance in relation to WHOIS Access recommendation #2 and a response was received on 23 February 2011 (seehttp://gnso.icann.org/mailing-lists/archives/council/msg10766.html) In addition, a discussion with Compliance Staff was held at the ICANN meeting in San Francisco. Whereas the GNSO Council thanked the ICANN Compliance Department for its feedback in relation to WHOIS Access recommendation #2 and determined that no further work on this recommendation was needed. The GNSO Council welcomed the commitment of the ICANN Compliance Department 'to report on compliance activities and publish data about WHOIS accessibility, on at least an annual basis' (seehttp://gnso.icann.org/mailing-lists/archives/council/msg10766.html) Whereas in response to WHOIS Access recommendation #1, the GNSO Council asked the WHOIS Survey Working Group to consider including the issue of WHOIS Access as part of the survey it has been tasked to develop, and the Working Group informed the GNSO Council on 11 January that 'the issue does not fall within the remit of its current charter and recommends that the item not be included in their upcoming survey'. Whereas the GNSO Council recognizes that the issue of WHOIS access is also covered in the Final Issue Report on the RAA (seehttp://gnso.icann.org/issues/raa/fInal-issue-report-raa-06mar12-en.pdf) THEREFORE BE IT, Resolved, the GNSO Council recommends that the issue of WHOIS access (to ensure that WHOIS data is accessible in an appropriately reliable, enforceable, and consistent fashion) is included in the RAA Policy Development Process when it commences. Resolved, the GNSO Council will review by end of September, 2012, whether the RAA PDP has commenced and included this issue or whether alternative approaches should be pursued.

1 0

Urgent Reminder: WHOIS Policy Review Team Final Report
by Benedetta Rossi May 31, 2012

May 31, 2012

Dear BC Members, Youwill recall that the BC rapporteur for WHOIS submitted comments on the WHOIS Policy Review Team's report (http://forum.icann.org/lists/whois-rt-draft-final-report/msg00018.html) The final report is now posted for public comments, as noted in the announcement below. The BC rapporteur on WHOIS after discussion with the Excomm will announce a process for further BC comments. The BC Chair advises that WHOIS will be a topic of discussion with the Board in its community interaction & during the public forum in Prague and the bc strategy will be a major topic of discussion in the upcoming BC call. -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org WHOIS Policy Review Team Final Report 3 <http://www.icann.org/en/news/announcements/announcement-11may12-en.htm#> 11 May 2012 *Forum Announcement:* Comment Period Opens on *Date:* 11 May 2012 *Categories/Tags:* Reviews/Improvements WHOIS Policy Transparency/Accountability *Purpose (Brief):* The WHOIS Policy Review Team, constituted underICANN's Affirmation of Commitments (AoC) agreement with the U.S. Department of Commerce, submitted its*Final Report and Recommendations* <http://www.icann.org/en/about/aoc-review/whois/final-report-11may12-en.pdf>[PDF, 1.44 MB] to theICANNBoard and this document has been posted for public comment. A redline version comparing the posted draft and final report is available at:http://www.icann.org/en/about/aoc-review/whois/final-report-redline-11ma…, 2.93 MB]. *Public Comment Box Link:* http://www.icann.org/en/news/public-comment/whois-rt-final-report-11may12-e…

1 0

Change of date: BC Members Pre Council Call: Wednesday June 6th @ 11 am EDT
by Benedetta Rossi May 31, 2012

May 31, 2012

Dear BC Members, Due to a variety of conflicts, please note that the upcoming BC Pre Council Members call has now been moved to *Wednesday June 6th at 11 am EDT (3 pm UTC / 5 pm CET)*. The agenda will be posted separately with the dial in details, as we are waiting for the motions and documents for the GNSO Council call to be posted in order to finalize the agenda for the preparation call with members. In the meantime please let me know if you require a dial out, and if you have any questions. Thank you, -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org

1 0

Re: [bc-gnso] Upcoming Pre Council BC Members Call - Tuesday June 5th 2012 @ 11 am EDT
by Marilyn Cade May 29, 2012

May 29, 2012

I agree that members here will want to attend. let me assess call options. Sent via BlackBerry by AT&T -----Original Message----- From: Phil Corwin <psc(a)vlaw-dc.com> Date: Tue, 29 May 2012 19:30:08 To: <bc-secretariat(a)icann.org>; <bc-gnso(a)icann.org> Subject: RE: [bc-gnso] Upcoming Pre Council BC Members Call - Tuesday June 5th 2012 @ 11 am EDT Bene-- This event is taking place next Tuesday in Dc, and some BC members may want to attend. Note that check-in starts at 11:30 am - The Congressional Internet Caucus Advisory Committee cordially invites you to . What Role Should the UN Have in Governing the Internet? A Briefing on the UN's Internet Governance Initiative Date: Tuesday, June 5, 2012 Time: 12:00 pm - 2:00 pm. Program begins promptly at 12:00 pm, check-in starts at 11:30 am. (Box lunch will be served) Location: Rayburn House Office Building, B-369 RSVP: rsvp(a)netcaucus.org <mailto:rsvp@netcaucus.org?subject=Internet%20Governance%20Event%20RSVP> or via phone to 202-407-8829 (Note: Registration is complimentary.) Additional Information: Click Here <http://www.netcaucus.org/events/2012/internetgovernance/> Panelists * Fiona Alexander - Associate Administrator, National Telecommunications & Information Administration (NTIA) [Bio <http://www.netcaucus.org/biography/fiona-alexander.shtml> ] * Richard Beaird - Senior Deputy United States Coordinator, International Communications and Information Policy, U.S. Department of State [Bio <http://www.netcaucus.org/biography/richard-beaird.shtml> ] * Amb. David Gross - Partner, Wiley Rein LLP [Bio <http://www.netcaucus.org/biography/david-gross.shtml> ] * Commissioner Robert McDowell - Federal Communications Commission (FCC) [Bio <http://www.netcaucus.org/biography/robert-mcdowell.shtml> ] * Sally Wentworth - Senior Manager for Public Policy, Internet Society (ISOC) [Bio <http://www.netcaucus.org/biography/sally-wentworth.shtml> ] Additional Panelists Will Be Confirmed The Internet has played a historic and integral role as an outlet for free expression and economic growth. A gathering of United Nations (UN) diplomats overseas has recently raised concerns among some about a potential takeover of the Internet by foreign powers, with others claiming such concerns are unfounded. The International Telecommunication Union (ITU), a branch of the UN whose 193 member states also includes the U.S., is hosting a Working Group meeting on June 20-22, 2012 in Geneva, Switzerland. The purpose of the conference is to seek consensus for an updating of the last set of international telecom regulations, also known as ITRs, which were issued in 1988. This panel briefing provides an important opportunity for a timely and informative panel discussion for Congressional Members and Staff about upcoming major developments at the UN/ITU that could significantly affect the governance of the Internet. The Geneva conference is part of a series of meetings to be held in advance of a December conference in Dubai, known as the World Conference on International Telecommunications (WCIT). The ramifications of Internet governance are enormous. We have assembled a distinguished panel of experts and government officials to discuss this important and timely issue. This briefing is of interest to policymakers and stakeholders working Internet and international technology policy issues. As the briefing will be held weeks prior to a major ITU council meeting, we strongly encourage your attendance and participation. For the latest news and developments with the Congressional Internet Caucus Advisory Committee <http://www.netcaucus.org/> , please follow us on Twitter <http://twitter.com/#!/netcaucusac> , Google+ <https://plus.google.com/103498997342005618277/> and Facebook <http://www.facebook.com/cicac> . This widely attended educational briefing is hosted by the Congressional Internet Caucus Advisory Committee (ICAC), part of a 501 (c)(3) charitable organization. Congressional staff and members of the press welcome. The ICAC is a private sector organization comprised of public interest groups, trade associations, non-profits, and corporations. More information on the ICAC is available at www.netcaucus.org <http://www.netcaucus.org/> . Congressional Internet Caucus Advisory Committee 1634 I Street NW - Washington, DC 20006 www.NetCaucus.org <http://www.NetCaucus.org> Find us on Facebook <http://www.facebook.com/cicac> , Twitter <http://twitter.com/#!/netcaucusac> & Google+ <https://plus.google.com/103498997342005618277/> Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey From: owner-bc-gnso(a)icann.org [mailto:owner-bc-gnso@icann.org] On Behalf Of Benedetta Rossi Sent: Tuesday, May 29, 2012 3:02 PM To: bc - GNSO list Subject: [bc-gnso] Upcoming Pre Council BC Members Call - Tuesday June 5th 2012 @ 11 am EDT Dear BC Members, Please save the date for the upcoming BC Members Pre Council Call taking place on Tuesday June 5th 2012 @ 11 am EDT (3 pm UTC / 5 pm CET). Dial in details and agenda will follow. Thank you, -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org <http://www.bizconst.org> bc-secretariat(a)icann.org <mailto:bc-secretariat@icann.org> ---------------- No virus found in this message. Checked by AVG - www.avg.com <http://www.avg.com> Version: 2012.0.2176 / Virus Database: 2425/5031 - Release Date: 05/29/12

1 0

Upcoming Pre Council BC Members Call - Tuesday June 5th 2012 @ 11 am EDT
by Benedetta Rossi May 29, 2012

May 29, 2012

Dear BC Members, Please save the date for the upcoming BC Members Pre Council Call taking place on *Tuesday June 5th 2012 @ 11 am EDT (3 pm UTC / 5 pm CET). * Dial in details and agenda will follow. Thank you, -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org

2 1

Re: [bc-gnso] FY13 Operating Plan and Budget Comment
by Marilyn Cade May 25, 2012

May 25, 2012

I do appreciate the points you are making. It is also strange to me that the detail re comms is lacking. Sent via BlackBerry by AT&T -----Original Message----- From: Gabriela Szlak <gabrielaszlak(a)gmail.com> Date: Fri, 25 May 2012 18:55:30 To: <marilynscade(a)hotmail.com> Cc: <chris(a)andalucia.com>; <bc-gnso(a)icann.org>; <bc-secretariat(a)icann.org> Subject: Re: [bc-gnso] FY13 Operating Plan and Budget Comment Thank you Chris, I agree with Marilyn: As one of the two fellows you are referring to, I am grateful the BC supports the fellowship program and agree to support small business participants from developing countries. >From my experience, most SMEs from my region are unaware of the work ICANN does. In that sense, as we have been discussing, I believe that the BC interest to support the fellowship program, must come together with outreach targeted activities. I will be happy to discuss more on that. G. Gabriela Szlak www.einstituto.org <http://www.einstituto.org> www.estudiorosz.com <http://www.estudiorosz.com> www.gabrielaszlak.com.ar <http://www.gabrielaszlak.com.ar> 2012/5/25 Marilyn Cade <marilynscade(a)hotmail.com <mailto:marilynscade@hotmail.com> > Thanks for doing this,Chris. I understand from the CSG Budget Group call, which you chair [ISPCP, IPC, BC} that it would be useful to have members have a high level understanding on the broader categories, so that we can have a sense of BC priorities. I did want to ask though, about the lack of detail in the budget, such as the inability to find the Fellowship Program as a detailed item; or the communications budget; totals for salary/benefits for staff, etc. Were those not detailed in the Operating Plan and Budget? I recognize that the Fellowship Program has had limited contribution to the BC specifically, except in two cases, but it is a program that the BC supports, and has interest in strengthening how it does contribute to supporting more small business participants from developing countries. ---------------- From: chris(a)andalucia.com <mailto:chris@andalucia.com> To: bc-gnso(a)icann.org <mailto:bc-gnso@icann.org> CC: bc-secretariat(a)icann.org <mailto:bc-secretariat@icann.org> Subject: [bc-gnso] FY13 Operating Plan and Budget Comment Date: Fri, 25 May 2012 00:54:52 +0200 Dear BC Members, Please find attached comments that I have submitted on the FY13 Operating Plan and Budget. We anticipate that the BC and the CSG will submit more detailed comments in the 'reply round' which opens tomorrow until the 15th June. I have asked a lot of clarification questions and drawn on material from our Framework Budget submission as I don't think it was adequately addressed at that time. I think we should focus on the 25 individual project comments in the reply round. Best regards, Chris Chaplow Managing Director Andalucia.com S.L. Avenida del Carmen 9 Ed. Puertosol, Puerto Deportivo 1ª Planta, Oficina 30 Estepona, 29680 Malaga, Spain Tel: + (34) 952 897 865 Fax: + (34) 952 897 874 E-mail: chris(a)andalucia.com <mailto:chris@andalucia.com> Web: www.andalucia.com <http://www.andalucia.com/> Information about Andalucia, Spain.

1 0

RE: ICANN DNS L-Root announcements
by Baskin, James F (Jim) May 25, 2012

May 25, 2012

BC Members, All L-Root instances are anycast. Here are the details from Joe Abley's response to my query. Jim > All L-Root instances mentioned in the two press releases are anycast deployments of the L-Root server. > The L-Root instance referred to in the April 4 announcement by RU-CENTER is in Moscow, Russia. > The L-Root instances referred to in the May announcement by Hostmaster are all in Ukraine. > You can see an accurate list of all locations where L-Root is deployed at <http://www.root-servers.org/>. There are 100+ locations live today. From: Baskin, James F (Jim) Sent: Monday, May 21, 2012 3:17 PM To: 'bc-gnso(a)icann.org' Subject: ICANN DNS L-Root announcements On a BC call about a month ago, I mentioned a question I had about a new instance of the ICANN L-Root that was mentioned in an ICANN announcement. I did some research and determined that the Russian server mentioned in the April 5 ICANN News Alert is a standard Anycast instance, and not an item that needs any special attention from the ICANN community. Since the April 5 Alert there have been two other similar ICANN news items - one announcing 14 new L-Root instances implemented in Brazil and another regarding L-Root instances in the Ukraine. The news item about Brazil specifically identified those servers as Anycast instances. Just to clarify that all of the mentioned L-Root instances mentioned are Anycast-based, I sent a note to Joe Abley, ICANN's Director of DNS Operations, last week seeking confirmation. As soon as I hear back from him, I will pass the confirmation along to the BC list. Jim Baskin

1 0

RE: [bc-gnso] New GNSO website live
by Jimson Olufuye May 24, 2012

May 24, 2012

1 0

New GNSO website live
by Chris Chaplow May 24, 2012

May 24, 2012

Dear BC Members, The new GNSO website is now live. It has left the old 1998 look and come into the modern world in a content System called Drupal. gnso.icann.org It is the product of a lot of work by a team as Ken explains below that included two BC members myself and Berry. The origins were the GNSO improvements CCT work team which was the first work I took part in for the BC. The design look was later created by Cheryl Gatward who creates the BC brochures. Congratulations to all. Best regards, Chris Chaplow Managing Director Andalucia.com S.L. Avenida del Carmen 9 Ed. Puertosol, Puerto Deportivo 1ª Planta, Oficina 30 Estepona, 29680 Malaga, Spain Tel: + (34) 952 897 865 Fax: + (34) 952 897 874 E-mail: <mailto:chris@andalucia.com> chris(a)andalucia.com Web: <http://www.andalucia.com/> www.andalucia.com Information about Andalucia, Spain. I would like to add my own personal congratulations to the entire team. Having been intimately involved in the early design phases of this project (with Scott Pinzon and Chris Chaplow) and now seeing it come alive so magnificently is gratifying to say the least! Thanks to everyone, especially Berry and the Web-Admin team, for having faith in the original concept and following it through to fruition! I know that it required an extraordinary effort to push this project into the end-zone, but the proof of success is now demonstrable at: http://gnso.icann.org. Well Done! J Ken Bour

2 1

ALERTS from the Secretariat: WHOIS Technical Requirements Survey Webinar 1 June 2012, at 13:00 & 20:00 UTC
by Benedetta Rossi May 24, 2012

May 24, 2012

Dear BC Members, Please find below an announcement regarding the WHOIS Technical Requirements Survey Webinar. Please follow instructions provided on the announcement below to participate. Thank you, Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org *WHOIS Technical Requirements **Survey Webinar*** 23 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.* The Generic Names Supporting Organization (GNSO) Council's WHOIS Survey Working Group (WSWG) requests community input on a draft WHOIS Technical Requirements Survey, to assess the content of the survey before releasing it for public solicitation. In parallel with the Public Comment period, the Working Group is hosting two webinar sessions to brief the community on the background of this effort and to solicit input from experts on technical requirements for a new WHOIS protocol, in particular people knowledgeable about technical aspects of WHOIS who can help assess if the survey asks the right questions and in the right style to elicit useful and clear technical feedback. The Working Group seeks specific suggestions on changes to language and questions that will make it clearer for experts to complete. Members of the Working Group will provide a briefing on *Friday 1 June at 13.00 UTC **and**Friday 1 June at 20.00 UTC*, summarizing the purpose of this effort and reviewing the work called for in the Working Group's charter. *13:00 UTC click on this link*: *http://tinyurl.com/85s8fou* *20:00 UTC click on this link* *http://tinyurl.com/7qydxhm* The webinars will also review the sections of the survey as they relate to the proposed technical requirements outlined in the GNSO WHOIS Service Requirement Report - http://gnso.icann.org/issues/whois/whois-service-requirements-final-report-… that was prepared by Staff at the GNSO Council's request in July 2010. The two sessions are duplicates, scheduled to accommodate different time zones. Each session, scheduled to run for 60 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 the 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, Friday at 13.00 UTC or Friday 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: ICANN POLICY UPDATE | Volume 12, Issue 4 - May 2012
by Benedetta Rossi May 22, 2012

May 22, 2012

Dear BC Members, Please find below ICANN's Policy Update. 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/resources/policy/update/update-may12-en.htm ICANN POLICY UPDATE | Volume 12, Issue 4 -- May 2012 1 May 2012 *PDF Version <http://www.icann.org/en/resources/policy/update/update-may12-en.pdf>*[680 KB] *http://www.icann.org/en/topics/policy/* CONTENTS: Across ICANN 1. *New Remote Participation Records Set at ICANN 43 <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#1>* 2. *Issues Currently Open for Public Comment <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#2>* ccNSO 3. *Curaçao, Palestinian Territory and Sint Maarten Join ccNSO <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#3>* 4. *First Look at ccNSO Prague Meeting Agenda <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#4>* 5. *Tips Available for Making Effective Presentations. <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#5>* 6. *ccNSO Gets Friendly on Facebook <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#6>* GNSO 7. *UK's National Physical Laboratory to Conduct Whois Privacy, Proxy Abuse Study <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#7>* 8. *Board Adopts Last Recommendation of Inter-Registrar Transfer Policy Part B <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#8>* ASO 9. *ICANN Board Ratifies Policy Proposal for Recovered IPv4 Address Blocks <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#9>* At-Large 10. *ALAC Approves Numerous Statements in Response to Public Comments <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#10>* 11. *Review of ALAC Rule of Procedures, Performance Indicators Begins <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#11>* 12. *Quick and Easy Translation Tool Installed on the At-Large Community Wiki Pages <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#12>* SSAC 13. *Issues Active in the SSAC <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#13>* GAC 14. *Where to Find GAC Information <http://www.icann.org/en/resources/policy/update/update-may12-en.htm#14>* Read in Your Preferred Language /ICANN Policy Update/is available in all six official languages of the United Nations. /Policy Update/ is posted on ICANN's web site <http://www.icann.org/en/topics/policy/>and available via online subscription. To receive the /Update/ in your Inbox each month, visit the ICANN subscriptions page <http://www.icann.org/en/newsletter/>, enter your e-mail address, and select "Policy Update" to subscribe. This service is free. <http://gnso.icann.org>

1 0

ALERTS From the Secretariat: TAS Reopens | ICANN
by Benedetta Rossi May 22, 2012

May 22, 2012

Dear BC Members, Please find below an ICANN announcement regarding the TAS' reopening. 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-21may12-en.htm Statement by Akram Atallah, COO 21 May 2012 The TLD Application System, or TAS, has reopened. All registered applicants can now log in, review and submit their applications. The system will remain open until 23:59 GMT/UTC on 30 May 2012. Consistent with our previous practice and to allow the application window to open as soon as possible, two-hour maintenance windows have been scheduled as follows: 22 May at 16:30 GMT/UTC, 25 May at 23:00 UTC, and 29 May at 22:00 UTC. Applicants are encouraged to review "/Top Things Users Should Know When TAS Reopens,/" posted on the new gTLD microsite at http://newgtlds.icann.org/en/applicants/tas/top-ten. The document provides advice on logging into and completing applications, submitting wire transfers, and contacting customer service with any issues users might encounter. During the last few weeks, we have fixed the technical glitch that caused us to take the system offline. Also, to address user feedback, we have improved the overall system performance and the HTML preview function. In our continuing review of the system logs and system traffic, we determined that in two instances, a single file might have been temporarily unavailable to an applicant. Full access to those two files has been restored. ICANN notified the affected users. We recognize and regret the inconvenience caused by this glitch and the delayed closing of the application window.

1 0

ICANN DNS L-Root announcements
by Baskin, James F (Jim) May 21, 2012

May 21, 2012

On a BC call about a month ago, I mentioned a question I had about a new instance of the ICANN L-Root that was mentioned in an ICANN announcement. I did some research and determined that the Russian server mentioned in the April 5 ICANN News Alert is a standard Anycast instance, and not an item that needs any special attention from the ICANN community. Since the April 5 Alert there have been two other similar ICANN news items - one announcing 14 new L-Root instances implemented in Brazil and another regarding L-Root instances in the Ukraine. The news item about Brazil specifically identified those servers as Anycast instances. Just to clarify that all of the mentioned L-Root instances mentioned are Anycast-based, I sent a note to Joe Abley, ICANN's Director of DNS Operations, last week seeking confirmation. As soon as I hear back from him, I will pass the confirmation along to the BC list. Jim Baskin

2 1

ALERTS from the Secretariat: TAS Interruption - Update (17 May 2012)
by Benedetta Rossi May 21, 2012

May 21, 2012

Dear BC Members, Please find below a TAS interruption update. 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-2-17may12-en.htm TAS Interruption - Update (17 May 2012) Statement by Akram Atallah, COO 17 May 2012 As we announced last week, ICANN is targeting 22 May 2012 as the reopening date for the TLD Application System, or TAS. Specifically, we are targeting 19:00 GMT/UTC on 22 May for the reopening. When we took the system offline on 12 April, just over twelve hours remained in the application window. We anticipate keeping TAS open for eight full days to allow users to review their applications and complete any remaining activities. We expect to close TAS at 23:59 GMT/UTC on 30 May 2012. We appreciate the community's continued interest and feedback on the TAS interruption. <http://gnso.icann.org>

1 0

ALERTS from the Secretariat: Period of 17-27 May 2012: Public Comment Periods Approaching Closing Date
by Benedetta Rossi May 21, 2012

May 21, 2012

Dear BC Members, Please find below an announcement of interest to BC members regarding public comment periods which are approaching closing dates. 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-17may12-en.htm Period of 17-27 May 2012: Public Comment Periods Approaching Closing Date 17 May 2012 The Following Public Comment periods are approaching their *Comment or Reply Period Close* dates, *May 17-27 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 <https://www.icann.org/en/news/public-comment> *Title* *Comment Period Close Date [UTC Time]* *Reply Period Close Date [UTC Time]* Second Annual IDN ccTLD Fast Track Process Review <https://www.icann.org/en/news/public-comment/fast-track-review-2012-09apr12…> 30 April 2012 [23:59] 21 May 2012 [23:59] ICANN Draft FY13 Operating Plan and Budget <https://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm> 24 May 2012 [23:59] 15 June 2012 [23:59] IDN Variant TLD Program - Revised Program Plan <https://www.icann.org/en/news/public-comment/idn-variant-tld-revised-progra…> 25 May 2012 [23:59] 15 June 2012 [23:59]

1 0

ALERTS from the Secretariat: New L-Root DNS Server Enhances DNS Fault Tolerance and Resistance to DDoS Attacks
by Benedetta Rossi May 21, 2012

May 21, 2012

Dear BC Members, Please find below an ICANN announcement on New L-root DNS Server. 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-18may12-en.htm New L-Root DNS Server Enhances DNS Fault Tolerance and Resistance to DDoS Attacks 18 May 2012 A new instance of L-Root has been installed in Odessa, Ukraine, increasing the Domain Name System's (DNS) overall fault tolerance and its resilience against certain types of cyber threats, such as Distributed Denial of Service (DDoS) attacks. The launch of the server node is a joint operation between ICANN and Ukrainian domain registry Hostmaster. DNS Root Servers form a key part of the Internet infrastructure that contribute to the global security and stability of the DNS. "Odessa is one of the largest Ukrainian cities, with one of the highest Internet penetration rates in the country," said Dmitry Kohmanyuk, a Hostmaster official. "Moreover, the Internet provider we opted for has quality connections to Western Ukraine, which is precisely why we decided to deploy the node there." Hostmaster, the Ukrainian administrator of the .UA domain, supplied the equipment necessary for the installation of the new L-Root node. "In addition to the newest L-Root server in Odessa, two other L-Root nodes, in Kyiv and Kharkiv, were also deployed through collaboration between ICANN and Hostmaster." said Joe Abley, Director of DNS Operations at ICANN." <http://gnso.icann.org>

1 0

ALERTS from the Secretariat: DRAFT - ICANN Language Services Policy and Procedures
by Benedetta Rossi May 21, 2012

May 21, 2012

Dear BC Members, Please find below an ICANN announcement regarding ICANN's Language Services Policy & Procedures. 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-2-18may12-en.htm DRAFT - ICANN Language Services Policy and Procedures * 简体中文 <https://www.icann.org/zh/news/announcements/announcement-2-18may12-zh.htm> * Français <https://www.icann.org/fr/news/announcements/announcement-2-18may12-fr.htm> * Español <https://www.icann.org/es/news/announcements/announcement-2-18may12-es.htm> * Русский <https://www.icann.org/ru/news/announcements/announcement-2-18may12-ru.htm> * العربية <https://www.icann.org/ar/news/announcements/announcement-2-18may12-ar.htm> 18 May 2012 *Forum Announcement:* Comment Period Opens on *Date:* 18 May 2012 *Categories/Tags:* Policy Processes; Transparency/Accountability; Reviews/Improvements; Participation; Events/Conferences *Purpose (Brief):* ICANN Language Services is submitting for public comment the draft Language Services Policy and Procedures. The purpose of this document, although implicit in its title, is to establish policies and procedures for all services related to languages – translation, simultaneous interpretation, teleconference interpretation, transcription (of recorded sessions) and RTT (real-time-transcription, also known as scribing). *Public Comment Box Link:* *Comment Open:* 18 May 2012 *Comment Close:* 2 July 2012 *Close Time (UTC):* 23:59 UTC Public Comment Announcement <https://www.icann.org/en/news/announcements/announcement-2-18may12-en.htm> *Reply Open:* 3 July 2012 To Submit Your Comments (Forum) <mailto:language-services-policy@icann.org> *Reply Close:* 1 August 2012 View Comments Submitted <http://forum.icann.org/lists/language-services-policy> *Close Time (UTC):* 23:59 UTC Report of Public Comments Brief Overview *Originating Organization:* ICANN Communications Department *Categories/Tags:* Policy Processes; Transparency/Accountability; Reviews/Improvements; Participation; Events/Conferences *Purpose (Brief):* ICANN is opening a public comment forum for the draft Language Services Policy and Procedures. Community members are asked to provide feedback on the proposed document. ICANN Language Services provides support for translation, simultaneous interpretation, teleconference interpretation, transcription (of recorded sessions) and RTT (real-time-transcription, also known as scribing). *Current Status:* Draft ICANN Language Services Policy and Procedures open for public comment. *Next Steps:* Comments will be accepted in this forum and in continued interaction with the community and staff. Once the comment and reply periods have ended, ICANN will review community feedback and post an assessment of comments received. The Board Committee on Public Participation will then submit the policy to the ICANN Board with its recommendation. *Staff Contact:* Christina M. Rodriguez *Email:* christina.rodriguez(a)icann.org <mailto:christina.rodriguez@icann.org?subject=More%20information%20on%20the%20DRAFT%20-%20ICANN%20Language%20Services%20Policy%20and%20Procedures%20public%20comment%20period> Detailed Information *Section I: Description, Explanation, and Purpose* The provision of language services is intended to facilitate access to ICANN and participation in its work for those who do not speak or are not fluent in English. The cost-effective provision of high quality multilingual services has two main objectives: * Make information about ICANN and its work accessible to those who speak languages other than English in ways that enhance participation in and the effectiveness of the multistakeholder model. * Make ICANN more effective as a global organization. ICANN's language services include: * Translation * Simultaneous interpretation * Teleconference interpretation * Transcription (of recorded sessions) * Scribing (Real Time Transcription - RTT) ICANN's working language is English. Its policy is to provide translation and interpretation in the six United Nations languages – currently Arabic, Chinese (Simplified), English, French, Russian and Spanish – where appropriate and taking account of budget constraints. *Section II: Background* Multilingualism is essential for a global multistakeholder organization. Meetings, documents and information must be accessible in a variety of languages. To address this need, ICANN submitted a previous version of this document (then called "Translation Programme <https://www.icann.org/en/news/announcements/announcement-13feb08-en.htm>") for public comment in March 2008, and in December 2008 contracted with a localization and language industry expert (a full-time translation coordinator). This complied with the Accountability and Transparency Framework and Principles, and laid the path toward more effective engagement with stakeholders. *Section III: Document and Resource Links* DRAFT – ICANN Language Services Policy and Procedures <https://www.icann.org/en/about/participate/language-services/draft-policies…>[PDF, 349 KB] *Section IV: Additional Information* None /(*) 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 this period lapses./

1 0

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

Re: [bc-gnso] RE: Important to hear from members -- Reconfiguring the URS?
by Marilyn Cade May 7, 2012

May 7, 2012

Folks, give us some additional advice: Chris and I will be on budget calls Tues and Wed. If NOT a Summit, or IF a Summit, what? We can't do much on substance on a budget camm, BUT we can say: high concern. Didn't get it right on any front. NOT representative of parties most affected. Sent via BlackBerry by AT&T -----Original Message----- From: Deutsch Sarah B <sarah.b.deutsch(a)verizon.com> Date: Mon, 7 May 2012 15:40:50 To: <psc(a)vlaw-dc.com>; <marie.pattullo(a)aim.be>; <Elisa.Cooper(a)markmonitor.com>; <marilynscade(a)hotmail.com>; <johnberard(a)aol.com>; <sdelbianco(a)netchoice.org>; <chris(a)andalucia.com>; <bc-gnso(a)icann.org> Cc: <zahid(a)dndrc.com> Subject: Re: [bc-gnso] RE: Important to hear from members -- Reconfiguring the URS? I respect Phil and his diligent representation of his domainer clients on this issue but I disagree. The UDRP's preponderance of evidence standard combined with establishing the already high bar of bad faith registration, use or trafficking in domain names has worked well. As someone with experience suing cybersquatters, we can obtain "clear and convincing" evidence usually only after months and sometimes years of litigation through discovery. I agree with Anjali that business owners need to have a real remedy like the do not sell list that prevents registrations of brands at the second level along with a workable URS. The URS problems go way beyond the price. As currently drafted, the process is fatally flawed at $300 and certainly will not get better at a higher price. The issue goes needs a better and fuller reevaluation process with broader participation, including from BC members. Sarah Sarah B. Deutsch Vice President & Associate General Counsel Verizon Communications Phone: 703-351-3044 Fax: 703-351-3670 sarah.b.deutsch(a)verizon.com From: Phil Corwin [mailto:psc@vlaw-dc.com] Sent: Monday, May 07, 2012 09:33 AM To: Marie Pattullo <marie.pattullo(a)aim.be>; 'Elisa Cooper' <Elisa.Cooper(a)markmonitor.com>; 'Marilyn Cade' <marilynscade(a)hotmail.com>; 'John Berard' <johnberard(a)aol.com>; 'Steve Delbianco' <sdelbianco(a)netchoice.org>; 'Chris at Andalucia' <chris(a)andalucia.com>; 'bc - GNSO list' <bc-gnso(a)icann.org> Cc: 'Zahid Jamil' <zahid(a)dndrc.com> Subject: RE: [bc-gnso] RE: Important to hear from members -- Reconfiguring the URS? Lowering the current burden of proof from "clear and convincing evidence" (strong case) to the same as the UDRP, which is "preponderance of the evidence" (which could be as low as 51/49) is not consistent with targeting "clear cut cases of trade mark infringement". That would bring in "shades of grey" cases that are not suitable for URS (intended for slam dunk, black and white cases) and belong in UDRP. It would also convert URS from a supplement to a substitute vis-à-vis UDRP. No competent examiner can properly weigh the evidence and provide adequate due process in such a case for a fee in the $300 to $500 range, which includes not just their compensation but the administrative costs of the accredited provider. Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey From: owner-bc-gnso(a)icann.org [mailto:owner-bc-gnso@icann.org] On Behalf Of Marie Pattullo Sent: Monday, May 07, 2012 6:55 AM To: 'Elisa Cooper'; 'Marilyn Cade'; 'John Berard'; 'Steve Delbianco'; 'Chris at Andalucia'; 'bc - GNSO list' Cc: 'Zahid Jamil' Subject: RE: [bc-gnso] RE: Important to hear from members -- Reconfiguring the URS? Dear all, AIM's members believe that we definitely need the URS, and as soon as possible. We need it to be a faster and cheaper solution than the UDRP, as the URS was originally meant to be. We also very much support the lowering of the burden of proof to deal with clear cut cases of trade mark infringement. Kind regards Marie From: owner-bc-gnso(a)icann.org <mailto:owner-bc-gnso@icann.org> [mailto:owner-bc-gnso@icann.org] <mailto:[mailto:owner-bc-gnso@icann.org]> On Behalf Of Elisa Cooper Sent: lundi 7 mai 2012 4:59 To: Marilyn Cade; John Berard; Steve Delbianco; Chris at Andalucia; bc - GNSO list Cc: Zahid Jamil Subject: [bc-gnso] RE: Important to hear from members -- Reconfiguring the URS? I agree - I think without really understanding what it is that they plan to "reconfigure", it's difficult to know whether it's policy or implementation. If we wait and see, will it be too late? What kind of preemptive action could we take here? Best, Elisa From: Marilyn Cade [mailto:marilynscade@hotmail.com] <mailto:[mailto:marilynscade@hotmail.com]> Sent: Friday, May 04, 2012 9:26 AM To: John Berard; Steve Delbianco; Chris at Andalucia; Elisa Cooper; bc - GNSO list Cc: Zahid Jamil Subject: Important to hear from members -- Reconfiguring the URS? Thanks, John, the discussion about URS needs to include the full BC. Many members have concerns, and I will note that that in the IRT last approach, some BC members were excluded from participation, in favor of others in the community, so we were not balanced in our BC participants. That was a serious challenge within the BC. Whether a URS; WHAT URS, and HOW URS is a serious topic to more than a few BC members. As to whether it is implementation/ and how that discussion progresses, versus if it is policy, is not clear, right now. What was the policy recommendation that created it? Should that policy recommendation be revised? Is this a change in how to implement a policy recommendation or a proposal to change/modify a policy recommendation? Finally, Summit? What is that? What are the parameters? Did the SO/AC/SG/Constituencies support such a budget proposal, and how and who would be funded to participate? The IPC may love this; the BC and ISPCP need to study it. As to what is 'returned' to Council to provide policy advice on, this is a seriously challenging area for us, I fully agree. We do want to hear from our broader membership on first this particular issue, and then we will talk further in the BC, probably in Prague, on 'what is policy and what is implementation'. I think that we all need to develop clarity on that for future. Whether the BC would take up a further policy clarity discussion on that latter topic would then come from Steve after the BC members offer views. Short term: My view on this for now: I want to see a staff discussion doc that explains the problems. Curtailing the URS and making it less useful doesn't excite me. paying a bit more an having useful option -- willing to discuss and understand. ICANN staff seem headed in a direction against that. Personal view: pay more/have a viable option. IF not, then no use, so don't proceed with URS. PERSONAL views only in that view. Discussion from informed members critical for next 36 hours. Marilyn Cade, BC Chair ---------------- Subject: Fwd: [council] Reconfiguring the URS? From: johnberard(a)aol.com <mailto:johnberard@aol.com> Date: Thu, 3 May 2012 16:09:38 -0400 CC: zahid(a)dndrc.com <mailto:zahid@dndrc.com> To: marilynscade(a)hotmail.com <mailto:marilynscade@hotmail.com> ; sdelbianco(a)netchoice.org <mailto:sdelbianco@netchoice.org> ; chris(a)andalucia.com <mailto:chris@andalucia.com> ; elisa.cooper(a)markmonitor.com <mailto:elisa.cooper@markmonitor.com> Do we agree with Phil that this is a policy matter? My instinct is to say it is not, but... Berard Sent from my iPhone Begin forwarded message: From: "Neuman, Jeff" <Jeff.Neuman(a)neustar.us <mailto:Jeff.Neuman@neustar.us> > Date: May 3, 2012 2:09:09 PM EDT To: "council(a)gnso.icann.org <mailto:council@gnso.icann.org> " <council(a)gnso.icann.org <mailto:council@gnso.icann.org> > Subject: [council] Reconfiguring the URS? All, Thanks to Phil Corwin for catching this, but buried in the new budget document (http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm) just put out for comment is a note on "reconfiguring" the URS. Excerpt provided below. I guess they could not find any URS providers that could do it for the costs that they had projected, so ICANN is holding 2 summits to work on a new model. My question for the Council, is whether this is really a policy issue that should be referred back to the GNSO Community as opposed to having ICANN on its own resolving after holding 2 summits. Given the controversy around this over the past few years, any tweaks to the URS should probably go back to the community in my opinion. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Uniform Rapid Suspension (URS) - $175K At present there is a significant gap between the features specified for the URS procedure and the desired cost. In order to bridge this gap we will: hold two summit sessions to reconfigure the URS to arrive at a lower cost model (one session in FY12 budget and another in this FY13 plan), conduct a process to develop and finalize URS Model in consultation with current UDRP providers and community members; and conduct RFP based on URS Model and select URS providers. The goal is have a URS program in place and providers contracted and onboard by June 2013. Jeffrey J. Neuman Neustar, Inc. / Vice President, Business Affairs 21575 Ridgetop Circle, Sterling, VA 20166 Office: +1.571.434.5772 Mobile: +1.202.549.5079 Fax: +1.703.738.7965 / jeff.neuman(a)neustar.biz <mailto:jeff.neuman@neustar.biz> / www.neustar.biz <http://www.neustar.biz/> ---------------- No virus found in this message. Checked by AVG - www.avg.com <http://www.avg.com> Version: 2012.0.2171 / Virus Database: 2425/4981 - Release Date: 05/06/12

3 2

Important to hear from members -- Reconfiguring the URS?
by Marilyn Cade May 7, 2012

May 7, 2012

Thanks, John, the discussion about URS needs to include the full BC. Many members have concerns, and I will note that that in the IRT last approach, some BC members were excluded from participation, in favor of others in the community, so we were not balanced in our BC participants. That was a serious challenge within the BC. Whether a URS; WHAT URS, and HOW URS is a serious topic to more than a few BC members. As to whether it is implementation/ and how that discussion progresses, versus if it is policy, is not clear, right now. What was the policy recommendation that created it? Should that policy recommendation be revised?Is this a change in how to implement a policy recommendation or a proposal to change/modify a policy recommendation? Finally, Summit? What is that? What are the parameters? Did the SO/AC/SG/Constituencies support such a budget proposal, and how and who would be funded to participate? The IPC may love this; the BC and ISPCP need to study it. As to what is 'returned' to Council to provide policy advice on, this is a seriously challenging area for us, I fully agree.We do want to hear from our broader membership on first this particular issue, and then we will talk further in the BC, probably in Prague, on 'what is policy and what is implementation'. I think that we all need to develop clarity on that for future. Whether the BC would take up a further policy clarity discussion on that latter topic would then come from Steve after the BC members offer views. Short term: My view on this for now: I want to see a staff discussion doc that explains the problems. Curtailing the URS and making it less useful doesn't excite me. paying a bit more an having useful option -- willing to discuss and understand. ICANN staff seem headed in a direction against that. Personal view: pay more/have a viable option. IF not, then no use, so don't proceed with URS. PERSONAL views only in that view. Discussion from informed members critical for next 36 hours. Marilyn Cade, BC Chair Subject: Fwd: [council] Reconfiguring the URS? From: johnberard(a)aol.com Date: Thu, 3 May 2012 16:09:38 -0400 CC: zahid(a)dndrc.com To: marilynscade(a)hotmail.com; sdelbianco(a)netchoice.org; chris(a)andalucia.com; elisa.cooper(a)markmonitor.com Do we agree with Phil that this is a policy matter? My instinct is to say it is not, but... Berard Sent from my iPhone Begin forwarded message: From: "Neuman, Jeff" <Jeff.Neuman(a)neustar.us> Date: May 3, 2012 2:09:09 PM EDT To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Reconfiguring the URS? All, Thanks to Phil Corwin for catching this, but buried in the new budget document (http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm) just put out for comment is a note on “reconfiguring” the URS. Excerpt provided below. I guess they could not find any URS providers that could do it for the costs that they had projected, so ICANN is holding 2 summits to work on a new model. My question for the Council, is whether this is really a policy issue that should be referred back to the GNSO Community as opposed to having ICANN on its own resolving after holding 2 summits. Given the controversy around this over the past few years, any tweaks to the URS should probably go back to the community in my opinion. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Uniform Rapid Suspension (URS) – $175K At present there is a significant gap between the features specified for the URS procedure and the desired cost. In order to bridge this gap we will: hold two summit sessions to reconfigure the URS to arrive at a lower cost model (one session in FY12 budget and another in this FY13 plan), conduct a process to develop and finalize URS Model in consultation with current UDRP providers and community members; and conduct RFP based on URS Model and select URS providers. The goal is have a URS program in place and providers contracted and onboard by June 2013. Jeffrey J. Neuman Neustar, Inc. / Vice President, Business Affairs 21575 Ridgetop Circle, Sterling, VA 20166 Office: +1.571.434.5772 Mobile: +1.202.549.5079 Fax: +1.703.738.7965 / jeff.neuman(a)neustar.biz / www.neustar.biz

5 6

Re: [bc-gnso] ALERTS from the Secretariat: TAS Interruption - Update (4 May 2012)
by Marilyn Cade May 7, 2012

May 7, 2012

We will add this specific topic to the BC call Friday as a question: how do we/BC affect defensive registrations_what is status of our proposals and how to advance them? Sent via BlackBerry by AT&T -----Original Message----- From: Hansen Anjali <AHansen(a)council.bbb.org> Date: Mon, 7 May 2012 15:08:35 To: <psc(a)vlaw-dc.com>; <bc-secretariat(a)icann.org>; <bc-gnso(a)icann.org> Subject: RE: [bc-gnso] ALERTS from the Secretariat: TAS Interruption - Update (4 May 2012) I am at the INTA conference now and one of the speakers just put up the costs to block and register 5 trademarks - the cost was over $137,000 based on her model of enforcing across X number of new gTLDS. Why do brandholders have to pay these costs? I don't know the ideal process for reining in defensive registrations, but I'm on this committee and not on others. So I am raising it here. Anjali Karina Hansen | Associate General Counsel Tel: 703-247-9340 Fax: 703-276-0634 Email: ahansen(a)council.bbb.org <mailto:ahansen@council.bbb.org> www.bbb.org <http://www.bbb.org/> | Start With Trust Council of Better Business Bureaus, Inc. 3033 Wilson Boulevard, Suite 600 Arlington, VA 22201 For consumer tips, scams and alerts: Read our blog <http://www.bbb.org/blog/> Find us on: Twitter <http://www.twitter.com/bbb_us> | Facebook <http://www.facebook.com/pages/Better-Business-Bureau-US/25368131403> | LinkedIn <http://www.linkedin.com/groups?about=&gid=1917928&trk=anet_ug_grppro> | YouTube <http://www.youtube.com/user/BBBconsumerTips> | Flickr <http://www.flickr.com/photos/bbb_us> <http://www.bbb.org/100-year> This message is a private communication, and may contain confidential and/or privileged information. If you have received this message by mistake, please notify the sender by reply email and then delete the message from your system without printing, copying or forwarding it. Thank you. From: Phil Corwin [mailto:psc@vlaw-dc.com] Sent: Monday, May 07, 2012 10:59 AM To: Hansen, Anjali; 'Benedetta Rossi'; bc - GNSO list Subject: RE: [bc-gnso] ALERTS from the Secretariat: TAS Interruption - Update (4 May 2012) Well, what you are saying implies reopening policy issues not just for the URS but for the function of the warning service tied to the TMC. If policy is to be reconsidered then why is that the exclusive province of this "committee', "summit", or whatever this newly made up process is when ICANN supposedly has a multi-stakeholder, bottom-up process for developing policy? Who is on this "committee', and from what does it derive its authority? I understand the concerns of TM holders completely in this new gTLD context, although I'm not in agreement that the multiple new rights protections for new gTLDs are insufficient, or that a judgment can be made without seeing them in operation. But if policy matters are to be reopened there should be an explanation of why that is happening beyond the fact that an unrealistic price target for an adjudicative process can't be met, and they should be reconsidered in regular order through standard ICANN process and not something made up on the fly. Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey From: Hansen, Anjali [mailto:AHansen@council.bbb.org] <mailto:[mailto:AHansen@council.bbb.org]> Sent: Monday, May 07, 2012 10:43 AM To: Phil Corwin; 'Benedetta Rossi'; bc - GNSO list Subject: RE: [bc-gnso] ALERTS from the Secretariat: TAS Interruption - Update (4 May 2012) That may be so, but I do not believe it is okay to make trademark holders defensively register in all of these new TLDS, so a compromise should be put forward by this committee. One that takes into account there may be authorized license holders, etc. Anjali Karina Hansen | Associate General Counsel Tel: 703-247-9340 Fax: 703-276-0634 Email: ahansen(a)council.bbb.org <mailto:ahansen@council.bbb.org> www.bbb.org <http://www.bbb.org/> | Start With Trust Council of Better Business Bureaus, Inc. 3033 Wilson Boulevard, Suite 600 Arlington, VA 22201 For consumer tips, scams and alerts: Read our blog <http://www.bbb.org/blog/> Find us on: Twitter <http://www.twitter.com/bbb_us> | Facebook <http://www.facebook.com/pages/Better-Business-Bureau-US/25368131403> | LinkedIn <http://www.linkedin.com/groups?about=&gid=1917928&trk=anet_ug_grppro> | YouTube <http://www.youtube.com/user/BBBconsumerTips> | Flickr <http://www.flickr.com/photos/bbb_us> <http://www.bbb.org/100-year> This message is a private communication, and may contain confidential and/or privileged information. If you have received this message by mistake, please notify the sender by reply email and then delete the message from your system without printing, copying or forwarding it. Thank you. From: Phil Corwin [mailto:psc@vlaw-dc.com] <mailto:[mailto:psc@vlaw-dc.com]> Sent: Monday, May 07, 2012 9:13 AM To: Hansen, Anjali; 'Benedetta Rossi'; bc - GNSO list Subject: RE: [bc-gnso] ALERTS from the Secretariat: TAS Interruption - Update (4 May 2012) Anjali: The TM Clearinghouse is tied to the warning service, which alerts registrants that their domain might be infringing and allows them to consider that, and the fact that they have been warned would almost certainly be a factor in any subsequent UDRP or URS action. However, as to your suggestion that "registrars will thereby put on notice not to sell those trademarks, or deviations thereof, to anyone except the actual trademark holders", that goes too far - there are many instances in which a registrant other than the trademark holder (e.g., an authorized reseller of a particular product or service) could register a domain incorporating a trademark without infringement. Best, Philip Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey From: owner-bc-gnso(a)icann.org <mailto:owner-bc-gnso@icann.org> [mailto:owner-bc-gnso@icann.org] <mailto:[mailto:owner-bc-gnso@icann.org]> On Behalf Of Hansen, Anjali Sent: Monday, May 07, 2012 8:15 AM To: 'Benedetta Rossi'; bc - GNSO list Subject: RE: [bc-gnso] ALERTS from the Secretariat: TAS Interruption - Update (4 May 2012) Thanks Benedetta. 2091 new TLDs to be prepared for. My major concerns about this are below: 1) The first thing that I am up in arms about is that the ICM Registry responsible for the .xxx is also applying for .sex and .adult. ICM will allow all of those trademark owners who registered for domains in .xxx to now do the same in .sex and .adult. As you recall, ICM made many millions off of anyone who didn't want to be associated with its .xxx and now they will be allowed to make millions more. It seems as if the brilliant business model in domaining is to apply for a registry everyone is afraid of being associated with and then take their money . I am hoping this committee might want to insist that ICANN put an end to such trademark blackmail. I'd like to get my money back for the trademarks I've had to block in .xxx. Not to mention that ICM has reserved BBB.xxx for their own use despite not holding the trademark thereto. Thus, we couldn't block our most famous trademark from .xxx. 2) I believe the legal and fair approach is to have everyone file their trademarks in a central Trademark Clearinghouse and the registries and registrars will thereby put on notice not to sell those trademarks, or deviations thereof, to anyone except the actual trademark holders. Otherwise, we might have to defensively register or block in hundreds or even a thousand new TLDs. I'd appreciate it if this committee would take on this issue of defensive registrations again at the appropriate time. I appreciate all that you have done thus far, but ICANN hasn't taken the appropriate measures to date. Thanks everyone. Anjali Anjali Karina Hansen | Associate General Counsel Tel: 703-247-9340 Fax: 703-276-0634 Email: ahansen(a)council.bbb.org <mailto:ahansen@council.bbb.org> www.bbb.org <http://www.bbb.org/> | Start With Trust Council of Better Business Bureaus, Inc. 3033 Wilson Boulevard, Suite 600 Arlington, VA 22201 For consumer tips, scams and alerts: Read our blog <http://www.bbb.org/blog/> Find us on: Twitter <http://www.twitter.com/bbb_us> | Facebook <http://www.facebook.com/pages/Better-Business-Bureau-US/25368131403> | LinkedIn <http://www.linkedin.com/groups?about=&gid=1917928&trk=anet_ug_grppro> | YouTube <http://www.youtube.com/user/BBBconsumerTips> | Flickr <http://www.flickr.com/photos/bbb_us> <http://www.bbb.org/100-year> This message is a private communication, and may contain confidential and/or privileged information. If you have received this message by mistake, please notify the sender by reply email and then delete the message from your system without printing, copying or forwarding it. Thank you. From: owner-bc-gnso(a)icann.org <mailto:owner-bc-gnso@icann.org> [mailto:owner-bc-gnso@icann.org] <mailto:[mailto:owner-bc-gnso@icann.org]> On Behalf Of Benedetta Rossi Sent: Sunday, May 06, 2012 4:29 PM To: bc - GNSO list Subject: [bc-gnso] ALERTS from the Secretariat: TAS Interruption - Update (4 May 2012) Dear BC Members, Please find below an ICANN announcement. Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org <http://www.bizconst.org> TAS Interruption - Update (4 May 2012) http://www.icann.org/en/news/announcements/announcement-04may12-en.htm Statement by Akram Atallah, COO 4 May 2012 The TLD Application System, or TAS, held 2091 applications - either submitted or in progress - when it was taken offline on 12 April 2012. In addition, there are 214 potential applications that were registered prior to the 29 March cut-off date, but whose payments have not yet been received or reconciled. ICANN has received approximately USD $350 million in fees for applications for new gTLDs. As we have reported, we are in the process of notifying applicants whether they were affected by the software glitch, and plan to complete this process on or before Tuesday, 8 May. Shortly after that process is complete, we will announce the schedule for reopening TAS and completing the application period. Once the system is reopened, we will keep it open for at least five business days. We appreciate your understanding as we work to bring the TLD application system back online. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org <mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org ---------------- No virus found in this message. Checked by AVG - www.avg.com <http://www.avg.com> Version: 2012.0.2171 / Virus Database: 2425/4981 - Release Date: 05/06/12 ---------------- No virus found in this message. Checked by AVG - www.avg.com <http://www.avg.com> Version: 2012.0.2171 / Virus Database: 2425/4983 - Release Date: 05/07/12

1 0

ALERTS from the Secretariat: TAS Interruption - Update (4 May 2012)
by Benedetta Rossi May 7, 2012

May 7, 2012

Dear BC Members, Please find below an ICANN announcement. Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org TAS Interruption - Update (4 May 2012) http://www.icann.org/en/news/announcements/announcement-04may12-en.htm Statement by Akram Atallah, COO 4 May 2012 The TLD Application System, or TAS, held 2091 applications - either submitted or in progress - when it was taken offline on 12 April 2012. In addition, there are 214 potential applications that were registered prior to the 29 March cut-off date, but whose payments have not yet been received or reconciled. ICANN has received approximately USD $350 million in fees for applications for new gTLDs. As we have reported, we are in the process of notifying applicants whether they were affected by the software glitch, and plan to complete this process on or before Tuesday, 8 May. Shortly after that process is complete, we will announce the schedule for reopening TAS and completing the application period. Once the system is reopened, we will keep it open for at least five business days. We appreciate your understanding as we work to bring the TLD application system back online. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org <mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

5 9

Re: Important to hear from members -- Reconfiguring the URS?
by Marilyn Cade May 7, 2012

May 7, 2012

I understand several BC members are at INTA. Perhaps it is possible to get a sense from the IPC members there on their views re this? Sent via BlackBerry by AT&T -----Original Message----- From: Elisa Cooper <Elisa.Cooper(a)markmonitor.com> Date: Mon, 7 May 2012 02:58:38 To: <marilynscade(a)hotmail.com>; <johnberard(a)aol.com>; <sdelbianco(a)netchoice.org>; <chris(a)andalucia.com>; <bc-gnso(a)icann.org> Cc: <zahid(a)dndrc.com> Subject: RE: Important to hear from members -- Reconfiguring the URS? Clean false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 I agree - I think without really understanding what it is that they plan to "reconfigure", it's difficult to know whether it's policy or implementation. If we wait and see, will it be too late? What kind of preemptive action could we take here? Best, Elisa From: Marilyn Cade [mailto:marilynscade@hotmail.com] Sent: Friday, May 04, 2012 9:26 AM To: John Berard; Steve Delbianco; Chris at Andalucia; Elisa Cooper; bc - GNSO list Cc: Zahid Jamil Subject: Important to hear from members -- Reconfiguring the URS? Thanks, John, the discussion about URS needs to include the full BC. Many members have concerns, and I will note that that in the IRT last approach, some BC members were excluded from participation, in favor of others in the community, so we were not balanced in our BC participants. That was a serious challenge within the BC. Whether a URS; WHAT URS, and HOW URS is a serious topic to more than a few BC members. As to whether it is implementation/ and how that discussion progresses, versus if it is policy, is not clear, right now. What was the policy recommendation that created it? Should that policy recommendation be revised? Is this a change in how to implement a policy recommendation or a proposal to change/modify a policy recommendation? Finally, Summit? What is that? What are the parameters? Did the SO/AC/SG/Constituencies support such a budget proposal, and how and who would be funded to participate? The IPC may love this; the BC and ISPCP need to study it. As to what is 'returned' to Council to provide policy advice on, this is a seriously challenging area for us, I fully agree. We do want to hear from our broader membership on first this particular issue, and then we will talk further in the BC, probably in Prague, on 'what is policy and what is implementation'. I think that we all need to develop clarity on that for future. Whether the BC would take up a further policy clarity discussion on that latter topic would then come from Steve after the BC members offer views. Short term: My view on this for now: I want to see a staff discussion doc that explains the problems. Curtailing the URS and making it less useful doesn't excite me. paying a bit more an having useful option -- willing to discuss and understand. ICANN staff seem headed in a direction against that. Personal view: pay more/have a viable option. IF not, then no use, so don't proceed with URS. PERSONAL views only in that view. Discussion from informed members critical for next 36 hours. Marilyn Cade, BC Chair ---------------- Subject: Fwd: [council] Reconfiguring the URS? From: johnberard(a)aol.com <mailto:johnberard@aol.com> Date: Thu, 3 May 2012 16:09:38 -0400 CC: zahid(a)dndrc.com <mailto:zahid@dndrc.com> To: marilynscade(a)hotmail.com <mailto:marilynscade@hotmail.com> ; sdelbianco(a)netchoice.org <mailto:sdelbianco@netchoice.org> ; chris(a)andalucia.com <mailto:chris@andalucia.com> ; elisa.cooper(a)markmonitor.com <mailto:elisa.cooper@markmonitor.com> Do we agree with Phil that this is a policy matter? My instinct is to say it is not, but... Berard Sent from my iPhone Begin forwarded message: From: "Neuman, Jeff" <Jeff.Neuman(a)neustar.us <mailto:Jeff.Neuman@neustar.us> > Date: May 3, 2012 2:09:09 PM EDT To: "council(a)gnso.icann.org <mailto:council@gnso.icann.org> " <council(a)gnso.icann.org <mailto:council@gnso.icann.org> > Subject: [council] Reconfiguring the URS? All, Thanks to Phil Corwin for catching this, but buried in the new budget document (http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm) just put out for comment is a note on "reconfiguring" the URS. Excerpt provided below. I guess they could not find any URS providers that could do it for the costs that they had projected, so ICANN is holding 2 summits to work on a new model. My question for the Council, is whether this is really a policy issue that should be referred back to the GNSO Community as opposed to having ICANN on its own resolving after holding 2 summits. Given the controversy around this over the past few years, any tweaks to the URS should probably go back to the community in my opinion. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Uniform Rapid Suspension (URS) - $175K At present there is a significant gap between the features specified for the URS procedure and the desired cost. In order to bridge this gap we will: hold two summit sessions to reconfigure the URS to arrive at a lower cost model (one session in FY12 budget and another in this FY13 plan), conduct a process to develop and finalize URS Model in consultation with current UDRP providers and community members; and conduct RFP based on URS Model and select URS providers. The goal is have a URS program in place and providers contracted and onboard by June 2013. Jeffrey J. Neuman Neustar, Inc. / Vice President, Business Affairs 21575 Ridgetop Circle, Sterling, VA 20166 Office: +1.571.434.5772 Mobile: +1.202.549.5079 Fax: +1.703.738.7965 / jeff.neuman(a)neustar.biz <mailto:jeff.neuman@neustar.biz> / www.neustar.biz <http://www.neustar.biz/>

2 1

ALERTS From the Secretariat: IDN Variant TLD Program - Revised Program Plan
by Benedetta Rossi May 6, 2012

May 6, 2012

http://www.icann.org/en/news/announcements/announcement-2-04may12-en.htm IDN Variant TLD Program - Revised Program Plan <http://www.icann.org/en/news/announcements/announcement-2-04may12-en.htm> *Forum Announcement:* Comment Period Opens on *Date:* 4 May 2012 *Categories/Tags:* Top-Level Domains *Purpose (Brief):* The purpose of this project is to resolve many of the issues necessary to delegate variant TLDs. The first IDN Variant Issues Project explored the issues associated with the potential inclusion of IDN variant TLDs in the DNS root zone, at the request of the ICANN Board and the community. The first two phases of the project have been completed with the publication of the final Integrated Issues Report on 20 February 2012 and the project is now entering its next phase. ICANN created a program plan for next steps, posted it for public comment, and presented it in a session at the ICANN meeting in Costa Rica in March 2012. Based on the comments received to date, the project plan has been updated, and the team is seeking input on the revised plan during this public comment period. *Public Comment Box Link:* http://www.icann.org/en/news/public-comment/idn-variant-tld-revised-program… <http://gnso.icann.org>

1 0

BC Initial Notes on Draft FY13 Budget
by Chris Chaplow May 3, 2012

May 3, 2012

Dear BC members, Here are my early bird notes on Draft FY13 Budget which was published on time 1 May 2012. The comment closes 25th May before reply round which closes on 15 June ahead of Board Finance Committee meeting and formal Board approval at Prague Meeting. <http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm> http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm Highlights Level of is the same as previous years. Ie One level of breakdown followed by text with some numbers. (Cross check this against original presentation in Cartagena with suggested a second level would be created this time). General revenue up to 78m$ in FY13 from 70m$ in FY12 Budget and 71m$ in FY12 Forcast Plus gTLD at 61m$ (part of 500 x 185k$ = 990m$) Operating Expenses 18% up 74m$ in FY13 from 71m$ in FY12 Budget and 63m$ in FY12 Forcast ie FY12 expenses are significant under budget Personal costs 18% up to 30.9m$ in FY13 Staff levels up from 149 to 189 Professional sevvices up 39% to 20.6m$ SSR - 14% up to 9.3 m$ in FY13 from 8.7 m$ in FY12 Budget and 8.0 m$ in FY12 Forcast Compliance - 60% up to 6.1 m$ in FY13 from 4.8 m$ in FY12 Budget and 3.8 m$ in FY12 Forcast Ie FY12 expenses are significant under budget. Contract Compliance up to 20 for FY13 “It is mainly driven by (i) a Compliance department headcount increase from an average of 9 FTE in FY12 to 15 FTE in FY13 for approximately $1.1 million, (ii) Compliance audit for $0.5 million, (iii) Legal allocated costs increase for $0.4 million, (iv) other overhead increases for $0.3 million.” (cross check 9FTE which is not as previously reported in CR) Meeting team increased for 11FTE to 13 FTE. Meeting sponsorship at 400k per meeting. Only 2 meeting in FY13 No fellowship budget identified No communication dept budget identified Large text on Global engagement including: “Participate in events and provide presentations on ICANN at the request of stakeholders, and expect increased interest in all regions as part of global engagement to promote a healthy Internet eco-system “ “Ongoing support for, and development of, the Newcomer Program at ICANN meetings” “Increased accessibility to ICANN materials through the dramatic increase in content translated into all six UN languages. Such translations have increased in volume by roughly 80 percent compared year-over-year. ” “During FY13 there will be an increased use of outreach tools (e.g., provision of a framework for community use) and continuation of current discussions with the community to identify gaps in outreach strategy. The goal of the FY13 work is to support new ICANN community members to take on effective participatory roles, engage existing participants to become ambassadors in the regions, educate and develop leaders within the SO and AC communities, and support existing community members through training and development. “ 25 projects identified with number of FTE and $ for each. (Need to cross reference against the Framework and our comments) Here are a few New Complaince System 1.2m$ Outreach 230k$ 2013-2016 Strat Plan 45k$ New gTLD Second Round $175k TradeMark ClearingHouse $438k Uniform Rapid suspension $175k WHOIS Programme $969k gTLD Budget Senarios for 500, 1000, 2000 aplications 500 applications, net loss in asset -5m$ 1000 applications, net gain in asset -0,6m$ 2000 applications, net loss in asset +30m$ New gTLD Panels Background Screening : Price Waterhouse Cooper DNS Stability and String registry : Interisle Consulting Group String Similarity : InterConnect Communications Geographical Nanes : InterConnect Communications Community Priority Evaluation : InterConnect Communications & Economist Inteligence Unit Financial Technical Operational : Ernst & Young, KPMG, JAS Global Advisors Quality Control : JAS Global Advisors SO /AC budget requests. BC Requests Leadership from Developing Countries Programme $24k YES APPROVED Secretariat Travel $6k NOT APPROVED Outreach and Awareness Event $12k YES APPROVED BC Officer Travel $16k YES APPROVED BC Newsletter $7.5k YES APPROVED (See caveats on page 74) In general most requests were approved. Total budget 530k$ Secretariat Travel and Services was not approved to any Constituency. CSG BOP WG are already studying the document and having a call next week to coordinate CSG and BC comment. re <https://community.icann.org/pages/viewpage.action?pageId=31163092> https://community.icann.org/pages/viewpage.action?pageId=31163092 Hope this is helpful Any comment or request for more elaboration in a particular area most welcome Best Chris Chaplow Copy Paste for FY13 Draft Budget Security, Stability and Resilience Operations (SSR) Page 13 In FY13, budget resources required to support SSR activities are estimated at $9.1 million, a 14 percent increase over FY12’s forecast. The increase for SSR in FY13 is due to continued collaboration and engagement in the following activities:  Work with ICANN’s IT on improving internal infrastructure, network security improvements and mobile device practices  Implement recommendations of the Security, Stability and Resiliency Review Team  Support root resilience efforts, L-root expansion and contingency exercises with partners  DNS capability training with ccTLD operators, law enforcement and the operational security community (including Interpol, Commonwealth Cybercrime Initiative and other community partners)  Conduct DNS Risk Management Framework assessment based on recommendations from Board-level working group and influenced by community-driven DNS Security and Stability Analysis Working Group (DSSA-WG)  Continued engagement and adoption activities for DNSSEC with TLD operators, registrars, ISPs and enterprises; key ceremonies and support to SSAC work party on key rollover  Support the IDN Program with the next phase of the IDN variant project  Security support to gTLD Operations (TAS, Digital Archery and other system security)  Implement objectives contained in the FY13 SSR Framework after the community and Board of Directors buy-in  Follow best practices for internal Information Security and network operations  Physical security improvements in Los Angeles, Brussels and other ICANN office locations  Conduct 4th Global DNS SSR Symposium in FY13 in collaboration with the Anti-Phishing Working Group  Support to Global Partnerships and Regional Vice Presidents in representing ICANN  Provide thought leadership and expertise as requested by others in the Internet ecosystem, such as in the IT Sector DNS Risk Update, and participate in events such as the Internet Governance Forum Contractual Compliance Page 14 In FY13, budget resources for Contractual Compliance are estimated to be $6.1 million, about 60 percent greater than FY12 forecast. It is mainly driven by (i) a Compliance department headcount increase from an average of 9 FTE in FY12 to 15 FTE in FY13 for approximately $1.1 million, (ii) Compliance audit for $0.5 million, (iii) Legal allocated costs increase for $0.4 million, (iv) other overhead increases for $0.3 million. The increase demonstrates ICANN’s continued commitment to “strengthen the Contractual Compliance function and its operations; and to establish clear performance measures and improve communication and reporting to the community”. Work in FY13 will focus in the following areas:  Continue to grow Compliance resources in numbers and expertise to: 1) improve operations with increased monitoring and proactive enforcement of the contracts and policies; 2) proactively engage and collaborate with registrars to improve compliance and reduce complaints; 3) promote a culture of compliance and increase compliance awareness among the contracted parties through global outreach activities  In addition, to support the augmented Contractual Compliance function, resource increases are planned for other ICANN departments, such as the Registrar and Registry Liaison teams, Legal (and external legal services), Information Technology, Finance, Security and Policy  Continue the effort to standardize operations, systems and tools for efficiency and effectiveness. This includes additional automation in complaint processing and tracking, rollout of an internal collaboration tool, enhancements to current systems to reflect the standard Contractual Compliance’s process and templates, launching a program to replace the current complaint intake systems and continue efforts in preparation for new gTLDs  Communicate, develop and implement the plan for a robust risk and audit strategy  Develop performance metrics for core operations and improve and deliver fact-based communications and reporting to the community

3 3

ICANN Eliminates Board Meetings at ICANN Meetings
by Phil Corwin May 2, 2012

May 2, 2012

In my opinion, a step backwards for transparency and accountability -- http://www.thedomains.com/2012/04/30/icann-eliminates-friday-public-board-m… . Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey

8 14

Save the date: Upcoming BC Members call: Monday May 7th 2012 @ 12 pm EDT
by Benedetta Rossi May 1, 2012

May 1, 2012

Dear BC Members, Please save the date for the upcoming BC Members call taking place on *Monday May 7th 2012 at 12 pm EDT. * Dial in details and agenda will follow. Please let me know if you require a dial out. Thank you! -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org

3 2

Re: [bc-gnso] PayPal Comments to Staff Roadmap for SAC 051
by Marilyn Cade May 1, 2012

May 1, 2012

Thanks, Bill. Sent via BlackBerry by AT&T -----Original Message----- From: Smith Bill <bill.smith(a)paypal-inc.com> Date: Tue, 1 May 2012 17:44:19 To: <bill.smith(a)paypal-inc.com> Cc: <bc-gnso(a)icann.org> Subject: Re: [bc-gnso] PayPal Comments to Staff Roadmap for SAC 051 My bad. My spam filter caught the ICANN "confirmsystem" message and I never saw it. I apologize for wasting everyone's time. On May 1, 2012, at 9:17 AM, Smith, Bill wrote: > I am forwarding this message to the BC list since PayPal's comments were not posted on the public site. Perhaps this is due to my late posting of comments. However, I received no notification that our comments would not be considered or published. > > Begin forwarded message: > > From: William Smith <bill.smith(a)paypal-inc.com<mailto:bill.smith@paypal-inc.com>> > Subject: PayPal Comments to Staff Roadmap for SAC 051 > Date: April 10, 2012 3:26:07 PM PDT > To: <sac051-draft-roadmap(a)icann.org<mailto:sac051-draft-roadmap@icann.org>> > > Attached Please find PayPal's comments for the Staff Roadmap for SAC 051. > > > <2012-04-10_ICANN.pdf>

1 0

Fwd: PayPal Comments to Staff Roadmap for SAC 051
by Smith, Bill May 1, 2012

May 1, 2012

I am forwarding this message to the BC list since PayPal's comments were not posted on the public site. Perhaps this is due to my late posting of comments. However, I received no notification that our comments would not be considered or published. Begin forwarded message: From: William Smith <bill.smith(a)paypal-inc.com<mailto:bill.smith@paypal-inc.com>> Subject: PayPal Comments to Staff Roadmap for SAC 051 Date: April 10, 2012 3:26:07 PM PDT To: <sac051-draft-roadmap(a)icann.org<mailto:sac051-draft-roadmap@icann.org>> Attached Please find PayPal's comments for the Staff Roadmap for SAC 051.

1 1

Save the date: Upcoming BC Members call: Monday May 7th 2012 @ 12 pm EDT
by Benedetta Rossi May 1, 2012

May 1, 2012

Dear BC Members, Please save the date for the upcoming BC Members call taking place on *Monday May 7th 2012 at 12 pm EDT. * Dial in details and agenda will follow. Please let me know if you require a dial out. Thank you! -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org

1 0