<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<title>RECOMMENDATIONS RELATING TO IMPROVING NOTIFICATION AND CONSENT FOR THE
USE CONTACT DATA IN THE WHOIS SYSTEM</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman";}
h1
{margin:0in;
margin-bottom:.0001pt;
text-align:center;
page-break-after:avoid;
text-autospace:none;
font-size:12.0pt;
font-family:"Times New Roman";
text-decoration:underline;}
h2
{margin-top:0in;
margin-right:-.5in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
page-break-after:avoid;
text-autospace:none;
font-size:11.0pt;
font-family:"Times New Roman";
font-style:italic;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{margin-top:0in;
margin-right:-.5in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:11.0pt;
font-family:"Times New Roman";
font-weight:bold;
font-style:italic;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1637640463;
mso-list-type:simple;
mso-list-template-ids:1528229162;}
@list l0:level1
{mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div id=cover-sheet>All:<br>
<br>
The attached document is proposed as the ISPCP statement on the recommendations
concerning improvements to notification and consent and whois. The Secretariat
encourages comment on this response to the ISPCP mailing list. If consensus is
reached on the list, this document will be forwarded to the gNSO as the
position of the ISPCP community on Monday at 1200 CST (1800
UTC).<br>
<br>
Thank you,<br>
<br>
Mark McFadden<br>
ISPCP Secretariat
<hr>
</div>
<div class=Section1>
<h1 style='margin-right:-.5in'><b><font size=4 face="Times New Roman"><span
style='font-size:14.0pt;text-transform:uppercase;text-decoration:none'>Recommendations
relating to improving notification and consent for the use contact data in the
WHOIS system<o:p></o:p></span></font></b></h1>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><font size=2
face="@Arial Unicode MS"><span lang=ES style='font-size:10.0pt;font-family:
"\@Arial Unicode MS"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:-.5in;margin-bottom:
0in;margin-left:.25in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
text-autospace:none'><![if !supportLists]><font size=2 face="Times New Roman"><span
lang=ES style='font-size:10.0pt'><span style='mso-list:Ignore'>1.<font size=1
face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><span lang=ES>Registrars must
ensure that disclosures regarding availability and third-party access to
personal data associated with domain names actually be presented to registrants
during the registration process. Linking to an external web page is not
sufficient.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoBodyText><b><i><font size=2 face="Times New Roman"><span lang=ES
style='font-size:11.0pt'>The ISPCP constituency supports this recommendation,
as it is a key factor to provide understanding of the registrant as to the
treatment that his/her data will be subject to. If this can be accomplished
during the registration process, instead of through reading “fine
print” after the registration has been concluded, it would appear to be a
sound business practice, and conducive to transparency with regards to personal
data manipulation. Pointing the registrant to a webpage is not a good solution,
as the registrant may waive this option in the hurry to complete his/her
registration, perhaps failing to pay adequate attention to the notice.</span></font></i></b></p>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:-.5in;margin-bottom:
0in;margin-left:.25in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
text-autospace:none'><![if !supportLists]><font size=2 face="Times New Roman"><span
lang=ES style='font-size:10.0pt'><span style='mso-list:Ignore'>2.<font size=1
face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><span lang=ES>Registrars must
ensure that these disclosures are set aside from other provisions of the
registration agreement if they are presented to registrants together with that
agreement. Alternatively, registrars may present data access disclosures
separate from the registration agreement. The wording of the notice provided by
registrars should, to the extent feasible, be uniform.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<h2><b><i><font size=2 face="Times New Roman"><span lang=ES style='font-size:
11.0pt'>The ISPCP constituency has no problem with either alternative, and
supports the necessity of some form of ‘highlighting” this notice,
in a way that ensures it cannot go unnoticed by the registrant. The wording of
the notice could perhaps be incorporated into the RAA to ensure uniformity
across all registrars. Although these recommendations are not targetted to the
subject of accuracy, perhaps the ‘enhanced’ notice to registrants
could simultaneously stress the need to supply accurate data to the registrar?
The collection of complete and accurate data, independently of the debate on
who will have access to it and how, is something the ISPCP considers vital to
the activities of it’s constsituents.</span></font></i></b></h2>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:-.5in;margin-bottom:
0in;margin-left:.25in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
text-autospace:none'><![if !supportLists]><font size=2 face="Times New Roman"><span
lang=ES style='font-size:10.0pt'><span style='mso-list:Ignore'>3.<font size=1
face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><span lang=ES>Registrars must
obtain a separate acknowledgement from registrars that they have read and
understand these disclosures. This provision does not affect registrars'
existing obligations to obtain registrant consent to the use of their contact
information in the WHOIS system.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><b><i><font
size=2 face="Times New Roman"><span lang=ES style='font-size:11.0pt;font-weight:
bold;font-style:italic'>The ISPCP supports this recommendation, assuming that
the correct phrasing is ‘Registrars must obtain a separate
acknowledgement from registrants’ (the above text reads <u>registrars</u>
at both ends of the procedure). The question that perhaps must be examined here
is: what happens if the registrant fails to acknowledge reading and
understanding of the disclosure procedures? Can he/she complete the
registration template anyway? Which is the ‘default’ conclusion in
the absence of registrant compliance?<o:p></o:p></span></font></i></b></p>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><b><i><font
size=2 face="Times New Roman"><span lang=ES style='font-size:11.0pt;font-weight:
bold;font-style:italic'><o:p> </o:p></span></font></i></b></p>
<p class=MsoNormal style='margin-right:-.5in;text-autospace:none'><b><i><font
size=2 face="Times New Roman"><span lang=ES style='font-size:11.0pt;font-weight:
bold;font-style:italic'>As a final comment, the ISPCP fully understands the
concerns of the Registrar community regarding possible cost factors in
implementing the required changes as proposed in the above recommendations.
However, in view of the prolongued and widespread debate over WHOIS and
Personal Data, it would appear there is no option other than to do something
about improving notification, and it would behoove the Registrars to evaluate
the least-cost method for achieving this.</span></font></i></b><b><i><font
size=2 face="@Arial Unicode MS"><span lang=ES style='font-size:11.0pt;
font-family:"\@Arial Unicode MS";font-weight:bold;font-style:italic'><o:p></o:p></span></font></i></b></p>
<p class=MsoNormal style='margin-right:-.5in'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-right:-.5in'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>--------------------------------------------------------------------------------------------------------------------------------------------</span></font></p>
<p class=MsoNormal style='margin-right:-.5in'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-right:-.5in'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>IPC COMMENTS -
EXTRACT</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=ES style='font-size:10.0pt;
font-family:Arial'>For example, obtaining specific consent on this issue from
the registrant during the registration process, separate from obtaining
agreement to extensive terms and conditions for the registration in general,
should be encouraged. Similarly, some registrars should be more specific and
forthright in communicating to registrants about the circumstances under which
Whois data is available to third parties. </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=ES style='font-size:10.0pt;
font-family:Arial'>" issue an advisory reminding registrars of the
importance of compliance with this contractual requirement, even registrars
operating primarily in countries in which local law apparently does not require
registrant consent to be obtained.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=ES style='font-size:10.0pt;
font-family:Arial'>IPC believes that registrars should take the lead in
developing best practices, with input from other interested constituencies,
that will improve the effectiveness of giving notice to, and obtaining consent
from, domain name registrants with regard to uses of registrant contact data.
IPC would be glad to participate in such an effort. </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=ES style='font-size:10.0pt;
font-family:Arial'>Recommendation 1 states that "[l]inking to an external
web page is not sufficient" to provide the required disclosure. It is
unclear to us what an "external" (or "internal" for that
matter) web page is. Perhaps this sentence could be amended to read:
"Linking to a web page is not sufficient."</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=ES style='font-size:10.0pt;
font-family:Arial'>Recommendation 2 states that disclosures must be "set
aside" from other provisions of the registration agreement if the
disclosure is presented as part of the agreement. It is unclear what "set
aside" means. Futhermore, Recommendation 2 allows as an alternative that
disclosures may be presented "separate from the registration agreement."
This might be viewed as inconsistent with the requirement in Recommendation 1
that the disclosure be provided "during the registration process." As
such, Recommendation 2 could be amended as follows: "Such disclosures must
be displayed prominently and conspicuously prior to the agreement being
executed by the registrant, regardless of whether they appear as a term of the
agreement or separate from the agreement."</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=ES style='font-size:10.0pt;
font-family:Arial'>IPC also suggests that the recommendations include notice to
registrants of the consequences of providing false or inaccurate Whois data
during the registration process. The text of such a notice could be similar to
what registrars provide registrants pursuant to the <a
href="http://www.icann.org/registrars/wdrp.htm">Whois Data Reminder Policy. </a></span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'>Statement of the Noncommercial Users Constituency on
Whois Task Force<br>
1/2 Recommendation: Improving Notification and Consent for the Use of<br>
Contact Data in the Whois Service<br>
<br>
1. Constituency position<br>
Noncommercial domain name users welcome efforts to ensure that domain<br>
name registrants are better informed about the publication of their<br>
private contact information via the Whois system. Public, anonymous<br>
access to private contact information poses a number of risks to<br>
registrants and may violate their rights to privacy. Until this<br>
situation is reformed, conspicuous notification is essential.<br>
<br>
The text we reviewed contains an error. Under point 3, the sentence<br>
"Registrars must obtain a separate acknowledgement from registrars that<br>
they have read and understand these disclosures" should read<br>
"Registrars must obtain a separate acknowledgement from _registrants_<br>
that they have read and understand these disclosures."<br>
<br>
NCUC strongly supports the requirement to set aside the notification<br>
and to require a distinct and separate acknowledgement from registrants<br>
that they are aware of the exposure of their private information. We<br>
observe, however, that for customers registering multiple domain names<br>
in the same transaction, only one such acknowledgement should be<br>
required. The constituency would like to make sure that the same<br>
notification and acknowledgement should take place during renewals.<br>
<br>
We strongly support the statement "The wording of the notice provided<br>
by registrars should, to the extent feasible, be uniform." Because of<br>
the highly competitive nature of the registrar business, registrars<br>
have<br>
an incentive to downplay or obscure the privacy implications of<br>
registering a domain name because they fear it may deter customers from<br>
signing up. The specific wording of the notification, therefore, should<br>
not be left to the discretion of registrars. We suggest that the wording<br>
be developed by staff subject to the approval of the GNSO Council, and<br>
translated as literally as possible into different languages by an<br>
independent party. This language should then be incorporated into the<br>
Registrar Accreditation Agreement.<br>
<br>
2. Method for Reaching Agreement on NCUC position<br>
<br>
NCUC's Chair drafted and circulated via email a constituency statement<br>
on its discussion list, soliciting input from its members. A minor<br>
addition to the draft, concerning renewals, was suggested and agreed and<br>
incorporated into the constituency statement. All comments were<br>
supportive except for one, which emphasized the additional burden on<br>
registrants of the additional process.<br>
<br>
3. Impact on Constituency.<br>
While there is some recognition that the registration process might be<br>
slightly more complicated as a result of the proposed change, all member<br>
organizations but one considered the benefits of more prominent<br>
notification and registrant awareness to outweigh any burden.<br>
<br>
<br>
<br>
Dr. Milton Mueller<br>
Syracuse University School of Information Studies<br>
<a href="http://www.digital-convergence.org/">http://www.digital-convergence.org</a><br>
<a href="http://www.internetgovernance.org/">http://www.internetgovernance.org</a><br>
<br>
<br>
<br>
</span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>To:
TF1-2<o:p></o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>CC:
gNSO Council<o:p></o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'> BC
List<o:p></o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>From:
Marilyn Cade and David Fares, for the BC<o:p></o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>Date:
January 31, 2005<o:p></o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'><o:p> </o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>. </span></font></p>
<p class=MsoNormal><b><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt;font-weight:bold'>PROVISIONAL COMMENTS OF THE BC:<o:p></o:p></span></font></b></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'>The BC membership has reviewed the comments provided
and we are submitting these as the provisional comments, while we conclude the
validation of our membership. That will be completed shortly. We do not expect
changes to these comments, however. Thus, these comments can be taken as the
input of the BC.</span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'>The BC has several questions about the proposed
recommendation which are described below, along with some suggested
modifications; however, the BC fully supports the general intent of the draft
policy recommendation. </span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'>Suggested changes or requests for clarification are
noted below, embedded in a copy of the recommendation. Immediately following
our suggested changes are further comments and suggestions. </span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><b><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt;font-weight:bold'>Suggested modifications to the
Proposed Policy: <o:p></o:p></span></font></b></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>1. Registrars
must ensure that notices regarding availability and possible third-party access
to personal data associated with domain name registrations actually be
presented to registrants during the registration process in a manner that is
easily visible and distinct to the registrant. Linking to an external web
page is not sufficient.</span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>2. Registrars
must ensure that these notices are set aside from other provisions of the
registration agreement if they are presented to registrants together with that
agreement. </span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>Alternatively,
registrars may present data availability and data access notices separate from
the registration agreement, as long as the registration cannot be completed
until there is acknowledgement of the notice. The wording of the notice
provided by registrars should be uniform and based on guidance included in the
consensus policy. </span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>3. Registrars
must obtain a separate acknowledgement from registrants that they have read and
understand these notices. This provision does not affect registrars' existing
obligations to obtain registrant consent to the use of their contact
information in the WHOIS system, </span></font><font size=3><span lang=ES
style='font-size:12.0pt'>as a registrant must permit such use before
registration can occur</span></font><span lang=ES>.</span><font
face="Courier New"><span lang=ES style='font-family:"Courier New"'><o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>General
Input and Further Comments of the BC<o:p></o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>The BC suggests
that it is preferable to use the term “notice”, since the use of
disclosure makes it sound as though the registrars are making the decision
individually regarding the requirement to provide accurate data and to have
that data included in the WHOIS database.</span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>In fact, the
registrant is required by current policy to provide accurate information and we
believe that the purpose is to remind the registrants of their obligations.</span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>Secondly, we
recommend the use of uniform and consistent notices. We believe that the
Registrars and the registrants are best served by using a uniform and
consistent notice. We are concerned that it is possible to provide confusing
notices regarding the obligation and wish to prevent that, or to have this
viewed as a way to achieve a competitive advantage. </span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>It is the
position of the BC that ensuring a fair and level playing field in the areas of
policy/contract compliance is best supported by uniform and consistent notices;
we also recommend that such notices should be developed with guidance by the
Council’s relevant TF, with approval by Council, and drafted by the ICANN
staff/legal counsel. </span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>We inserted the
additional language to the last sentence in #3 in order to clarify that
“consent” should not suggest that this is an option. Acceptance of
this policy requirement is required before the registration can continue, as
specified by current consensus policy of ICANN. </span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>Impact
on BC members: </span></font></b><span lang=ES>The BC members are negatively
impacted by inaccurate registrant data, since they are reliant upon WHOIS data
for a number of uses, including policing their domain names, preventing fraud;
defending against harmful and confusing uses of their trademark names by
competitors, or for other negative purposes. They also heavily use WHOIS data
in cooperation with law enforcement when dealing with fraud, and other civil
legal issues, or in resolving and dealing with network problems. Thus accurate
data is extremely important to the BC membership. The BC also endorses the need
for registrants to be factually informed of their obligations. We do not
believe that entities, whether individuals or organizations/corporations should
be allowed to register domain names without providing full and complete contact
data that is kept accurate and up to date.</span></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>Implementation:</span></font></b><span
lang=ES> As to the length of time it will take to implement the policy, it
appears to us that the policy can be implemented expeditiously, once approved
by the TF, and then the Council and sent to the Board for approval. The
drafting of a standardized statement to be used for disclosure should be done
by the ICANN staff/legal counsel, with the input and agreement of the Council,
and should not be an onerous task, since there are many models of notice
statements in the commercial and non commercial online world. </span></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>As a part of
approving the consensus policy, the Council could request from the registrars
constituency preliminary advice on how long it might take to enable a uniform
posting throughout the registrar community. Understandably, the registrars
will want to have this change supported by factual explanations that explain to
the registrants in a <b><span style='font-weight:bold'>neutral</span></b>
manner, the need for the change and the purpose of the change. However, it is
the position of the BC that ICANN should not exclude those who are impacted by
such changes, e.g. users/registrants as represented by the BC, ISPCP, IPC, Non
Commercial representatives, At Large, from participating in any consideration
about the development of a uniform posting notice, or any discussions about
time frames. </span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>Further
Recommendations to the TF</span></font></b><span lang=ES>: </span></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'><o:p> </o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>Extension
to renewals:</span></font></b><span lang=ES> Further, we strongly recommend
that this notice be required in any re-registration, or renewal of a
registration. It is likely that the TF has taken that for granted in its
deliberations, but we note it, in the event it has been overlooked.</span></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>Additional
and related work of the TF</span></font></b><span lang=ES>: The TF is also
examining “tiered access” at this time, and as a separate work item
from the above proposed policy modification. In the view of the BC members,
this TF should also be examining the availability of services that meet the
needs of any registrant with a legitimate need for non display of data. This
should include the availability of “anonymizing services” provided
either by the registrar or third parties for a fee, and the soon to be
available <b><span style='font-weight:bold'>.<i><span style='font-style:italic'>post</span></i></span></b>
which seems to provide yet another solution for any registrant who needs to
remain anonymous. </span></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'>In any event, the
BC notes that its members fully support the gathering of full identifying and
contact data, and that all data collected should be accurate, and that
mechanisms to support the efficient and effective correction of data should be
a priority. </span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'><o:p> </o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>Timing
of policy changes:</span></font></b><span lang=ES> However, since TF 3 is also
considering a related possible policy change, the BC recommends that other
policy changes related to WHOIS based on consensus policy be examined for
possible aggregation, if feasible, and practical. We exclude the work on Tiered
Access from this given its fledgling nature, but the work of the present TF3
should be considered for possible implementation at the same time as this policy
change, should they both be accepted as consensus policy. Thus, if there are a
number of changes approved as consensus policy, they all be made at one time,
so that the registrars <b><i><span style='font-weight:bold;font-style:italic'>and
registrants</span></i></b> are not overburdened by multiple changes, introduced
at different times.</span></p>
<p class=MsoNormal style='text-autospace:none'><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Times New Roman"><span lang=ES style='font-size:10.0pt;font-weight:bold'>Better
Information and Educational resources by ICANN</span></font></b><span lang=ES>:
Finally, the BC has from time to time noted that it supports the importance of
ICANN itself providing easily available and distributed information about
changes in policy. </span></p>
<p class=MsoNormal><b><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt;font-weight:bold'><o:p> </o:p></span></font></b></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><br>
-----Original Message-----<br>
From: <a href="mailto:owner-dow1-2tf@gnso.icann.org">owner-dow1-2tf@gnso.icann.org</a>
[mailto:owner-dow1-2tf@gnso.icann.org]<br>
On Behalf Of Thomas Keller<br>
Sent: Monday, January 31, 2005 12:10 PM<br>
To: <a href="mailto:dow1-2tf@gnso.icann.org">dow1-2tf@gnso.icann.org</a><br>
Subject: [dow1-2tf] preliminary submission of the Registrar Constituency<br>
<br>
Hello all,<br>
<br>
please find below the preliminary submission of the Registrar<br>
Consituency in regard to the policy recommendations of Whois <br>
TF 1-2 . Please keep in mind that this version is not the<br>
offical statement of the Constituency until voted upon. The<br>
ballot for finalization is just on its way.<br>
<br>
Best,<br>
<br>
tom<br>
<br>
# RC Preliminary Submission ---------------------------------------<br>
<br>
Whereas, the GNSO Registrar Constituency ("RC") has considered the<br>
proposed policy recommendations of Whois Task Force 1/2 in their<br>
entirety;<br>
<br>
Whereas, the RC believes that the continued stability of the<br>
registration process depends on its simplicity, straightforwardness, and<br>
transparency;<br>
<br>
Whereas, burdening this process with policy and consumer rights<br>
education notices diminishes its simplicity, straightforwardness and<br>
transparency;<br>
<br>
Whereas, the RC believes that prescribing the method of notification<br>
from registrants interferes with the simplicity of this process,<br>
discourages desirable business innovations, and represents entirely new<br>
obligations that would require many registrars to completely<br>
re-establish their method of registration;<br>
<br>
Whereas, the RC appreciates and understands the concerns of the task<br>
force pertaining to Recommendations #2 and #3, but does not agree with<br>
the costly and difficult to implement proposal to require the specific<br>
highlighting of one provision out of the many important provisions<br>
contained within the registration agreement;<br>
<br>
Whereas, the requirements in Recommendation #3 already are mandated in<br>
the current Registrar Accreditation Agreement in sub-sections 3.7.7.4,<br>
3.7.7.5, and 3.7.7.6; and<br>
<br>
Whereas, no data or evidence has been presented that indicate that the<br>
requirements of the current RAA are unsuitable or ineffective; and<br>
implementing a separate and additional acknowledgement from registrants<br>
as proposed would be a costly and cumbersome process that cannot be<br>
practically implemented in the current environment.<br>
<br>
Therefore, it is resolved that;<br>
<br>
[Resolved 1.0]; the Registrar Constituency does not support adopting<br>
Recommendation #1 as consensus policy, but would support a<br>
recommendation in the following form:<br>
<br>
"Registrars must ensure that disclosures regarding availability and<br>
third-party access to personal data associated with domain names<br>
actually be available to registrants during the registration process;"<br>
<br>
[Resolved 2.0]; the Registrar Constituency does not support adopting<br>
Recommendation #2 as consensus policy, but encourages registrars to<br>
increase such notification to registrants on a voluntary basis;<br>
<br>
[Resolved 3.0]; the Registrar Constituency does not support adopting<br>
Recommendation #3 as a consensus policy, as it believes that the current<br>
RAA requirements are sufficient, but encourages registrars to increase<br>
such notification to registrants on a voluntary basis;<br>
<br>
[Resolved 4.0]; the foregoing positions of the Registrar Constituency be<br>
reported to the Whois Task Force 1/2 and be included in any Task Force<br>
report; and<br>
<br>
[Resolved 4.1]; the Task Force members from the Registrar Constituency<br>
represent the foregoing positions at Task Force 1/2.<br>
<br>
<br>
<br>
<br>
</span></font></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span lang=ES
style='font-size:10.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>