September 2011 - Bc-gnso - lists.icann.org

Updated FY12 op plan, released on 12th of Sep - Chris Chaplow
by Chris Chaplow 16 Sep '11

16 Sep '11

Dear Members, Here is my update that I was intending to report on the call. Third FY12 budget has just been published. To remind you these were Draft in 17-May, then Public and Constituency comments, board approval 21-June subject to unspecified changes. Approved budget published 9-August. (Only changes I can see from draft to approved were the AC/SO support requests reduced from 970k to 597k) although the introduction does mention board minuted approval of RPKI (no numbers) and JAS ( 2m$ but I can not see it in the budget) Rational for the 9 Sept Budget is Based on the Board's decision to approve the launch of the New gTLD Program and to open the application window on 12 January 2012, the application processing now extends into the 2013 fiscal year. Therefore, it became obvious that including the New gTLD revenue and expenses across FY12 and FY13 presents a more accurate view of the overall FY12 budget. Also published are a <http://www.icann.org/en/financials/consolidated-budget-fy12-09sep11-en.pdf> new consolidated budget schedule which simply summarizes the consolidated budget detail into two pages. (somebody must have taken my idea from the sheet I waved at the BC board meeting) and a new schedule presenting the <http://www.icann.org/en/financials/new-gtld-program-cash-flow-09sep11-en.pd f> estimated cash flows for the New gTLD program, to include the processing of the 1st round applications over FY12 and FY13. Also mentioned is a re-allocation of approved constituency funding from three At-Large regional meetings to one General Assembly are reflected in this <http://www.icann.org/en/financials/adopted-opplan-budget-fy12-09sep11-en.pd f> updated FY12 Budget ( although this was in the 9-Augand and the heading does not mention the denial of the constituency requests element) So what highlight of this new budget. 97m gTLD income (500 * 185k) is moved from FY12 to 27m in FY12 and 64m FY13. Costs move as well but this has the effect of moving the previous this has the effect of reducing the 18m increase in net assets (profit) to only 180k. (a number so small and positive that it must have been worked backwards) Also new is out of 94m income that is allowance for 8.2m refunds. Costs already occurred in previous years seem to be included again. So it look like the whole exercise is not to show profit for the program. This would be a conservative as accounting is supposed to be. I have to go now so will send this first part now and another to more to follow. 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

conflict of interest policy
by Chris Chaplow 16 Sep '11

16 Sep '11

Phil Are these the docs we should read on the conflict of interest policy. <http://www.icann.org/en/committees/coi/coi-policy-30jul09-en.htm> http://www.icann.org/en/committees/coi/coi-policy-30jul09-en.htm http://www.icann.org/en/committees/coi/coi-policy-04mar99.htm 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

Policy Calendar for 17-Feb-2011 BC Member call
by Steve DelBianco 15 Sep '11

15 Sep '11

To: Business Constituency Members From: Steve DelBianco, vice chair for policy coordination Below is the latest BC policy calendar, for use during 17-Feb member call. (attachments are provided for Channel 4 below) Channel 1. BC participation in ICANN Public Comment processes: ICANN Public Comment page is at http://www.icann.org/en/public-comment/ Selected Public Comments open at this time: (in order of comment closing dates) 1: Accountability & Transparency Review Team FINAL recommendations (14-Feb) http://forum.icann.org/lists/atrt-final-recommendations/index.html#00010 2: Proposed process for recognizing new Constituencies (4-Mar) 3: Interim report on internationalized registration data (14-Mar) Note: BC members are encouraged to submit individual or company comments on any topic. Based on member interest, the BC selects topics on which to submit official positions. Channel 2. Support for discussion and votes of our representatives on GNSO Council Upcoming discussions & votes at 24-Feb GNSO Council meeting (15:00 UTC) Full agenda at http://gnso.icann.org/meetings/agenda-council-24feb11-en.htm Item 4: proposed guidelines for working groups. Should they be adopted or posted for further comment? Item 5: Responding to Board resolution asking GNSO for definitions & metrics for AOC terms (consumer choice, consumer trust, and competition). Several BC members have volunteered. No outreach yet from Rosemary Sinclair. Item 6: WHOIS studies. Staff posted an analysis of "Privacy & Proxy Relay & Reveal". Council must decide which of remaining 3 studies (Registrant Identification, Proxy and Privacy "abuse" and this Relay and Reveal study) staff should initiate. (see http://gnso.icann.org/issues/whois/whois-studies-chart-11feb11-en.pdf) Item 7: update on Joint DNS security and stability analysis working group. Draft charter at http://www.ccnso.icann.org/workinggroups/dssa-draft-charter-12nov10-en.pdf Item 8: discussion of cross-community working groups Item 9: Staff feedback regarding Registration Abuse Policies (RAP) motion passed at 3-Feb meeting (http://gnso.icann.org/resolutions/#201102 ) RESOLVED #1, the GNSO Council instructs ICANN Policy Staff to forward the two issues identified by the RAP IDT as having low resource requirements, WHOIS Access recommendation #2 and Fake Renewal Notices recommendation #1, to ICANN Compliance Staff for resolution. ICANN? Compliance Staff is requested to provide the GNSO Council with its feedback on the two recommendations and proposed implementation in a timely manner. RESOLVED #2, the GNSO Council requests an Issues Report on the current state of the UDRP. RESOLVED #3, the GNSO Council requests 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. Council Working Groups: (see GNSO Project Status List as of 27-Jan-2011, at http://gnso.icann.org/meetings/pending-projects-list.pdf Channel 3. Supporting discussion and voting on policy matters before the Commercial Stakeholders Group (CSG) (SarahDeutsch ) Channel 4. BC statements and responses during public meetings (Board meetings, outreach events, public forum, etc.) Upcoming Board/GAC Intercessional meeting in Brussels, 28-Feb to 1-Mar GAC 'scorecard' expected before 22-Feb. Selected previous BC positions on GAC-Board topics (attached) Affirmation review team for Whois (Susan Kawaguchi, Bill Smith) Affirmation reviewteam for SSR (Security, Stability, & Reslience) (Jeff Brueggeman)

