[gnso-dow123] Whois tf Revised draft minutes 7 June 2005
[To: gnso-dow123tf[at]gnso.icann.org] Please find attached the revised Whois combined Task Force draft minutes for the maating held on 7 June 2005. Please let me know what changes you would like made. Thank you very much. Kind regards, Glen de Saint Géry <!--#set var="bartitle" value="WHOIS Task Forces 1 2 3 teleconference
minutes"-->
<!--#set var="pagetitle" value="WHOIS Task Force 1 2 3 teleconference
minutes"-->
<!--#set var="pagedate" value="7 June 2005" value=""-->
<!--#set var="bgcell" value="#ffffff"-->
<!--#include virtual="/header.shtml"-->
<!--#exec cmd="/usr/bin/perl /etc/gnso/menu.pl 'WHOIS Task Force 1 2 3
teleconference minutes'"-->
<h4 align="center"><font face="Arial, Helvetica, sans-serif"><b>WHOIS Task
Forces
1 2 3<br>
<br>
7 June 2005 - Minutes</b></font></h4>
<p><font face="Arial, Helvetica, sans-serif"><b>ATTENDEES:<br>
GNSO Constituency representatives:<br>
</b> Jordyn Buchanan - Chair<br>
gTLD Registries constituency - Ken Stubbs<br>
gTLD Registries constituency - David Maher <br>
Non Commercial Users Constituency - Milton Mueller <br>
Commercial and Business Users constituency - Marilyn Cade<br>
Commercial and Business Users Constituency - David Fares<br>
Intellectual Property Interests
Constituency - Steve Metalitz<br>
Internet Service and Connectivity Providers constituency - Maggie Mansourkia
<br>
<strong>Liaisons</strong><br>
At-Large Advisory Committee (ALAC) liaisons - Wendy Seltzer</font> <font
face="Arial, Helvetica, sans-serif"> <br>
GAC Liaison - Suzanne Sene <br>
<br>
<b>ICANN Staff</b>: <br>
Maria Farrell Farrell - ICANN GNSO Policy Officer<br>
<b>GNSO Secretariat </b>- Glen
de Saint Géry <br>
<br>
<b>Absent:</b><br>
Registrars constituency - Paul Stahura <br>
Registrars constituency - Tim Ruiz (alternate) - apologies <br>
Registrars constituency - Tom Keller - apologies <br>
Intellectual Property Interests Constituency - Niklas Lagergren - apologies
<br>
Registrars constituency - Ross Rader - apologies <br>
Non Commercial Users Constituency
- Marc Schneiders<br>
Non Commercial Users Constituency - Kathy Kleiman - apologies <br>
Non Commercial Users Constituency - Frannie Wellings <br>
Commercial and Business Users Constituency - Sarah Deutsch - apologies<br>
Internet Service and Connectivity Providers constituency - Tony Harris -
apologies <br>
Internet Service and Connectivity Providers constituency - Greg Ruth <br>
<br>
</font> <font face="Arial, Helvetica, sans-serif"><a
href="http://gnso-audio.icann.org/WHOIS-20050607-tf123.mp3%20";>MP3
Recording</a> <br>
<a href="http://forum.icann.org/lists/gnso-dow123/msg00372.html";>Preliminary
Summary <br>
</a><strong><br>
Agenda </strong><br>
1. Update on conflict with national law work item undertaken by Steve
Metalitz and Kathy Kleiman. <br>
2. Planning for Luxembourg meetings - GAC Workshop<br>
Planning for Luxembourg meetings - GNSO Public Forum <br>
3. Review Council discussion and terms of reference<br>
4. Discuss work plan in light of the new terms of reference<br>
<br>
</font><font face="Arial, Helvetica, sans-serif"><strong>1. Update on
conflict with national law work item undertaken by Steve Metalitz and Kathy
Kleiman. </strong><br>
<strong>Steve Metalitz</strong> reported that progress had been made on
dividing the recommendation in 2: <br>
-
a recommendation for consensus policy <br>
-
a recommended procedure that staff would consider as a starting point in
implementing a policy. <br>
<strong>Kathy Kleiman</strong> would circulate a draft.<br>
<br>
</font><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><strong> Summary </strong><B
style="mso-bidi-font-weight:
normal">
Recommendation 2 – conflicts with national laws<br>
<o:p></o:p></B>Steve Metalitz and Kathy Kleiman are working offline on a
revised draft and will circulate it to the list for discussion.
<o:p></o:p><o:p> <br>
</o:p><br>
</span></font><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><B
style="mso-bidi-font-weight: normal">Actions<o:p></o:p></B></span></font></p>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l3 level1 lfo3; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">There will be a discussion of the revised draft on
next week’s call (Tuesday, June
14<SUP>th</SUP>).<o:p></o:p></span></font></LI>
</UL>
<p><font face="Arial, Helvetica, sans-serif"> <br>
<strong><br>
2. Planning for Luxembourg meetings - GAC Workshop</strong><br>
<strong>Suzanne Sene</strong> reported that the Government Advisory
Committee (GAC) was planning a workshop on Sunday 10 July
2005 from 14:00 to 18:00, to which the GNSO, ccNSO, and ASO Councils
would be invited as well as the WHOIS task force members. The council
chairs of the ccNSO, GNSO and ASO, were asked to identify appropriate speakers
and the GAC representatives would identify law enforcement speakers. <br>
A closed session, meaning not open to the press, was planned to ensure the
level of detail from law enforcement and to increase their comfort. The
Supporting Organizations were being asked ensure that all parties would
participate and it was envisaged that the entire GAC would participate rather
than just the GAC working group. ICANN meeting organizers were working on the
logistics of the venue. An agenda would be circulated via the Supporting
Organization chairs. <br>
<strong><br>
Milton Mueller </strong>commented, that there appeared to be no
representation for people who might be expert on individual rights against law
enforcement activities and questioned whether it was a one-sided attempt to
promote a particular view or was it intended to be a broad discussion on law
enforcement?<br>
<strong><br>
Suzanne Sene</strong> responded that it was intended to be a broad discussion
with the first session focused on law enforcement with the understanding that
other issues would be addressed in subsequent meetings.<br>
<br>
<strong>Milton Mueller</strong> noted that privacy had been deferred, as
usual, to some date undetermined in the future.</font></p>
<p><font face="Arial, Helvetica, sans-serif"><br>
<strong>Jordyn Buchanan</strong> thanked Suzanne Sene. <br>
<br>
</font><font face="Arial, Helvetica, sans-serif"><strong>Planning for
Luxembourg meetings - GNSO Public Forum</strong></font></p>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span
class="687172317-09062005"><o:p><strong> </strong></o:p></span></font><font
face="Arial, Helvetica, sans-serif"><strong><font size="2"><span
class="687172317-09062005"><o:p></o:p><o:p></o:p></span></font>Marilyn Cade
</strong>addressed the topic of the public forum that was relatively new for
the GNSO council and that it gave the community an additional opportunity for
public comment. There would be online access during the session which usually
lasted 2 hours. The intention was to have the task force present their work and
take public comments on it. <br>
She proposed putting together a plan on the topics the task force would like
to address and have the chair go back to the council and confirm that it would
be appropriate in view of the time available.<br>
<strong>Marilyn Cade </strong>commented that the Luxembourg meeting schedule
was not yet available but the proposed times for the Whois task force meetings
were Monday or Wednesday afternoon. There would be a GNSO Public Forum and
Bruce Tonkin had requested that the task force be part of the public forum. <br>
</font><font face="Arial, Helvetica, sans-serif"><strong>Jordyn
Buchanan</strong> suggested focusing on tasks 1 and 2 while <strong>Steve
Metalitz</strong> was of the opinion that topics the task force had been
discussing for some years, including accuracy, national laws, notification and
consent would be of more value.<br>
He suggested that the task force develop a list of questions soliciting
feedback on topics such as, what do you think is the purpose of WHOIS / who do
you list as contact for domain names etc. <br>
<br>
</font><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><B
style="mso-bidi-font-weight: normal"><o:p></o:p></B></span></font><font
size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><B
style="mso-bidi-font-weight: normal"> Summary
Planning for <st1:country-region
w:st="on"><st1:place
w:st="on">Luxembourg</st1:place></st1:country-region><o:p></o:p></B></span></font></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span class="687172317-09062005">Suzanne Sene provided
information on the GAC working session in <st1:country-region
w:st="on"><st1:place
w:st="on">Luxembourg</st1:place></st1:country-region> on 10 July,
2005. An agenda is expected to be circulated in approximately two
weeks. <o:p></o:p><o:p> </o:p>The GNSO Council has invited the task force
to be present during the GNSO open forum to address whois issues.
<o:p></o:p><o:p> <br>
</o:p><B
style="mso-bidi-font-weight: normal">Decisions<o:p></o:p></B></span></font></P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo5; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">The task force will propose to focus its time during
the open forum on items 1 and 2. <o:p></o:p> </span></font>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-layout-grid-align: none; mso-list: l0 level1
lfo5; tab-stops: list .5in"><font size="3" face="Arial, Helvetica,
sans-serif"><span class="687172317-09062005">The task force will prepare for
the forum a proposed list of questions it is seeking input onto act as a
starting point for discussions in the Luxembourg GNSO open forum.
<o:p></o:p> </span></font>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo5; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">The task force will finalise the authoritative list
of questions on or directly after next week's call and then send them out to
the constituencies.<B style="mso-bidi-font-weight:
normal"><o:p></o:p></B></span></font></LI>
</UL>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span class="687172317-09062005"><o:p> </o:p><B
style="mso-bidi-font-weight: normal">Actions<o:p></o:p></B></span></font></P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l5 level1 lfo6; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">Jordyn will send to the list a proposed list of
questions for input ahead of next week’s call. <o:p></o:p>
</span></font>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l5 level1 lfo6; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">Task force members will provide input on the list of
questions using the mailing list and also on next week’s call.
</span></font></LI>
</UL>
<p><font face="Arial, Helvetica, sans-serif"> <br>
</font><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><br>
<o:p></o:p></span></font><font size="2" face="Arial, Helvetica,
sans-serif"><span class="687172317-09062005"><o:p></o:p></span></font><font
size="2" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><o:p></o:p></span></font><font face="Arial,
Helvetica, sans-serif"><strong>3. Review Council discussion and terms of
reference<br>
4. Discuss work plan in light of the new terms of reference <br>
Jordyn Buchanan reported:</strong><br>
-
that the Council did not take action on the <a
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg00963.html";>
final report from the WHOIS task force with respect to improving notification
and consent for the use of contact data in the Whois system.</a> and the vote
was deferred to the next council meeting on June 23, 2005. <BR>
- that the Council had approved the <a
href="http://gnso.icann.org/policies/terms-of-reference.html";>new terms of
reference</a>. <br>
In summary there were
5 tasks: <br>
1. Define the purpose of the WHOIS service in the context of ICANN's mission
and relevant core values, <br>
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 <A
href="http://www.icann.org/gnso/transfers-tf/report-exhc-12feb03.htm";>Exhibit C
of the Transfers Task force report </A>as a starting point <br>
3. Determine what data collected should be available for public access in the
context of the purpose of WHOIS. <br>
One difference between this terms of reference and the <a
href="http://www.gnso.icann.org/issues/whois-privacy/tor2.shtml";>previous terms
of reference</a>, was that it was in the scope of the task force to discuss
what data should be gathered. However as it now stands, of the data gathered,
what should be available to public access.<br>
4. Determine how to improve the process for notifying a registrar of
inaccurate
WHOIS data, and the process for investigating and correcting inaccurate data.
A response based mechanism relating to issues dealing with accuracy. <br>
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<BR>
WHOIS service, as well as the obligation to abide by the terms of the
agreements with ICANN that relate to the WHOIS service. Work being undertaken
by Steve Metalitz and Kathy Kleiman. <br>
<br>
The numbering did not indicate any specific order of priority.<br>
<BR>
<strong>Marilyn Cade</strong> reported that <strong>Maria Farrell</strong>,
the GNSO Policy Officer, was given a short data gathering assignment to report
back to the GNSO
council and the combined WHOIS task force on a review of the top 10
registrars and a random selection of 10 other registrars to determine how
registrars make registrants aware of their obligations to provide contact
information for public display via the WHOIS service. <STRONG><BR>
</STRONG>On the terms of references, she noted that the GNSO council would
continue to be very closely involved and require frequency reports on the task
force progress and be able to offer assistance or reports at any point if the
task force deemed it necessary. <br>
<br>
<strong>Jordyn Buchanan</strong> suggested that tasks one and two, defining
the purpose of WHOIS and the contacts seemed to be preliminary work in framing
tasks three and four. It would be difficult to decide what information should
be publicly accessible without a notion of the purpose and what the contacts
were for. <br>
He suggested a serial work plan approach.</font></p>
<p><font face="Arial, Helvetica, sans-serif"><strong>Steve Metalitz</strong>
noted that for task 4, Ross Rader had put forward a proposal and suggested
building on what had already been done. He further commented that the IPC and
the majority of the constituencies on the council believed the reference was
too narrow, and in view of the work done on investigating inaccurate data, it
should be made a priority.<br>
<br>
<strong>Marilyn Cade</strong> suggested dividing up the tasks into 3
initiatives and having a work plan for each initiative so that they could be
advanced simultaneously. <br>
<strong></strong><br>
Initiative 1
- tasks one, two <br>
Initiative 2 - task 4 <br>
Initiative 3 - task 5 <br>
<strong><br>
Milton Mueller </strong>commented that if a work plan was being put forward,
task 5 could be advanced on a parallel track. With respect to tasks 1, 2, 3
& 4 it was clear that the purpose should first be dealt with before the
other tasks could be resolved. He noted that under data protection law and
norms, if data was to be collected there had to be a clearly defined purpose
and that purpose indicated what data was needed or not needed, how much
resources should be invested in making it accurate, what the states of accuracy
were, what needed to be publicly accessible and what did not. Thus it appeared
that nothing could be done before task 1 was resolved. He did not agree that
the order of the tasks did not reflect an ordered priority. The sequence was
clear: first define the purpose of the WHOIS service in the context of the
ICANN mission, second define the purpose of the the specific data elements, and
third define what should be available for public access, and once that was
done, accuracy could be addressed.<br>
<br>
<strong>Marilyn Cade</strong>, did not disagree with Milton Mueller, but
attempted to clarify council's intention that work needed to be advanced on
tasks 1 and 2, and that some amount of data gathering and discussion needed to
occur in an interactive way as opposed to sequential. <br>
It was suggested requesting clarification from Bruce Tonkin as the GNSO Council
chair on task 4.<br>
<br>
<strong>Steve Metalitz </strong>agreed on separate work plans for tasks 1,2
& 3 together, 4 & 5 but did not agree with seeking clarification on
task 4 as the task force had been involved in drafting the terms of reference.
He believed <a
href="http://forum.icann.org/lists/gnso-dow123/msg00237.html";>Ross Rader's
accuracy proposal </a>to be a good starting point for task 4. He questioned
Bruce Tonkin instructing the staff with regard to supporting the task force and
setting priorities. </font></p>
<p><font face="Arial, Helvetica, sans-serif"><strong>Jordyn Buchanan
</strong>clarified that Maria Farrell had been asked to gather data in support
of a council's vote on <a
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg00963.html";>recommendation
1</a>.</font></p>
<p><font face="Arial, Helvetica, sans-serif"><strong>Milton Mueller</strong>
commented the current process for investigating and correcting inaccurate data
was flawed, as a consequence of the lack of attention paid to privacy and the
NCUC believed that it would only be resolved on a consensus basis when tasks 1,
2 & 3 were resolved. Thus the process envisaged in the terms of reference
was seen as a hierarchical step by step way of resolving those issues and by
going down the hierarchy the level of cooperation from the NCUC other
constituencies would increase. </font></p>
<p><font face="Arial, Helvetica, sans-serif"><strong>Marilyn Cade</strong>, in
the interest of advancing work between now and Luxembourg, proposed:<br>
-
parking task 4 and developing a work plan for tasks 1,2 & 3 and 5 so that
there could be a meaningful discussion at the public comment forum in
Luxembourg.<br>
- re visiting the work plan discussion on task 4 at a time when there was full
representation from all constituencies, either in Luxembourg or on a conference
call.<br>
<br>
<strong>Jordyn Buchanan</strong> stressed that it was important to advance
work between now and Luxembourg, that he was sensitive to Steve Metalitz's
concern that work on task 4 should not be abandoned and proposed:<br>
- focusing work around tasks 1 and 2 (with limited ability to go forward on
task 3) <br>
- to
continue advancing task 5 as well and maybe discuss it next week on a call<br>
- to continue to allow and encourage the development of <a
href="http://forum.icann.org/lists/gnso-dow123/msg00237.html";>Ross Rader's
accuracy proposal</a> or any other item relating to accuracy, on the list
without completely parking it <br>
<br>
<strong>Steve Metalitz</strong> was opposed to<strong> Marilyn Cade
</strong>and<strong> Jordyn Buchanan's</strong> proposal of parking task
4.</font></p>
<p><font face="Arial, Helvetica, sans-serif"><strong>Jordyn Buchanan</strong>
summarised the proposal <br>
- the next few calls focusing on task 5, then on tasks 1 and 2. <br>
- to discuss task 4 with representatives from all the constituencies on a task
force call immediately following Luxembourg, 19 July 2005 and to encourage
work on the accuracy topic on the list.</font></p>
<p><font face="Arial, Helvetica, sans-serif"><strong>David Fares</strong> noted
that there was a commitment from the task force to address accuracy and
<strong>Jordyn</strong> <strong>Buchanan</strong> confirmed that there were no
dissenting voices on the call.<br>
<br>
</font><font size="2" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><font size="3"><B
style="mso-bidi-font-weight:
normal"> Summary Task force terms of
reference* and workplan. </B><br>
There was a discussion on the order in which work items in the task force terms
of reference will be tackled. (The work items of the terms of reference
are included at the end of this document as the discussion referred to them by
number.)<o:p></o:p></font></span></font></p>
<P class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><font size="3"
face="Arial, Helvetica, sans-serif"><span class="687172317-09062005"><B
style="mso-bidi-font-weight: normal"><o:p> </o:p></B></span></font></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span class="687172317-09062005"><o:p> </o:p><B
style="mso-bidi-font-weight: normal">Decisions* </B>(Steve Metalitz objected to
this ordering of work items)<o:p></o:p></span></font></P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l1 level1 lfo4; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">The task force calls before the <st1:country-region
w:st="on"><st1:place
w:st="on">Luxembourg</st1:place></st1:country-region> meeting will focus on
items 5, 1 and 2. <B
style="mso-bidi-font-weight: normal"><o:p></o:p></B> If possible within the
time, work will be done on item 3.<B
style="mso-bidi-font-weight: normal"><o:p></o:p></B> Work on the list will be
done on item 4, based on Ross Rader’s proposal on accuracy. <B
style="mso-bidi-font-weight: normal"><o:p></o:p></B> </span></font>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l1 level1 lfo4; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">After the <st1:country-region w:st="on"><st1:place
w:st="on">Luxembourg</st1:place></st1:country-region> meeting, the task force
will resuming work on item 4.<B
style="mso-bidi-font-weight: normal"><o:p></o:p></B></span></font></LI>
</UL>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span class="687172317-09062005"><o:p> </o:p><B
style="mso-bidi-font-weight: normal">Actions<o:p></o:p></B></span></font></P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo5; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">Jordyn will forward Ross Rader’s proposal on
accuracy to the mailing list. <o:p></o:p></span></font></LI>
</UL>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span class="687172317-09062005"><B
style="mso-bidi-font-weight: normal"><o:p></o:p></B></span></font><font
size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><o:p><br>
</o:p><B
style="mso-bidi-font-weight: normal">Decisions<o:p></o:p></B></span></font></P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo5; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">The task force will propose to focus its time during
the open forum on items 1 and 2. <o:p></o:p> </span></font>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-layout-grid-align: none; mso-list: l0 level1
lfo5; tab-stops: list .5in"><font size="3" face="Arial, Helvetica,
sans-serif"><span class="687172317-09062005">The task force will prepare for
the forum a proposed list of questions it is seeking input onto act as a
starting point for discussions in the Luxembourg GNSO open forum.
<o:p></o:p> </span></font>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo5; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">The task force will finalise the authoritative list
of questions on or directly after next week's call and then send them out to
the constituencies.<B style="mso-bidi-font-weight:
normal"><o:p></o:p></B></span></font></LI>
</UL>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span class="687172317-09062005"><o:p> </o:p><B
style="mso-bidi-font-weight: normal">Actions<o:p></o:p></B></span></font></P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l5 level1 lfo6; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">Jordyn will send to the list a proposed list of
questions for input ahead of next week’s call. <o:p></o:p>
</span></font>
<LI class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-list: l5 level1 lfo6; tab-stops: list
.5in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">Task force members will provide input on the list of
questions using the mailing list and also on next week’s call.
<o:p></o:p></span></font></LI>
</UL>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; tab-stops: list .75in"><font
size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><o:p></o:p></span></font><font size="3" face="Arial,
Helvetica, sans-serif"><span
class="687172317-09062005"><o:p></o:p></span></font></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; tab-stops: list .75in"><font
size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><o:p> </o:p><o:p> </o:p><B
style="mso-bidi-font-weight: normal"><o:p></o:p></B></span></font><font
size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005"><B
style="mso-bidi-font-weight:
normal">4
Next task force call:<o:p></o:p></B></span></font></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span class="687172317-09062005"><B
style="mso-bidi-font-weight: normal"><o:p> </o:p></B></span></font></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><font size="3" face="Arial,
Helvetica, sans-serif"><span class="687172317-09062005">The next call will be
held on <strong>Tuesday, June 14<SUP>th</SUP> 2005 </strong>and will deal with:
<o:p></o:p></span></font></P>
<P class=MsoNormal
style="MARGIN: 0in 0in 0pt 1in; TEXT-INDENT: -0.25in; mso-list: l2 level2 lfo1;
tab-stops: list 1.0in"><font size="3" face="Arial, Helvetica, sans-serif"><span
class="687172317-09062005">·
The draft recommendation 1 on conflicts with national law, and<br>
<o:p></o:p>· The proposed list of questions to solicit input on
whois at the GNSO public forum in <st1:country-region
w:st="on"><st1:place w:st="on">Luxembourg</st1:place></st1:country-region>.
</span></font><font size="2" face="Arial"><span
class="687172317-09062005"><o:p></o:p><STRONG><o:p></o:p><o:p></o:p><o:p></o:p></STRONG></span></font></P>
<p><strong><font face="Arial, Helvetica, sans-serif">* WHOIS Task Force terms
of reference tasks:</font></strong></p>
<p><font face="Arial, Helvetica, sans-serif">(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<br>
that relate specifically to the WHOIS service, and the changing nature of
Registered Name Holders.</font></p>
<p><font face="Arial, Helvetica, sans-serif">(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<br>
<br>
</font><font face="Arial, Helvetica, sans-serif">(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.</font></p>
<p><font face="Arial, Helvetica, sans-serif">(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<br>
inaccurate contact information associated with a Registered Name it sponsors,
it shall take reasonable steps to correct that inaccuracy."</font></p>
<p><font face="Arial, Helvetica, sans-serif">(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<br>
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.]<br>
<br>
<strong>Jordyn Buchanan </strong>thanked all the task force members for
participating.</font></p>
<p><font face="Arial, Helvetica, sans-serif"><strong>The WHOIS task force call
ended at 17:35 CET </strong></font></p>
<p> <font face="Arial, Helvetica, sans-serif"><br>
</font></p>
<p><font face="Arial, Helvetica, sans-serif">-</font></p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<h1> </h1>
<p> </p>
<p align="center"> </p>
<p> </p>
|