May 2005 - council - lists.icann.org

GNSO Council draft minutes 12 May 2005
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 24 May '05

24 May '05

[To: council[at]gnso.icann.org] Dear Council Members, Please find attached an html version of the draft minutes of the GNSO Council meeting held on 12 May 2005. This may be easier to read than the previous version sent to the council list earlier on. Please let me know if you would like any changes made. Thank you. Kind regards, -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

GNSO Council draft minutes 12 May 2005
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 24 May '05

24 May '05

[To: council[at]gnso.icann.org] Dear Council Members, Please find attached the draft minutes of the GNSO Council meeting held on 12 May 2005. Please let me know if you would like any changes made. Thank you. Kind regards, Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Draft Agenda for GNSO Council teleconference - Thursday 2 June 2005
by Bruce Tonkin 24 May '05

24 May '05

Draft Agenda for Council meeting Thursday 2 June 2005 Coordinated Universal Time UTC 12:00 (5:00 Los Angeles, 8:00 Washington DC, 14:00 Brussels, 22:00 Melbourne) Item 1: Approval of minutes Item 2: Staff report - current areas of work - WHOIS, new gtlds, transfers, IDNs - Update on .net agreement and new sponsored agreements - update on strategic/operational planning process - status of meeting agenda for Luxembourg Item 3: Approval of new terms of reference for combined WHOIS task force, and approval of membership and voting rules Item 4: Process for use by ICANN in considering requests for consent and related contractual amendments to allow changes in the architecture operation of a gTLD registry. - update Item 5: Transfers policy staff report - update Item 6: new gtlds - discuss next steps for staff to begin to develop issues reports Item 7: internationalised domain names - update Item 8: Comments on 2005/2006 budget/operational plan Item 9: Any other business

1 0

FW: ICANN Strategic Plan Process Comments
by Grant Forsyth 20 May '05

20 May '05

Fellow Councillors and other interested parties on the stratplan discussion list, Below is a posting made today as a further step in progress towards introducing a comprehensive bottom up strategic planning process to ICANN. As noted, those of us who are working to develop and document the consultation process, would welcome your comments and input to refine the process and settle it in time for consultation on the next cycle of strategic planning to commence at and post Luxembourg. Please feel free to post to any of the those individuals copied in on this email as well as/or alternately to the stratplan list. We also commend you posting comments on both the proposed process and substance of the latest version of the ICANN Strategic Plan, to the stratplan-revision list Regards Grant Forsyth Business Constituency Representative on the ICANN GNSO Council > -----Original Message----- > From: Grant Forsyth > Sent: Friday, 20 May, 2005 15:20 > To: 'stratplan-revision(a)icann.org' > Cc: 'Gomes, Chuck'; Marilyn Cade; Maureen Cubberley > Subject: ICANN Strategic Plan Process Comments > > Attached please find a paper that addresses the process for ongoing > consultation and review of the ICANN Strategic Plan. > This is work that originated in the discussions that were held in > Amsterdam in February 2005 and refined by consultation and discussions > between members of the various ICANN Support Organisations and in > particular through discussions held at the ICANN meeting in Mar del Plata > in April 2005. > > The main collaborative group of authors responsible for the work include: > Marilyn Cade > Maureen Cubberley > Chuck Gomes > Grant Forsyth > > Our wish is to have the process agreed prior to the next ICANN > face-to-face meeting in Luxembourg. The draft ICANN 2005-2006 budget has > just been released and is scheduled to be adopted by the Board at the > Luxembourg meeting. It is important that the consultation process be > understood and agreed prior to Luxembourg, in order that consultation on > the draft Budget can be received and considered prior to Luxembourg and > the review of the Strategic Plan can be finalized and started in July. > > > Grant Forsyth > Business Constituency Representative on the GNSO Council > <<ICANN Strategic Planning Process Proposal 050520.doc>>

2 1

ICANN has posted the proposed Budget for the FY 2005 -2006
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 18 May '05

18 May '05

[To:council[at]gnso.icann.org; ga[at]gnso.icann.org] [To:announce[at]gnso.icann.org;liaison6c[at]gnso.icann.org] FYI, ICANN has posted the proposed Budget for the Fiscal Year 2005 -2006 and invites public comment. http://www.icann.org/financials/proposed-budget-17may05.html In accordance with Article XVI, Section 4 of the ICANN Bylaws, ICANN today posted its Proposed Budget for fiscal year 2005-06. The budget will be submitted to the ICANN Board for approval in Luxembourg on 15 July 2005 after additional review by the Budget Advisory Group and Finance Committee, constituency reviews, public comment, and possible amendment. Comment can be made to budget-comments(a)icann.org. The archive of comments is available at <http://forum.icann.org/lists/budget-comments/>. Kind regards, 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

