[registrars] [dow2tf] Draft minutes, WHOIS tf2, Jan. 5, 2004 (fwd)

[Thomas Keller <tom@xxxxxxxxxx>]

Hello,

here are the minutes of our last call.

Best,

tom

--

Thomas Keller

Domain Services
Schlund + Partner AG
Brauerstrasse 48         		Tel. +49-721-91374-534
76135 Karlsruhe, Germany               	Fax  +49-721-91374-215
http://www.schlund.de                  	tom@xxxxxxxxxx

--- Begin Message ---

• To: "2DOW2tf" <dow2tf@xxxxxxxxxxxxxx>
• Subject: [dow2tf] Draft minutes, WHOIS tf2, Jan. 5, 2004
• From: "GNSO SECRETARIAT" <gnso.secretariat@xxxxxxxxxxxxxx>
• Date: Wed, 7 Jan 2004 17:17:08 +0100
• Importance: Normal
• Reply-to: <gnso.secretariat@xxxxxxxxxxxxxx>
• Sender: owner-dow2tf@xxxxxxxxxxxxxx

[To: dow2tf[at]gnso.icann.org]

Attached please find the minutes of The WHOIS  task force 2, January 5,
2004.

Please let me know if you would like any changes made.

Thank you,

Glen
GNSO Secretariat

<!--#set var="bartitle" value="WHOIS Task Force 2 minutes"-->
<!--#set var="pagetitle" value="WHOIS Task Force 2 minutes"-->
<!--#set var="05 January 2004" value=""-->
<!--#set var="bgcell" value="#ffffff"-->
<!--#include virtual="/header.shtml"-->
<!--#exec cmd="/usr/bin/perl /etc/gnso/menu.pl 'WHOIS Task Force 2 minutes'"-->
<p align="center"><font face="Arial, Helvetica, sans-serif"><b>WHOIS Task Force 
  2 Teleconference January 5 - Minutes</b></font></p>
<p><b><font face="Arial, Helvetica, sans-serif">ATTENDEES:<br>
  </font></b></p>
