[alac] [fwd] [gnso-dow123] Whois task force terms of reference accepted by GNSO Council 2 June 2005
We've been asked for ALAC's feedback on the questions in yet another set of terms-of-reference for yet another reconstitution of the WHOIS task forces: --Wendy ----- Forwarded message from "GNSO.SECRETARIAT@xxxxxxxxxxxxxx" <gnso.secretariat@xxxxxxxxxxxxxx> ----- From: "GNSO.SECRETARIAT@xxxxxxxxxxxxxx" <gnso.secretariat@xxxxxxxxxxxxxx> To: gnso-dow123@xxxxxxxxxxxxxx Date: Fri, 03 Jun 2005 22:58:20 +0200 Subject: [gnso-dow123] Whois task force terms of reference accepted by GNSO Council 2 June 2005 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) [To: gnso-dow123[at]gnso.icann.org] Dear Task Force members, Please find attached the terms of reference as accepted by the GNSO Council at its meeting on 2 June 2005. All Council members present voted in favour. No votes against, no abstentions. Thank you very much. Kind regards, -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org WHOIS Task Forces 1 2 3 2 June 2005 TERMS OF REFERENCE 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.In performing this mission, ICANN's bylaws set out 11 core values to guide its decisions and actions. Any ICANN body making a recommendation or decision shall exercise its judgment to determine which of these core values are most relevant and how they apply to the specific circumstances of the case at hand, and to determine, if necessary, an appropriate and defensible balance among competing values. 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 to a Registrar accurate and reliable contact details and promptly correct and update them during the term of the Registered Name registration, including: the full name, postal address, e-mail address, voice telephone number, and fax number if available of the Registered Name Holder; name of authorized person for contact purposes in the case of an Registered Name Holder that is an organization, association, or corporation; 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. The contact information must be 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 natural persons that may be Registered Name Holders, the authorised representative for contact purposes of a Register Name Holder, 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 and relevant core values, international and national laws protecting privacy of natural persons, international and national laws that relate specifically to the WHOIS service, 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. Use the relevant definitions from [1]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.
Domain Holder: The individual or organization that registers a
specific
domain name. This individual or organization holds the right to 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 agreement with the Registry operator for 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 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." (5) Determine how to resolve differences between a Registered Name Holder's, gTLD Registrar's, or gTLD Registry's obligation to abide by all applicable laws and governmental regulations that relate to the WHOIS service, as well as the obligation to abide by the terms of the agreements with ICANN that relate to the WHOIS service. [Note this task refers to the current work in the WHOIS task force called 'Recommendation 2', A Procedure for conflicts, when there are conflicts between a registrar's of registry's legal obligations under local privacy laws and their contractual obligations to ICANN.] References 1. http://www.icann.org/gnso/transfers-tf/report-exhc-12feb03.htm
-- Wendy Seltzer -- wendy@xxxxxxxxxxx || wendy@xxxxxxx Electronic Frontier Foundation Berkman Center for Internet & Society at Harvard Law School http://cyber.law.harvard.edu/seltzer.html Chilling Effects: http://www.chillingeffects.org/ |