<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">I think we may perhaps
be a trifle overwhelmed, Marika, by the size of the poll, the
need to understand the handout if not the entire context of
the EWG report, and of course evaluate the data elements against
a still inchoate sense of the RDS overall purpose. I know I
am overwhelmed, and I am pretty familiar with the EWG report
and its new data elements.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">I certainly appreciate
that we need to make progress and move along, but this is a
big gulp in terms of homework this week, when many of us are
catching up on work not done while we were in Joburg, or the
lucky ones who are either on holidays or at the IETF are not
going to be on the call. So I have a further concern that not
only are we going to have our usual slim attendance at the
rotational call (i.e. middle of the night for North America)
but there are other factors dropping attendance.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">I am going to fill the
poll out, but I have been studying it first and i am not sure
I am going to be able to fully comment on each concern. I hope
my comments will be taken constructively, but there is a lot
of nuance in some of the contextual significance of the data
elements. As Andrew Sullivan said<br>
</font></font></p>
<pre wrap=""><font size="+2" face="Times New Roman, Times, serif"><i>I fear what is happening is that we are failing to work at the right
level of abstraction...
Therefore, we need to distinguish policy desires that are
inconsistent with existing protocols or technical deployments if we're
going to propose policies that require such changes, and we need to
analyse what utility arises from a given desired element in the event
that the element is necessarily sometimes wrong. It is bad policy to
create elements that are likely to be the source of bad policy.
</i><font face="Lucida Grande">I think this true, and while I understand that we have to, for instance, provide an opportunity for individuals to offer their skype handles if that is the way they wish to be contacted....going through all the possible variants of these data elements is not the correct level of data analysis. I look forward to the call on Tuesday, but I am worried that the results of this particular poll will not be as useful as one might hope.
Stephanie Perrin
</font><i>
</i></font></pre>
<p><font size="+1"><font face="Lucida Grande"><br>
</font></font></p>
<br>
<div class="moz-cite-prefix">On 2017-07-14 17:25, Marika Konings
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DE51A667-6419-4A56-9ACE-DCBA3924F69A@icann.org">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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:"GT Walsheim Light";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"GT Walsheim Light",serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier",serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal">Kathy, I’m not sure why you think this is a
referendum. As discussed in Johannesburg and agreed by those
in attendance, the idea is to first identify the ‘universe’ of
data elements to then be able to determine which of those data
elements should be in RDS, which is exactly what this survey
is aiming to do. As such the EWG Final Report is used as an
input to this discussion as directed by the WG’s charter, but
it is now for the WG to critically assess that input and add,
eliminate, change as it deems appropriate. So please take this
as your opportunity to raise any questions about any of the
data elements as well as provide your suggestions on what
should be included in the RDS that has not been listed yet or
what should not be included with your rationale. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To Sara’s point, the WG and leadership team
has recognized from the start that this is an iterative
process and additional input or expertise that is provided
throughout the process may affect preliminary WG agreements.
As such, please do fill out the survey with your wish list,
based on the deliberations as well as input received to date.
At the end of the day, the only way to ‘test’ whether the WG’s
recommendations are considered compliant is to be able to put
something concrete on the table and allow others to provide
input on those recommendations. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All, please make sure to review the handout
before responding to the survey as it provides important
background information on the different data elements that may
help inform your responses.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Marika<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:12.0pt;color:black">From: </span></b><span
style="font-size:12.0pt;color:black"><a class="moz-txt-link-rfc2396E" href="mailto:gnso-rds-pdp-wg-bounces@icann.org"><gnso-rds-pdp-wg-bounces@icann.org></a>
on behalf of Kathy Kleiman <a class="moz-txt-link-rfc2396E" href="mailto:kathy@kathykleiman.com"><kathy@kathykleiman.com></a><br>
<b>Date: </b>Friday, July 14, 2017 at 22:01<br>
<b>To: </b><a class="moz-txt-link-rfc2396E" href="mailto:gnso-rds-pdp-wg@icann.org">"gnso-rds-pdp-wg@icann.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-rds-pdp-wg@icann.org"><gnso-rds-pdp-wg@icann.org></a><br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] IMPORTANT: Reminder
- Poll from 28 June Meeting<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>+1 to Sara's comment. <o:p></o:p></p>
<p>Question: I thought the question on the table in Johannesburg
was what data needed to be collected in order to provide the
service of domain name registration and maintenance? How does
that lead to a referendum on the data elements of the EWG
report?<o:p></o:p></p>
<p>By way of background, the EWG report changed considerably
from its "draft" to its "final" form - adding dozens of pages
to the final report never reviewed or even seen by the ICANN
Community. These included many funky new registration data
elements, some which were optional, some which were not, some
which were clearly defined, and many which were not. Questions
raised about many of these registration data elements at the
ICANN Meeting in London with the EWG were never answered. To
this day, I still don't understand the definition of many of
these data elements.<o:p></o:p></p>
<p>A referendum on these fields now seems like a very odd place
to be right now. <o:p>
</o:p></p>
<p>Best, Kathy<o:p></o:p></p>
<div>
<p class="MsoNormal">On 7/14/2017 2:12 PM, Sara Bockey wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-family:"GT
Walsheim Light",serif">I believe these polling
questions are premature. Given GDPR and outstanding legal
reviews, I don’t see how I can answer these questions
outside of a “wish list” response.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"GT
Walsheim Light",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"GT
Walsheim Light",serif">Sara</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"GT
Walsheim Light",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"GT
Walsheim Light",serif"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:12.0pt;color:black">From: </span></b><span
style="font-size:12.0pt;color:black"><a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
moz-do-not-send="true"><gnso-rds-pdp-wg-bounces@icann.org></a>
on behalf of Lisa Phifer
<a href="mailto:lisa@corecom.com" moz-do-not-send="true"><lisa@corecom.com></a><br>
<b>Date: </b>Wednesday, July 12, 2017 at 10:08 AM<br>
<b>To: </b><a href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true">"gnso-rds-pdp-wg@icann.org"</a>
<a href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true"><gnso-rds-pdp-wg@icann.org></a><br>
<b>Subject: </b>[gnso-rds-pdp-wg] IMPORTANT: Reminder -
Poll from 28 June Meeting</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">Dear all,<br>
<br>
Many thanks to the 14 WG members who have already completed
this week's poll and provided thoughtful rationale for and
against data elements beyond the minimum public data set
(MPDS).<br>
<br>
For those who have not yet done so, please be sure to leave
yourself extra time to review the handout before taking this
week's longer-than-usual poll.<br>
<br>
Link to the poll:<br>
<a href="https://www.surveymonkey.com/r/P5MBXZ2"
moz-do-not-send="true">https://www.surveymonkey.com/r/P5MBXZ2</a><br>
<br>
Link to the handout, for info about each data elements
beyond the MPDS:<br>
<a
href="https://community.icann.org/download/attachments/66086729/28JunePoll-DataElements-ExpandedHandout.pdf"
moz-do-not-send="true">https://community.icann.org/download/attachments/66086729/28JunePoll-DataElements-ExpandedHandout.pdf</a>
<br>
<br>
Link to the last meeting's recording and transcript where
this approach was discussed:<br>
<a href="https://community.icann.org/x/lATfAw"
moz-do-not-send="true">https://community.icann.org/x/lATfAw</a><br>
<br>
<b>This poll will close at COB this Saturday 15 July.<br>
<br>
</b>Best, Lisa<br>
<br>
<br>
At 04:05 PM 7/8/2017, Lisa Phifer wrote:<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Dear all,<br>
<br>
In follow-up to our ICANN59 F2F WG meeting, <b>all RDS
PDP WG Members</b> are encouraged to participate in the
following poll:<br>
<br>
<b><a href="https://www.surveymonkey.com/r/P5MBXZ2"
moz-do-not-send="true">https://www.surveymonkey.com/r/P5MBXZ2</a><br>
<br>
</b>Also attached is an <b>extended version of the Data
Elements handout</b> used for deliberation in our F2F
meeting. This handout provides information about each data
element in this poll, extracted from the EWG Final Report.
<i>Please use time previously set aside for our cancelled
11 July meeting to review this handout and then complete
this week?s longer-than-usual poll.<br>
</i> <br>
Responses should be submitted through the above URL. For
offline reference, a PDF of poll questions can also be
found at:<br>
<br>
<a
href="https://community.icann.org/download/attachments/64947348/Poll-from-28JuneCall.pdf"
moz-do-not-send="true">https://community.icann.org/download/attachments/64947348/Poll-from-28JuneCall.pdf</a>
<br>
<br>
<b>This poll will close at COB Saturday 15 July. Poll
results and the attached handout will be discussed in
our 18 July 16.00 UTC WG meeting.<br>
</b> <br>
Please note that you must be a WG Member to participate in
polls. If you are a WG Observer wishing to participate in
polls, you must first contact
<a href="mailto:gnso-secs@icann.org"
moz-do-not-send="true">gnso-secs@icann.org</a> to
upgrade to WG Member.<br>
<br>
Regards,<br>
Lisa<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</body>
</html>