<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)">
<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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p
{mso-style-priority:99;
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;}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
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.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle38
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle39
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle40
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle41
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle42
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle43
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle44
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle45
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle46
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle47
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle48
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle49
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle50
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle51
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle52
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle53
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle54
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle55
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle56
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle57
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle58
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle59
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle60
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle61
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle62
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle63
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle64
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle65
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle66
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle67
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle68
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle69
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle70
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle71
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle72
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle73
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle74
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle75
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle76
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle77
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle78
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle79
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle80
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle81
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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><!--[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="blue" vlink="purple">
<div class="WordSection1">
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Dear All,</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please find the attendance of the call attached to this email. The MP3, Adobe Connect recording and Adobe Connect chat below for the Review of all Rights
Protection Mechanisms (RPMs)<span style="color:#1F497D"> </span>PDP Working Group call held Wednesday, 03 May 2017<span style="color:black"> at
</span>16<span style="color:black">:00</span><span style="color:black"> UTC</span>. Attendance of the call is posted on agenda wiki page:<span style="color:#1F497D">
</span><a href="https://community.icann.org/x/YQTfAw">https://community.icann.org/x/YQTfAw</a><o:p></o:p></span></p>
<p style="line-height:15.6pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">MP3:</span></b><span class="MsoHyperlink"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#111111;text-decoration:none">
</span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#111111"><a href="https://audio.icann.org/gnso/gnso-rpm-review-03may17-en.mp3">https://audio.icann.org/gnso/gnso-rpm-review-03may17-en.mp3</a><o:p></o:p></span></p>
<p class="MsoNormal"><span class="MsoHyperlink"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;text-decoration:none">Adobe Connect recording: </span></b></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<a href="https://participate.icann.org/p2alb0v4h8n/?OWASP_CSRFTOKEN=db441a9fc3f1dbab4a44a7882fd09687d0ac76186bdbb7181b70976b2026473e">
<b><span style="color:black;background:white">https://participate.icann.org/p2alb0v4h8n/</span></b></a><o:p></o:p></span></p>
<p style="line-height:15.6pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="http://gnso.icann.org/en/group-activities/calendar">http://gnso.icann.org/en/group-activities/calendar</a><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">** Please let me know if your name has been left off the list **</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Mailing list archives: </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="http://mm.icann.org/pipermail/gnso-rpm-wg/"><span style="background:white">http://mm.icann.org/pipermail/gnso-rpm-wg/</span></a><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Wiki page: </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="https://community.icann.org/x/wCWAAw">https://community.icann.org/x/wCWAAw</a><span style="color:#1F497D"><o:p></o:p></span></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Thank you.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Kind regards,<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Julie
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Adobe Connect chat transcript for 03 May 2017:</span></u></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<o:p></o:p></span></p>
<p class="MsoPlainText"> Julie Bisland:Welcome to the Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group on Wednesday, 03 May 2017 at 16:00 UTC for 90 minute duration.<o:p></o:p></p>
<p class="MsoPlainText"> Julie Bisland:Agenda Wiki page: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_YQTfAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=IntYCrZkD56chphrbu3XRfVONVKPh4X39ilucRbQ5eE&s=P1I4Y7NY6wVfu_bnng3CiseHUdTJl_zGiMCEV0pg55s&e">
https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_YQTfAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=IntYCrZkD56chphrbu3XRfVONVKPh4X39ilucRbQ5eE&s=P1I4Y7NY6wVfu_bnng3CiseHUdTJl_zGiMCEV0pg55s&e</a>=
<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Hi folks.<o:p></o:p></p>
<p class="MsoPlainText"> Petter Rindforth:Hi there!<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Hey Petter. How are you?<o:p></o:p></p>
<p class="MsoPlainText"> Petter Rindforth:Happy - the first day of spring here in Stockholm!<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:That's great.<o:p></o:p></p>
<p class="MsoPlainText"> Petter Rindforth:@Mary: Do we have an updated time schedule somewhere, or are we still working on the "old one" when it comes to next steps (like the URS, etc)?<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Petter, we've (staff) been working on one but it doesn't change the URS portion. It mostly tries to accommodate what the Sunrise and Claims Sub Teams are proposing.<o:p></o:p></p>
<p class="MsoPlainText"> Petter Rindforth:Ok, thanks<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:We anticipate more changes after Joburg as well, where the Working Group will have a 3 hour meeting :)<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:I hope that one is in the afternoon local time, to make it more convenient for those in North America.<o:p></o:p></p>
<p class="MsoPlainText"> Steve Levy:Hi all. FYI, I'll need to leave my office and jump to the audio bridge at some point in today's meeting.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@George, it's Joburg time from 9 a.m. to noon (or thereabouts)<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Looks like that'll be around 3 am NYC time. Ouch.<o:p></o:p></p>
<p class="MsoPlainText"> Paul Keating:Hcellow all<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@George, sorry :( FYI that most of the Working Group sessions are in the morning Joburg time, to accommodate cross community sessions in the afternoon. One consequence of the 4-day Policy Forum meeting format, I'm afraid<o:p></o:p></p>
<p class="MsoPlainText"> David McAuley:Hello all<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):Hello ll<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:Morning all -- on audio bridge as well.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:is there a tentative Jo'Burg schedule posted yet?<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:for the whole meeting<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Lori, I think there is an overall block schedule that either was just published or is just about to be. Let me check.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:I saw the RPM time in the chat<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Lori, all - here is the latest draft of the block schedule for the overall ICANN59 meeting in Joburg:
<a href="https://meetings.icann.org/sites/default/files/icann59_block_schedule_v3.3_1may17.pdf">
https://meetings.icann.org/sites/default/files/icann59_block_schedule_v3.3_1may17.pdf</a><o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:We are hoping to finalize the GNSO schedule soon.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:You do a fine job.<o:p></o:p></p>
<p class="MsoPlainText"> Paul Tattersfield:Sorry I'm late<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Thanks.<o:p></o:p></p>
<p class="MsoPlainText"> Paul Keating:I remain very interested<o:p></o:p></p>
<p class="MsoPlainText"> Paul Keating::-)<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:Still waiting for someone to pick up the dial in line...<o:p></o:p></p>
<p class="MsoPlainText"> Kristine Dorrain - Amazon Registry Services:Mary sent a fabulous tutorial about SMD files around last week to the main list.<o:p></o:p></p>
<p class="MsoPlainText"> Kristine Dorrain - Amazon Registry Services:To echo Lori, we may want to still schedule something though<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Paul M, we're checking<o:p></o:p></p>
<p class="MsoPlainText"> Kristine Dorrain - Amazon Registry Services:But if the broader WG doesnt understand the TMCH/SMD file process, please take advantage of that amazing resource<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:I'm in!<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Mary - thanks!<o:p></o:p></p>
<p class="MsoPlainText"> David McAuley:+1 @Paul - thanks Mary<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Mary: thank you for the note regarding where we may need more data for sunrise questions.
<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Lori, credit goes to Kristine D for those!<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:then thanks to Kristine D.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Phil - any word on Private Protections Subgroup?<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:Will do, Phil.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):question: does the same level of protection exist in the real world - inclusion of the word in other word marks?<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):current inclusion of "the" will lead to lots of claim messages which will freak out lots of registrants<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Indeed, Maxim. Too many false positives.<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:I am in the Adobe Connect room now.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):is there a right which prohibits others from inclusion of the words?<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:@Maxim the same service does exist in the real world. All trademark watch services offer similar matching rules<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:"RED" (for AIDS fundraising), for example, would have numerous matches, including "BARED", "SCARRED", "WATERED", etc.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):I think it is an additional service and not rights protection<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):the reson for issuing lots of claims needs to be well justified<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):*reason<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Michael, so we are talking about adding plurals plus "contains"<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:These can already be monitoRED, using tools like DomainTools, etc.<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:George :)<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Michael, are you also talking about both types of notices (Claims Notice plus Notice of Registered Name)?<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):we should not give more rights than already granted in real world<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:For fanciful marks like EXPEDIA, etc., it might make sense.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:If there was a way to draw some objective metric for reducing false positives, it could be workable.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:e.g. check the term against the 100 million+ domains in the .com zone file, and see how many matches there are. "RED" would fail, but "EXXON" or "EXPEDIA" might pass.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:RED would not be confused with Scared but could be confused with REDdonations.whatever<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):what do we do with a single letter inclusions into TMCH?<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Right, Lori. Just a matter of how you make it so that the TM Claims notice only appears for REDDomains.junk, vs. something else that is clearly a false positive.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:+1 Michael on this proposal. Thanks for putting it together.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:Jonathan's proposal is at the bottom of Page 5.<o:p></o:p></p>
<p class="MsoPlainText"> Paul Tattersfield:Good question Maxim<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:*RedDonations.junk, even<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Paul -- Thanks.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:TM Claims notice would need to no longer be finite, then, implicitly, in Michael's proposal.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Phil - what does holding the already late additional GI proposal do to our ability to discuss the 2 that are currently on the floor? I don't want to waste time talking today to indecision...<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):Legacy TLDs have special rights - their RAs are quite different<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:That was my question as well thanks Brian.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Since Legacy TLDs are long past their launch.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):and all Sunrises are long in the past, thus ... 90 days are long over<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@George, I suppose that's true for pre-launch mechanisms.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:@Mary: also for post launch, since the TM Claims only last for 90 days.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:True - since that is not a continuing mechanism (at the moment<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Plus, we've already heard from registry operators that some registrars are not participating in new gTLD launches, because of the costs of implementing TM claims notices, etc.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:So, this could have a detrimental effect on existing registrars.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:(as well as registrants)<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Page 6, top left.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Phil - thanks. <o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:As an aside, does anyone know how many unique GIs exist worldwide? (we know there are millions (tens of millions?) of registered TMs)<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Phil - agree. We want to give everyone a chance to present ideas, but they do need to get around to doing so in a timely manner.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:Q7 - proposals received from Kathy and Greg<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:I believe that WIPO keeps GI data<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@George - likely none. For example, some governments make GI claims to "champaign" but it is also a city in Illinois...<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:We coivered these proposals last week. Why are we re-covering this?<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@John, I think the idea is to have a really quick summary (2 minutes) to refresh memories and for those who weren't on the call.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:@Paul: sorry, poorly phrased. I meant "unique" as to total number, not "unique" in the sense of non-colliding.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:(e.g. a GI might exist in both Japan and Germany, don't want to double-count them.<o:p></o:p></p>
<p class="MsoPlainText"> Ivett Paulovics:EUIPO has a list of GIs in the 28 Member States of the EU<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:I object to use of the words "rules". The IRT and the STI provided recommendations.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:i.e. are we up to 1000+ GIs yet? or still in the hundreds? Or into the 10,000+ range?<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:lol Kathy<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:That said, the GAC also provided GAC advice that impacted how the RPMs weree actually implemented.<o:p></o:p></p>
<p class="MsoPlainText"> Hector Ariel Manoff:I practice in Argentina and we do not have this kind of mark as descdribed<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:What Kathy is reading is NOT the law. It is misleading. Words that are dominant portion of a design mark or a stylized word mark are always protected b/c the reality is that consumer use words to communitcate.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Agree with J Scott. <o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:The AGB just says "word mark" - will this exclude marks comprised entirely of stylized text?<o:p></o:p></p>
<p class="MsoPlainText"> Steve Levy:I'm jumping to the audio bridge<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:A will clarify my earlier posting. Are always protectable when they can be protected as a tradeamark.<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:@Mary. I would argue not. <o:p></o:p></p>
<p class="MsoPlainText"> Hector Ariel Manoff:The Argentina system of trademark law is very simmilar that US system in this respect<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:I think we should refrain from saying whether one entity or another did not follow the guidebook. We should only be focusing on future recommendations in my point of view<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Page 10 of <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__euipo.europa.eu_tunnel-2Dweb_secure_webdav_guest_document-5Flibrary_observatory_documents_Geographical-5Findications-5Freport_geographical-5Findications-5Freport-5Fen.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=IntYCrZkD56chphrbu3XRfVONVKPh4X39ilucRbQ5eE&s=UooioBZKq4LIaFaPMAuk9YRVJ-A3OAhLSClV3DVr79M&e">
https://urldefense.proofpoint.com/v2/url?u=https-3A__euipo.europa.eu_tunnel-2Dweb_secure_webdav_guest_document-5Flibrary_observatory_documents_Geographical-5Findications-5Freport_geographical-5Findications-5Freport-5Fen.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=IntYCrZkD56chphrbu3XRfVONVKPh4X39ilucRbQ5eE&s=UooioBZKq4LIaFaPMAuk9YRVJ-A3OAhLSClV3DVr79M&e</a>=
mentions there are 4,800 protected GIs in the EUIPO database.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:(more than I expected)<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:I agree with Jeff Neuman <o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:We need to decide what is the best practice and make sure the TMCH is following that best practice<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:@Jeff: it could be an indication that the policy is too vague, if it left too much open to interpretation by the TMCH provider.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:Agree with Jeff and J Scott. We don't need to blame anyone to determine what the future should look like.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:May staff suggest the following questions for discussion: (1) are marks comprised entirely stylized text included or not; (2) are marks that comprise text plus design (where it can be shown that the text portion is predominant
and not disclaimed) included or not; and (3) clarify that marks comprised entirely of design (i.e. figurative marks without letters, wholly device marks) are excluded?<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):word 'best' surrounded by 7 pineapple images ... gives quite nice TMCH inclusion<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:Mary, (3) could never get in anyway, could it?<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:The distinctions must be between (1) and (2)<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Agree with Mary's questions<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Rebecca, yes, so that question is probably unnecessary as a question (unless it needs to be reconfirmed :))<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Rebecca is correct about 3 but maybe we state the obvious anyway just to clarify the other questions<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:That's why it's asked as a "clarify that they are excluded" :)<o:p></o:p></p>
<p class="MsoPlainText"> David McAuley:That's how I read Mary's #3 - as a point of confirmation<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:I'm worried about "predominant" and "can be shown"--who does the showing? What is the standard?<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:As much as I like challenge processes, I am not sure that would work in this case since the information behind the Sunrise registration is not publicly known until much later if at all.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Rebecca, yes that's difficult - which is why we're raising it as a possible question for discussion (rather than just say throw out all marks with some design element even if there is potentially protectable text in them))<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:There is always an element of subjectivity to trademark issues. Not sure how that is eliminated 100% as mechanical rules can yield bizarre results as evidenced in matching rules used by INGO IRT.<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:In other words, a third party has no information by which to base its challenge of a registration. It could only get this information in a "claims period". But if the registration was taken during Sunrise, there would
be no ability to get a claims notice since the domain is "not available".<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@George -- Sorry, just coming back to chat. What do you mean "would need to no longer be finite"?<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:I am fine with text only marks. That is, marks whether portrayed in block letter type or stylized fonts.<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:I am not advocating that the information should be made public at all. Just saying that a post-facto challenge is not really a viable remedy<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:In the later (styized) color claims should not prevent the mark from registration in the TMCH<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:The challenges could be gamed, if they lead to the domains being transferred. e.g. Team Member #1 uses a bogus TM to obtain a domain. Team Member #2 "challenges" team member #1. Team Member #1 defaults, thereby passing
domain name "cleanly" to Team Member #2.<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@George -- I see now -- you mean they would not be subject to 90 day or other limit if applied to Legacy TLDs. I see point. Thanks.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:(kind of how fraud bidding can occur in domain auctions, where a fraudulent top bidder is associated with an underbidder)<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:@George. I have been working on ICANN DNS policy since 1998. ALL systems can be gamed. If gaming is found, we need to address the specific gaming not refuse to offer a solution because bad actor abuse the system.<o:p></o:p></p>
<p class="MsoPlainText"> Paul Keating:I Prefer Ms. Kleiman's proposal. It strikes a proper balance.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady: I Prefer Mr. Shatan's proposal. It strikes a proper balance.<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:In a challenge George, Team Member #2 would have to show that they have legitimate rights to the name under a challenge process. That would be by showing a valid mark, which Team Member #2 in your example would not be
able to show<o:p></o:p></p>
<p class="MsoPlainText"> Paul Keating:limiting acceptance to purely text-based marks is also simpler and avoids any subjective issues relative to acceptalnce.<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:George, team member 2 would have to have a bona fide registration, so I think your scenario doesn't work.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Agree with Shatan proposal.<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:+1 J. Scott Also I thought I heard Kathy say she would allow a device mark in this context? The TMCH guide treats that as the equivalent of a design mark.<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:I support Mr. Shatan's proposal. <o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:@JScott: a system that eliminates the TMCH and/or sunrise is much harder to game (i.e. there'd be most post-registration UDRPs, but that's a small price to pay overall).<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:Agree with Shatan proposal.<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:Rebecca's point is not exact.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):I wonder what happens with emojis ... now in IDN TLDs ... those which allow that
<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):sorry - currently in cctlds , but who knows<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:@Rebecca. That point can be made of ALL trademarks.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Rebecca, what about stylized text without device/design elements?<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):and legacy TLD ... for example <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__xn-2D-2Dn3h.com_&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=IntYCrZkD56chphrbu3XRfVONVKPh4X39ilucRbQ5eE&s=c0akvUJ9-CWi90ODfYPUrWxXcd7rmO6_i7WB4xMcEJY&e">
https://urldefense.proofpoint.com/v2/url?u=http-3A__xn-2D-2Dn3h.com_&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=IntYCrZkD56chphrbu3XRfVONVKPh4X39ilucRbQ5eE&s=c0akvUJ9-CWi90ODfYPUrWxXcd7rmO6_i7WB4xMcEJY&e</a>=
<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Or text inside an oval or square?<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:All infringement is a multifactor test. No one (registrars expecially) don't want to have to deal with it. Soooo, we have to deal with a system in the most efficient way possible.<o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:Here is a clarifying response to Phil's question about actual steps : "Where the national authority has distinguished between standard character marks, stylized marks and design marks, no stylized marks or design marks
may be registered in the TMCH database. In addition, where the only text that would be entered into the TMCH has been disclaimed, either as a phrase or as separate words or any combination thereof, the text may not be registered in the TMCH database."
<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:@Mary as I posted to the list the same is true with stylized text.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Claims are warnings not decisions.<o:p></o:p></p>
<p class="MsoPlainText"> J. Scott Evans:How about all marks can be registered and use the TM Claims and only text (both block letter and stylized) can use Sunrise?<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:The national authorities make those designations for purposes of coding.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:@Kathy: but then that encourages forum shopping, implicitly "endorsing" jurisdictions where the national authority makes no such distinction.<o:p></o:p></p>
<p class="MsoPlainText"> Phil Marano (Mayer Brown):Isn't the stylized A example somewhat irrelevant in practice given that one character domains are almost always reserved, and to the extent they are released they are released after Sunrise as premium names?
<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Kathy, what will be the scope/definition of "stylized mark" and "design mark"?<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:I do not suuport Kathy typed response<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Particularly in jurisdictions where design elements are coded and text are not. It's not 'legal protection" issue its a coding issue.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):due to poor education of registrants - they freak out after getting a claim notice sent to them<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Do we have evidence of "freaking out"? Even anecdotal"<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@J Scott -- I was just thinking the same thing: Text + trademarks are only registered for TM Claims, and do not give Sunrise registration rights.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:@Lori: yes, if you do a search.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Where is "freaking out" evidence?<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Again, differentiating between text, stylized, etc. has a lot to do with coding for searches rather than actual issues of what may or not be protected.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:https://www.reddit.com/r/Bitcoin/duplicates/65o867/trademark_for_blockchain/<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Paul -- Agree with dual purpose of TM Claims Notice<o:p></o:p></p>
<p class="MsoPlainText"> Paul Keating:@Paul, if notice is teh main issue then limit the sunrise application and limit the TMCH to a notice provider<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):+1 @Greg<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Just looked at that. Not sufficient for me to understand the response of a set of end users.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Lori, that's why distinguishing between a "purely standard word/character mark" and a "stylized text only" mark is difficult. it's different from distinguishing between these two types of mark and a mark that includes both
text and design elements. <o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:Paul and Kathy are the original parents? I have already been forgotten.....................<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Mary, we agree on that.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):so the Claim notice is more informative and in the end has - did you understand it?<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:So I err on side of inclusion not exclusion.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Agree, exclusion is too great with Kathy's proposal.<o:p></o:p></p>
<p class="MsoPlainText"> David McAuley:Jeff, you have a right to be forgotten, no?<o:p></o:p></p>
<p class="MsoPlainText"> Colin O'Brien:I agree with Lori inclusion not exclusion<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Paul K - I have no problem bifurcating this topic along Claims and Sunrise lines - similar to what Michael G did in his plurals/goods&services proposal. Can't know for sure if we can reach agreement on the outcomes, but
by all means, let's talk through it.<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:I am only forgotten when I dont want to be :)<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Good point, Paul Mc.<o:p></o:p></p>
<p class="MsoPlainText"> David McAuley:LOL<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:There is a convention used in the TMCH derived from TM practice in multiple jurisdictions which the TMCH refers to as the "name" of the trademark. Is that a translation? It is a convention based on the literal element
of the mark that assists in searching. Would be allowing domainers to search for stylized word rademarks named in the database to purchase as domains but deny those same mark owners protection of those same words by notice of such purchase. If the words of
a registered mark can be purchased as a domain name why deny its owner protection against abuse by mere notice?<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:Like Rodney Dangerfield....I get "no respect"<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Here's one where a person was scared to register NYC.beer:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.reddit.com_r_legaladvice_comments_2hfuy7_trademarked-5Fwebsite-5Fname_&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=IntYCrZkD56chphrbu3XRfVONVKPh4X39ilucRbQ5eE&s=Jqd1uW8_bThV328hICijKP9IY_UHjb0dNkT-J8q6kjk&e">
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.reddit.com_r_legaladvice_comments_2hfuy7_trademarked-5Fwebsite-5Fname_&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=IntYCrZkD56chphrbu3XRfVONVKPh4X39ilucRbQ5eE&s=Jqd1uW8_bThV328hICijKP9IY_UHjb0dNkT-J8q6kjk&e</a>=
<o:p></o:p></p>
<p class="MsoPlainText"> Paul Tattersfield:Thanks George<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:@George .... That is a proper trademark owned by the City of New York as they should have been warned<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Far too many "weak" marks like "NYC" scarring registrants.<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:But a bad bright line is not good for registrants when they apply for domain names.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:I see that. Then I would argue that the prospective purchase of nyc.beer has the responsibility to learn where his rights might lay.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:*scaring, even<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Although, some registrants who are scared, might also be scarred. :-)<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:I would not characterize the implicit message of the claims notice somewhat differently -- not quite so scary, especially if you have your own rights to rely on or you can see from the TMCH notice that the claimed mark
is used very differently from that of the applicant.<o:p></o:p></p>
<p class="MsoPlainText"> Kiran Malancharuvil 2:+1 Michael<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:We all enter this sphere at our own risk and yes, many are scarred after years of this debate.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:hehe Lori<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:I agree scope isn't for the TMCH; the question is whether the national authority registered the thing that is to be entered into the TMCH (or a court case recognized it)<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:We are not creating trademark rights.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:No we are not.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:For NYC.beer, I actually looked into the WHOIS history this past weekend, and it doesn't appear that the Reddit poster followed through with the registration (someone in Cleveland ended up buying it instead).<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):we should not<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:We are verifying TM rights.<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:I believe my proposal carries out what's set forth in the AGB.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:(via DomainTools WHOIS history)<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Rebecca: Exactly -- and we should not ask or require TMCH to analyze.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:Some distinctions to consider: (1) pure word/character marks vs stylized text marks; (2) stylized text comprising descriptive words vs stylized text not containing descriptive words; (3) word marks (with or without stylization)
vs word+design mark<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Text marks offer the greatest protection -- you can impute any style.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Stylization narrows for side by side comparisons on product packaging not domains<o:p></o:p></p>
<p class="MsoPlainText"> Paul Tattersfield:that's right George it pushes registrations to professional (bulk holder) registrants rather than people looking to set up a new business
<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:+1 Kathy. We shouldn't "solve" a problem created by those TM applicants who created a problem for themselves.<o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:The choice is totally that of the Trademark Owner<o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:What they choose to register and how they choose to register it is their option.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Exactly, Kathy.<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:This is a problem we are creating for them, by limiting protection of stylized and composite marks beyond that of the trademark laws.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Choice is not always the choice of TM owner where certain jurisdictions require registration based on how mark appears on packaging...a brick and mortar issue not a domain issue<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:words are words<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:@Greg: We're not creating any "problem" for them. The TMCH complements existing law, doesn't replace all other enforcement mechanisms.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Kathy - who does it being written in cursive change the nature of the mark? Do we really draw the line because the DNS doesn't offer cursive fonts?<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:TM owners should be entitled to rely on stylized and composite registrations for entry into the TMCH as they do in using and enforcing their marks.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:+1 Greg<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:Can anyone provide the reference to the 90% refusal to continue with registration stat?<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Lori -- +1<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:Isn't there a distinction to be made between excluding a stylized text mark where the text itself would have been distinctive (it's just that the TM owner chose to register a stylized text version), and excluding a stylized
text mark where the text is descriptive?<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Refusing to give someone an "advantage" doesn't equate with "creating a problem".<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@John, it's in the Analysis group report.<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Lori -- Would you please comment on the "as appears on packaging" requirement and consequences?<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:We should reserve the "advantages" to strictly defined criteria.<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:@ Mary Thanks<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:If we limit the TMCH to text-only standard character marks is creating a problem.<o:p></o:p></p>
<p class="MsoPlainText"> Kristine Dorrain - Amazon Registry Services:Kathy, penalizing the owner of a single mark that happens to be a stylized font likely will have a disproportionate impact on SMEs. Big corporations have deeper pockets to get an array of
rights. I think it's potentially dangerous to assume that all brand owners are Fortune 100 companies with trademark portfolios.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Paul k. - too bad no data along those lines was collected at the time.<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:+1 Kristine<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:+1 Kristine - the SMEs always get ignored in ICANNland. Agree we should not do that here.<o:p></o:p></p>
<p class="MsoPlainText"> Salvador Camacho:Sorry, I have to leave for another meeting but I will check the further emails. Have a great day!<o:p></o:p></p>
<p class="MsoPlainText"> Terri Agnew:finding the line<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:Is anyone else hearing that beeping?<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Kristine -- My concern as well.<o:p></o:p></p>
<p class="MsoPlainText"> Paul Keating:Im sorry but I must leave the call for other matters.<o:p></o:p></p>
<p class="MsoPlainText"> Terri Agnew:we are trying to find the line<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:With regard to abandonment rate, we have 0% idea why these were abandoned or who (or what) abandoned the application.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Might be Scott Austin? (note the icon next to his name?)<o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:Sorry Scott<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Oops, I guess he's speaking.<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:Mary, agree with that distinction.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Domainers don't equate with "bad faith users".<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Stop lumping them in together, please.<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:As to 94% figure -- without context or comparison the figure really has no significance.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:+1 Scott - cybersquatters (not legit domainers) will have a playbook about what to squat on<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:+1 Phil - not the same folks.<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:What's the playbook? Are TMCH refusals public?<o:p></o:p></p>
<p class="MsoPlainText"> Kristine Dorrain - Amazon Registry Services:Scott, if a domain name registrant did purposely target a logo for cybersquatting, how would putting that logo in the TMCH assist the brand owner. That person is clearly hell-bent on cybersquatting
and is highly unlikely to be deterred by a claims notice....I'm not following your suggestion, I'm afraid.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Rebecca - no, but trademark records are<o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:From my experience, it is the SMEs who will be using the same words for their names, goods and services.
<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Phil - we have to be careful. We don't actually know that.,<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:on 0.3% claims notices were ever challenged. So you could say that a vast majority of the abandonments were legitimate<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:We know from the top 10 of The Analysis Group that folks are attempting to register common dictionary words. Hopefully we'll see the top 500 soon.<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@John -- Correct!<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:@Kristine They can search the database based on the literal element of a words plus design mark then purchase the domain name for the literal elements befoer the TM owner does.<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:Any conclusions about abandonment are idle speculation. We don't know if the rate should be 96%. Even calling it "high" is assuming facts not in evidence.<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@George -- and are these "common dictionary words" registered as trademarks? If so, I do not see your point.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:@Michael: yes, they are, because they match somethign in the TMCH.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:e.g. ONE, HOTEL, LUXURY, etc.<o:p></o:p></p>
<p class="MsoPlainText"> Kristine Dorrain - Amazon Registry Services:@ Scott, so your comment was towards Sunrise, not Claims. Ok, thanks for clarifying.<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Greg - +1. beyond idle at this point since we have addressed that issue so many times already. Not just idle - wasteful.<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Steve Levy -- +1<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):THE ?<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:@Kristine the literal element of the logo (stylized text or words plus design) would be used to identify the "name" of the registered mark in the (e.g.) USPTO TESS database.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:Note that we don't know whether the "dictionary words" were registered as word marks somewhere, or as stylized text marks, or as text+design marks (without disclaimer).
<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Mary -- Understood. I think the disclaimer exception would help here. Applicants ALWAYS have the option of declaring there's no likelihood of confusion and proceeding with application.
<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:How many marks in the TMCH were based on design or stylized marks?<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:+1 Lori. <o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:@Jeff: that would be great to know!<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@jeff, taht's what staff is noting - we don't. The question is, whether excluding all forms of stylization and marks that are word+design is the right solution.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):+1<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:I would not say "too far".<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:I do not agree with saying that they have a bit too far a field<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:I thought we agreed on focusing on the the future<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:not the oast<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:@Mary, the other question is whether including all forms of stylization and marks that are word+design is the right solution.<o:p></o:p></p>
<p class="MsoPlainText"> Jeff Neuman:past<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:INTA is reviewing the glosssary and will provide input based on established TM<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:@Mary & Phil - INTA is looking over the draft glossary and will comment<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:There's no way to evaluate the current operations without looking at the current rules & examples given by Deloitte<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Agree with Rebecca that we should look at rules and examples but not assume "too far" or expanding right.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:+1 Michael<o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:Both proposals before us to note that Deloitte has gone too far...
<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:We know what Deloitte is doing, generally - that's in the TMCH Guidelines. Not sure that we can evaluate whether they are applying those standards uniformly, consistently and correctly.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:No consensus that Deloitte has gone too far<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:Should we consider information/metrics that we need or should request in order to answer the questions we have been chartered to answer?<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:@George the bad faith portion of domain purchasers was my intention, which is I beieve the target of the RPM<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:I assisted with the drafting of Greg's proposal and do not agree that Deloitte has
<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):shall we ask for a poll on that (or degrees of "too far/not too far/Ok) ?<o:p></o:p></p>
<p class="MsoPlainText"> John McElwaine:gone to far<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Maxim - agree that we have to take temperature of the entire working group not the proposals of a few<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):@Lori - binary questions quite often are bit misleading<o:p></o:p></p>
<p class="MsoPlainText"> Scott Austin:+1 John<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:Online survey would be better, yes<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:And on a specific proposal or alternative sets of proposals<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:@maxim - agree which is why we need options. I would not support any suggestion that Deloitte is out of scope or "too far"<o:p></o:p></p>
<p class="MsoPlainText"> Kristine Dorrain - Amazon Registry Services:+1 Paul.... sunrise and claims are separate<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:Lori, do you think that Deloitte should have accepted all the examples in the annex? You may well think that--just trying to be clear.<o:p></o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):@Lori , also adding field " comment " might help to understand other levels of support/non-suport<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:I would also mention my ad hoc third proposal, which is for the current practice to be better carried out.<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Rebecca -- What are the examples -- can you point to them?<o:p></o:p></p>
<p class="MsoPlainText"> Rebecca L Tushnet:The ones sent to Deloitte--they should be on the wiki or we can ask Mary to recirculate.<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Rebecca -- Thanks, I will look for them.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:They're on the wiki - I'll send the link around again<o:p></o:p></p>
<p class="MsoPlainText"> Michael R Graham:@Mary -- Thanks!<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:The Deloitte examples are at: <a href="http://mm.icann.org/pipermail/gnso-rpm-wg/2017-April/001583.html">
http://mm.icann.org/pipermail/gnso-rpm-wg/2017-April/001583.html</a><o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:@Michael, there you go! Thanks, George.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Also at: <a href="http://mm.icann.org/pipermail/gnso-rpm-wg/2017-April/001573.html">
http://mm.icann.org/pipermail/gnso-rpm-wg/2017-April/001573.html</a><o:p></o:p></p>
<p class="MsoPlainText"> Julie Bisland:Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group Wednesday, 17 May 2017 at 17:00 UTC for 90 minute duration.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:1700 UTC<o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:To anyone attending GDD - enjoy!<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:My regrets. It's INTA annual meeting time.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:(2nd link starting from page 4 or so)<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Many will be on the road.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:I will be.<o:p></o:p></p>
<p class="MsoPlainText"> Paul Tattersfield:Would a suggestion of extending proof of use to Claims Notices require a formal proposal?<o:p></o:p></p>
<p class="MsoPlainText"> Julie Bisland:Lori, I've noted your apology.<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:Thank you.<o:p></o:p></p>
<p class="MsoPlainText"> Mary Wong:The updated Work Plan doesn't have a meeting on 24 May b/c of INTA<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:I will miss 2 weeks then.<o:p></o:p></p>
<p class="MsoPlainText"> George Kirikos:Bye folks. Have a great two weeks! <o:p>
</o:p></p>
<p class="MsoPlainText"> Maxim Alzoba (FAITID):bye all<o:p></o:p></p>
<p class="MsoPlainText"> Lori Schulman:bye<o:p></o:p></p>
<p class="MsoPlainText"> Kathy Kleiman:@Paul T: probably<o:p></o:p></p>
<p class="MsoPlainText"> Paul McGrady:Thanks Phil. Great call!<o:p></o:p></p>
<p class="MsoPlainText"> Paul Tattersfield:thanks Kathy<o:p></o:p></p>
<p class="MsoPlainText"> Paul Tattersfield:Bye all<o:p></o:p></p>
<p class="MsoPlainText"> Georges Nahitchevansky:Bye everyone<o:p></o:p></p>
<p class="MsoPlainText"> Greg Shatan:Bye all.<o:p></o:p></p>
<p class="MsoPlainText"> David McAuley:Thanks Phil, staff, good bye all<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
</div>
</body>
</html>