<<<
Chronological Index
>>> <<<
Thread Index
>>>
[gnso-dow123] Edits to Introduction & Background
- To: gnso-dow123@xxxxxxxxxxxxxx, maria.farrell@xxxxxxxxx
- Subject: [gnso-dow123] Edits to Introduction & Background
- From: KathrynKL@xxxxxxx
- Date: Wed, 31 Aug 2005 22:37:05 EDT
With thanks to Jordyn for the extension, I have now reviewed our report in
detail.
Attached please find the report with my edits (which should visible in
green). All my changes are to Section I. Introduction & Background. In brief
they
are:
- Linking to the top of the Whois-tf2-preliminary report (not to the proxy
section)
- Adding a link to the Appendix I table in its readable Excel format
(something Barbara Roseman always promised, but was not done).
- Checking of some noted sections with quotations for exact match of text,
caps, etc
- Adding two words for the full quote in section 3.3
- A few changes of formatting and rearranging of wording to make the last
paragraph (a very important one) flow a bit more easily.
Overall a good job, and I think these edits finish it up.
Regards,
Kathy
--Apple-Mail-6-643692415
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
delsp=yes;
format=flowed
Hello:
Maria has put together a draft preliminary report for review. This
includes the recommendations that we will be voting on next Tuesday.
(Which should be no surpr
Maria's indicated that she's having some problems tracking down the
BC constituency statement, but that will get added in before this
gets posted.
Jordyn
--Apple-Mail-6-643692415
Content-Type: multipart/appledouble;
boundary=Apple-Mail-7-643692416
Content-Disposition: attachment
--Apple-Mail-7-643692416
Content-Transfer-Encoding: base64
Content-Type: application/applefile;
name="TF 123 Conflicts draft Prelim Report.html"
Content-Disposition: attachment;
filename="TF 123 Conflicts draft Prelim Report.html"
AAUWBwACAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAJAAAAPgAAAAoAAAADAAAASAAAACkAAAACAAAA
cQAAAX5URVhUUipjaAAAVEYgMTIzIENvbmZsaWN0cyBkcmFmdCBQcmVsaW0gUmVwb3J0Lmh0bWwA
AAEAAAABTAAAAEwAAAAyAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASAAJTW9uYWNvAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAABgAEACwBbQLHA+0ALAFtAscD7b8zS/gAAH3+AAB9/gAAev0BAAAAAQAAAAFMAAAA
TAAAADIATgCMAIgAAAAcADIAAE1QU1IAAAAKA+3//wAAAAABDkWY
--Apple-Mail-7-643692416
Content-Transfer-Encoding: 7bit
Content-Id: <A8FFB430-DC30-4FAD-B168-45198055B60F@local>
Content-Type: text/html;
x-mac-type=54455854;
x-unix-mode=0644;
x-mac-creator=522A6368;
name="TF 123 Conflicts draft Prelim Report.html"
Content-Disposition: attachment;
filename="TF 123 Conflicts draft Prelim Report.html"
<BASE
href="https://owa.register.com/Exchange/jbuchanan/Deleted%20Items/No%20Subject-8476.EML/";
/>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:st1="urn:schemas-microsoft-com:office:smarttags"
xmlns="http://www.w3.org/TR/REC-html40";>
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 10">
<meta name=Originator content="Microsoft Word 10">
<link rel=File-List href="gnsodow1%20w_edits%20KK_files/filelist.xml">
<link rel=Edit-Time-Data href="gnsodow1%20w_edits%20KK_files/editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title> </title>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place" downloadurl="http://www.5iantlavalamp.com/"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="date"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City" downloadurl="http://www.5iamas-microsoft-com:office:smarttags"/>
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:TrackRevisions/>
<w:Compatibility>
<w:ApplyBreakingRules/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if !mso]><object
classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object>
<style>
st1\:*{behavior:url(#ieooui) }
</style>
<![endif]-->
<style>
<!--
font-face
{font-family:Batang;}
font-face
{font-family:Georgia;}
font-face
{font-family:Garamond;}
font-face
{font-family:"\@Arial Unicode MS";}
font-face
{font-family:"\@Batang";}
/* Font Definitions */
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:647 0 0 0 159 0;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:647 0 0 0 159 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
h1
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
mso-outline-level:1;
font-size:24.0pt;
font-family:"Times New Roman";
font-weight:bold;}
h2
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
mso-outline-level:2;
font-size:18.0pt;
font-family:"Times New Roman";
font-weight:bold;}
h3
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
mso-outline-level:3;
font-size:13.5pt;
font-family:"Times New Roman";
font-weight:bold;}
h4
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
mso-pagination:widow-orphan;
page-break-after:avoid;
mso-outline-level:4;
font-size:14.0pt;
font-family:"Times New Roman";
font-weight:bold;}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
{margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:Georgia;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
p.MsoHeader, li.MsoHeader, div.MsoHeader
{margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
span.MsoFootnoteReference
{vertical-align:super;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
p
{margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
pre
{margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
font-size:10.0pt;
font-family:"Courier New";
mso-fareast-font-family:"Times New Roman";}
p.style1, li.style1, div.style1
{mso-style-name:style1;
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:Georgia;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
font-weight:bold;}
p.default, li.default, div.default
{mso-style-name:default;
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";
color:black;}
ins
{mso-style-type:export-only;
text-decoration:none;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
text-underline:single;}
span.msoDel
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:line-through;
color:lime;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:294336057;
mso-list-template-ids:-457778628;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1
{mso-list-id:297758144;
mso-list-template-ids:2072309254;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:346830840;
mso-list-template-ids:-1360724500;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l3
{mso-list-id:1958367108;
mso-list-template-ids:-1776914732;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l3:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'>
<div class=Section1>
<h3><o:p> </o:p></h3>
<h3> </h3>
<h3 align=center style='text-align:center'><a name="_Toc101951776">Combined
WHOIS Task Force (1, 2, 3) of the GNSO Council</a></h3>
<h3> </h3>
<p> </p>
<p align=center style='text-align:center'><strong>Preliminary task force report
on a policy recommendation and advice on a procedure for handling </strong></p>
<p align=center style='text-align:center'><span
class=GramE><b>conflicts</b></span><b>
between a registrar/registry’s legal obligations under privacy laws and
their contractual obligations to ICANN</b><strong><span style='font-weight:
normal'> </span></strong></p>
<p align=center style='text-align:center'><strong> </strong></p>
<p align=center style='text-align:center'><strong> </strong></p>
<p align=center style='text-align:center'><strong>For public comment from xx
August 2005 to xx September 2005</strong></p>
<p align=center style='text-align:center'> </p>
<h3> </h3>
<p class=MsoNormal> </p>
<h2><strong>Table of contents </strong></h2>
<p> </p>
<p><a href="#_Toc101951776">Combined WHOIS Task Force (1, 2, 3) of the GNSO
Council </a></p>
<p><a href="#_Toc101951777">1 Introduction & background </a></p>
<p><a href="#_Toc101951778">1.1 Text of recommendation and advice on a
procedure </a></p>
<p><a href="#Section1_2">1.2 Task Force Vote</a></p>
<p><a href="#_Toc101951780">2 Constituency statements </a></p>
<p><a href="#_Toc101951781">2.1 Commercial and Business User Constituency
</a></p>
<p><a href="#_Toc101951782">2.2 Non-Commercial User Constituency </a></p>
<p><a href="#_Toc101951783">2.3 Intellectual Property Constituency </a></p>
<p><a href="#_Toc101951784">2.4 Registrar Constituency </a></p>
<p><a href="#_Toc101951785">2.5 Registry Constituency</a></p>
<p><a href="#_Toc101951786">2.6 Internet Service Providers & Connectivity
Providers Constituency </a></p>
<p><a href="#_Toc101951795">Annex 1 Relevant provisions of the Registrar
Accreditation Agreement </a></p>
<h3><br>
</h3>
<h1><a name="_Toc101951777">1 Introduction & background</a></h1>
<p class=MsoNormal>This document is the Preliminary Task Force Report on a
consensus policy recommendation and advice on a procedure for handling WHOIS
conflicts with local or national privacy laws. It is comprised of the
proposed recommendation and advice, background information, and the
constituency statements on the recommendation and advice. </p>
<p> </p>
<p>In December 2003, WHOIS Task Force 2 was tasked with “document(<span
class=SpellE>ing</span>) examples of existing privacy laws in regard to
display/transmittal of data”. <span class=GramE>(Task Force 2 terms
of reference, point 4 of ‘tasks and milestones’; <a
href="../../../../../../../../exchweb/bin/redir.asp%3fURL=http:/gnso.icann.org/issues/whois-privacy/tor2.shtml"
target="_blank">http://gnso.icann.org/issues/whois-privacy/tor2.shtml</a>).</span></p>
<p> </p>
<p>Task Force 2’s preliminary report was published for public comment in
June 2004 at <a
href="../../../../../../../../exchweb/bin/redir.asp%3fURL=http:/gnso.icann.org/issues/whois-privacy/Whois-tf2-preliminary.html%23ProxyServices"
target="_blank">http://gnso.icann.org/issues/whois-privacy/Whois-tf2-preliminary.html<span
class=msoDel><del cite="mailto:Kleiman";
datetime="2005-08-31T21:56">#ProxyServices</del></span></a><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:23"> [to enter
to top of report]</ins></span>. <span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:00"><span style='mso-spacerun:yes'> </span>Appendix
<span
class=GramE>A<span class=msoIns><ins datetime="2005-08-31T22:02"><span
class=msoIns><ins>(</ins></span></ins></span></span></ins></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:02">I), Table of
Information by Country, can be founded in Excel format at:<span
style='mso-spacerun:yes'> </span>[fill in the GNSO URL</ins></span><span
class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:26">.</ins></span><span
class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:02">].</ins></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:28"><span
style='mso-spacerun:yes'> </span></ins></span><span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:00"><span
style='mso-spacerun:yes'> </span></ins></span>The report found (in section 2.3)
that: </p>
<p> </p>
<p class=MsoNormal>“<i>After documenting and reviewing the examples of
local privacy laws it is the Task Force’s finding that different nations
have very different privacy laws and that the determination whether they are
applicable to the <span class=SpellE>gTLD</span> WHOIS situation is not an easy
one. However, situations have arisen in which privacy laws or regulations have
conflicted with WHOIS-related contractual obligations with ICANN. </i></p>
<p class=MsoNormal><i>…</i></p>
<p class=MsoNormal><i>The Task Force believes that there is an ongoing risk of
conflict between <span class=GramE>a registrars’ or registries’
legal obligations</span> under local privacy laws and their contractual
obligations to ICANN. </i></p>
<p class=MsoNormal><i><span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:14">[formatting in this paragraph should be checked
against original text </ins></span><span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:15">–</ins></span><span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:14"> for </ins></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:15">caps,
hyphens, etc, in original </ins></span>Since the variety of the existing local
privacy laws does not allow for a one-size-fits-all solution, the registrars
and registries encountering such local difficulties should be allowed an
exception from the contractual WHOIS obligation for the part of the WHOIS data
in
question by the local regulation, after proving the existence of such a
conflict with a law or regulation. In addition, a procedure should be
established for seeking to resolve such conflicts with local authorities as new
regulations evolve in a way that promotes stability and uniformity of the WHOIS
system. </i></p>
<p class=MsoNormal><i>Such steps will undoubtedly achieve a greater legal
certainty and foster the international competition on the domain name
market.”</i></p>
<p class=MsoNormal style='text-indent:0in;mso-text-indent-alt:0in;mso-list:
none;mso-list-ins:Kleiman 20050831T2214'><span dir=LTR><span class=msoIns><ins
cite="mailto:Kleiman";
datetime="2005-08-31T22:14"><o:p> </o:p></ins></span></span></p>
<p class=MsoNormal style='mso-prop-change:Kleiman 20050831T2215'>The report
recommended (section 3.3) that <span class=msoDel><del cite="mailto:Kleiman";
datetime="2005-08-31T22:15">ICANN “</del></span><span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:15"> “ICANN should
</ins></span><i>develop
and implement a procedure for dealing with the situation where a registrar (or
registry, in thick registry settings) can credibly demonstrate that it is
legally prevented by local mandatory privacy law or regulations from fully
complying with applicable provisions of its ICANN contract regarding the
collection, display and distribution of personal data via <span
class=SpellE>Whois</span>.
The goal of the procedure should be to resolve the conflict in a manner
conducive to stability and uniformity of the <span class=SpellE>Whois</span>
system.”</i> </p>
<p class=MsoNormal>The report gave details for the steps to be included in such
a procedure: </p>
<p class=MsoNormal
style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-.25in;mso-list:l1 level1 lfo3;mso-list-change:\F0B7 Kleiman 20050831T2155;
tab-stops:list .5in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:Symbol;mso-fareast-font-family:Symbol;
mso-bidi-font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New
Roman"'>
</span></span></span><![endif]><span dir=LTR><i>“Written notification by
the affected registrar/registry to ICANN with a detailed report which includes
but is not limited to: </i></span></p>
<p class=MsoNormal
style='margin-left:1.0in;text-indent:-1.0in;mso-text-indent-alt:
-.25in;mso-list:l1 level2 lfo3;mso-list-change:o Kleiman 20050831T2155;
tab-stops:list 1.0in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:"Courier New";mso-fareast-font-family:
"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times
New Roman"'>
</span></span></span><![endif]><span dir=LTR><i>The law or regulation that
causes the conflict.</i></span></p>
<p class=MsoNormal
style='margin-left:1.0in;text-indent:-1.0in;mso-text-indent-alt:
-.25in;mso-list:l1 level2 lfo3;mso-list-change:o Kleiman 20050831T2155;
tab-stops:list 1.0in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:"Courier New";mso-fareast-font-family:
"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times
New Roman"'>
</span></span></span><![endif]><span dir=LTR><i>The part of the <span
class=SpellE>Whois</span> obligation in question.</i></span></p>
<p class=MsoNormal
style='margin-left:1.0in;text-indent:-1.0in;mso-text-indent-alt:
-.25in;mso-list:l1 level2 lfo3;mso-list-change:o Kleiman 20050831T2155;
tab-stops:list 1.0in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:"Courier New";mso-fareast-font-family:
"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times
New Roman"'>
</span></span></span><![endif]><span dir=LTR><i>The steps that will have to be
taken to cure the conflict.</i></span></p>
<p class=MsoNormal
style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-.25in;mso-list:l1 level1 lfo3;mso-list-change:\F0B7 Kleiman 20050831T2155;
tab-stops:list .5in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:Symbol;mso-fareast-font-family:Symbol;
mso-bidi-font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New
Roman"'>
</span></span></span><![endif]><span dir=LTR><i>If data elements are removed
this must be notified to the requester by the insertion of standardized notice
in the <span class=SpellE>Whois</span> results advising the requester of the
problem and, if possible, directing requester to another source or alternative
procedure for obtaining access to this data element.</i></span></p>
<p class=MsoNormal
style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-.25in;mso-list:l1 level1 lfo3;mso-list-change:\F0B7 Kleiman 20050831T2155;
tab-stops:list .5in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:Symbol;mso-fareast-font-family:Symbol;
mso-bidi-font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New
Roman"'>
</span></span></span><![endif]><span dir=LTR><i>Prompt notification from ICANN
to the public informing it of the change and of the reasons for ICANN’s
forbearance from enforcement of full compliance with the contractual provision
in question. </i></span></p>
<p class=MsoNormal
style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-.25in;mso-list:l1 level1 lfo3;mso-list-change:\F0B7 Kleiman 20050831T2155;
tab-stops:list .5in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:Symbol;mso-fareast-font-family:Symbol;
mso-bidi-font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New
Roman"'>
</span></span></span><![endif]><span dir=LTR><i>The changes must be archived on
a public website for future research</i></span></p>
<p class=MsoNormal><i>Except in those cases arising from a formal complaint or
contact by a local law enforcement authority that will not permit consultation
with ICANN prior to resolution of the complaint under local law, the procedure
should be initiated using the following steps:</i></p>
<p class=MsoNormal
style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-.25in;mso-list:l3 level1 lfo6;mso-list-change:\F0B7 Kleiman 20050831T2155;
tab-stops:list .5in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:Symbol;mso-fareast-font-family:Symbol;
mso-bidi-font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New
Roman"'>
</span></span></span><![endif]><span dir=LTR><i>prompt notification by the
affected registrar/registry to ICANN with detailed summary of the problem
arising
including: </i></span></p>
<p class=MsoNormal
style='margin-left:1.0in;text-indent:-1.0in;mso-text-indent-alt:
-.25in;mso-list:l3 level2 lfo6;mso-list-change:o Kleiman 20050831T2155;
tab-stops:list 1.0in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:"Courier New";mso-fareast-font-family:
"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times
New Roman"'>
</span></span></span><![endif]><span dir=LTR><i>The law or regulation that
causes the conflict.</i></span></p>
<p class=MsoNormal
style='margin-left:1.0in;text-indent:-1.0in;mso-text-indent-alt:
-.25in;mso-list:l3 level2 lfo6;mso-list-change:o Kleiman 20050831T2155;
tab-stops:list 1.0in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:"Courier New";mso-fareast-font-family:
"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times
New Roman"'>
</span></span></span><![endif]><span dir=LTR><i>The part of the <span
class=SpellE>Whois</span> obligation in question.</i></span></p>
<p class=MsoNormal
style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-.25in;mso-list:l3 level1 lfo6;mso-list-change:\F0B7 Kleiman 20050831T2155;
tab-stops:list .5in'><![if !supportLists]><span style='font-size:10.0pt;
mso-bidi-font-size:12.0pt;font-family:Symbol;mso-fareast-font-family:Symbol;
mso-bidi-font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New
Roman"'>
</span></span></span><![endif]><span dir=LTR><span
class=GramE><i>consultation</i></span><i>
by the registrar/registry with ICANN and other parties (which may include
government agencies) to try to resolve the problem/ remove the impediment to
full compliance with contract.</i>”</span></p>
<p><b> </b></p>
<p style='mso-prop-change:Kleiman 20050831T2217'>On 30 November 2004, the WHOIS
Task Forces 1 and 2 produced <b><a
href="../../../../../../../../exchweb/bin/redir.asp%3fURL=http:/gnso.icann.org/issues/whois-privacy/whois-tf-conflict-30nov04.pdf"
target="_blank">Recommendation 1 – A Procedure for conflicts, when
there are conflicts between a registrar's <span class=msoDel><del
cite="mailto:Kleiman"; datetime="2005-08-31T22:17">of </del></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:17"><u>or?
</u></ins></span><span
class=GramE>registry's</span> legal obligations under local privacy laws and
their contractual obligations to ICANN.</a> </b>This recommendation was
presented to the GNSO Council during the GNSO public forum at the ICANN meeting
in <span class=SpellE>Capetown</span> in December 2004. </p>
<p> </p>
<p class=MsoNormal style='mso-prop-change:Kleiman 20050831T2223'><span
class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:16">[</ins></span><span
class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:23">W</ins></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:16">hole
paragraph </ins></span><span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:23">should be changed </ins></span><span
class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:16">to Times 12</ins></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:17">;
</ins></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:23">currently
some
</ins></span><span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:17">Garamond</ins></span><span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:23"> is present</ins></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:16">]
</ins></span>On
<st1:date Year="2005" Day="17" Month="2">February 17, 2005</st1:date>, the
WHOIS task force’s 1, 2 and 3 were combined into a single, <span
class=SpellE>combinedWHOIS</span> Task Force. (<span style='font-size:10.0pt;
font-family:"Courier New"'><a
href="../../../../../../../../exchweb/bin/redir.asp%3fURL=http:/www.gnso.icann.org/meetings/minutes-gnso-17feb05.shtml"
target="_blank">http://www.gnso.icann.org/meetings/minutes-gnso-17feb05.shtml</a>)
The combined WHOIS task force was chartered by the GNSO Council with terms of
reference and set of tasks on </span><st1:date Year="2005" Day="2"
Month="6"><span
style='font-size:10.0pt;font-family:"Courier New"'>2nd June
2005</span></st1:date><span
style='font-size:10.0pt;font-family:"Courier New"'><span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:18"> that required the Combined
WHOIS TF to conclude its work on the </ins></span><span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:19">“conflicts”
</ins></span><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:20">policy
</ins></span><span
class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:19">recommendation</ins></span><span
class=msoDel><del cite="mailto:Kleiman";
datetime="2005-08-31T22:18">:</del></span></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier
New"'><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:18"><span
style='mso-spacerun:yes'> </span></ins></span><span class=msoDel><del
cite="mailto:Kleiman"; datetime="2005-08-31T22:18"><a
href="../../../../../../../../exchweb/bin/redir.asp%3fURL=http:/gnso.icann.org/policies/terms-of-reference.html"
target="_blank">http://gnso.icann.org/policies/terms-of-reference.html</a>.</del></span></span><span
class=msoDel><del cite="mailto:Kleiman";
datetime="2005-08-31T22:18"><o:p></o:p></del></span></p>
<p class=MsoNormal style='text-indent:0in;mso-text-indent-alt:0in;mso-list:
none;mso-list-ins:Kleiman 20050831T2218'><span dir=LTR>“</span><span
style='font-family:Garamond'>(5) Determine how to resolve differences between a
Registered Name Holder's, <span class=SpellE>gTLD</span> Registrar's, or <span
class=SpellE>gTLD</span> Registry's obligation to abide by all applicable laws
and governmental regulations that relate to the<span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:17"> [no line
break]</ins></span><span
class=msoDel><del cite="mailto:Kleiman"; datetime="2005-08-31T22:17"><br>
</del></span>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.]”<span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:18"><span style='mso-spacerun:yes'>
</span></ins></span></span><span
style='font-size:10.0pt;font-family:"Courier New"'><span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:18"><a
href="../../../../../../../../exchweb/bin/redir.asp%3fURL=http:/gnso.icann.org/policies/terms-of-reference.html"
target="_blank">http://gnso.icann.org/policies/terms-of-reference.html</a>.</ins></span></span><span
class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:18"><o:p></o:p></ins></span></p>
<p class=MsoNormal style='mso-prop-change:Kleiman
20050831T2217'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-family:Garamond'><span class=msoDel><del
cite="mailto:Kleiman"; datetime="2005-08-31T22:21">Task 5 of the terms of
reference required the Combined WHOIS Task Force to conclude its work on this
recommendation.</del></span><span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:21">Accordingly<span class=GramE>, <span
style='mso-spacerun:yes'> </span>Task</span> force members continued to develop
the recommendation through June 2005. The task force voted
</ins></span></span>on
<st1:date Year="2005" Day="24" Month="5">May 24, 2005</st1:date> to divide its
work into a recommendation for consensus policy accompanied by advice for a
procedure.<span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:22"> </ins></span><span
style='font-family:Garamond'><span
class=msoIns><ins cite="mailto:Kleiman"; datetime="2005-08-31T22:22">[<span
class=GramE>no</span> line break.]</ins></span></span><span class=msoDel><del
cite="mailto:Kleiman"; datetime="2005-08-31T22:22"><o:p></o:p></del></span></p>
<p class=MsoNormal style='mso-prop-change:Kleiman 20050831T2222'><span
style='font-family:Garamond'>Constituency statements on the recommendation were
solicited by </span><st1:date Year="2005" Day="21" Month="7"><span
style='font-family:Garamond'>21 July 2005</span></st1:date><span
style='font-family:Garamond'>.<span class=msoIns><ins cite="mailto:Kleiman";
datetime="2005-08-31T22:22"><o:p></o:p></ins></span></span></p>
<p class=MsoNormal style='text-indent:0in !msorm;mso-text-indent-alt:0in !msorm;
mso-list:none !msorm;text-indent:0in;mso-text-indent-alt:0in;mso-list:none;
mso-list-ins:Kleiman 20050831T2222;mso-prop-change:Kleiman 20050831T2222'><span
dir=LTR><span style='font-family:Garamond'><span class=msoIns><ins
cite="mailto:Kleiman";
datetime="2005-08-31T22:22"><o:p> </o:p></ins></span></span></span></p>
<p class=MsoNormal style='text-indent:0in !msorm;mso-text-indent-alt:0in !msorm;
mso-list:none !msorm;text-indent:0in;mso-text-indent-alt:0in;mso-list:none;
mso-list-ins:Kleiman 20050831T2222;mso-prop-change:Kleiman 20050831T2222'><span
dir=LTR><span style='font-family:Garamond'><span class=msoIns><ins
cite="mailto:Kleiman"; datetime="2005-08-31T22:22">[If necessary:<span
style='mso-spacerun:yes'> </span>“After Constituency statements were
received, the following changes were added by the TF:]</ins></span>
</span></span></p>
<p> </p>
<h2><a name="_Toc101951778">1.1 Text of recommendation</a> and advice on a
procedure</h2>
<p class=MsoNormal align=center style='text-align:center'> <b><span
style='font-size:14.0pt'>WHOIS Task Force</span></b></p>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:14.0pt'>Policy recommendation and advice on <span
class=SpellE>Whois</span> conflicts with national and local privacy
laws</span></b></p>
<p class=MsoNormal><b><span style='font-size:14.0pt'> </span></b></p>
<p class=MsoNormal><b>Preamble:</b></p>
<p class=MsoNormal><b> </b></p>
<p class=MsoNormal>Task Force 2 spent over a year collecting data and working
on the conflict between a registrar/registry’s legal obligations under
privacy
laws and their contractual obligations to ICANN. Its report included the
statement: “The Task Force believes that there is an ongoing risk
of conflict between a registrar’s or <span
class=GramE>registry’s</span>
legal obligations under local privacy laws and their contractual obligations to
ICANN<i>. TF2 Report, Section 2.3,</i>
http://www.gnso.icann.org/issues/whois-privacy/Whois-tf2-preliminary.html.</p>
<p class=MsoNormal> </p>
<p class=MsoNormal>By vote of the Task Force, now merged, on <st1:date
Year="2005" Day="24" Month="5">May 24, 2005</st1:date>, the work of Task Force
2 is hereby divided into a recommendation for “consensus policy”
accompanied by “well-developed advice for a procedure.”</p>
<p class=MsoNormal> </p>
<p class=MsoNormal><b>I. Task Force Policy for WHOIS Conflicts with
Privacy Law</b></p>
<p class=MsoNormal><b><span
style='font-variant:small-caps'> </span></b></p>
<p class=MsoNormal><b><span style='font-variant:small-caps'>Consensus Policy
Recommendation</span></b></p>
<p class=MsoNormal> </p>
<p class=MsoNormal>In order to facilitate reconciliation of any conflicts
between
local/national mandatory privacy laws or regulations and applicable provisions
of the ICANN contract regarding the collection, display and distribution of
personal data via <span class=SpellE>Whois</span>, ICANN should: </p>
<p class=MsoNormal> </p>
<p class=MsoNormal>1. Develop and publicly document a procedure for
dealing
with the situation in which a registrar or registry can credibly demonstrate
that it is legally prevented by local/national privacy laws or regulations from
fully complying with applicable provisions of its ICANN contract regarding the
collection, display and distribution of personal data via WHOIS.
</p>
<p class=MsoNormal> </p>
<p class=MsoNormal>2. Create goals for the procedure which include:
</p>
<p class=MsoNormal> </p>
<p
class=MsoNormal>
a.<span class=GramE> Ensuring</span> that ICANN staff is informed of a
conflict at the earliest appropriate juncture;</p>
<p class=MsoNormal> </p>
<p
class=MsoNormal>
b.<span class=GramE> Resolving</span> the conflict, if possible, in a
manner conducive to ICANN’s
<st1:City><st1:place>Mission</st1:place></st1:City>,
applicable Core Values and the stability and uniformity of the <span
class=SpellE>Whois</span> system;</p>
<p class=MsoNormal> </p>
<p
class=MsoNormal>
c. Providing a mechanism for the recognition, if appropriate, in
circumstances where the conflict cannot be otherwise resolved, of an exception
to contractual obligations with regard to collection, display and distribution
of personally identifiable data via <span class=SpellE>Whois</span>; and </p>
<p class=MsoNormal> </p>
<p
class=MsoNormal>
d.<span class=GramE> Preserving</span> sufficient flexibility for ICANN
staff to respond to particular factual situations as they arise.</p>
<p class=MsoNormal> </p>
<p class=MsoNormal> </p>
<p class=MsoNormal><b>II.<span class=GramE> Text</span> of Recommended
Procedure</b></p>
<p class=MsoNormal><b> </b></p>
<p class=MsoNormal><b><span style='font-variant:small-caps'>Well-Developed
Advice on a Procedure for Handling WHOIS Conflicts</span></b></p>
<p class=MsoNormal><b><span style='font-variant:small-caps'> with Privacy
Law </span></b></p>
<p class=MsoNormal> </p>
<p class=MsoNormal>Based on extensive research and negotiation among Task Force
2 together with the merged Task Force and ICANN staff, the following procedure
for handling the policy recommendation set out in Section I above is set out as
a Recommended </p>
<p class=MsoNormal><span class=GramE>Step-by-Step Procedure for Resolution of
WHOIS Conflicts with Privacy Law.</span> We encourage ICANN staff to use
this Recommended Procedure as a starting point for developing the procedure
called for in the Consensus Policy Recommendation above. </p>
<p class=MsoNormal> </p>
<p class=MsoNormal> </p>
<p class=MsoNormal><i>Step One: Notification of Initiation of Action</i></p>
<p class=MsoNormal> </p>
<p class=MsoNormal>Once receiving notification of an investigation, litigation,
regulatory proceeding or other government or civil action that might affect its
compliance with the provisions of the RAA or other contractual agreement with
ICANN dealing with the collection, display or distribution of personally
identifiable
data via <span class=SpellE>Whois</span> (“<span class=SpellE>Whois</span>
Proceeding”), a Registrar/ Registry must within thirty (30) days provide
ICANN’s General Counsel (or other staff member as designated by ICANN)<a
name="_ftnref1"></a><a href="#_ftn1" title=""><span
style='mso-bookmark:_ftnref1'><span
class=MsoFootnoteReference>[1]</span></span><span
style='mso-bookmark:_ftnref1'></span></a><span
style='mso-bookmark:_ftnref1'></span> with the following information: </p>
<p class=MsoNormal> </p>
<p class=MsoNormal style='margin-left:39.35pt;text-indent:-.25in'><span
class=GramE><span style='font-family:Symbol'>·</span><span style='font-size:
7.0pt'> </span>Summary description of
the nature and status of the action (e.g., inquiry, investigation, litigation,
threat of sanctions, etc.)</span></p>
<p class=MsoNormal style='margin-left:39.35pt;text-indent:-.25in'><span
class=GramE><span style='font-family:Symbol'>·</span><span style='font-size:
7.0pt'> </span>Contact information
for the responsible official of the registrar/registry for resolving the
problem.</span></p>
<p class=MsoNormal style='margin-left:39.35pt;text-indent:-.25in'><span
class=GramE><span style='font-family:Symbol'>·</span><span style='font-size:
7.0pt'> </span>Contact information
for the responsible territorial government agency or other claimant and a
statement from the registrar/registry authorizing ICANN to communicate with
those officials or claimants on the matter.</span> If the registrar/registry is
prevented by applicable law from granting such authorization, the notification
should document this.</p>
<p class=MsoNormal style='margin-left:39.35pt;text-indent:-.25in'><span
style='font-family:Symbol'>·</span><span
style='font-size:7.0pt'>
</span><span class=GramE>The</span> text of the applicable law or regulations
upon which the local government or other claimant is basing its action or
investigation, if such information has been indicated by the government or
other claimant.</p>
<p class=MsoNormal> </p>
<p class=MsoNormal>Meeting the notification requirement permits
Registrars/Registries to participate in investigations and respond to court
orders, regulations, or enforcement authorities in a manner and course deemed
best by their counsel.</p>
<p class=MsoNormal> </p>
<p class=MsoNormal>Depending on the specific circumstances of the <span
class=SpellE>Whois</span> Proceeding, the Registrar/Registry may request that
ICANN keep all correspondence between the parties confidential <span
class=GramE>pending</span> the outcome of the <span class=SpellE>Whois</span>
Proceeding. It is recommended that ICANN respond favorably to such
requests to the extent that they can be accommodated with other legal
responsibilities and basic principles of transparency applicable to ICANN
operations. </p>
<p class=MsoNormal style='text-indent:.5in'> </p>
<p class=MsoNormal style='page-break-after:avoid'><i>Step Two:
Consultation</i></p>
<p class=MsoNormal style='page-break-after:avoid'><i> </i></p>
<p class=MsoNormal style='page-break-after:avoid'>Unless impractical under the
circumstances, we recommend that the ICANN General Counsel, upon receipt and
review of the notification and, where appropriate, dialogue with the
registrar/registry, consider beginning a process of consultation with the
local/national enforcement authorities or other claimant together with the
registrar/registry. The goal of the consultation process should be to
seek to resolve the problem in a manner that preserves the ability of the
registrar/registry to comply with its contractual obligations to the greatest
extent possible. </p>
<p class=MsoNormal> </p>
<p class=MsoNormal>If the <span class=SpellE>Whois</span> proceeding<span
class=GramE> ends</span> without requiring any changes and/or the
required changes in registrar/registry practice do not, in the opinion of the
General Counsel, constitute a deviation from the R.A.A. or other contractual
obligation , then the General Counsel and the registrar/registry need to take
no further action. </p>
<p class=MsoNormal> </p>
<p class=MsoNormal>If the registrar/registry is required by local law
enforcement authorities or a court to make changes in its practices affecting
compliance with <span class=SpellE>Whois</span>-related<span class=GramE>
contractual</span> obligations before any consultation process can occur, the
registrar/registry shall promptly notify the General Counsel of the changes
made and the law/regulation upon which the action was based. The
Registrar/Registry may request that ICANN keep all correspondence between the
parties confidential pending the outcome of the <span class=SpellE>Whois</span>
Proceeding. It is recommended that ICANN respond favorably to such
requests to the extent that they can be accommodated with other legal
responsibilities and basic principles of transparency applicable to ICANN
operations. </p>
<p class=MsoNormal> </p>
<p class=MsoNormal> </p>
<p class=MsoNormal><i>Step Three: General Counsel <span
class=GramE>analysis</span>
and recommendation</i></p>
<p class=MsoNormal><i> </i></p>
<p class=MsoNormal>If the local/national government requires changes (whether
before, during or after the consultation process described above)<span
class=GramE> that</span>, in the opinion of the General Counsel, prevent
full compliance with contractual WHOIS obligations, ICANN should consider the
following alternative to the normal enforcement procedure. Under this
alternative, ICANN would refrain, on a provisional basis, from taking
enforcement action against the registrar/registry for non-compliance, while the
General Counsel prepares a report and recommendation and submits it to the
ICANN Board for a decision. Such a report may contain: </p>
<p class=MsoNormal> </p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.5in'><span
class=SpellE>i</span>.<span
style='font-size:7.0pt'>
</span>A summary of the law or regulation involved in the conflict;</p>
<p class=MsoNormal style='margin-left:.5in'> </p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.5in'>ii.<span
style='font-size:7.0pt'>
</span>Specification of the part of the registry or registrar’s
contractual WHOIS obligations with which full compliance if being prevented;
</p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.5in'>iii.<span
style='font-size:7.0pt'>
</span>Summary of the consultation process if any under step two; and </p>
<p class=MsoNormal> </p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.5in'>iv.<span
style='font-size:7.0pt'>
</span>Recommendation of how the issue should be resolved, which may include
whether ICANN should provide an exception for the registrar/registry from one
or more identified WHOIS contractual provisions. The report should include a
detailed justification of its recommendation, including the anticipated impact
<span
style='color:black'>on the operational stability, reliability, security, or
global interoperability of the </span>Internet's unique identifier systems if
the recommendation were to be approved or <span class=GramE>denied <span
style='color:black'>.</span></span><span style='color:black'> </span></p>
<p class=MsoNormal style='text-indent:.5in'> </p>
<p class=MsoNormal>The registrar/registry should be provided a copy of the
report and provided a reasonable opportunity to comment on it to the
Board. The Registrar/Registry may request that ICANN keep such report
confidential prior to any resolution of the Board. It is recommended that
ICANN respond favorably to such requests to the extent that they can be
accommodated with other legal responsibilities and basic principles of
transparency applicable to ICANN operations. </p>
<p class=MsoNormal> </p>
<p class=MsoNormal style='text-indent:.5in'> </p>
<p class=MsoNormal style='text-indent:.5in'> </p>
<p class=MsoNormal style='page-break-after:avoid'><i>Step Four: Resolution
</i></p>
<p class=MsoNormal style='page-break-after:avoid'> </p>
<p class=MsoNormal style='page-break-after:avoid'>Keeping in the mind the
anticipated impact <span style='color:black'>on the operational stability,
reliability, security, or global interoperability of the </span>Internet's
unique identifier systems, the Board should consider and take appropriate
action on the recommendations contained in the General Counsel’s report
as soon as practicable. Actions could include, but are not limited to:</p>
<p class=MsoNormal> </p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.25in'><span
style='font-family:Symbol'>·</span><span
style='font-size:7.0pt'>
</span>Approving or rejecting the report’s recommendations, with or
without modifications;</p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.25in'><span
style='font-family:Symbol'>·</span><span
style='font-size:7.0pt'>
</span>Scheduling a public comment period on the report; or </p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.25in'><span
style='font-family:Symbol'>·</span><span
style='font-size:7.0pt'>
</span><span class=GramE>Referring</span> the report to GNSO for its review and
comment by a date certain.</p>
<p class=MsoNormal> </p>
<p class=MsoNormal> </p>
<p class=MsoNormal style='margin-left:.75in'> </p>
<p class=MsoNormal> </p>
<p class=MsoNormal><i>Step Five: Public Notice</i></p>
<p class=MsoNormal> </p>
<p
class=MsoNormal>
The Board’s resolution of the issue, together with the General
Counsel’s report, should ordinarily be made public, along with the
reasons for it, and be archived on a public website (along with other related
materials) for future research. Prior to release of such information to the
public, the Registry/Registrar may request that certain information (including,
but not limited to, communications between the Registry/Registrar and ICANN, or
other privileged/confidential information) be redacted from the public
notice. In the event that such redactions make it difficult to convey to
the public the nature of the actions being taken by the Registry/Registrar, the
General Counsel should work with the Registry/Registrar on an appropriate
notice to the public describing the actions being taken and the justification
for such actions. </p>
<p class=MsoNormal> </p>
<p class=MsoNormal>Unless the Board decides otherwise, if the result of its
resolution of the issue is that data elements in the registrar’s <span
class=SpellE>Whois</span> output will be removed or made less accessible, ICANN
should issue an appropriate notice to the public of the resolution and of the
reasons for ICANN’s forbearance from enforcement of full compliance with
the contractual provision in question. </p>
<p class=MsoHeader> </p>
<p class=MsoNormal> </p>
<p> </p>
<p> </p>
<p> </p>
<h3><a name="Section1_2">1.2 Results of Task Force Vote</a> </h3>
<p style='mso-outline-level:4'><b>This report will be the subject of a task
force vote to be held on Tuesday, August 30<sup>th</sup>, 2005. Results of the
vote will be inserted at that time.<o:p></o:p></b></p>
<h1><a name="_Toc100224740"></a><a name="OLE_LINK2"></a><a
name="OLE_LINK1"></a><a
name="_Toc101951780"></a>2 Constituency statements</h1>
<h3><a name="_Toc101951781">2.1 Commercial and Business User
Constituency</a></h3>
<p style='mso-outline-level:4'><strong> TBA</strong><b><o:p></o:p></b></p>
<p style='mso-outline-level:4'><strong> </strong><b><o:p></o:p></b></p>
<h3><a name="_Toc101951782">2.2 Non-Commercial User Constituency</a></h3>
<p class=MsoNormal style='mso-outline-level:4'><span class=GramE><b>NCUC
Statement on "<span class=SpellE>Whois</span> Task Force Policy
Recommendation and Advice on <span class=SpellE>Whois</span> Conflicts with
National and local Privacy Laws."</b></span><b><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b>The NCUC supports passage and
quick implementation of the "<span class=SpellE>Whois</span> Task Force
Policy Recommendation and<span class=GramE> Advice</span> on <span
class=SpellE>Whois</span> Conflicts with National Privacy Laws." The NCUC
views this procedure as a stop-gap measure that needs to be implemented pending
a more comprehensive reform of the <span class=SpellE>Whois</span> service to
make it conform to ICANN's<span class=GramE> mission</span>, national
privacy laws and international privacy norms.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b> <o:p></o:p></b></p>
<p
style='mso-outline-level:4'><strong> </strong><b><o:p></o:p></b></p>
<h3><a name="_Toc101951783">2.3 Intellectual Property Constituency</a></h3>
<p class=default style='mso-outline-level:4'><b>This statement responds to the
request for constituency input on the <span class=SpellE>Whois</span> Task
Force<span class=GramE> recommendations</span> regarding conflicts
between local law and <span class=SpellE>Whois</span> requirements. <i>See
</i>Call for constituency statements: WHOIS Consensus Policy & Procedure
for conflicts with national law, <i>at</i> <a
href="../../../../../../../../exchweb/bin/redir.asp%3fURL=http:/forum.icann.org/lists/gnso-dow123/msg00415.html"
target="_blank">http://forum.icann.org/lists/gnso-dow123/msg00415.html</a>.
Pursuant to requirements of the GSNO policy development process, outlined by
the ICANN bylaws, see Annex A, Sec. <span class=GramE>7(d</span>), available at
<u>http://www.icann.org/general/archive-bylaws/bylaws-19apr04.htm</u>, the IPC
came to the following conclusion. <o:p></o:p></b></p>
<p class=MsoNormal
style='mso-outline-level:4'><b>
<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b>The Intellectual Property
Interests Constituency (IPC) generally supports the “Policy/Advice
Recommendation on conflicts between national privacy laws and registries’
or registrars’ contractual obligations to ICANN.”<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b>While we agree with the
statement by <span class=SpellE>Whois</span> Task Force 2 that “there is
an ongoing risk of conflict between a registrar’s or <span
class=GramE>registry’s</span>
legal obligations under local privacy laws and their contractual obligations to
ICANN,” we believe this risk is generally low in the <span
class=SpellE>gTLD</span>
environment. Public access to <span class=SpellE>Whois</span> and local
privacy laws have coexisted for many years, and the likelihood is that this
will continue to be the case in the future. The main reasons for this are
(1) under ICANN’s contracts, no domain name may be registered in a
generic Top Level Domain until the registrant has been notified of, and
consented to, the uses and disclosures that may be made of personally
identifiable data submitted in connection with the registration;<a
name="_ftnref2"></a><a href="#_ftn2" title=""><span
style='mso-bookmark:_ftnref2'><span
class=MsoFootnoteReference>[2]</span></span><span
style='mso-bookmark:_ftnref2'></span></a><span
style='mso-bookmark:_ftnref2'></span> and (2) <span class=SpellE>Whois</span>
data has historically been, and continues to be, collected for the broad
purpose of enabling contact with the entities responsible for a given Internet
resource. Current ICANN agreements and long-standing registrar practices make
clear that public access is one of the purposes for which <span
class=SpellE>Whois</span>
data is collected. Indeed, the contractual obligations of the Registered
Name Holder <i>depend</i> on the public’s ability to access the
information and use it. <a name="_ftnref3"></a><a href="#_ftn3" title=""><span
style='mso-bookmark:_ftnref3'><span
class=MsoFootnoteReference>[3]</span></span><span
style='mso-bookmark:_ftnref3'></span></a><span
style='mso-bookmark:_ftnref3'></span><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b>However, because the risk of
conflict between RAA obligations and national law, while probably very low, is
not zero, we support the idea that ICANN should have a procedure in place for
handling claims of such conflicts. The alternative<span class=GramE>
--</span> to have no formal procedure in place for this eventuality –
could have adverse consequences. Registrars and registries might simply
unilaterally change their policies and practices so that they fail to comply
with ICANN agreements, and wait for compliance action from ICANN, if any.
This could create uncertainty, insecurity and instability in the domain name
system, and reduce uniformity of <span class=SpellE>Whois</span>
policies. The result could be confusion and frustration of the purposes
of the <span class=SpellE>Whois</span> database, to the detriment of
intellectual property owners, businesses, consumers, parents, law enforcement
agencies, and others who rely upon access to it. <o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='text-indent:.5in;mso-outline-level:4'><b>The goals
for the procedure, set out in item 2 of the Consensus Policy Recommendation,
are critical: <o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal
style='margin-left:75.0pt;text-indent:-.25in;mso-outline-level:
4'><b><span style='font-family:Symbol'>·</span></b><b><span style='font-size:
7.0pt'> </span>ICANN should be made
aware of a potential or asserted conflict as soon as possible, and where
appropriate ICANN should actively assist in efforts to resolve the issue in a
way that allows full compliance with both local law and contractual
obligations. For example, local law may require that the registrar do
more than the ICANN contract requires in order <span class=GramE>to
obtain</span>
a consent from the registrant, which is legally valid under that
jurisdiction’s laws, for a use of <span class=SpellE>Whois</span>
data. In such a circumstance, the registrar should be required to take
those extra steps to obtain such consent, if it is practical to do so, and if
consent obtained simply by following the contractual obligations would make the
use problematic under local law. <o:p></o:p></b></p>
<p class=MsoNormal
style='margin-left:75.0pt;text-indent:-.25in;mso-outline-level:
4'><b><span style='font-family:Symbol'>·</span></b><b><span style='font-size:
7.0pt'> </span>The mechanism for
recognizing an exception to contractual obligations should be exercised only in
extraordinary circumstances, and should not be mandatory or automatic whenever
efforts at resolution meet an impasse. Recognizing exceptions could have
adverse impacts on the security and stability of the current system, and on the
competitive playing field among registrars. Conceivably, the application of
some local law could be so rigid or <o:p></o:p></b></p>
<p class=MsoNormal
style='margin-left:75.0pt;text-indent:-.25in;mso-outline-level:
4'><b><span style='font-family:Symbol'>·</span></b><b><span style='font-size:
7.0pt'> </span>demanding that a
registrar or registry subject to that law simply cannot fulfill its contractual
obligations to ICANN and thus the contractual relationship must be phased out.<a
name="_ftnref4"></a><a href="#_ftn4" title=""><span
style='mso-bookmark:_ftnref4'><span
class=MsoFootnoteReference>[4]</span></span><span
style='mso-bookmark:_ftnref4'></span></a><span
style='mso-bookmark:_ftnref4'></span> <o:p></o:p></b></p>
<p class=MsoNormal
style='margin-left:75.0pt;text-indent:-.25in;mso-outline-level:
4'><b><span style='font-family:Symbol'>·</span></b><b><span style='font-size:
7.0pt'> </span> Finally,
flexibility is critical, since we cannot now anticipate the specific contours
of a future potential conflict, and the legal issues – beginning with
which jurisdiction’s law is even applicable – may be extremely
complex. <o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4'><b>In general, IPC believes the
Recommended Procedure meets these goals and forms a good starting point for
development of the policy. The General Counsel (or some other ICANN staff
person) should be designated to receive notifications of potential conflicts,
to engage in consultation efforts to help resolve them, and to inform the Board
and ultimately the ICANN community of any action that needs to be taken.
While this may include, in an extraordinary case, forbearance from full
enforcement
of contractual obligations, it may also include enforcement action to compel
compliance. <o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='text-indent:.5in;mso-outline-level:4'><b>IPC offers a
few specific comments regarding the Recommended Procedure, which it urges the
ICANN staff to consider in formulating its own procedure:<o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b>A.
We are concerned that the confidentiality provisions in Steps One, Two, and
Three could, as a practical matter, foreclose the ability of interested parties
to question or rebut the need for a departure from the RAA on a case-by-case
basis. Such an ability to question a registrar’s assertion of a conflict
in a specific case is particularly important in light of the sparse or
non-existent history of insurmountable conflicts between national laws and the
RAA. Although we agree there could be circumstance in which confidentiality
might be necessary, the policy should not favor such requests, and in fact
should specify that they would be granted only in unusual
circumstances.<o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b>B.
The statement near the end of Step One that “Meeting the notification
requirements permits Registrar/Registries to participate in investigations and
respond to court orders, regulations, or enforcement authorities in a manner
and course deemed best by their counsel” is ambiguous. This
language may be intended to provide an incentive for registrars to comply with
the notification requirements set out in Step One. However, the
consequence of failing to meet the notification requirements is not
specified. On the other hand, it may be that this sentence is intended as
an explanatory comment only. <o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='text-indent:.5in;mso-outline-level:4'><b>C.
"Step Four: Resolution” should
re-emphasize the goal of achieving uniform <span class=SpellE>Whois</span>
disclosure requirements. Therefore, we suggest amending the first
sentence to read as follows: “Keeping in the mind the anticipated impact
on the operational stability, reliability, security, or global interoperability
of the Internet's unique identifier systems, <i><u>and the value of
uniform <span class=SpellE>Whois</span> requirements applying to all
Registrars/Registries to the extent possible,</u></i> the Board should consider
and take appropriate action on the recommendations contained in the General
Counsel’s report as soon as practicable.”<o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b>D.
The Public Notice portion of the Procedure should include information about how
information made less accessible can be accessed through other sources.
For example, if a departure from the RAA resulted in the registrant’s
name but not address being made available, the notice should include
information on alternative ways in which such information might be
obtained.
Therefore, the final sentence of the recommendation should be amended as
follows: “Unless the Board decides otherwise, if the result of its
resolution of the issue is that data elements in the registrar’s <span
class=SpellE>Whois</span> output will be removed or made less accessible, ICANN
should issue an appropriate notice to the public of the resolution and of the
reasons for ICANN’s forbearance from enforcement of full compliance with
the contractual provision in question<i><u>, including relevant contact
information for how such data might be accessed in appropriate
circumstances</u></i>.”
<o:p></o:p></b></p>
<p class=MsoNormal style='text-indent:.5in;mso-outline-level:4'><b>
<o:p></o:p></b></p>
<p class=MsoNormal
style='text-indent:.5in;mso-outline-level:4'><b> <o:p></o:p></b></p>
<pre style='mso-outline-level:4'><span class=SpellE><b><span style='font-size:
12.0pt;font-family:"Times New Roman"'>i</span></b></span><b><span
style='font-size:12.0pt;font-family:"Times New Roman"'>) If a Supermajority
Vote was reached, a clear statement of the constituency's position on the
issue;</span><o:p></o:p></b></pre><pre
style='mso-outline-level:4'><b><span style='font-size:12.0pt;font-family:"Times
New Roman"'> </span><o:p></o:p></b></pre><pre
style='mso-outline-level:4'><b><span style='font-size:12.0pt;font-family:"Times
New Roman"'>See above. </span><o:p></o:p></b></pre>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<pre style='mso-outline-level:4'><b><span style='font-size:12.0pt;font-family:
"Times New Roman"'>(ii) If a Supermajority Vote was not reached, a clear
statement of all positions espoused by constituency
members;</span><o:p></o:p></b></pre>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>N/A
<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<pre style='mso-outline-level:4'><b><span style='font-size:12.0pt;font-family:
"Times New Roman"'>(iii) A clear statement of how the constituency arrived at
its position(s). Specifically, the statement should detail specific
constituency meetings,</span><o:p></o:p></b></pre><pre
style='mso-outline-level:4'><span class=GramE><b><span style='font-size:12.0pt;
font-family:"Times New Roman"'>teleconferences</span></b></span><b><span
style='font-size:12.0pt;font-family:"Times New Roman"'>, or other means of
deliberating an issue, and a list of all members who participated or otherwise
submitted their views;</span><o:p></o:p></b></pre>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
IPC membership was notified of the request for a constituency statement on June
22. A draft constituency statement was circulated on July 8. The
statement and the issue were discussed at the IPC meeting in
</b><st1:country-region><st1:place><b>Luxembourg</b></st1:place></st1:country-region><b>
on July 11. A revised version of the statement was circulated on July 20
and discussed on an IPC membership call on July 22. At that
meeting, on a motion, which was seconded, it was agreed without objection to
approve the constituency statement, subject to minor drafting changes.
<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>
<o:p></o:p></b></p>
<pre style='mso-outline-level:4'><span class=GramE><b><span style='font-size:
12.0pt;font-family:"Times New Roman"'>(iv) An</span></b></span><b><span
style='font-size:12.0pt;font-family:"Times New Roman"'> analysis of how the
issue would affect the constituency, including any financial impact on the
constituency; </span><o:p></o:p></b></pre>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>As
noted above, a sound policy in this area would benefit the constituency, whose
members rely upon public access to <span class=SpellE>Whois</span> data to
manage their domain name portfolios, enforce their rights against copyright and
trademark infringers, and combat <span class=SpellE>cybersquatting</span>,
among other purposes. The lack of a policy in this area could ultimately
reduce this access to <span class=SpellE>Whois</span> data, make access less
uniform and predictable, reduce transparency and accountability, and encourage
infringers and other violators to utilize particular registrars or registries
in order to evade detection or enforcement efforts. This would have an
adverse financial impact on constituency members. <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<pre style='mso-outline-level:4'><b><span style='font-size:12.0pt;font-family:
"Times New Roman"'>(v) An analysis of the period of time that would likely be
necessary to implement the policy.</span><o:p></o:p></b></pre>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>While
this question should be directed to ICANN staff, IPC believes that the
recommended procedure is a sufficiently good starting point that a formal
procedure could be promulgated within a short time after approval of this
recommendation. <o:p></o:p></b></p>
<p style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt
274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt
732.8pt'><strong> </strong><b><o:p></o:p></b></p>
<h3 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt
366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_Toc101951784">2.4 Registrar Constituency</a></h3>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><a
name="_Toc101951785"><b>A marked copy of the edits to the proposal recommended
by the Registrar Constituency position is included below. These recommendations
have been reviewed by the Registrar Constituency and ratified by a
super-majority vote conducted in accordance with the Registrar Constituency
Bylaws.</b></a><b><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>A
summary of the recommended changes is as follows:<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>1.
Section II should be positioned as guidance for the staff in establishing
recommended procedures for handling WHOIS conflicts with national law. Section
II therefore would be a non-exhaustive, non-binding suggestion rather than a
consensus policy recommendation that must be implemented as
written.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>2.
Section II, Step 2 should include additional language that ensures that the
registrar in question has worked with staff to identify whether or not a
solution exists that satisfies the requirements of local law and the ICANN
policy in question.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>3.
There are other minor stylistic edits redlined throughout the
document.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>N.B.
Additional text is marked in italics and bold. Text that is suggested for
deletion is marked in strikethrough mode. <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><span
style='font-variant:small-caps'> </span><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><span
style='font-variant:small-caps'>“Consensus Policy
Recommendation</span><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>In
order to facilitate reconciliation of any conflicts between local/national
mandatory privacy laws or regulations and applicable provisions of the ICANN
contract regarding the collection, display and distribution of personal data
via <span class=SpellE>Whois</span>, ICANN should: <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>1.
Develop and publicly document a procedure for dealing with the situation in
which a registrar or registry can credibly demonstrate that it is legally
prevented by local/national privacy laws or regulations from fully complying
with applicable provisions of its ICANN contract regarding the collection,
display and distribution of personal data via WHOIS.
<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>2.
Create goals for the procedure which include: <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt
732.8pt'><b>
a.<span class=GramE> Ensuring</span> that ICANN staff is informed of a
conflict at the earliest appropriate juncture;<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt
732.8pt'><b>
b.<span class=GramE> Resolving</span> the conflict, if possible, in a
manner conducive to stability and uniformity of the <span
class=SpellE>Whois</span>
system;<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt
732.8pt'><b>
c. Providing a mechanism for the recognition, in appropriate
circumstances where the conflict cannot be otherwise resolved, of an exception
to contractual obligations <i>for all registrars</i> with regard to collection,
display and distribution of personally identifiable data via <span
class=SpellE>Whois</span>; and <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt
732.8pt'><b>
d.<span class=GramE> Preserving</span> sufficient flexibility for ICANN
staff to respond to particular factual situations as they
arise.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>II.<span
class=GramE> <s>Text</s></span><s> of Recommended </s><i>Guidance</i>
on Procedure<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><span
style='font-variant:small-caps'>Well-Developed Advice on a Procedure for
Handling WHOIS Conflicts</span><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><span
style='font-variant:small-caps'> with Privacy Law
</span><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>Based
on extensive research and negotiation among Task Force 2 together with the
merged Task Force and ICANN staff, the following procedure for handling the
policy recommendation set out in Section I above is set out as a Recommended
<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><span
class=GramE><b>Step-by-Step Procedure for Resolution of WHOIS Conflicts with
Privacy Law.</b></span><b> We encourage ICANN staff to use this
Recommended Procedure as a starting point for developing the procedure called
for in the Consensus Policy Recommendation above. <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><i>Step
One: Notification of Initiation of Action</i><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>Once
receiving notification of an investigation, litigation, regulatory proceeding
or other government or civil action that might affect its compliance with the
provisions of the RAA or other contractual agreement with ICANN dealing with
the collection, display or distribution of personally identifiable data via
<span
class=SpellE>Whois</span> (“<span class=SpellE>Whois</span>
Proceeding”), a Registrar/ Registry must within thirty (30) days provide
ICANN’s General Counsel (or other staff member as designated by ICANN)<a
name="_ftnref5"></a><a href="#_ftn5" title=""><span
style='mso-bookmark:_ftnref5'><span
class=MsoFootnoteReference>[5]</span></span><span
style='mso-bookmark:_ftnref5'></span></a><span
style='mso-bookmark:_ftnref5'></span> with the following information:
<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal
style='margin-left:39.35pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
class=GramE><b><span style='font-family:Symbol'>·</span></b><b><span
style='font-size:7.0pt'>
</span>Summary
description of the nature and status of the action (e.g., inquiry,
investigation, litigation, threat of sanctions,
etc.)</b></span><b><o:p></o:p></b></p>
<p class=MsoNormal
style='margin-left:39.35pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
class=GramE><b><span style='font-family:Symbol'>·</span></b><b><span
style='font-size:7.0pt'>
</span>Contact
information for the responsible official of the registrar/registry for
resolving the problem.</b></span><b><o:p></o:p></b></p>
<p class=MsoNormal
style='margin-left:39.35pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
class=GramE><b><span style='font-family:Symbol'>·</span></b><b><span
style='font-size:7.0pt'>
</span>Contact
information for the responsible territorial government agency or other claimant
and a statement from the registrar/registry authorizing ICANN to communicate
with those officials or claimants on the matter.</b></span><b> If the
registrar/registry is prevented by applicable law from granting such
authorization, the notification should document this.<o:p></o:p></b></p>
<p class=MsoNormal
style='margin-left:39.35pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
style='font-family:Symbol'>·</span></b><span class=GramE><b><span
style='font-size:7.0pt'>
</span>The</b></span><b>
text of the applicable law or regulations upon which the local government or
other claimant is basing its action or investigation, if such information has
been
indicated by the government or other claimant.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>Meeting
the notification requirement permits Registrars/Registries to participate in
investigations and respond to court orders, regulations, or enforcement
authorities in a manner and course deemed best by their
counsel.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>Depending
on the specific circumstances of the <span class=SpellE>Whois</span>
Proceeding, the Registrar/Registry may request that ICANN keep all
correspondence between the parties confidential <span class=GramE>pending</span>
the outcome of the <span class=SpellE>Whois</span> Proceeding. It is
recommended that ICANN respond favorably to such requests to the extent that
they can be accommodated with other legal responsibilities and basic principles
of transparency applicable to ICANN operations. <o:p></o:p></b></p>
<p class=MsoNormal style='text-indent:.5in;mso-outline-level:4;tab-stops:45.8pt
91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt
549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='page-break-after:avoid;mso-outline-level:4;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt
458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><i>Step
Two: Consultation</i><o:p></o:p></b></p>
<p class=MsoNormal style='page-break-after:avoid;mso-outline-level:4;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt
458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt
732.8pt'><b><i> </i><o:p></o:p></b></p>
<p class=MsoNormal style='page-break-after:avoid;mso-outline-level:4;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt
458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b>Unless
impractical under the circumstances, we recommend that the ICANN General
Counsel, upon receipt and review of the notification and, where appropriate,
dialogue with the registrar/registry, consider beginning a process of
consultation with the local/national enforcement authorities or other claimant
together with the registrar/registry. The goal of the consultation
process should be to seek to resolve the problem in a manner that preserves the
ability of the registrar/registry to comply with its contractual obligations to
the greatest extent possible. <o:p></o:p></b></p>
<p class=MsoNormal style='page-break-after:avoid;mso-outline-level:4;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt
458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt
732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='page-break-after:avoid;mso-outline-level:4;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt
458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><i>The
Registrar should attempt to identify a solution that allows the registrar to
meet the requirements of both the local law and ICANN obligations. The
General Counsel can assist in advising the registrar on whether the proposed
solution meets the ICANN obligations.</i><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>If
the <span class=SpellE>Whois</span> proceeding<span class=GramE>
ends</span>
without requiring any changes and/or the required changes in registrar/registry
practice do not, in the opinion of the General Counsel, constitute a deviation
from the R.A.A. or other contractual obligation , then the General Counsel and
the registrar/registry need to take no further action. <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>If
the registrar/registry is required by local law enforcement authorities or a
court to make changes in its practices affecting compliance with <span
class=SpellE>Whois</span>-related<span class=GramE> contractual</span>
obligations before any consultation process can occur, the registrar/registry
shall promptly notify the General Counsel of the changes made and the
law/regulation upon which the action was based. The
Registrar/Registry may request that ICANN keep all correspondence between the
parties confidential pending the outcome of the <span class=SpellE>Whois</span>
Proceeding. It is recommended that ICANN respond favorably to such
requests to the extent that they can be accommodated with other legal
responsibilities and basic principles of transparency applicable to ICANN
operations. <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><i>Step
Three: General Counsel <span class=GramE>analysis</span> and
recommendation</i><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><i> </i><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>If
the local/national government requires changes (whether before, during or after
the consultation process described above)<span class=GramE> that</span>,
in the opinion of the General Counsel, prevent full compliance with contractual
WHOIS obligations, ICANN should consider the following alternative to the
normal enforcement procedure. Under this alternative, ICANN would
refrain, on a provisional basis, from taking enforcement action against the
registrar/registry for non-compliance, while the General Counsel prepares a
report and recommendation and submits it to the ICANN Board for a decision.
Such a report may contain: <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='margin-left:.5in;mso-outline-level:4;tab-stops:45.8pt
91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt
549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
class=SpellE><span class=GramE><b>i</b></span></span><b> A summary
of the law or regulation involved in the conflict;<o:p></o:p></b></p>
<p class=MsoNormal style='margin-left:.5in;mso-outline-level:4;tab-stops:45.8pt
91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt
549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.5in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b>ii<span
class=GramE> Specification</span> of the part of the registry or
registrar’s contractual WHOIS obligations with which full compliance if
being prevented; <o:p></o:p></b></p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.5in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt
732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='margin-left:.5in;mso-outline-level:4;tab-stops:45.8pt
91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt
549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
class=GramE><b>iii</b></span><b> Summary of the consultation process if any
under step two; and <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='margin-left:1.0in;text-indent:-.5in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b>iv
Recommendation of how the issue should be resolved, which may include whether
ICANN should provide an exception for <s>the</s> <i>all</i>
registrar<i>s</i>/registr<i>ies</i>
from one or more identified WHOIS contractual provisions. The report should
include a detailed justification of its recommendation, including the
anticipated impact <span style='color:black'>on the operational stability,
reliability, security, or global interoperability of the </span>Internet's
unique identifier systems if the recommendation were to be approved or denied
<span
style='color:black'>. </span><o:p></o:p></b></p>
<p class=MsoNormal style='text-indent:.5in;mso-outline-level:4;tab-stops:45.8pt
91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt
549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
registrar/registry should be provided a copy of the report and provided a
reasonable opportunity to comment on it to the Board. The
Registrar/Registry may request that ICANN keep such report confidential prior
to any resolution of the Board. It is recommended that ICANN respond
favorably to such requests to the extent that they can be accommodated with
other legal responsibilities and basic principles of transparency applicable to
ICANN operations.” <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>End
of proposed changes to the recommendation and advice.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
Registrar Constituency proposed no changes to the remaining sections of the
procedure: <i>Step Four: Resolution </i>and<span class=GramE>
<i>Step</i></span><i>
Five: Public Notice</i><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoHeader style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<h3 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt
366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'>2.5
Registry Constituency statement</h3>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>This
statement responds to the request for constituency input on the WHOIS COMBINED
TASK FORCE Policy/Advice Recommendation 2 on conflicts between national privacy
laws and registries' or registrars' contractual obligations to
ICANN.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>Pursuant
to requirements of the GSNO policy development process, the Registry
Constituency (<span class=SpellE>RyC</span>) has concluded:<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>I.
Constituency Position<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
<span class=SpellE>RyC</span> supports the general principles of the
Policy/Advice Recommendation 2 on conflicts between national privacy laws and
registries' or registrars' contractual obligations to ICANN. The <span
class=SpellE>RyC</span> further believes that the recommended procedures should
deal with the possibility of the following: <o:p></o:p></b></p>
<p class=MsoNormal style='margin-left:.5in;mso-outline-level:4;tab-stops:45.8pt
91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt
549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b>(1)
If exceptions to contractual requirements are made to accommodate local law(s)
for one registrar or registry in a local jurisdiction, should the same
exceptions be extended to other registrars and registries in that jurisdiction
and, if so, how should that take place; and<o:p></o:p></b></p>
<p class=MsoNormal style='margin-left:.5in;mso-outline-level:4;tab-stops:45.8pt
91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt
549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> (2)
If exceptions to contractual requirements are made to accommodate local law(s),
it is possible that the variation in requirements for different registrars or
registries will begin to create a fragmented experience for users and therefore
create a need to revisit the contractual requirement in a broader
way</b><b><span
style='font-size:10.0pt;font-family:Arial;color:blue'>.</span><o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
<span class=SpellE>RyC</span> also believes that the Combined Task Force should
include, in its final Recommendation, a further recommendation that affording
tiered access to WHOIS data be available to registrars and registries as a
means of complying with local legal requirements when
applicable.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>II.
Method for Reaching Agreement on <span class=SpellE>RyC</span> Position
<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
<span class=SpellE>RyC</span> drafted and circulated via email a constituency
statement, soliciting input from its members. <span class=SpellE><span
class=GramE>RyC</span></span><span class=GramE> members suggested edits and
additions to the draft which were subsequently incorporated into the final
constituency statement.</span> The statement was adopted by a unanimous vote.
One constituency member, <span class=SpellE>RegistryPro</span> did not take
part in the vote. <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>III.
Impact on Constituency<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
Policy/Advice Recommendation 2 in its present form would assist the members of
the <span class=SpellE>RyC</span> in fulfilling their legal obligations in
their respective jurisdictions. It should be noted, however, that the
Policy/Advice Recommendation 2 does not purport to provide complete assurance
that potential conflicts can be avoided or resolved.<o:p></o:p></b></p>
<span style='font-size:12.0pt;font-family:"Times New
Roman";mso-fareast-font-family:
"Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US;
mso-bidi-language:AR-SA'><br clear=all style='page-break-before:always'>
</span>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>IV.
Time Period Necessary to Complete Implementation<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>We
anticipate that the Policy/Advice Recommendation 2 supported by this statement
would not require an extensive time period to implement. <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt
274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt
732.8pt'><b> <o:p></o:p></b></p>
<h3 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt
366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_Toc101951786">2.6 Internet Service Providers & Connectivity
Providers Constituency</a></h3>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><u>Introduction</u><o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
Internet Service Providers & Connectivity Providers Constituency (ISPCP
Constituency) herein provides input to the combined <span
class=SpellE>Whois</span>
Task Force on its recommendations on policies related to the <span
class=SpellE>Whois</span> database as required by the ICANN GNSO policy
development process. Specifically, the task force has put forth a
recommendation on procedures to be followed in the event of a conflict between
national privacy laws and registry/registrar contractual obligations to
ICANN<o:p></o:p></b></p>
<p class=MsoBodyText style='margin-left:.25in;mso-outline-level:4;tab-stops:
45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt
503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><u>The
ISPCP constituency views on conflict of law resolution
process.</u><o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
ISPCP is generally supportive of the task force recommendations on how
conflicts shall be addressed in the event of a conflict between the national
laws of a registrar or registry’s home base and its ICANN contract.
<o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
ISPCP does not deem such conflicts to be a common occurrence in the <span
class=SpellE>gTLD</span> or <span class=SpellE>ccTLD</span> space and further,
we do not see any indicators that this trend is likely to change in the
foreseeable future. We are guided in our belief by the examination of the
record over the course of the past several years where, in the <span
class=SpellE>gTLD</span> and <span class=SpellE>ccTLD</span> space, registries
and registrars have rarely had reason to challenge their contractual
obligations related to <span class=SpellE>Whois</span> disclosures as a result
of conflicting national or local privacy laws. <o:p></o:p></b></p>
<p class=MsoNormal style='text-align:justify;mso-outline-level:4;tab-stops:
45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt
503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='text-align:justify;mso-outline-level:4;tab-stops:
45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt
503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b>This
was further evidenced by the previous <span class=SpellE>Whois</span> Task
Force 2 findings during a survey completed in 2004. Within the EU member
states’ <span class=SpellE>ccTLD</span> operators, those who submitted
survey responses indicated that they work closely with their respective
country’s data protection authorities and are in full compliance with
their respective privacy laws. <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><u>ISPCP
Position</u><o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
majority of established privacy regimes throughout many regions of the world
require that actual information use and disclosure practices <span
class=GramE>be</span>
limited to the list of intended use and disclosure practices that are provided
to the data subject at the time of data collection. Accordingly, once
more conspicuous disclosure is provided and consent obtained, the subsequent
use of the registrant data for <span class=SpellE>Whois</span> purposes,
pursuant to the ICANN contract, is not likely to be in conflict with local or
national laws. <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
ISPCP believes that once registrants receive notice of the intended uses of
their registration data as it relates to the <span class=SpellE>Whois</span>
database, there is little reason for future use in accordance with the contract
terms to somehow come in conflict with applicable privacy laws. The
likelihood of a conflict is further reduced once the more conspicuous notice
requirements go into <span class=GramE>affect,</span> and registrants are
better alerted to the possible uses of the personally identifiable registration
data they provide. <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>Nevertheless,
if a scenario arises whereby such conflict does arise, the ISPCP strongly
favors the implementation of a process, clearly defined and transparent, that
sets forth the steps in resolving any possible conflict. In reviewing the
proposal set forth by the <span class=SpellE>Whois</span> task force, the ISPCP
finds it to be well thought out, neutral and respectful of the needs and
interests of the ICANN community and the registry/registrar
organizations. Our constituency believes that no organization should be
placed in a situation where it must choose between breaking its contractual
obligations or violate applicable law, and we do not believe that any of the
ICANN RAA terms are likely to do that. <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>Based
upon the forgoing values, we strongly urge the <span class=SpellE>Whois</span>
task force to consider the following concepts prior to finalizing its policy
recommendations related to conflict of law issues. <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText
style='margin-left:43.5pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
style='font-family:Symbol'>·</span></b><b><span
style='font-size:7.0pt'>
</span>Transparency is paramount. It is not only a major tenet of the
ICANN policy development <span class=GramE>process,</span> it is also an
implicit aspect of most privacy laws. Without full disclosure and
transparency in the manner that information is collected and used, there can
hardly be a viable notion of privacy protection. While
confidentiality of actions, negotiations and discussions may be necessary in
some instances, it is not always a requirement or the most useful manner in
which to resolve conflict. Thus, the ISPCP believes that to the extent
possible, the ICANN community be notified when the resolution process is begun
and as much as possible throughout the process as well. <o:p></o:p></b></p>
<p class=MsoBodyText style='margin-left:25.5pt;mso-outline-level:4;tab-stops:
45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt
503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText
style='margin-left:43.5pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
style='font-family:Symbol'>·</span></b><b><span
style='font-size:7.0pt'>
</span>Outcomes should be uniform. Some have indicated that legal
obstacles will be used by registries or registrars to obtain competitive
advantages, resulting in forum shopping. The ISPCP has not seen any
evidence that this is in fact reality. Nevertheless, in order to remove
the perception that this may be happening, the recommendation should emphasize
the importance of uniformity and consistency of handling conflicts should they
arise. <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText
style='margin-left:79.5pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
class=GramE><b><span style='font-family:"Courier
New"'>o</span></b></span><b><span
style='font-size:7.0pt'> </span>It is
worthy to note that transparency of the process will inevitably lead to more
uniformity and better consistency among conflicts that do
arise.<o:p></o:p></b></p>
<p class=MsoBodyText style='margin-left:97.5pt;mso-outline-level:4;tab-stops:
45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt
503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText
style='margin-left:43.5pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
style='font-family:Symbol'>·</span></b><b><span
style='font-size:7.0pt'>
</span>Review should be ongoing. The ISPCP believes that there will be
some lessons learned from the first instance where this process is
implemented. With substantial input from the relevant registry or
registrar, together with all constituencies, there should be a review of the
pros and cons of how the process worked, and the development of revisions
designed to make the process better and more efficient, should the need arise
again at some point in the future.<o:p></o:p></b></p>
<p class=MsoBodyText style='margin-left:25.5pt;mso-outline-level:4;tab-stops:
45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt
503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText
style='margin-left:79.5pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
class=GramE><b><span style='font-family:"Courier
New"'>o</span></b></span><b><span
style='font-size:7.0pt'> </span>Again,
we’d like to highlight the fact that this goal will be easier met when
there is transparency and uniformity throughout the process.
<o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText
style='margin-left:43.5pt;text-indent:-.25in;mso-outline-level:
4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt
412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
style='font-family:Symbol'>·</span></b><b><span
style='font-size:7.0pt'>
</span>Accuracy is the goal. If this and other recommendations do not work
towards improved accuracy, the system will remain substantially flawed. The
ISPCP task force members have participated in good faith to achieve the
improved privacy protections that are important to community. The constituency
expects that all members of the task force, and the chair and ICANN staff
especially,
show commitment to improved accuracy and quickly move on to developing changes
aimed at the same.<o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b><u>Conclusion</u><o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>The
ISPCP hereby thanks the task force for its work in this matter and looks
forward to seeing a better <span class=SpellE>Whois</span> experience for all
stakeholders who develop, populate, oversee and use the <span
class=SpellE>Whois</span>
databases. <o:p></o:p></b></p>
<p class=MsoBodyText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<h1 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt
366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_Toc101951795"></a><a name=3.7.7.4></a>Annex 1 Relevant provisions of the
Registrar Accreditation Agreement</h1>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b>3.7.2
Registrar shall abide by applicable laws and governmental
regulations.<o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<p style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt
274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt
732.8pt'><a
name="_ftn7"></a><b><a href="#_ftnref7"></a><o:p></o:p></b></p>
<p style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt
274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt
732.8pt'><a
name="_ftn8"></a><b><a href="#_ftnref8"></a><o:p></o:p></b></p>
<p style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt
274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt
732.8pt'><a
name="_ftn9"></a><b><a href="#_ftnref9"></a> <o:p></o:p></b></p>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
<div>
<h3 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt
366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><br
clear=all style='mso-special-character:line-break'>
</h3>
<h3 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt
366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'>
<hr size=1 width="33%" align=left>
</h3>
<div id=ftn1>
<p class=MsoFootnoteText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt
137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt
595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_ftn1"></a><a href="#_ftnref1" title=""><span
style='mso-bookmark:_ftn1'><span
class=MsoFootnoteReference><b>[1]</b></span></span><span style='mso-bookmark:
_ftn1'></span></a><span style='mso-bookmark:_ftn1'></span><b> For simplicity,
this designated official is referred to hereafter as the General Counsel, with
the understanding that the functions described may be allocated differently
among the ICANN staff. <o:p></o:p></b></p>
</div>
<div id=ftn2>
<p class=MsoFootnoteText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt
137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt
595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_ftn2"></a><a href="#_ftnref2" title=""><span
style='mso-bookmark:_ftn2'><span
class=MsoFootnoteReference><b>[2]</b></span></span><span style='mso-bookmark:
_ftn2'></span></a><span style='mso-bookmark:_ftn2'></span><b> See RAA
Subsections 3.7.7.4 and 3.7.7.5. <o:p></o:p></b></p>
</div>
<div id=ftn3>
<p class=MsoNormal style='mso-outline-level:4;tab-stops:45.8pt 91.6pt 137.4pt
183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt
641.2pt 687.0pt 732.8pt'><a
name="_ftn3"></a><a href="#_ftnref3" title=""><span
style='mso-bookmark:_ftn3'><span
class=MsoFootnoteReference><b>[3]</b></span></span><span style='mso-bookmark:
_ftn3'></span></a><span style='mso-bookmark:_ftn3'></span><b> </b><b><span
style='font-size:10.0pt'>Most notably, Registered Name Holders agree to be
subject
to the Uniform Dispute Resolution Policy, as imposed by RAA Subsection
3.7.7.11. It is impossible for a member of the public claiming trademark rights
to bring a proceeding under the UDRP <u>without</u> using <span
class=SpellE>Whois</span>
data to specify the Respondent. <span class=GramE><i>See, e.g.</i>, <i>Wells
Fargo & Co. v. Doe</i>, No.</span> <span class=GramE>FA0411000362108 (Nat.
<span
class=SpellE>Arb</span>.</span> Forum Dec. 30, 2004) (ruling on
complainant’s request to name “John Doe” as the respondent
because the actual registrant had inserted the personal information of an
innocent identity theft victim in the <span class=SpellE>Whois</span> database,
the panel held that under the UDRP the complainant <u>must</u> name the party
appearing in the <span class=SpellE>Whois</span> record as the Respondent in
the complaint, but could request that the panel replace that name with
“John Doe” in its published opinion</span>).<o:p></o:p></b></p>
<p class=MsoFootnoteText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt
137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt
595.4pt 641.2pt 687.0pt 732.8pt'><b> <o:p></o:p></b></p>
</div>
<div id=ftn4>
<p class=MsoFootnoteText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt
137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt
595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_ftn4"></a><a href="#_ftnref4" title=""><span
style='mso-bookmark:_ftn4'><span
class=MsoFootnoteReference><b>[4]</b></span></span><span style='mso-bookmark:
_ftn4'></span></a><span style='mso-bookmark:_ftn4'></span><b> Similarly, if a
local law is applied to prevent registrars from obtaining valid consent from
registrants in a particular jurisdiction, it may ultimately no longer be
possible for such registrars to accept such registrations<o:p></o:p></b></p>
</div>
<div id=ftn5>
<p class=MsoFootnoteText style='mso-outline-level:4;tab-stops:45.8pt 91.6pt
137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt
595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_ftn5"></a><a href="#_ftnref5" title=""><span
style='mso-bookmark:_ftn5'><span
class=MsoFootnoteReference><b>[5]</b></span></span><span style='mso-bookmark:
_ftn5'></span></a><span style='mso-bookmark:_ftn5'></span><b> For simplicity,
this designated official is referred to hereafter as the General Counsel, with
the understanding that the functions described may be allocated differently
among the ICANN staff. <o:p></o:p></b></p>
</div>
</div>
</div>
</body>
</html>
--Apple-Mail-7-643692416--
--Apple-Mail-6-643692415--
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|