July 2006 - council - lists.icann.org

Updated terms of reference for IDN-gTLDs policy development
by Bruce Tonkin July 27, 2006

July 27, 2006

Hello All, Below is an update of the terms of reference for further discussion on this list prior to the meeting next Thursday 3 August 2006. The updated terms of reference specifically address the work underway on new gTLDs in PDP-Dec05, so that the IDN PDP doesn't repeat work already undertaken. Regards, Bruce Tonkin Proposed Terms of Reference for Policy Development Relating to IDN at the Top-Level of the Domain Name System The following terms of reference for further work are focused on GNSO activities and therefore address gTLD considerations. Subsequent to working group assessment of the Preliminary Issues Report, they were adopted by the GNSO Council on xx August 2006. 1. Introduction of Generic Top-Level Domains with IDN Labels (IDN-gTLDs) a. Given the urgency of current interest in fully localized domain names, and the limited range of potential outcomes of the impending technical tests of devices for entering top-level IDN labels into the root zone, the policy for the inclusion of IDN-gTLDs can begin to be assessed. b. Assuming that top-level IDN labels will be added to the root zone, awaiting the outcome of the requisite initial trials, address the following additional terms of reference. 2. Selection Criteria for Top-Level Domains with IDN Labels a. Taking into account the background, considerations and findings regarding selection criteria in the New gTLD PDP [PDP-Dec05], develop modified or additional criteria for the inclusion of IDN labels in subsequent action toward ICANN's goals of expanding the use and usability of the Internet. 3. Allocation Methods for Top-Level Domains with IDN Labels a. Taking into account the background, considerations and findings regarding allocation methods in the New gTLD PDP [PDP-Dec05], develop modified or additional allocation methods that may be applied to gTLDs with IDN labels. 4. Policy to Guide Contractual Conditions for Top-Level Domains with IDN Labels a. Taking into account the background, considerations and findings regarding contractual conditions in the New gTLD PDP [PDP-Dec05], develop policies to guide the specific contractual criteria needed for gTLDs with IDN labels, to be made publicly available prior to any application rounds. 5. Additional Policy Considerations Regarding Top-Level Domains with IDN Labels a. Determining that a proposed new IDN label is adequately differentiated from a pre-existing label requires comparison in graphic, phonetic, and semantic terms. Two levels of differentiation are necessary, of which the one pertains to situations where the two labels are being considered for delegation to the same operator, and the other where the labels are to be delegated to independent registries. The former case can be further subdivided into two situations. In the one, the intention is for the same set of sub-domain names to appear under multiple TLD labels, and in the other independent name trees are to be established. b. With specific regard to the preceding point, determine whether the script used for an IDN-gTLD label can, or should, be exclusively propagated on all lower levels in the sub-domain tree (allowing for the general exceptions attaching to that script as referenced in the ICANN IDN Guidelines). If such a procedure is viable, intention to implement it may serve as a differentiation criterion or otherwise be invoked in the consideration of a request for a new label. c. Be particularly mindful of detail which, although initially considered in the IDN context, may otherwise be relevant to the New gTLD PDP. The association of two separate labels with the same TLD is an example of this, given that the linguistic justification for such action can as easily be derived from two languages that can be adequately represented using ASCII characters as it can from a situation where one or both labels requires IDN representation. d. The implementation of policies based on an aliasing mechanism (as implicit in Section 5a above) may require the development of new technical resources if the tests of the currently available alternatives (as referenced in Section 1a above) determine that none are viable. In general, care should be taken to recognize distinctions between technical and policy concerns, as well as cultural and political considerations. Addressing their manifold interdependencies should be approached as collaborative action with other organizations as appropriate to any given case.

1 0

Revised Draft minutes of the GNSO Council teleconference 20 July 2006
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG July 26, 2006

July 26, 2006

