June 2009 - council - lists.icann.org

GNSO related Sydney Agenda ... UPDATE
by Glen de Saint Géry June 19, 2009

June 19, 2009

Dear All, Attached, please find the updated draft GNSO related meeting schedule for Sydney. Please note that on Saturday, except for the lunch time presentation 'GNSO Scope and Consensus' by Margie Milam and the Travel Drafting Group face to face meeting at 18:00, the times for the different topics related to new gTLDs may change. The meetings in room 5-6 will all be transcribed and there will be recordings available. This agenda is posted on pages: http://gnso.icann.org/index.html http://gnso.icann.org/calendar/#june This schedule should be read along with the full schedule on page: http://syd.icann.org/full-sched Please also consult the Wiki pages, for agendas and updates. All links are posted on http://gnso.icann.org/ Particularly https://st.icann.org/gnso-council/index.cgi?gnso_council_workspace Please let me know if you have any questions. Thank you, Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Draft GNSO Council minutes 28 May 2009
by Glen de Saint Géry June 15, 2009

June 15, 2009

Dear Councillors, Attached please find the draft GNSO Council minutes 28 May 2009. Please let me know if you would like any changes made. Thank you very much. kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Proposed GNSO Council Public Meeting Agenda, Sydney, 24 June 2009
by Glen de Saint Géry June 15, 2009

June 15, 2009

Proposed GNSO Council Public Meeting Agenda, Sydney, 24 June 2009 This agenda was established according to the Rules of Procedure for the GNSO Council Coordinated Universal Time 22:00 UTC 23 June - see below for local times Local time Sydney 08:00 (07:00 Los Angeles, 10:00 Washington DC, 15:00 London, 16:00 Brussels, 00:00 Melbourne next day) Avri Doria will be chairing the GNSO Council meeting Scheduled time for meeting 08:00 -12:30 Remote participation details sent individually to Council members . Item 0: Roll call of Council members (08:00- 08:30) Item 1: Update any statements of interest Item 2: Review/amend agenda Item 3: Post Expiration Domain Name Recovery - PDP WG Charter (08:30 - 09:00) - 3. 1 Explanation of Charter and Motions - 3. 2 Survey Council Positions - 3. 3 Open discussion - 3. 4 Vote on motion https://st.icann.org/gnso-council/index.cgi?24_june_09_motions Item 4: Inter-Registrar Transfer Policy (IRTP) Part B (09:00 - 10:30) - 4. 1 Staff update on issues report - 4. 2 Presentation of Motion - 4. 3 Council Positions - 4. 4 Open discussion - 4. 5 Vote on motion https://st.icann.org/gnso-council/index.cgi?24_june_09_motions Item 5: Internationalized Domain Names Group (IDNG) Charter (09:30 - 10:00) - 5. 1 Staff update on status and options - 5. 2 Council Positions - 5. 3 Open discussion - 5. 4 Vote on motion https://st.icann.org/gnso-council/index.cgi?24_june_09_motions Item 6: By-Law Changes (10:00 - 10:30) - 6. 1 Update on status and options - 6. 2 Council Positions - 6. 3 Open discussion - 6. 4 Vote on motion (if ready) https://st.icann.org/gnso-council/index.cgi?24_june_09_motions BREAK 10:30 - 11:00 Item 7: GNSO Improvements and Restructuring (11:00 - 11:30) - 7. 1 Policy Process Steering Committee (PPSC) and Operations Steering Committee (OSC) Activities including work team (WT) status - 7. 1. 1 Status Updates - 7. 1. 2 Q/A and Discussion - 7. 2 Update on constituency re-certification - 7. 2. 1 Status Updates - 7. 2. 2 Q/A and Discussion - 7. 3. Update on Stakeholder Group charters - 7. 3.1 Status Updates - 7. 3. 2 Q/A and Discussion - 7. 4. Guideline for Council Roles/Responsibilities - 7. 4. 1 To what extent is constituency review required Open Mike (11:30 - 12:30) (15:00 Los Angeles, 18:00 Washington DC, 23:00 London, Tuesday, 23 June 2009, 00:00 Brussels, 08:00 Melbourne Wednesday, 24 June 2009) -------------------------------------------------------------------------------------------- Local time between March and October, Summer in the NORTHERN hemisphere -------------------------------------------------------------------------------------------- Reference (Coordinated Universal Time) 22:00 UTC 23 June 2009 -------------------------------------------------------------------------------------------- California, USA (PDT) UTC-7+1DST 15:00 23 June New York/Washington DC, USA (EDT) UTC-4+1DST 18:00 23June Buenos Aires, Argentina UTC-3+0DST 19:00 23 June Rio de Janeiro, Brazil UTC-3+0DST 19:00 23 June London, United Kingdom (BST) UTC+1DST 23:00 23 June Brussels, Belgium (CEST) UTC+1+1DST 00:00 Paris, France (CEST) UTC+1+1DST 00:00 Barcelona, Spain (CEST) UTC+1+1DST 00:00 Karachi, Pakistan UTC+5+0DST 04:00 Hong Kong, China UTC+8+0DST 06:00 Singapore, Singapore UTC+8+0DST 06:00 Melbourne/Sydney, Australia (EST) UTC+10+0DST 08:00 ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of October 2009, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

motions for 24 april
by Avri Doria June 14, 2009

June 14, 2009

Hi, I have populated the wiki page https://st.icann.org/gnso-council/index.cgi?24_june_09_motions with the motions submitted by Tim as well as the motion for the Bylaws changes. There is also a place holder for the IDNG motion on its charter. We need to have all motions posted on the web before Tuesday, June 16, 2009 at 22:00:00 UTC in order to have them posted 7 days before the meeting in Sydney on Wednesday, June 24, 2009 at 8:00:00 AM. Amendments to these motions if any are needed can be added later, but I beleive it would be best to have them in place by the Tuesday UTC deadline. Tim, please check to make sure that I have transcribed your motions correctly - feel free to correct anything I got wrong (or let me know what I need to fix) thanks a.

