<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">The below is an excerpt from SAC058: “SSAC Report on Domain Name Registration Data Validation”
<a href="https://www.icann.org/en/system/files/files/sac-058-en.pdf">https://www.icann.org/en/system/files/files/sac-058-en.pdf</a>
<o:p></o:p></p>
<p class="MsoNormal">The excerpt is about contact data specifically. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As I mentioned on the RDS mailing list last week, WHOIS conveys kinds of registration data other than contact data. These include whether a domain is registered, creation and expiration dates, the name and ID of the sponsoring registrar,
what nameservers are delegated to the domain, and so on. We (and users) should absolutely expect an RDS to provide accurate data in those areas. Those kinds of data are not subject to the vagaries that contact data is. For example, a registry is required
to accurately timestamp a domain creation, and the RDS should provide the same timestamp. If a domain is in the registry, the RDS should not return a “domain does not exist” response (outside any update-time SLAs).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For the kinds of data mentioned in the paragraph above, providing data that is accurate is an RDS’s very reason for being.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">SAC058 is worth the time to read, and I recommend it to all members of the WG. It provides a useful framework for talking about contact accuracy and validation, and it poses questions and makes formal recommendations directly to our WG.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><snip from SAC058><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2.1 Why Accurate Registration Data is Important <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In SAC003: WHOIS Recommendation of the Security and Stability Advisory Committee, the SSAC outlined two principal reasons to maintain accurate registration data: technical and legal. The technical rationale is that if there are problems
with or abuse originating from a resource (e.g., a domain name, route, or Internet Protocol (IP) address), the registration data for the resource is the only source for finding the contact information of the responsible party. For some legal and other law-related
purposes (e.g. serving court papers), the registration data may be the only source for finding the contact information for the responsible party.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In SAC 010: Renewal Considerations for Domain Name Registrants, the SSAC observed that registration data often contain "stale" contact information and that this problem can cause difficulties when registrants seek to renew a domain name
or modify DNS information. Stale information may prevent registrars from notifying a registrant that a domain registration is about to expire or that changes, possibly unauthorized, have been made to his domain registration. Failure to update information may
result in domain hijacking or a dispute over the "ownership" of a domain.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It is important to note in understanding the scale of potential problems from inaccurate information that the difficulties do not arise only in criminal matters. The contexts also can include a simple contact issue, as described above with
regard to domain renewals, civil and administrative law enforcement, private actions, and public needs to contact registrants that might arise, for example, when a consumer wants to reach an online seller.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"></snip><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All best,<o:p></o:p></p>
<p class="MsoNormal">--Greg <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>