July 2005 - council - lists.icann.org

More information about Venue address and shuttle service
by Maria Farrell 09 Jul '05

09 Jul '05

Dear all, For tomorrow's 1000 meeting, you'll need to take the 0900 shuttle to the convention centre as there is a break in shuttle service after this time. For Monday's breakfast meeting at 0730 in the convention centre, there won't be a shuttle that leaves in time (the first non-staff shuttle is at 0730), so you are advised to take taxis to the centre. All the best, Maria -----Original Message----- From: owner-gnso-dow123(a)icann.org [mailto:owner-gnso-dow123@icann.org] On Behalf Of GNSO.SECRETARIAT(a)GNSO.ICANN.ORG Sent: Saturday, July 09, 2005 1:32 PM To: gnso-dow123(a)gnso.icann.org Subject: [gnso-dow123] Venue address and shuttle service [To: Council[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org] [To: gnso-dow123[at]gnso.icann.org] For those of you attending the meetings in Luxembourg please note that to enter the ICANN meetings, you must come to the CC KIEM (Conference Centre Kiem) on Rue de Carlo Hemmer, which is on the back side of LuxExpo. This is where the hotel shuttles should arrive. If you are taking a taxi, make sure they take you to the correct entrance. At the following times, the shuttles will run every 10 minutes: 07.30-09.00 10.45-11.45 13.00-14.00 18.15-19.00 Between 14.00 and 18.15, there will be a shuttle on demand at the convention center for transport to the hotels. Shuttle service will continue less frequently until 8pm - the last shuttle returning to the hotels is 8pm. -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Convention centre address and shuttle service
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 09 Jul '05

09 Jul '05

[To: Council[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org] [To: gnso-dow123[at]gnso.icann.org] For those of you attending the meetings in Luxembourg please note that to enter the ICANN meetings, you must come to the CC KIEM (Conference Centre Kiem) on Rue de Carlo Hemmer, which is on the back side of LuxExpo. This is where the hotel shuttles should arrive. If you are taking a taxi, make sure they take you to the correct entrance. At the following times, the shuttles will run every 10 minutes: 07.30-09.00 10.45-11.45 13.00-14.00 18.15-19.00 Between 14.00 and 18.15, there will be a shuttle on demand at the convention center for transport to the hotels. Shuttle service will continue less frequently until 8pm - the last shuttle returning to the hotels is 8pm. -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Administration meeting with ICANN staff - 3pm Saturday Luxembourg conference centre
by Bruce Tonkin 09 Jul '05

09 Jul '05

Hello All, For those that are available (and have arrived in Luxembourg), I have called an administrative meeting with both the operational and policy development staff at 3pm today in the Luxembourg conference centre. The purpose of the meeting is to discuss in general how to improve the interactions between the GNSO policy council, ICANN operational staff responsible for GNSO issues, and ICANN policy development staff responsible for GNSO issues, and also to go through what is needed for the various policy meetings during the rest of this week. For those not able to make it, I will provide a summary of any outcomes from the meeting on Sunday morning. Regards, Bruce

1 0

GNSO and Whois task force meeting venues
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 09 Jul '05

09 Jul '05

[To: council and Whois task force] Saturday: the GNSO Council admin meeting for those councillors already in Luxembourg starts at 15:00 and will be in Salle C at the "Luxexpo" convention centre. Sunday: the GNSO Council admin meeting at 10:00 will be in Salle C. Monday: GNSO Breakfast at 7:30 will be in the "Bar" at the "Luxexpo" convention centre.Followed by the opening ceremony in the "Main room" and the constituency meetings. Tuesday: Whois task force meeting 7:30 to 8:30 will be in Salle E. Thursday: GNSO Council, Whois task force meetings will be in Salle A. Thank you! Glen -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

GNSO Public Forum and Council meeting Dial-in information 12 July
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 08 Jul '05

08 Jul '05

[To: council[at]gnso.icann.org] If you will not be physically present in Luxembourg there will be a telephone hook up for the GNSO Public Forum followed by the GNSO Council meeting on Tuesday 12 July ( see below for starting times) DURATION: 4 hr LEADER: MS GLEN DE SAINT GERY USA Toll Free Number: 888-469-0489 USA Toll Number: +1-517-308-9011 PASSCODE: COUNCIL California, USA UTC-8+1DST 5:30 Monterrey, Mexico UTC-6+1DST 7:30 Irving, Texas (CST) UTC-6+1DST 7:30 Washington DC, USA (EST) UTC-5+1DST 8:30 Buenos Aires, Argentina UTC-3+0DST 9:30 London, United Kingdom UTC+0+1DST 13:30 Brussels, Belgium (CET) UTC+1+1DST 14:30 Karlsruhe, Germany (CET) UTC+1+1DST 14:30 Zeist, Netherlands (CET) UTC +1+1DST 14:30 Stockholm, Sweden (CET) UTC+1+1DST 14:30 Phnom Penh, Cambodia UTC+7+0DST 19:30 Melbourne, Australia UTC+10+0DST 22:30 Auckland, New Zealand UTC+12+0DST 00:30 Wednesday 13 July Please let me know whether you will be making use of this facility. Thank you very much. Kind regards, Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Letter from ICANN to registrars regarding approving the budget
by Bruce Tonkin 07 Jul '05

07 Jul '05

Hello All, I have attached a copy of a letter sent to registrars from ICANN seeking support for the registrar fee structure. It is written with registrars in mind, but does give a feel for what ICANN believes it has achieved in the past year, and what it is planning to do that has an impact on registrars. Regards, Bruce Tonkin 24 June 2005 To: registrar It has been a motivating and challenging year since we discussed the development of the present ICANN budget. At the outset, please let me express our gratitude for the Registrar expression of support for the budget and the ICANN model during the past year. We do not take for granted the fees paid by the Registrars and recognize the significance of those fees. We do not cash those checks believing they are our due but rather, we acknowledge that we must continually earn the right to receive those fees through ICANN's performance. We are writing to request that you provide your formal approval of the Registrar fee structure as defined in the ICANN fiscal year 2005-06 budget. As discussed last year, the fee structure described in the budget for the upcoming year remains the same as the previous year's budget. That is, the budget provides for a 25-cent (U.S.) per transaction fee and a flat fee of $3.8 million to be divided among all active Registrars. In addition, the flat $4000 annual accreditation fee remains in place. This flat fee will provide Registrar access to new registries as they are designated with a minimum administrative burden. ICANN has been receiving the higher level of revenue as provided in the new fee structure since March of this year. While we have only been receiving that new level of support for a few months, we are putting that money to work in the ways we discussed last year at this time. Initiatives =========== ICANN has posted a plan and procedures for contractual enforcement or compliance. We are presently in the process of hiring three positions to initially staff that function. In addition, we have devoted essentially a full-time equivalent to enforcement of the consensus based Inter- Registrar Transfer policy. This compliance function includes rectification of transfers improperly blocked, return of names transferred without proper authentication, and a report describing recommended improvements to the policy. The recommendations include increased flexibility in the policy where security would not be compromised and taking steps to improve the reliability of the transfer authentication. ICANN staff is spending considerable resources contributing to the study and prevention of domain name hijacking. The fruition of that work will be presented by SSAC in Luxembourg. We are also adding two full-time equivalents to respond to general Registrar requests in a timely manner. In addition, ICANN staff has devoted considerable time and study to the issues and potential abuses created by the "add-storm" surrounding the batch pool and the use of adds/deletes within the five-day grace period. There have been workshops and proposals describing potential solutions to both these issues, solutions in which market forces will continue to drive the business segments. ICANN will work with Registrars in order to timely implement a consensus based solution. ICANN is also designating new TLDs that are intended to open up the name space and create new market opportunities. Several new registries will be designated as a result of the recent sTLD round. ICANN has taken measures to ensure that the new sTLDs release names through accredited Registrars only in the same way as existing Registries do. In addition, this round of sTLD designations is serving to provide lessons for future rounds of gTLD designations. With the increased funding, ICANN is commissioning the studies necessary to determine under what conditions new TLDs can best be created to react to market forces rather than regulation. Additional effort is also being applied to the investigation of the stable deployment of full IDNs (or IDN.IDN registrations). We think that this effort will result in new markets for many accredited Registrars. A major feature of the .NET agreement is the stream-lined, tightly defined manner in which ICANN will consider new registry services for approval. This roadmap will provide better clarity and predictability to Registrars in determining how to approach proposed changes by registries and also how to effectively pursue changes that Registrars see as beneficial. One of the initiatives to be taken on immediately is the re-drafting of the Registrar Accreditation Agreement. ICANN staff has prepared an issues list for discussion with the Registrar constituency in Luxembourg. Responding to External Forces ============================= The Finance Committee members have reviewed the budget against our future goals. These goals are not only desires for improvements, they are requirements imposed by external organizations or forces. For example, ICANN is more than halfway into a three-year MoU with the U.S. Department of Commerce. That agreement specifies the path by which ICANN will become an independent organization. ICANN has satisfied 16 of 25 milestones on that path, all on or before the required deadlines. However, much work remains for the full completion of these tasks. Investment in infrastructure, contingency plan execution and business back-up agreements (to mention some) must be put into place before ICANN can become an independent entity. ICANN has also devoted some resources by becoming involved in the U.N.'s World Summit on an Information Society (WSIS). WSIS and the recognition that a viable ICANN model must involve stakeholders worldwide has lead ICANN to globalize its efforts with regard to ensuring stakeholder participation. To fail in either the MoU or in the WSIS environment may lead to a governance model different from one that encourages innovation and bottom-up consultation. This is why we believe investment in these areas is so important to ICANN, and also the Registrar community. Diversifying Sources of Funding =============================== Finally, ICANN continues to diversify its sources of funding. This year, the .NET registry agreement was re-written in several significant aspects. First, the successor registry, VeriSign, will pay fees to ICANN equal to 75-cents (U.S.) per registration-year. This is in-line with our discussions with Registrars last year that registry fees were, relatively speaking, too low when compare with the business models and fees paid by Registrars. While the altered funding scheme has not resulted in a proposal by ICANN to reduce Registrar fees at this writing, we expect that further diversification in the future will lead to opportunities for the Finance Committee to reconsider the quantum of Registrar fees. Conclusion and Next Steps ========================= We are pleased with the work so far, but realize that we have more to do. Everyone at ICANN recognizes the importance of the Registrar community in facilitating the development of effective new business models in the DNS and to ICANN itself. We have heard and considered your concerns, ideas, and views over the past year. We will continue to participate in meaningful dialogue on the issues affecting the Registrar community. We look forward to working with you into the future while we achieve mutual goals. Conversations with many Registrars regarding the new budget indicate that the approval process need not be the extended process that occurred last year. If you wish to signal your approval for the budget, please write an email or letter to Kurt Pritz, Vice President, Business Operations, indicating that the writer, an officer of the company empowered to do so, "approves the Registrar fee structure in the FY 2005-06 ICANN Proposed Budget". If you have any questions regarding the budget or ICANN's initiatives, please feel free to contact either Paul or Kurt Pritz directly. Thank you again for the time taken to read and consider this material. Sincerely, Paul Twomey, CEO Hagen Hultzsch, Chair, Board Finance Committee

1 0

ICANN Statement on London Bombings
by Bret Fausett 07 Jul '05

07 Jul '05

*http://www.icann.org STATEMENT CONCERNING LONDON BOMBINGS AND ICANN MEETING IN LUXEMBOURG* Friends and Colleagues, There have been multiple bomb blasts in London this morning. At the time of writing, it does not look like the airports have been hit, but clearly the public transport system in London itself has been. The advice we have received is that if you are transiting through London on the way to the ICANN meeting in Luxembourg, please do not go to central London. If you have a stopover, please stay at hotels at the airport or west of the city. At the moment the airports are not affected and we understand that flights are not being diverted but one should expect heightened security and hence delays at British airports. If members of the community have any questions, please direct them to traveltolux(a)icann.org Arrangements in Luxembourg continue as planned. Paul Twomey President & CEO /7 July 2005/

1 0

[Fwd: New TLDs Workshop Invitation]
by Glen De Saint Géry 06 Jul '05

06 Jul '05

Forwarded from Denise Michel Glen, Could you please send this New TLDs Workshop notice to your GNSO constituencies email list and ask them to share it with their members? Thanks. Denise michel(a)icann.org ========NOTICE============ INVITATION TO WORKSHOP ON NEW TOP LEVEL DOMAINS Your constituency members are invited to participate in the “Domain Name Users Workshop: New Top Level Domains" scheduled for Sunday, 10 July 2005, from 14:30 -17:00 in the LuxExpo's "Salle 10” room in Luxembourg City. All individuals interested in the current new sTLD process, and the issues that must be resolved to move forward on the introduction of new gTLDs, are encouraged to attend the Workshop. In addition to providing an overview of current activities and key stakeholder concerns and positions in this area, there will be an open discussion of how individual Internet users are affected by the introduction of new top level domains. The agenda is included below. We would appreciate it if you would post and distribute this invitation to your constituency members. Thank you for your assistance Sincerely, The At-Large Advisory Committee committee(a)alac.icann.org www.alac.icann.org ------------------------------------------- DOMAIN NAME USERS WORKSHOP: NEW TOP LEVEL DOMAINS Sunday, 10 July 2005 14:30 – 17:00 LuxExpo <http://www.icannluxembourg.org/en/Venue.php>, Luxembourg City Open discussion of how individual Internet users are affected by the introduction of new top level domains Sponsored by the ICANN At-Large Advisory Committee <http://www.alac.icann.org/> (ALAC) AGENDA *14:30 Welcome and Introductions* ~ Vittorio Bertola, Chair, ALAC *New Sponsored Top Level Domains (sTLDs)* ~ What are they? How are they chosen? When will they launch? What do they mean for individual Internet users? Can we expect more? ICANN’s Board has designated .JOBS and .TRAVEL as new sponsored top level domains (sTLDs), and five more applications are pending: .MOBI, .XXX, .CAT, .POST, .ASIA, .MAIL, .TEL-Pulver, and .TEL-Telnic. How will they benefit the world’s individual Internet users? What are their deployment plans, including initially-reserved names and registration of personal names? How will they apply internationalized domain names (IDNs)? What is their perspective on ICANN’s current sTLD process and what are their suggestions for ICANN’s future process for the introduction of new TLDs? *Introductions and Overview of the sTLD Process* ~ Bret Fausett, ALAC GNSO Liaison (Moderator) *New sTLD: .JOBS* ~ Ray Fassett, Executive VP, Operations & Policy, Employ Media LLC. *Pending sTLD:* *. XXX* ~ Stuart Lawley, Chairman, ICM Registry *Questions/Discussion* *New Generic Top Level Domains (gTLDs)* ~ How are they different from sTLDs? What process for introducing new gTLDs (or more sTLDs) would most benefit the world’s registrants ….and the world’s individual Internet users? How should ICANN promote such objectives as: registrant choice; value to individual Internet users; an open and competitive domain name market; TLD applications in major non-English languages; and a wider geographical distribution of TLD registries (to name a few)? ICANN’s Board designated seven new gTLDs in 2000: .AERO, .BIZ, .COOP, .INFO, .MUSEUM, .NAME, and .PRO. Since then, ICANN has been considering technical, economic, operational, legal, public policy and other issues involved in new TLDs, and has proposed a “New gTLD Implementation Strategy.” *Introductions and Overview of the gTLD Process* ~ Bret Fausett, ALAC Liaison (Moderator) *ICANN’s Strategy and Timeline for New gTLDs *~ Olof Nordling, Manager, ICANN *At-Large Advisory Cmt. Recommendations* ~ Wendy Seltzer, ALAC member (via phone) *Recommendations of Business/Intellectual Property/Internet Service Providers* ~ Philip Sheppard, member, Business Constituency and GNSO Council *Questions/Discussion* *Next Steps for At-Large Community *~ Bret Fausett, ALAC Liaison* *17:00 Close* -- Glen de Saint Géry ICANN glen[at]icann.org http://www.icann.org

1 0

Luxembourg Schedule modification
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 06 Jul '05

06 Jul '05

[To: council[at]gnso.icann.org; gnso-dow123[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org] Please note the gTLD Registries constituency will meet in Salle H on Monday 11 July Constituency day. The Gala dinner will be from 19:30 to 22:30 on Monday 11 July Please note the time of the GNSO Public Forum and the GNSO Council meeting on Tuesday 12 July 2005: 14:30-16:30 GNSO Public Forum Main room 16:30-18:30 GNSO Council Meeting Main room Thank you, See you there. Glen -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

FW: VeriSign's language on New Registry Services
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 06 Jul '05

06 Jul '05

Forwarded from Jeff Neuman -------- Original Message -------- Subject: FW: VeriSign's language on New Registry Services Date: Wed, 6 Jul 2005 08:47:53 -0400 From: Neuman, Jeff <Jeff.Neuman(a)neustar.us> To: GNSO.SECRETARIAT(a)GNSO.ICANN.ORG <gnso.secretariat(a)gnso.icann.org> CC: <bruce.tonkin(a)melbourneit.com.au> Glen, There seems to be no place to post this comment although I believe the Council should see this posting as it is extremely relevant now. I would have gotten it in during the comment period, but unfortunately, ICANN did not make the world aware of what it was doing for .net until after the comment period for registry services was over. Jeff ------------------------------------------------------------------------ *From:* Neuman, Jeff *Sent:* Tuesday, July 05, 2005 5:42 PM *To:* 'registry-services(a)icann.org' *Cc:* 'bruce.tonkin(a)melbourneit.com.au'; 'secretariat(a)gnso.icann.org'; 'Bhavin Turakhia' *Subject:* VeriSign's language on New Registry Services All, Enclosed is a compare version of VeriSign’s new .net agreement as compared with the draft that was posted in March. In light of the changes VeriSign got in its .net agreement, I believe that no further discussion should take place within the GNSO Council on the process for Registry Services other than all registries should have the same language as VeriSign’s .net agreement. Anything else, I believe is unacceptable and flies in the face of any notion of fair and free competition amongst the registries. Jeff (PLEASE NOTE THIS IS POSTED IN MY PERSONAL CAPACITY AND DOES NOT NECESSARILY REFLECT THE VIEW OF MY COMPANY) -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0