[council[at]gnso.icann.org] Dear Council Members, Please find the revised draft minutes of the GNSO Council teleconference held on 20 July 2006. Item 5: Update on PDP-Dec05 - new gTLDs (Correction in capitals)now reads: The INITIAL Report will be sent to the other Supporting Organisation, the GAC and the ALAC for review and comments. Thank you for picking this up Liz. Kind regards, Glen ----------------------------------------------------------------------- 20 July 2006 Proposed agenda and meeting documents List of attendees: Philip Sheppard - Commercial & Business Users C. Marilyn Cade - Commercial & Business Users C. Alistair Dixon - Commercial & Business Users C - absent - apologies Greg Ruth - ISCPC Antonio Harris - ISCPC - absent - apologies Tony Holmes - ISCPC Thomas Keller- Registrars Ross Rader - Registrars Bruce Tonkin - Registrars Ken Stubbs - gTLD registries June Seo - gTLD registries Cary Karp - gTLD registries Lucy Nichols - Intellectual Property Interests C - absent - apologies Ute Decker - Intellectual Property Interests C Kiyoshi Tsuru - Intellectual Property Interests C - absent - apologies Robin Gross - NCUC. Norbert Klein - NCUC. - absent - apologies Mawaki Chango - NCUC Sophia Bekele - Nominating Committee appointee - absent Maureen Cubberley - Nominating Committee appointee - absent - apologies Avri Doria - Nominating Committee appointee 14 Council Members ICANN Staff Denise Michel - Vice President, Policy Development Olof Nordling - Manager, Policy Development Coordination Liz Williams - Senior Policy Counselor Glen de Saint Géry - GNSO Secretariat GNSO Council Liaisons Suzanne Sene - GAC Liaison Bret Fausett - ALAC Liaison Quorum present at 12:07 UTC. MP3 Recording Bruce Tonkin chaired this meeting Approval of the agenda Marilyn Cade requested two topics under Any Other Business: 1. Council input to the ICANN strategic plan 2. Council input to the program committee for the ICANN meetings in Sao Paulo The Secretariat asked for approval of the GNSO Council minutes of 18 May 2006 and 28 June 2006 to be added to the agenda. Item 1: Update any statements of interest No updates noted Item 2: Approval of the GNSO Council minutes of 18 May 2006 and 28 June 2006. The minutes of the GNSO Council minutes of 28 June 2006 were deferred to the next Council meeting on 3 August 2006. Philip Sheppard moved for the adoption of the GNSO Council minutes of 18 May 2006. The adoption of the GNSO Council minutes of 18 May 2006 was unanimously approved. Decision 1: The GNSO Council minutes of 18 May 2006 adopted Item 3: Vote on tabled WHOIS motion from Marrakech Bruce Tonkin reminded Council that the motion in response to the extensive community and Government input on the definition of the purpose of WHOIS, based on the discussions at the Marrakech meeting, and seconded by Tony Holmes, had undergone further discussion on the GNSO council mailing list. Bruce Tonkin proposed withdrawing the motion on the table from the Marrakech meeting and replacing it with two separate motions: - one relating to the WHOIS service - one relating to the data that is collected by registrars. Motion One on the WHOIS service "The GNSO Council notes that the WHOIS definition approved by the GNSO Council on 18 April 06, as a working definition to allow the WHOIS task force to proceed with its work, is related to the service that provides public access to some of the data collected by registrars. It is not a definition of the purpose of the data collected by the registrars in the course of registering a domain name for their customers. In response to the extensive community and Government input on the definition of the purpose of WHOIS, the GNSO Council agrees to undertake the following steps: (1) Each Council member that voted in favour of the definition may provide a brief explanation of the reason for supporting the resolution and their understanding of its meaning. (2) The ICANN staff will provide a summary of the other interpretations of the definition that have been expressed during the public comment period, and subsequently in correspondence from the public and Governments. (3) The GNSO Council requests that the WHOIS task force continue with their work as specified in the terms of reference taking into account the recent input that has been provided. (4) The GNSO Council will take the Final Report (as specified in clause 9(c) of the GNSO PDP process) from the WHOIS task force after the task force finishes its work on all the terms of reference, engage in further dialogue with the Advisory Committees (including the GAC, SSAC and ALAC), and consider improving the wording of the WHOIS service definition so that it is broadly understandable. Note that the WHOIS Task force will produce a Task Force Report (as specified in clause 7(e) of the GNSO PDP process) later in 2006 that addresses all terms of reference. This report will be subject to a further public comment process, and the output of this public comment will be incorporated into the Final Report. Note that the previous clause (3) in the motion posted on 13 July 2006 that related to the purposes for collecting data is now the subject of a separate motion (see below)." Two friendly amendments were proposed: (a) by Cary Karp amending the language in (1) to read "Any Council member who.. " (b) by Bret Fausett, the ALAC Liaison to the GNSO Council, as ALAC had participated in the work of the WHOIS task Force, for the motion to include the option for an Advisory Committee that supports the current definition to also make a statement for the record through the appropriate liaison to the GNSO Council. The amendments were accepted and the motion proposed by Bruce Tonkin was seconded by Marilyn Cade. Discussion on the motion clarified the following areas: - The definition of the WHOIS service was consistent with theWHOIS Task Force Terms of Reference. - The definition refers to data that is made public, but some of the data collected to display via WHOIS , may be collected for other purposes. - There was uncertainty in the community why the council voted in favour of formulation 1, and while it was not possible for the Council as whole to give a response, the intent of the present motion was to give individual council members the opportunity to explain why they supported the motion. - Calling on an elected constituency representative to account individually for their vote retroactively caused some concern as some constituencies direct how their representatives should vote on a particular issue. A reference was made to the ICANN Board vote on the dotCOM agreement where members stated their reasons for their vote. Clarification was given that Board members had a standard procedure where after a formal vote, any Board member could voluntarily go on record and comment on their vote. It was generally accepted that at any time a Council member would have the opportunity to explain a vote via the public GNSO Council mailing list. It was also noted that several Council members may choose to make a joint statement. - The motion's intent was to direct the WHOIS task force to continue its work, while taking additional input into consideration. - The timeline mentioned in the motion referred to the' task force report' in the policy development process in the ICANN bylaws, which is the report that deals with the complete terms of reference and is published for public comment before the Final Report is produced. The expectation is that the task force report would be ready for public input at the Sao Paulo meetings, but this could be subject to change depending on the progress of the WHOIS task force. . The Government Advisory Committee should be made aware of the timeline and their assistance sought to accommodate the process. Philip Sheppard and Ross Rader both supported the motion and called the question: Bruce Tonkin seconded by Marilyn Cade proposed a motion on the WHOIS service: "The GNSO Council notes that the WHOIS definition approved by the GNSO Council on 18 April 06, as a working definition to allow the WHOIS task force to proceed with its work, is related to the service that provides public access to some of the data collected by registrars. It is not a definition of the purpose of the data collected by the registrars in the course of registering a domain name for their customers. In response to the extensive community and Government input on the definition of the purpose of WHOIS, the GNSO Council agrees to undertake the following steps: (1) Any Council member who voted in favour of the definition may provide a brief explanation of the reason for supporting the resolution and their understanding of its meaning. An Advisory Committee that supports the current definition may also make a statement for the record through the appropriate liaison to the GNSO Council. (2) The ICANN staff will provide a summary of the other interpretations of the definition that have been expressed during the public comment period, and subsequently in correspondence from the public and Governments. (3) The GNSO Council requests that the WHOIS task force continue with their work as specified in the terms of reference taking into account the recent input that has been provided. (4) The GNSO Council will take the Final Report (as specified in clause 9(c) of the GNSO PDP process) from the WHOIS task force after the task force finishes its work on all the terms of reference, engage in further dialogue with the Advisory Committees (including the GAC, SSAC and ALAC), and consider improving the wording of the WHOIS service definition so that it is broadly understandable. Note that the WHOIS Task force will produce a Task Force Report (as specified in clause 7(e) of the GNSO PDP process) later in 2006 that addresses all terms of reference. This report will be subject to a further public comment process, and the output of this public comment will be incorporated into the Final Report. Note that the previous clause (3) in the motion posted on 13 July 2006 that related to the purposes for collecting data is now the subject of a separate motion. The motion passed by voice vote. 20 votes in favour: Philip Sheppard, Marilyn Cade, Tony Holmes, Greg Ruth, Mawaki Chango, Robin Gross, Avri Doria, Ute Decker, Ken Stubbs, Cary Karp, June Seo, Bruce Tonkin, Ross Rader, Tom Keller. Council members absent who did not vote: Alistair Dixon, Tony Harris, Lucy Nichols, Kiyoshi Tsuru, Norbert Klein, Sophia Bekele, Maureen Cubberley. Decision 2: "The GNSO Council notes that the WHOIS definition approved by the GNSO Council on 18 April 06, as a working definition to allow the WHOIS task force to proceed with its work, is related to the service that provides public access to some of the data collected by registrars. It is not a definition of the purpose of the data collected by the registrars in the course of registering a domain name for their customers. In response to the extensive community and Government input on the definition of the purpose of WHOIS, the GNSO Council agrees to undertake the following steps: (1) Any Council member who voted in favour of the definition may provide a brief explanation of the reason for supporting the resolution and their understanding of its meaning. An Advisory Committee that supports the current definition may also make a statement for the record through the appropriate liaison to the GNSO Council. (2) The ICANN staff will provide a summary of the other interpretations of the definition that have been expressed during the public comment period, and subsequently in correspondence from the public and Governments. (3) The GNSO Council requests that the WHOIS task force continue with their work as specified in the terms of reference taking into account the recent input that has been provided. (4) The GNSO Council will take the Final Report (as specified in clause 9(c) of the GNSO PDP process) from the WHOIS task force after the task force finishes its work on all the terms of reference, engage in further dialogue with the Advisory Committees (including the GAC, SSAC and ALAC), and consider improving the wording of the WHOIS service definition so that it is broadly understandable. Note that the WHOIS Task force will produce a Task Force Report (as specified in clause 7(e) of the GNSO PDP process) later in 2006 that addresses all terms of reference. This report will be subject to a further public comment process, and the output of this public comment will be incorporated into the Final Report. Note that the previous clause (3) in the motion posted on 13 July 2006 that related to the purposes for collecting data is now the subject of a separate motion. Bruce Tonkin introduced the second motion and stated that it related to the data that is collected by registrars and what happened with that data collected. It was intended as a parallel activity to the WHOIS task force work. The definition of "Personal data" in clause 1.6 of the Registrar Accreditation Agreement: Personal data refers to any identified or identifiable natural person. It was noted that even a work address for a natural person could be considered as personal data. Bruce Tonkin, seconded by Marilyn Cade proposed the motion: "The GNSO Council notes that, consistent with generally accepted privacy principles, Registrars are required under clause 3.7.7.4 of the Registrar Accreditation Agreement to provide notice to each new or renewed Registered Name Holder stating: (i) The purposes for which any Personal Data collected from the applicant are intended; (ii) The intended recipients or categories of recipients of the data (including the Registry Operator and others who will receive the data from Registry Operator); (iii) Which data are obligatory and which data, if any, are voluntary; and (iv) How the Registered Name Holder or data subject can access and, if necessary, rectify the data held about them. To further understand the range of purposes for which data is intended, the GNSO proposes the following steps: (1) The ICANN staff will review a representative sample of registrar agreements with Registered Name Holders, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which registrars collect Personal Data in the course of registering a domain name for their customers. (2) The ICANN staff will review a representative sample of cctld registry or cctld registrar agreements with registrants, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which these organisations collect Personal Data from registrants. (3) The ICANN staff will summarise the current material that has resulted from WHOIS discussions since 2002 that document the current uses and abuses of the Personal Data that is currently made public through the WHOIS service. (4) Supported by the material produced in steps (1), (2) and (3) above, the Council will undertake a dialogue with the ICANN Advisory Committee's, such as the GAC, SSAC and ALAC, regarding the purposes for collecting Personal Data, and discuss whether any policy development is required in this area consistent with ICANN's mission and core values. The dialogue should seek to examine and understand consumer protection, privacy/data protection and law enforcement perspectives." The motion carried with a vote by acclamation. There were no abstentions and no votes against Decision 3: "The GNSO Council notes that, consistent with generally accepted privacy principles, Registrars are required under clause 3.7.7.4 of the Registrar Accreditation Agreement to provide notice to each new or renewed Registered Name Holder stating: (i) The purposes for which any Personal Data collected from the applicant are intended; (ii) The intended recipients or categories of recipients of the data (including the Registry Operator and others who will receive the data from Registry Operator); (iii) Which data are obligatory and which data, if any, are voluntary; and (iv) How the Registered Name Holder or data subject can access and, if necessary, rectify the data held about them. To further understand the range of purposes for which data is intended, the GNSO proposes the following steps: (1) The ICANN staff will review a representative sample of registrar agreements with Registered Name Holders, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which registrars collect Personal Data in the course of registering a domain name for their customers. (2) The ICANN staff will review a representative sample of cctld registry or cctld registrar agreements with registrants, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which these organisations collect Personal Data from registrants. (3) The ICANN staff will summarise the current material that has resulted from WHOIS discussions since 2002 that document the current uses and abuses of the Personal Data that is currently made public through the WHOIS service. (4) Supported by the material produced in steps (1), (2) and (3) above, the Council will undertake a dialogue with the ICANN Advisory Committee's, such as the GAC, SSAC and ALAC, regarding the purposes for collecting Personal Data, and discuss whether any policy development is required in this area consistent with ICANN's mission and core values. The dialogue should seek to examine and understand consumer protection, privacy/data protection and law enforcement perspectives." Item 4: Vote to initiate IDN-gTLD PDP [PDP-Jul06] - updated IDN issues report with proposed terms of reference to be provided by Olof Nordling by 13 July 06 Bruce Tonkin stated that there had been requests for more time to work on the IDN Issues Report and the proposed terms of reference before initiating a policy development process. Olof Nordling reported that the focus of the IDN Issues Report, since the Marrakech meeting, had been on the proposed terms of reference in preparation for approval at the current Council meeting. It was suggested that staff should work towards a substantive report representative of all workshops, historical materials on the topic and taking into account any input from councillors . The Constituencies are encouraged to reflect on what impact IDNs have on the current policy work on new gTLDs and whether the current policy assumptions are correct, because IDN based gTLDs are a subcategory of new gTLDs. The Council, in consultation with the constituencies should progress with parallel work on refining the terms of reference . A new draft of the terms of reference will be available by 27 July, 7 days before the next Council meeting on 3 August 2006 where a vote will be taken to initiate a policy development process. Item 5: Update on PDP-Dec05 - new gTLDs - confirm planning for face-to-face meeting Dr Liz Williams reported that the latest version of the New gTLDs report, which reflects the inputs from the GNSO public forum in Marrakech and other commentary from the 15 June meeting was being reviewed by Dan Halloran, deputy General Counsel. Council members should work closely with their constituencies to consult on the revised report which will be released in the week of 24 July, and bring the feed back to the face to face meeting in Amsterdam. Appropriate questions are being developed for a public comment period and Council members are encouraged to provide input. A face to face meeting for the committee for new gTLDs, open to interested observers, has been scheduled for 29, 30 and 31 August 2006, in Amsterdam. The Initial Report will be sent to the other Supporting Organisation, the GAC and the ALAC for review and comments. The Final report is targeted for presenting to the Board at the ICANN meetings in Sao Paulo. Dr. Liz Williams wished her thanks to be recorded to all those who had contributed and been closely involved in the process. Item 6: Update on PDP-Feb06 - Contractual conditions for existing gTLDs Dr Liz Willaims reported that the three actions items from the Marrakech meeting were underway: Release an updated version of report Propose a draft schedule Propose a series of materials The updated version of the Report on PDP-Feb06 - Contractual conditions for existing gTLDs which includes the input from the Marrakech meeting is being reviewed by Dan Halloran, deputy General Counsel, and will be released shortly. In the interim period, a request has been made for recommendations with respect to written materials and related experts. It is expected that at the end of September the impact of the expert materials on the preliminary report could be evaluated. An opportunity for a discussion or briefing from experts in this area required more work from the task force to identify where the specific input from specific people might fall. Marilyn Cade was not in agreement delaying this step and considered that access to advice and dialogue with anti-trust and competition experts earlier in the process, would be more advantageous. Dr. Liz Williams undertook to consult with the task force chair, Maureen Cubberley, on the issue of experts and the date for the next task force meeting. Item 7: Any other business: 7.1 Input to the ICANN Strategic plan Marilyn Cade called for a group of volunteers, comprising of councillors and constituency members who would be interested in collecting input in those areas of the ICANN strategic plan that impacted the Council to contact her off line. 7.2 ICANN meetings in Sao Paulo Council members should provide input for requirements during the Sao Paulo meetings. Bruce Tonkin suggested that two topics for discussion with the Government Advisory Committee would be new gTLDs and WHOIS. The Secretariat will enquire what visa arrangements ICANN is making for Brazil. Bruce Tonkin formally closed the meeting and thanked everybody for participating. The meeting ended: 13:59 UTC Next GNSO Council teleconference 3 August at 12:00 UTC see: Calendar -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