2 2

Names for the ACSO meeting
by Avri Doria June 14, 2009

June 14, 2009

Hi, It is time again for me to collect 4 names, one from each of the SG that will be. The do not need to be council members, but they should be people with opinions on the subject being discussed. And should be people who are not afraid to peak their minds in an a wide and varied audience. The subject of the meeting is: Institutional Improvements The roles and responsibilities of ACs, SOs, Policy Staff and Board in ICANN's processes: current situation and possible evolutions The full discussion can be found at: http://syd.icann.org/node/3808 Note, there will be a preparation breakfast meeting on the Monday for the panelists and the various ACSO chairs/v-chairs. Please get me names as soon as possible as Kieren would like to be able to post the names of panelists. thanks a.

3 5

UPDATED Sydney Schedule
by Glen de Saint Géry June 12, 2009

June 12, 2009

Dear All, Attached, please find the updated draft GNSO related meeting schedule for Sydney. Please note that on Saturday, except for the lunch time presentation 'GNSO Scope and Consensus' by Margie Milam and the Travel Drafting Group face to face meeting at 18:00, the times for the different topics related to new gTLDs may change. The meetings in room 5-6 will all be transcribed and there will be recordings available. This schedule should be read along with the full schedule on page: http://syd.icann.org/full-sched Please note there may be other changes, but we will keep you apprised. Please also consult the Wiki pages, al links posted on http://gnso.icann.org/ for agendas and updates. Particularly https://st.icann.org/gnso-council/index.cgi?gnso_council_workspace Please let me know if you have any questions. 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

Public Comment: One & Two-Character Names in dot-travel
by Glen de Saint Géry June 12, 2009

June 12, 2009

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] News Alert http://www.icann.org/en/announcements/announcement-2-10jun09-en.htm ________________________________ Public Comment: One & Two-Character Names in dot-travel 10 June 2008 A new public comment period opens today for 30 days on a proposed amendment from Tralliance to Appendix 6 and 7 of the dot-travel Registry Agreement. On 18 May 2009, ICANN posted for public information a request submitted by Tralliance through the Registry Services Evaluation Process (RSEP). The request calls for a phased allocation process for one and two-character names in dot-travel. The Tralliance proposal is available at http://www.icann.org/registries/rsep/travel-18may09-en.pdf<http://www.icann.org/en/registries/rsep/travel-18may09-en.pdf>. As provided for by existing consensus policy (http://www.icann.org/en/registries/rsep/rsep.html) ICANN performed a preliminary review to determine whether the proposal might raise significant security, stability, or competition issues. ICANN's determination is that the proposal does not raise such issues. [Note that, from 13 June to 13 July 2008, ICANN conducted a public comment forum on a proposed single-character second-level domain names allocation framework (http://www.icann.org/en/registries/rsep/proposed-scsld-allocation-framework…) which supported the allocation single-character second-level domain names in existing registries and reviewed various allocation methods.] The proposal requires an amendment to the dot-travel Schedule of Reserved Names (Appendix 6) and a description of the phased allocation program is proposed to be inserted in Section 9 of Appendix 7. A copy of the proposed contract amendment is available here<http://www.icann.org/en/tlds/agreements/travel/proposed-amendment-10jun09.p…> [PDF, 20K]. Comments on the proposed amendment may be submitted to tralliance-amendment at icann.org<mailto:tralliance-amendment@icann.org> through 10 July 2009 23:59 UTC. Comments may be viewed at http://forum.icann.org/lists/tralliance-amendment/. All documentation related to the Tralliance proposal is available at http://www.icann.org/en/registries/rsep/#2009003. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

New gTLD Program Updates
by Glen de Saint Géry June 12, 2009

