<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Please add my name also. Good work.<br>
<br>
Nicolas Adam<br>
<br>
<div class="moz-cite-prefix">On 13/03/2015 2:11 PM, Kathy Kleiman
wrote:<br>
</div>
<blockquote cite="mid:5503286E.5090904@kathykleiman.com" type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<o:smarttagtype
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="stockticker"><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
</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 Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;
mso-font-charset:2;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-536870145 1073786111 1 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin-top:0in;
margin-right:0in;
margin-bottom:8.0pt;
margin-left:0in;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:Calibri;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
color:#0563C1;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
p
{mso-style-noshow:yes;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:Calibri;}
p.ListParagraph, li.ListParagraph, div.ListParagraph
{mso-style-name:"List Paragraph";
margin-top:0in;
margin-right:0in;
margin-bottom:8.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:Calibri;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
p.ListParagraphCxSpFirst, li.ListParagraphCxSpFirst, div.ListParagraphCxSpFirst
{mso-style-name:"List ParagraphCxSpFirst";
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:Calibri;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
p.ListParagraphCxSpMiddle, li.ListParagraphCxSpMiddle, div.ListParagraphCxSpMiddle
{mso-style-name:"List ParagraphCxSpMiddle";
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:Calibri;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
p.ListParagraphCxSpLast, li.ListParagraphCxSpLast, div.ListParagraphCxSpLast
{mso-style-name:"List ParagraphCxSpLast";
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:8.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:Calibri;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
p.Default, li.Default, div.Default
{mso-style-name:Default;
mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
mso-layout-grid-align:none;
text-autospace:none;
font-size:12.0pt;
font-family:Calibri;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:Calibri;
color:black;}
@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:436798382;
mso-list-type:hybrid;
mso-list-template-ids:-467795212 832970478 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:roman-upper;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.5in;
mso-bidi-font-family:"Times New Roman";}
@list l1
{mso-list-id:715273727;
mso-list-type:hybrid;
mso-list-template-ids:2047491072 -946837770 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.25in;
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.5in;
text-indent:-.25in;
mso-bidi-font-family:"Times New Roman";}
@list l2
{mso-list-id:935165720;
mso-list-type:hybrid;
mso-list-template-ids:755943590 -156453420 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-start-at:4;
mso-level-number-format:roman-upper;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.5in;
mso-bidi-font-family:"Times New Roman";}
@list l3
{mso-list-id:1568031947;
mso-list-type:hybrid;
mso-list-template-ids:502179168 240931314 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l3:level1
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
mso-bidi-font-family:"Times New Roman";}
@list l4
{mso-list-id:1764454596;
mso-list-template-ids:-1328108636;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l5
{mso-list-id:1784767240;
mso-list-type:hybrid;
mso-list-template-ids:180881914 67698711 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l5:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-bidi-font-family:"Times New Roman";}
@list l6
{mso-list-id:2121289688;
mso-list-template-ids:-1061628230;}
@list l6:level1
{mso-level-number-format:roman-lower;
mso-level-tab-stop:.5in;
mso-level-number-position:right;
text-indent:-.25in;
mso-bidi-font-family:"Times New Roman";}
@list l6:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-bidi-font-family:"Times New Roman";}
@list l6:level3
{mso-level-start-at:3;
mso-level-number-format:alpha-upper;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-bidi-font-family:"Times New Roman";}
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]-->
<p class="MsoNormal"
style="margin-bottom:0in;margin-bottom:.0001pt;
text-align:center;line-height:normal" align="center"><br>
<o:smarttagtype
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
</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 Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;
mso-font-charset:2;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:0 268435456 0 0 -2147483648 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";}
@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:401830995;
mso-list-type:hybrid;
mso-list-template-ids:-2068777340 -2101079488 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
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]--> </o:smarttagtype><o:smarttagtype
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"> </o:smarttagtype></p>
<p class="MsoNormal" align="left">Dear All,</p>
<p class="MsoNormal" align="left">Attached please find an
important set of comments. They are to the Whois Accuracy
Pilot Study Report – by a group of researchers at the <st1:place><st1:placetype>University</st1:placetype>
of <st1:placename>Chicago</st1:placename></st1:place>
called NORC. Buried in this report turns out to be a many
issues important to us in the Whois domain name registration
databases – including the question of postal addresses (should
we be validating and publishing the physical addresses of
political dissident groups, religious minorities, girls’
schools in areas where many do not like girls education?<span
style="mso-spacerun:yes"> </span>Is there a danger to be
evaluated *before* we undertake this new policy?)<span
style="mso-spacerun:yes"> </span></p>
<p class="MsoNormal" align="left"><o:p> </o:p></p>
<p class="MsoNormal" align="left">Identity Validation is a very
open question as well, yet NORC seems ready to start work in
this area. I have written a set of questions that say STOP –
and let’s consider the policy implications of these acts
before we develop plans to put them into effect. The comments
are below (with a full copy attached). <br>
</p>
<p class="MsoNormal" align="left"><o:p> </o:p></p>
<p class="MsoNormal" align="left"><b
style="mso-bidi-font-weight:normal">They are due tonight!<span
style="mso-spacerun:yes"> </span>If you can sign on,
please do. Please let me know your name and/or organization
and/or country.<o:p></o:p></b></p>
<p class="MsoNormal" align="left"><b
style="mso-bidi-font-weight:normal"><o:p> </o:p></b></p>
<p class="MsoNormal" align="left">Great tx to Stephanie Perrin
for editing! Here are some thoughts of members on our Policy
Committee: <span style="mso-spacerun:yes"> </span></p>
<p class="MsoNormal"
style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
lfo1; tab-stops:list .5in" align="left"><!--[if !supportLists]--><span
style="mso-list:Ignore">-<span style="font:7.0pt "Times
New Roman""> </span></span><!--[endif]-->Kathy’s
drafted, what I believe to be, an excellent comment in
response. – Amr Elsadr<o:p></o:p></p>
<p class="MsoNormal"
style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
lfo1; tab-stops:list .5in" align="left"><!--[if !supportLists]--><span
style="mso-list:Ignore">-<span style="font:7.0pt "Times
New Roman""> </span></span><!--[endif]-->Great
job Kathy!! I support this document. -- Stephanie Perrin</p>
<p class="MsoNormal"
style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
lfo1; tab-stops:list .5in" align="left"><!--[if !supportLists]--><span
style="mso-list:Ignore">-<span style="font:7.0pt "Times
New Roman""> </span></span><!--[endif]-->Feel
free to add my name as endorsing the document – Ed Morris</p>
<p class="MsoNormal" align="left"><o:p> </o:p></p>
<p class="MsoNormal"
style="border:none;mso-border-bottom-alt:solid windowtext
.75pt; padding:0in;mso-padding-alt:0in 0in 1.0pt 0in"
align="left">Best and tx!!<br>
Kathy (Kleiman)<br>
</p>
<div style="border:none;border-bottom:solid windowtext
1.0pt;mso-border-bottom-alt: solid windowtext
.75pt;padding:0in 0in 1.0pt 0in"> </div>
</o:smarttagtype>
<p class="MsoNormal"
style="margin-bottom:0in;margin-bottom:.0001pt;
text-align:center;line-height:normal" align="center"><b
style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
WHOIS Accuracy Pilot Study Report<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-align:center" align="center"><span
style="font-size:12.0pt;line-height:107%;font-family:"Times
New Roman"">Burying Extremely Divisive Policy Questions
in a Technical Implementation Report Written by an ICANN
Contractor is Improper and, in this Case, Dangerous<br>
</span></p>
<p class="MsoNormal" style="text-align:center" align="center"><br>
<span
style="font-size:12.0pt;line-height:107%;font-family:"Times
New Roman""><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">These are comments written in response to the
WHOIS Accuracy Pilot Study Report. <span
style="mso-spacerun:yes"> </span>Buried in this Report –
which purports to be an implementation report of an ICANN
Contractor (NORC/University of Chicago) -- are some of the
most controversial and unsettled issues in ICANN policy
discussions and history. These issues are the subject of deep
and bitter divides over many years of ICANN work, the subject
of interest across the world, and the focus of a series of
explosive comments in </span><st1:country-region><st1:place><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Singapore</span></st1:place></st1:country-region><span
style="font-size:12.0pt;font-family:"Times New
Roman""> when the ICANN Community began to realize what
was happening. <br>
</span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><br>
<span style="font-size:12.0pt;font-family:"Times New
Roman""><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">It is inappropriate in the extreme, for ICANN
policy issues to be buried in a ICANN Contractor’s
implementation report, and even further, deep in its Appendix
B,</span><i style="mso-bidi-font-style:normal"><span
style="font-family:"Times New Roman""> Next Steps
for the Development of the WHOIS Accuracy Report System
(ARS). </span></i><span
style="font-size:12.0pt;font-family:"Times New
Roman""><span style="mso-spacerun:yes"> </span>This
follows pages of study “methods and approach” language and
sample design which are obscure even to those who follow Whois
policy issues on a regular basis.<span
style="mso-spacerun:yes"> </span>We submit that after the
many years of heated controversy over this topic, it is
disingenuous at the very least to allow this to happen policy
debate to continue its development in this manner.<o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">We are deeply concerned that ICANN Staff has not
flagged this Report, or this Comment Proceeding, for what it
appears to be – a process to seek permission from the ICANN
Community for the:<o:p></o:p></span></p>
<p class="ListParagraphCxSpFirst"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-add-space:auto;text-indent:-.25in;line-height:normal;mso-list:l5
level1 lfo3"><!--[if !supportLists]--><span
style="font-size:12.0pt;font-family:"Times New
Roman""><span style="mso-list: Ignore">a)<span
style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><b
style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">wholesale checking of the physical addresses of
online speakers across the world (whether using domain names
for political speech, personal speech, or religious, ethnic
or sexual minority expression)</span></b><span
style="font-size:12.0pt;font-family: "Times New
Roman""> thus creating an unprecedented inextricable link
between a speaker and her physical location, and <o:p></o:p></span></p>
<p class="ListParagraphCxSpMiddle"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:.25in;mso-add-space:auto;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><o:p> </o:p></span></p>
<p class="ListParagraphCxSpMiddle"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-add-space:auto;text-indent:-.25in;line-height:normal;mso-list:l5
level1 lfo3"><!--[if !supportLists]--><span
style="font-size:12.0pt;font-family:"Times New
Roman""><span style="mso-list: Ignore">b)<span
style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><b
style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">the</span></b><span
style="font-size:12.0pt;font-family:"Times New
Roman""> <b style="mso-bidi-font-weight: normal">radical
new concept of Identity Validation for each and every domain
name Registrant to the ICANN Community, </b>a concept with
inconceivable implications for political, ethnic and religious
minorities worldwide, as well as entrepreneurs, emerging
organizations and those operating today without identities who
seek to create them.<o:p></o:p></span></p>
<p class="ListParagraphCxSpMiddle"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:0in;mso-add-space:auto;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><o:p> </o:p></span></p>
<p class="ListParagraphCxSpMiddle"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:0in;mso-add-space:auto;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">We respectfully add the issues below to this
debate.<o:p></o:p></span></p>
<p class="ListParagraphCxSpMiddle"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:0in;mso-add-space:auto;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><o:p> </o:p></span></p>
<p class="ListParagraphCxSpLast"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:.75in;mso-add-space:auto;text-indent:-.5in;line-height:normal;
mso-list:l0
level1 lfo4"><!--[if !supportLists]--><b
style="mso-bidi-font-weight: normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><span style="mso-list:Ignore">I.<span
style="font:7.0pt "Times New Roman""> </span></span></span></b><!--[endif]--><b
style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">ICANN has never been given a mandate for
Address Checking on a Massive Scale<o:p></o:p></span></b></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Although the Contractor’s Report seems to suggest
that the ICANN Community has approved the massive checking of
postal addresses in the existing gTLD Whois databases, that is
not the case. <o:p></o:p></span></p>
<p class="ListParagraph"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:.75in;mso-add-space:auto;text-indent:-.25in;line-height:normal;
mso-list:l3
level1 lfo5"><!--[if !supportLists]--><span
style="font-size:12.0pt; font-family:"Times New
Roman""><span style="mso-list:Ignore"><br>
A.<span style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span
style="font-size:12.0pt;font-family:"Times New
Roman"">The Whois Review Team Final Report set the
standard of “contactability” -- reaching the domain name
registrant with questions and concerns – not absolute accuracy
of all data in the whois<span style="mso-spacerun:yes"> </span><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">The Current NORC Study (2014) and its
accompanying ICANN Staff Summary accompanying this NORC’s
Pilot Report misrepresent the WHOIS Policy Review Team Final
Report and its Recommendations. <span
style="mso-spacerun:yes"> </span>The goal of the Whois
Review Team was “Contactibility” and “Reachability” of the
Registrant. To this end WHOIS Policy Review Team Final Report
looked “holistically” at the Whois record and did not seek the
accuracy of each and every element of a Registrant’s Whois
record.<span style="mso-spacerun:yes"> </span><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
Specifically, the NORC Report of 2009/2010 (an earlier report
called the NORC Data Accuracy Study) created five categories
for ranking the data quality of a Whois record: <b
style="mso-bidi-font-weight:normal">Full Failure</b>
(overwhelmingly inaccurate); <b
style="mso-bidi-font-weight:normal">Substantial Failure</b>
(most data inaccurate); <b
style="mso-bidi-font-weight:normal">Limited Failure</b>
(data to some degree present and considered useful); <b
style="mso-bidi-font-weight: normal">Minimal Failure</b>
(may benefit from additional information, but data provided is
accurate) and <b style="mso-bidi-font-weight:normal">No
Failure </b>(data complete and accurate). <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><b style="mso-bidi-font-weight:normal"><i
style="mso-bidi-font-style: normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
The Whois Review Team called for ICANN to significantly
reduce the number of “Full Failure” and “Substantial
Failure” Whois Records --- Avoidance of “No Failure” was
not a goal at all.<span style="mso-spacerun:yes"> </span></span></i></b><span
style="font-size:12.0pt;font-family:"Times New
Roman"">As shared many times in meetings of the Whois
Review Team and members of the ICANN Community, including the
GAC, what the WHOIS Review Team recommended was that Whois
information be sufficiently available and accurate for the
Registrant to be reached –for legitimate technical,
administrative and other questions: [Recommendation] “<b
style="mso-bidi-font-weight:normal">6. <span
style="letter-spacing:-.05pt">ICANN should</span><span
style="letter-spacing:-.3pt"> </span><span
style="letter-spacing: -.15pt">take</span><span
style="letter-spacing:-.1pt"> appropriate</span><span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.05pt">measures</span><span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.05pt">to</span><span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.1pt">reduce </span><span
style="letter-spacing:-.05pt">the</span><span
style="letter-spacing:-.2pt"> </span>number<span
style="letter-spacing:-.25pt"> </span>of<span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing:-.05pt">WHOIS</span> <span
style="letter-spacing:-.1pt">registrations</span><span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing:-.05pt">that</span><span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing:-.05pt">fall</span><span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.1pt">into</span><span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing:-.05pt">the</span><span
style="letter-spacing:-.1pt"> </span><span
style="letter-spacing:-.05pt">accuracy</span><span
style="letter-spacing:-.1pt"> groups</span><span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.1pt">Substantial Failure</span><span
style="letter-spacing: -.15pt"> </span><span
style="letter-spacing:-.05pt">and</span> <span
style="letter-spacing:-.05pt">Full </span><span
style="letter-spacing:-.1pt">Failure</span><span
style="letter-spacing:3.55pt;mso-font-width:99%"> </span><span
style="letter-spacing:-.05pt">(as</span><span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing:-.05pt">defined</span><span
style="letter-spacing:-.3pt"> </span>by<span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing: -.05pt">the</span><span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.05pt">NORC</span><span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing:-.05pt">Data</span><span
style="letter-spacing:-.25pt"> </span><span
style="letter-spacing:-.05pt">Accuracy</span><span
style="letter-spacing:-.15pt"> Study,</span><span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing: -.05pt">2009/10)</span><span
style="letter-spacing:-.3pt"> </span>by<span
style="letter-spacing:-.3pt"> </span>50%<span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.05pt">within</span><span
style="letter-spacing:-.2pt"> </span>12<span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.05pt">months</span> and<span
style="letter-spacing:-.2pt"> </span>by<span
style="letter-spacing: -.25pt"> </span>50%<span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing:-.05pt">again</span><span
style="letter-spacing:-.3pt"> </span><span
style="letter-spacing:-.05pt">over</span><span
style="letter-spacing:-.2pt"> </span><span
style="letter-spacing:-.05pt">the</span><span
style="letter-spacing:-.1pt"> </span><span
style="letter-spacing:-.05pt">following</span><span
style="letter-spacing:-.2pt"> </span>12<span
style="letter-spacing:-.15pt"> </span><span
style="letter-spacing: -.05pt">months.</span></b><span
style="letter-spacing:-.05pt">”</span><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
Thus, for the Whois Review Team, “No Failure” (full accuracy
of all fields) was <b style="mso-bidi-font-weight:normal"><i
style="mso-bidi-font-style:normal">not the goal</i></b>;<span
style="mso-spacerun:yes"> </span>“contactability” and
“reachability” of Registrants was. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
text-indent:.5in;line-height:normal"><span
style="font-size:12.0pt;font-family: "Times New
Roman""><br>
B. 2013 Registrar Accreditation Agreement<span
style="mso-spacerun:yes"> </span><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
The WHOIS Review Team Final Report noted that efforts were
already underway to improve accuracy and contactibility of
Registrants in the then-pending “direct negotiations with
Registrars on revisions to the RAA.” These negotiations
resulted in the 2013 RAA which furthered the goal of reaching
Registrants through verified phone numbers and email
addresses:<span style="mso-spacerun:yes"> </span><o:p></o:p></span></p>
<p><span style="mso-tab-count:1"> </span>1.f :
“Verify:<o:p></o:p></p>
<p
style="margin-left:85.5pt;text-indent:-85.5pt;mso-text-indent-alt:-9.0pt;
mso-list:l6
level1 lfo1"><a moz-do-not-send="true"
name="whois-accuracy.1.f.1"></a><!--[if !supportLists]--><span
style="mso-fareast-font-family:"Times New Roman""><span
style="mso-list:Ignore"><span style="font:7.0pt "Times
New Roman"">
</span>i.<span style="font:7.0pt "Times New
Roman""> </span></span></span><!--[endif]-->the
email address of the Registered Name Holder (and, if different,
the Account Holder) by sending an email requiring an affirmative
response through a tool-based authentication method such as
providing a unique code that must be returned in a manner
designated by the Registrar, or<o:p></o:p></p>
<p
style="margin-left:85.5pt;text-indent:-85.5pt;mso-text-indent-alt:-9.0pt;
mso-list:l6
level1 lfo1"><a moz-do-not-send="true"
name="whois-accuracy.1.f.ii"></a><!--[if !supportLists]--><span
style="mso-fareast-font-family:"Times New Roman""><span
style="mso-list:Ignore"><span style="font:7.0pt "Times
New Roman"">
</span>ii.<span style="font:7.0pt "Times New
Roman""> </span></span></span><!--[endif]-->the
telephone number of the Registered Name Holder (and, if
different, the Account Holder) by either (A) calling or sending
an SMS to the Registered Name Holder's telephone number
providing a unique code that must be returned in a manner
designated by the Registrar, or (B) calling the Registered Name
Holder's telephone number and requiring the Registered Name
Holder to provide a unique code that was sent to the Registered
Name Holder via web, email or postal mail.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">As with the Final Report of the Whois Review
Team, the goal of the 2013 RAA was “contactability” and
“reachability” of the domain name Registrant for technical or
administrative questions by third parties. <o:p></o:p></span></p>
<p class="ListParagraph"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:1.5in;mso-add-space:auto;text-indent:-.25in;line-height:normal;
mso-list:l6
level3 lfo1"><!--[if !supportLists]--><span
style="font-size:12.0pt; font-family:"Times New
Roman""><span style="mso-list:Ignore">C.<span
style="font:7.0pt "Times New Roman""> </span></span></span><!--[endif]--><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Where Did the “No Failure” Standard Come From for
NORC – the Validation and Verification of Each and Every Whois
Element Without Policy Processes or Assessments of the Risks
and Harms? <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Consistent with the Whois Review Team Final
Report and the 2013 RAA, we can understand the NORC
methodology and approach to checking email addresses and
telephone numbers – but postal address validation?<span
style="mso-spacerun:yes"> </span>Where is the underlying
GNSO Policy driving this direction to NORC from ICANN Staff? <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><b style="mso-bidi-font-weight:normal"><i
style="mso-bidi-font-style: normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Where is the assessment of the risks and
benefits of updating the physical addresses of hundreds of
millions of political, personal, religious, ethnic and
sexual speakers – including dissidents, minorities and
those discriminated against by the laws and customs of
various regions?</span></i></b><span style="font-size:
12.0pt;font-family:"Times New Roman""> <span
style="mso-spacerun:yes"> </span>Where is NORC evaluating
the wholesale and massive verification of postal address in
the existing gTLD WHOIS databases without such an assessment?<span
style="mso-spacerun:yes"> </span>How did ICANN Staff come
to direct it? <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
The NORC Contractor seems to have jumped from the logical –
checking email and phone – to checking physical addresses. <span
style="mso-spacerun:yes"> </span>But this leap from an open
and undecided policy question to a mere implementation issue
should be disturbing to everyone in the ICANN Community. What
we know from history and the most tragic of recent events is
that speech and physical location are a dangerous combination.
<o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
When individuals armed with automatic rifles wish to express
their disagreement with the legal speech of a satirical
magazine, they find the location in </span><st1:city><st1:place><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Paris</span></st1:place></st1:city><span
style="font-size:12.0pt;font-family:"Times New
Roman""> and kill writers, publishers and cartoonists. <span
style="mso-spacerun:yes"> </span>When they want to express
contempt for those practicing another religion, they bring
their guns to kosher grocery stores in </span><st1:city><st1:place><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Paris</span></st1:place></st1:city><span
style="font-size:12.0pt;font-family:"Times New
Roman""> and synagogues in </span><st1:city><st1:place><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Copenhagen</span></st1:place></st1:city><span
style="font-size:12.0pt;font-family:"Times New
Roman"">. Tracking down and beheading Christian
minorities is a horror of daily life in some parts of the
world. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:243.0pt"><span
style="font-size:12.0pt;font-family: "Times New
Roman""><br>
The UN Declaration of Human Rights, adopted in 1948, states:<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;mso-list:l4 level1 lfo2;tab-stops:list
.5in"><span style="font-size:12.0pt;font-family:"Times
New Roman"">Everyone has the right to freedom of
opinion and expression; this right includes freedom to hold
opinions without interference and to seek, receive and
impart information and ideas through any media and
regardless of frontiers.<o:p></o:p></span></li>
</ul>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:243.0pt"><span
style="font-size:12.0pt;font-family: "Times New
Roman""><br>
It does not say that everyone must put their address on that
speech. Where, as here, the Internet has become the major path
of communication for that speech, the requirement of a
physical address for every speaker may well violate the
requirement of the right to speak and the protection for that
expression. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:243.0pt"><span
style="font-size:12.0pt;font-family: "Times New
Roman""><br>
Further, the validation of postal addresses represents a major
change of policy – one not mandated or requested by the Whois
Review Team, the 2013 RAA or by any Policy-Development Team we
know of.<span style="mso-spacerun:yes"> </span><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:243.0pt"><span
style="font-size:12.0pt;font-family: "Times New
Roman"">Who has evaluated the impact and dangers of
wholesale adoption of postal address validation of the
long-existing gTLD Whois databases– especially in a world that
has changed dramatically in the last few years – where entire
governments have risen and fallen, where formerly free
countries and regions are enslaved by terrorist organizations
and a new set of dictators? While proxy/privacy registrations
are available, <b style="mso-bidi-font-weight: normal"><i
style="mso-bidi-font-style:normal">they are a costly
luxury for many and completely unknown to others</i></b>.
<o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:243.0pt"><span
style="font-size:12.0pt;font-family: "Times New
Roman""><br>
The mandatory validation of the massive number of postal
addresses in the gTLD Whois database – as appears to be the
policy proposal buried between methodology and sample sizes in
the Contractor’s report -- will result in the dangerous,
harmful, even life-threatening exposure of those using their
domain names for nothing more than communicating their ideas,
concerns, political hopes, and religious meetings via private
streams of domain name communications, such as on listservs
and email addresses, and more public resources including
websites and blogs. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:243.0pt"><span
style="font-size:12.0pt;font-family: "Times New
Roman""><br>
No policy we know has ever directed ICANN Staff to instruct a
Contractor to engage in massive Postal Address Validation –
and no policy development process we know has studied,
weighed, debated or valued the enormous impact to speech and
expression of going back over 25+ years of domain names
registrations to suddenly “correct” the postal address and
thereby expose battered women’s shelters, women’s schools in
Pakistan, pro-democracy groups, family planning groups and
LBGQT locations worldwide. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:243.0pt"><span
style="font-size:12.0pt;font-family: "Times New
Roman""><br>
If this is the policy we in ICANN choose to adopt in the
future (as we certainly have NOT adopted it already), then it
will require enormous amounts of preparation, notice and
warning to gTLD domain name <br>
registrants on a global scale. <span style="mso-spacerun:yes"> </span>Absent
that,
we know (without doubt or hyperbole) that ICANN will have
blood on its hands.<o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:243.0pt"><span
style="font-size:12.0pt;font-family: "Times New
Roman"">Overall, ICANN’s Contractor NORC seems to have
jumped into policy-making, not mere implementation. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:1.25in;text-indent:-.5in;line-height:normal;tab-stops:list
1.25in"><b style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt;font-family: "Times New
Roman""><br>
II. </span></b><b style="mso-bidi-font-weight:normal"><span
style="font-size:7.0pt;font-family:"Times New
Roman""> </span></b><b
style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt; font-family:"Times New
Roman"">Identity Validation – Really? <o:p></o:p></span></b></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:list 1.25in"><span
style="font-size:12.0pt; font-family:"Times New
Roman""><br>
Buried deep in Appendix B, of the Contractor’s Report, behind
“syntactic accuracy” and “operational accuracy” is the
explosive issue of “exploring accuracy from an identity
perspective” (page 45). <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;tab-stops:list 1.25in"><span
style="font-size:12.0pt; font-family:"Times New
Roman"">At no time has ICANN ever held a Policy
Development Processes on Identity Validation. Accordingly,
where does this guidance from ICANN to its Contractor to
explore identity validation implementation come from?<span
style="mso-spacerun:yes"> </span>For those who attended
the public Whois meeting in LA, this issue certainly was not
flagged in the discussion; for those who attended the public
meeting in Singapore, this issue was introduced and
IMMEDIATELY FLAGGED as intensely controversial and divisive. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
Identity validation of those engaged in freedom of expression,
publishing and political discussion is a deeply controversial
prospect – and one with heartfelt objection and opposition
grounded in history and law. <span style="mso-spacerun:yes"> </span>The
</span><st1:country-region><st1:place><span
style="font-size:12.0pt;font-family:"Times New
Roman"">United States</span></st1:place></st1:country-region><span
style="font-size:12.0pt;font-family:"Times New
Roman"">, for example, sought to be free of </span><st1:country-region><st1:place><span
style="font-size:12.0pt; font-family:"Times New
Roman"">England</span></st1:place></st1:country-region><span
style="font-size:12.0pt;font-family:"Times New
Roman""> in part because of the mandatory licensing of
its printing presses – and the arrest of all who published
objections to actions of the English crown. <span
style="mso-spacerun:yes"> </span>Pamphlets issued without
names and addresses are not just a cultural right in the </span><st1:country-region><st1:place><span
style="font-size:12.0pt;font-family:"Times New
Roman"">US</span></st1:place></st1:country-region><span
style="font-size:12.0pt;font-family:"Times New
Roman"">, but a constitutional one.<span
style="mso-spacerun:yes"> </span><i
style="mso-bidi-font-style:normal">McIntyre vs. </i></span><st1:state><st1:place><i
style="mso-bidi-font-style:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Ohio</span></i></st1:place></st1:state><i
style="mso-bidi-font-style:normal"><span
style="font-size:12.0pt;font-family: "Times New
Roman""> Elections Commission, 514 </span></i><st1:country-region><st1:place><i
style="mso-bidi-font-style:normal"><span
style="font-size:12.0pt;font-family: "Times New
Roman"">U.S.</span></i></st1:place></st1:country-region><i
style="mso-bidi-font-style:normal"><span
style="font-size:12.0pt;font-family: "Times New
Roman""> 334 (US Supreme Court, 1995). </span></i><span
style="font-size:12.0pt;font-family:"Times New
Roman""><span style="mso-spacerun:yes"> </span><o:p></o:p></span></p>
<p class="ListParagraph"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:1.0in;mso-add-space:auto;text-indent:-.25in;line-height:normal;
mso-list:l1
level1 lfo6"><!--[if !supportLists]--><span
style="font-size:12.0pt; font-family:"Times New
Roman""><span style="mso-list:Ignore"><br>
A.<span style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span
style="font-size:12.0pt;font-family:"Times New
Roman"">The GAC asked for a weighing of the risks and
benefits <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">We note that the GAC has not issued policy in
this area. <span style="mso-spacerun:yes"> </span>According
to the “Brief Overview” provided by ICANN as introduction to
this Contractor Report and this public comment period, the GAC
“asked for an assessment of the feasibility, costs and
benefits of conducting identity validation as part of the
development of the ARS.” <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
Nowhere in this report do we see any assessment of the costs,
delays, risks and harms that might be incurred by gTLD
Registrants, Registrars and Registries worldwide if identity
validation were adopted. Nowhere do we even see an analysis of
how identity validation takes places, what happens when a
minority seeks to register, or when a speaker must disclose
and show her identification as the cost of signing up for a
domain name highlighting family planning, women rights, or
women’s education in parts of the world not as conducive to
these fundamental rights and basic principles. <span
style="mso-spacerun:yes"> </span>Must she go through her
father for this too? <o:p></o:p></span></p>
<p class="ListParagraph"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:1.0in;mso-add-space:auto;text-indent:-.25in;line-height:normal;
mso-list:l1
level1 lfo6"><!--[if !supportLists]--><span
style="font-size:12.0pt; font-family:"Times New
Roman""><span style="mso-list:Ignore"><br>
B.<span style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span
style="font-size:12.0pt;font-family:"Times New
Roman"">ICANN has promised a policy making process. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">In his response to the GAC on this issue, Dr.
Crocker noted concerns:<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-bottom:0in;margin-bottom:.0001pt;text-indent:
.5in;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">The costs of operating the Accuracy Reporting
System are largely dependent<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">upon the number of WHOIS records to be examined,
as well as the level of<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">validation (syntactic, operational, or identity).
For example, the initial<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">responses to the ICANN RFP reveal that identity
validation services are both<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">costly and difficult to administer on a global
basis. <b style="mso-bidi-font-weight:normal"><i
style="mso-bidi-font-style:normal">There may also be data<o:p></o:p></i></b></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><b
style="mso-bidi-font-weight: normal"><i
style="mso-bidi-font-style:normal"><span
style="font-size:12.0pt; font-family:"Times New
Roman"">protection and privacy issues of concern to
the community when conducting<o:p></o:p></span></i></b></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><b
style="mso-bidi-font-weight: normal"><i
style="mso-bidi-font-style:normal"><span
style="font-size:12.0pt; font-family:"Times New
Roman"">extensive identity validation on WHOIS
records.</span></i></b><span
style="font-size:12.0pt;font-family:"Times New
Roman""> Hence, the costs of<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">completing the development of Phase 3 will be
determined based on<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">engagement with the community to identify the
appropriate level of identity<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">validation for ICANN to conduct, as well as the
costs associated with<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.5in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">performing identity validation on a global scale.
(</span><a moz-do-not-send="true"
href="https://www.icann.org/en/system/files/correspondence/crocker-to-dryden-02sep14-en.pdf"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">https://www.icann.org/en/system/files/correspondence/crocker-to-dryden-02sep14-en.pdf</span></a><span
style="font-size:12.0pt;font-family:"Times New
Roman"">, emphasis added.)<o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
As always, policy development must proceed implementation. We
call on ICANN to take this discussion out of the recesses of a
Contractor report, and into the light of the policy
development process. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
text-indent:.5in;line-height:normal"><st1:stockticker><b
style="mso-bidi-font-weight: normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
III</span></b></st1:stockticker><b
style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt;font-family: "Times New
Roman"">. Wide Outreach Needed<o:p></o:p></span></b></p>
<a moz-do-not-send="true" name="_GoBack"><span
style="font-size:12.0pt;font-family: "Times New
Roman"">One thing the Whois Review Team did note in its
Final Review is the need for clear and concerted outreach on
issues that impact the Whois: “We found great interest in the
WHOIS policy among a number of groups that do not
traditionally participate in ICANN’s more technical
proceedings. <span style="mso-spacerun:yes"> </span>They
include the law enforcement community, Data Protection
Commissioners, and the privacy community more generally.”<span
style="mso-spacerun:yes"> </span>The Whois Review Team’s
recommendation specifically call for active and concerted
outreach to these communities of its issue:<o:p></o:p></span></a><o:smarttagtype
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="stockticker"> <span style="mso-bookmark:_GoBack"></span>
<p class="Default" style="margin-left:.5in"><b><i><span
style="font-size:11.5pt">Recommendation 3 - Outreach </span></i></b><span
style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;line-height:normal"><span
style="font-size:11.5pt">ICANN should ensure that WHOIS
policy issues are accompanied by cross-community outreach,
including outreach to the communities outside of ICANN with
a specific interest in the issues, and an ongoing program
for consumer awareness. <br>
<o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
That has clearly not happened here – when so much of
substance is buried so deeply in the back of a report. When
will ICANN be undertaking clear, robust global Outreach on
these important freedom of expression and privacy issues and
implications? <o:p></o:p></span></p>
<p class="ListParagraph"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:1.0in;mso-add-space:auto;text-indent:-.5in;line-height:normal;
mso-list:l2
level1 lfo7"><!--[if !supportLists]--><b
style="mso-bidi-font-weight: normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><span style="mso-list:Ignore"><br>
IV.<span style="font:7.0pt "Times New Roman"">
</span></span></span></b><!--[endif]--><b
style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Finally, let’s Add Policy Staff and Freedom
of Expression and Data Protection Expertise<o:p></o:p></span></b></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">We ask that an ICANN Staff deeply steeped in
data protection and freedom of expression laws and rights be
brought on to work on the development of these address and
identity issues. We understand that ICANN feels previous
backgrounds of its staffers do not limit their activities,
but the perception and reality of this issue would be
considered much more balanced if the ICANN Staffers of the
project hailed from an array of backgrounds and had
represented multiple sides of this issue in their prior
lives. <o:p></o:p></span></p>
<p class="ListParagraph"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;margin-left:1.0in;mso-add-space:auto;text-indent:-.5in;line-height:normal;
mso-list:l2
level1 lfo7"><!--[if !supportLists]--><b
style="mso-bidi-font-weight: normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><span style="mso-list:Ignore"><br>
V.<span style="font:7.0pt "Times New Roman"">
</span></span></span></b><!--[endif]--><b
style="mso-bidi-font-weight:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">Conclusion<o:p></o:p></span></b></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman"">We can’t bury wholesale physical address
checking and the new concept of identity validation in the
back of a Contractor Report. <span style="mso-spacerun:yes"> </span>These
are NOT policies examined or endorsed by the whole of the
ICANN or even the GNSO communities, nor policies evaluated
yet by the whole of the ICANN Community. The risks and
benefits must be assessed before the implementation is
planned. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
Signed, <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman""><br>
MEMBERS OF THE NONCOMMERCIALS STAKEHOLDERS GROUP<br>
[name, and/or organization, and/or country]<o:p></o:p></span></p>
</o:smarttagtype> </blockquote>
<br>
</body>
</html>