<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#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;}
.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:770199161;
mso-list-type:hybrid;
mso-list-template-ids:-1216188320 2139232284 1719938884 134807553 -801063670 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:"Calibri",sans-serif;
mso-fareast-font-family:"Times New Roman";}
@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">The next EPDP Phase 2A meeting will be Tuesday, 31 August 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="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">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:"Apple Color Emoji";color:black">🚨🚨</span></u></b><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></span></u></b><b><u><span style="font-size:11.0pt;font-family:"Apple Color Emoji";color:black">🚨🚨</span></u></b><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><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. Support Staff to create a clean
<a href="https://docs.google.com/document/d/1knSKHXt0njWqXMmpiDKA76amycenNBUl/edit">
"cannot live with" table</a> and an updated redline Section 3 that incorporates (i) the non-substantive grammatical changes (which were highlighted in green) and (ii) the EPDP Team agreements from today's meeting. (complete)<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">2. Support Staff to propose compromise language based on the outstanding items from today's discussion. (complete)<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">3. EPDP Team to review the updated Section 3 document and populate any further "cannot live with" items based on the four highlighted questions (on p. 3, 7, and
9 of the redline Section 3 doc) into the <a href="https://docs.google.com/document/d/1knSKHXt0njWqXMmpiDKA76amycenNBUl/edit">
new "cannot live with" table</a> by <b><u>17:00 UTC on Monday, 30 August.</u></b><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 #39</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">Thursday 26 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 “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">26 August – consider “cannot live with” items identified & agree on updates to 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">27 August – publish draft Final Report for EPDP Team review, consensus call.
<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.<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 – 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 “cannot live with” items identified<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<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">Goal is to publish the integrated draft Final Report, following agreed upon next steps, including statement on consensus
<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">31 August – address remaining issues<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">May need to pencil in 2 September as a tentative meeting to resolve final issues, if any<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">Support Staff grouped the items that were flagged to better organize today’s discussion.<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 first issue is the proposal to the GNSO Council – there are two specific proposals here. The first is to delete reference to implementation plans. Also, some noted that language in second part
should 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">Ultimately, it is still the Council’s decision when it would take on more scoping work.
<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">Question for the Team to consider: would any of these changes being proposed result in “cannot live with” items for other groups?<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 default should be does everyone agree not the other way around. Future changes should be defaulted to everyone cannot live with unless they say that they can.
<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">Some note the reference to 9.4.4 in this recommendation should be deleted, as this is already referenced later in the report.
<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">Question to the group – would the cannot live with item be resolved by deleting “which indicates that a Contracted Party needs to have a mechanism to identify that a registration record does not
contain any personal data.”<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">Groups can live with the proposed compromise here<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The question to the group is – is the new version preferred over the previous version?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There is a difference in the Phase 1 rec. between 17.1 and 17.3 – the important point to make is to resolve the legal v. natural issue, but not all are convinced that the legal v. natural issue
was resolved. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would the group be OK with removing lines 87-91 and move these opinions to the minority statements, or if not, group should consider the proposed edits.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not everyone will read the minority statements, so this text should be included in the text of the report.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not agree to remove this text, this constitutes whitewashing the report, as most readers will not read the minority statements<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The report should accurately reflect the context in which the recommendation is given – that is why this preamble is important. Agree to be concise, but should not be whitewashed.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This does seem to be a significant change to be making at this stage.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This text detracts from the report and do not agree that this is whitewashing. If the Team lands on retaining this section, it needs to be clear that the paragraph does not belong in the previous
section to GNSO Council. <o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If these are kept, they should be moved to footnotes so as to be clear that these are not part of the recommendation or policy. Whether or not someone reads the minority reports should not be this
team’s concern – what matters most is how the recommendations are implemented, and the text needs to be clear for that reason.
<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;margin-left:.1pt;mso-list:l0 level4 lfo1">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The next edits apply to recommendation #1 and the footnote added.<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">It is important to maintain the option to create this field within their own platform – not just RDDS or SSAD.<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 concerned with what CPs are doing individually – the change from a must to a may is changing the entire concept of what was being discussed. The purpose is that when the fields are created
is for all to use them.<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">It is coming back to haunt the Team that the Team is using different language to create these fields than we are using to create all other fields for Phase 1.
<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">See value in having the field displayed somewhere, but do not think there is consensus on 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">Most important that the field is created.
<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 proposed changes from Staff Support reflect what the group agreed to.
<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">Believe the group agreed to creation of an optional field that is similar to other RDDS fields – perhaps a footnote that makes this crystal clear is necessary. If we are talking about something
that is just part of the registrar system, that is akin to a credit card 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">Suggest update to the specific contact provisions – the RDDS Spec of the CL&D policy
<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">No members of the CPH team are supportive of using the field in RDDS at all<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 the small team, there was agreement that there should be no prohibition in using this field in RDDS, but do see value in a standardized system, in particular for use and integration with SSAD<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 terminology of RDDS was included originally so that there was a clear trigger for ICANN org to initiate the process outside of ICANN in the standards bodies in developing the RDAP extension
– this field must be created. The language regarding RDAP and RDDS is now causing challenges – perhaps we could change this to a field must be created and include a footnote to enable or initiate this process to create a new extension.
<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">Can the group not have a must and have a few mays in the same sentence – a field MUST be created and then tie to this language: The EPDP expects that the technical community, for example the Registration
Data 119 Access Protocol (RDAP) Working Group, will develop any necessary standards associated with such fields. Having one long sentence is a bit confusing.<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">Fundamentally, the group has agreement that the new field must be created and must be used by those who differentiate. The specificity is the problem. RDDS may be one option for the use of such
a field, but there may be other uses as well. Please provide suggested text either during the call today or shortly thereafter to move this forward.<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">Suggest that breaking the paragraph apart could help so that there is clear delineation between the must and the mays. Impression about the may be used in RDDS and the connection to the footnote
– in RDAP, if there is no value in that field, it never gets transferred. Impression about the may – is that if a registrar chose to display this field, if they chose to publish it, it would mimic the Phase 1 recommendation the additional data element – for
example, if .medical TLD requires additional registration requirements and they wanted it to be published, it would fall in as an additional data element that CPs could choose to publish as part of minimum public data set, but it would fall in with CL&D –
in that it would be published at the bottom. <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 original proposed language from the small team – field must be created that may be used by the contracted parties – that was the first draft and what was originally discussed. That was later
amended to created or extended in RDAP. Finally, that was changed to “created for the RDDS” – these successive edits change the meaning. CPs agreed to a standard data element and agreed that it could be used in RDDS.<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">Action: Staff and Leadership team will come forward with proposed text for the group to consider.
<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">Regarding ALAC’s comment about default values, registries did not have adequate time to discuss if this a cannot live with value. However, not clear why not having default values is a cannot live
with item. <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 default value, the possible values are legal, natural, unspecified (which means registrant said will not say), or the question has never been asked. The default value should be no data
has been provided. <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">Defining a field with four distinct values and would like clarity on what would be the default.
<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">If advising a registrar would advise to ignore what a registrant says if not sure about geographic whereabouts – it is entirely possible for the field to be blank, vacant, or deleted.
<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">May want to ignore the value, but do not agree that therefore you must not record the value. The default value is that you don’t anything and don’t know. How that translates into subsequent action
is a separate matter. <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 first value is the most innocuous and should be the default – looking for clarity for the implementation team.
<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">RySG comment to change SHOULD to MAY – disagree with this change as it undermines the effort of many members<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">Could “are encouraged to” be in replace of should?
<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 guidance may be applicable in all jurisdictions and all cases – therefore this suggestion is not applicable in all cases. This is not an attempt to water down the language – just heard some
pushback around the word should. <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 point is you should follow the guidance – one of the reasons some would like the guidance is it helps to establish a normative direction. Could live with are encouraged to.
<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">“Such flagging would facilitate” – RySG recommend changing would to could, as this is speculative.
<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">No objections, so change applied.<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">Staff to update Section 3 in a redlined format and flag outstanding items from Support Staff’s side re: Rec. 1 and use it for further exercise of cannot live with.
<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">Question from Staff – what does “within ICANN” mean in the context in the Code of Conduct? Noting that a code of conduct was not part of phase 1 or 2.
<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">RrSG note that point ii under Rec. 5 is confusing – is this a cannot live with?
<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 the yellow-highlighted change from strongly encourage to suggest considered a minor change to the Team?
<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">What is the preferred way for the EPDP team to provide feedback?<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">Support Staff to create a clean table for the team to provide further input. Support Staff will also produce an updated redline so that everyone can see the what the changes will look like.<o:p></o:p></span></li></ul>
</ul>
</li><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 #40 Tuesday 31 August at 14.00 UTC<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>
</body>
</html>