<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Noto Sans Symbols";}
/* 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;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.xmsolistparagraph, li.xmsolistparagraph, div.xmsolistparagraph
{mso-style-name:x_msolistparagraph;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.xmsonormal0, li.xmsonormal0, div.xmsonormal0
{mso-style-name:x_msonormal0;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.xmsochpdefault, li.xmsochpdefault, div.xmsochpdefault
{mso-style-name:x_msochpdefault;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman",serif;}
span.xemailstyle19
{mso-style-name:x_emailstyle19;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle20
{mso-style-name:x_emailstyle20;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle21
{mso-style-name:x_emailstyle21;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle22
{mso-style-name:x_emailstyle22;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle23
{mso-style-name:x_emailstyle23;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle24
{mso-style-name:x_emailstyle24;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle25
{mso-style-name:x_emailstyle25;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle26
{mso-style-name:x_emailstyle26;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle27
{mso-style-name:x_emailstyle27;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle28
{mso-style-name:x_emailstyle28;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle29
{mso-style-name:x_emailstyle29;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle30
{mso-style-name:x_emailstyle30;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle31
{mso-style-name:x_emailstyle31;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle32
{mso-style-name:x_emailstyle32;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle33
{mso-style-name:x_emailstyle33;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle37
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:334040244;
mso-list-template-ids:331744624;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</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:#1F497D">Rebecca:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Since I’m trying to revise the “harm” question-samples, I want to understand your question and comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">My understanding (and I can stand corrected) is that “data” seeks empirically quantifiable answers (e.g. “How many UDRP actions have you filed?” “How many NORNs
have you received?”) whereas “anecdotal” seeks narrative responses. Obviously, the fact that we receive 5 anecdotal responses stating the same thing may become data, but that would be in the analysis, and not in the questions. So what I presumed was that
by categorizing questions as “data” or “anecdotal” we are referring to the type of answers we expect to receive from survey takers.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Michael R. Graham<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Gnso-rpm-data [mailto:gnso-rpm-data-bounces@icann.org]
<b>On Behalf Of </b>Tushnet, Rebecca<br>
<b>Sent:</b> Friday, February 16, 2018 1:59 PM<br>
<b>To:</b> Julie Hedlund <julie.hedlund@icann.org>; gnso-rpm-data@icann.org<br>
<b>Subject:</b> Re: [Gnso-rpm-data] Action Items from 16 February 2018 RPM Data Sub Team Call<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div id="divtagdefaultwrapper">
<p><span style="font-family:"Calibri",sans-serif;color:black">Thanks for sending these notes. I will take up the drafting of a few sentences. I'm not sure the list of questions is more helpful than the basic question we're trying to answer but I am willing
to put them back in as examples of what we came up with but don't think are necessarily good wording for eliciting reactions from nonlawyers.<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif;color:black">One comment: I am increasingly puzzled by the way "anecdotal" is being used across the board, including for the evidence of harm and as inserted in part 5. In a properly sampled, representative survey,
the plural of anecdote actually is data. It seems to me that, in particular, contemplated long form answers to the survey are being tossed into the "anecdote" pile for no particularly good reason. Could someone explain their reasoning on these?<o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div id="Signature">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Rebecca Tushnet<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Frank Stanton Professor of First Amendment Law, Harvard Law School<br>
703 593 6759 <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Gnso-rpm-data <<a href="mailto:gnso-rpm-data-bounces@icann.org">gnso-rpm-data-bounces@icann.org</a>>
on behalf of Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>><br>
<b>Sent:</b> Friday, February 16, 2018 4:08:47 PM<br>
<b>To:</b> <a href="mailto:gnso-rpm-data@icann.org">gnso-rpm-data@icann.org</a><br>
<b>Subject:</b> [Gnso-rpm-data] Action Items from 16 February 2018 RPM Data Sub Team Call</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xmsonormal"><a name="x__MailOriginalBody"><span style="font-size:11.0pt">All,
</span></a><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">Below are the action items and notes staff captured from the RPM Data Sub Team meeting today (16 February 2018). The notes from the call are posted to the Sub Team wiki space, together with the call recording,
transcript and Adobe Connect chat and attendance records.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">Note also that the next call will be on
<b>Friday, 23 February at 1700 UTC.</b></span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">Best Regards,</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">Julie</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">Julie Hedlund, Policy Director</span><o:p></o:p></p>
<p class="xmsonormal"><b><span style="font-size:11.0pt"> </span></b><o:p></o:p></p>
<p class="xmsonormal"><b><span style="font-size:11.0pt">Action Items:</span></b><span style="font-size:11.0pt">
</span><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Staff will update Section 5. Survey of Potential Registrants beginning on page 33 in the Google Doc based on the discussion during today’s
call.</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">With respect to hypotheticals (question on 35-36 in the Google Doc) Sub Team members should volunteer to produce two documents and circulate
them on the list prior to the 23 February call:</span><span style="font-family:"Calibri",sans-serif">
<o:p></o:p></span></li></ol>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Short summary of what they hope to get from the use of hypotheticals;
</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Short summary of why not to use a hypothetical. Kristine has volunteered for the second item.</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ol>
</ol>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RPM Data Sub Team meeting at ICANN61: The RPM Co-Chairs will discuss whether one of the slots could be repurposed for the RPM Data Sub Team.</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Section 3, Survey of TM and Brand Owners: Sub Team members should review and comment on the list concerning the final anecdotal and data questions
for the question “What is the evidence of harm under the existing [exact match] system?”, page 22-23.</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ol>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><b><span style="font-size:11.0pt">Notes:</span></b><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">5. Survey of Potential Registrants.</span><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:11.0pt">Page 33 -- Inserted note to the survey providers:</span></i><span style="font-size:11.0pt"> Language is helpful and clear.</span><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:11.0pt">Page 34 -- Have you attempted to register a domain name in one of these new domains? [If no to both, terminate the survey]</span></i><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Thought we weren't going to suggest terminating the survey. But if they aren't considering registering and haven't tried to register then they aren't a potential registrant. Or do we still want them
to look at the claims notice? If they continue with the survey, it might be good to find if the process seems confusing.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Leave the language as is, and also give the survey provider latitude to change it.</span><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:11.0pt">Page 34-35 -- The wording of this set of questions should be discussed with the surveyor... [etc.]</span></i><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Gather information multiple different ways.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Question: In other cases we've been more specific; have we given enough direction here?</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Thought we were leaving in all of the variations of the questions? Examples -- deleted in the Google doc: "If, when registering your domain, you received a notice with the following wording, would you
believe you were: </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">legally allowed to continue with the registration, not legally allowed to continue, not be sure if you were legally allowed to continue?" etc.
</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Bring back the deleted questions and include them in the note:
</span><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:11.0pt;color:black">The wording of this set of questions should be discussed with the surveyor. We would like to present the language of the notice to people in all relevant groups (1-3) and ask comprehension
questions. The questions should be as neutral and non-leading as possible. This may involve beginning with “explain in your own words” and then asking more directed questions about perceptions of legal rights and risks, as well as “what would you do next
if you received the notice when you attempted to register?” (e.g., stop, continue, consult someone else, etc.) and “why or why not?” – Anecdotal question.
</span></i><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:11.0pt;color:black">Other sample questions:</span></i><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:11.0pt;color:black"> If, when registering your domain, you received a notice with the following wording, would you believe you were:
</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">a. legally allowed to continue with the registration</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">b. not legally allowed to continue</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">b. not be sure if you were legally allowed to continue? </span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">If, when registering your domain, you received a notice with the following wording, would you believe you would:</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">a. definitely get sued if you continued</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">b. might or might not get sued</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">c. definitely would not get sued if you continued?
</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">If, when registering your domain, you received a notice with the following wording, would you believe that:</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">a. you had a legal right to continue with the registration?</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">b. you might or might not have a legal right to continue with the registration?</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">c. you had no legal right to continue with the registration?
</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">What would you do if you received a notice with the following wording:</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="font-family:"Noto Sans Symbols";color:black">a.
</span><span style="color:black">continue with the registration</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">b. not continue with the registration</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">c. consult someone else [who]</span></i><o:p></o:p></p>
<p style="vertical-align:baseline"><i><span style="color:black">something else [explain]</span></i><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">Page 35-36:</span><o:p></o:p></p>
<p class="xmsonormal"><i><span style="font-size:11.0pt">Consider offering Hypothetical: Famous maker of computers, Horse, and scenarios at extremes such as horse.computers and horse.farm -- if consumer attempting to register these received notice, what would
they do? </span></i><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Did not have consensus on this. Guidance on what to present to the full WG.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Trying to get to a general understanding of what is trademark law, but not sure offering hypotheticals is the best way to do this. Perhaps in a more direct fashion?</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Is that the purpose of the Hypothetical? Not automatically opposed to hypotheticals, but need to understand what info we're trying to get at & whether there's a less subjective way to get that info.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- The idea is to try to figure out if people would be scared away from non-infringing uses of TM terms.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Could ask the survey provider if this helps.
</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- It actually sounds like we don't all have the same understanding of what info the hypotheticals are trying to elicit.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- But the problem is we can never know what intent is and even if someone says I think it's ok to get "apple.farm" if their intent is bad faith (which we would not know).</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- There is no right answer.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- How useful is the data? Could also get adverse inferences. Not in agreement on what we would get by using a hypothetical. Okay if we are trying to elicite specific information that is actionable.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Anything that helps us to make the claims notice is helpful.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">ACTION: Leave this suggestion (the hypothetical) and ask for a volunteer to make a short summary of what they hope to get from the hypothetical (Rebecca?). Kristine would be willing to write why not to use
a hypothetical. Susan has offered to help.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">2. Timing of future meetings & ICANN61</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Try to knock the Additional Marketplace RPMs on the head as quickly as possible.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Have a big session in PR to get it done. Make the room set up as a working session. Make it clear that people shouldn't be there if they aren't going to be working. Not a presentation of findings.
Make sure we have remote participation.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- Could be difficult to schedule an additional meeting given conflicts, and “pop-up” rooms do not have remote access.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">-- The RPM WG has 4 session slots for a total of 6 hours; the Co-Chairs will discuss whether one of the slots could be repurposed for the RPM Data Sub Team.
</span><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>