[dow3tf] Whois tf 3 draft minutes/notes, teleconf. January 14.

["GNSO SECRETARIAT" <gnso.secretariat@xxxxxxxxxxxxxx>]

 [To: DOW3tf@xxxxxxxxxxxxxx]

Attached please find the draft notes/minutes of the Whois task force 3 held
on January 14, 2004.

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

Thank you very much

Glen de Saint Géry

GNSO Secretariat

<!--#set var="bartitle" value="WHOIS Task Force 3 minutes"-->
<!--#set var="pagetitle" value="WHOIS Task Force 3 minutes"-->
<!--#set var="14 January 2004" value=""-->
<!--#set var="bgcell" value="#ffffff"-->
<!--#include virtual="/header.shtml"-->
<!--#exec cmd="/usr/bin/perl /etc/gnso/menu.pl 'WHOIS Task Force 3 minutes'"-->
<p align="center"><font face="Arial, Helvetica, sans-serif"><b>WHOIS Task Force 
  3 Teleconference January 14, 2004 - 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"> Intellectual Property 
  Interests Constituency - Brian Darville - Chair:<br>
  Intellectual Property Interests Constituency - Terry Clark <br>
  Registrars Constituency - Ross Rader<br>
  Non Commercial Users constituency - Frannie Wellings<br>
  Internet Service Providers and connectivity providers Constituency</font> - 
  <font face="Arial, Helvetica, sans-serif">Greg Ruth</font><br>
  <font face="Arial, Helvetica, sans-serif">gTLD Registries constituency: - Ken 
  Stubbs </font><font face="Arial, Helvetica, sans-serif"> <br>
  <br>
  </font><font face="Arial, Helvetica, sans-serif"><b>GNSO Secretariat:</b> Glen 
  de Saint G&eacute;ry <br>
  <br>
  <b>Absent: </b></font><br>
  <font face="Arial, Helvetica, sans-serif"><b>ICANN Staff Manager</b>: Barbara 
  Roseman</font> <br>
  <font face="Arial, Helvetica, sans-serif">Commercial and Business Users constituency 
  - Sarah Deutsch</font> <br>
  <font face="Arial, Helvetica, sans-serif">At-Large Advisory Committee (ALAC) 
  liaisons: Vittorio Bertola<br>
  Intellectual Property Interests Constituency - Kiyoshi Tsuru<br>
  <br>
  Brian Darville proposed the following agenda:</font></p>
