<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="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:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:24.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:24.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-GB;}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
{mso-style-priority:99;
mso-style-link:"Footnote Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-GB;}
span.MsoFootnoteReference
{mso-style-priority:99;
font-family:"Calibri",sans-serif;
vertical-align:super;}
span.MsoCommentReference
{mso-style-priority:99;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-GB;
font-weight:bold;}
span.FootnoteTextChar
{mso-style-name:"Footnote Text Char";
mso-style-priority:99;
mso-style-link:"Footnote Text";
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-GB;}
.MsoChpDefault
{mso-style-type:export-only;}
/* Page Definitions */
@page
{mso-endnote-separator:url("cid:header.htm\@01D79E72.59BC1E00") es;
mso-endnote-continuation-separator:url("cid:header.htm\@01D79E72.59BC1E00") ecs;}
@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:770199161;
mso-list-type:hybrid;
mso-list-template-ids:-16843568 2139232284 1719938884 134807553 67698689 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:68.1pt;
text-indent:-50.0pt;
mso-ansi-font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:72.1pt;
text-indent:-.25in;
font-family:"Times New Roman",serif;
mso-ascii-font-family:Calibri;
mso-hansi-font-family:Calibri;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:117.1pt;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:144.1pt;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:180.1pt;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:216.1pt;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:252.1pt;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:288.1pt;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:324.1pt;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Dear EPDP Team,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Please find below the notes and action items from today’s meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Following today’s discussion, the Support Staff Team incorporated the agreements we captured into an updated version of the Final Report for your review (<a href="https://drive.google.com/drive/folders/1TW3Z-s6DzS2QsV_VwJ6iUQTvKVIXQrmG">https://drive.google.com/drive/folders/1TW3Z-s6DzS2QsV_VwJ6iUQTvKVIXQrmG</a></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">).
<span style="color:black"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">EPDP Team members are now requested to review the
<a href="https://drive.google.com/drive/folders/1TW3Z-s6DzS2QsV_VwJ6iUQTvKVIXQrmG">
pdf version of the complete Final Report</a> and indicate what changes/updates are essential, within this
<a href="https://docs.google.com/document/d/1Il7T4x1nOXA5i8ru58zCwB3KlTg9aZ5h/edit">
Google Doc</a>, before the Final Report can be published. Please provide your input as soon as possible, but no later than
<b><u>Wednesday, 1 September 14.00 UTC</u></b>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Please note there is currently a placeholder meeting scheduled for Thursday, 2 September at 14:00 UTC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><br>
Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Marika, Berry, and Caitlin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">--<o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="https://docs.google.com/spreadsheets/d/17qLMYb3HC7qGYPQveXbUq5ZSzvedrQ3t8AdVdrRIdrw/edit#gid=0">Action Items</a><o:p></o:p></span></u></b></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">1. Keith to circulate Chair's statement to the EPDP Team for their review prior to closing out Ask #1 (stating groups' discomfort with Recommendation #1).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">2. EPDP Team to review Keith's statement by 14:00 on Wednesday, 1 September and flag if further discussion is needed on Ask #1.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">3. EPDP Support Staff to incorporate changes agreed to during today's meeting into Section 3 of the Final Report and circulate to the EPDP Team. (see attached)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">4. EPDP Team members are now expected to review the pdf version of the complete Final Report and indicate, within this
<a href="https://docs.google.com/document/d/1Il7T4x1nOXA5i8ru58zCwB3KlTg9aZ5h/edit">
Google Doc</a>, what changes/updates are essential before the Final Report can be published. Please provide your input as soon as possible, but no later than Wednesday 1 September 14.00 UTC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">EPDP Phase 2A - Meeting #40</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Proposed Agenda</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Tuesday 31 August 2021 at 14.00 UTC<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt;text-indent:-38.7pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Roll Call & SOI Updates (5 minutes)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt;text-indent:-38.7pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Welcome & Chair updates (Chair) (5 minutes)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt;text-indent:-38.6pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Consider and resolve remaining four “cannot live with” items for section 3 of Final Report - Responses to Council Questions & Recommendations (75 minutes)
– see <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:56.7pt"><a href="https://docs.google.com/document/d/1knSKHXt0njWqXMmpiDKA76amycenNBUl/edit"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">https://docs.google.com/document/d/1knSKHXt0njWqXMmpiDKA76amycenNBUl/edit</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">As a reminder: timeline to get to Final Report<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">30 August – deadline for minority statements<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">31 August – finalize report and address any outstanding items, if any. Chair to circulate proposed consensus designations and Chair statement.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">2 September – placeholder meeting, submission of Final Report to GNSO Council<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">10 September – final deadline for minority statements (any minority statements submitted after 30 August will be added to the Final Report, with the updated version to be submitted
to the Council in time for the September meeting document deadline)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level2 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Review ask #1: Ask #1: EPDP Team to consider if this section (lines 100-104), as well as footnote 5, 20 and 21, can be removed if the Chair statement on consensus designations makes clear that
there was significant disagreement within the group on a number of these issues and that readers are encouraged to review the minority statements to better understand the different views and perspectives.<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:72.1pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:72.1pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Leadership Assessment:
</span><i><span style="font-size:11.0pt;font-family:"Calibri Light",sans-serif;color:black">There appears to be general support for removing the current statement and related footnotes expressing opinions but only if the Chair statement accurately reflects
the EPDP Team’s conversations and differences of opinions to make clear that readers understand that where the recommendations have ended up, is not necessarily what some would have liked to see. Keith to circulate consensus designations and proposed Chair’s
statement following the call to allow the EPDP Team to confirm that this has been done in an acceptable manner.
</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="1" type="a">
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:9.1pt;margin-bottom:.0001pt;mso-list:l0 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Consider EPDP Team input provided<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It is hard to make a final call on this issue in the absence of seeing and reviewing the Chair’s statement. It’s unlikely that readers will read minority statements, so the four corners of the
report should clearly indicate the disagreements. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Cautious against making the arguments made in the minority statements. It is theoretically possible to write a dry and analytical note regarding the significant dissension among the groups, some
advocating for x and some advocating for y. This is a pivotal statement and the one that everyone reads, so it is important.<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:9.1pt;margin-bottom:.0001pt;mso-list:l0 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confirm next steps<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Keith to circulate statement after this call for group to review.<o:p></o:p></span></li></ul>
</li></ul>
<li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level2 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Review ask #2: Do the updates and the reorganization of recommendation #1 address the cannot live with items flagged? If not, how can these be addressed, factoring in the discussions
to date.</span><span class="MsoCommentReference"><span style="font-size:8.0pt"> </span>
</span><span class="MsoCommentReference"><o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:72.1pt;margin-bottom:.0001pt">
<span class="MsoCommentReference"><span style="font-size:8.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><i><span style="font-size:11.0pt;font-family:"Calibri Light",sans-serif;color:black">Leadership Assessment: There is still a level of discomfort with the recommendation, although based on the discussions to date
the group does seem to agree on the underlying principle (a field(s) must be created (technically), but this field(s) is optional for use by CPs. If this is indeed the common understanding, and factoring in the other suggestions, would the following updates
be helpful:<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt;font-family:"Calibri Light",sans-serif;color:black"><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-left:1.0in;background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">The EPDP Team recommends that a field or fields MUST be created<a style="mso-footnote-id:ftn1" href="#_ftn1" name="_ftnref1" title=""><span class="MsoFootnoteReference"><b><span class="MsoFootnoteReference"><b><span style="font-size:11.0pt;color:black;mso-fareast-language:EN-US">[1]</span></b></span></b></span></a>
to <s>allow for</s> <b>facilitate </b>differentiation between legal and natural person registration data and/or if that registration data contains personal or non-personal data. The EPDP expects that the technical community, for example the RDAP WG, will develop
any necessary standards associated with such fields.<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in;background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">This field or fields MAY<a style="mso-footnote-id:ftn2" href="#_ftn2" name="_ftnref2" title=""><span class="MsoFootnoteReference"><span class="MsoFootnoteReference"><span style="font-size:11.0pt;color:black;mso-fareast-language:EN-US">[2]</span></span></span></a>
be used by those Contracted Parties that differentiate between legal and natural person registration data and/or if that registration data contains personal or non-personal information. For clarity, Contracted Parties MAY make use of the field(s), which means
that if a Contracted Party decides not to make use of the field(s), it may be left blank or may not be present. Additionally,<b> Contracted Parties MAY include
</b>the field(s) <s>is not required to be included</s> in a RDDS response.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="2" type="a">
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:9.1pt;margin-bottom:.0001pt;mso-list:l0 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Consider EPDP Team input provided<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question regarding the word created – can you provide examples of how the field or fields could be used and where the fields would be used?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In terms of allow for vs. facilitate, believe that language should be facilitate optional differentiation b/w legal and natural. With respect to the second footnote, this is causing discomfort
with the RySG. Did not discuss this specific language or how this would be implemented. RySG sees value in having a standardized field for CPs who choose to differentiate. In the small group, the group was not supportive of including this field in the public
RDDS response. In the small group, however, there was an ask that even though some does not support it, could the recommendation at least not prevent it. With that background, in reading the footnote, this goes further than Rys are willing to compromise on.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This language was Support Staff’s attempt to try to find middle ground. The precision that is required b/w the must for data elements to be created and the mays regarding how CPs may use it is
not a coercive attempt to make this a bigger requirement. With respect to Footnote 1, none of the policy staff are experts in IETF land; however, if this were an adopted recommendation, the technical services team or another group within ICANN org would be
tasked with submitting an internet draft to the IETF – how that happens in detail, we do not know. If a CP were to choose to use these fields, it is a pretty safe bet that they would need to do so through their EPP systems and processed the data via RDAP or
an SSAD, all of those technical requirements need to be laid out outside of ICANN before CPs can use these fields. In reference to footnote 2, what is important is the last sentence – CPs may include this in the RDDS response. The Small Team’s original instruction
– at that time, it seemed clear that there was no broad support for the fields to be published in the public RDDS, but there may be support for it to be disclosed through a restrictive system. In the discussions, however, there was the aspect of certain parties
not wanting to restrict if they chose to publish or make available these fields in the RDDS. In Phase 1 implementation, it outlines what the future requirement is going to be for an RDDS query format. It is not complete, but the reason Support Staff tried
to include Footnote 2 is that if a registrar did choose to publish both of the fields in the public query, the intent of CL&D and advisory is that these fields would be appended to or appear at the end of the query format.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">These fields should be co-equal and distinct from each other. There is a policy at the level that we are talking about and then there will be a policy of each of the parties, principally the registrars.
The consensus is permissive with respect to whether the fields are collected, how the field is used, and whether the field is published or not published. Individual registrars will have their own policies which may differ from each other.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The footnote regarding EPP and RDAP comes closer to a previous concern. The previous language about created without reference to where and how they are created was unhelpful. Would like to see
a reference to specifications to the RAA and specifications. In Phase 1, there was detail with respect to how fields can be used. Because we are omitting that, the concept of where they are used needs to be more specific.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From a CPH perspective, do not want this language in the footnote. It is not necessary in order to display these optional fields. Clarify that we did not add an additional field – we allowed for
additional fields – this is to account for the fact that Registries can include additional elements. In terms of implementation, the EPDP team expects the technical community to develop standards for such a field.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">GAC views this as necessary infrastructure to provide information to differentiate between legal and natural. This is no misunderstanding that this is mandatory to publish or use; however, if these
fields are created, if it’s infrastructure and needs to work within the entire system. If there is no specificity, it will be of no utility. The fields need to have the capacity to work in the system, including disclosure and publication. The present configuration
prior to the updated footnote lacked that specificity that this would work within the system of disclosure and publication.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would think that footnote 2 is unnecessary, but after listening to what other team members have said, believe that it is necessary.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would the group agree to change the footnote from will be appended to may be appended?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Once this goes to the IETF, do not want to ensure that human rights groups are represented – these will be forgotten. The policy recommends that this be optional; footnotes should not coerce this.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Should not make reference to any existing contracts here – it a dangerous step to imply that the community has the right to amend the contracts.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The PDP modifies contracted parties’ obligations, but it does not amend the contracts b/c the contract says that CPs are obligated to comply with consensus policies. It is not a process of amending
the contract itself, but it has the effect of modifying a CP’s obligations under the agreement. References to amending the contract should be removed.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The additional field of identifying personal v. non-personal preserves the distinction focused on by some.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The PDP manual allows for agreement on terms and conditions – WHOIS language amendments from PDP has gone directly into the contracts.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Proposed language: ICANN MUST coordinate the technical community, for example the RDAP WG, to develop any necessary standards associated with such fields.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is this proposed language OK for ICANN org?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not need to amend the contract at all. There can be supplements. If there are recommendations in the policy that ultimately lead to a requirement to have the fields or make them optional, that
is sufficient. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Generally the IRT does not amend the contract, but sometimes the language will supersede the contract.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The contract can be modified via an RSEP, but do not want registries to have to file an RSEP to use these fields. If these fields are not to be included, why are other fields included there?
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The redlines are acceptable. The language here accomplishes what others would like to accomplish.
<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:9.1pt;margin-bottom:.0001pt;mso-list:l0 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confirm next steps<o:p></o:p></span></li></ul>
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level2 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Review ask #3: Considering the org input (“because this recommendation is for guidance only (and thus not subject to compliance enforcement), the use of should vs may wouldn’t be expected to have
a significant impact from the org perspective"), can the group live with leaving this as “SHOULD” (lines 261-265). If not, please provide alternative suggestions that take into account the EPDP Team’s discussion.<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:72.1pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:72.1pt;margin-bottom:.0001pt">
<i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Leadership assessment: All groups, apart from the RySG, seems to be able to live with the word “SHOULD”. Is the RySG willing to accept that outcome, or would it like to stick with
its “cannot live with” position which will be factored into the consensus designation process.</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="3" type="a">
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:9.1pt;margin-bottom:.0001pt;mso-list:l0 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Consider EPDP Team input provided<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Will voice concern over should v. may in the minority statement and that will be enough to get non-objection from the RySG<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:9.1pt;margin-bottom:.0001pt;mso-list:l0 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confirm next steps<o:p></o:p></span></li></ul>
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level2 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Review ask #4: please consider the updates proposed by the RrSG (lines 322-329 - “any future work within ICANN by the ….”) & RySG team (“any future work by ICANN by the relevant controllers and
processors in relation…”. Also, please provide further input on what these changes would mean or imply as work on a Code of Conduct was not part of phase 1 or phase 2 recommendations. Also consider additional language suggested by IPC (late submission): “For
the avoidance of doubt, RDS data requestors are relevant controllers and processors and must be included in any such future work.”<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:68.1pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt;color:black">
</span></i><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Leadership assessment: based on the input provided, and additional review of the GDPR requirements in relation to the development of a Code of Conduct, would the following
updates address the different positions:<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> The EPDP Team recommends, in line with GDPR Article 40 requirements for Codes of Conduct,<a style="mso-footnote-id:ftn3" href="#_ftn3" name="_ftnref3" title=""><sup><sup><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">[3]</span></sup></sup></a>
that the above developed guidance concerning legal/natural differentiation should be considered by any
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">possible</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> future work
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">within ICANN</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> by the relevant controllers and processors in relation to the development of a GDPR code of conduct.
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Consistent with GDPR recital 99, “</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">When drawing
up a code of conduct, or when amending or extending such a code, associations and other bodies representing categories of controllers or processors should consult relevant stakeholders, including data
subjects where feasible, and have regard to submissions received and views expressed in response to such consultations”.</span></b><span style="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"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:68.1pt;margin-bottom:.0001pt">
<s><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This future work is expected to be carried out in an open and transparent manner, allowing for observers to follow the discussions and with the opportunity for the community to provide input
before the Code of Conduct is finalized.<o:p></o:p></span></s></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:68.1pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="4" type="a">
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:9.1pt;margin-bottom:.0001pt;mso-list:l0 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Consider EPDP Team input provided<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Concerned with use of Code of Conduct as this is a term in the RAA<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Proposed edit: for the avoidance of doubt, this Code of Conduct is separate and distinct from the code of conduct referenced in the RAA and/or registry agreements.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not all readers will see the footnote – important to incorporate the text into the recommendation.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is it possible to ask ICANN to commence a code of conduct in line with Article 40 of GDPR<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confirm the GAC proposed addition of pseudonymized is a minor edit<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Team intentionally used the term masked instead of pseudonymized – the proposed clarification is useful but should be consistent. The Team used masked intentionally because it is less of a loaded
term legally speaking. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not willing accept the term masked unless defined.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Perhaps “intended to be pseudonymous”<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Pseudonyms are intended to be reversible
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not agree to this change<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:9.1pt;margin-bottom:.0001pt;mso-list:l0 level3 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confirm next steps<o:p></o:p></span></li></ul>
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:.1pt;margin-bottom:.0001pt;mso-list:l0 level2 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agree on next steps<o:p></o:p></span></li></ol>
</ol>
<p class="MsoNormal"><span style="mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:56.7pt;margin-bottom:.0001pt;text-indent:-38.7pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Wrap and confirm next EPDP Team meeting (5 minutes):<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:72.1pt;margin-bottom:.0001pt;text-indent:-15.4pt;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">EPDP Team Meeting #41 Thursday 2 September at 14.00 UTC (placeholder, if necessary)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:72.1pt;margin-bottom:.0001pt;text-indent:-15.4pt;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Confirm action items<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:72.1pt;margin-bottom:.0001pt;text-indent:-15.4pt;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">c.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Confirm questions for ICANN Org, if any</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<div style="mso-element:footnote-list"><br clear="all">
<hr align="left" size="1" width="33%">
<div style="mso-element:footnote" id="ftn1">
<p class="MsoFootnoteText"><a style="mso-footnote-id:ftn1" href="#_ftnref1" name="_ftn1" title=""><span class="MsoFootnoteReference"><b><span style="font-size:9.0pt"><span class="MsoFootnoteReference"><b><span style="font-size:9.0pt;mso-fareast-language:EN-GB">[1]</span></b></span></span></b></span></a><b><span style="font-size:9.0pt">
“Created” in this context means that ICANN org, with the assistance of the the technical community will develop a standard that defines how and where this field or fields can be used within EPP and the RDAP protocol.<o:p></o:p></span></b></p>
</div>
<div style="mso-element:footnote" id="ftn2">
<h1 style="margin:0in;margin-bottom:.0001pt;background:white"><a style="mso-footnote-id:ftn2" href="#_ftnref2" name="_ftn2" title=""><span class="MsoFootnoteReference"><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black;font-weight:normal"><span class="MsoFootnoteReference"><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black;mso-fareast-language:EN-GB">[2]</span></span></span></span></a><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black;font-weight:normal">
If a Contracted Party chooses to</span><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black"> differentiate between legal and natural registration data or personal and non-personal data AND chooses to</span><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black;font-weight:normal">
publish this field or fields in RDDS, </span><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black">those field(s) will be appended to the requirements of an RDDS response format as currently defined in the RDDS Specifications for
Ry & Rr (see </span><span style="color:black"><a href="https://www.icann.org/resources/pages/registry-agreement-raa-rdds-2015-04-27-en"><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif">https://www.icann.org/resources/pages/registry-agreement-raa-rdds-2015-04-27-en</span></a></span><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black;font-weight:normal">)
</span><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black">and WHOIS Advisory (https://www.icann.org/resources/pages/registry-agreement-raa-rdds-2015-04-27-en)</span><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black;font-weight:normal">.
<s>the existing </s></span><span style="color:black"><a href="https://www.icann.org/resources/pages/rdds-labeling-policy-2017-02-01-en"><s><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;font-weight:normal">Registry Registration Data Directory
Services Consistent Labelling and Display Policy</span></s></a></span><s><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black;font-weight:normal"> is expected to apply</span></s><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;color:black">.</span><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif"><o:p></o:p></span></h1>
</div>
<div style="mso-element:footnote" id="ftn3"><w:Sdt SdtTag="goog_rdk_293" id="-185444823">
<p class="MsoNormal"><a style="mso-footnote-id:ftn3" href="#_ftnref3" name="_ftn3" title=""></a><span class="MsoFootnoteReference"><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif"><span class="MsoFootnoteReference"><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif;mso-fareast-language:EN-US">[3]</span></span></span></span><span style="font-size:9.0pt;font-family:"Calibri Light",sans-serif"><w:sdtPr></w:sdtPr><w:Sdt SdtTag="goog_rdk_292" id="-1063797769">
Not to be confused with the Code of Conduct that is referenced in the RAA and/or Registry Agreements.</w:Sdt></span><span style="font-size:9.0pt"><o:p></o:p></span></p>
</w:Sdt></div>
</div>
</body>
</html>