<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Dear All,<o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; 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><b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(51, 51, 51);">Sub
Team for </span></b><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Trademark Claims </span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">call held on </span><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Friday,
16 June 2017 at 16:00 UTC<b>. </b>Attendance of the call is posted on agenda wiki page: <o:p></o:p></span><a href="https://community.icann.org/x/_kjwAw" style="font-family: Calibri, sans-serif; font-size: 14px;">https://community.icann.org/x/_kjwAw</a></p>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: 15.6pt;">
<b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">MP3: </span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><a href=" https://audio.icann.org/gnso/gnso-rpm-review-trademark-claims-16jun17-en.mp3
" style="font-family: Calibri, sans-serif; font-size: 14px;">https://audio.icann.org/gnso/gnso-rpm-review-trademark-claims-16jun17-en.mp3</a></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span class="MsoHyperlink"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Adobe Connect recording: </span></b></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span><a href="https://participate.icann.org/p6erdmrfxmh/" style="font-family: Calibri, sans-serif; font-size: 14px;">https://participate.icann.org/p6erdmrfxmh/</a></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=53guiRzsIm52y2arEi1oK3cZB85_WaVbAwT-RuOvf1U&s=rgxIRrQDuq51-CxCB7m2-j6VZSbzaD_sax3FXJHB7Ss&e=" style="color: purple;">http://gnso.icann.org/en/group-activities/calendar[gnso.icann.org]</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">** Please let me know if your name has been left off the list **<o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Mailing list archives: </span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://mm.icann.org/pipermail/gnso-rpm-trademark/" style="color: purple;"><u><span style="color: rgb(59, 115, 175); background-color: white;">http://mm.icann.org/pipermail/gnso-rpm-trademark/</span></u></a><o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Wiki page: </span><a href="https://community.icann.org/x/_kjwAw" style="font-family: Calibri, sans-serif; font-size: 14px;">https://community.icann.org/x/_kjwAw</a></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Thank you.<o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Kind regards,<o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Michelle </span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></p>
<p style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<b><u><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Adobe Connect chat </span></u></b><b><u><span style="font-size: 11pt; font-family: Calibri, sans-serif;">transcript for 16 June 2017:</span></u></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">
</span></p>
<div style="font-family: -webkit-standard;"> Michelle DeSmyter:Welcome to the Review of all Rights Protection Mechanisms (RPMs) Sub Team for Trademark Claims on Friday, 16 June 2017 at 16:00 UTC</div>
<div style="font-family: -webkit-standard;"> Michelle DeSmyter:Agenda wiki page: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_-5FkjwAw&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=vIzIINx8AG7ijzn4zzo5T2dG-O19GlVizOk_W8s_aAw&s=hmCPyd5VtqSrwEGvoUP3rdYZWIWVV8ZnbgcT41kB-Ec&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_-5FkjwAw&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=vIzIINx8AG7ijzn4zzo5T2dG-O19GlVizOk_W8s_aAw&s=hmCPyd5VtqSrwEGvoUP3rdYZWIWVV8ZnbgcT41kB-Ec&e=</a></div>
<div style="font-family: -webkit-standard;"> Greg Shatan:All, I just sent around a further revision of the questions, using Justine's version as a jumping off point. Sorry not to get it done further in advance of the call.</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:thanks Greg, we'll include that in our discussion today.</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:I'm hearing a little echo....just me?</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:Kristine's additions to the rest of the questions are in red font in the text, but may not be very clear.</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:4. Does the exact match criteria for Trademark Claims Notices limit its usefulness? a. What is the evidence of harm under the existing system?.i. Are there studies,
reports or articles discussing the harm of typosquatting and other forms of non-exact-match cybersquatting?ii. What is the actual experience of brandowners?iii. What is the link between non-exact-match cybersquatting and phishing,malware distribution, botnets,
counterfeiting, and other related harms?iv. What information can be gleaned from UDRP/URS studies? What are the limitations of relying on UDRP/URS studiesv. What other sources of information should be used to explore the level of harm? b. Should the
matching criteria for Notices be expanded? i. If so, how (which criteria) and why?A. Review each suggested non-exact match ii. What results (including unintended consequences) might each suggested form of expansion of matching criteria have? iii.
What balance should be adhered to in striving to deter bad-fa</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:I have Greg's proposal ready for upload into the AC room, so let me know when.</div>
<div style="font-family: -webkit-standard;"> Greg Shatan:Thanks, both Amr and Kristine. Probably easier to read in the AC room version.</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:Support Greg's version limited to: 4/a/b/c/d/i/ii/iii and not the other data subquetions.</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:"Subquestions"</div>
<div style="font-family: -webkit-standard;"> Philip Corwin:Agree with Greg that we should examine different types of non-eact matches separately, not as an indivisible whole</div>
<div style="font-family: -webkit-standard;"> Philip Corwin:Don't agree with proposed 4iii -- we are tasked to look at protection of TM rights, not other types of harm</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:Agree</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Phil and Greg -- Agree: Proposed or Exposed other non-exact matches types should be subject of separate, specific queries.</div>
<div style="font-family: -webkit-standard;"> Greg Shatan:Phil, we can't look a this in a vacuum.</div>
<div style="font-family: -webkit-standard;"> Philip Corwin:We also need to add looking at what types of changes in language of notice to domain registarnts would need to be made for different types of non-exact matches</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:Agree with Kristine re: data gathering items.</div>
<div style="font-family: -webkit-standard;"> Rebecca Tushnet:+1 Michael</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Phil -- Woud that be 4.d.i.?</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:Current google doc with all the questions here: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_13u5h6Wh6QUqW0vzT5q0zCTEmjMQ8-5FiCat6ZehLHQC7Q_edit&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=vIzIINx8AG7ijzn4zzo5T2dG-O19GlVizOk_W8s_aAw&s=ArJ_W1KRj6l-hvdkb9tO2HHXiGdjNJ4VMp0i4xUAnBA&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_13u5h6Wh6QUqW0vzT5q0zCTEmjMQ8-5FiCat6ZehLHQC7Q_edit&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=vIzIINx8AG7ijzn4zzo5T2dG-O19GlVizOk_W8s_aAw&s=ArJ_W1KRj6l-hvdkb9tO2HHXiGdjNJ4VMp0i4xUAnBA&e=</a></div>
<div style="font-family: -webkit-standard;"> Philip Corwin:@Michael -- yes, but also need to examine whether one master notice is sufficient or whether different notice would need to be generated for different types of matches</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:Thanks Phil...that was a part of the original Qs that may have been left behind.</div>
<div style="font-family: -webkit-standard;"> Greg Shatan:The desk chair's not even cold yet....</div>
<div style="font-family: -webkit-standard;"> Greg Shatan:We could ask for the actual experience and practices of cybersquatters as well.</div>
<div style="font-family: -webkit-standard;"> Greg Shatan:I guess they are a subcategory of registrants....</div>
<div style="font-family: -webkit-standard;"> Rebecca Tushnet:I use a walking desk...</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:Welcome back, Michael.</div>
<div style="font-family: -webkit-standard;"> Rebecca Tushnet:But indeed it could be interesting to find out how many malware etc. distributors use nonexact matches</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:Amr: Two suggestions I noted so far. 1. 4(a) should include the same analysis for the current claims system as well as the proposed ones. and 2. 4(b) should include
a reference to an analysis of each proposed non-exact match.</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:Third suggestion: Should the text of the claims notice be different for various matches/situations?</div>
<div style="font-family: -webkit-standard;"> Rebecca Tushnet:+1 Phil</div>
<div style="font-family: -webkit-standard;"> Rebecca Tushnet:That's a good point--some have suggested in the main group that notices should only go to one side, and we should add a question about that (though I doubt I will support that in the end)</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Kristine -- Agree</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:NOTE: Should we identify any terms in our questions that need definition/clarification for the main group? I'm thinking of the need to be sure we change "Registrant" to "Applicant" when referring
to entities that applied for a domain but abandoned the application.</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Susan: Agree need to keep our eye on Consumer Protection -- this consideration should be part of the main group's answers to questions. </div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:@Michael: Justine had the same observation RE: "users" in question 3, which might more appropriately be changed to "potential registrants".</div>
<div style="font-family: -webkit-standard;"> Philip Corwin:To clarify, I stipulated that other types of harm may be associated with a cybersquatted domain. So that any analysis of the incidence of typosquats will implicitly capture that. What I don't favor
is detailed inquiry into the degree to which a type of non-TM harrm is associated with a partiucular form of non-exact match.</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:Amr, I think we need to stick with the definition we've agreed to</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Amr -- I would use the more accurate "applicants" -- "potential registrants" suggests that EXCEPT FOR notice they would have been able to register and would have proceeded to register the applied
for domain names.</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:We do want to review the impact of the Claims notice on both types of users.</div>
<div style="font-family: -webkit-standard;"> Greg Shatan:I am referring particularly to spearphishing and fraud.</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Kristine -- Two Suggestions: Looking at Question 3, if we include question re: users, should we also include question about post-registration notice to TMCH Registrant? Also, change 3.c. "potential
registrants" to "applicants"</div>
<div style="font-family: -webkit-standard;"> Susan Payne:phil I can assure you that some of the most effective scams involve the typo domains because the recipient who makes a cursory check of the domain reads it as the name they are expecting</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Phil -- Agree as clarified. Thanks.</div>
<div style="font-family: -webkit-standard;"> Susan Payne:I think we have a difference of iopinion on what is a trade mark harm.. potential customers who are scammed create a major reputational risk for brands in addition to the harms to the member of the
public</div>
<div style="font-family: -webkit-standard;"> Greg Shatan:Superannuated hand.</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Susan -- That is exactly correct. I believe TM owners would agree that a vast majority, if not all of identified phishing schemes targeting their customers and suppliers use domain names that
incorporate known or TMCH-registered trademarks.</div>
<div style="font-family: -webkit-standard;"> Kristine Dorrain - Amazon Registry Services:<a href="https://docs.google.com/document/d/13u5h6Wh6QUqW0vzT5q0zCTEmjMQ8_iCat6ZehLHQC7Q/edit">https://docs.google.com/document/d/13u5h6Wh6QUqW0vzT5q0zCTEmjMQ8_iCat6ZehLHQC7Q/edit</a></div>
<div style="font-family: -webkit-standard;"> Philip Corwin:Again, I stipulated for the record that any or all of those harms may be associated with typosquatted domains. I'm not saying that shouldn't factor into our analysis of each type of non-exact match.
I just don't favor extended inquiry into the extent to which each type of further harm is associated with a partucular form of NEM, especially as I doubt that any data available is that granular.</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:Actually, with the data we have from the AG, we can't even confirm that all trademark records downloaded and contributing to the abandonment rate had any association with attempted registrations at all.</div>
<div style="font-family: -webkit-standard;"> Philip Corwin:what is the alternative term?</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:"applicant"/"domain name applicants"/"cart holders"</div>
<div style="font-family: -webkit-standard;"> Philip Corwin:I'm fine with DN applicant</div>
<div style="font-family: -webkit-standard;"> Philip Corwin:Don't like cart holder at all</div>
<div style="font-family: -webkit-standard;"> Philip Corwin:Indeed, if the registration is deterred by the TM Claims Notice the domain never gets to the cart</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Kristine -- Hate to be the latecomer to the party and suggest changing the party's color scheme -- but Updated Question =1.b. change "good-faith registrations" to "good-faith domain name applications"</div>
<div style="font-family: -webkit-standard;"> Susan Payne:fine by me</div>
<div style="font-family: -webkit-standard;"> Greg Shatan:Ok, here. No intent, including an intent to register a domain name.</div>
<div style="font-family: -webkit-standard;"> Rebecca Tushnet:What about "what does the customer see in the process?"</div>
<div style="font-family: -webkit-standard;"> Rebecca Tushnet:That can't be proprietary</div>
<div style="font-family: -webkit-standard;"> Susan Payne:and brand owners do receive claims notices too</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:Sorry. Dropped off the call.</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:Back on now.</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Kristine -- Agree to removal of Q4</div>
<div style="font-family: -webkit-standard;"> Susan Payne:totally agree</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Susan -- Great explanation -- and Agree</div>
<div style="font-family: -webkit-standard;"> Susan Payne:great work Kristine and Michael</div>
<div style="font-family: -webkit-standard;"> Michael R Graham:@Kristine -- THANKS!</div>
<div style="font-family: -webkit-standard;"> Amr Elsadr:Thanks all. Bye.</div>
</div>
<div><br>
</div>
</body>
</html>