<p><font face="Arial, Helvetica, sans-serif"><br>
  1. <a href="http://gnso.icann.org/mailing-lists/archives/dow3tf/msg00029.html";>ccTLDs 
  Questions from Brian Darville</a><br>
  2. <a href="http://gnso.icann.org/mailing-lists/archives/dow3tf/msg00030.html";>Questions 
  from Sarah Deutsch</a><br>
  3. Identifying <a href="http://gnso.icann.org/mailing-lists/archives/dow3tf/msg00031.html";>other 
  companies</a> to check their data verification procedure<br>
  <br>
  <br>
  <b>Item 1. </b> <b>ccTLDs Questions from Brian Darville<br>
  </b>Brian Darville referred to the draft <a href="http://gnso.icann.org/mailing-lists/archives/dow3tf/msg00029.html";>ccTLD 
  Questionnaire</a> he sent to the task force list<br>
  : <br>
  The GNSO's WHOIS Task Force #3 is chartered with reviewing the current ICANN 
  whois policy regarding the accuracy of collected WHOIS data. <br>
  Toward that end, we are interested to know what procedures various ccTLDs employ 
  relating to the accuracy of collected WHOIS data. It would be very helpful if 
  the ccTLDs who will be part of your survey could provide information (including 
  links and copies) concerning the following points, which are of particular interest: 
  <br>
  <br>
  a) What steps do you currently take to verify the accuracy of collected WHOIS 
  data? <br>
  b) What if any staff members do you employ who have responsibility for verifying 
  the accuracy of collected WHOIS data? <br>
  c) What if any automated processes do you use or employ to verify the accuracy 
  of collected WHOIS data? <br>
  d) At what stage in the domain name registration process do you verify the accuracy 
  of the collected WHOIS data? <br>
  e) What steps, if any, do you take upon learning that submitted WHOIS data is 
  inaccurate or false? <br>
  f) Do you employ or retain any outside services for the verification of the 
  accuracy of collected WHOIS data? <br>
  If so, what is the approximate cost of such services and how are they priced? 
  <br>
  <br>
  It was suggested that Sarah Deutsch's 8th question be added to the list.<br>
  </font><font face="Arial, Helvetica, sans-serif">8. Do you have a process in 
  place for receiving reports of inaccuracies or fraud? What is that process? 
  <br>
  <br>
  <b>Ken Stubbs</b> suggested contacting other ccTLD regional organizations.<br>
  <b>Ken Stubbs</b> mentioned a recent Australian Government bill on tightening 
  the rules for domain names as a result of fraud and commented that there were 
  perhaps laws in other countries that impacted domain names registered in their 
  own ccTLD space as opposed to the administrative policy by the ccTLD management.<br>
  <b>Brian Darville</b> suggested adding a question: <br>
  What laws and regulations do you currently have in place regarding the accuracy 
  of WHOIS data?<br>
  Summarize those rules and regulations.<br>
  <br>
  The questions were approved by the task force.<br>
  <br>
  <b>Brian Darville</b> suggested contacting the GNSO Council ccTLD liaison concerning 
  a wide distribution of the questions. <br>
  <br>
  <b>Item 2. Sarah Deutsch's questions:</b><br>
  <br>
  </font><font face="Arial, Helvetica, sans-serif"><b>Brian Darville</b> referred 
  to the following list of general survey questions for other industries regarding 
  their handling the accuracy of data in online transactions submitted by <b>Sarah 
  Deutsch.<br>
  </b><br>
  1. What steps do you take to verify the accuracy of data that is submitted to 
  your company as part of an online transaction? <br>
  2. How do you ensure that the customer's name, address and other identifying 
  information is correct? <br>
  3. Do you rely on a web GUI, template or other up front screening mechanism 
  to encourage the accurate listing of identifying information? <br>
  4. Do you use credit card information and passwords to verify the accuracy of 
  the customer's identity and the legitimacy of the transaction? <br>
  5. Do you believe these systems work to provide your company with a warning 
  about inaccurate data or potential frauds in online transactions? 6. Do you 
  use in-house capabilities or retain outside services to provide verification 
  services? What are the approximate costs? <br>
  7. What steps do you take when you learn that your customer data may be inaccurate 
  or instances of fraud are reported?<br>
  8. Do you have a process in place for receiving reports of inaccuracies or fraud? 
  What is that process? <br>
  <br>
  There was general consensus on the questions and they were approved.<br>
  <br>
  <b>Item 3: Identifying other companies to check their data verification procedure<br>
  </b></font><font face="Arial, Helvetica, sans-serif"><br>
  <b>Brian Darville</b> referred to the following list he submitted of several 
  industries, companies and other sources that might be surveyed in connection 
  with data gathering regarding WHOIS data accuracy practices by other online 
  service providers.<br>
  <br>
  1) Telecommunications/Cellular - AT&T, Verizon, Sprint, British Telecom, Nortel 
  <br>
  2) Banking/Financial Services - VISA, American Express, Citi Bank, [European 
  and other International Financial Services Companies] <br>
  3) E-Bay, Paypal, Amazon<br>
  4) Verisign<br>
  5) Travel: Expedia, Travelocity <br>
  6) News: CNN, New York Times, Wall Street Journal, Washington Post.com, London 
  Times Online <br>
  7) UN Centre for Trade Facilitation and Electronic Business www.unece.org/cefact 
  <br>
  8) <a href="http://gnso.icann.org/mailing-lists/archives/dow3tf/msg00026.html";>ENUM 
  Project </a>previously circulated by Sarah Deutsch <br>
  <br>
  <b>Ken Stubbs</b> commented that Banking/Financial Services were off scale relative 
  to what was required from the task force. It was suggested that the cellular 
  telephone industry should be surveyed.<br>
  <b>Ross Rader</b> commented that surveying a bunch of multi-national enterprises 
  was not going to give a broad understanding regarding what was happening in 
  the internet services industry. The scale was very different and the practices 
  were going to be very different so it was difficult to see how they would be 
  relevant in best practices. What the typical operator was experiencing was considered 
  to be of greater value.<br>
  There was discussion on going to a specific registry, rather than registries 
  in general. It was suggested that all the registries be surveyed and <b>Ken 
  Stubbs </b>volunteered to assure the registry cooperation.<br>
  <b>Ross Rader </b>suggested that would be helpful to identify local and regional 
  companies that provided Internet services and undertook to find the necessary 
  information so that they could be included as another category.<br>
  <b>Terry Clark</b> would take on looking at the available data in the UN Centre 
  for Trade Facilitation and Electronic Business www.unece.org/cefact and the 
  ENUM Project <br>
  <b>Ross Rader</b> suggested also contacting Richard Shockey as the chair of 
  the ENUM working group rather than relying on unofficial internet-drafts which 
  while publicly available, typically do not have official standing. </font><font face="Arial, Helvetica, sans-serif"><br>
  It was proposed that <b>Ken Stubbs</b> find information on cellular telephone 
  companies to include in the survey.<br>
  <br>
  <b>Next Call:</b></font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>1. Brian Darville:</b> circulate 
  revised list of companies adding Internet Service Providers and web hosting 
  companies.<br>
  Deadline Friday 16, January</font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>2. Ross Rader</b>: Provide information 
  on pingid.com</font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>3. Terry Clark</b> to summarize 
  UN Centre for Trade Facilitation and Electronic Business www.unece.org/cefact 
  <br>
  <a href="http://gnso.icann.org/mailing-lists/archives/dow3tf/msg00026.html";>ENUM 
  Project </a>material for the task force.<br>
  Deadline Friday 23, January</font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>4.</b> Respond to the circulated 
  revised list e-mail where task force members have contacts that they could focus 
  on to in the relevant company to get the relevant information.<br>
  <br>
  <b>5. </b>Finalize the survey and the companies.<br>
  <br>
  <b>Brian Darville thanked everyone for their presence and participation and 
  ended the call at 16:50 UTC.<br>
  <br>
  </b> <b>Next call: Wednesday 21 January</b> <b>15:00 UTC, 10:00 EST, 7:00 Los 
  Angeles, 16:00 CET.<br>
  <br>
  <br>
  </b></font></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>