<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>So I have added the following statement to the document:</p>
<p><br>
</p>
<p>"
</p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:18.0pt"><span style="font-family:"Times New
Roman",serif;
mso-fareast-font-family:"Times New Roman"">We note
that those parties who
pushed the hardest for making this distinction between legal and
natural
persons also pushed hard for a field or fields to input the
data.<span style="mso-spacerun:yes"> </span>Given that the
recommendation will remain
that it is a voluntary field, and it is up to the contracted
parties, whose
business models vary enormously, how they use the field(s), we
do not believe
that recommendations concerning the precision of the field are
useful.<span style="mso-spacerun:yes"> </span>If ICANN
undertakes to instruct the IETF, for
instance, how to standardize the field, how is the distinction
and the collection
and disclosure of the relevant data necessary to make that
distinction still
voluntary?<span style="mso-spacerun:yes"> </span>This is a
matter to be left to
private sector best practice. <span style="mso-spacerun:yes"> </span></span></p>
<p>
<style>@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;
mso-font-alt:新細明體;
mso-font-charset:136;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:-1610611969 684719354 22 0 1048577 0;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-536859905 -1073732485 9 0 511 0;}@font-face
{font-family:"\@PMingLiU";
panose-1:2 1 6 1 0 1 1 1 1 1;
mso-font-charset:136;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:-1610611969 684719354 22 0 1048577 0;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin:0cm;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:PMingLiU;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:PMingLiU;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}div.WordSection1
{page:WordSection1;}</style></p>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">It appears immediately before the last
paragraph.</div>
<div class="moz-cite-prefix">Manju and I remain convinced that we
need to make this statement. She is hopefully asleep at this
moment, being 12 hours out of sync with EST. It reflects the
arguments we have been pursuing for the last number of months,
nothing new here....but it will be forgotten if we don't restate
it, and we all know that comments on the final report are not
going to be read as much as these minority statements.</div>
<div class="moz-cite-prefix">I am including Kathy and Bruna on this
thread as I know Kathy has been following the arguments recently
rather closely.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">cheers Steph<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2021-09-10 12:02 p.m., Stephanie E
Perrin wrote:<br>
</div>
<blockquote type="cite" cite="mid:4b5efd4c-a000-fb45-0d60-128ded32c0bd@mail.utoronto.ca">
<p>Actually, the GAC minority statement makes my point rather
eloquently. We did not include a comment on the stupidity of
providing precision about the data elements of a field that is
not mandatory.....see the following<br>
</p>
<p><span style="left: 60px; top: 86.6556px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.930697);" role="presentation" dir="ltr">Recommendation #1 Fields to
Facilitate Differentiation between Legal and Natural Person
Registration Data</span><br role="presentation">
<span style="left: 60px; top: 136.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.905203);" role="presentation" dir="ltr">The GAC urged for the creation
and use of data fields to flag legal registrants and the
presence or absence of personal</span><br role="presentation">
<span style="left: 60px; top: 161.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.919814);" role="presentation" dir="ltr">information in their data sets.
Such flagging mechanisms would provide a necessary first step
for differentiation.</span><br role="presentation">
<span style="left: 60px; top: 186.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.928752);" role="presentation" dir="ltr">Recommendation 1 includes
several obligations with regard to the creation of fields to
facilitate differentiation</span><br role="presentation">
<span style="left: 60px; top: 211.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.92673);" role="presentation" dir="ltr">between legal and natural person
registration data and identify whether that registration data
contains personal or</span><br role="presentation">
<span style="left: 60px; top: 236.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.927445);" role="presentation" dir="ltr">non-personal data. In addition
to creating these fields, there are further obligations:</span><br role="presentation">
<span style="left: 90px; top: 261.656px; font-size: 18.3333px;
font-family: sans-serif;" role="presentation" dir="ltr">●</span><span style="left: 120px; top: 261.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.906917);" role="presentation" dir="ltr">for ICANN to coordinate the
technical community, for example the RDAP WG, to develop any
necessary</span><br role="presentation">
<span style="left: 120px; top: 286.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.907152);" role="presentation" dir="ltr">standards associated with such
field(s);</span><br role="presentation">
<span style="left: 90px; top: 311.656px; font-size: 18.3333px;
font-family: sans-serif;" role="presentation" dir="ltr">●</span><span style="left: 120px; top: 311.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.910993);" role="presentation" dir="ltr">for the SSAD, consistent with
the EPDP Phase 2 recommendations, to support the fields in
order to facilitate</span><br role="presentation">
<span style="left: 120px; top: 336.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.902015);" role="presentation" dir="ltr">integration between SSAD and the
Contracted Parties’ systems; and</span><br role="presentation">
<span style="left: 90px; top: 361.656px; font-size: 18.3333px;
font-family: sans-serif;" role="presentation" dir="ltr">●</span><span style="left: 120px; top: 361.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.914252);" role="presentation" dir="ltr">for the fields to support
specific values related to the status of legal persons and the
presence or absence of</span><br role="presentation">
<span style="left: 120px; top: 386.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.911399);" role="presentation" dir="ltr">personal data.</span><br role="presentation">
<span style="left: 60px; top: 436.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.902721);" role="presentation" dir="ltr">The GAC especially values the
precision of this Recommendation in specifying precisely what
values should be</span><br role="presentation">
<span style="left: 60px; top: 461.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.915141);" role="presentation" dir="ltr">included in these fields. The
GAC though believes that Recommendation 1 would be more
effective in creating the</span><br role="presentation">
<span style="left: 60px; top: 486.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.942198);" role="presentation" dir="ltr">necessary infrastructure for
differentiation if it:</span><br role="presentation">
<b><span style="left: 90px; top: 511.656px; font-size:
18.3333px; font-family: sans-serif; transform:
scaleX(0.909378);" role="presentation" dir="ltr">1.</span></b><b><span style="left: 103.913px; top: 511.656px; font-size:
18.3333px; font-family: sans-serif;" role="presentation" dir="ltr"> </span></b><b><span style="left: 120px; top:
511.656px; font-size: 18.3333px; font-family: sans-serif;
transform: scaleX(0.931816);" role="presentation" dir="ltr">required
contracted parties to not just create but also to</span></b><b><span style="left: 537.982px; top: 511.656px; font-size:
18.3333px; font-family: sans-serif;" role="presentation" dir="ltr"> </span></b><b><span style="left: 542.117px; top:
511.656px; font-size: 18.3333px; font-family: sans-serif;
transform: scaleX(0.876411);" role="presentation" dir="ltr">use</span></b><b><span style="left: 568.029px; top: 511.656px; font-size:
18.3333px; font-family: sans-serif;" role="presentation" dir="ltr"> </span></b><b><span style="left: 572.165px; top:
511.656px; font-size: 18.3333px; font-family: sans-serif;
transform: scaleX(0.920754);" role="presentation" dir="ltr">these
fields;</span></b><b><br role="presentation">
</b><b><span style="left: 90px; top: 536.656px; font-size:
18.3333px; font-family: sans-serif; transform:
scaleX(0.909378);" role="presentation" dir="ltr">2.</span></b><b><span style="left: 103.913px; top: 536.656px; font-size:
18.3333px; font-family: sans-serif;" role="presentation" dir="ltr"> </span></b><b><span style="left: 120px; top:
536.656px; font-size: 18.3333px; font-family: sans-serif;
transform: scaleX(0.920795);" role="presentation" dir="ltr">provided
specific timelines for making these fields operable; and</span></b><b><br role="presentation">
</b><b><span style="left: 90px; top: 561.656px; font-size:
18.3333px; font-family: sans-serif; transform:
scaleX(0.909378);" role="presentation" dir="ltr">3.</span></b><b><span style="left: 103.913px; top: 561.656px; font-size:
18.3333px; font-family: sans-serif;" role="presentation" dir="ltr"> </span></b><b><span style="left: 120px; top:
561.656px; font-size: 18.3333px; font-family: sans-serif;
transform: scaleX(0.930029);" role="presentation" dir="ltr">ensured
that the fields will operate within the current and
contemplated systems for data collection and</span></b><b><br role="presentation">
</b><b><span style="left: 120px; top: 586.656px; font-size:
18.3333px; font-family: sans-serif; transform:
scaleX(0.904756);" role="presentation" dir="ltr">disclosure.</span></b><br role="presentation">
<span style="left: 60px; top: 636.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.925277);" role="presentation" dir="ltr">For clarity, the GAC thinks that
requiring contracted parties to populate these fields for all
future registrations,</span><br role="presentation">
<span style="left: 60px; top: 661.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.938143);" role="presentation" dir="ltr">irrespective of whether the
contracted parties elect to differentiate in their treatment
of data from natural versus</span><br role="presentation">
<span style="left: 60px; top: 686.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.921914);" role="presentation" dir="ltr">legal entities, is efficient and
in the public interest because it would provide a basis to
flag and identify data that may</span><br role="presentation">
<span style="left: 60px; top: 711.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.914114);" role="presentation" dir="ltr">be the subject of future
expedited SS</span></p>
<p><span style="left: 60px; top: 711.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.914114);" role="presentation" dir="ltr"><br>
</span></p>
<p><span style="left: 60px; top: 711.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.914114);" role="presentation" dir="ltr">Going to go back in and add a
comment on this stupidity that flies in the face of database
construction logic</span></p>
<p><span style="left: 60px; top: 711.656px; font-size: 18.3333px;
font-family: sans-serif; transform: scaleX(0.914114);" role="presentation" dir="ltr">cheers Steph<br>
</span></p>
<div class="moz-cite-prefix">On 2021-09-10 11:27 a.m., Mueller,
Milton L wrote:<br>
</div>
<blockquote type="cite" cite="mid:DM6PR07MB47001745013700B934A262A8A1D69@DM6PR07MB4700.namprd07.prod.outlook.com">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<br>
<div> </div>
<div>
<div dir="auto">> Our arguments are not clearly presented
in the final report. <br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">So? What matters in the final report is the
policy conclusions, not the arguments of all sides. <br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I invite you to write a guest blog for IGP
covering the process, but that's public commentary, which
should never be confused with an ICANN policy document. <span id="🙂">🙂</span><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">>jockeying tecently about what goes in the
report and what has to be in minority statements has <br>
</div>
<div dir="auto">> been intense and ludicrous.</div>
<div dir="auto"><br>
</div>
<div dir="auto">indeed.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
</blockquote>
</blockquote>
</body>
</html>