ICANN/GNSO GNSO Email List Archives

[dow3tf]


<<< Chronological Index >>>    <<< Thread Index >>>

[dow3tf] Whois Task Force 3 draft notes October 6, 2004

  • To: "3DOW3tf" <dow3tf@xxxxxxxxxxxxxx>
  • Subject: [dow3tf] Whois Task Force 3 draft notes October 6, 2004
  • From: "GNSO SECRETARIAT" <gnso.secretariat@xxxxxxxxxxxxxx>
  • Date: Wed, 13 Oct 2004 17:30:15 +0200
  • Importance: Normal
  • Reply-to: <gnso.secretariat@xxxxxxxxxxxxxx>
  • Sender: owner-dow3tf@xxxxxxxxxxxxxx

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

Please find the draft notes/minutes of the Whois task force teleconference
held on October 6, 2004.
Please let me know whether there are any changes that you would like made
before theya re published on the website.
Thank you very much.

Kind regards,

Glen de Saint Géry
GNSO Secretariat

*********************************************************************
ATTENDEES:
GNSO Constituency representatives:
Intellectual Property Interests Constituency - Brian Darville - Chair:
Internet Service Providers and connectivity providers Constituency - Greg
Ruth
gTLD Registries constituency: - Ken Stubbs
Government Advisory Committee (GAC) liaison - Suzanne Sene


ICANN Staff Manager: Barbara Roseman
GNSO Secretariat: Glen de Saint Géry

Absent:
Registrars Constituency - Ross Rader - apologies
Commercial and Business Users constituency - Sarah Deutsch
Intellectual Property Interests Constituency - Kiyoshi Tsuru
Intellectual Property Interests Constituency - Terry Clark
Non Commercial Users constituency - Frannie Wellings
At-Large Advisory Committee (ALAC) liaisons: - Vittorio Bertola


MP3 recording on
http://gnso.icann.org/calendar/#oct
6 October Whois tf 3 teleconf 7:30 LA,10:30 EST, 14:30 UTC 16 :30 CET

Brian Darville referred to the draft recommendations sent to the task force
mailing list:

Draft TF3 Recommendations
I. Steps to Verify & Correct Inaccuracy in Response to a Complaint
A. If a registrar receives a complaint about the accuracy of registrant
data, whether by the Whois Data Problems Reporting System, or by any other
means, that registrar shall take reasonable steps to verify the accuracy of
that data by simultaneously contacting the registrant through at least two
of the following four methods:
1) email;
2) telephone number;
3) facsimile number;
or 3) postal mail.
If one method fails, then another method shall be used. If both of the two
pursued methods fail (e.g., email bounce-back; telephone or fax
disconnected; or a return to sender message), registrar shall place the
domain name on hold, allowing registrant 15 days to respond before the
domain name is cancelled. If it is apparent that a registrant has willfully
provided inaccurate contact data, a registrar may immediately place the
domain name on hold without first attempting to contact the registrant.
B. If a registrant responds to registrar notifications of inaccuracy within
the 15 day time limit, providing updated data, registrar shall verify the
accuracy of at least two of the following three updated data elements:
1) email;
2) telephone number; or
3) facsimile number.
Verification may consist of the registrar using the updated data to
effectively contact the registrant, confirming the registrants correction of
its contact data. If one element remains inaccurate, registrar shall verify
the third element. If both remain inaccurate registrar shall immediately
cancel the domain name registration.

II. Additional Steps to Verify & Correct Inaccuracy in Response to a
Complaint
A. Registrar shall provide any complainant with the option of expedited
verification and correction. If this option is chosen, the registrar may
charge a fee to be determined by registrar [not to exceed $xx] and shall
promptly advise complainant of the completion of each of the following
steps:
1. Registrar uses all of the following methods simultaneously to contact the
registrant:
a. email;
b. Telephone;
c. Facsimile;
d. Postal mail; and
2. If at least two of the four contact methods fails, registrar immediately
places domain name on hold, allowing registrant 15 days to respond before
the domain name is cancel; or
3. If registrant does respond to inaccuracy notifications, registrar
individually verifies the accuracy of the following updated data elements:
a. email;
b. Telephone;
c. Facsimile; and
d. Postal mail.
B. A registrant whose domain name was cancelled or placed on hold due to
inaccurate data, discovered through this expedited process, must first
reimburse the complainants fee, plus a reasonable handling fee, to the
registrar before re-activating or re-registering its domain name. The
registrar shall promptly reimburse the complainant.

Brian Darville suggested changing the period of 15 days to 30 days as was
preferred and suggested by task force members.
Suzanne Sene suggested that when the task force had reached some conclusions
she would draft a report for prior approval before it was sent to the GAC.
Brian Darville suggested that the other constituencies should comment before
further work could be done.

Brian Darville thanked everyone for their presence and participation and
ended the call at 11:00 EST, 16:00 UTC.

Next call: Wednesday 13 October 15:30 UTC, 10:30 EST, 7:30 Los Angeles,
16:30 CET.







