[dow1-2tf] Envoi d'un message : TMP1098192647.htm

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

  [To dow1-2tf[at]gnso.icann.org]

Please find the draft notes of the last Whois 1 & 2 task force call held on
Tuesday 5 October 2004.
Let me know if there is anything that you would like changed, and please
forgive the last minute posting!

Looking forward to hearing you all in just over an hour from now!

Kind regards,
Glen

Glen de Saint Géry
GNSO Secretariat

<!--#set var="bartitle" value="WHOIS Task Forces 1 and 2 minutes"-->
<!--#set var="pagetitle" value="WHOIS Task Force 1 and 2 minutes"-->
<!--#set var="pagedate" value="5 October 2004" value=""-->
<!--#set var="bgcell" value="#ffffff"-->
<!--#include virtual="/header.shtml"-->
<!--#exec cmd="/usr/bin/perl /etc/gnso/menu.pl 'WHOIS Task Forces 1 and 2 
minutes'"-->
<p align="center"><font face="Arial, Helvetica, sans-serif"><b>WHOIS Task 
Forces 
  1 and 2 Teleconference 5 October, 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">gTLD Registries 
constituency: 
  - Jeff</font><b><font face="Arial, Helvetica, sans-serif"> </font></b><font 
face="Arial, Helvetica, sans-serif">Neuman</font><b><font face="Arial, 
Helvetica, sans-serif"> 
  - </font></b><font face="Arial, Helvetica, 
sans-serif">Co-Chair</font><b><font face="Arial, Helvetica, sans-serif"> 
  <br>
  </font></b><font face="Arial, Helvetica, sans-serif">gTLD Registries 
constituency 
  - David Maher </font><b><font face="Arial, Helvetica, sans-serif"><br>
  </font></b><font face="Arial, Helvetica, sans-serif">Commercial and Business 
  Users constituency - David Fares</font> <font face="Arial, Helvetica, 
sans-serif"> 
  <br>
  </font><font face="Arial, Helvetica, sans-serif">Registrars constituency - 
Tom 
  Keller</font><font face="Arial, Helvetica, sans-serif"> <br>
  </font><font face="Arial, Helvetica, sans-serif">Intellectual Property 
Interests 
  Constituency - Steve Metalitz </font><font face="Arial, Helvetica, 
sans-serif"><br>
  Intellectual Property Interests Constituency - Niklas Lagergren,<br>
  <font face="Arial, Helvetica, sans-serif">Internet Service and Connectivity 
  Providers constituency: - Antonio </font></font><font face="Arial, Helvetica, 
sans-serif">Harris<br>
  Non Commercial Users Constituency - Marc Schneiders </font> <font 
face="Arial, Helvetica, sans-serif"></font><font face="Arial, Helvetica, 
sans-serif"> 
  <br>
  </font><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"> 
  <br>
  </font><font face="Arial, Helvetica, sans-serif"><b>Liaisons:</b><br>
  At-Large Advisory Committee (ALAC) liaisons - Thomas Roessler<br>
  <br>
  <br>
  <b>ICANN Staff Manager</b>: Barbara Roseman</font> <font face="Arial, 
Helvetica, sans-serif"><br>
  <b>GNSO Secretariat:</b> Glen de Saint G&eacute;ry <br>
  <br>
  <b>Absent:</b></font><font face="Arial, Helvetica, sans-serif"><br>
  Registrars constituency - Jordyn Buchanan - Co-Chair<b> </b> </font><font 
face="Arial, Helvetica, sans-serif"> 
  - apologies</font><br>
  <font face="Arial, Helvetica, sans-serif">Registrars constituency - Paul 
Stahura</font><font face="Arial, Helvetica, sans-serif"></font><br>
  <font face="Arial, Helvetica, sans-serif">Commercial and Business Users 
constituency 
  - Marilyn Cade</font>, <font face="Arial, Helvetica, 
sans-serif">apologies</font><br>
  <font face="Arial, Helvetica, sans-serif"> </font><font face="Arial, 
Helvetica, sans-serif">Internet 
  Service and Connectivity Providers constituency - Maggie Mansourkia</font> 
<br>
  <font face="Arial, Helvetica, sans-serif">Intellectual Property Interests 
Constituency 
  - Jeremy Banks</font><br>
  <font face="Arial, Helvetica, sans-serif">Amadeu Abril l Abril</font> <br>
  <font face="Arial, Helvetica, sans-serif">Non Commercial Users Constituency 
  - Milton Mueller </font> <font face="Arial, Helvetica, 
sans-serif"></font><font face="Arial, Helvetica, sans-serif"> 
  </font><font face="Arial, Helvetica, sans-serif"><br>
  </font><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"></font> 
  <font face="Arial, Helvetica, sans-serif">At-Large Advisory Committee (ALAC) 
  liaisons - Wendy Seltzer <br>
  <br>
  <a href="http://gnso-audio.icann.org/WHOIS-20040921-tf12.mp3";>MP3 
recording</a><br>
  </font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>Jeff Neuman</b> referred to 
Steve 
  Metalitz's <a 
href="http://www.gnso.icann.org/mailing-lists/archives/dow1-2tf/msg00064.html";>draft
 
  procedure for conflicts: step-by-step</a> and encouraged the task force to 
comment 
  on the list, make revisions and reach a consensus. <br>
  Jeff also referred to the <a 
href="http://www.gnso.icann.org/mailing-lists/archives/dow1-2tf/msg00041.html";>work
 
  on conspicuous notice</a> proposed by David Maher and encouraged the task 