June 12, 2009

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] http://www.icann.org/en/announcements/announcement-3-10jun09-en.htm ________________________________ New gTLD Program Updates 10 June 2009 A ICANN offers a set of announcements for public discussion as meeting in Sydney nears. The announcements include: New Explanatory Memo for Pre-delegation Testing for New gTLDs The module 5 of the Draft Applicant Guidebook version 2 available since early February describes procedures applicable at the concluding stages of the gTLD application process, more specifically, a pre-delegation test addressing technical and other requirements the applicant will be asked to fulfill. ICANN is posting today the Pre-Delegation Testing explanatory memoranda<http://www.icann.org/en/topics/new-gtlds/pre-delegation-testing-08jun09-en.…> [PDF, 108K]. This explanatory memo has been incorporated to the following currently open public comment forum http://www.icann.org/en/topics/new-gtlds/comments-e-en.htm. The deadline for comments is 20 July 2009. The purpose of the pre-delegation technical test is to verify the applicant has met its commitment to establish registry operations in accordance with ICANN’s technical and operational criteria described in the Applicant Guidebook. The checks are also intended to ensure that the applicant can operate the gTLD in a stable and secure manner. There are three sets of tests or verification: DNS infrastructure testing and prerequisites, registry system testing and prerequisites, and an additional requirement to provide for continuity of basic registry operations. ICANN encourages comments on the interim language provided. The comments received will be considered for version 3 of the draft Applicant Guidebook, scheduled to be published in September 2009. IRT Report of Trademark Protection in New gTLDs Public Comment Period Extended The public comments period for the Final Report on Trademark Protection in New gTLDs<http://www.icann.org/en/topics/new-gtlds/irt-final-report-trademark-protect…> [PDF, 299K] prepared by the Implementation Recommendation Team (IRT) has been extended to July 6th, 2009. Malicious Behavior Overarching Issue The Anti-Phishing Working Group (APWG) has provided a working draft of their comprehensive ongoing study on the topic of potential malicious abuse of the DNS and new gTLD expansion. The draft report describes several issues and is available for review on the ICANN New gTLD Overarching Issues Wiki<https://st.icann.org/new-gtld-overarching-issues/index.cgi>. Recommended New gTLD Sessions during ICANN Sydney Meeting<http://syd.icann.org> The ICANN Meeting in Sydney (June 21 – 26) will have several New gTLD program sessions. The selection below is a recommendation only and we encourage the ICANN community to see the Sydney schedule for additional details. 21 June 2009 New gTLD Program Updates This session will provide an overview on the progress being made on the New gTLD Program. There will be an opportunity for public feedback. Workshop on Registry-Registrar Cross-Ownership One of the remaining issues to be resolved with regard to the New gTLD Applicant Guidebook is what restrictions should be imposed on new gTLD operators concerning the ownership or control of registrars. This Workshop will focus on potential harms and benefits associated with vertical integration of gTLD registries and registrars, and tools ICANN and the community could consider to attempt to address the issue. The workshop will include presentations from a panel of economists, plus an opportunity for comments from interested registries and registrars, other industry stakeholders, and the public. New gTLD Program: Managing a Registry: Best Practices At this session, few Top-Level Domain (TLD) Registry managers will share their experience discussing the practical aspects of managing a TLD Registry. This session will cover business, operational and technical aspects of day-to-day Registry management. Some of the topics covered will be: buy vs build; security and scalability considerations; channel management; TLD acceptance issues; IDNs management. June 24 2009 New gTLD Program – Consultation Session on Trademark Protection & Malicious Behavior This session is designed to discuss with the community two of the four overarching issues identified in the New gTLD Program: (a) trademark protection; (b) and potential for malicious behavior. This session will be divided in two parts: (1) Trademark Protection - a panel of experts will present and discuss with the community several proposed mechanisms for enhancing protection of intellectual property rights in the New gTLD Program; (2) Malicious Behavior – a panel of experts will provide the community with an update of work done to identify and mitigate potential increases in malicious conduct following the introduction of new gTLDs. Other New gTLD Related Events Sydney marks the first of a series of overarching issues consultation sessions ICANN staff is planning to conduct in June and July. The four overarching issues that were identified in the first two public comment periods of the Draft Applicant Guidebook (DAG) are: Trademark Protection; Malicious Behavior; Security & Stability; Scale & Demand (the economic impact of the new gTLDs). Upcoming live consultation sessions will be held in New York (July 13) and London (July 15). In addition to the overarching issues consultation sessions described above, ICANN will also be hosting live outreach/educational events and webinars to offer an introduction about New gTLDs, give up-to date program developments and make available relevant ICANN staff for face to face discussions. These events are designed in a wide range of formats to address different levels of knowledge. A pre-registrations page for these events will be made available soon. For updates, please go to the New gTLD Program page<http://www.icann.org/en/topics/new-gtld-program.htm>. Resources: New gTLD Program: http://www.icann.org/en/topics/new-gtld-program.htm Overarching Issues Wiki: https://st.icann.org/new-gtld-overarching-issues/index.cgi?new_gtld_overarc… Sydney Meeting: http://syd.icann.org/ Relevant Open Public Comments: Trademark Protection (IRT Final Report): http://www.icann.org/en/public-comment/public-comment-200906.html#irt-report Revised Excerpts of New gTLD Applicant Guidebook (DAG): http://www.icann.org/en/topics/new-gtlds/comments-e-en.htm New GTLDs and the Internet Openness Change Innovation After years of discussion and thought, new generic top-level domains (gTLDs) are being expanded. They will allow for more innovation, choice and change to a global Internet presently served by only 21 generic top-level domain names. As a not-for profit corporation dedicated to coordinating the Internet's addressing system, ICANN is not doing this to add to its revenue. An implementation plan is being developed with opportunities for public comment. There will be processes for objections. There has also been detailed technical scrutiny to ensure the Internet's stability and security. There will be an evaluation fee but it will recover costs only (expenses so far, application processing and anticipated legal costs). Promoting competition and choice is one of the principles upon which ICANN was founded. In a world with 1.5 billion Internet users (and growing), diversity, choice and innovation are key. The Internet has supported huge increases in choice, innovation and the competition of ideas, and expanding new gTLDs is an opportunity for more. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Per Diem payments for the Sydney Meeting
by Glen de Saint Géry June 11, 2009

June 11, 2009

To: Community members requesting information on Per Diems Cc: Those interested in ICANN's travel program (please forward if I missed anyone) Individual notifications will go out to individual travelers, but I promised to many of you an update by today on Sydney per diems to many of you, and.....here it is.... Special thanks to all of the community travelers for working with our ICANN travel support team to ensure that your trip to the ICANN Sydney meeting is as productive as possible. We believe that most rooms have been reserved and most air travel arrangements have been completed as well. Now, the key remaining action item is to process payments for meals, ground transportation and incidental expenses. For most of our supported travelers this means, per diem payments. We expect most per diem payments to be wire transferred or checks sent by close of business tomorrow in accordance with the specific requirements provided by the individual traveler, and calculated based upon the per diem guidelines (e.g., $95/ day x approved days for support). Each traveler who receives a payment will also receive an email notification. If you do not receive your payment after being notified by email (after a reasonable transit time of say, 5 business days), please contact us at ICANN travel, so that we can put a tracer for your payment. For those travelers who either cannot receive wire transfers or who have not provided proper payment detail information by our deadlines, will be eligible to receive a cash payment at the ICANN Sydney meeting. Details of the distribution times and procedures will be sent to those travelers individually. For those travelers who have other payment arrangements (such as those who receive payments after the ICANN meeting) will be handled accordingly. If you have any specific question about your travel situation, please continue to use our hotline: Constituency-Travel(a)icann.org<mailto:Constituency-Travel@icann.org>. Thank you Kevin

1 0

IRTP Part B Motions for action in Sydney
by Tim Ruiz June 11, 2009

June 11, 2009