2 1

President's Strategy Committee Update - Output of Consultations
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG July 26, 2006

July 26, 2006

[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] http://www.icann.org/announcements/psc-output.html Please note the President's Strategy Committee Update - Output of Consultations In follow-up to the President's Strategy Committee consultations, please find the preliminary un-proofed version of the transcripts. A proofed version will be provided by the end of this week. The audio portion of the teleconference can be accessed via these links: Session 1, Session 2. -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

ICANN Announces the Implementation of the Process for Review of New gTLD Registry
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG July 26, 2006

July 26, 2006

http://www.icann.org/announcements/rsep-advisory-25jul06.htm Please note that ICANN Announces the Implementation of the Process for Review of New gTLD Registry Services Today ICANN announces the implementation of the consensus policy for review of new gTLD Registry Services and adoption of the Registry Services Evaluation Process. The effective date of the Policy is 15 August 2006. The implementation of this process includes an online tool (available for registry testing by 15 August) to facilitate submission of requests for new registry services to ICANN. 25 July 2006 -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

[Fwd: [gtld-council] Personalised website for Amsterdam hotel reservation]
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG July 24, 2006

July 24, 2006

Dear Council Members Please let me know who has been chosen from each constituency to benefit from the ICANN travel support. So far, only 2 constituencies have responded. Thank you. Kind regards, Glen -------- Original Message -------- Subject: [gtld-council] Personalised website for Amsterdam hotel reservation Date: Mon, 24 Jul 2006 17:39:31 +0200 From: GNSO.SECRETARIAT(a)GNSO.ICANN.ORG <gnso.secretariat(a)gnso.icann.org> To: gtld-council(a)gnso.icann.org [To gtld-council[at]gnso.icann.org] Dear All, Below are two urls pointing to a personalized web site, use either one, and make your own booking for the GNSO New gTLDs committee policy work on new gTLDs and IDNs to be held in Amsterdam on 29, 30 and 31 August 2006. Guests can access the site to learn more about the event and to book, modify, or cancel a reservation from July 24, 2006 to August 25, 2006 Access to the site is organized by guest type and can be obtained by going to the appropriate link below: Attendee ICANN (click here or cut/paste the following into a browser) http://www.starwoodmeeting.com/StarGroupsWeb/res?id=0607245015&key=434B4 Or Custom URL (click here or cut/paste the following into a browser) http://www.starwoodmeeting.com/Book/Icann1 The special ICANN rate is 165 Euros per night which includes breakfast but not city tax. Will those Council members, supported by ICANN for traveling costs and hotel accommodation, please complete the attached travel approval request form and give me their exact arrival and departure dates. I will take care of the hotel booking. If you have any questions, please let me know. Thank you very much. Kind regards, Glen -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Draft minutes of the GNSO Council teleconference 20 July 2006
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG July 24, 2006

