<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=utf-8">
<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:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
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;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.xmsolistparagraph, li.xmsolistparagraph, div.xmsolistparagraph
{mso-style-name:x_msolistparagraph;
mso-style-priority:99;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.xmsonormal0, li.xmsonormal0, div.xmsonormal0
{mso-style-name:x_msonormal0;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.xxmsolistparagraph, li.xxmsolistparagraph, div.xxmsolistparagraph
{mso-style-name:x_xmsolistparagraph;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.xmsochpdefault, li.xmsochpdefault, div.xmsochpdefault
{mso-style-name:x_msochpdefault;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.xmsohyperlink
{mso-style-name:x_msohyperlink;
color:#0563C1;
text-decoration:underline;}
span.xmsohyperlinkfollowed
{mso-style-name:x_msohyperlinkfollowed;
color:#954F72;
text-decoration:underline;}
span.xemailstyle20
{mso-style-name:x_emailstyle20;
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.xemailstyle34
{mso-style-name:x_emailstyle34;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle35
{mso-style-name:x_emailstyle35;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle36
{mso-style-name:x_emailstyle36;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle37
{mso-style-name:x_emailstyle37;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle38
{mso-style-name:x_emailstyle38;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle39
{mso-style-name:x_emailstyle39;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle40
{mso-style-name:x_emailstyle40;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle41
{mso-style-name:x_emailstyle41;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle42
{mso-style-name:x_emailstyle42;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle43
{mso-style-name:x_emailstyle43;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xapple-converted-space
{mso-style-name:x_apple-converted-space;}
span.EmailStyle51
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle52
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle55
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle56
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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 bgcolor="white" lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:EN-US">Thank you, John.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> GNSO-RPM-WG <gnso-rpm-wg-bounces@icann.org>
<b>On Behalf Of </b>John McElwaine<br>
<b>Sent:</b> Wednesday, October 23, 2019 7:01 PM<br>
<b>To:</b> gnso-rpm-wg@icann.org<br>
<b>Subject:</b> Re: [GNSO-RPM-WG] FW: New Q15 Proposal re: Actions & Notes: RPM PDP WG Meeting 16 October 2019<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">I recall that the issue of the confidentiality of the TMCH database specifically came up in the Implementation Assistance Group (IAG) which was
the group putting together the details and rules of the TMCH. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Having “Data Access” limited to a “need to know basis” was how the subject was originally introduced to the IAG. I believe (but am not sure)
that this “Data Access” may have resulted out of Section 8.1 of the STI Report which stated:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">If feasible, the TM Claims Notice should provide links, or provide alternative methods of providing access, to the
registrant for accessing the TC Database information referenced in the TM Claims Notice for a fuller understanding of the TM rights being claimed by the trademark owner. These links shall be provided in real time without cost to the Registrant. The implementation
details should be left to ICANN Staff to determine how to easily provide access to registrants to this information.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From the September 26, 2012 Report of the IAG which was used to prepare “the draft implementation model of the Trademark Clearinghouse published
by ICANN for discussion purposes”:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Misuse of Data<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">To minimize abuse, distribution of TMCH data should be limited to situations where necessary to implement TMCH functionality.
It should also be justified by technical, performance, uptime, availability, and economic factors. At a minimum, there should be sufficient contractual restrictions to provide enforcement capabilities to guard against abuse of the access and information provided
through the TMCH. Specifically, rights holders have expressed concerns related to the aggregation of mark data through the TMCH, which may expose their brand protection strategies or be used to gather competitive intelligence by competitors. If
<b><u>the TMCH database is freely searchable and accessible, it could be possible to identify a rights holder’s gaps in its intellectual property protection strategies</u></b>. For example, it might be possible to identify jurisdictions in which the rights
holder has not registered its trademarks or in which it has not chosen to defensively register domain names. In this regard, this information could be misused by criminals, such as to conduct phishing attacks or other types of social engineering attacks.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">In addition, concerns were raised with regard to limiting information submitted in the TMCH that may be valuable to
a competitor, especially with regards to a brand-related registry. If it is possible to do extensive searching of the database to compile a list of marks that a mark holder has registered, some IAG members believed that this can reveal the mark holder’s brand
protection strategy because it shows which marks it believes are more valuable than others. If someone can access all of the countries where a specific brand is registered, this may also create competitive advantage because a competitor might go to the unprotected
jurisdiction and register the mark before the mark holder. The TMCH should not allow extensive searching to be done in a manner where a trademark holder’s entire portfolio could be easily accessed. Accordingly, the TMCH should be structured to address how
to minimize data mining by a registry of a competitor’s trademark registration patterns.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">The above report and analysis was related to work undertaken by the IAG looking at the “Data Access” (which labeled issue T1). From the April
13, 2012 Draft Implementation Model:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Specifically, some rights holders indicated concern that the aggregation of rights data through the Clearinghouse may
expose corporate strategies or be used to gather competitive intelligence, particularly if the database is freely searchable and accessible. For example, it might be possible to identify jurisdictions in which a rights holder has not registered its trademarks
or in which it has not chosen to register domain names. In this regard, this information could drive uses such as phishing or other types of social engineering activities.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> GNSO-RPM-WG <<a href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@icann.org</a>>
<b>On Behalf Of </b>Kathy Kleiman<br>
<b>Sent:</b> Wednesday, October 23, 2019 11:22 AM<br>
<b>To:</b> <a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><br>
<b>Subject:</b> Re: [GNSO-RPM-WG] FW: New Q15 Proposal re: Actions & Notes: RPM PDP WG Meeting 16 October 2019<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><strong><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:red">◄External Email►</span></strong><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> - From:
<a href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@icann.org</a> <o:p>
</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
</div>
<p><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">The Trademark Clearinghouse database -- as negotiated by the GNSO Council appointed group and approved unanimously by the GNSO Council and ICANN Board -- was *not* secret or confidential.
It's openness was discussed, debated and agreed to as a monitoring and oversight mechanism, and additionally because so much of what was already within the TMCH would be public materials -- registered trademarks themselves.<o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">Kathy (with my hat as member of the STI)<o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">On 10/23/2019 10:52 AM, Marie Pattullo wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks, Julie. I’m about to go into a call so apologies for the hit & run response, but initial thoughts inline:</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Para one:
</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">The Working Group understands that, on the one hand, trademark owners may register trademarks and enter them into the Trademark Clearinghouse as part of a business-confidential
strategy, including for new products yet to enter the market. </span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:red">Access to the database would allow misuse, including by bad actors and/or competitors.
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">On the other hand, some Working Group members have noted
<span style="background:yellow;mso-highlight:yellow">that it was not clear</span>, during the lead up to the launch of the 2012 New gTLD Program, that the Trademark Clearinghouse database was intended to be a non-publicly-accessible, confidential database.
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:red;background:yellow;mso-highlight:yellow">I wasn’t involved then, but I thought Claudio said that it was always intended to be confidential? I’ve never seen reference
to it being considered as being an open resources.</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:red">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> In addition, some Working Group members expressed concern that potential registrants may benefit from knowing what marks are already in the Trademark Clearinghouse database
prior to attempting a registration, especially in view of the likelihood (based on discussions the Working Group has held with the current Trademark Clearinghouse validator) that some marks may consist of generic words which potential registrants may legitimately
wish to use as a domain name. </span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:red">If it’s a legitimate use, then brand holders won’t stop them.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">The Working Group agrees in principle that an audit of the Trademark Clearinghouse database can be beneficial.
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:red">I still have reservations about this – I don’t think the potential harm, based on fact, is an equal balance for the potential gain, based on supposition.
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Accordingly, the Working Group recommends that, in order to inform the next review of the Trademark Clearinghouse, a small group of community volunteers be formed that will
have limited, specifically-defined, confidential access to the Trademark Clearinghouse database, for the sole purpose of working with ICANN Org and any appointed third party examiner on such review. The scope of such confidential access is to be limited to
oversight purposes only and must not violate any terms of confidentiality that apply to trademark owners whose marks are already in the Trademark Clearinghouse database at that time.
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:red">Should this be take forward, any trademark owners that have chosen to enter their trademarks in the Trademark Clearinghouse must first be given time to consider if
they wish to remove them, and to do so, before they are made known to any such community members, with appropriate safeguards considered for the effect that this may have on such trademark owners.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> GNSO-RPM-WG
<a href="mailto:gnso-rpm-wg-bounces@icann.org"><gnso-rpm-wg-bounces@icann.org></a>
<b>On Behalf Of </b>Tushnet, Rebecca<br>
<b>Sent:</b> Wednesday, October 23, 2019 3:15 PM<br>
<b>To:</b> Julie Hedlund <a href="mailto:julie.hedlund@icann.org"><julie.hedlund@icann.org></a>;
<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><br>
<b>Subject:</b> Re: [GNSO-RPM-WG] New Q15 Proposal re: Actions & Notes: RPM PDP WG Meeting 16 October 2019</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Calibri",sans-serif">I asked this in the meeting but didn't directly address it to Staff: Analysis Group reported on the top ten queried terms in the TMCH. Is it Staff's understanding that this disclosure
by AG breached a confidentiality duty? </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Calibri",sans-serif">The description "n</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#201F1E;background:white">on-publicly-accessible, confidential database"
is not accurate, given that members of the public with no duties of confidentiality can find out on a term-by-term basis by attempting to register. I would suggest something like "database that is inaccessible to the public except through individual registration
attempts."</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Calibri",sans-serif">More generally, I think the proposal needs to state ICANN's understanding of the current rule. Without a clear statement of the current rule, I don't think this audit proposal
is understandable--and to the extent it suggests that disclosing anything, including a top ten list, is a violation of confidentiality, that seems like a worsening of the problem.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div id="Signature">
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Rebecca Tushnet</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Frank Stanton Professor of First Amendment Law, Harvard Law School<br>
703 593 6759 </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-US">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> GNSO-RPM-WG <<a href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-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> Wednesday, October 23, 2019 9:01 AM<br>
<b>To:</b> <a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a> <<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>><br>
<b>Subject:</b> [GNSO-RPM-WG] New Q15 Proposal re: Actions & Notes: RPM PDP WG Meeting 16 October 2019</span><span lang="EN-US">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="xmsonormal"><span lang="EN-US">Dear WG members,<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Per the action item below to draft a new Q15 proposal relating to the discussion during the meeting on 16 October, staff submits for your consideration the following suggested text. We very much look forward to working
with you on further revisions as needed, as well as to the discussion on today’s call.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Kind regards,<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Mary, Ariel, and Julie<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><u><span lang="EN-US">Staff-suggested draft (based on Working Group discussions and suggestions made on the Working Group call of 16 October)</span></u><span lang="EN-US">:<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">The Working Group understands that, on the one hand, trademark owners may register trademarks and enter them into the Trademark Clearinghouse as part of a business-confidential strategy, including for new products yet
to enter the market. On the other hand, some Working Group members have noted that it was not clear, during the lead up to the launch of the 2012 New gTLD Program, that the Trademark Clearinghouse database was intended to be a non-publicly-accessible, confidential
database. In addition, some Working Group members expressed concern that potential registrants may benefit from knowing what marks are already in the Trademark Clearinghouse database prior to attempting a registration, especially in view of the likelihood
(based on discussions the Working Group has held with the current Trademark Clearinghouse validator) that some marks may consist of generic words which potential registrants may legitimately wish to use as a domain name.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">The Working Group agrees in principle that an audit of the Trademark Clearinghouse database can be beneficial. Accordingly, the Working Group recommends that, in order to inform the next review of the Trademark Clearinghouse,
a small group of community volunteers be formed that will have limited, specifically-defined, confidential access to the Trademark Clearinghouse database, for the sole purpose of working with ICANN Org and any appointed third party examiner on such review.
The scope of such confidential access is to be limited to oversight purposes only and must not violate any terms of confidentiality that apply to trademark owners whose marks are already in the Trademark Clearinghouse database at that time.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="xmsonormal"><b><span lang="EN-US" style="font-size:12.0pt">From: </span>
</b><span lang="EN-US" style="font-size:12.0pt">GNSO-RPM-WG <<a href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@icann.org</a>> on behalf of Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>><br>
<b>Date: </b>Wednesday, October 16, 2019 at 3:27 PM<br>
<b>To: </b>"<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>" <<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>><br>
<b>Subject: </b>[GNSO-RPM-WG] Actions & Notes: RPM PDP WG Meeting 16 October 2019</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<p class="xmsonormal"><span lang="EN-US">Dear All,<o:p></o:p></span></p>
<p class="xmsonormal" style="font-variant-caps:normal;orphans:auto;text-align:start;widows:auto;word-spacing:0px">
<span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal" style="font-variant-caps:normal;orphans:auto;text-align:start;widows:auto;word-spacing:0px">
<span lang="EN-US">Please see below the action items captured by staff from the<span class="xapple-converted-space"> </span>RPM PDP Working Group call held on 16 October 2019 at 17:00 UTC. Staff will post these to the wiki space. <b><i>Please note that these
are high-level notes and are not meant as a substitute for the recording, chat room, or transcript</i></b><i>.</i> The recording, Zoom chat, transcript and attendance records are posted on the wiki<span class="xapple-converted-space"> </span>at:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_RARPMRIAGPWG_2019-2D10-2D16-2BReview-2Bof-2Ball-2BRights-2BProtection-2BMechanisms-2B-2528RPMs-2529-2Bin-2Ball-2BgTLDs-2BPDP-2BWG&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=GU7oC_LaBo7KvH3LCTYNBb2Z62O2_gB7PePpFA2YNvE&s=Lebe-G6v-muk6fUa-l7fXJ95Vfc50wtSu3jY53kDW2k&e=">
https://community.icann.org/display/RARPMRIAGPWG/2019-10-16+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG</a>.
<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Best Regards,<o:p></o:p></span></p>
<p class="xmsonormal" style="font-variant-caps:normal;orphans:auto;text-align:start;widows:auto;word-spacing:0px">
<span lang="EN-US">Julie<o:p></o:p></span></p>
<p class="xmsonormal" style="font-variant-caps:normal;orphans:auto;text-align:start;widows:auto;word-spacing:0px">
<span lang="EN-US">Julie Hedlund, Policy Director<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">==</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><b><span lang="EN-US">NOTES & ACTION ITEMS</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><b><span lang="EN-US">Actions:</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><b><span lang="EN-US">Open and Deferred TMCH Questions:</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><u><span lang="EN-US">Q7 Design Marks</span></u><span lang="EN-US">: ACTION: WG agrees to publish Kleiman/Muscovitch and Shatan proposals in the Initial Report for Public Comment.<o:p></o:p></span></p>
<p class="xmsonormal"><u><span lang="EN-US">Q8 GIs: ACTION</span></u><span lang="EN-US">: WG agrees to publish Tushnet proposal in the Initial Report for Public Comment.<o:p></o:p></span></p>
<p class="xmsonormal"><u><span lang="EN-US">Q12</span></u><span lang="EN-US">: ACTION: Staff will work with Maxim to revise the proposal to include context and background, and make it more formal. Make it clear that this is an implementation recommendation,
not policy. Publish to the WG email list for review.<o:p></o:p></span></p>
<p class="xmsonormal"><u><span lang="EN-US">Q15</span></u><span lang="EN-US">: ACTIONS: 1) WG agrees to publish Karanicolas proposal in the Initial Report for Public Comment. 2) ACTION: Staff to draft a new proposal based on suggestions and circulate it to
interested WG members and the Co-Chairs.<o:p></o:p></span></p>
<p class="xmsonormal"><u><span lang="EN-US">Q2</span></u><span lang="EN-US">: Proposal from Martin Pablo Silva Valent: ACTIONS: 1) Martin to revise the proposal with assistance of other WG members and circulate it on the WG email list for review. 2) Staff will
check to see if either party to the contract can seek modifications.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><b><span lang="EN-US">Discussion of whether individual URS proposals should be revisited by the WG, and methodology for doing so: </span></b><span lang="EN-US">ACTION: WG members are requested to continue discussion on the email list.
See the draft survey at: <span class="xapple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__forms.gle_kak3MEWFTNeq69wN9&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=36glY4CKyg4JCvpnCKFaXpx9PW_r5RObgdpcO0mtVM8&s=pEK5aTpdV-IIoTgVC0PHNGEZ969HY26RoiVzAAphdcw&e=">survey
[forms.gle]</a>.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><b><span lang="EN-US">Notes:</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">1. Updates to Statements of Interest: No updates provided.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">2. Status of Questions Q7, Q8, Q12, and Q15:<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Q7 Design Marks: ACTION: WG agrees to publish Kleiman/Muscovitch and Shatan proposals in the Initial Report for Public Comment.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Q8 GIs: ACTION: WG agrees to publish Tushnet proposal in the Initial Report for Public Comment.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Q12: Proposal from Maxim Alzoba – TMCH Operational Considerations<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Need to improve redundancy and availability of the TMCH.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Question: Are you referring to the TM database, run by IBM? Deloitte is the validator and IBM is the maintainer of the database. Answer: Relates to the provision of the database. Or could be a issue with the design,
it’s hard to say. Need to review how it works. Might not be limited to software functions. Could be dataflow design.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Need to get background on the cases reported to GDD colleagues. The validation function is kept separate from the database function. If the WG wishes to investigate this further this is probably an issue with implementation
as to SLA (there are applicable SLAs). Need also to go back and look at the deliberations concerning the original design of the TMCH and database.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Information about the SOW with IBM (and for that matter the SLAs with Deloitte) on this Working Group wiki page, under TMCH Contracting:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pages_viewpage.action-3FpageId-3D61606864&d=DwMDaQ&c=qmi9WrYRGQEDDOxOwKrAjW7mWovpzN_EKyRbeK_zbP0&r=Kepk-9GEB6JgOj0vUGl8c0hdrRM7FW-8Is-VAQU1VAk&m=6PdODCxx0pFS_O8Ct151GXBvBolgy6QESpwRhpAInzE&s=AaHHM_PFma3YOKVp3Fa79Iw_DMDLVZUNFVKWJgOPee8&e=">
https://community.icann.org/pages/viewpage.action?pageId=61606864</a></span><span style="font-family:"MS Gothic"">
</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">ACTION: Staff will work with Maxim to revise the proposal to include context and background, and make it more formal. Make it clear that this is an implementation recommendation, not policy. Publish to the WG email
list for review.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Q15: ACTION: WG agrees to publish Karanicolas proposal in the Initial Report for Public Comment.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Hoped that we could get consensus. <o:p>
</o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Could allow a limited group to access the data, perhaps a future review team? Can’t just open up now when those who participate have been assured of confidentiality.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Question - is there a way for the WG to reach agreement on how to ensure there is some kind of specific, limited access to the data in the TMDB for oversight purposes only (including future reviews)?<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">ACTION: Staff to draft a new proposal based on suggestions and circulate it to interested WG members and the Co-Chairs.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US" style="font-size:12.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">3. Remaining Deferred Charter Questions (see the attached Status of WG Discussions on Agreed TMCH Charter Questions):<o:p></o:p></span></p>
<p class="xmsonormal"><b><i><span lang="EN-US"> </span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><b><i><span lang="EN-US">a. Close Discussion:</span></i></b><span class="xapple-converted-space"><span lang="EN-US"> </span></span><span lang="EN-US">TMCH Category 6: Balance: Charter Question 16: Close discussion.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US" style="font-size:12.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><b><i><span lang="EN-US">b. Discussion:</span></i></b><span class="xapple-converted-space"><span lang="EN-US"> </span></span><span lang="EN-US">TMCH Category 1: Education: Charter Questions 1, 2, and 3 – Proposal submitted by Martin P
Valent for Q2 (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_109482780_Martin-2520Pablo-2520Silva-2520Valent-2520-2D-2520Q2.pdf-3Fversion-3D1-26modificationDate-3D1569963225000-26api-3Dv2&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=GU7oC_LaBo7KvH3LCTYNBb2Z62O2_gB7PePpFA2YNvE&s=PKnCPcJaP-hGDv7k41qSJp4G-vUa7kFbgWNfm3FAImo&e=">1
Oct 2019</a>) <o:p></o:p></span></p>
<p class="xmsonormal"><b><i><span lang="EN-US"> </span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Q1: Close discussion.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">Q2: Proposal from Martin Pablo Silva Valent:<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- TMCH should educate rights holders; it is already doing outreach and should do more.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Needs to be revised to be in the form of a recommendation.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Amendment: this effort would work in conjunction with whatever marketing ICANN is doing to support knowledge around new gTLD program in general and the TMCH.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Not clear as drafting what is the remit of Deloitte and what falls elsewhere. Some of this should be done at an ICANN level.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Not sure involving ICANN at this level is required.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- ICANN is not involved in marketing gTLDs.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Needs to be some definition/scope. Don’t see TMCH providing education on RPMs. We also need to clarify what is meant by “education.” Is this essentially “awareness” or is something more contemplated?<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- In the end we need much more in terms of education. If it’s not in the current contract then it’s worth considering in future discussion.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Need to be careful how to express this.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- From staff: ICANN Org does not have control over the TMCH provider’s website and information. The contract was an initial 5-year term that expired on the first anniversary of the entering into force of the new gTLD
program, and followed by consecutive 1-year renewal terms unless there’s a 180 day notice of termination. See:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pages_viewpage.action-3FpageId-3D61606864&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=GU7oC_LaBo7KvH3LCTYNBb2Z62O2_gB7PePpFA2YNvE&s=9vB4Yvqqu-gSbuPEj2gY7ATdZdok63vjBBtw77AvqOA&e=">
https://community.icann.org/pages/viewpage.action?pageId=61606864</a> . We are in the 1-year renewal term.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Should look at what Deloitte already provides on their website.
<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- There's a lot of talk about what should be done - but no-one identifying anything actually glaringly missing.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Maybe it’s more of an outreach question, if the education already exists.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- We should be identifying what’s not being done. Otherwise, we’re just endorsing education conceptually, or providing a generic roadmap for what could be done that will include many things that are already being done.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">ACTION: Martin to revise the proposal with assistance of other WG members and circulate it on the WG email list for review.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">ACTION: Staff will check to see if either party to the contract can seek modifications.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">4. Discussion of whether individual URS proposals should be revisited by the WG, and methodology for doing so. See the draft survey at: <span class="xapple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__forms.gle_kak3MEWFTNeq69wN9&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=36glY4CKyg4JCvpnCKFaXpx9PW_r5RObgdpcO0mtVM8&s=pEK5aTpdV-IIoTgVC0PHNGEZ969HY26RoiVzAAphdcw&e=">survey
[forms.gle]</a>:<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Survey does not designate which proposals go into the Initial Report – that will be decided via WG discussion.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- WG members should consider whether or not names and affiliations should be included, although the survey is not a poll.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- WG members will decide what to do with the data.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">-- Co-Chairs suggest allowing WG members to take the survey as a way to inform, but not direct, WG discussions.<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US">ACTION: WG members are requested to continue discussion on the email list.
<o:p></o:p></span></p>
<p class="xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<pre><span lang="EN-US">_______________________________________________<o:p></o:p></span></pre>
<pre><span lang="EN-US"><o:p> </o:p></span></pre>
<pre><span lang="EN-US">GNSO-RPM-WG mailing list<o:p></o:p></span></pre>
<pre><span lang="EN-US"><o:p> </o:p></span></pre>
<pre><span lang="EN-US"><a href="mailto:GNSO-RPM-WG@icann.org">GNSO-RPM-WG@icann.org</a><o:p></o:p></span></pre>
<pre><span lang="EN-US"><o:p> </o:p></span></pre>
<pre><span lang="EN-US"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drpm-2Dwg&d=DwMDaQ&c=qmi9WrYRGQEDDOxOwKrAjW7mWovpzN_EKyRbeK_zbP0&r=Kepk-9GEB6JgOj0vUGl8c0hdrRM7FW-8Is-VAQU1VAk&m=6PdODCxx0pFS_O8Ct151GXBvBolgy6QESpwRhpAInzE&s=8FH-5Lm9_iyYjpspSNzAt2dOVuvjvZ2kyCIQh2x7n9Y&e=">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><o:p></o:p></span></pre>
<pre><span lang="EN-US"><o:p> </o:p></span></pre>
<pre><span lang="EN-US">_______________________________________________<o:p></o:p></span></pre>
<pre><span lang="EN-US"><o:p> </o:p></span></pre>
<pre><span lang="EN-US">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMDaQ&c=qmi9WrYRGQEDDOxOwKrAjW7mWovpzN_EKyRbeK_zbP0&r=Kepk-9GEB6JgOj0vUGl8c0hdrRM7FW-8Is-VAQU1VAk&m=6PdODCxx0pFS_O8Ct151GXBvBolgy6QESpwRhpAInzE&s=j15WQS8Bnm8KeBCSUJPlw5Hdbmvws-gnr_af0NTo1s4&e=">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMDaQ&c=qmi9WrYRGQEDDOxOwKrAjW7mWovpzN_EKyRbeK_zbP0&r=Kepk-9GEB6JgOj0vUGl8c0hdrRM7FW-8Is-VAQU1VAk&m=6PdODCxx0pFS_O8Ct151GXBvBolgy6QESpwRhpAInzE&s=nykW72AfYIBMd5943mKpT4hvlgo8SdVQo0ChyyJJz_w&e=">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></span></pre>
</blockquote>
<p class="MsoNormal"><span lang="EN-US" style="color:windowtext"><br>
<br>
<o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:7.5pt">Confidentiality Notice <br>
<br>
This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee,
you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies
of this message. <o:p></o:p></span></p>
</div>
</body>
</html>