I am making the following two motions regarding IRTP Part B (drafted in consultation with the Transfers WG) for consideration in Sydney. Seconds please. The motions are also attached as a doc file. Tim Motion I – Initiation of a PDP on IRTP Part B Whereas The Inter-Registrar Transfer Policy (IRTP) is an existing consensus policy under review by the GNSO, The GNSO Transfers Working Group identified a number of issues in its review of the current Policy and those issues have been grouped into suggested PDPs, set A-E, as per the Council's resolution of 8 May 2008, The GNSO Council, in order to be more efficient and hopefully reduce the overall timeline for addressing all the IRTP PDPs, resolved on 16 April 2009 to combine the issues outlined under the original issue set B, addressing three issues on undoing IRTP transfers, and some of the issues outlined in issue set C, related to registrar lock status into one IRTP Part B, The GNSO Issues Report Inter-Registrar Transfer Policy Part B was submitted to the GNSO Council on 15 May 2009, The Issues Report recommends that the GNSO Council proceed with a Policy Development Process limited to consideration of the issues discussed in this report, and The General Counsel of ICANN has indicated the topic is properly within the scope of the ICANN policy process and within the scope of the GNSO Resolved The GNSO will initiate a PDP on the issues defined in Inter Registrar Transfer Policy Issues Report Part B. A Working Group will be created for the purpose of fulfilling the requirements of the PDP. Motion II – Approval of a Charter for the IRTP Part B WG Whereas On [date] 2009 the GNSO Council initiated PDP IRTP Part B and, decided to create a PDP WG for the purposes of fulfilling the requirements of the PDP, and, The GNSO Council has reviewed the charter. Resolved The GSNO Council approves the charter and appoints Tim Ruiz confirmed as the GNSO Council Liaison to the IRTP PDP Part B WG. The GNSO council further directs that the work of the IRTP Part B WG be initiated no later then 14 days after the approval of this motion. Until such time as the WG can select a chair and that chair can be confirmed by the GNSO Council, the GNSO council Liaison shall act as interim chair. Charter The Working Group shall consider the following questions as outlined in the issues report and make recommendations to the GNSO Council: a) Whether a process for urgent return/resolution of a domain name should be developed, as discussed within the SSAC hijacking report (http://www.icann.org/announcements/hijacking-report-12jul05.pdf) see also (http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm) b) Whether additional provisions on undoing inappropriate transfers are needed, especially with regard to disputes between a Registrant and Admin Contact (AC). The policy is clear that the Registrant can overrule the AC, but how this is implemented is currently at the discretion of the registrar; c) Whether special provisions are needed for a change of registrant when it occurs near the time of a change of registrar. The policy does not currently deal with change of registrant, which often figures in hijacking cases; d) Whether standards or best practices should be implemented regarding use of a Registrar Lock status (e.g. when it may/may not, should/should not be applied); e) Whether, and if so, how best to clarify denial reason #7: A domain name was already in “lock status” provided that the Registrar provides a readily accessible and reasonable means for the Registered Name Holder to remove the lock status. Working Group processes: While the development of Guidelines for Working Group operations are still to be developed the following guidelines will apply to this WG: - The WG shall function on the basis of rough consensus, meaning all points of view will be discussed until the chair can ascertain that the point of view is understood and has been covered. Consensus views should include the names and affiliations of those in agreement with that view. Anyone with a minority view will be invited to include a discussion in the WG report. Minority report should include the names and affiliations of those contributing to the minority report. - In producing the WG report, the chair will be responsible for designating each position as having one of the following designations: --- Unanimous consensus position --- Rough consensus position - a position where a small minority disagrees but most agree --- Strong support but significant opposition --- Minority viewpoint(s) - If several participants in a WG disagree with the designation given to a position by the chair or any other rough consensus call, they can follow these steps sequentially: 1. Send email to the chair, copying the WG explaining why the decision is believed to be in error. 2. If the chair still disagrees, forward the appeal to the council liaison(s) to the group. The chair must explain his or her reasoning in the response. * If the liaisons support the chair's position, forward the appeal to the council. The liaison(s) must explain his or her reasoning in the response. 3. If the council supports the chair and liaison's position, attach a statement of the appeal to the board report. This statement should include all of the documentation from all steps in the appeals process and should include a statement from the council. - The chair, in consultation with the GNSO council liaison(s) is empowered to restrict the participation of someone who seriously disrupts the WG. Any such restriction will be reviewed by the GNSO council. Generally the participant should first be warned privately, and then warned publicly before such a restriction is put into place. In extreme circumstances this requirement may be bypassed. - The WG will have an archived mailing list. The mailing list will be open for reading by the community. All WG meetings will be recorded and all recordings will be available to the public. A IRTP PDP B mailing list has been created (Gnso-irtp-b-jun09(a)icann.org) and the public archives are at http://gnso.icann.org/mailing-lists/. - A SocialText wiki has been provided for WG usage and can be found at https://st.icann.org/irtp-partb/index.cgi?irtp_part_b - If the guidelines for WG processes change during the course of the WG, the WG may continue to work under the guidelines active at the time it was (re)chartered or use the new guidelines. - The council liaisons to the WG will be asked to report on the WG status monthly to the council. - All WG charters must be reviewed by the GNSO council every 6 months for renewal. Milestones - WG formed, chair & Council liaison & staff coordinator identified = T - Initial Report: T + 170 days - First comment period ends: T + 190 days - Preliminary Final Report: T + 220 days. Note: If the WG decides that a change is needed to the milestone dates, it should submit a revised time line to the GNSO council for approval

2 1

Board - Policy Staff - GNSO Council topics
by Avri Doria June 11, 2009

June 11, 2009

