May 2005 - council - lists.icann.org

Draft Agenda for GNSO Council teleconference - Thursday 12 May 2005
by Bruce Tonkin July 26, 2005

July 26, 2005

Draft Agenda for Council meeting Thursday 12 May 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: Approval of new terms of reference for combined WHOIS task force, and approval of membership and voting rules Item 3: 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. - review revised preliminary report for publication for public comment Item 4: Transfers policy report - discuss staff report, and provide guidance for the 6 monthly review Item 5: Update on ICANN strategic and operational planning process Item 6: Any other business

3 2

Reminder: Registry Approval Process Comments due May 27, 2005
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG June 1, 2005

June 1, 2005

-------------------------------------------------------------------------------- [To council[at]gnso.icann.org] REMINDER Please submit your comments by COB on May 27, 2005 to: council[at]gnso.icann.org or reg-com[at]gnso.icann.org mailing lists. 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

4 3

Fifth draft of WHOIS terms of reference
by Bruce Tonkin May 30, 2005

May 30, 2005

Hello All, The draft below incorporates a specific reference to the current work on resolving conflict between national laws and ICANN, as suggested by Maria Farrell. Regards, Bruce Fifth 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. 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 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.]

2 1

RE: [council] [Fwd: Re: [alac] Draft Terms of Reference for Whois Task Force]
by Bruce Tonkin May 30, 2005

May 30, 2005

Hello Bret, Thanks for passing on the comment from John Levine. Note that task 3 includes the requirement: "Determine how to access data that is not available for public access." > > This concern from ALAC member John Levine seems like a fair > subject for inclusion in the terms of reference. > Specifically, could we have a discussion about what > constitutes abusive v. legitimate access to a registrar's > whois data? and avenues for users claiming to be legitimate > users to follow when they want/need whois access? > The starting point is to first determine the purpose for which the data is collected, the purpose of the public display of this data via WHOIS, and determine what is available for public access. Abuse in simple terms would be using the data for purposes other than which it was collected. Registrars implement various mechanisms to meet their obligations to ensure they take reasonable precautions to protect Personal Data from loss, misuse, unauthorized access or disclosure, alteration, or destruction. The mechanisms should not stop a user accessing the public data for the purpose for which it was collected and displayed. Regards, Bruce

1 0

ICANN publishes revised Telcordia report on .NET RFP
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG May 30, 2005

May 30, 2005

[To:council[at]gnso.icann.org; ga[at]gnso.icann.org] [To:announce[at]gnso.icann.org;liaison6c[at]gnso.icann.org] http://www.icann.org/ FYI, ICANN has published the Revised Telcordia Report on .NET RFP Evaluation Final Report 27 May 2005 http://www.icann.org/tlds/dotnet-reassignment/net-rfp-finalreport-issue4-27… -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

2 1

[Fwd: Re: [alac] Draft Terms of Reference for Whois Task Force]
by Bret Fausett May 26, 2005

May 26, 2005

Councilors, This concern from ALAC member John Levine seems like a fair subject for inclusion in the terms of reference. Specifically, could we have a discussion about what constitutes abusive v. legitimate access to a registrar's whois data? and avenues for users claiming to be legitimate users to follow when they want/need whois access? Bret -------- Original Message -------- Subject: Re: [alac] Draft Terms of Reference for Whois Task Force Date: 24 May 2005 22:46:31 -0400 From: John R Levine <johnl(a)iecc.com> To: Bret Fausett <bfausett(a)internet.law.pro> CC: ALAC <alac(a)icann.org> References: <4293D812.2000307(a)internet.law.pro> I don't know whether this is to the current negotiation, but I'd like to see something about ensuring WHOIS access to legitimate users. A nearby ISP and I provide secondary DNS service to each other, a very typical setup. Since I am a faster perl programmer than he is, I wrote a little program that runs every week and figures out which of his domains are nearing expiration and which have expired, by checking the WHOIS data. Its use of whois is quite moderate since it remembers the results from last time and only rechecks domains that are close to their expiration date, and the total number of domains we're talking about here is small, about 1100, spread over many registrars. Nonetheless, a while ago a computer at Network Solutions decided that I was abusing their whois server and blocked access from my entire network. I could deal with that if there were some way to get unblocked, but as far as I can tell there isn't, since they've never responded to any of my attempts to contact them. I realize that whois scraping is a problem, but it's hard to see how the modest number of lookups I've been doing would set off someone's scrape-o-meter, and it stinks that there's no way to correct errors. Regards, John Levine, johnl(a)iecc.com, Primary Perpetrator of "The Internet for Dummies", Information Superhighwayman wanna-be, http://www.johnlevine.com, Mayor "I shook hands with Senators Dole and Inouye," said Tom, disarmingly.

3 4

Final Whois Task Force report on Recommendation 1 - improving notification and consent
by Bruce Tonkin May 26, 2005

May 26, 2005

