<html 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=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:449979178;
mso-list-type:hybrid;
mso-list-template-ids:-2013599320 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1090468444;
mso-list-type:hybrid;
mso-list-template-ids:-1193131172 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2
{mso-list-id:1197547912;
mso-list-template-ids:806681222;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:1276448970;
mso-list-type:hybrid;
mso-list-template-ids:-1524602466 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l4
{mso-list-id:1654212788;
mso-list-type:hybrid;
mso-list-template-ids:-1011735374 67698703 67698689 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l4:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l4:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.25in;
text-indent:-9.0pt;}
@list l4:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;}
@list l4:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l4:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:2.75in;
text-indent:-9.0pt;}
@list l4:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;}
@list l4:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l4:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:4.25in;
text-indent:-9.0pt;}
@list l5
{mso-list-id:1752703491;
mso-list-type:hybrid;
mso-list-template-ids:-305231688 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l5:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l5:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l5:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l5:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l5:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l5:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l5:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l5:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6
{mso-list-id:1791628754;
mso-list-type:hybrid;
mso-list-template-ids:-1883997680 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l6:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l6:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l6:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear Working Group Members,</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Below are the action items and notes from today’s WG call. The action items, notes and meeting documents have been posted on the meeting’s wiki page here:
<a href="https://community.icann.org/x/VWfwAw">https://community.icann.org/x/VWfwAw</a>. The recordings and transcripts will be posted to the same page as soon as they are available.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Amr</p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Action Items:<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="margin-left:-.25in;mso-list:l4 level1 lfo1">Leadership to develop new poll question(s) based on Q6 discussion to re-poll on concepts raised. All WG members encouraged to participate in the poll by COB Saturday.</li><li class="MsoNormal" style="margin-left:-.25in;mso-list:l4 level1 lfo1">Staff to redistribute slides from Marrakech meeting drawn from SAC054, to kick off on-list discussion of what it means to be "in the RDS."</li><li class="MsoNormal" style="margin-left:-.25in;mso-list:l4 level1 lfo1">Staff to incorporate the following WG agreements in the working document:
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:-.25in;mso-list:l4 level2 lfo1"><b>WG Agreement #26:</b> RDS policy must include a definition for every gTLD registration data element including both a semantic definition and (by reference to appropriate standards)
a syntax definition.</li><li class="MsoNormal" style="margin-left:-.25in;mso-list:l4 level2 lfo1"><b>WG Agreement #27:</b> At least one element identifying the domain name registrant (i.e., registered name holder) must be collected and included in the RDS.</li><li class="MsoNormal" style="margin-left:-.25in;mso-list:l4 level2 lfo1"><b>WG Agreement #28:</b> Data enabling at least one way to contact the registrant must be collected and included in the RDS.</li><li class="MsoNormal" style="margin-left:-.25in;mso-list:l4 level2 lfo1"><b>(Revised) WG Agreement #29:</b> At a minimum, one or more e-mail addresses must be collected for every domain name included in the RDS, for contact roles that require an e-mail address
for contactability</li><li class="MsoNormal" style="margin-left:-.25in;mso-list:l4 level2 lfo1"><b>WG Agreement #31:</b> At least one element enabling contact must be based on an open standard and not a proprietary communication method.</li></ul>
</li></ol>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Notes:<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><i>These high-level notes are designed to help PDP WG members navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are
posted on the wiki above.<o:p></o:p></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1) Roll Call/SOI Updates</p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l6 level1 lfo2">SOI Updates:</li><li class="MsoNormal" style="margin-left:0in;mso-list:l6 level1 lfo2">Alan Greenberg is now a member and interim Chair of the RDS-WHOIS2 Review Team</li><li class="MsoNormal" style="margin-left:0in;mso-list:l6 level1 lfo2">Volker Greimann, Stephanie Perrin, Carlton Samuels, and Susan Kawaguchi are also now members of the RDS-WHOIS2 Review Team
</li></ul>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal">2) Continue deliberation beyond "minimum public data set" </p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> a) Charter Question: "What data should be collected, stored and disclosed?" focusing on identifying set of data required in the RDS first</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> b) See annotated poll results from 25 July call</p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level1 lfo3">Question 2
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Proposed WG Agreement #26 - rough consensus (82%)</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Results: 82.61% Agree, 17.39% Unsure/No Opinion</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">There was no objection on the call to accepting this key concept as a WG agreement</li></ul>
</li></ul>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>WG Agreement #26:</b> RDS policy must include a definition for every gTLD registration data element including both a semantic definition and (by reference to appropriate standards) a syntax definition.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level1 lfo3">Question 3
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Proposed WG Agreement #27 - rough consensus (82%)</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">One WG member participating in the poll disagreed - WG members who disagree are encouraged to provide rationale</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Agree: 82.61%, Disagree: 4.35% (1 member), 13.04% (Unsure/No Opinion)</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">In Question 3, “registrant” could also be referring to a proxy provider - WG has accepted consensus policy that proxy provider may be identified as the registrant on previous WG calls</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">If proxy provider or legal representative of registrant are listed as the registrant, they assume responsibility of the domain name registration, unless they disclose the identity of the
customer actually using the domain name (see 2013 RAA and PPSAI Final Report for further information)</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Distinction should be made between privacy and proxy registration – for a domain registered with a privacy service, the privacy provider is not the registrant, while for a domain registered
with a proxy service, the proxy provider is the registrant</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">From RAA: The Registrant is the entity that has acquired the right to use the Internet resource. A Domain Name Registrant is the person or organization who has registered the domain name,
also referred to as a Registered Name Holder.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">After discussion, there was no objection on the call to accepting this key concept as a WG agreement.</li></ul>
</li></ul>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>WG Agreement #27:</b> At least one element identifying the domain name registrant (i.e., registered name holder) must be collected and included in the RDS.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level1 lfo3">Question 4:
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Agree: 78.26%, Disagree: 4.35% (I WG member), Unsure/No opinion: 17.39%</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Proposed WG Agreement #28 - rough consensus (78%), (c) Disagree: 8.70%</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">It was noted that “at least one way” does not preclude more than one way; further discussion under Question 5</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">After discussion, there was no objection on the call to accepting this key concept as a WG agreement.</li></ul>
</li></ul>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>WG Agreement #28:</b> Data enabling at least one way to contact the registrant must be collected and included in the RDS.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level1 lfo3">Question 5:
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Answer choices (a) 53.17% and (b) 39.13% cumulatively agree, (c) 8.70% disagree</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Proposed WG Agreement #29 - split a/b (52%/39%)</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Rationale for disagreement in poll: Problems with email access may create impediments to following up with correspondence regarding domain name registrations</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Requiring email as a contact does not preclude other forms of contact methods being collected/used - language of poll question includes "at minimum"</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Concern expressed about requirement to have/use an email address to register a domain name - there are other legitimate methods to contact domain name registrants</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Registrants don't necessarily have to be the recipient of email sent to that address - may be entities serving in other roles - but care should be taken in terms of other processes/policies
where email contact is a cross-cutting requirement - key concept worded specifically to reflect this understanding</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Login for the registrar’s web-based services may be tied to the email address</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Some customers use an email address while registering for a service, and may stop/use a different email or contact method without updating their contact information</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">"At minimum" is not "At most" - option a) states that email address to reach the Registrant is mandatory to collect and include in the RDS</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">option b) states that one or more email address(es) to reach contact(s) serving in certain roles is mandatory to collect and include in the RDS</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Registrants who use the domain being registered as part of the contact address create a risk if the domain stops working - contact method stops working - WG might want to consider whether
it wishes to allow this</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Alan Greenberg to propose a reworded key concept to be discussed on-list to address overlap between email address used to register a domain name, and email address used for email contact
thereafter</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">No objections by WG members on the call to accepting option (b) as the rough consensus WG agreement for this key concept</li></ul>
</li></ul>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>(Revised) WG Agreement #29:</b> At a minimum, one or more e-mail addresses must be collected for every domain name included in the RDS, for contact roles that require an e-mail address for contactability</p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level1 lfo3">Question 6:
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">(a) 21.74% and (b) 56.52% indicate agreement</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Distinction between options (a) and (b) include "must" vs "may" - option (a) requires an alternative method of communication</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Current status quo requires at least two other contact methods - useful to have other methods of communication in the event that email fails</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Another Proposed alternative: In addition to email address, data enabling two alternative methods of contact must be collected and included in the RDS.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Several concepts are reflected within these three alternative phrasing, including whether to require alternative/preferred contacts, how many should be required, what alternative contact
methods should be required, etc.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">See further discussion under agenda item 2c) below</li></ul>
</li></ul>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>ACTION ITEM:</b> Leadership to develop new poll question(s) based on Q6 discussion to re-poll on concepts raised</p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level1 lfo3">We need to clarify that the data currently collected, disclosed, and escrowed as provided by the RAA may be surplus to what is permissible under the GDPR</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level1 lfo3">Question 7:
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Agree: 86.96%, 13.04: Unsure/No Opinion</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">Proposed WG Agreement #31 - rough consensus (87%)</li><li class="MsoNormal" style="margin-left:0in;mso-list:l3 level2 lfo3">There was no objection on the call to accepting this key concept as a WG agreement.</li></ul>
</li></ul>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>WG Agreement #31:</b> At least one element enabling contact must be based on an open standard and not a proprietary communication method.</p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Action Item:</b> Staff to incorporate the above WG agreements in the working document:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">c) Deliberate on key concepts for Registrant Email Address and other contact methods</p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">What risks is the WG trying to manage - is it associated with security/stability of the DNS?</li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">WG not considering publication/display of this data at this time - only considering collection and inclusion in the RDS</li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">Alternative methods of communication may be required by the registrar to be able to contact registrants/customers, but not necessarily include them in the RDS</li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">WG cannot address all forms of risks, however email is a contact method that does carry risk, so practical to have alternative methods of contact available in the RDS</li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">Not clear if within ICANN's mandate to require registrars to collect data that is not included in the RDS - should ICANN mandate registrar business practices?</li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">Some data is collected by registrars to assist them in meeting their contractual obligations, without including them in the RDS, as well as information outside of the purview of ICANN and
domain name registration (such as data collected for the purpose of provision of web hosting services)</li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">Recall a year or so ago when we discussed SAC054, Report on Domain Name Registration Data Model (June 2012) and noted some data is collected that is beyond the scope of RDS data:
<a href="https://www.icann.org/en/system/files/files/sac-054-en.pdf">https://www.icann.org/en/system/files/files/sac-054-en.pdf</a></li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">Some data collected for RDS purposes, others collected to meet contractual obligations in the RAA (but not to be included in the RDS), while others are collected by registrars for unrelated
reasons altogether</li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">In developing countries and rural areas in developed countries, communication methods are not reliable or constant - there are legitimate purposes to contact registrants in these areas at
times, so alternative methods of communication are necessary, and should be made available via the RDS</li><li class="MsoNormal" style="margin-left:0in;mso-list:l5 level1 lfo4">Discussion of this point to be continued on-list in the coming week</li></ul>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Action Item:</b> Staff to redistribute slides from Marrakech meeting drawn from SAC054, to kick off on-list discussion of what it means to be "in the RDS."</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">d) Overview of EWG Report Contacts Concepts: PBC-Overview-1August.pdf</p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5"><a href="https://community.icann.org/download/attachments/66086741/PBC-Overview-1August.pdf">https://community.icann.org/download/attachments/66086741/PBC-Overview-1August.pdf</a>
</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Rod Rasmussen prepared and presented this overview, at the request of leadership</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slides drawn from EWG presentations made on Purpose Based Contacts, to introduce concepts as input to this WG</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slide 2: Concept is to define a set of roles and concepts around how roles are collected and displayed. Apply concepts consistently for all roles that are eventually agreed.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slide 3: Each role is tied to a contact - block of data enabling contact with someone serving in that role. Each contact has an ID (ROID), allowing the contact to be linked to domain names
that are using that contact in some role. This allows reuse of contacts in many domain names, across all DNs someone may register.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slide 4: Some registrars create objects for contacts and allow reuse of that contact, within a registrar or registry (e.g., Network Solutions NIC handles long ago). Today those contacts don't
have to be reusable and cannot be shared across registries. (Note slide illustrates that some (most) contact data is to be gated in the EWG Report, but that is a separate point of deliberation). Importantly, entities that create contacts are allowed to manage
their own contact data, separately from domain name registrations that use them - and also must give permission to be designated as serving in a role for each DN that does so.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slide 5: Two examples of roles - here, P/P Provider and Business Contact - but the idea is that every role can be linked (via ID) to a contact where the data can be found when appropriate
to display </li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slide 6: Three examples of DN registrations: individual using own data for contact data in all roles, individual using a proxy provider as contact in many roles, business using third party
contacts that differ for each role.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slide 7 - How do contacts get created? The idea the EWG proposed is that an entity that wants to be a contact for at least one DN creates a contact using a "validator." Registrars could be
validators if they choose, but so could others - this unlinks registrars from the function of collecting contact data. (Note that slide touches on validation, but accuracy is to be deliberated separately) Then when you register a domain name, you use contacts
for certain roles by referring to ID. Registrars could automate some of this behind the scenes if they choose.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slide 8: Illustrates the benefits of allowing entities to create and manage their own contacts and (when needed) update contacts to fix obsolete or inaccurate data - fix once, fixes apply
to all DNs that refer to the contact</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Slide 9: For background reference, to see how all the pieces fit together.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Question: If contact data is associated with ROIDs, does this require identity validation of contact? Does it require a single database of persons associated with ROIDs? [Repository Object
IDentifier in EPP]</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Answer: There is nothing saying you cannot create multiple contacts for yourself, with different ROIDs - but this allows for creation of reusable contacts by those who want to (e.g., businesses
with many DNs) to reduce effort and inaccuracy. Enables more efficient validation.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Question: Worried about the Registrant ID field. That being public would allow anyone to figure out the complete set of domains owned by a registrant. And that may allow cross-referencing
detective work</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Answer: Yes, this can be helpful for anti-abuse. However, registrants/contacts can choose not to reuse contacts if they wish to avoid.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Question: Does this force any registrant to go through a registrar or validator?
</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Answer: This WG still needs to decide what's in or out of the MPDS - slide 9 just shows the EWG's take on that, which relied on public IDs and gated access to contact data. We still need
to discuss these concepts in the PDP WG.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo5">Question: Admin and Business seem similar, did the EWG consider combining? Yes, Admin is contact about the DN itself, versus optionally publishing a contact for customers to use to reach
the business itself.</li></ul>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal"> e) Deliberate on "roles" that were broadly supported: Admin, Tech, Abuse, Privacy/Proxy (deferred, pick up next week)</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">3) Confirm action items and proposed decision points</p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Action Items:<o:p></o:p></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo6"><b>Action Item:</b> Leadership to develop new poll question(s) based on Q6 discussion to re-poll on concepts raised. All WG members encouraged to participate in the poll by COB Saturday.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo6"><b>Action Item:</b> Staff to redistribute slides from Marrakech meeting drawn from SAC054, to kick off on-list discussion of what it means to be "in the RDS."</li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo6"><b>Action Item:</b> Staff to incorporate the following WG agreements in the working document:</li></ul>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Working Group Agreements:<o:p></o:p></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo6"><b>WG Agreement #26:</b> RDS policy must include a definition for every gTLD registration data element including both a semantic definition and (by reference to appropriate standards) a syntax
definition.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo6"><b>WG Agreement #27:</b> At least one element identifying the domain name registrant (i.e., registered name holder) must be collected and included in the RDS.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo6"><b>WG Agreement #28:</b> Data enabling at least one way to contact the registrant must be collected and included in the RDS.</li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo6"><b>(Revised) WG Agreement #29:</b> At a minimum, one or more e-mail addresses must be collected for every domain name included in the RDS, for contact roles that require an e-mail address
for contactability</li><li class="MsoNormal" style="margin-left:0in;mso-list:l1 level1 lfo6"><b>WG Agreement #31:</b> At least one element enabling contact must be based on an open standard and not a proprietary communication method.</li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">4) Confirm next meeting date: 8 August 16.00 UTC</p>
<p class="MsoNormal"><b>Meeting Materials:<o:p></o:p></b></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in;mso-list:l2 level1 lfo7"><a href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-25July2017.pdf?version=1&modificationDate=1501027940000&api=v2">KeyConceptsDeliberation-WorkingDraft-25July2017.pdf</a><b> </b>and <a href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-25July2017.docx?version=1&modificationDate=1501027924000&api=v2">doc</a></li><li class="MsoNormal" style="margin-left:0in;mso-list:l2 level1 lfo7"><a href="https://community.icann.org/download/attachments/66086741/PBC-Overview-1August.pdf?version=1&modificationDate=1501602782000&api=v2"><i>PBC-Overview-1August.pdf</i></a></li><li class="MsoNormal" style="margin-left:0in;mso-list:l2 level1 lfo7"><b><i>25 July Call Poll </i></b></li><li class="MsoNormal" style="margin-left:0in;mso-list:l2 level1 lfo7"><b>Link to participate:</b> Closed@ COB Saturday 29 July</li><li class="MsoNormal" style="margin-left:0in;mso-list:l2 level1 lfo7"><b>PDF of Poll Questions: </b><a href="https://community.icann.org/download/attachments/66086734/Poll-from-25JulyCall.pdf?version=1&modificationDate=1501027105639&api=v2">Poll-from-25JulyCall.pdf</a></li><li class="MsoNormal" style="margin-left:0in;mso-list:l2 level1 lfo7"><b>SurveyMonkey Summary Poll Results: </b><a href="https://community.icann.org/download/attachments/66086741/SummaryResults-Poll-from-25JulyCall.pdf?version=1&modificationDate=1501445918000&api=v2">SummaryResults-Poll-from-25JulyCall.pdf</a></li><li class="MsoNormal" style="margin-left:0in;mso-list:l2 level1 lfo7"><b>SurveyMonkey Raw Data Poll Results: </b><a href="https://community.icann.org/download/attachments/66086741/RawDataResults-Poll-from-25JulyCall.zip?version=1&modificationDate=1501445931000&api=v2">RawDataResults-Poll-from-25JulyCall.zip</a> and <a href="https://community.icann.org/download/attachments/66086741/RawDataResults-Poll-from-25JulyCall.xlsx?version=1&modificationDate=1501445942000&api=v2">XLS</a></li><li class="MsoNormal" style="margin-left:0in;mso-list:l2 level1 lfo7"><b>Annotated Survey Results</b>: <a href="https://community.icann.org/download/attachments/66086741/AnnotatedResults-Poll-from-25JulyCall.pdf?version=2&modificationDate=1501610982521&api=v2">AnnotatedResults-Poll-from-25JulyCall.pdf</a></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>