8 23

ALERTS from the Secretariat: Safe and Secure New gTLDs: ICANN Seeks Back-up Registry Operators
by Benedetta Rossi 15 Sep '11

15 Sep '11

http://www.icann.org/en/announcements/announcement-2-14sep11-en.htm Safe and Secure New gTLDs: ICANN Seeks Back-up Registry Operators(Emergency Back-End Registry Operators or "EBEROs")14 September 2011ICANN is issuing today a Request for Information (RFI) [PDF, 660 KB] to identify potential Emergency Back-End Registry Operators (EBERO).One of ICANN's core missions is to preserve the operational security and stability of the Internet while also supporting open competition. With the upcoming launch of the New generic Top-Level Domain (New gTLD) program, the Internet will see a number of new gTLD registry operators. Although all applicants must meet technical, operational and financial requirements (see the gTLD Applicant Guidebook – http://www.icann.org/en/topics/new-gtlds/dag-en.htm) the community developed new gTLD program includes provision for a backup process. The EBERO is designed to be activated should a registry operator require assistance to sustain critical registry functions for a period of time or in the case of transition for one registry operator to another.Candidates are expected to meet the requirements outlined in the RFI, which requires, for example, at least three years of experience in operating Domain Name services (DNS) and one year of experience operating Registration Data Directory Services (RDDS) and Extensible Provisioning Protocol (EPP) services. Besides the technical requirements, ICANN seeks candidates from geographically diverse regions in order to provide local service to registries in all regions and provide alternate sites in case of local disasters.ICANN is looking forward to receiving comprehensive information from the potential candidates. Negotiations with certain respondents to the RFI that provide comprehensive information will be initiated for the purpose of creating process details and entering into an agreement to provide backend services. The deadline for responses is November 30, 2011 at 23:59 UTC. Please direct your information to ebero(a)icann.org. Responses after the deadline will not be considered.RFI activities schedule at a glance:Request for proposals issued by ICANN14 September 2011Respondents' Q&A – TeleconferenceOn or about 16 November 2011Written proposals due30 November 2011 – 23:59 UTC1. What is a registry?A "Registry" is the authoritative, master database of all domain names registered in each Top-Level Domain. The registry operator keeps the master database and also generates the "zone file" which allows computers to route Internet traffic to and from top-level domains anywhere in the world.2. What is an Emergency Operator?Emergency Operator or Back-End Registry Operator is an organization that has partnered with ICANN to provide registry services in case another registry is unable to operate. The emergency operators will be selected by ICANN based on the criteria outlined in the RFI. 3. What happens when a gTLD registry operation fail either financially or due a technical emergency?If an emergency occurs, and a Registry is unable to provide critical services, it will be the function of the Emergency Operator to ensure the continuity of the services. This provider emergency transition process is managed by ICANN and requires multiple providers to be available to take on the function in case one provider is not able to timely take the operation or if there is a conflict of interest.4. What are the critical registry functions?Functions that are critical to the operation of a gTLD registry (i.e., those provided by the EBERO) are:Domain Names System (DNS) resolution;Domain Name System Security Extensions (DNSSEC) properly signed zone (if DNSSEC is offered by the registry);Shared Registration System (SRS), usually by means of the Extensible Provisioning Protocol (EPP);Registration Data Directory Services (RDDS), e.g., WHOIS provided over both port 43 and through a web based service;Registry Data Escrow.5. What kind of information is ICANN requesting and who should respond?Respondents should be parties interested in committing themselves as potential Emergency Back-End Registry Operators. The RFI covers numerous areas, but respondents should be prepared to discuss the following:Capabilities and experience in the critical registry functions;Registry Transition concepts, experience, SLAs, and use cases;Pricing models for providing critical registry functions;Profile of the respondents organization, leadership and resources.BackgroundIn April 2009, ICANN published the ICANN gTLD Registry Continuity Plan –http://www.icann.org/en/registries/continuity/. This document depicts a gTLD Registry Continuity Framework developed in collaboration with experienced gTLD, ccTLD registries and members of the technical community. The overall goals of ICANN's gTLD Registry Continuity Framework are:the protection of existing registrants; andto ensure confidence in the DNS.The Registry Continuity framework recognized the need for a prescribed ability to continue services in the event of a Registry Operator failure. It introduced the concept of a Back-End Operator and the intrinsic complications in a single back-up operator supporting all existing capabilities of different registry models. In view of those complications, the concept of identifying base level "critical functions", required to maintain the minimum operating services of a Top Level Domain, was established and defined.In May 2010 ICANN published a New Top-Level Domain Explanatory Memorandum "gTLD Registry Transition Processes Model" (RyTP) - http://www.icann.org/en/topics/new-gtlds/registry-transition-processes-clea… [PDF, 747 KB]. This document further elaborates on the concept of critical functions required for maintaining Top-Level Domain services and discusses the types of transitions between one Registry Operator and another. The concept of the Emergency Back-End Registry Operator was also introduced to support the TLD critical functions of failing Registry Operators, when there is no immediate assigned successor Registry Operator.Links to Relevant Information:New gTLD Program: http://www.icann.org/en/topics/new-gtld-program.htmgTLD Registry Continuity Document Archive: http://www.icann.org/en/registries/continuity/archive-en.htm Kindest Regards, Benedetta Rossi BC Secretariat