Hi, The top 2 topics were: 1. with 11 in favor: Critical Issues for new gTLDs - Geographic names at 1st and 2nd levels 2. with 10 in favor: Critical Issues for new gTLDs - The IRT Report and in third: 3. with 8 in favor: Restructuring issues: By-laws and Charters the other topics were distant also-ran with 0 and 2 votes. So have decided the number one issue: Critical Issues for new gTLDs - Geographic names at 1st and 2nd levels Will be the main topic at the dinner and the number 2 issue Critical Issues for new gTLDs - The IRT Report will be the dessert topic. I am assuming that the number 3 topic will be available for people who decide they have nothing further to say on the previous two topics or who are looking for some light banter during cocktails or in the bar after dinner, but will not schedule it for the dinner. I am hoping, however, there will be chance for all of the Stakeholder Groups to discuss their pending charters with the SIC and the Board at some time during the week in Sydney. With having resolved most of the issue on the By-Laws in the DT, I think the charter issues are largely SG specific in any case. Thanks for taking part in the poll. a.

1 0

PEDNR Charter and Motion for Council Action in Sydney
by Tim Ruiz June 10, 2009

June 10, 2009

Attached and copied below in text is the charter developed by the PEDNR Charter Drafting Team. I also make the motion stated in the Charter section just following the introductory comments. Tim Post-Expiration Domain Name Recovery - PDP Working Group Charter This charter is based on the GNSO Council decision to create a PDP WG to recommend best practices and/or consensus policies regarding the issues defined in the Post-Expiration Domain Name Recovery Issues Report at: http://gnso.icann.org/issues/post-expiration-recovery/report-05dec08.pdf The full resolution of the Council on 7 May 2009: Whereas on 05 December 2008, the GNSO received an Issues Report on Post-Expiration Domain Name Recovery (PEDNR); Whereas on 29 January 2009 the GNSO Council decided to form a Drafting Team (DT) to consider the form of policy development action in regard to PEDNR; Whereas a DT has formed and its members have discussed and reviewed the issues documented in the Issues Report; Whereas the DT has concluded that although some further information gathering may be needed, it should be done under the auspices of a PDP; Whereas staff has suggested and the DT concurs that the issue of registrar transfer during the RGP might be better handled during the IRTP Part C PDP. The GNSO Council RESOLVES To initiate a Policy Development Process (PDP) to address the issues identified in the Post-Expiration Domain Name Recovery Issues Report. The charter for this PDP should instruct the Working Group: that it should consider recommendations for best practices as well as or instead of recommendations for Consensus Policy; that to inform its work it should pursue the availability of further information from ICANN compliance staff to understand how current RAA provisions and consensus policies regarding deletion, auto-renewal, and recovery of domain names during the RGP are enforced; and that it should specifically consider the following questions: - Whether adequate opportunity exists for registrants to redeem their expired domain names; - Whether expiration-related provisions in typical registration agreements are clear and conspicuous enough; - Whether adequate notice exists to alert registrants of upcoming expirations; - Whether additional measures need to be implemented to indicate that once a domain name enters the Auto-Renew Grace Period, it has expired (e.g., hold status, a notice on the site with a link to information on how to renew, or other options to be determined). - Whether to allow the transfer of a domain name during the RGP. The GNSO Council further resolves that the issue of logistics of possible registrar transfer during the RGP shall be incorporated into the charter of the IRTP Part C charter. Charter Whereas: The GNSO council has decided to initiate a PDP on Post-Expiration Domain Name Recovery (PEDNR); and The GNSO council had decided against initiating a Task force as defined in the bylaw; The GNSO Council RESOLVES To form a Working Group composed of Constituency representatives as well as interested stakeholders in order to develop potential policy and/or best practices to address the issues covered, while seeking additional information as appropriate to inform the work. The WG will also be open to invited experts and to members or representatives of the ICANN Advisory Committees, whether acting in their own right or as representatives of their AC. The Working Group initially shall: 1. Pursue the availability of further information from ICANN compliance staff to understand how current RAA provisions and consensus policies regarding deletion, auto-renewal, and recovery of domain names following expiration are enforced; 2. Review and understand the current domain name life cycle; 3. Review current registrar practices regarding domain name expiration, renewal, and post-expiration recovery. The Working Group shall then consider the following questions: 1. Whether adequate opportunity exists for registrants to redeem their expired domain names; 2. Whether expiration-related provisions in typical registration agreements are clear and conspicuous enough; 3. Whether adequate notice exists to alert registrants of upcoming expirations; 4. Whether additional measures need to be implemented to indicate that once a domain name enters the Auto-Renew Grace Period, it has expired (e.g., hold status, a notice on the site with a link to information on how to renew, or other options to be determined); 5. Whether to allow the transfer of a domain name during the RGP. The Working Group is expected to organize an issue update / workshop at the Seoul meeting, in addition to an update to the GNSO Council. The Working Group should consider recommendations for best practices as well as or instead of recommendations for Consensus Policy. Working Group processes: While the development of Guidelines for Working Group operations are still to be developed the following guidelines will apply to this WG: - The WG shall function on the basis of rough consensus, meaning all points of view will be discussed until the chair can ascertain that the point of view is understood and has been covered. Consensus views should include the names and affiliations of those in agreement with that view. Anyone with a minority view will be invited to include a discussion in the WG report. Minority report should include the names and affiliations of those contributing to the minority report. - In producing the WG report, the chair will be responsible for designating each position as having one of the following designations: -- Unanimous consensus position -- Rough consensus position - a position where a small minority disagrees but most agree -- Strong support but significant opposition -- Minority viewpoint(s) - If several participants in a WG disagree with the designation given to a position by the chair or any other rough consensus call, they can follow these steps sequentially : 1. Send email to the chair, copying the WG explaining why the decision is believed to be in error. 2. If the chair still disagrees, forward the appeal to the council liaison(s) to the group. The chair must explain his or her reasoning in the response. * If the liaisons support the chair's position, forward the appeal to the council. The liaison(s) must explain his or her reasoning in the response. 3. If the council supports the chair and liaison's position, attach a statement of the appeal to the board report. This statement should include all of the documentation from all steps in the appeals process and should include a statement from the council. - The chair, in consultation with the GNSO council liaison(s) is empowered to restrict the participation of someone who seriously disrupts the WG. Any such restriction will be reviewed by the GNSO council. Generally the participant should first be warned privately, and then warned publicly before such a restriction is put into place. In extreme circumstances this requirement may be bypassed. - The WG will have an archived mailing list. The mailing list will be open for reading by the community. All WG meetings will be recorded and all recordings will be available to the public. A PEDNR WG mailing list has been created (gnso-pednr-dt(a)icann.org) with public archives at: http://forum.icann.org/lists/gnso-pednr-dt/. - A SocialText wiki has been provided for WG usage and can be found at https://st.icann.org/post-expiration-dn-recovery-wg/index.cgi?post_expirati… - If the guidelines for WG processes change during the course of the WG, the WG may continue to work under the guidelines active at the time it was (re)chartered or use the new guidelines. - The council liaisons to the WG will be asked to report on the WG status monthly to the council. - All WG charters must be reviewed by the GNSO council every 6 months for renewal. Milestones (dates to be updated if/when charter is approved) - WG formed, chair & Council liaison & staff coordinator identified = T - Initial Report: T + 150 - 170 days - First comment period ends: T + 170 - 200 days - Preliminary Final Report: T + 190 - 220 days. Note: If the WG decides that a change is needed to the milestone dates, it should submit a revised time line to the GNSO council for approval