July 24, 2006

[council[at]gnso.icann.org] Dear Council Members, Please find the draft minutes of the GNSO Council teleconference held on 20 July 2006. Please let me know what changes you would like made. Thank you very much. Kind regards, Glen ------------------------------------------------------------------- 20 July 2006 Proposed agenda and meeting documents List of attendees: Philip Sheppard - Commercial & Business Users C. Marilyn Cade - Commercial & Business Users C. Alistair Dixon - Commercial & Business Users C - absent - apologies Greg Ruth - ISCPC Antonio Harris - ISCPC - absent - apologies Tony Holmes - ISCPC Thomas Keller- Registrars Ross Rader - Registrars Bruce Tonkin - Registrars Ken Stubbs - gTLD registries June Seo - gTLD registries Cary Karp - gTLD registries Lucy Nichols - Intellectual Property Interests C - absent - apologies Ute Decker - Intellectual Property Interests C Kiyoshi Tsuru - Intellectual Property Interests C - absent - apologies Robin Gross - NCUC. Norbert Klein - NCUC. - absent - apologies Mawaki Chango - NCUC Sophia Bekele - Nominating Committee appointee - absent Maureen Cubberley - Nominating Committee appointee - absent - apologies Avri Doria - Nominating Committee appointee 14 Council Members ICANN Staff Denise Michel - Vice President, Policy Development Olof Nordling - Manager, Policy Development Coordination Liz Williams - Senior Policy Counselor Glen de Saint Géry - GNSO Secretariat GNSO Council Liaisons Suzanne Sene - GAC Liaison Bret Fausett - ALAC Liaison Quorum present at 12:07 UTC. MP3 Recording Bruce Tonkin chaired this meeting Approval of the agenda Marilyn Cade requested two topics under Any Other Business: 1. Council input to the ICANN strategic plan 2. Council input to the program committee for the ICANN meetings in Sao Paulo The Secretariat asked for approval of the GNSO Council minutes of 18 May 2006 and 28 June 2006 to be added to the agenda. Item 1: Update any statements of interest No updates noted Item 2: Approval of the GNSO Council minutes of 18 May 2006 and 28 June 2006. The minutes of the GNSO Council minutes of 28 June 2006 were deferred to the next Council meeting on 3 August 2006. Philip Sheppard moved for the adoption of the GNSO Council minutes of 18 May 2006. The adoption of the GNSO Council minutes of 18 May 2006 was unanimously approved. Decision 1: The GNSO Council minutes of 18 May 2006 adopted Item 3: Vote on tabled WHOIS motion from Marrakech Bruce Tonkin reminded Council that the motion in response to the extensive community and Government input on the definition of the purpose of WHOIS, based on the discussions at the Marrakech meeting, and seconded by Tony Holmes, had undergone further discussion on the GNSO council mailing list. Bruce Tonkin proposed withdrawing the motion on the table from the Marrakech meeting and replacing it with two separate motions: - one relating to the WHOIS service - one relating to the data that is collected by registrars. Motion One on the WHOIS service "The GNSO Council notes that the WHOIS definition approved by the GNSO Council on 18 April 06, as a working definition to allow the WHOIS task force to proceed with its work, is related to the service that provides public access to some of the data collected by registrars. It is not a definition of the purpose of the data collected by the registrars in the course of registering a domain name for their customers. In response to the extensive community and Government input on the definition of the purpose of WHOIS, the GNSO Council agrees to undertake the following steps: (1) Each Council member that voted in favour of the definition may provide a brief explanation of the reason for supporting the resolution and their understanding of its meaning. (2) The ICANN staff will provide a summary of the other interpretations of the definition that have been expressed during the public comment period, and subsequently in correspondence from the public and Governments. (3) The GNSO Council requests that the WHOIS task force continue with their work as specified in the terms of reference taking into account the recent input that has been provided. (4) The GNSO Council will take the Final Report (as specified in clause 9(c) of the GNSO PDP process) from the WHOIS task force after the task force finishes its work on all the terms of reference, engage in further dialogue with the Advisory Committees (including the GAC, SSAC and ALAC), and consider improving the wording of the WHOIS service definition so that it is broadly understandable. Note that the WHOIS Task force will produce a Task Force Report (as specified in clause 7(e) of the GNSO PDP process) later in 2006 that addresses all terms of reference. This report will be subject to a further public comment process, and the output of this public comment will be incorporated into the Final Report. Note that the previous clause (3) in the motion posted on 13 July 2006 that related to the purposes for collecting data is now the subject of a separate motion (see below)." Two friendly amendments were proposed: (a) by Cary Karp amending the language in (1) to read "Any Council member who.. " (b) by Bret Fausett, the ALAC Liaison to the GNSO Council, as ALAC had participated in the work of the WHOIS task Force, for the motion to include the option for an Advisory Committee that supports the current definition to also make a statement for the record through the appropriate liaison to the GNSO Council. The amendments were accepted and the motion proposed by Bruce Tonkin was seconded by Marilyn Cade. Discussion on the motion clarified the following areas: - The definition of the WHOIS service was consistent with theWHOIS Task Force Terms of Reference. - The definition refers to data that is made public, but some of the data collected to display via WHOIS , may be collected for other purposes. - There was uncertainty in the community why the council voted in favour of formulation 1, and while it was not possible for the Council as whole to give a response, the intent of the present motion was to give individual council members the opportunity to explain why they supported the motion. - Calling on an elected constituency representative to account individually for their vote retroactively caused some concern as some constituencies direct how their representatives should vote on a particular issue. A reference was made to the ICANN Board vote on the dotCOM agreement where members stated their reasons for their vote. Clarification was given that Board members had a standard procedure where after a formal vote, any Board member could voluntarily go on record and comment on their vote. It was generally accepted that at any time a Council member would have the opportunity to explain a vote via the public GNSO Council mailing list. It was also noted that several Council members may choose to make a joint statement. - The motion's intent was to direct the WHOIS task force to continue its work, while taking additional input into consideration. - The timeline mentioned in the motion referred to the' task force report' in the policy development process in the ICANN bylaws, which is the report that deals with the complete terms of reference and is published for public comment before the Final Report is produced. The expectation is that the task force report would be ready for public input at the Sao Paulo meetings, but this could be subject to change depending on the progress of the WHOIS task force. . The Government Advisory Committee should be made aware of the timeline and their assistance sought to accommodate the process. Philip Sheppard and Ross Rader both supported the motion and called the question: Bruce Tonkin seconded by Marilyn Cade proposed a motion on the WHOIS service: "The GNSO Council notes that the WHOIS definition approved by the GNSO Council on 18 April 06, as a working definition to allow the WHOIS task force to proceed with its work, is related to the service that provides public access to some of the data collected by registrars. It is not a definition of the purpose of the data collected by the registrars in the course of registering a domain name for their customers. In response to the extensive community and Government input on the definition of the purpose of WHOIS, the GNSO Council agrees to undertake the following steps: (1) Any Council member who voted in favour of the definition may provide a brief explanation of the reason for supporting the resolution and their understanding of its meaning. An Advisory Committee that supports the current definition may also make a statement for the record through the appropriate liaison to the GNSO Council. (2) The ICANN staff will provide a summary of the other interpretations of the definition that have been expressed during the public comment period, and subsequently in correspondence from the public and Governments. (3) The GNSO Council requests that the WHOIS task force continue with their work as specified in the terms of reference taking into account the recent input that has been provided. (4) The GNSO Council will take the Final Report (as specified in clause 9(c) of the GNSO PDP process) from the WHOIS task force after the task force finishes its work on all the terms of reference, engage in further dialogue with the Advisory Committees (including the GAC, SSAC and ALAC), and consider improving the wording of the WHOIS service definition so that it is broadly understandable. Note that the WHOIS Task force will produce a Task Force Report (as specified in clause 7(e) of the GNSO PDP process) later in 2006 that addresses all terms of reference. This report will be subject to a further public comment process, and the output of this public comment will be incorporated into the Final Report. Note that the previous clause (3) in the motion posted on 13 July 2006 that related to the purposes for collecting data is now the subject of a separate motion. The motion passed by voice vote. 20 votes in favour: Philip Sheppard, Marilyn Cade, Tony Holmes, Greg Ruth, Mawaki Chango, Robin Gross, Avri Doria, Ute Decker, Ken Stubbs, Cary Karp, June Seo, Bruce Tonkin, Ross Rader, Tom Keller. Council members absent who did not vote: Alistair Dixon, Tony Harris, Lucy Nichols, Kiyoshi Tsuru, Norbert Klein, Sophia Bekele, Maureen Cubberley. Decision 2: "The GNSO Council notes that the WHOIS definition approved by the GNSO Council on 18 April 06, as a working definition to allow the WHOIS task force to proceed with its work, is related to the service that provides public access to some of the data collected by registrars. It is not a definition of the purpose of the data collected by the registrars in the course of registering a domain name for their customers. In response to the extensive community and Government input on the definition of the purpose of WHOIS, the GNSO Council agrees to undertake the following steps: (1) Any Council member who voted in favour of the definition may provide a brief explanation of the reason for supporting the resolution and their understanding of its meaning. An Advisory Committee that supports the current definition may also make a statement for the record through the appropriate liaison to the GNSO Council. (2) The ICANN staff will provide a summary of the other interpretations of the definition that have been expressed during the public comment period, and subsequently in correspondence from the public and Governments. (3) The GNSO Council requests that the WHOIS task force continue with their work as specified in the terms of reference taking into account the recent input that has been provided. (4) The GNSO Council will take the Final Report (as specified in clause 9(c) of the GNSO PDP process) from the WHOIS task force after the task force finishes its work on all the terms of reference, engage in further dialogue with the Advisory Committees (including the GAC, SSAC and ALAC), and consider improving the wording of the WHOIS service definition so that it is broadly understandable. Note that the WHOIS Task force will produce a Task Force Report (as specified in clause 7(e) of the GNSO PDP process) later in 2006 that addresses all terms of reference. This report will be subject to a further public comment process, and the output of this public comment will be incorporated into the Final Report. Note that the previous clause (3) in the motion posted on 13 July 2006 that related to the purposes for collecting data is now the subject of a separate motion. Bruce Tonkin introduced the second motion and stated that it related to the data that is collected by registrars and what happened with that data collected. It was intended as a parallel activity to the WHOIS task force work. The definition of "Personal data" in clause 1.6 of the Registrar Accreditation Agreement: Personal data refers to any identified or identifiable natural person. It was noted that even a work address for a natural person could be considered as personal data. Bruce Tonkin, seconded by Marilyn Cade proposed the motion: "The GNSO Council notes that, consistent with generally accepted privacy principles, Registrars are required under clause 3.7.7.4 of the Registrar Accreditation Agreement to provide notice to each new or renewed Registered Name Holder stating: (i) The purposes for which any Personal Data collected from the applicant are intended; (ii) The intended recipients or categories of recipients of the data (including the Registry Operator and others who will receive the data from Registry Operator); (iii) Which data are obligatory and which data, if any, are voluntary; and (iv) How the Registered Name Holder or data subject can access and, if necessary, rectify the data held about them. To further understand the range of purposes for which data is intended, the GNSO proposes the following steps: (1) The ICANN staff will review a representative sample of registrar agreements with Registered Name Holders, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which registrars collect Personal Data in the course of registering a domain name for their customers. (2) The ICANN staff will review a representative sample of cctld registry or cctld registrar agreements with registrants, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which these organisations collect Personal Data from registrants. (3) The ICANN staff will summarise the current material that has resulted from WHOIS discussions since 2002 that document the current uses and abuses of the Personal Data that is currently made public through the WHOIS service. (4) Supported by the material produced in steps (1), (2) and (3) above, the Council will undertake a dialogue with the ICANN Advisory Committee's, such as the GAC, SSAC and ALAC, regarding the purposes for collecting Personal Data, and discuss whether any policy development is required in this area consistent with ICANN's mission and core values. The dialogue should seek to examine and understand consumer protection, privacy/data protection and law enforcement perspectives." The motion carried with a vote by acclamation. There were no abstentions and no votes against Decision 3: "The GNSO Council notes that, consistent with generally accepted privacy principles, Registrars are required under clause 3.7.7.4 of the Registrar Accreditation Agreement to provide notice to each new or renewed Registered Name Holder stating: (i) The purposes for which any Personal Data collected from the applicant are intended; (ii) The intended recipients or categories of recipients of the data (including the Registry Operator and others who will receive the data from Registry Operator); (iii) Which data are obligatory and which data, if any, are voluntary; and (iv) How the Registered Name Holder or data subject can access and, if necessary, rectify the data held about them. To further understand the range of purposes for which data is intended, the GNSO proposes the following steps: (1) The ICANN staff will review a representative sample of registrar agreements with Registered Name Holders, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which registrars collect Personal Data in the course of registering a domain name for their customers. (2) The ICANN staff will review a representative sample of cctld registry or cctld registrar agreements with registrants, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which these organisations collect Personal Data from registrants. (3) The ICANN staff will summarise the current material that has resulted from WHOIS discussions since 2002 that document the current uses and abuses of the Personal Data that is currently made public through the WHOIS service. (4) Supported by the material produced in steps (1), (2) and (3) above, the Council will undertake a dialogue with the ICANN Advisory Committee's, such as the GAC, SSAC and ALAC, regarding the purposes for collecting Personal Data, and discuss whether any policy development is required in this area consistent with ICANN's mission and core values. The dialogue should seek to examine and understand consumer protection, privacy/data protection and law enforcement perspectives." Item 4: Vote to initiate IDN-gTLD PDP [PDP-Jul06] - updated IDN issues report with proposed terms of reference to be provided by Olof Nordling by 13 July 06 Bruce Tonkin stated that there had been requests for more time to work on the IDN Issues Report and the proposed terms of reference before initiating a policy development process. Olof Nordling reported that the focus of the IDN Issues Report, since the Marrakech meeting, had been on the proposed terms of reference in preparation for approval at the current Council meeting. It was suggested that staff should work towards a substantive report representative of all workshops, historical materials on the topic and taking into account any input from councillors . The Constituencies are encouraged to reflect on what impact IDNs have on the current policy work on new gTLDs and whether the current policy assumptions are correct, because IDN based gTLDs are a subcategory of new gTLDs. The Council, in consultation with the constituencies should progress with parallel work on refining the terms of reference . A new draft of the terms of reference will be available by 27 July, 7 days before the next Council meeting on 3 August 2006 where a vote will be taken to initiate a policy development process. Item 5: Update on PDP-Dec05 - new gTLDs - confirm planning for face-to-face meeting Dr Liz Williams reported that the latest version of the New gTLDs report, which reflects the inputs from the GNSO public forum in Marrakech and other commentary from the 15 June meeting was being reviewed by Dan Halloran, deputy General Counsel. Council members should work closely with their constituencies to consult on the revised report which will be released in the week of 24 July, and bring the feed back to the face to face meeting in Amsterdam. Appropriate questions are being developed for a public comment period and Council members are encouraged to provide input. A face to face meeting for the committee for new gTLDs, open to interested observers, has been scheduled for 29, 30 and 31 August 2006, in Amsterdam. The Final report will be sent to the other Supporting Organisation, the GAC and the ALAC for review and comments. The Final report is targeted for presenting to the Board at the ICANN meetings in Sao Paulo. Dr. Liz Williams wished her thanks to be recorded to all those who had contributed and been closely involved in the process. Item 6: Update on PDP-Feb06 - Contractual conditions for existing gTLDs Dr Liz Willaims reported that the three actions items from the Marrakech meeting were underway: Release an updated version of report Propose a draft schedule Propose a series of materials The updated version of the Report on PDP-Feb06 - Contractual conditions for existing gTLDs which includes the input from the Marrakech meeting is being reviewed by Dan Halloran, deputy General Counsel, and will be released shortly. In the interim period, a request has been made for recommendations with respect to written materials and related experts. It is expected that at the end of September the impact of the expert materials on the preliminary report could be evaluated. An opportunity for a discussion or briefing from experts in this area required more work from the task force to identify where the specific input from specific people might fall. Marilyn Cade was not in agreement delaying this step and considered that access to advice and dialogue with anti-trust and competition experts earlier in the process, would be more advantageous. Dr. Liz Williams undertook to consult with the task force chair, Maureen Cubberley, on the issue of experts and the date for the next task force meeting. Item 7: Any other business: 7.1 Input to the ICANN Strategic plan Marilyn Cade called for a group of volunteers, comprising of councillors and constituency members who would be interested in collecting input in those areas of the ICANN strategic plan that impacted the Council to contact her off line. 7.2 ICANN meetings in Sao Paulo Council members should provide input for requirements during the Sao Paulo meetings. Bruce Tonkin suggested that two topics for discussion with the Government Advisory Committee would be new gTLDs and WHOIS. The Secretariat will enquire what visa arrangementsICANN is making for Brazil. Bruce Tonkin formally closed the meeting and thanked everybody for participating. The meeting ended: 13:59 UTC Next GNSO Council teleconference 3 August at 12:00 UTC see: Calendar -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Fwd: [council] Motions passed by the GNSO Council on 20 July 2006
by Sophia B July 21, 2006

