<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=utf-8">
<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:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText"><a name="_MailEndCompose">Folks are discussing the original source of data, and the repositories of data. For a domain record, some (not all) data starts with a registrant. Some data in a domain record is collected from the registrant
by a registrar (the first repository of that data). Some of that data is then placed in the registry (the second repository). And some data in a domain record is created and held originally at the registry.<o:p></o:p></a></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">For legal purposes, and for some technical purposes, the definition of “authoritative” is the fourth (and maybe also third) definition that Paul gave. That meaning of “authoritative” is: what
is to be relied upon as the data of record, what is official, what rules if there’s a discrepancy. This setup answers questions like: who’s the registrant of record? What nameservers does this domain resolve to? When does the domain expire?<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">In practical terms, “what data is to be relied upon, what is official, what rules” resides in the registry. Certainly for thin data, and I think also for thick data in a thick regime, which
is what ICANN has been moving to. <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">Registries exist to be authoritative repositories of data; that’s is their function and what they are designed to do. (So, for example, two different people can’t register the same domain name,
or so a domain won’t resolve to the wrong nameservers.) Domain registries are generally considered authoritative for at least the thin data. (Domain, sponsoring registrar, dates, statuses, nameservers.) The registry creates or is the repository of record
for most of those fields (domain, sponsoring registrar, dates). And the registry is authoritative for status and nameserver data, using them to enable and control resolution, or to prevent certain actions from taking place in the registry (such as deletions,
and registrar-to-registrar transfers). Registries are the ones that publish TLD zone files; that is one of their core functions.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">The Thick WHOIS PDP decided that all gTLD registries should be thick. One reason was to ensure that there won’t be any more disagreements (discrepancies) between what the registrar says the
data is and what the registry says it is (and as seen via WHOIS or a successor system). Another reason was to hold contact data in one place reliably, so it could be served from one (to-be-trusted) place and can be escrowed reliably; as a consequence registrar
port 43 WHOIS service will eventually go away. <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">So the current situation seems to be pretty simple, and is on the path to getting even simpler:
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">1. If the registry is thick, the registry is authoritative (to be relied upon, official) for all data we see in WHOIS today.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">2. If the registry is thin, the registry is authoritative (to be relied upon, official) for the thin data, and the contact data held by the registrar is authoritative (to be relied
up[on, official). The remaining thin registries will go thick in a couple of years, which makes things simpler.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">In other words, all registries should be considered authoritative (to be relied upon, official) for all the data we see in WHOIS, if they are not already. That was the desired policy and operational
outcome. It is also the most practical and elegant solution.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">The above has nothing to do with the accuracy (truthfulness) of contact data. That’s a related but separate issue.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">All best,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">--Greg<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-bookmark:_MailEndCompose">(P.S.: the UDRP Rules say that the contact data in the “Registrar’s WHOIS” must be relied upon for proceedings (i.e. the registrar is authoritative for contact data). That was written in 1999,
back before thick gTLD registries even existed. I believe that language should eventually be changed to meet evolving reality. In )<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Paul Keating<br>
<b>Sent:</b> Monday, May 1, 2017 8:34 AM<br>
<b>To:</b> Hollenbeck, Scott <shollenbeck@verisign.com><br>
<b>Cc:</b> gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] authoritative<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Authoritative is an adjective and thus relative by definition.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">One source can be more or less authoritative than another. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div style="margin-left:9.0pt;margin-top:6.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Main Entry:</b> source<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Part of Speech:</b> noun<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Definition:</b> beginning; point of supply<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Synonyms:</b> antecedent, author, authority, authorship, begetter, birthplace, cause, commencement, connection, dawn, dawning, derivation, determinant, expert, father, fount, fountain, fountainhead, horse's
mouth, inception, informant, maternity, mother, onset, opening, origin, origination, originator, parent, paternity, provenance, provenience, rise, rising, root, specialist, spring, start, starting point, wellspring<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Antonyms:</b> effect, end, result<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><br>
<br>
<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><br>
<br>
<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<div style="margin-left:9.0pt;margin-top:6.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Main Entry:</b> authoritative<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Part of Speech:</b> adjective<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Definition:</b> recognized as true, valid<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Synonyms:</b> accurate, attested, authentic, authenticated, circumstantiated, confirmed, definitive, dependable, documented, factual, faithful, learned, legit, proven, reliable, righteous, scholarly, sound,
straight from horse's mouth, supported, trustworthy, truthful, validated, verified, veritable<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Antonyms:</b> democratic<o:p></o:p></p>
</div>
<div id="hider_synonyms">
<div style="margin-left:9.0pt;margin-top:6.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Main Entry:</b> authoritative<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Part of Speech:</b> adjective<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Definition:</b> domineering<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Synonyms:</b> assertive, authoritarian, autocratic, commanding, confident, decisive, dictatorial, doctrinaire, dogmatic, dominating, imperative, imperious, imposing, masterly, officious, peremptory, self-assured<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Antonyms:</b> democratic<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-top:6.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Main Entry:</b> authoritative<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Part of Speech:</b> adjective<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Definition:</b> official, authorized<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Synonyms:</b> administrative, approved, bureaucratic, canonical, departmental, ex cathedra, ex officio, executive, imperial, lawful, legal, legitimate, magisterial, mandatory, ruling, sanctioned, sovereign,
supreme<o:p></o:p></p>
</div>
<div style="margin-left:9.0pt;margin-right:9.0pt">
<p class="MsoNormal" style="line-height:15.0pt"><b>Antonyms:</b> democratic<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Sincerely,<o:p></o:p></p>
<div>
<p class="MsoNormal">Paul Keating, Esq.<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 1, 2017, at 1:51 PM, Hollenbeck, Scott via gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On an alternative to "authoritative": I prefer to use word that means something along the lines of "closest to the original producer or collector", applying the concept of provenance (information about the creation, chain of custody, modifications
or influences pertaining to an artifact) to data. One possible alternative might be "definitive".<br>
<br>
Scott<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">-----Original Message-----<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a> [mailto:gnso-rds-pdp-wg-<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><a href="mailto:bounces@icann.org">bounces@icann.org</a>] On Behalf Of Gomes, Chuck via gnso-rds-pdp-wg<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Sent: Sunday, April 30, 2017 5:07 PM<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">To: <a href="mailto:dave@davecake.net">dave@davecake.net</a>;
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Subject: [EXTERNAL] Re: [gnso-rds-pdp-wg] authoritative<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">In preparation for the WG meeting this coming Tuesday, I ask all members<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">to read David's message below and any messages on the list in response to<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">it. We will try to reach at least a tentative conclusion on this in that<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">meeting.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Realizing that I temporarily halted discussion of issues on the list on<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Friday, because this is really a definition of terminology and not really<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">an issue of requirements, if anyone has a suggestion for an alternative<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">term instead of 'authoritative', it would be okay to share it on the list.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Thanks to those of you who already responded.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Chuck<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">-----Original Message-----<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a> [mailto:gnso-rds-pdp-wg-<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><a href="mailto:bounces@icann.org">bounces@icann.org</a>] On Behalf Of David Cake<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Sent: Thursday, April 27, 2017 1:12 PM<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">To: RDS PDP WG <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Subject: [EXTERNAL] [gnso-rds-pdp-wg] authoritative<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> I want to just write an (overdue) email recording what I<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">verbalising reported to the meeting earlier this week.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">The small group looking at the term ‘authoritative’ and its definition<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">concluded that the term was best avoided.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Essentially, we identified three ways in which the term was in use, and<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">concluded that the potential for confusion was problematic.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> One sense in which it was used was in a technical sense within the<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">DNS. This sense is defined in RFC 7719 (which Andrew Sullivan was a co-<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">author of), and as the DNS and RDS are closely linked systems this<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">presents the potential for confusion. The definition is, however, of no<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">use to the RDS, as it is highly specific to the DNS.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> The second sense is in a more general data-theoretic use. This is<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">conceptually related to the DNS use, though there are significant<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">complications. This sense is the sense in which it was earlier used in<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">discussion of RDS requirements - the concept that within a data system<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">there is a source of the data that is considered to have precedence over<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">other sources of data. For example, in many data systems (including the<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">DNS) data may be cached, and that cached data is not considered<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">authoritative, even though it is a copy of authoritative data, and if that<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">non-authoritative data is ever found to be different to the authoritative<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">data, the authoritative data is assumed to be correct.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> The third sense is a legal sense, that is data that is guaranteed<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">to be correct by some authority. This sense of authoritative was found to<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">be confusing, and had been found to be problematic in the past, including<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">within ICANN. Michael Palage discussed examples where this had happened,<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">and made a strong case that if the term authoritative was to be used, it<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">would have needed to be appropriately qualified.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> With significant potential for confusion, it seemed as if avoiding<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">the specific term, but finding a term that captured the meaning of the<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">data-theoretic sense.A forms of words suggested included "Data from the<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">source repository,”. I felt that while that form of words looked<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">appropriate for our purposes, having untangled the definitional issues<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">that were the focus of the small group, it was appropriate to move<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">discussion back to the main group for further refining of terminology in<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">context.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> It should be noted that previous discussion involving the term in<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Copenhagen did not intend to preclude the use of non-authoritative data<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">(caching and similar issues were regarded as implementation issues for<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Phase 2, that should not be precluded by requirements in Phase 1).<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> David<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">_______________________________________________<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">gnso-rds-pdp-wg mailing list<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">_______________________________________________<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">gnso-rds-pdp-wg mailing list<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
<p class="MsoNormal">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</body>
</html>