force 
  to comment on the list.<br>
  <br>
  Agenda: tiered access<br>
  Jeff Neuman suggested the following questions: <br>
  Is tiered access feasible?<br>
  Who are the experts that could be invited to address the subject?<br>
  <br>
  <b>Steve Metalitz</b> remarked that the common feature was identifying and 
authenticating 
  Whois data.<br>
  In a tiered access system it is necessary to know who the requestor is. 
Perhaps 
  experts could assist with issues such as reliability and how time consuming 
  it would be.<br>
  <b>Tony Harris</b> suggested that people requiring the data should be 
accredited 
  and that there should be specific qualities that an entity should meet such 
  as, a justification why the full data is required, signing an agreement to 
ensure 
  that they would only use the data for themselves.<br>
  <b>Jeff Neuman</b> commented that task force 1 started discussing the topic 
  and raised such issues as a license to use the data and third party accessing 
  data on behalf of someone else.<br>
  <b>Tony Harris</b> mentioned portals where information concerning American 
companies 
  could only be accessed by American companies. Access to any website should 
require 
  a password and user name.<br>
  <br>
  <b>Tom Keller</b> and <b>Jeff Neuman</b> both mentioned the new technologies, 
  CRISP and IRIS in identification and that a briefing on the current status 
would 
  be helpful.<br>
  <b>Thomas Roessler</b> commented that it was important to know what one 
wanted 
  to link to a query, what kind of data elements should be in there. It would 
  be difficult to answer if one did not know what data elements were 
controlled. 
  Furthermore it depended on the information that was to be protected.<br>
  <b>Steve Metalitz</b> suggested:<br>
  -</font><font face="Arial, Helvetica, sans-serif"> that the task force have 
  a briefing on the current status of IRIS<br>
  -finding out what the most sensitive piece of data was in the current Whois 
  data elements<br>
  - what ought to be required to gain access to this<br>
  <b>Tony Harris</b> adding to public key structure, suggested asking companies 
  such as Verisign, Entrust and Baltimore how it could be done.<br>
  </font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>Jeff Neuman</b> reminded the 
group 
  that one of the recommendations that came out of the group was that:<br>
  - the </font><font face="Arial, Helvetica, sans-serif">Requestor needed to 
identify 
  themselves and provide some sort of justification</font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>In summary:</b><br>
  There were some technologies already there, whether it was PKI, digital 
certificates 
  or any other that could identify a requestor. <br>
  The questions still to be answered were:<br>
  - whether the symmetrical approach, that the data provided by the requestor 
  needed to match the data that the requestor was actually seeking to get, 
should 
  be applied<br>
  - w</font><font face="Arial, Helvetica, sans-serif">hether if there were an 
  accreditation process it should be:<br>
  -- a centralized accreditation body or <br>
  -- a particular, such as in the case of .name , <br>
  In theory there could be an accreditation process which did not reveal 
anything 
  about the entity accredited.</font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>Marc Schneiders</b> raised the 
  issue that when an accredited whois user was accessing data , the registrant 
  would be notified that the data is being used. <br>
  Jeff Neuman responded that sight had not been lost of the issue, but that 
would 
  be tackled down the line.<br>
  Currently the issues concentrated around feasibility</font></p>
<p><font face="Arial, Helvetica, sans-serif">If there were to be accreditation 
  </font> <font face="Arial, Helvetica, sans-serif">there could be a short list 
  as to who had access to full data such as a list locating law enforcement, 
whether 
  ISPs should ask for it, or give associations right of entry.</font></p>
<p><font face="Arial, Helvetica, sans-serif"> A view expressed was that it 
should 
  be feasible for anyone to access data as in the example of the </font><font 
face="Arial, Helvetica, sans-serif">Chilean 
  ccTLD (.cl) which requires an email address and the reason why the data is 
wanted. 
  It was felt that it was difficult to set up a list of criteria to access 
data. 
  </font></p>
<p><font face="Arial, Helvetica, sans-serif">In the authentification process 
there 
  would be information about the person and if there were a problem, the person 
  could be tracked.</font></p>
<p><font face="Arial, Helvetica, sans-serif">Some felt that the reason for 
accessing 
  the data should not be stated at the beginning of the process but should be 
  stated during the query process.</font></p>
<p><font face="Arial, Helvetica, sans-serif">Assuming there were an 
accreditation 
  process or verification there would be a need for accountability to be built 
  into the system. If there were abuse, available legal remedies should be 
sought 
  and there would be information about the abuser. In accountability, the 
question 
  arises who is going to decide. If it is agreed that notification is 
necessary, 
  when should that notification be given, before or after.</font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>Next call </b><br>
  <b>Jeff Neuman</b> suggested:<br>
  - revising a draft and circulating it to the task force for comments on the 
  list and discussion on the next call<br>
  - work on lists of experts<br>
  - who could help answer the questions<br>
  <b><br>
  Comment on two documents that have been circulated:</b><br>
  </font><font face="Arial, Helvetica, sans-serif"><b>Conspicuous notice </b>by 
  David Maher <br>
  <b>Step by step procedure relating to conflicts with local law </b>by Steve 
  Metalitz<br>
  </font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>Jeff Neuman thanked everyone 
for 
  their presence and participation and particularly for the contributions to 
the 
  mailing list.. <br>
  The call ended at 12:15 EST, 18:15 CET<br>
  </b><b><br>
  </b><b>Next Call:</b> <b>19 October 2004<br>
  see: </b></font><font face="Arial, Helvetica, sans-serif"><a 
href="http://gnso.icann.org/calendar/";>GNSO 
  calendar</a><b><br>
  <br>
  </b></font></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>