<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font size="+1"><font face="Lucida Grande">+1</font></font></p>
<p><font size="+1"><font face="Lucida Grande">It is not every day
that I quote the EWG conclusions, as there are quite a few
with which I disagree. In this case though, it does seem to
me we discussed this exhaustively, and reached the conclusion
that the registrars were the authoritative source. From a
data protection perspective, this is consistent. I believe it
would be the common view that the entity closest to the
individual on the data map would be the authority on the data,
not the entity further down the chain of control, and not the
data controller (in this case ICANN). I realize I am mixing
technical perspectives with legal perspectives here but I
believe it is useful to flesh out how the matter is analyzed
from each point of view.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">cheers Stephanie P</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-04-05 07:10, Hollenbeck, Scott
via gnso-rds-pdp-wg wrote:<br>
</div>
<blockquote
cite="mid:831693C2CDA2E849A7D7A712B24E257F73D9F2C5@BRN1WNEXMBX01.vcorp.ad.vrsn.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:916132951;
mso-list-template-ids:238837776;}
@list l1
{mso-list-id:1852065836;
mso-list-type:hybrid;
mso-list-template-ids:167920412 67698703 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Greg Aaron<br>
<b>Sent:</b> Tuesday, April 04, 2017 5:18 PM<br>
<b>To:</b> Michael D. Palage <a class="moz-txt-link-rfc2396E" href="mailto:michael@palage.com"><michael@palage.com></a>; 'RDS
PDP WG' <a class="moz-txt-link-rfc2396E" href="mailto:gnso-rds-pdp-wg@icann.org"><gnso-rds-pdp-wg@icann.org></a><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Proposed
Definition/Background for Authoritative<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Mike. A few notes to contribute as
people consider “authoritative”:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Registries exist to be authoritative
repositories of data; that’s 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 original recorder 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).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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 (authoritative) place; as a
consequence registrar port 43 service will eventually go
away. In other words, all registries should become
authoritative for all the data we see in WHOIS, if they are
not already. That was the desired policy and operational
outcome.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So the current situation seems to be pretty
simple, and is on the path to getting even simpler:
<o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="margin-left:0in;mso-list:l1
level1 lfo3">If the registry is thick, the registry is
authoritative for all data we see in WHOIS today.<o:p></o:p></li>
</ol>
<p class="MsoNormal"><b><i><span style="color:#1F497D"><o:p> </o:p></span></i></b></p>
<p class="MsoNormal"><span style="color:#1F497D">I can’t agree
with the conclusion that thick registries are authoritative
for all the data they possess. Being the last holder in a
chain of custody makes them a *<b>convenient</b>* source of
access to certain data elements, but they are not the
original, authoritative* (able to be trusted as being
accurate or true; reliable) source. An example:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">A registrar
creates an agreement with a registrant. That agreement has
an expiration date. The registrar pushes this expiration
date to the registry for publication in an RDDS. The
registry has no direct contact or relationship with the
registrant or the agreement between the registrant and the
registrar.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In this and
similar indirect data collection situations, the registry is
just the last holder in the chain of custody. The registrar
is the original source of the data, and is thus a more
accurate and reliable source of information.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Scott<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:5.25pt"><span
style="color:#1F497D">* I think it’s very important for us
to agree on a definition of “authoritative”, and that
doesn’t mean that we get to make one up. I’ve included mine
(taken from the Oxford English dictionary) here.<o:p></o:p></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</body>
</html>