<!-- This file has been automatically generated. See web/README.md -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div id="compose-container" style="direction: ltr" itemscope="" itemtype="https://schema.org/EmailMessage">
<span itemprop="creator" itemscope="" itemtype="https://schema.org/Organization"><span itemprop="name" content="Outlook Mobile for iOS"></span></span>
<div>
<div style="direction: ltr;">Paul </div>
<div><br>
</div>
<div style="direction: ltr;">As a registrar we always have a lot more data about the registrant than is published.</div>
<div style="direction: ltr;">There's an important difference between "collection" and "display".</div>
<div style="direction: ltr;">So, for example, An Garda Siochana could ask us for the IP addresses used by a registrant to access our billing system. We'd have that data and other elements, but they're never published.</div>
<div style="direction: ltr;">Access to data and collection of data always have been different.</div>
<div><br>
</div>
<div style="direction: ltr;">Regards</div>
<div><br>
</div>
<div style="direction: ltr;">Michele </div>
<div><br>
</div>
<div class="acompli_signature">--<br>
Mr Michele Neylon<br>
Blacknight Solutions<br>
Hosting, Colocation & Domains<br>
<a dir="ltr" href="https://www.blacknight.com/" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="0">https://www.blacknight.com/</a><br>
<a dir="ltr" href="https://blacknight.blog/" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="1">https://blacknight.blog/</a><br>
<a dir="ltr" href="https://ceo.hosting/" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="2">https://ceo.hosting/</a><br>
Intl. +353 (0) 59 9183072<br>
Direct Dial: +353 (0)59 9183090<br>
-------------------------------<br>
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty<br>
Road,Graiguecullen,Carlow,R93 X265,<br>
Ireland Company No.: 370845</div>
<div class="gmail_quote">_____________________________<br>
From: Paul Keating <<a dir="ltr" href="mailto:paul@law.es" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="6">paul@law.es</a>><br>
Sent: Thursday, April 27, 2017 3:51 p.m.<br>
Subject: Re: [gnso-rds-pdp-wg] Proposed Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC<br>
To: Gomes, Chuck <<a dir="ltr" href="mailto:cgomes@verisign.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="7">cgomes@verisign.com</a>>, Michele Neylon - Blacknight <<a dir="ltr" href="mailto:michele@blacknight.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="8">michele@blacknight.com</a>>,
Anderson, Marc <<a dir="ltr" href="mailto:mcanderson@verisign.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="9">mcanderson@verisign.com</a>>, <<a dir="ltr" href="mailto:gregshatanipc@gmail.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="10">gregshatanipc@gmail.com</a>><br>
Cc: <<a dir="ltr" href="mailto:gnso-rds-pdp-wg@icann.org" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="11">gnso-rds-pdp-wg@icann.org</a>><br>
<br>
<br>
<meta content="text/html; charset=Windows-1252">
<div>Eliminating access to data is dangerous IMHO. While one could make a case that certain data fields are not relevant, we need only look to recent history to see how mistaken such presumptions can be. Once eliminated, it is difficult to regain the data.
We are dealing with a global system of data which is meant to be authoritative in nature (coming from a trusted source – e.g. I will call a “Publisher"). While some of that data may come to the Publisher from sources that have not yet been completely verified
(e.g. Name and address of registrant), it remains imperative to hold to a single design and trusted source concept. I am thus loath to agree to remove data fields absent an extremely compelling reason to do so.</div>
<div style="direction: ltr;"><br>
</div>
<div>Im sure I did not adequately describe myself and that the data experts are rolling eyes…..</div>
<div style="direction: ltr;"><br>
</div>
<div>Paul</div>
<div style="direction: ltr;"><br>
</div>
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; border-bottom:medium none; border-left:medium none; padding-bottom:0in; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; border-right:medium none; padding-top:3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>> on behalf of "Gomes, Chuck via gnso-rds-pdp-wg" <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><br>
<span style="font-weight:bold">Reply-To: </span>"Gomes, Chuck" <<a href="mailto:cgomes@verisign.com">cgomes@verisign.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, April 27, 2017 at 3:31 PM<br>
<span style="font-weight:bold">To: </span>Michele Blacknight <<a href="mailto:michele@blacknight.com">michele@blacknight.com</a>>, "Anderson, Marc" <<a href="mailto:mcanderson@verisign.com">mcanderson@verisign.com</a>>, "<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>"
<<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>" <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [gnso-rds-pdp-wg] Proposed Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC<br>
</div>
<div style="direction: ltr;"><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="border-left:#b5c4df 5 solid; padding:0 0 0 5; margin:0 0 0 5">
<div>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--@font-face {font-family:"Cambria Math"}@font-face {font-family:Calibri}@font-face {font-family:Tahoma}@font-face {font-family:Consolas}@font-face {font-family:Verdana}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 {color:blue; text-decoration:underline}a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline}pre {margin:0in; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New"}p.msonormal0, li.msonormal0, div.msonormal0 {margin-right:0in; margin-left:0in; font-size:12.0pt; font-family:"Times New Roman",serif}span.HTMLPreformattedChar {font-family:Consolas}span.EmailStyle22 {font-family:"Calibri",sans-serif; color:windowtext}.MsoChpDefault {font-size:10.0pt}@page WordSection1 {margin:1.0in 1.0in 1.0in 1.0in}div.WordSection1 {}--></style>
<div bgcolor="white" lang="EN-US">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">If and when the transition to Thick Whois is finished, would the need for links to some of the think data elements such as Whois URLs go away for other users besides registrars
and registries? </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">It would be good to hear from some of the other users on this.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Chuck</span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></a></p>
<span style=""></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"><a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]<b>On Behalf Of
</b>Michele Neylon - Blacknight<br>
<b>Sent:</b> Thursday, April 27, 2017 5:03 AM<br>
<b>To:</b> Anderson, Marc <<a href="mailto:mcanderson@verisign.com">mcanderson@verisign.com</a>>;<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><br>
<b>Cc:</b> <a 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 Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Marc</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">At the moment registrars need access to public whois in order to handle transfers of thin registries (com + net).</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">We don’t need it for thick registries as we can get the data we need via EPP.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">With the transition of com and net to thick (or its replacement) our need for whois access will be reduced or possibly removed.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Regards</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Michele</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></p>
<div>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">--</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Mr Michele Neylon</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Blacknight Solutions</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Hosting, Colocation & Domains</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"><a href="https://www.blacknight.com/">https://www.blacknight.com/</a></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"><a href="https://blacknight.blog/"><span style="color:#0563C1">https://blacknight.blog/</span></a></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"><a href="https://ceo.hosting/"><span style="color:#0563C1">https://ceo.hosting/</span></a></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Intl. +353 (0) 59 9183072</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Direct Dial: +353 (0)59 9183090</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">-------------------------------</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Road,Graiguecullen,Carlow,R93 X265,</span></p>
</div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Ireland Company No.: 370845</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></p>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style=""><b><span lang="EN-GB" style="font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-GB" style="font-family:"Calibri",sans-serif"><<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>>
on behalf of "Anderson, Marc via gnso-rds-pdp-wg" <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Reply-To: </b>"Anderson, Marc" <<a href="mailto:mcanderson@verisign.com">mcanderson@verisign.com</a>><br>
<b>Date: </b>Thursday 27 April 2017 at 00:51<br>
<b>To: </b>"<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>" <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><br>
<b>Cc: </b>"<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>" <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] Proposed Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC</span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
</div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Greg, my apologies for misquoting you, please consider me corrected.</span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">I don’t think that a future RDS that facilitates access to the BPS of data rather than a one stop aggregator of data (which comes with synchronization
and update challenges) would create a tsunami. After all this is how the DNS works today and it has much higher volumes than RDS. That said you make a fair point about possible unintended consequences and not letting perfect be the enemy of the good.</span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">I would be interested in hearing more about the registrar that needs access to 10k plus whois records a day. Has that use case been accounted for in
the list of potential RDS requirements the working group has collected?</span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Thanks,<br>
Marc</span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><b><span lang="EN-GB" style="font-size:10.0pt; font-family:"Tahoma",sans-serif">From:</span></b><span lang="EN-GB" style="font-size:10.0pt; font-family:"Tahoma",sans-serif"> Greg Shatan [<a href="mailto:gregshatanipc@gmail.com">mailto:gregshatanipc@gmail.com</a>]<br>
<b>Sent:</b> Wednesday, April 26, 2017 3:16 PM<br>
<b>To:</b> Anderson, Marc<br>
<b>Cc:</b> Gomes, Chuck; <a href="mailto:gtheo@xs4all.nl">gtheo@xs4all.nl</a>; <a 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 Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC</span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif">Marc,</span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif"> </span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif">I don't think the importance of convenience or "one-stop" to information related to the registration should be underestimated. I have heard that one registrar I know
of accesses approximately 10,000 WHOIS records a day. Slicing and dicing the data currently in WHOIS could have massive ripple effects (maybe tsunami effects is more appropriate), if one look-up now becomes several look-ups later. The possible split between
thin and thick is bad enough.</span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif"> </span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif">Also, if some of the data is taken from the best possible (avoiding "authoritative") source (BPS), rather than the RDS database being the best possible source, then that
should be explained and understood. Methods for insuring the highest fidelity to the BPS should be put in place, and the gaps should be generally explained and understood (e.g., if the RDS and the BPS only sync once a day or once an hour that should be understood,
so that if you need absolutely current information from the BPS, you may need to go to the BPS as well). </span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif"> </span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif">Whatever we do, there will still be some know-how and tricks of the trade, but we shouldn't let the perfect be the enemy of the good.</span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif"> </span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif">Finally, to be clear, your statement, based on my statement, isn't quite accurate (e.g., my email would be the BPS...). </span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif">You said, "As has been pointed out in another thread, this isn’t just the “Privacy Working Group”; it’s the “Next Gen RDS Working Group”."</span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif">It would be a more accurate paraphrase to say, "</span><span lang="EN-GB" style="font-size:9.5pt; font-family:"Verdana",sans-serif">As has been pointed out in another
thread, this isn’t the “Privacy Working Group”; it’s just the “Next Gen RDS Working Group”."</span><span lang="EN-GB"></span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-family:"Verdana",sans-serif">Greg</span><span lang="EN-GB"></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB"><br clear="all">
</span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p><a name="UNIQUE_ID_SafeHtmlFilter_UNIQUE_ID_SafeH"></a><b><span lang="EN-GB" style="font-size:10.0pt; font-family:"Arial",sans-serif">Greg Shatan<br>
</span></b><span lang="EN-GB" style="font-size:10.0pt; font-family:"Arial",sans-serif">C: 917-816-6428<br>
S: gsshatan<br>
Phone-to-Skype: 646-845-9428<br>
</span><span lang="EN-GB"><a href="mailto:gregshatanipc@gmail.com" target="_blank"><span style="font-size:10.0pt; font-family:"Arial",sans-serif">gregshatanipc@gmail.com</span></a></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB">On Wed, Apr 26, 2017 at 2:15 PM, Anderson, Marc via gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>> wrote:</span></p>
<div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB">Chuck, I didn’t do a very good job explaining my hesitation on yesterday’s call so let me try again here.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">I appreciate that we’ve gotten bogged down recently and that the leadership team is trying to move the PDP forward. From my perspective though, we went from trying to define a purpose(s) of RDS and discussing
what data elements should be collected (making sure they map back to a purpose) and then defining who should have access to those data elements and under what circumstances to just throwing up our hands and saying hey, the elements of today’s “thin” whois
don’t seem to have any personally identifiable information in them, does anyone object to just making it all available for unlimited anonymous access in a future RDS solution.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">When you asked if anyone objects I felt left with a choice: either say nothing which would in effect be agreeing that this working group has reached rough consensus that all of today’s “thin” whois elements should
continue to be available via unlimited anonymous access or object. While I’m not sure exactly what I would have been agreeing to by remaining silent I don’t feel comfortable saying that existing thin whois should continue as is.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">On a previous call we discussed the Registrar field and if that should be required or not. We ran out of time before fully getting into the discussion. Aside from the “Sponsoring Registrar IANA ID” field, I
don’t think it makes sense to require other registrar meta data in a domain query response. For example the Whois Server, Referral URL and (newly required) Registrar abuse phone and Registrar abuse email fields. These are all registrar specific data elements
not domain data elements. If querying a registrar RDS service, you already know the whois server and referral URL so it really doesn’t make sense to have those in the response.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">As ICANN accredits registrars and already maintains public lists of them, to me it makes more sense to have that data centrally managed/maintained and made available by ICANN. At risk of pre-supposing a solution,
RDAP would provide the ability to bring that data together in a single client pulling from separate (more appropriate) data sources.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">I have questions about other fields as well. Name Server information for example is already available via DNS. There is undoubtedly a convenience factor to being able to get that from whois as well. I know
that authoritative is a loaded term but in the event that whois and DNS were different I don’t think anyone would consider whois authoritative using any definition of the term. Shouldn’t we consider if it makes sense to continue to provide the same domain
data elements in two different places?</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">Domain statuses have been discussed a little bit by this working group but to my knowledge not in detail. From what I’ve heard so far I’m not sure that data should be available to anyone other than the registrar
and registrant. I’m not saying there isn’t a valid use case, but unless I missed it, I don’t think we’ve really had a chance to discuss, much less come to consensus.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">Again I realize we are trying to move things forward and if the intent is to table some of these discussions so we can get to the gated access discussion, I get it. It felt to me on the call though that we had
boiled things down to since there is no personally identifiable information in traditional thin whois, let’s just have all of that be available for unlimited anonymous access. As has been pointed out in another thread, this isn’t just the “Privacy Working
Group”; it’s the “Next Gen RDS Working Group”.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">Hopefully that helps explain my hesitation and why I put a red “X” in Adobe.</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">Thanks,</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB">Marc</span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style=""><b><span lang="EN-GB" style="font-size:10.0pt; font-family:"Tahoma",sans-serif">From:</span></b><span lang="EN-GB" style="font-size:10.0pt; font-family:"Tahoma",sans-serif"><a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>
[mailto:<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>]<b>On Behalf Of
</b>Gomes, Chuck via gnso-rds-pdp-wg<br>
<b>Sent:</b> Tuesday, April 25, 2017 6:02 PM<br>
<b>To:</b> <a href="mailto:gtheo@xs4all.nl" target="_blank">gtheo@xs4all.nl</a>; <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">
gnso-rds-pdp-wg@icann.org</a></span><span lang="EN-GB"></span></p>
<div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB"><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Proposed Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC</span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Thanks Theo. Do I understand you are saying that you could support thin Whois data elements as public data in the RDS?</span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Regardless, I would still like to see if we can find a resolution to Marc’s concern as long as we don’t spend an inordinate amount of time on it. I
will try to reach out to Marc to see if I can understand his position better. And the Leadership team will try to schedule a call later this week to work on this further.</span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Chuck</span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><a name="m_-6279980457633982584__MailEndCompose"><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span></a><span style=""></span><span lang="EN-GB"></span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style=""><b><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]<b>On Behalf Of
</b>theo geurts<br>
<b>Sent:</b> Tuesday, April 25, 2017 2:31 PM<br>
<b>To:</b> <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Proposed Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC</span><span lang="EN-GB"></span></p>
</div>
</div>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB">Repeating my agreement with the below as mentioned earlier on the call.<br>
<br>
Regarding my earlier comments about NO WHOIS, still technically feasible, and in my opinion good to think outside of the box and check what the purpose is, and I think we should keep checking the purpose all the time. For the progress of the WG, it is best
to move to gated access and use thin WHOIS for now as available public data. <br>
<br>
For the discussion about gated access perhaps it is an idea look at the IPC/RrSG developed framework for the PPSAI to see if that is sufficient to address copyright and trademark concerns. Could save us work if that is workable.<br>
<br>
Best,<br>
<br>
Theo Geurts</span></p>
<div>
<p class="MsoNormal" style=""><span lang="EN-GB">On 25-4-2017 16:40, Victoria Sheckler wrote:</span></p>
</div>
<blockquote style="margin-top:5.0pt; margin-bottom:5.0pt">
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Apologies for missing last week’s and today’s meeting. With respect to item 4 below, based on the discussion we’ve had to date, I believe all thin whois
data should be publicly available as it is either not personally identifiable information, or, in extreme edge cases (such as a long domain name that includes personal information), then it is clear that that individual has chosen to make such information
public. </span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style=""><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> </span><span lang="EN-GB"></span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style=""><b><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]<b>On Behalf Of
</b>Lisa Phifer<br>
<b>Sent:</b> Monday, April 24, 2017 12:51 PM<br>
<b>To:</b> RDS PDP WG <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">
<gnso-rds-pdp-wg@icann.org></a><br>
<b>Subject:</b> [gnso-rds-pdp-wg] Proposed Agenda for RDS PDP WG Meeting Tuesday 25 April 16.00 UTC</span><span lang="EN-GB"></span></p>
</div>
</div>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB" style="font-family:"Calibri",sans-serif">Dear all,<br>
<br>
The next GNSO Next-Gen RDS PDP Working Group teleconference will take place on <b>
Tuesday, 25 April at 16.00 UTC</b> <br>
<br>
Below please find the proposed agenda for this meeting, along with links to meeting materials, which can all be found on the meeting page: <a href="https://community.icann.org/x/DcPRAw" target="_blank">https://community.icann.org/x/DcPRAw<br>
<br>
</a>Regards,<br>
Lisa<br>
<br>
<u>Proposed Agenda for RDS PDP WG Meeting 25 April 16.00 UTC<br>
</u>1) Roll Call/SOI Updates<br>
2) Plan to complete in-progress tasks<br>
a) ccTLD questions<br>
b) Definition of authoritative<br>
3) Revised Task 12 sequence and timeline<br>
See <a href="https://community.icann.org/download/attachments/56986784/RDSPDP-Task12-Revised-21April2017.pdf?version=1&modificationDate=1492802630734&api=v2" target="_blank">
RDSPDP-Task12-Revised-21April2017.pdf</a><br>
4) Start deliberation on the charter question/subquestion 5.1:<br>
<i>Should gTLD registration "thin data" be entirely public or should access be controlled?<br>
</i> See <a href="https://community.icann.org/download/attachments/64078605/NewSection5-Intro-KeyConcepts-21April2017.pdf?version=1&modificationDate=1492802791000&api=v2" target="_blank">
NewSection5-Intro-KeyConcepts-21April2017.pdf</a><br>
5) Confirm action items and proposed decision points<br>
6) Confirm next meeting date: 2 May 2017 at 16:00 UTC <br>
<br>
<b>Meeting Materials:</b> <a href="https://community.icann.org/x/DcPRAw" target="_blank">
https://community.icann.org/x/DcPRAw</a></span><span lang="EN-GB"></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB"> </span></p>
<pre><span lang="EN-GB">_______________________________________________</span></pre>
<pre><span lang="EN-GB">gnso-rds-pdp-wg mailing list</span></pre>
<pre><span lang="EN-GB"><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span></pre>
<pre><span lang="EN-GB"><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></pre>
</blockquote>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style=""><span lang="EN-GB"><br>
_______________________________________________<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" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></p>
</div>
<p class="MsoNormal" style=""><span lang="EN-GB"> </span></p>
</div>
</div>
</div>
</div>
</div>
_______________________________________________ gnso-rds-pdp-wg mailing list <a href="mailto:gnso-rds-pdp-wg@icann.org">
gnso-rds-pdp-wg@icann.org</a> <a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>
<br>
<br>
</div>
</div>
</div>
</body>
</html>