<!--#set var="bartitle" value="WHOIS Task Force 3 minutes"-->
<!--#set var="pagetitle" value="WHOIS Task Force 3 minutes"-->
<!--#set var="06 October 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 October 6, 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>
  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> <br>
  <font face="Arial, Helvetica, sans-serif">Government Advisory Committee (GAC) 
  liaison - </font> <font face="Arial, Helvetica, sans-serif">Suzanne Sene</font><br>
  <font face="Arial, Helvetica, sans-serif"> </font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>ICANN Staff Manager</b>: Barbara 
  Roseman<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">Registrars Constituency - Ross Rader</font> 
  - <font face="Arial, Helvetica, sans-serif">apologies</font><br>
  <font face="Arial, Helvetica, sans-serif"> Commercial and Business Users constituency 
  - Sarah Deutsch</font> <br>
  <font face="Arial, Helvetica, sans-serif">Intellectual Property Interests Constituency 
  - Kiyoshi Tsuru<br>
  Intellectual Property Interests Constituency - Terry Clark <br>
  Non Commercial Users constituency - Frannie Wellings<br>
  At-Large Advisory Committee (ALAC) liaisons: - Vittorio Bertola <br>
  <br>
  <br>
  MP3 recording on <br>
  http://gnso.icann.org/calendar/#oct <br>
  6 October Whois tf 3 teleconf 7:30 LA,10:30 EST, 14:30 UTC 16 :30 CET </font></p>
<p><font face="Arial, Helvetica, sans-serif">Brian Darville referred to the draft 
  recommendations sent to the task force mailing list:</font></p>
<p><font face="Arial, Helvetica, sans-serif"> Draft TF3 Recommendations <br>
  I. Steps to Verify & Correct Inaccuracy in Response to a Complaint <br>
  A. If a registrar receives a complaint about the accuracy of registrant data, 
  whether by the Whois Data Problems Reporting System, or by any other means, 
  that registrar shall take reasonable steps to verify the accuracy of that data 
  by simultaneously contacting the registrant through at least two of the following 
  four methods:<br>
  1) email; <br>
  2) telephone number; <br>
  3) facsimile number; <br>
  or 3) postal mail. <br>
  If one method fails, then another method shall be used. If both of the two pursued 
  methods fail (e.g., email bounce-back; telephone or fax disconnected; or a return 
  to sender message), registrar shall place the domain name on hold, allowing 
  registrant 15 days to respond before the domain name is cancelled. If it is 
  apparent that a registrant has willfully provided inaccurate contact data, a 
  registrar may immediately place the domain name on hold without first attempting 
  to contact the registrant. <br>
  B. If a registrant responds to registrar notifications of inaccuracy within 
  the 15 day time limit, providing updated data, registrar shall verify the accuracy 
  of at least two of the following three updated data elements: <br>
  1) email; <br>
  2) telephone number; or <br>
  3) facsimile number. <br>
  Verification may consist of the registrar using the updated data to effectively 
  contact the registrant, confirming the registrants correction of its contact 
  data. If one element remains inaccurate, registrar shall verify the third element. 
  If both remain inaccurate registrar shall immediately cancel the domain name 
  registration. <br>
  <br>
  II. Additional Steps to Verify & Correct Inaccuracy in Response to a Complaint 
  <br>
  A. Registrar shall provide any complainant with the option of expedited verification 
  and correction. If this option is chosen, the registrar may charge a fee to 
  be determined by registrar [not to exceed $xx] and shall promptly advise complainant 
  of the completion of each of the following steps: <br>
  1. Registrar uses all of the following methods simultaneously to contact the 
  registrant: <br>
  a. email; <br>
  b. Telephone;<br>
  </font><font face="Arial, Helvetica, sans-serif">c. Facsimile; <br>
  d. Postal mail; and <br>
  2. If at least two of the four contact methods fails, registrar immediately 
  places domain name on hold, allowing registrant 15 days to respond before the 
  domain name is cancel; or <br>
  3. If registrant does respond to inaccuracy notifications, registrar individually 
  verifies the accuracy of the following updated data elements: <br>
  a. email;<br>
  b. Telephone; <br>
  c. Facsimile; and <br>
  d. Postal mail. <br>
  B. A registrant whose domain name was cancelled or placed on hold due to inaccurate 
  data, discovered through this expedited process, must first reimburse the complainants 
  fee, plus a reasonable handling fee, to the registrar before re-activating or 
  re-registering its domain name. The registrar shall promptly reimburse the complainant. 
  <br>
  <br>
  Brian Darville suggested changing the period of 15 days to 30 days as was preferred 
  and suggested by task force members.<br>
  Suzanne Sene suggested that when the task force had reached some conclusions 
  she would draft a report for prior approval before it was sent to the GAC.<br>
  Brian Darville suggested that the other constituencies should comment before 
  further work could be done.<br>
  <br>
  </font><font face="Arial, Helvetica, sans-serif"> </font><font face="Arial, Helvetica, sans-serif"><b>Brian 
  Darville thanked everyone for their presence and participation and ended the 
  call at 11:00 EST, 16:00 UTC.<br>
  <br>
  </b> <b>Next call: Wednesday </b><b>13 October 15:30 UTC, 10:30 EST, 7:30 Los 
  Angeles, 16:30 CET.<br>
  <br>
  <br>
  </b></font></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>


<<< Chronological Index >>>    <<< Thread Index >>>