1 0

ccNSO update
by Olga Cavalli June 10, 2009

June 10, 2009

Hi, Vanuatu (.vu) is now the 92nd member of the ccNSO. Also the Working Group 1 IDN ccPDP will schedule a face to face meeting in Sydney. GNSO participants in this WG are Edmond, myself, and Avri and Chuck as observers. Best regards, Olga -- Olga Cavalli, Dr. Ing. www.south-ssig.com.ar

1 0

With ATTACHMENT Working space available in Sydney on Saturday 20 June 2008
by Glen de Saint Géry June 10, 2009

June 10, 2009

Dear All, The GNSO has two working rooms in Sydney for Saturday 20 and Sunday 21 June 2009 meetings on level 2. One of these rooms, level 2 - Function room 2 is currently not being used on Saturday and would be available for any small groups to use. Attached for your convenience, is the draft schedule for the GNSO related events during the meeting. Please remember that the schedule may change Please let us know if you would like to take up this offer. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

With ATTACHMENT Working space available in Sydney on Saturday 20 June 2008
by Glen de Saint Géry June 10, 2009

June 10, 2009

Dear All, The GNSO has two working rooms in Sydney for Saturday 20 and Sunday 21 June 2009 meetings on level 2. One of these rooms, level 2 - Function room 2 is currently not being used on Saturday and would be available for any small groups to use. Attached for your convenience, is the draft schedule for the GNSO related events during the meeting. Please remember that the schedule may change Please let us know if you would like to take up this offer. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

AGP Limits Policy - Implementation Report
by Craig Schwartz June 10, 2009

June 10, 2009

Dear Councilors, Please find attached the first AGP Limits Policy Implementation Report. This report provides a status update on the implementation of the Policy since it was announced to the community on 17 December 2008. As always, please let me know if you have any questions about this information. Best, Craig _______________________ Craig Schwartz Chief gTLD Registry Liaison ICANN 1875 I Street, NW, Suite 501 Washington, DC 20006 Office +1 202.429.2703 www.icann.org

1 0

Clarified Technical Name Server Checks Published
by Glen de Saint Géry June 9, 2009

June 9, 2009

Council FYI Clarified Technical Name Server Checks Published 8 June 2009 ICANN has published a revised procedure, entitled "Technical requirements for authoritative name servers", on the IANA website. When a domain operator within an IANA-managed zone (such as a top-level domain operator) wishes to change their authoritative name server delegation details, ICANN performs technical checks against the proposed servers. These tests are designed to check minimal conformance with technical standards to ensure the domain will function correctly. The previous technical conformance criteria available on the IANA website were published in 2001, and did not comprehensively reflect current practice. Recognising the need for better documentation, staff also felt that the intent of the checks could be better fulfilled by implementing improved evaluation techniques. ICANN published the current set of tests performed and solicited public feedback on those tests. Useful contributions were received from many parties, both through the public comment period, and through subsequent discussions at operator forums. This feedback, particularly from the top-level domain operator community, formed the basis of the revised requirements. In the procedures, the technical checks performed are advisory. If the domain operator does not meet all the criteria, if they can show Internet stability is not harmed then the technical changes can still be accepted. Technical requirements for authoritative name servers http://www.iana.org/procedures/nameserver-requirements.html Call for public comments on technical check procedure http://www.icann.org/en/announcements/announcement-18aug06.htm Comments received during call for public comments http://forum.icann.org/lists/techcheck-comments/ Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Working space available in Sydney on Saturday 20 June 2008
by Glen de Saint Géry June 9, 2009

June 9, 2009

Dear All, The GNSO has two working rooms in Sydney for Saturday 20 and Sunday 21 June 2009 meetings on level 2. One of these rooms, level 2 - Function room 2 is currently not being used on Saturday and would be available for any small groups to use. Attached for your convenience, is the draft schedule for the GNSO related events during the meeting. Please remember that the schedule may change Please let us know if you would like to take up this offer. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Two-Week Countdown to Sydney!
by Glen de Saint Géry June 9, 2009