2 1

ALERTS from the Secretariat: Un petit déjeuner spécial sur le thème de la egouvernance
by Benedetta Rossi 15 Sep '11

15 Sep '11

http://www.icann.org/fr/announcements/announcement-14sep11-fr.htm Un petit déjeuner spécial sur le thème de la egouvernance14 septembre 2011Madame, MonsieurA l'occasion de sa venue à Paris, Renaissance Numérique a l'honneur de recevoir M. Rod Beckstrom, CEO de l'ICANN(Internet Corporation for Assigned Names and Numbers), auparavant directeur du Centre national de la cyber-sécurité aux Etats-Unis.Nous organisons pour l'événement un petit déjeuner spécial sur le thème de la egouvernance, le mercredi 21 septembre à 8h30, au restaurant Ladurée (16 rue Royale, 75008 Paris).Nous vous attendons nombreux pour cette occasion unique de rencontrer un spécialiste de la gouvernance d'internet.Pour des raisons logistiques, nous aurons besoin de savoir rapidement si vous serez présent ou absent.Dans cette attente nous nous tenons bien entendu à votre disposition.Renaissance Numérique tient également à remercier chaleureusement M. Christophe Ginisty qui nous a permis d'organiser cette rencontre.Bien à vous,Sophie ANDREChargée de missionRenaissance Numérique13, rue Eugène Flachat, 75017 ParisT: +33 (0)1 82 83 92 33 - M: +33 (0)6 49 81 77 89sophie(a)renaissancenumerique.orgwww.renaissancenumerique.org Kindest Regards, Benedetta Rossi BC Secretariat

1 0

ALERTS from the Secretariat: 2012 Will See One of the Biggest Changes in the History of the Internet. Are You Ready?
by Benedetta Rossi 15 Sep '11

15 Sep '11

