<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=us-ascii">
<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;}
@font-face
{font-family:-webkit-standard;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
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;}
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.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="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I thought the WG discussion was excellent today so encourage those not present to listen to the recording or read the chat.<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></a></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>Michelle DeSmyter<br>
<b>Sent:</b> Tuesday, May 09, 2017 5:30 PM<br>
<b>To:</b> gnso-rds-pdp-wg@icann.org<br>
<b>Cc:</b> gnso-secs@icann.org<br>
<b>Subject:</b> [EXTERNAL] [gnso-rds-pdp-wg] Recordings, attendance & AC chat from Next-Gen RDS PDP WG call on Tuesday, 09 May 2017 at 16:00 UTC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Dear All,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Please find the attendance of the call attached to this email and the MP3 recording below for the Next-Gen RDS PDP Working
group call held on Tuesday, 09 May 2017 at 16:00 UTC.</span><span style="color:black"><o:p></o:p></span></p>
<p style="line-height:15.6pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">MP3:</span></b><b><span style="font-family:"Calibri",sans-serif;color:black"> </span></b><span style="color:black"><a href="https://audio.icann.org/gnso/gnso-nextgen-rds-pdp-09may17-en.mp3%20"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif">https://audio.icann.org/gnso/gnso-nextgen-rds-pdp-09may17-en.mp3 </span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-pdp-11apr17-en.mp3"><br>
</a><o:p></o:p></span></p>
<p style="line-height:15.6pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">AC recording:</span></b><span style="color:black"> <a href="https://participate.icann.org/p7cfnzbdipw/"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif">https://participate.icann.org/p7cfnzbdipw/</span></a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group-2Dactivities_calendar-23nov&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=GJMkY4Fbi9sry9Z53DaSWJm-mHxMfFxg7MEVDf2JU90&s=FI3QJYH6DWWCDQir6NDMSjPkzdqfTTUmf9Ua-AYpc14&e="><span style="color:purple">http://gnso.icann.org/en/group-activities/calendar</span></a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">** Please let me know if your name has been left off the list **</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Mailing list archives:<a href="http://mm.icann.org/pipermail/gnso-rds-pdp-wg/"><span style="color:purple">http://mm.icann.org/pipermail/gnso-rds-pdp-wg/</span></a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Wiki page: </span></b><span style="color:black"><a href="https://community.icann.org/x/EsPRAw"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif">https://community.icann.org/x/EsPRAw</span></a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Thank you.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Kind regards,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:black">Michelle </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Calibri",sans-serif;color:black">———————————————</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><b><u><span style="font-family:"Calibri",sans-serif;color:black">AC Chat Next-Gen RDS PDP WG Tuesday, 09 May 2017</span></u></b><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black">Michelle DeSmyter:Dear all, Welcome to the GNSO Next-Gen RDS PDP Working Group call on Tuesday 09 May 2017 at 16:00 UTC.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michelle DeSmyter:Meeting agenda page: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_EsPRAw&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=m5BDCwOsnoXbuUY5nyWPqgN7jyUjwZTa3Xh98YGERKE&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_EsPRAw&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=m5BDCwOsnoXbuUY5nyWPqgN7jyUjwZTa3Xh98YGERKE&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Chuck Gomes:Hello all<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:RDS PDP WG Newcomers, if you may be interested in a one-hour tutorial, please complete this survey: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.surveymonkey.com_r_3GG6CRR&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=NxVZzqFhoi2iNXgmAMwAg2eIhRilRPcHqfmikoFODPo&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.surveymonkey.com_r_3GG6CRR&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=NxVZzqFhoi2iNXgmAMwAg2eIhRilRPcHqfmikoFODPo&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Fabricio Vayra:hello, all!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Venkata Atluri:Hello Everyone<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Maxim Alzoba (FAITID):Hello All<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Maxim Alzoba (FAITID):I will have to drop after 60 minutes<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michael Hammer:Greetings<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Chuck Gomes:How's the GDD Summit Maxim?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Maxim Alzoba (FAITID):good so far <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Displayed on-screen: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078610_AnnotatedResultsV2-2DPoll-2Don-2DPurpose-2Dfrom-2D2MayCall.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=uxzZv_WYEACCDWawcFdOyygM8IQyAkLYf3SSYkxzBno&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078610_AnnotatedResultsV2-2DPoll-2Don-2DPurpose-2Dfrom-2D2MayCall.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=uxzZv_WYEACCDWawcFdOyygM8IQyAkLYf3SSYkxzBno&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michelle DeSmyter:Remmy<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Q2 results are on page 3<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:WG Agreement to be recorded in our deliberation working draft: gTLD registration "thin data" should be accessible without requiring inquirers
to identify themselves or state their purpose.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Marika Konings:Please note that the charter outlines the process for determining consensus and level of consensus. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:All points of rough consensus are captured in our working document; the latest draft is <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_56986791_KeyConceptsDeliberation-2DWorkingDraft-2D21April2017.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=d3L9zG4ZV6dKQ9-xxsdLhIP4o_fjo1gh7cFpyqLWUm8&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_56986791_KeyConceptsDeliberation-2DWorkingDraft-2D21April2017.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=d3L9zG4ZV6dKQ9-xxsdLhIP4o_fjo1gh7cFpyqLWUm8&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:The most recent version of our working document is always posted at the top of this wiki page: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_gTLDRDS_Phase-2B1-2BDocuments&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=y3BdD9LZAUMiQNbxybTHxTP2v0NCVw43dbEGec1qvOo&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_gTLDRDS_Phase-2B1-2BDocuments&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=y3BdD9LZAUMiQNbxybTHxTP2v0NCVw43dbEGec1qvOo&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Agreements on data element requirements (thin and otherwise) will also be recorded in that working draft, under the Data Elements charter question<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Q3 results start on page 5<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:We will be displaying this handout for futher deliberation momentarily: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078610_Charter-2520Question-25205-2520-2D-2520Handout-2520-2D-2520For9MayCall.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=QVV8--1EIFOLrguivnaSSqAftjK81HmBa2VpZ8MvcxQ&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078610_Charter-2520Question-25205-2520-2D-2520Handout-2520-2D-2520For9MayCall.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=QVV8--1EIFOLrguivnaSSqAftjK81HmBa2VpZ8MvcxQ&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:Apparently I am incompetent and failed somehow to save my answers, but in any case, I have no idea how (2) is supposed to work<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:What we conclude from Q3 is that there is interest in deliberating these - this poll question did not seek agreement or disagreement to each possible
requirement<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Displayed on-screen: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078610_AnnotatedResultsV2-2DPoll-2Don-2DPurpose-2Dfrom-2D2MayCall.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=uxzZv_WYEACCDWawcFdOyygM8IQyAkLYf3SSYkxzBno&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078610_AnnotatedResultsV2-2DPoll-2Don-2DPurpose-2Dfrom-2D2MayCall.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=uxzZv_WYEACCDWawcFdOyygM8IQyAkLYf3SSYkxzBno&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:I sort of feel like a number of people imagine all access to this data is by a human looking at it<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:@Andrew - by (2) did you mean 3b?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:yes, 3b<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:If you wish to be able to refer offline to your own comments, once we move on to deliberation<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:See my comment - what's even the point?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:Indeed<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Handout now displayed on-screen: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078610_Charter-2520Question-25205-2520-2D-2520Handout-2520-2D-2520For9MayCall.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=QVV8--1EIFOLrguivnaSSqAftjK81HmBa2VpZ8MvcxQ&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078610_Charter-2520Question-25205-2520-2D-2520Handout-2520-2D-2520For9MayCall.pdf&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=QVV8--1EIFOLrguivnaSSqAftjK81HmBa2VpZ8MvcxQ&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Page 2 gives WG Agreement from last week as foundation for further deliberation on possible requirements for controlling access to "thin data"<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Page 3 uses results from poll question 3 to just lay out several different possible requirements for deliberation in this call<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Alan Greenberg:Sorry to be late.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Current RAA WHOIS specification allows rate limiting<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:someone has an open mic<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:3rd item may have a technical aspect but is driven by policy.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michael Hammer:+1 to Rod's comment.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Rod, mute your speakers when talking<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Marika Konings:Jim, it looks like your microphone is still open<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:Someone needs to mute or be muted.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michael Hammer:For example, rate limiting to a very low rate might be used to drive people to a pay offering - that is policy, not technical.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:Not my speakers.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Amr Elsadr:@Rod: We're on slide 3 now.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:We are discussing possible requirements on page 3 of displayed document<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Alan Greenberg:Please, WHISH SLIDE?? We all have scrolling<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:So for the purposes of the current discussion, are we talking about thin data only?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:Thanks - explains the disconnect<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Yes, we are deliberating "What steps should be taken to control thin data access" - thin data only<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Scott, when querying a gTLD domain name to retrieve "Thin Data" elements... might be better?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:Friendly amendment, then: "_Requestor identification_ for access to thin data elements should be…" and so on<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Andrew, for example: 1) Requestor identification for access to "thin data" elements should be a) Disallowed, b) Allowed but not required, or
c) Required<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Scott Hollenbeck (Verisign):@Lisa: maybe, if we assume that peopls explicitly submit queries for access to subsets of the available data<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Vicky Sheckler:apologies but I've been called away unexpectedly<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Vicky Sheckler:will catch up later<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:No, Stephanie, you are not correct.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Scott, if there are multiple requirements that apply to a particular scenario, they must all be taken into account, but for right now we focus
on requirements for any scenario that involves access to "tihin data"<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Lisa, Scott: I think the point is that if you put it in terms of "elements" then the response to an unauthenticated (or whatever) query isn't
allowed to get non-thin data<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Scott Hollenbeck (Verisign):@Andrew: yes<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:I agree that the phrasing is a little infelicitous, in that it suggests that people query for particular data<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:I don't think I understood Rod's point about mutliple interfaces<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:it seems to me that if we have an RDAP system, and unauthenticated access is permitted to some subset of data, then if you send a query without
authentication you get the small subset<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:and if you send a query while authenticated you get the answer you're supposed to<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Scott Hollenbeck (Verisign):@Lisa: then I think we should be discussing the conditions under which you have access to only thin data<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> steve metalitz:Isn't the status quo on #1 and 2 (a) (disallowed); and if so, what would be gained by moving to (b) (requestor ID required or some form of
authentication required in some cases but not others)? <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Andrew, what you describe is what the EWG recommended - with the exception that authentication was not the only criteria applied to determine
what data elements you are authorized to receive in your reply<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:no, the status quo on all of it is completely unauthenticated and unidentified permission.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Lisa: I know<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Scott Hollenbeck (Verisign):@steve: access control decisions can be made if the server knows something about the client asking the question.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:The Velvet Hammer.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michael Hammer:Apologies, dropped audio connection<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Scott, Andrew - How in WHOIS today can a requestor identify or authenticate themselves? <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Scott Hollenbeck (Verisign):@Lisa: no can do<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Lisa some registries at some point ran a VPN with authentication to connect and a whois behind it<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Scott Hollenbeck (Verisign):(except for web-nased interfaces that accept server-assigned user names and passwords)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:but that's pretty weak broth<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Michael - not requiring identification is different than disallowing identification, thus we are probing further with 1)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:My point on different "interfaces" can also be thought of as needing to make different types of queries depending upon the type of request you're
making. I would argue that you should get "thin" data for "free" when you're making a gated data element(s) query. If you you have to make two different queries<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> steve metalitz:@Greg, isn;t another way of saying that that 1 and 2 should be answered (a)? <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:My point on different "interfaces" can also be thought of as needing to make different types of queries depending upon the type of request you're
making. I would argue that you should get "thin" data for "free" when you're making a gated data element(s) query. If you "disallow" requestor identification for thin data, then you have to make two different queries to get the data you need - one with your
ID and one without.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:From a policy perspective, rate limiting and CAPTCHA can be allowed or required as anti-abuse measures - or they can be allowed purely to meet
operational needs. The latter is the situation in today's WHOIS?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:Yes, Steve; in order for us to be consistent with ourselves then 1 and 2 should be answered (a).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Greg, for 1 and 2, how is b) Allowed but not required, inconsistent with last week's agreement?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Maxim Alzoba (FAITID):We should not forget that real infrastructure (CPUs, Memory, storage) add costs , so the issue is to make real "bandwidth" balanced
(there is no such thing as truly limitless perfomance)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:OK, we have a wording issue here that's creating a bit of a problem in 1 & 2 - disallowed for *only* thin access but *allowed* when you're making
a more complex query to catch my concern.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Rod, +1<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Maxim Alzoba (FAITID):need to drop the call, bye all<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:Lisa: are you saying 'give the requestor the option of identifying himdelf/herself?" But in all cases, give the thin data to requestors whether
ort not they have identified themselves?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:have to step away for a moment<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Suggest that we try to derive possible statements from 1/2, separately from 3/4, to describe what policy requirements may apply to thin data access<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:That's the gist of it @Greg<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Greg, yes<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:Agree, thick data should "embrace" thin data.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:in terms of a query response.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Rod, Requestor Authentication should be allowed but not required for access to any data elements (including thin data elements)?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Daniel K. Nanghaka:I think Requester Identification should be allowed because it helps in enhancement the legitimacy of the Requester<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Actually that's probably not it... but is that going in the direction you meant?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:So my questions are 1) doesn't that create inefficienes as Rod says, 2) if you collect requestor info then do thpose people a right to opt out
and remove their info from the database later, 3) are registries going to sell data about who queries WHOIS? ICANN might need policy around that....<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:back<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Daniel K. Nanghaka:@Greg, then they should have the consent to to opt out - but if you are going to query the data again then I do not see the reason to remove
your info from the database <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michael Hammer:If the answer to #1 is a) then question #2 becomes meaningless.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Would it be helpful to divvy deliberation on access methods: web, bulk, protocol queries - and look at access requirements for each?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Daniel K. Nanghaka:And yes, ICANN will need a policy towards user data and authentication of the Requester <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:I think it is obvious that if someone gets a superset of thin data by authentication, then it is ok that they get the thin data along with
it<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:but I do not want a registr[y|ar] to be able to decide unilaterally to require authentication<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Andrew, not if authentication is disallowed by policy<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Lisa: that's the reason that Scott's worried about how this is phrased<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:because you get that effect if only because of how it's phrased<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Rod Rasmussen:@Andrew - yep, it's obvious, so that's why I'm sayin' it - too many times I've seen "obvious" missed in creation of policy. :-)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Rod: oh yes, strongly agree<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Andrew, can you suggest a possible requirement that allows authentication but does not require authentication for access to thin data elements?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michelle DeSmyter:one moment<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:The point is that an unauthenticated requestor MUST have access to thin data elements, within the required operational bounds of the service
(so rate limiting for anti-DoS is acceptable)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:But authenticated users might have access to other data elements<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> steve metalitz:Could this be resolved by changing the beginning of each statement to "To the extent querying gTLD 'thin data' elements only," .....?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:+1 Andrew<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Fabricio Vayra:+1 Andrew<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Scott Hollenbeck (Verisign):@Andrew! YES!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:This is why EWG differentiated between the minimum public data set and gated data elements. Public data is accessible with or without authentication.
Gated data requires authentication.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Possible requirement: "Thin data" elements must be accessible with or without authentication.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:Not a complication, but not part of this protocol. As Scott has already pointed out, you get those permissions out of band using your authentication
and authorization mechanism<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:This would be in addition to last week's agreement: "Thin data" should be accessible without requiring inquirers to identify themselves or state
their purpose.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Possible requirement: "Thin data" elements must be accessible with or without authentication.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:Last week's agreement was for "accessibility". It didn't say that was the _only_ way thin elements were accessible<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> steve metalitz:@Lisa that would change the answer to 2 to (b). Still don't understand rationale for that <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@STeve, it allows a single authenticated query to return both thin and thick data elements<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:"Thin data"elements must be accessible with or without authentication" can be interpreted TWO differnt ways, and one of those ways is not what
we want. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Greg: what's the second way?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:My concern is that it can be read to _allow_ authentication to be required when only thin data elements are being requested.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:I'm the other Greg but that's my thought on the second way.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> steve metalitz:"Thin data elements must be accessible with authenticatoin" implies that that they need not be accessible without authentication. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:Lawyers are never evil, they are only carrying out the desires of clients, who may be evil.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Stephanie Perrin:We use a disjunctive comma to imply the second interpretation, do we not?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Possible alternative: "Thin data" elements must not require authentication, but must allow for optional authentication of the inquirer<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Stephanie: this is what happens when people don't follow Oxford on commas :-D<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> steve metalitz:@Lisa we are getting way ahead of ourselves to torture this lanaguage to accommodate a gated access structure for "non-thin" data which we
have not even begun to discuss. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Stephanie Perrin:I know, so much confusion when you forget the importance of commas.....<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Steve, we are trying to be clear that we are not precluding authentication by policy<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Daniel K. Nanghaka:Accessibility is open and authentication can be be an option with multiple access of the data <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Lisa: how about Thin data elements are to be accessble regardless of the level of authentication of the requestor?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:Agree with Greg S.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> steve metalitz:+1 to Andrew's last formulation. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Andrew, I think that works<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> steve metalitz:my coments are in chat, thanks. . <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Possible alternative (from Andrew): Thin data elements are to be accessble regardless of the level of authentication of the requestor<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michael Hammer:how about Thin data elements are to be accessble regardless of the level of authentication, or lack thereof, of the requestor?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Nathalie Coupet:@Chuck: Quesion: What would consumers need to do to be able to identify the author of a website besides going to court and getting an injunction? <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Nathalie Coupet:Question<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Stephanie Perrin:The simpler the better.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Nathalie Coupet:From thin data<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:The question of how and whether our policies cover third-partying data stores of RDS information (e.g., a service provider).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Aaron:Have we defined "authentication"? The dictionary defines authentication as: "the process or action of proving or showing something to be true,
genuine, or valid."So if you require a requestor's email address, that is not authentication. And under the language being discussed, registries[rars) could request all kinds of info, such as email addresses.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Daniel K. Nanghaka:I think the levels of Authentication are needed <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:I don't have a problem with the concept that Lisa just. stated.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Daniel K. Nanghaka:because if the data is beyond thin data then there is a need for authentication<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:It's just the "doctrine of unintended consequences" at play here in the current formulation.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Greg Shatan:Daniel, we are just discussing thin data at the moment.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Michael Hammer:need? or desire for authentication?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:@Daniel, if the WG should agree that authentication is allowed or required, then it would define level(s) of authentication. But if authentication
is disallowed, there are no levels to define.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:@Greg A: if the server operator asks for an email address but doesn't check that it works, then it's not authentication. If there is an email-send-use-this-URL
loop, then it's weak authentication<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Nick Shorey:re ccTLDs - if sharing with ccNSO just bear in mind that not all ccTLDs are members of ccNSO<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:For whatever it's worth, I think I'm on the record in favour of the Data of Record approach<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Lisa Phifer:Newcomer tutorial survey: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.surveymonkey.com_r_3GG6CRR&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=NxVZzqFhoi2iNXgmAMwAg2eIhRilRPcHqfmikoFODPo&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.surveymonkey.com_r_3GG6CRR&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=1QvZPa0jqhCG5cB2idF0ww4YIt2OReibUHXLKJymI34&s=NxVZzqFhoi2iNXgmAMwAg2eIhRilRPcHqfmikoFODPo&e=</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Venkata Atluri:Thank you all<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> andrew sullivan:bye all<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Nathalie Coupet:Bye<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Daniel K. Nanghaka:bye all<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"> Nick Shorey:Ciao<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>