RE: [gnso-dow123] RE: [council] Third draft of WHOIS task force terms of reference
by Niklas_Lagergren＠mpaa.org 17 May '05

17 May '05

Dear All - I think the amendments put forward by Marilyn to Bruce's third draft make a lot of sense. By adding a few elements that I think can fairly be described as factual, it results in a draft ToR that could constitute a good basis for future work on the "WHOIS" topic. However - in order not to give the impression that the GNSO is ducking a crucial issue - I would suggest one additional amendment to Task (4) of the draft ToR, specifically to the first sentence of Task (4). See red-coloured addition below: "(4) Determine how to improve the process for notifying a registrar of inaccurate WHOIS data, and the processes for investigating and correcting inaccurate data and for preventing the initial collection of inaccurate data." I have also included this suggestion in the Word document circulated by Marilyn (see updated Word document in attachment). Many thanks to both Bruce and Marilyn for their work on this! Kind regards - Niklas _____ From: Marilyn Cade [mailto:marilynscade@hotmail.com] Sent: mardi 17 mai 2005 0:39 To: 'Bruce Tonkin'; council(a)gnso.icann.org Cc: gnso-dow123(a)gnso.icann.org Subject: [gnso-dow123] RE: [council] Third draft of WHOIS task force terms of reference Attached is a redline version of my BC proposal for changes to the Third version of the ToR. I made what I consider some factual additions to include the registered name holder. I also tried to make what I hope will make the ToR more broadly adoptable by using neutral terms in describing applicable and relevant law, etc., while still acknowledging privacy specifically. To the BC, there are many applicable and relevant laws, including those that deal with consumer protection, crimes, etc. that also have to be acknowledged, but I didn't spell those out... My interest is trying to get a neutral tone to that segment that can allow the TF work to move forward. I also put in a placeholder for the addition of the work items from the existing activities, that I believe that Jordyn and Maria were drafting. PLEASE NOTE, JUST IN CASE ANYONE HAS TROUBLE OPENING THE WORD DOCUMENT THAT THIS IS NOT A REDLINED VERSION BELOW. IT IS THE THIRD VERSION WITH MY PROPOSED ADDITIONS INCORPORATED -- ALL THE SYSTEM WOULD ALLOW ME TO DO, BUT I KNOW THAT SOME ARE TRAVELING AND MAY HAVE LIMITED ACCESS. ------------------------------------- Changes provided by Marilyn Cade, BC Councilor, as modifications to Bruce Tonkin's Third Draft of Terms of Reference for WHOIS task force The mission of The Internet Corporation for Assigned Names and Numbers ("ICANN") is to coordinate, at the overall level, the global Internet's systems of unique identifiers, and in particular to ensure the stable and secure operation of the Internet's unique identifier systems. ICANN has agreements with gTLDS registrars and gTLDS registries that require the provision of a WHOIS service via three mechanisms: port-43, web based access, and bulk access. The agreements also require a Registered Name Holder to provide accurate contact information for themselves, as well as technical and administrative contact information adequate to facilitate timely resolution of any problems that arise in connection with the Registered Name. A registrar is required in the Registrar Accreditation Agreement (RAA) to take reasonable precautions to protect Personal Data from loss, misuse, unauthorized access or disclosure, alteration, or destruction. The goal of the WHOIS task force is to improve the effectiveness of the WHOIS service in maintaining the stability and security of the Internet's unique identifier systems, whilst taking into account where appropriate the issues of privacy for the personal data of individuals that may be Registered Name Holders, or the administrative or technical contact for a domain name. Tasks: (1) Define the purpose of the WHOIS service in the context of ICANN's mission, relevant applicable international and national laws, including, but not limited to those regarding privacy, and the changing nature of Registered Name Holders. (2) Define the purpose of the registered name holder, technical and administrative contacts, in the context of the purpose of WHOIS, and the purpose for which the data was collected. Relevant definitions are taken from Exhibit C of the Transfers Task force report as a starting point (from http://www.icann.org/gnso/transfers-tf/report-exhc-12feb03.htm): "Contact: Contacts are individuals or entities associated with domain name records. Typically, third parties with specific inquiries or concerns will use contact records to determine who should act upon specific issues related to a domain name record. There are typically three of these contact types associated with a domain name record, the Administrative contact, the Billing contact and the Technical contact. Contact, Administrative: The administrative contact is an individual, role or organization authorized to interact with the Registry or Registrar on behalf of the Domain Holder. The administrative contact should be able to answer non-technical questions about the domain name's registration and the Domain Holder. In all cases, the Administrative Contact is viewed as the authoritative point of contact for the domain name, second only to the Domain Holder. Contact, Billing: The billing contact is the individual, role or organization designated to receive the invoice for domain name registration and re-registration fees. Contact, Technical: The technical contact is the individual, role or organization that is responsible for the technical operations of the delegated zone. This contact likely maintains the domain name server(s) for the domain. The technical contact should be able to answer technical questions about the domain name, the delegated zone and work with technically oriented people in other zones to solve technical problems that affect the domain name and/or zone." Contact: Domain Holder: The individual or organization that registers a specific domain name. This individual or organization holds the right o use that specific domain name for a specified period of time, provided certain conditions are met and the registration fees are paid. This person or organization is the "legal entity" bound by the terms of the relevant service agreements with the Registry operation of the TLD in question." (3) Determine what data collected should be available for public access in the context of the purpose of WHOIS. Determine how to access data that is not available for public access. The current elements that must be displayed by a registrar are: - The name of the Registered Name; - The names of the primary name server and secondary name server(s) for the Registered Name; - The identity of Registrar (which may be provided through Registrar's website); - The original creation date of the registration; - The expiration date of the registration; - The name and postal address of the Registered Name Holder; - The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the Registered Name; and - The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the Registered Name. (4) Determine how to improve the process for notifying a registrar of inaccurate WHOIS data, and the process for investigating and correcting inaccurate data. Currently a registrar must require a "Registered Name Holder [to] provide to Registrar accurate and reliable contact details and promptly correct and update them during the term of the Registered Name registration;" "shall abide by any specifications or policies established according to Section 4 requiring reasonable and commercially practicable (a) verification, at the time of registration, of contact information associated with a Registered Name sponsored by Registrar or (b) periodic re-verification of such information; " and "shall, upon notification by any person of an inaccuracy in the contact information associated with a Registered Name sponsored by Registrar, take reasonable steps to investigate that claimed inaccuracy. In the event Registrar learns of inaccurate contact information associated with a Registered Name it sponsors, it shall take reasonable steps to correct that inaccuracy." Insert here the relevant sections being drafted by Jordyn and Maria that captures the existing work. Submitted by Marilyn Cade, BC Councilor -----Original Message----- From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Bruce Tonkin Sent: Saturday, May 14, 2005 9:32 PM To: council(a)gnso.icann.org Cc: gnso-dow123(a)gnso.icann.org Subject: [council] Third draft of WHOIS task force terms of reference Hello All, Here is a third draft of the WHOIS terms of reference. The main changes are: - ICANN mission statement taken directly from ICANN bylaws - noting that there is a difference between the data collected and the display of that data (presently the agreements assume that everything collected will be publicly displayed - the new draft takes in account that in future some data that is collected may not be placed on public display), I have made it clearer that the present agreements require Registered Name Holders to provide certain data to the Registrar and keep it accurate, the Registrar is required to display this data as part of its WHOIS obligations. The purpose of the WHOIS service (ie the public display of data) is not clearly defined, but the purpose for which data is collected is indirectly defined in clause 3.7.7.3. - at the suggestion of the NCUC I have added the need to take into account international and national privacy laws when defining the purpose of WHOIS. Regards, Bruce Tonkin Third Draft of Terms of Reference for WHOIS task force The mission of The Internet Corporation for Assigned Names and Numbers ("ICANN") is to coordinate, at the overall level, the global Internet's systems of unique identifiers, and in particular to ensure the stable and secure operation of the Internet's unique identifier systems. ICANN has agreements with gtld registrars and gtld registries that require the provision of a WHOIS service via three mechanisms: port-43, web based access, and bulk access. The agreements also require a Registered Name Holder to provide accurate technical and administrative contact information adequate to facilitate timely resolution of any problems that arise in connection with the Registered Name. A registrar is required in the Registrar Accreditation Agreement (RAA) to take reasonable precautions to protect Personal Data from loss, misuse, unauthorized access or disclosure, alteration, or destruction. The goal of the WHOIS task force is to improve the effectiveness of the WHOIS service in maintaining the stability and security of the Internet's unique identifier systems, whilst taking into account where appropriate the need to ensure privacy protection for the Personal Data of individuals that may be Registered Name Holders, or the administrative or technical contact for a domain name. Tasks: (1) Define the purpose of the WHOIS service in the context of ICANN's mission, international and national laws protecting privacy, and the changing nature of Registered Name Holders. (2) Define the purpose of the technical and administrative contacts, in the context of the purpose of WHOIS, and the purpose for which the data was collected. Use the definitions from Exhibit C of the Transfers Task force report as a starting point (from http://www.icann.org/gnso/transfers-tf/report-exhc-12feb03.htm): "Contact: Contacts are individuals or entities associated with domain name records. Typically, third parties with specific inquiries or concerns will use contact records to determine who should act upon specific issues related to a domain name record. There are typically three of these contact types associated with a domain name record, the Administrative contact, the Billing contact and the Technical contact. Contact, Administrative: The administrative contact is an individual, role or organization authorized to interact with the Registry or Registrar on behalf of the Domain Holder. The administrative contact should be able to answer non-technical questions about the domain name's registration and the Domain Holder. In all cases, the Administrative Contact is viewed as the authoritative point of contact for the domain name, second only to the Domain Holder. Contact, Billing: The billing contact is the individual, role or organization designated to receive the invoice for domain name registration and re-registration fees. Contact, Technical: The technical contact is the individual, role or organization that is responsible for the technical operations of the delegated zone. This contact likely maintains the domain name server(s) for the domain. The technical contact should be able to answer technical questions about the domain name, the delegated zone and work with technically oriented people in other zones to solve technical problems that affect the domain name and/or zone." (3) Determine what data collected should be available for public access in the context of the purpose of WHOIS. Determine how to access data that is not available for public access. The current elements that must be displayed by a registrar are: - The name of the Registered Name; - The names of the primary nameserver and secondary nameserver(s) for the Registered Name; - The identity of Registrar (which may be provided through Registrar's website); - The original creation date of the registration; - The expiration date of the registration; - The name and postal address of the Registered Name Holder; - The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the Registered Name; and - The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the Registered Name. (4) Determine how to improve the process for notifying a registrar of inaccurate WHOIS data, and the process for investigating and correcting inaccurate data. Currently a registrar "shall, upon notification by any person of an inaccuracy in the contact information associated with a Registered Name sponsored by Registrar, take reasonable steps to investigate that claimed inaccuracy. In the event Registrar learns of inaccurate contact information associated with a Registered Name it sponsors, it shall take reasonable steps to correct that inaccuracy."

1 0

Third draft of WHOIS task force terms of reference
by Bruce Tonkin 17 May '05

17 May '05

Hello All, Here is a third draft of the WHOIS terms of reference. The main changes are: - ICANN mission statement taken directly from ICANN bylaws - noting that there is a difference between the data collected and the display of that data (presently the agreements assume that everything collected will be publicly displayed - the new draft takes in account that in future some data that is collected may not be placed on public display), I have made it clearer that the present agreements require Registered Name Holders to provide certain data to the Registrar and keep it accurate, the Registrar is required to display this data as part of its WHOIS obligations. The purpose of the WHOIS service (ie the public display of data) is not clearly defined, but the purpose for which data is collected is indirectly defined in clause 3.7.7.3. - at the suggestion of the NCUC I have added the need to take into account international and national privacy laws when defining the purpose of WHOIS. Regards, Bruce Tonkin Third Draft of Terms of Reference for WHOIS task force The mission of The Internet Corporation for Assigned Names and Numbers ("ICANN") is to coordinate, at the overall level, the global Internet's systems of unique identifiers, and in particular to ensure the stable and secure operation of the Internet's unique identifier systems. ICANN has agreements with gtld registrars and gtld registries that require the provision of a WHOIS service via three mechanisms: port-43, web based access, and bulk access. The agreements also require a Registered Name Holder to provide accurate technical and administrative contact information adequate to facilitate timely resolution of any problems that arise in connection with the Registered Name. A registrar is required in the Registrar Accreditation Agreement (RAA) to take reasonable precautions to protect Personal Data from loss, misuse, unauthorized access or disclosure, alteration, or destruction. The goal of the WHOIS task force is to improve the effectiveness of the WHOIS service in maintaining the stability and security of the Internet's unique identifier systems, whilst taking into account where appropriate the need to ensure privacy protection for the Personal Data of individuals that may be Registered Name Holders, or the administrative or technical contact for a domain name. Tasks: (1) Define the purpose of the WHOIS service in the context of ICANN's mission, international and national laws protecting privacy, and the changing nature of Registered Name Holders. (2) Define the purpose of the technical and administrative contacts, in the context of the purpose of WHOIS, and the purpose for which the data was collected. Use the definitions from Exhibit C of the Transfers Task force report as a starting point (from http://www.icann.org/gnso/transfers-tf/report-exhc-12feb03.htm): "Contact: Contacts are individuals or entities associated with domain name records. Typically, third parties with specific inquiries or concerns will use contact records to determine who should act upon specific issues related to a domain name record. There are typically three of these contact types associated with a domain name record, the Administrative contact, the Billing contact and the Technical contact. Contact, Administrative: The administrative contact is an individual, role or organization authorized to interact with the Registry or Registrar on behalf of the Domain Holder. The administrative contact should be able to answer non-technical questions about the domain name's registration and the Domain Holder. In all cases, the Administrative Contact is viewed as the authoritative point of contact for the domain name, second only to the Domain Holder. Contact, Billing: The billing contact is the individual, role or organization designated to receive the invoice for domain name registration and re-registration fees. Contact, Technical: The technical contact is the individual, role or organization that is responsible for the technical operations of the delegated zone. This contact likely maintains the domain name server(s) for the domain. The technical contact should be able to answer technical questions about the domain name, the delegated zone and work with technically oriented people in other zones to solve technical problems that affect the domain name and/or zone." (3) Determine what data collected should be available for public access in the context of the purpose of WHOIS. Determine how to access data that is not available for public access. The current elements that must be displayed by a registrar are: - The name of the Registered Name; - The names of the primary nameserver and secondary nameserver(s) for the Registered Name; - The identity of Registrar (which may be provided through Registrar's website); - The original creation date of the registration; - The expiration date of the registration; - The name and postal address of the Registered Name Holder; - The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the Registered Name; and - The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the Registered Name. (4) Determine how to improve the process for notifying a registrar of inaccurate WHOIS data, and the process for investigating and correcting inaccurate data. Currently a registrar "shall, upon notification by any person of an inaccuracy in the contact information associated with a Registered Name sponsored by Registrar, take reasonable steps to investigate that claimed inaccuracy. In the event Registrar learns of inaccurate contact information associated with a Registered Name it sponsors, it shall take reasonable steps to correct that inaccuracy."

3 3

Strategic plan - regional presence - '... immediate job openings for the position of Liaison Managers for multiple world regions'
by Alick Wilson 17 May '05

17 May '05

ICANN has posted '... immediate job openings for the position of Liaison Managers for multiple world regions.' http://www.icann.org/general/jobs.htm#RegionalLiaisonManagers. The job listing does not state the preferred location of the successful candidates? Are the positions located in the two existing offices of Marina del Rey and Brussels, or are they located in regional offices? 'I note that 'ICANN Staff posted the latest version of the Strategic Plan on 6 May 2005 and has extended the public comment period until 20 May 2005.' http://www.icann.org/minutes/resolutions-03may05.htm. I also note that Version 7.3 of the plan http://www.icann.org/strategic-plan/strategic-plan-v7_3.pdf states ' In addition there are a number of areas that are included in this plan that have been identified by the community through the consultation process as needing more discussion and further work. Rather than attempt to deal with these issues in the timeframe of the current plan, they are listed here so that they can be given the detailed treatment that they need as part of the next planning cycle. Those issues are: ... . Determining whether ICANN should have segregated funds . Clarifying the nature of ICANN's regional presences ... ' It seems inappropriate, then, to post these 'immediate job openings' when 1. Version 7.3 of the plan is still open for comment. 2. Version 7.3 proposes deferment and detailed treatment of issues related to regional presence 3. The Board has not approved Version 7.3 of the plan or any variation thereof. Perhaps this is a logistics error, in which case the job listings should be removed ASAP with appropriate notice. If it is not a logistics error, would Board and/or staff please explain? Alick Wilson

1 0

GNSO Council discussion posted to dot Net public forum
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 15 May '05

15 May '05

[To: council[at]gnso.icann.org] Please find attached the posting, GNSO Council discussion on dot Net - excerpt from draft minutes, http://forum.icann.org/lists/net-rfp-general/msg00055.html sent to the dot Net public comment forum http://forum.icann.org/lists/net-rfp-general/ The full minutes will be published shortly on the Council list. Thank you. Kind regards, Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Revised Registry Approval Process - constituency comments by May 27,2005
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 14 May '05

14 May '05

[To council[at]gnso.icann.org] At the GNSO council meeting on Thursday May 12, 2005 it was agreed that the constituencies discuss the revised preliminary report on the Registry Approval Process with their members and submit comments within 14 days, that is, by COB on May 27, 2005. The report and the marked up copy can be viewed at the urls below: Second draft of Registry Approval Process http://www.gnso.icann.org/mailing-lists/archives/reg-com/msg00032.html Marked up copy of Second draft of Registry Approval Process http://www.gnso.icann.org/mailing-lists/archives/reg-com/msg00033.html Thank you. Kind regards, -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

2 1