<p><b><font face="Arial, Helvetica, sans-serif">GNSO Constituency representatives:<br>
  </font></b><font face="Arial, Helvetica, sans-serif">gTLD Registries constituency: 
  - Jordyn Buchanan</font><b><font face="Arial, Helvetica, sans-serif"> chair<br>
  </font></b><font face="Arial, Helvetica, sans-serif">gTLD Registries constituency 
  </font><b><font face="Arial, Helvetica, sans-serif">- </font></b><font face="Arial, Helvetica, sans-serif">David 
  Maher</font><font face="Arial, Helvetica, sans-serif"></font><font face="Arial, Helvetica, sans-serif"> 
  (alternate) </font><font face="Arial, Helvetica, sans-serif"><br>
  Intellectual Property Interests Constituency - Steve Metalitz (speaker)<br>
  Intellectual Property Interests Constituency - Niklas Lagergren <br>
  Registrars Constituency - Thomas Keller <br>
  Commercial and Business Users constituency:- Marilyn Cade<br>
  Non Commercial Users Constituency:- Kathryn Kleiman<br>
  Internet Service and Connectivity Providers constituency - Maggie Mansourkia 
  <br>
  </font><font face="Arial, Helvetica, sans-serif"><br>
  <b>Liaisons:</b><br>
  At-Large Advisory Committee (ALAC) liaisons - Thomas Roessler<br>
  At-Large Advisory Committee (ALAC) liaisons - Wendy Seltzer<br>
  <br>
  <br>
  <b>ICANN Staff Manager</b>: Barbara Roseman<br>
  <b>GNSO Secretariat:</b> Glen de Saint G&eacute;ry <br>
  <br>
  <b>Absent with apologies</b></font><br>
  <font face="Arial, Helvetica, sans-serif">GNSO Council independent representative 
  - Amadeu Abril I Abril<br>
  <br>
  </font><font face="Arial, Helvetica, sans-serif"><b>The agenda was approved.</b><br>
  1. Approve questions for constituencies<br>
  2. Data elements<br>
  3. Preliminary letter<br>
  4. Calendaring<br>
  5. GAC related questions<br>
  <br>
  <b>Barbara Roseman </b>reported that the Calendar and covering letter were not 
  yet complete but would be available by mid week (7 January).<br>
  Progress was being made on the history of the data elements.<br>
  The survey of the online Registrars, what their websites show and how they present 
  requests for WHOIS information is underway and should be completed by Monday 
  12 January.<br>
  <br>
  <b>Steve Metalitz </b>asked whether the request that these questions be forwarded 
  be registrars to their major resellers be included in the questions (e.g., Q. 
  4) or made part of the cover note/"prelude" to be drafted?<br>
  The general feeling of the group was that it should be part of the cover letter.<br>
  <br>
  <b>Item 1. Approve questions for constituencies</b><br>
  <br>
  <b>Jordyn Buchanan</b> posted</font><font face="Arial, Helvetica, sans-serif"> 
  all of the edits into a final list of questions to registrars: <br>
  1) What information do you provide to potential and existing registrants about 
  the following, and what mechanisms do you use to provide this information to 
  them: <br>
  (a) the purposes for which contact data is collected; <br>
  (b) the intended recipients or categories of recipients of contact data; <br>
  (c) which contact data are obligatory and which (if any) are voluntary; <br>
  (d) how registrants may access and seek to rectify their contact data. <br>
  <br>
  Please provide applicable URLs. <br>
  <br>
  2) What mechanisms do you use to obtain consent from registrants for use of 
  their contact data?<br>
  <br>
  Please provide applicable URLs.<br>
  <br>
  3) If you offer registrations through channels other than your website, how 
  do the mechanisms used to inform registrants of the use of their contact data, 
  and to gain consent for that usage, differ from those used on the website? <br>
  <br>
  4) What requirements, if any, do you make of your resellers in terms of informing 
  registrants of the use of their contact data, and gaining consent for that usage? 
  <br>
  <br>
  5) Do you provide any mechanisms for anonymous domain registrations? If so, 
  under what conditions, if any, is the registrant's anonymity lifted, or the 
  anonymous registration canceled? <br>
  <br>
  6) Do you provide any mechanisms to limit the amount of contact data made publicly 
  available through WHOIS? If so, under what conditions, if any, is access granted 
  to data that is collected, but not made publicly available through WHOIS? <br>
  <br>
  7) Describe any accommodations that you have made to comply with local laws 
  pertaining to the collection or display of contact information. Please cite 
  the specific laws. <br>
  <br>
  The questions were approved with no discussion and it was proposed to send them 
  out when the covering letter was ready.<br>
  <b><br>
  Item 2. Data Elements:</b><br>
  Reference was made to the data elements on <a href="http://gnso.icann.org/m";>Thomas 
  Roessler's table <br>
  </a> who explained that he had looked at the Registrar Accreditation Agreements 
  and the Registry Agreements and tried to isolate elements relevant to the task 
  force and data elements that were not specific to TLDs and data elements that 
  related to the eligibility verification of registrants. In addition certain 
  data elements were ignored such as Name Server and IP address and Name Server 
  Names, organization fields and trademark information as it applies to .info 
  and .pro.<br>
  <b>Steve Metalitz</b> <a href="http://gnso.icann.org/mailing-lists/archives/dow2tf/msg00055.html";>commented 
  </a>that .name had not been charted and recommended that the most comprehensive 
  list of data elements available be listed. Certain discrepancies were noted, 
  the appendix to the Registrar agreement is contradictory and it was suggested 
  that the Registries be asked to confirm what was in the agreement and what was 
  not. Further comments related to suggestions to clarify the presentation. <br>
  <br>
  <b>Thomas Roessler</b> further commented that thick Registries published more 
  data than is available to the Registrars and that the focus should be on the 
  Registrar Accreditation Agreement data elements and what elements are available. 
  While Registrars have no obligation to publish data thick Registries do have 
  an obligation to publish data which brings up issues concerning consent, information 
  and why there was the difference.<br>
  <br>
  <b>Jordyn Buchanan</b>, as a point of clarification added that the individual 
  Registrar/Registry agreements were part of the Registry agreement with ICANN 
  and were not subject to modification on a per registrar basis.<br>
  <br>
  <b>Jordyn Buchanan</b> proposed 2 charts:<br>
  a. a list of exhaustive data elements that could be used for reference<br>
  b. a simpler list of data elements, stipulating that it was not obtained from 
  any one WHOIS but was some of the data elements, that could be sent with the 
  covering letter.<br>
  <br>
  <b>Jordyn Buchanan</b> proposed 2 action items:</font><br>
  <font face="Arial, Helvetica, sans-serif">a. Create an easy to read data element 
  chart - Jordyn Buchanan<br>
  b. Update the chart with .name - list the different elements in .name - Steve 
  Metalitz/Thomas Roessler<br>
  <br>
  <b>Item 3. GAC related Issues<br>
  </b>The <a href="http://gnso.icann.org/mailing-lists/archives/dow2tf/msg00058.html";>GAC 
  response</a> was due an initiative by Marilyn Cade.<br>
  <b>Kathy Kleiman, Thomas Roessler and Tom Keller</b> were of the general opinion 
  that questions to the GAC should be more detailed, while <b>Steve Metalitz</b> 
  felt that more could be obtained from a general approach than from details. 
  It was noted that the GAC has received a limited response to the questionnaire.<br>
  <b>Kathy Kleiman</b> commented that it was important to get questions out to 
  the GAC and suggested that the GAC responses should be used to frame additional 
  questions.<br>
  <b>Marilyn Cade</b> suggested a single approach to the GAC, putting together 
  a statement and coordinating with the other task forces on what was required 
  from the GAC.<br>
  It was generally agreed that in the interaction</font><font face="Arial, Helvetica, sans-serif"> 
  with the GAC the important point was to know what the WHOIS task force wanted 
  from the GAC and that there had to be rapid action.<br>
  <b>Jordyn Buchanan </b>undertook :<br>
  - to ask Suzanne Sene if it would be possible to share the GAC responses with 
  the task force <br>
  - proposed asking the GNSO Council for the most appropriate way to approach 
  the GAC<br>
  <br>
  Time line Friday 9, January - Specific questions to the GAC taking into account 
  modifications that have been made by Steve Metalitz -<br>
  <b></b> <br>
  <br>
  <b>Item 4. Any Other Business</b><br>
  <br>
  <b>Thomas Keller </b>was asked to draw up an initial short list of questions 
  for the ccTLD launching group, Centr, etc<br>
  <b>Jordyn Buchanan</b> would contact Elisabeth Porteneuve regarding the ccTLD 
  survey.<br>
  <br>
  <b>Next Meeting:</b></font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>Kathy Kleiman</b> - enquire about 
  an online form for the OECD material.<br>
  <b>Barbara Roseman</b> - covering letter<br>
  <b>Steve Metalitz/Thomas Roessler</b> - Update the chart with .name - list the 
  different elements in .name <br>
  <b>Jordyn Buchanan</b> - Create an easy to read data element chart<br>
  <b>Thomas keller</b> - ccTLD questions <br>
  <b>Barbara Roseman</b> - enquire whether the other WHOIS task forces would ask 
  the GAC questions.</font></p>
<p><font face="Arial, Helvetica, sans-serif"> </font><font face="Arial, Helvetica, sans-serif"> 
  </font><font face="Arial, Helvetica, sans-serif"> </font><font face="Arial, Helvetica, sans-serif"><b>Jordyn 
  Buchanan thanked everyone for their presence and participation and ended the 
  call at 18:35 UTC.<br>
  <br>
  </b> <b>Next call: Monday 12 January </b></font><font face="Arial, Helvetica, sans-serif"> 
  <b>16:00 UTC, 11:00 EST, 8:00 Los Angeles, 17:00 CET. <br>
  The call will be scheduled for one hour and thirty minutes.<br>
  <br>
  <br>
  </b></font></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>

--- End Message ---