2012 Will See One of the Biggest Changes in the History of the Internet. Are You Ready?14 September 2011In January 2012, companies, organisations, causes, start-ups and even cities will be able to apply for their own web domain. This represents a fundamental change to the way we use the Internet and many feel this will offer new global branding and marketing opportunities.Join the Internet Corporation for Assigned Names and Numbers (ICANN), overseers of the new domain application and approval process, for an informative and thought-provoking discussion on all aspects of the new Generic Top Level Domain (gTLD) program.For more information on ICANN's new gTLD program, please visit: http://www.icann.org/en/topics/new-gtlds/factsheet-new-gtld-program-20jul11… [PDF, 1.15 MB]Rod Beckstrom, CEO, ICANNLesley Cowley OBE, CEO, NominetLorna Gradden, Director, Com LaudeKevin Murphy, Journalist, Blogger & AnalystJonathan Hargreaves, Edelman (Chair)Date:Time: Venue:RSVP:Tuesday, 20th September 20118am - Breakfast8:30am - Panel Discussion and Q&A10am - CloseEdelman, Southside, 105 Victoria Street, London SW1E 6QTandrew.robertson(a)edelman.com http://www.icann.org/en/announcements/announcement-3-14sep11-en.htm Kindest Regards, Benedetta Rossi BC Secretariat

1 0

ICANN coms plan underway
by Chris Chaplow 14 Sep '11

14 Sep '11

Marilyn, In spite of much critism from Kieren and others on .nxt blog and twitter it looks to looks to me like the ICANN communications plan has started out to be more balanced and in line with BC position. I want to make clear that ICANN is an organization that is not advocating new gTLDs for anyone, said Beckstrom. Our role is merely facilitation to implement the policy and the programs approved by our community, so we are here to educate not to advocate. <http://www.icann.org/en/news/releases/release-12sep11-en.pdf> http://www.icann.org/en/news/releases/release-12sep11-en.pdf Perhaps helped by your breakfast with Barbara and my phone call with Scott. Scott Pinzon told me it was likely to be in two phases now to Dec 11 mostly directed applicants, Jan 12 onwards directed to users. best 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

Open Public Comments + Release of FY12 Op Plan and Budget Update
by Benedetta Rossi 14 Sep '11

14 Sep '11

Dear BC Members, Please find below the links to the currently open Public Comments from the ICANN web site: Open for Comments NowTitleClose Date [UTC Time]Post-Expiration Domain Name Recovery Recommendations for ICANN Board Consideration15 September 2011 [23:59]Phase II of Public Comments Process Enhancements30 September 2011 [23:59]Revisions to Conflicts of Interest Policy and Bylaws to Allow Board to Consider Compensation for Director Services3 October 2011 [06:59] Please also find below the updated FY12 Operating Plan and Budget, as published on the ICANN web site: http://www.icann.org/en/announcements/announcement-12sep11-en.htm Updated FY12 Operating Plan and Budget12 September 2011On 24 June 2011 in Singapore, the ICANN Board approved the FY12 Operating Plan and Budget [PDF, 2.08 MB] as noted in the Board resolutions posted at http://www.icann.org/en/minutes/resolutions-24jun11-en.htm.Based on the Board's decision to approve the launch of the New gTLD Program and to open the application window on 12 January 2012, the application processing now extends into the 2013 fiscal year. Therefore, it became obvious that including the New gTLD revenue and expenses across FY12 and FY13 presents a more accurate view of the overall FY12 budget, which can be seen in the documents below:A new schedule [PDF, 89 KB] which simply summarizes the consolidated budget detail into one table;A new schedule presenting the estimated cash flows for the New gTLD program [PDF, 120 KB], to include the processing of the 1st round applications over FY12 and FY13.Furthermore, a revised schedule of New gTLD program related expenses, the allocation by EAG (Expense Area Group), and a re-allocation of approved constituency funding from three At-Large regional meetings to one General Assembly are reflected in this updated FY12 Budget [PDF, 1.53 MB].Page 6 / Figure 1-2: revised table to reflect the breakdown of New gTLD program related expenses.Page 20 / Figure 4-2: revised table to reflect the re-allocation of the At-Large regional meeting funding from three meetings to one General Assembly.Page 62 /Figure 7-1: revised tables to reflect the breakdown of New gTLD program related expenses.Page 64 / Figure 7-2: revised tables to reflect the breakdown of New gTLD program related expenses.Page 79 /Figure C-2: revised tables to reflect updated allocation by Expense Area Group (EAG)Page 80 /Figure C-3: revised tables to reflect updated allocation by Expense Area Group (EAG)Throughout the year, up to date financial information, including the Board adopted FY12 Operating Plan and Budget, can be found on the ICANN Financial Information webpage. Kindest Regards, Benedetta Rossi BC Secretariat