June 9, 2009

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] Two-Week Countdown to Sydney! 8 June 2009 ICANN's 35th International Public Meeting is just two weeks away. The conference will be held 21-26 June 2009 at the Hilton Sydney. A full schedule for the meeting, including a synopsis of each session being held throughout the week, is available on the ICANN Sydney Meeting website at http://syd.icann.org. Highlights Two main issues will likely dominate the conference: new generic Top-Level-Domains (gTLDs), and Internationalised Domain Names (IDNs). Workshops on the status of the new gTLD process, as well as the IDN Fast-Track process, will take place on Monday. A Joint AC/SO Meeting, in which representatives from ICANN's constituent groups will be discussing the roles and responsibilities of Advisory Committees, Supporting Organisations, Policy Staff and Board Members in ICANN's processes, is also on Monday's agenda . Other highlights include: the ccNSO Tech Day (Monday); an Improving Institutional Confidence Workshop (Wednesday); a forum on Abuse of the DNS (Thursday); and a public meeting of the Board's Public Participation Committee (Wednesday). Social events Two evenings of social events are also written into the calendar. Monday night will see a cocktail reception at the Hilton, followed by "restaurant night" on the waterfront in Sydney where several restaurants will offer a special 20% discount to ICANN Meeting attendees. On Wednesday, a Gala Event will be held at Sydney's Overseas Passenger Terminal - where the world's luxury liners dock - with a spectacular view across Sydney harbour to the famous Opera House and Bridge. An after-party will be held at The Argyle bar. Remote participation Are you unable to attend in person, but still wish to follow events online? You will find extensive remote participation tools on the meeting website at http://syd.icann.org. Most sessions will have live, multilingual audio streaming, web chat rooms, and downloadable presentations. The main room and all ccNSO events will be broadcast live using Adobe's Connect software, which allows you to not only hear and see what is going on in the room but also see the presentations, a real-time text transcript, and interact in a chatroom at the same time. To access the interactive room you just need to go to a given meeting's webpage and a single link will launch it (please note: this system may not work with all Linux users). For sessions outside those two rooms, visit the session's specific webpage from the schedule and you will be able to choose from listening to audio feeds in multiple languages, to interacting in live web chatrooms and/or downloading speaker presentations. If you wish to ask a question in the public forum on Thursday, visit our online question box at http://syd.icann.org/public-forum. General information Other information regarding Sydney itself, including suggestions on things to do, travel and visa issues, transportation, and tourist advice are all available on the Sydney meeting website at http://syd.icann.org. We look forward to seeing you there. ICANN Staff Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Clarified Technical Name Server Checks Published
by Glen de Saint Géry June 9, 2009

June 9, 2009

Clarified Technical Name Server Checks Published 8 June 2009 ICANN has published a revised procedure, entitled "Technical requirements for authoritative name servers", on the IANA website. When a domain operator within an IANA-managed zone (such as a top-level domain operator) wishes to change their authoritative name server delegation details, ICANN performs technical checks against the proposed servers. These tests are designed to check minimal conformance with technical standards to ensure the domain will function correctly. The previous technical conformance criteria available on the IANA website were published in 2001, and did not comprehensively reflect current practice. Recognising the need for better documentation, staff also felt that the intent of the checks could be better fulfilled by implementing improved evaluation techniques. ICANN published the current set of tests performed and solicited public feedback on those tests. Useful contributions were received from many parties, both through the public comment period, and through subsequent discussions at operator forums. This feedback, particularly from the top-level domain operator community, formed the basis of the revised requirements. In the procedures, the technical checks performed are advisory. If the domain operator does not meet all the criteria, if they can show Internet stability is not harmed then the technical changes can still be accepted. Technical requirements for authoritative name servers http://www.iana.org/procedures/nameserver-requirements.html Call for public comments on technical check procedure http://www.icann.org/en/announcements/announcement-18aug06.htm Comments received during call for public comments http://forum.icann.org/lists/techcheck-comments/ Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Public Comments: Proposal for the Systematization of the Organizational Review Processes
by Glen de Saint Géry June 9, 2009

June 9, 2009

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] Public Comments: Proposal for the Systematization of the Organizational Review Processes 9 June 2009 The Structural Improvements Committee of the Board has - among other duties - the responsibility of 'Reviewing, and suggesting changes as warranted to, ICANN's policies and processes governing organizational review'. In this role, and taking stock from the lessons learned in the recent past, the Structural Improvements Committee undertook an analysis of the processes, timeline and methodology of the Organizational Review activity, which is crucial for the organizational improvement of ICANN. Based on this analysis, the Structural Improvements Committee presents now for public comments its proposals for a systematization of the OR processes [PDF, 673K]. The paper analyses - for each of the phases making up the Organizational Review processes - the opportunities in revising the phases, their objectives, the lessons learnt, and proposals for their systematization. The adoption of the proposed processes since the present phases of the first round of ORs will contribute to enhance accountability and transparency of organizational reviews, to increase consultation with the communities under review, and to streamline key phases of the processes. A public comment period is now open until the 8 July 2009 to allow comments from the community and interested parties. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Presentation of the Second Interim Report of the Board Review Working Group, and Public Comment Period
by Glen de Saint Géry June 9, 2009

June 9, 2009

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] English Français Español Русский 日本語 Deutsch Português 한국어 Italiano Presentation of the Second Interim Report of the Board Review Working Group, and Public Comment Period 9 June 2009 ICANN appointed the Boston Consulting Group/Colin Carter & Associates to perform the external review of its Board of Directors; their review report http://www.icann.org/en/announcements/announcement-3-02nov08-en.htm#reports was presented at the Cairo meeting. A public comment period followed and comments were received. The Board review WG, having considered the Independent Reviewer's final report, Board input, and comments from stakeholders and the public, issued an Interim Report for consultation with the Community, which was presented at the ICANN meeting in Mexico City. This Interim Report presented the WG's "initial thinking" on the questions under review; then, a public comment period allowed for comments from interested parties. Following this second round of consultation the Board review WG continued its activity and presents now its second Interim Report. Most issues related to the external reviewer's report have been finalized, while the WG seeks further inputs from the community on three issues that remain outstanding, in view of the finalization of its report. This second Interim Report [PDF, 133K] will be presented at the Sydney meeting, and a public comment period is now open until the 5 July 2009. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

IRTP Part B PDP Wiki link
by Glen de Saint Géry June 9, 2009

June 9, 2009

