<div dir="ltr">Sorry for replying late. I agree with Sam and Cake.</div><br><div class="gmail_quote"><div dir="ltr">Le mer. 17 mai 2017 à 13:51, Sam Lanfranco <<a href="mailto:sam@lanfranco.net">sam@lanfranco.net</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have been traveling and unable to join the adobe connect calls but<br>
want to join in this chorus. My voice was for this approach from the<br>
start and the continued trouble with the term "authoritative" only added<br>
evidence to that position. Let's close this chapter and go with data of<br>
record.<br>
<br>
Sam Lanfranco<br>
<br>
On 5/16/2017 10:59 PM, David Cake wrote:<br>
> I’ve said before that it was the conclusion of the small group that the term ‘authoritative' was problematic because multiple uses of the term (both formal and informal) naturally apply in areas relevant to our Phase 1 deliberations, and so is likely to cause confusion. Further discussions have demonstrated that this remains an issue even when we are aware of those issues.<br>
><br>
> The term is referenced only in one requirement in our deliberations so far. The most recent version of that requirement and had relative agreement (84%) (but not consensus was: "A purpose of RDS is to facilitate dissemination of authoritatively-sourced gTLD registration data, such as domain names and their domain contacts and name servers, in accordance with applicable policy.”<br>
><br>
> That was the most strongly supported wording of our poll on 28h of March.<br>
><br>
> Following the recommendation of the small group that the term authoritative (and by extension, authoritatively), I recommend that we use none of the variations presented in that pol, but take the most strongly supported and remove the wording that directly references ‘authoritatively’.<br>
><br>
> Instead, focussing on the idea that that requirement referred originally to the data theoretic sense of the term authoritative, I recommend that we consider a variation of that requirement that uses the term ‘data of record’, and replace 'authoritatively-sourced gTLD registration data” with 'gTLD registration data of record’’ so the wording becomes "A purpose of RDS is to facilitate dissemination of gTLD registration data of record, such as domain names and their domain contacts and name servers, in accordance with applicable policy.”<br>
><br>
> In turn, we need to define the term ‘data of record’, and Andrew Sullivan has provided this definition "the data set at a given time relevant to a given<br>
> registration object that expresses the data provided in the then-current registration for that object.”<br>
><br>
> My intention is not to reject the idea of a requirement that specifies the source of the data, but that we make that requirement separate to the one about access to the data of record. Gpong forward I encourage Working Group members to find a requirements statement about the source of data that capture the idea of 'authoritatively sourced’ or similar for WG discussion.<br>
><br>
> David<br>
> _______________________________________________<br>
> gnso-rds-pdp-wg mailing list<br>
> <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr">Regards<div><div>@__f_f__</div><div><br></div><div>PhD Candidate, Universität der Bundeswehr München</div><div>Computer Security | Internet of Things</div><div><a href="http://about.me/farell">about.me/farell</a></div></div></div></div>