July 21, 2006

---------- Forwarded message ---------- From: Sophia B <sophiabekele(a)gmail.com> Date: 21-Jul-2006 13:46 Subject: Re: [council] Motions passed by the GNSO Council on 20 July 2006 To: Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> Dear All, I am sorry I was not able to attend the meeting yesterday. I has the date mixed up for today as I am in Addis Ababa. In any case I have received the MP3 and will provide my input accordingly. Respectfully, Sophia On 21/07/06, Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> wrote: > > > Hello All, > > > > > (1) Any Council member who voted in favour of the definition may > > provide a brief explanation of the reason for supporting the > > resolution and their understanding of its meaning. > > > > Note the motion was amended to include the option for an Advisory > Committee that supports the current definition to also make a statement > for the record through the appropriate liaison to the GNSO Council. > This amendment was requested by Bret Fausett, the ALAC Liaison to the > GNSO Council, as ALAC has participated in the work of the WHOIS task > Force. > > Regards, > Bruce Tonkin > >

1 0

travel request form
by Denise Michel July 21, 2006

July 21, 2006

Attached. Denise Denise Michel Vice President, Policy Development ICANN denise.michel(a)icann.org

1 0

Travel support for Amsterdam GNSO Council meeting
by Denise Michel July 21, 2006

July 21, 2006