________________________________ From: Maria Farrell [mailto:maria.farrell@icann.org] Sent: Thursday, May 26, 2005 9:42 PM To: 'owner-council(a)gnso.icann.org' Subject: Final Whois Task Force report on Recommendation 1 - improving notification and consent Dear all, Attached is the Final Task Force Report on recommendations for improving notification and consent for the use of contact data in the Whois system. I am submitting this report to you on behalf of the Combined WHOIS Task Force (1, 2, 3) of the GNSO Council. The Combined Whois Task Force has continued the work of Task Force 2 whose terms of reference (29 October 2003) included the task of determining; "What is the best way to inform registrants of what information about themselves is made publicly available when they register a domain name and ... and receive notification of its use?" In addition, during the combined task force's discussions, a number of implementation issues were identified as possibly appropriate for consideration by an implementation group, if the Council chooses to form such a group. This list is attached with the caveats that the issues are not agreed on by everyone in the task force, are all worthy of further consideration and the list is not exhaustive. Best regards, Maria

1 0

Revised Draft Agenda for GNSO Council teleconference - Thursday 2 June 2005
by Bruce Tonkin May 26, 2005

May 26, 2005

Hello All, I have added a separate agenda item to consider the final report from the WHOIS task force on improving notification and consent for the use of contact data in the Whois system. Regards, Bruce Tonkin Revised 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: Consideration of final report from the WHOIS task force with respect to improving notification and consent for the use of contact data in the Whois system. Item 4: Approval of new terms of reference for combined WHOIS task force, and approval of membership and voting rules Item 5: 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 6: Transfers policy staff report - update Item 7: new gtlds - discuss next steps for staff to begin to develop issues reports Item 8: internationalised domain names - update Item 9: Comments on 2005/2006 budget/operational plan Item 10: Any other business

1 0

RE: [council] Fourth draft of WHOIS task force terms of reference
by Bruce Tonkin May 26, 2005

May 26, 2005

Hello Maria, > > I have two editing suggestions regarding the terms of > reference. One is to tighten or footnote the language about > the Internet's unique identifiers in the first paragraph so > that it can't be interpreted as including other unique > identifiers such as IP numbers. I know the text in this > draft is there to avoid opening up other debates, so I will > try to find some existing language that describes ICANN's > role. Failing that, I'll suggest a footnote to narrow the > scope of the term. > The statement of mission at the beginning of the terms of reference is simply a factual statement of ICANN's mission from the bylaws. The remaining text of the terms of reference define the tasks of the task force. I will review the remaining text to make clear that this task force is looking at gTLD domain name WHOIS, rather than the use of the WHOIS service/protocol with respect to other identifiers. Regards, Bruce

1 0

Fourth draft of WHOIS task force terms of reference
by Bruce Tonkin May 26, 2005

May 26, 2005

Hello All, Below is a fourth draft of the WHOIS task force terms of reference. I reviewed the input from Marilyn Cade, Niklas Lagergren, and Tim Ruiz (on the WHOIS mailing list). The main changes are: (1) Added a second paragraph that reflects the need to consider ICANN core values using text extracted from Article 1,Section 2 of the ICANN Bylaws (http://www.icann.org/general/bylaws.htm#I) (2) In the third paragraph I extracted the full text of the obligation of the Registered Name Holder to provide data from clause 3.7.7.1 of the Registrars Accreditation Agreement (see http://www.icann.org/registrars/ra-agreement-17may01.htm ) (3) In task 1, I have also added the need to consider laws that relate specifically to WHOIS For example, from searching at: http://thomas.loc.gov, I have identified the U.S. Fraudulent Online Identity Sanctions Act 2004, which seems to provide penalties in the case of a Registered Name Holder doing something wrong with the domain, and at the same time providing materially false contact information to a domain name registrar, domain name registry, or other domain name registration authority. Note however this Act doesn't specifically mention the WHOIS service. The current requirement for Registered Name Holders to provide correct information is consistent with this Act. The various privacy laws around the world would seem to directly apply to WHOIS with respect to Personal Data. If members of the task force are aware of specific laws that related to WHOIS then they can post them to the list, and advise ICANN staff. I believe that in some countries, parties selling services on the Internet must display their contact information on the website (and presumably in emails) that is used to provide the service as part of consumer protection laws. These laws may not have any requirement with respect to WHOIS. (4) In task 3, I added the definition of "Domain Holder" from the Transfers Policy report. (5) I added a new task 5, that relates to the work on conflicts between the ICANN agreement and local laws. With respect to further changes to task 4 relating to accuracy, I noted that Niklas wished to include work on preventing the initial collection of inaccurate data. Marilyn also referenced a provision in the registrars accreditation agreement that states that if a consensus policy is created in this area, that registrars must comply (which is of course redundant as registrars have to comply with any consensus policy). I understand that this issue has been discussed at length within the previous WHOIS Task Force 3, and that there did not seem to be a chance in the short term of reaching consensus on further work on improving data collection. In the last few meetings of the WHOIS Task Force 3, there did seem to me to be willingness to improve the process of reporting, and responding to reports, on WHOIS inaccuracy, and potentially doing some verification of data provided in response to an accuracy complaint. I have drafted the terms of reference to be consistent with the work items that have been discussed so far in Mar Del Plata and in other recent meetings of the WHOIS task force and the GNSO Council. I suggest that further work on improving accuracy of data collection, would be more appropriate once other aspects of the WHOIS service have been refined. I have not added a task relating to requiring registrants to explicitly agree to the WHOIS provisions, as this work has as I understand it been completed by the task force (the final report is almost complete), and will be discussed at the Council before these terms of reference will be approved. Regards, Bruce Tonkin Fourth 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. 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 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.

2 1