<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Further to our discussion this morning about the openness (or
otherwise) of WHOIS, here is the quote I was referring to from the
SSAC document 003, from 2003:<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div data-canvas-width="773.8723699333334" style="left: 113.399px;
top: 1182.7px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.00087);">In order for Whois data to be readily
available it must be both accessible and usable by </div>
<div data-canvas-width="754.9844832333339" style="left: 113.399px;
top: 1205.1px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.00379);">automatic tools. To be accessible the
Whois protocol must be updated to support the </div>
<big><big>recent shift in the architecture to separate the functions
of the registry and the registrar. </big></big>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div style="width: 1019px; height: 1319px;" class="textLayer">
<div data-canvas-width="784.9671569000002" style="left: 113.4px;
top: 126.7px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.00094);">This shift has made it impractical
to support searching and frequently makes it difficult to </div>
<div data-canvas-width="743.6461618999998" style="left: 113.4px;
top: 149.1px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.00359);">find Whois services. To be usable
the data returned by Whois services must in be a </div>
<div data-canvas-width="150.19882255" style="left: 113.4px; top:
171.3px; font-size: 20px; font-family: sans-serif; transform:
scaleX(1.00177);">common format. </div>
<div data-canvas-width="753.3715670999994" style="left: 113.4px;
top: 217.5px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.00452);"><b>However, being accessible and
usable must also protect a registrant's privacy. Many </b></div>
<div data-canvas-width="761.5858615166663" style="left: 113.4px;
top: 239.9px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.00088);"><b>countries require that personal
information is protected but in addition registrants may </b></div>
<div data-canvas-width="766.0752778333326" style="left: 113.4px;
top: 262.1px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.00075);"><b>wish to discourage the
unintended, undesirable, and otherwise unwanted uses of their
</b></div>
<div data-canvas-width="725.8621645833334" style="left: 113.4px;
top: 284.5px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.00227);"><b>Whois data. In particular, it is
widely believed that Whois data is a source of email </b></div>
<div data-canvas-width="760.673605733333" style="left: 113.4px;
top: 306.9px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.001);"><b>addresses for the distribution of
spam. Methods must be developed to discourage the </b></div>
<div data-canvas-width="379.05126079999997" style="left: 113.4px;
top: 329.3px; font-size: 20px; font-family: sans-serif;
transform: scaleX(1.0008);"><b>harvesting or mining of Whois
information</b>.<br>
<br>
I interpret this as support for the notion that there have been
reservations from parties other than civil <br>
society, with respect to the concept of all WHOIS data being
freely available, from the early days of ICANN.<br>
Stephanie Perrin<br>
</div>
</div>
<br>
</body>
</html>