<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 25-4-2017 16:40, Victoria Sheckler
wrote:<br>
</div>
<blockquote
cite="mid:SN1PR07MB2318CA5E887C578E5F573E5BD51E0@SN1PR07MB2318.namprd07.prod.outlook.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:"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.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.EmailStyle18
{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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<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 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>Lisa Phifer<br>
<b>Sent:</b> Monday, April 24, 2017 12:51 PM<br>
<b>To:</b> 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> [gnso-rds-pdp-wg] Proposed Agenda for
RDS PDP WG Meeting Tuesday 25 April 16.00 UTC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
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 moz-do-not-send="true"
href="https://community.icann.org/x/DcPRAw">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 moz-do-not-send="true"
href="https://community.icann.org/download/attachments/56986784/RDSPDP-Task12-Revised-21April2017.pdf?version=1&modificationDate=1492802630734&api=v2">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 moz-do-not-send="true"
href="https://community.icann.org/download/attachments/64078605/NewSection5-Intro-KeyConcepts-21April2017.pdf?version=1&modificationDate=1492802791000&api=v2">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 moz-do-not-send="true"
href="https://community.icann.org/x/DcPRAw">https://community.icann.org/x/DcPRAw</a></span><o:p></o:p></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>