Dear All, Just to inform you that the link to the IRTP Part B PDP Wiki pages is posted on page http://gnso.icann.org/ on the left hand navigation bar under the heading Wiki. https://st.icann.org/irtp-partb/index.cgi?irtp_part_b Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

New gTLDs – Final Reports Available on Competition and Pricing
by Glen de Saint Géry June 8, 2009

June 8, 2009

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] http://www.icann.org/en/announcements/announcement-06jun09-en.htm ________________________________ New gTLDs – Final Reports Available on Competition and Pricing 6 June 2009 ICANN posted today two reports relating to the introduction of new gTLDs, both by Dr. Dennis Carlton: * Report Of Dennis Carlton Regarding ICANN's Proposed Mechanism for Introducing New gTLDs<http://www.icann.org/en/topics/new-gtlds/carlton-re-proposed-mechanism-05ju…> [PDF, 628K], and * Comments on Michael Kende's Assessment of Preliminary Reports on Competition and Pricing<http://www.icann.org/en/topics/new-gtlds/carlton-re-kende-assessment-05jun0…> [PDF, 52K] Both reports are briefly summarized below. A public comment forum has been opened on these preliminary reports prepared by Professor Carlton for 45 days, until 20 July 2009. Post comments to competition-pricing-final(a)icann.org<mailto:competition-pricing-final@icann.org> and view comments at http://forum.icann.org/lists/competition-pricing-final. Summary: Report of Dennis Carlton Regarding ICANN's Proposed Mechanism for Introducing New gTLDs This report combines and updates Dennis Carlton's two preliminary reports from March 2009 that address ICANN's proposed mechanism for introducing new gTLDs. This paper analyzes, from an economic perspective, costs and benefits of ICANN's proposed introduction of new generic top level domain names (gTLDs) and addresses concerns raised by the Department of Justice and other parties about the ICANN proposal. The paper concludes that ICANN's proposed framework for introducing new gTLDs is likely to facilitate entry and benefit consumers by expanding output, lowering price and increasing innovation. Even if new gTLDs do not compete with .com and the other major TLDs for existing registrants, it is likely that consumers would nonetheless realize significant benefits due to increased competition for new registrants and increased product choice. Thus, evaluation of ICANN's proposal does not depend on addressing the extent of competition between existing TLDs, a question posed by the ICANN Board in 2006. While a variety of commenters have expressed concerns that the introduction of gTLDs will require trademark holders to undertake defensive registrations, alternative mechanisms for addressing such concerns are available. Several proposals are currently being reviewed by ICANN which may address these concerns while precluding the consumer harm that is likely to result from the draconian remedy of restricting entry of new gTLDs. The ability of ICANN to protect trademark holders through dispute resolution mechanisms also implies that price caps on new gTLDs are not necessary to protect trademark holders. Summary: Comments on Michael Kende's Assessment of Preliminary Reports on Competition and Pricing This paper responds to the report submitted on April 17, 2009 by Dr. Michael Kende, prepared on behalf of AT&T entitled "Assessment of ICANN Preliminary Reports on Competition and Pricing" which comments on Dennis Carlton's two preliminary reports submitted to ICANN in March 2009. In this reply, Carlton concludes that there is no basis for Dr. Kende's claim that the study of the scope of the market for registration services authorized by the ICANN Board in 2006 is necessary for evaluating ICANN's gTLD proposal. This is because, even if new gTLDs did not compete with .com and other major TLDs for existing registrants, new gTLDs would be expected to result in greater product choice and increased competition for new registrants. Additionally, Dr. Kende provides no basis for concluding that restricting the entry of new gTLDs is the best solution to trademark holders' concerns that new gTLDs will increase the need for defensive registrations. Alternative mech! anisms for protecting trademark holders are being reviewed by ICANN that are likely to protect trademark holders interests while preserving the benefits to consumers of entry. In addition, data presented by Dr. Kende appears to exaggerate the need for defensive registrations by failing to distinguish between productive supplemental registrations which attract and maintain traffic from those which are undertaken only to protect trademarks. Finally, this paper explains that there is no apparent basis for Dr. Kende's suggestion that the absence of price caps for new gTLDs will require elimination of price caps for existing TLDs. New GTLDs and the Internet Openness Change Innovation After years of discussion and thought, new generic top-level domains (gTLDs) are being expanded. They will allow for more innovation, choice and change to a global Internet presently served by only 21 generic top-level domain names. As a not-for profit corporation dedicated to coordinating the Internet's addressing system, ICANN is not doing this to add to its revenue. An implementation plan is being developed with opportunities for public comment. There will be processes for objections. There has also been detailed technical scrutiny to ensure the Internet's stability and security. There will be an evaluation fee but it will recover costs only (expenses so far, application processing and anticipated legal costs). Promoting competition and choice is one of the principles upon which ICANN was founded. In a world with 1.5 billion Internet users (and growing), diversity, choice and innovation are key. The Internet has supported huge increases in choice, innovation and the competition of ideas, and expanding new gTLDs is an opportunity for more. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Revised: Travel Support Community Feedback
by Glen de Saint Géry June 8, 2009

June 8, 2009

Forwarded from Kevin Wilson : Dear ICANN Community members interested in travel support guidelines: We have posted the draft Travel Support Guidelines<http://www.icann.org/en/announcements/announcement-03jun09-en.htm> which were developed based upon community feedback after the Mexico City meeting. Another online forum has been established, and there will be a workshop in Sydney<http://syd.icann.org/node/4035> on the subject. I know we are planning to meet with the GNSO Travel drafting team on Saturday at 18:00 in Sydney which is a different meeting from the Travel Workshop mentioned above. If you would like to schedule any other meeting/conference call with your constituency to discuss the draft Guidelines and answer any questions, please let me know. Best regard Kevin Wilson CFO ICANN Kevin.wilson(a)icann.org<mailto:Kevin.wilson@icann.org>

1 0