2 1

FW: [council] Motion to Address the Remaining Registration Abuse Policies Working Group Recommendations
by Zahid Jamil 13 Sep '11

13 Sep '11

Sincerely, Zahid Jamil Barrister-at-law Jamil & Jamil Barristers-at-law 219-221 Central Hotel Annexe Merewether Road, Karachi. Pakistan Cell: +923008238230 Tel: +92 21 35680760 / 35685276 / 35655025 Fax: +92 21 35655026 <http://www.jamilandjamil.com/> www.jamilandjamil.com Notice / Disclaimer This message contains confidential information and its contents are being communicated only for the intended recipients . If you are not the intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete it from your system. The contents above may contain/are the intellectual property of DNDRC, and constitute privileged information protected by attorney client privilege. The reproduction, publication, use, amendment, modification of any kind whatsoever of any part or parts (including photocopying or storing it in any medium by electronic means whether or not transiently or incidentally or some other use of this communication) without prior written permission and consent of DNDRC is prohibited. From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Zahid Jamil Sent: 13 September 2011 02:12 To: council(a)gnso.icann.org; gnso.secretariat(a)gnso.icann.org; 'Glen de Saint Gery'; 'Glen de Saint Géry' Cc: 'Marika Konings'; 'John Berard' Subject: [council] Motion to Address the Remaining Registration Abuse Policies Working Group Recommendations Dear Councillors, Please find below a motion on RAP I am proposing for the next GNSO Council call: Motion to Address the Remaining Registration Abuse Policies Working Group Recommendations Whereas the Registration Abuse Policies (RAP) Working Group submitted its report to the GNSO Council on 29 May 2010 (see <http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf> http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf) Whereas the GNSO Council reviewed the report and its recommendations and decided to form 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 (see <http://gnso.icann.org/correspondence/rap-idt-to-gnso-council-15nov10-en.pdf > http://gnso.icann.org/correspondence/rap-idt-to-gnso-council-15nov10-en.pdf) ; Whereas the GNSO Council considered the proposed approached at its Working Session at the ICANN meeting in Cartagena; Whereas the GNSO Council acted on a number of RAP recommendations at its meeting on 3 February 2011 (see <http://gnso.icann.org/resolutions/#201102> http://gnso.icann.org/resolutions/#201102) Whereas the GNSO Council requested feedback from ICANN Compliance in relation to WHOIS Access recommendation #2 and Fake Renewal Notices recommendation #1 and a response was received on 23 February 2011 ( <http://gnso.icann.org/mailing-lists/archives/council/msg10766.html> http://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 considered the remaining RAP recommendations in further detail during its working session at the ICANN meeting in Singapore based on an overview prepared by ICANN Staff (see <http://gnso.icann.org/correspondence/overview-rapwg-recommendations-18may11 -en.pdf> http://gnso.icann.org/correspondence/overview-rapwg-recommendations-18may11- en.pdf). NOW THEREFORE BE IT: RESOLVED, the GNSO Council thanks the ICANN Compliance Department for its feedback in relation to WHOIS Access recommendation #2 and determines that no further work on this recommendation is needed. The GNSO Council welcomes the commitment of the ICANN Compliance Department to report on compliance activities and publish data about WHOIS accessibility, on at least an annual basis' (see (http://gnso.icann.org/mailing-lists/archives/council/msg10766.html) RESOLVED, the GNSO Council thanks the ICANN Compliance Department for its feedback in relation to Fake Renewal Notices recommendation #1 and determines that no further work on this recommendation is needed. RESOLVED, the GNSO Council determines that additional information is needed from the Registrar Stakeholder Group with regard to the conditional Fake Renewal Notices recommendation #2 before an Issue Report should be requested of Staff. The GNSO Council hereby requests that the Registrar Stakeholder Group provide further information and data on the nature and scope of the issue of Fake Renewal Notices to help inform the GNSO Councils and its RAP WG deliberations on whether an Issue Report should be requested. A small group of volunteers consisting of registrar representatives and others interested (including former RAP WG members) should be formed to prepare such a request, work with the Registrar Stakeholder Group to obtain the information requested and report back to the GNSO Council accordingly. RESOLVED, in response to WHOIS Access recommendation #1, the GNSO Council requests the WHOIS Survey Drafting Team to consider including the issue of WHOIS Access as part of the survey it has been tasked to develop. If the WHOIS Survey Drafting Team is of the view that it is not appropriate or timely to include WHOIS Access as part of the survey, it should inform the GNSO Council accordingly so that the GNSO Council can determine what next steps, if any, might be appropriate at this stage in relation to this recommendation. RESOLVED, with regard to the recommendation on Meta Issue: Collection and Dissemination of Best Practices, the GNSO Council acknowledges receipt of this recommendation and determines to defer its consideration until it evaluates the outcome of Malicious Use of Domain Names recommendation #1, which aims to develop best practices to help registrars and registries address the illicit use of domain names. In light of the pending request to Staff to develop a Discussion Paper on the Malicious Use of Domain Names, the GNSO Council believes that the upcoming review and analysis of this Discussion Paper may serve to inform the Council of the issues related to the Meta Issue: Collection and Dissemination of Best Practices recommendation. RESOLVED, in regard to the recommendations on cross-TLD Registration Scam and Domain Kiting/Tasting, the GNSO Council Chair shall communicate to the Security and Stability Advisory Committee (SSAC) the findings of the RAP WG in this regard and request that the SSAC consider evaluating and/or monitoring these abuses. If the SSAC elects to conduct this work, the GNSO Council requests that the SSAC inform the GNSO Council if it believes that further policy work by the GNSO Council should be undertaken to address these two types of abuse. In addition, the GNSO Council suggests that the issue of cross-TLD registration scam be included in the agenda of its next meeting with the ccNSO Council since this type of abuse may also affect ccTLDs. RESOLVED, in response to the recommendation on Meta Issue: Uniformity of Reporting, the GNSO Council acknowledges receipt of this recommendation, and hereby requests the ICANN Compliance Department to report on existing systems to report and track violations and/or complaints; improvements / changes made since the RAPWG Report or foreseen in the near future, and: identify gaps and any improvements that might be desirable but not foreseen at this stage. Further consideration of this Meta Issue, including the recommendations and considerations of the RAP WG in this regard, is deferred pending receipt of such information from the ICANN Compliance Department. RESOLVED, in response to the recommendation on Uniformity of Contracts, the GNSO Council requests an Issue Report to evaluate whether a minimum baseline of registration abuse provisions should be created for all in scope ICANN agreements, and if created, how such language would be structured to address the most common forms of registration abuse. RESOLVED, in response to the recommendations on Gripe Sites, Deceptive and/or Offensive Domain Names recommendation #2, and; Cybersquatting recommendation #2, since the RAPWG did not achieve consensus on these recommendations, the GNSO Council defers undertaking further policy work on these recommendations at this time. RESOLVED, in response to Gripe Sites; Deceptive and/or Offensive Domain Names recommendation #1, the GNSO Council acknowledges receipt of this recommendation, and agrees with the RAPWG that no further action is called for at this time. Sincerely, Zahid Jamil Barrister-at-law Jamil & Jamil Barristers-at-law 219-221 Central Hotel Annexe Merewether Road, Karachi. Pakistan Cell: +923008238230 Tel: +92 21 35680760 / 35685276 / 35655025 Fax: +92 21 35655026 <http://www.jamilandjamil.com/> www.jamilandjamil.com Notice / Disclaimer This message contains confidential information and its contents are being communicated only for the intended recipients . If you are not the intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete it from your system. The contents above may contain/are the intellectual property of DNDRC, and constitute privileged information protected by attorney client privilege. The reproduction, publication, use, amendment, modification of any kind whatsoever of any part or parts (including photocopying or storing it in any medium by electronic means whether or not transiently or incidentally or some other use of this communication) without prior written permission and consent of DNDRC is prohibited.

1 0

NOTE THE DATE: WEBINAR- JAS WG Final Report - 19 September 12:00 UTC & 22:00 UTC
by Benedetta Rossi 12 Sep '11

12 Sep '11

Dear BC Members, As BC Secretariat I will be forwarding announcements of particular BC relevance to the BC-GNSO list for your individual action and awareness. Kind Regards, Benedetta Rossi BC Secretariat JAS WG Final Report Webinar Please note the date and time, details about how to join the JAS WG Final Report webinar will follow later: Date: September 19th 2011.Times: 12:00 UTC and 22:00 UTC Time for each session: 90 minutesStructure: Adobe Connect with a slide presentation (ppt) along with a dial-in conference bridge for audio. Sessions are duplicated. Recorded.Intro/moderators: Carlton Samuels, Rafik Dammak, Karla Valente Speakers: Avri Doria and Alan Greenberg; members from the JAS WG for the Q&A session

1 0