In order to facilitate GNSO's policy development activities, ICANN will provide travel support for the Amsterdam GNSO Council meeting (29 - 31 August) for one representative of each GNSO constituency, the NomCom-appointed Council members, the GNSO Liaisons, and the Chair, as needed. The terms of this travel support are outlined below and will be coordinated by Glen. Please contact her directly as soon as possible. Regards, Denise Denise Michel Vice President, Policy Development ICANN denise.michel(a)icann.org 1. Designated Council members need to contact Glen directly to confirm travel support. Each traveler must complete a travel request form (attached) outlining: • Dates of departure and return • Destination • Purpose of trip • Estimated costs • Projected outcomes Email completed forms to Glen, who will facilitate ICANN approval. 2. Once your travel is approved, please contact ICANN's travel agent directly to arrange for the booking and purchase of your airline ticket: Nadine Davidson TravelStore Platinum 11601 Wilshire Blvd. Ste. 325 Los Angeles, CA 90025 USA (310)575-5540 x 15419 (310)575-5541 fax Nadine.D(a)TravelStoreUSA.com If other travel arrangements are needed (train, etc.), please alert Glen. Glen will provide you additional information on hotel reservations and payment. 3. ICANN will pay for the following: • Economy-class travel booked by an ICANN travel agent or by the traveler at the lowest possible cost; • Accommodations at a hotel pre-selected by ICANN. All other costs will be borne by the traveler including meals, local travel and related incidentals. In the case of an upgrade, ICANN will pay up to the cost of an economy-class ticket as quoted from an ICANN travel agent. In the case where two consecutive trips are taken (one funded by ICANN and one non-related/personal) ICANN will pay the lower of the two airline segments to and from the meeting or the equivalent of a round-trip economy-class ticket from the point of origin to the meeting. 4. Upon completion of the trip, each traveler is asked to acknowledge full participation in the Council meeting by sending a brief email to Glen describing the value realized from the trip, and providing any suggestions they may have for improving such meetings.

1 0

Draft GNSO Council Agenda for Thursday 3 August 2006
by Bruce Tonkin July 21, 2006

July 21, 2006

Draft Agenda for Council meeting - Thursday 3 August 2006 Coordinated Universal Time UTC 12:00 (5:00am Los Angeles, 8:00am Washington DC, 9:00am Buenos Aires, 13:00 London, 14:00 Brussels, 19:00 Phnom Penh, 22:00 Melbourne, 00:00 Auckland) Item 1: Update any statements of interest Item 2: Approval of Minutes - 28 June 2006 (http://www.gnso.icann.org/mailing-lists/archives/council/msg02685.html) - 20 July 2006 Item 3: Vote to initiate IDN-gTLD PDP [PDP-Jul06] - updated terms of reference to be posted to the mailing list by 27 July 2006 Item 4: Update on planning for Amsterdam meeting (29-31 August 2006) Item 5: Any other business Regards, Bruce Tonkin

1 0