<div dir="ltr"><div><font color="#073763" face="verdana,sans-serif">Paul T.,</font></div><div><font face="verdana,sans-serif"><br><font color="#073763"></font></font></div><div><font color="#073763" face="verdana,sans-serif">Since things were moving so fast over the past month - Yes, when I get some time later this week, I would be happy to draft a summation of my proposal on Q8.</font></div><div><br></div><div><font color="#073763" face="verdana,sans-serif">The summary will be helpful for overall WG transparency purposes, and can be utilized by staff / the co-chairs for the purposes of the initial report drafting; and potentially further consensus-building, as I recall Rebecca had a question or two that she sent to the list after I posted the official transcript from ICANN43 with the confirmation of the meaning of 3.4.2 from ICANN's General Counsel.</font></div><div><font color="#073763" face="verdana,sans-serif"><br></font></div><div><font color="#073763" face="verdana,sans-serif">Thanks for everyone's ongoing hard work and perseverance in this PDP.</font></div><div><font color="#073763" face="verdana,sans-serif"><br></font></div><div><font color="#073763" face="verdana,sans-serif">Best regards,</font></div><div><font color="#073763" face="verdana,sans-serif">Claudio</font><br></div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Fri, Oct 18, 2019 at 4:00 PM Paul Tattersfield <<a href="mailto:gpmgroup@gmail.com" target="_blank">gpmgroup@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div dir="ltr"><div dir="ltr"><div dir="ltr"><span lang="EN-GB" style="font-family:Calibri;font-size:11pt">It
would seem to me it is within the WG mandate unless the WG removes 3.2.4. If
3.2.4 remains and 3.2.4 doesn’t flow to the 7.1 (claims) and 7.2 (sunrise) I
don’t see why if the RO’s want to enter into agreements the TMCH that benefit multiple
RO’s we should intervene.<br>
<br>
However in the absence of further comment I remain concerned about the other
proposal. Claudio, do you have a latest draft of your proposal you can share?</span></div></div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Fri, Oct 18, 2019 at 8:33 PM claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div dir="ltr"><div dir="ltr"><div>Paul K.,</div><div><br></div><div>At a high level, the review of the TMCH is in our charter and the associated provisions in the AGB about eligible types of IP, and under what form of law, or how they are to be processed therein, is all appropriately under our remit; hence the informed discussions we've been having since time eternal. </div><div><br></div><div>For example, examining issues regarding the treatment or protection of Geographic Indications/Appellations of Origin are specifically mentioned in our charter for review.</div><div><br></div><div>What is not under our remit is creating rules for registries or registrars to follow in terms of their voluntary RPMs, in other words how they should be designed and issues along those lines - yes those are out of scope.</div><div><br></div><div>Hope that helps.</div><div><br></div><div>Cheers,</div><div>Claudio <br></div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Fri, Oct 18, 2019 at 3:11 PM Paul Keating <<a href="mailto:paul@law.es" target="_blank">paul@law.es</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div dir="auto">So beyond the advertisement for Deloitte, it’s purely voluntary and thus outside of the WG mandate imho. <div><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On 18 Oct 2019, at 16:58, claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div>Paul K.,</div><div><br></div><div>Great question.</div><div><br></div>The answer is for registry-specific (voluntary RPMs), that every registry operator is able to set up for allocating domain names in a manner: <div><br></div><div>1) consist with the local laws of the registry operator; and;</div><div><br></div><div>2) to minimize abuse and to help create a safe, trusted namespace for Internet users, IP owners, registrants - both commercial and non-commercial.</div><div><br></div><div>This is a win-win for everyone because it helps promote a successful new gTLD program, where domains can be registered for commerce and free expression.<br><div><br></div><div>Some of these voluntary RPMs are already established in the ICANN system, such as the Limited Registration Period, which takes place after the Sunrise period is over, at the sole discretion of the registry operator.</div><div><br></div><div>Registries can also build other mechanisms if they so desire under the New gTLD Registry Agreement, that rely upon or leverage the TMCH, if so desired and approved by the registry and TMCH Operator.</div><div><br></div><div>As we know, the TMCH simply functions as the administrative/technical system that supports the various mechanisms that registries 1) are required under the contract to implement, like Sunrise; or 2) voluntary mechanisms that the contract permits them to create, which go above the ICANN-mandated “floor” so to speak.</div><div><br></div><div>For example on the latter use-case, from recollection I believe Google runs a permanent Claims notice for their new gTLDs (it doesn’t end after 90-days). <br></div><div><br></div><div>I don’t recall off-hand the specific section, but this is part of the existing Applicant Guidebook and Registry Agreement; the TMCH was designed to allow other forms of IP (non-trademarks) to be recorded under 3.2.4, but expressly states that 3.2.4 is only for registry-specific consumer protection measures, i.e. not for Sunrise or TM Claims which are limited to trademarks.</div><div><br></div><div>The TMCH Operator (Deloitte and IBM) are premier companies in their space and have the know how/capacity to implement these rules; and anyway, we know it’s not that complex from a technical level to parse database records out for varying forms of use.</div><div><br></div><div>Hope helpful, please let me know of questions/comments. Thanks!</div><div><br></div><div>Best regards,</div><div>Claudio</div><div><div><div><div><br>On Friday, October 18, 2019, Paul Keating <<a href="mailto:paul@law.es" target="_blank">paul@law.es</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div dir="auto">If they are not part of the sunrise/notice program, what is their relevance and why are they being dealt with in an ICANN situation?<br><br><div dir="ltr">Sent while on the run.</div><div dir="ltr"><br>On 17 Oct 2019, at 01:05, Tushnet, Rebecca <<a href="mailto:rtushnet@law.harvard.edu" target="_blank">rtushnet@law.harvard.edu</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">
<div style="color:rgb(0,0,0);font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt">
There has been a lot of conflating of the TMCH database with the TMCH as entity that might also run ancillary databases/services. My proposal deals with this by making clear that GIs can be in a database (or multiple databases), including one(s) run by Deloitte,
but not the one that's used to run Sunrise/Notice. I think this adequately addresses your concern that GIs be allowed in some database while minimizing the chance of error. The difference between us seems to me to be that you want "the database" to include
both Sunrise/Notice-eligible marks and also non-Sunrise/Notice-eligible terms. I think it makes more sense to be very clear about the difference in the rules, although we need not specify any technical back end. </div>
<div style="color:rgb(0,0,0);font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt">
<br>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt">
The reason I thought we were satisfied as a group is that I do not think there is a material difference between these proposals once we adequately specify the difference between the TMCH as entity and TMCH database as the thing used to provide Sunrise and Notice--which,
at present, is the only thing it does, as it doesn't seem that Deloitte has offered any separate services as yet. Claudio, since I believe that you agree that GIs shouldn't get Sunrise and Notice, why should they be in the database used to provide Sunrise
and Notice? </div>
<div style="color:rgb(0,0,0);font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt">
<br>
</div>
<div>
<div style="font-family:Tahoma;font-size:13px">
<div style="font-family:Tahoma;font-size:13px">
<div><br>
</div>
Rebecca Tushnet</div>
<div style="font-family:Tahoma;font-size:13px">Frank Stanton Professor of First Amendment Law, Harvard Law School<br>
703 593 6759 </div>
</div>
</div>
<div></div>
<hr style="width:98%;display:inline-block">
<div dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size:11pt"><b>From:</b> GNSO-RPM-WG <<a href="mailto:gnso-rpm-wg-bounces@icann.org" target="_blank">gnso-rpm-wg-bounces@icann.org</a>> on behalf of claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>><br>
<b>Sent:</b> Wednesday, October 16, 2019 6:42 PM<br>
<b>To:</b> Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>><br>
<b>Cc:</b> <a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a> <<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>><br>
<b>Subject:</b> [GNSO-RPM-WG] Actions & Notes: RPM PDP WG Meeting 16 October 2019</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div><font color="#073763" face="verdana,sans-serif">Julie, all,</font></div>
<div><font color="#073763" face="Verdana"><br>
</font></div>
<div><font color="#073763" face="Verdana">Thanks for sending this around.</font></div>
<div><font color="#073763" face="verdana,sans-serif"><br>
</font></div>
<div><font color="#073763" face="verdana,sans-serif">Unfortunately, this document does not represent the consensus of the small group (I'm sorry to say) in several important areas.</font></div>
<div><font color="#073763" face="verdana,sans-serif"><br>
</font></div>
<div><font color="#073763" face="verdana,sans-serif">For example, this document includes language that states that GIs must be removed from the TMCH, which we did not agree upon in the small group.
</font></div>
<div><font color="#073763" face="verdana,sans-serif"><br>
</font></div>
<div><font color="#073763" face="verdana,sans-serif">To illustrate why they should not be removed, I circulated the transcript from ICANN43, which clearly demonstrates that 3.2.4 "Other marks that constitute IP" was intended to include other IP (non-trademarks)
for the purpose of voluntary registry-specific RPMs. </font></div>
<div><font color="#073763" face="verdana,sans-serif"><br>
</font></div>
<div><font color="#073763" face="verdana,sans-serif">The mandatory RPMs were intended to be the floor, not the ceiling, and the TMCH can be used to support the voluntary RPMs, and GIs can be recorded in the TMCH under 3.2.4</font></div>
<div><font color="#073763" face="Verdana"><br>
</font></div>
<div><font color="#073763" face="Verdana">The transcript reflects community comments and confirmation from ICANN's General Counsel that this is the purpose and intent of 3.2.4; therefore, GIs are properly recordable in the TMCH, but only for the purposes of
voluntary registry-specific RPMs, and should not be removed from the database.</font></div>
<div><font color="#073763" face="Verdana"><br>
</font></div>
<div><font color="#073763" face="Verdana">There is additional language in this document that forms part of Rebecca’s proposal that I did not agree to. </font></div>
<div><font color="#073763" face="Verdana"><br>
</font></div>
<div><font color="#073763" face="Verdana">As you may recall at the time, I suggested we extent the time allotted to the small group to continue working in the background, but my suggestion was rejected - that’s how or why we ended up in this spot.</font></div>
<div><font color="#073763" face="Verdana"><br>
</font></div>
<div><font color="#073763" face="Verdana">Best,</font></div>
<div><font color="#073763" face="Verdana">Claudio</font></div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div>
<div dir="ltr">On Wed, Oct 16, 2019 at 5:50 PM Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div lang="EN-US">
<div>
<p>Paul,<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Apologies for any confusion, but it also is the staff’s understanding – and evidently this is not clearly conveyed – that the support on the call earlier today was for the small group proposal, rather than an individual proposal. While
it was identified as a proposal from Rebecca, the reference was to the version she submitted on
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_109482780_Rebecca-2520Tushnet-2520Proposal-2520-2D-2520Q8-2520-2D-252010-2520Oct-25202019.pdf-3Fversion-3D1-26modificationDate-3D1570726064000-26api-3Dv2&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=TTiRUNcHancDG25EHZlgZ0NcoWSHqYswk83501fN1ts&s=h-YGB64igxNLOyvyIrdJLhRzDfiQ_0jqQArTCmsrYLU&e=" target="_blank">
10 October</a> (not her original proposal submitted on 01 October) after engaging with the small group, which staff thus thought represented the agreement of the small group.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Claudio’s subsequent message after reviewing the recording from 10 October provides some helpful detail in this matter.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Kind regards,<u></u><u></u></p>
<p>Julie<u></u><u></u></p>
<p><u></u> <u></u></p>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in">
<p><b><span style="color:black;font-size:12pt">From: </span>
</b><span style="color:black;font-size:12pt">Paul Tattersfield <<a href="mailto:gpmgroup@gmail.com" target="_blank">gpmgroup@gmail.com</a>><br>
<b>Date: </b>Wednesday, October 16, 2019 at 5:42 PM<br>
<b>To: </b>claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>><br>
<b>Cc: </b>Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>>, "<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>" <<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>><br>
<b>Subject: </b>[Ext] Re: [GNSO-RPM-WG] Actions & Notes: RPM PDP WG Meeting 16 October 2019<u></u><u></u></span></p>
</div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<div>
<p><span lang="EN-GB" style="font-size:12pt">I share your concerns Claudio, I was under the impression that the request for support on the call earlier today was for a final proposal after agreement had been sought from the whole of the
small group rather than just an individual proposal, very disappointing.<br>
<br>
I trust there will be a way of including Claudio’s proposals in the initial report.
<br>
<br>
I’m fine with discussing 6ter marks after/during the comments, though I think given the importance of the marks involved at a very minimum those responsible for the final proposal should as a matter of courtesy:
<br>
<br>
(1) if there are any changes to today’s approved proposal, publish the final proposal wording to the working group list.<br>
<br>
(2) explain under which section any proposal places a mark such as ‘UNHCR’? <br>
<br>
Thanks, Paul</span><u></u><u></u></p>
</div>
</div>
<p><u></u> <u></u></p>
<div>
<div>
<p>On Wed, Oct 16, 2019 at 9:56 PM claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-width:medium medium medium 1pt;border-style:none none none solid;border-color:currentColor currentColor currentColor rgb(204,204,204);padding:0in 0in 0in 6pt;margin-right:0in;margin-left:4.8pt">
<p>Im not blaming staff Julie, so no worries. <u></u><u></u></p>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p>Since the WG was not able to reach resolution, we formed a small group - with Rebecca and I being the only active participants - to flesh out the issues, which generated Rebecca’s proposal and my proposal.<u></u><u></u></p>
</div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p>Once that process concluded, we did not allocate time discussing those areas of divergence in order to reach compromise or consensus - please review the transcripts for confirmation of this fact.<u></u><u></u></p>
</div>
<div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p>We also didn’t conclude the WG’s views or treatment of 3.2.4 on the last meeting, which the transcript will also clearly reflect. That is why I sent the email today of the transcript of the ICANN Meeting when 3.2.4 was discussed, which
contained the affirmation of ICANN’s General Counsel on this specific issue. <u></u><u></u></p>
</div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p>We also did not conclude discussions on the list on specific working on 3.2.3., but there is high level agreement on the treatment of certain names during TM Claims and Sunrise.<u></u><u></u></p>
</div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p>In either case, Action item #8 needs be updated to include the publication of my proposal in the initial report. There are important areas of divergence that require public comment and there was sufficient support expressed for doing
so. It’s as simple as that, so I hope there is no controversy involved here.<u></u><u></u></p>
</div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p>Thanks!<u></u><u></u></p>
</div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p>Best regards,<u></u><u></u></p>
</div>
<div>
<p>Claudio<u></u><u></u></p>
</div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<div>
<div>
<p><u></u> <u></u></p>
</div>
<div>
<p><br>
On Wednesday, October 16, 2019, Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>> wrote:<u></u><u></u></p>
<blockquote style="border-width:medium medium medium 1pt;border-style:none none none solid;border-color:currentColor currentColor currentColor rgb(204,204,204);padding:0in 0in 0in 6pt;margin-right:0in;margin-left:4.8pt">
<div>
<div>
<p>With apologies Claudio, but staff had not seen that you indicated that you would be joining late today, thus the agenda was followed in its original order. Also, Q8 was discussed on the call on 10 October and based on that discussion
it was deemed that no further discussion was necessary on today’s call.<u></u><u></u></p>
<p> <u></u><u></u></p>
<p>Staff will review the transcripts and recording for the meeting on 10 October to ensure that the results of the discussions are accurately reflected.<u></u><u></u></p>
<p> <u></u><u></u></p>
<p>Kind regards,<u></u><u></u></p>
<p>Julie<u></u><u></u></p>
<p> <u></u><u></u></p>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:windowtext currentColor currentColor;padding:3pt 0in 0in">
<p><b><span style="color:black;font-size:12pt">From: </span>
</b><span style="color:black;font-size:12pt">claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>><br>
<b>Date: </b>Wednesday, October 16, 2019 at 4:26 PM<br>
<b>To: </b>Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>><br>
<b>Cc: </b>"<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>" <<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>><br>
<b>Subject: </b>[Ext] Re: [GNSO-RPM-WG] Actions & Notes: RPM PDP WG Meeting 16 October 2019</span><u></u><u></u></p>
</div>
<div>
<p> <u></u><u></u></p>
</div>
<p>Action item 8 need to be modified to include publishing my proposal in the Initial Report based on the support expressed by various members throughout these discussions.
<u></u><u></u></p>
<div>
<p> <u></u><u></u></p>
</div>
<div>
<p>I sent a note to the list indicating that I was joining late. Frankly, I’m surprised and disappointed that after all the work that was done on this issue, this agenda item was discussed first on the agenda, without the involvement of
person who put in the work that was the basis of the agenda item. <u></u><u></u></p>
<div>
<p> <u></u><u></u></p>
</div>
<div>
<p>Mismanagement aside, please take the appropriate steps as outlined above. Thank you.<u></u><u></u></p>
</div>
<div>
<p> <u></u><u></u></p>
</div>
<div>
<p>Best regards,<u></u><u></u></p>
</div>
<div>
<p>Claudio<br>
<br>
On Wednesday, October 16, 2019, Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>> wrote:<u></u><u></u></p>
<blockquote style="border-width:medium medium medium 1pt;border-style:none none none solid;border-color:currentColor currentColor currentColor windowtext;margin:5pt 0in 5pt 4.8pt;padding:0in 0in 0in 6pt">
<div>
<div>
<p><span style="color:black">Dear All,</span><u></u><u></u></p>
<p style="word-spacing:0px"><span style="color:black"> </span><u></u><u></u></p>
<p style="word-spacing:0px"><span style="color:black">Please see below the action items captured by staff from the </span>RPM PDP Working Group<span style="color:black"> call held on</span> 16 October 2019 at 17:00 UTC<span style="color:black">.
Staff </span>will post<span style="color:black"> these to the wiki space. <b><i>Please note that these
</i></b></span><b><i>are<span style="color:black"> high-level notes and are not meant as a substitute for the recording</span>, chat room, or transcript</i></b><i><span style="color:black">.</span></i><span style="color:black"> The recording, Zoom chat,</span>
transcript<span style="color:black"> and attendance records are posted on the wiki at</span>:
<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=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=TTiRUNcHancDG25EHZlgZ0NcoWSHqYswk83501fN1ts&s=R83fbvI-Q57WQK0k__EK5m6yMNXDF8bk9TL0raE-_8s&e=" target="_blank">
https://community.icann.org/display/RARPMRIAGPWG/2019-10-16+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG</a>.
<u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="color:black">Best Regards,</span><u></u><u></u></p>
<p style="word-spacing:0px">Julie<u></u><u></u></p>
<p style="word-spacing:0px">Julie Hedlund, Policy Director<u></u><u></u></p>
<p><span style="font-family:"Arial",sans-serif;font-size:10pt"> </span><u></u><u></u></p>
<p><span style="font-family:"Arial",sans-serif;font-size:10pt">==</span><u></u><u></u></p>
<p><span style="font-family:"Arial",sans-serif;font-size:10pt"> </span><u></u><u></u></p>
<p><b>NOTES & ACTION ITEMS</b><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><b><span style="color:black">Actions:</span></b><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><b>Open and Deferred TMCH Questions:</b><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><u><span style="color:black">Q7 Design Marks</span></u><span style="color:black">: ACTION: WG agrees to publish Kleiman/Muscovitch and Shatan proposals in the Initial Report for Public Comment.</span><u></u><u></u></p>
<p><u><span style="color:black">Q8 GIs: ACTION</span></u><span style="color:black">: WG agrees to publish Tushnet proposal in the Initial Report for Public Comment.</span><u></u><u></u></p>
<p><u><span style="color:black">Q12</span></u><span style="color:black">: 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.</span><u></u><u></u></p>
<p><u><span style="color:black">Q15</span></u><span style="color:black">: 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.</span><u></u><u></u></p>
<p><u><span style="color:black">Q2</span></u><span style="color:black">: 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.</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><b><span style="color:black">Discussion of whether individual URS proposals should be revisited by the WG, and methodology for doing so: </span></b><span style="color:black">ACTION: WG members are requested to continue discussion on
the email list. See the draft survey at: <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=" target="_blank">survey
[forms.gle]</a>.</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><b>Notes:</b><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="color:black">1. Updates to Statements of Interest: No updates provided.</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><span style="color:black">2. Status of Questions Q7, Q8, Q12, and Q15:</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><span style="color:black">Q7 Design Marks: ACTION: WG agrees to publish Kleiman/Muscovitch and Shatan proposals in the Initial Report for Public Comment.</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><span style="color:black">Q8 GIs: ACTION: WG agrees to publish Tushnet proposal in the Initial Report for Public Comment.</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><span style="color:black">Q12: Proposal from Maxim Alzoba – TMCH Operational Considerations</span><u></u><u></u></p>
<p><span style="color:black">-- Need to improve redundancy and availability of the TMCH.</span><u></u><u></u></p>
<p><span style="color:black">-- 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.</span><u></u><u></u></p>
<p><span style="color:black">-- 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.</span><u></u><u></u></p>
<p><span style="color:black">-- 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=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=TTiRUNcHancDG25EHZlgZ0NcoWSHqYswk83501fN1ts&s=2hfgDnGz7dpxe0fwAhjF8xwU2pKjGR6cuaiYcVLLHtM&e=" target="_blank">
https://community.icann.org/pages/viewpage.action?pageId=61606864</a></span><span style="color:black;font-family:"MS Gothic"">
</span><u></u><u></u></p>
<p><span style="color:black">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.</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><span style="color:black">Q15: ACTION: WG agrees to publish Karanicolas proposal in the Initial Report for Public Comment.</span><u></u><u></u></p>
<p><span style="color:black">-- Hoped that we could get consensus.
</span><u></u><u></u></p>
<p><span style="color:black">-- 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.</span><u></u><u></u></p>
<p><span style="color:black">-- 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)?</span><u></u><u></u></p>
<p><span style="color:black">ACTION: Staff to draft a new proposal based on suggestions and circulate it to interested WG members and the Co-Chairs.</span><u></u><u></u></p>
<p><span style="color:black;font-size:12pt"> </span><u></u><u></u></p>
<p><span style="color:black">3. Remaining Deferred Charter Questions (see the attached Status of WG Discussions on Agreed TMCH Charter Questions):</span><u></u><u></u></p>
<p><b><i><span style="color:black"> </span></i></b><u></u><u></u></p>
<p><b><i><span style="color:black">a. Close Discussion:</span></i></b><span style="color:black"> TMCH Category 6: Balance: Charter Question 16: Close discussion.</span><u></u><u></u></p>
<p><span style="color:black;font-size:12pt"> </span><u></u><u></u></p>
<p><b><i><span style="color:black">b. Discussion:</span></i></b><span style="color:black"> 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=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=TTiRUNcHancDG25EHZlgZ0NcoWSHqYswk83501fN1ts&s=hNmT7AsTaYqVRZM6iMCKscr3EuNWrO7JJ4x_NDgLpcE&e=" target="_blank">1
Oct 2019</a>) </span><u></u><u></u></p>
<p><b><i><span style="color:black"> </span></i></b><u></u><u></u></p>
<p><span style="color:black">Q1: Close discussion.</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><span style="color:black">Q2: Proposal from Martin Pablo Silva Valent:</span><u></u><u></u></p>
<p><span style="color:black">-- TMCH should educate rights holders; it is already doing outreach and should do more.</span><u></u><u></u></p>
<p><span style="color:black">-- Needs to be revised to be in the form of a recommendation.</span><u></u><u></u></p>
<p><span style="color:black">-- 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.</span><u></u><u></u></p>
<p><span style="color:black">-- Not clear as drafting what is the remit of Deloitte and what falls elsewhere. Some of this should be done at an ICANN level.</span><u></u><u></u></p>
<p><span style="color:black">-- Not sure involving ICANN at this level is required.</span><u></u><u></u></p>
<p><span style="color:black">-- ICANN is not involved in marketing gTLDs.</span><u></u><u></u></p>
<p><span style="color:black">-- 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?</span><u></u><u></u></p>
<p><span style="color:black">-- 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.</span><u></u><u></u></p>
<p><span style="color:black">-- Need to be careful how to express this.</span><u></u><u></u></p>
<p><span style="color:black">-- 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=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=TTiRUNcHancDG25EHZlgZ0NcoWSHqYswk83501fN1ts&s=2hfgDnGz7dpxe0fwAhjF8xwU2pKjGR6cuaiYcVLLHtM&e=" target="_blank">
https://community.icann.org/pages/viewpage.action?pageId=61606864</a> . We are in the 1-year renewal term.</span><u></u><u></u></p>
<p><span style="color:black">-- Should look at what Deloitte already provides on their website.
</span><u></u><u></u></p>
<p><span style="color:black">-- There's a lot of talk about what should be done - but no-one identifying anything actually glaringly missing.</span><u></u><u></u></p>
<p><span style="color:black">-- Maybe it’s more of an outreach question, if the education already exists.</span><u></u><u></u></p>
<p><span style="color:black">-- 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.</span><u></u><u></u></p>
<p><span style="color:black">ACTION: Martin to revise the proposal with assistance of other WG members and circulate it on the WG email list for review.</span><u></u><u></u></p>
<p><span style="color:black">ACTION: Staff will check to see if either party to the contract can seek modifications.</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><span style="color:black">4. Discussion of whether individual URS proposals should be revisited by the WG, and methodology for doing so. See the draft survey at: <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=" target="_blank">survey
[forms.gle]</a>:</span><u></u><u></u></p>
<p><span style="color:black"> </span><u></u><u></u></p>
<p><span style="color:black">-- Survey does not designate which proposals go into the Initial Report – that will be decided via WG discussion.</span><u></u><u></u></p>
<p><span style="color:black">-- WG members should consider whether or not names and affiliations should be included, although the survey is not a poll.</span><u></u><u></u></p>
<p><span style="color:black">-- WG members will decide what to do with the data.</span><u></u><u></u></p>
<p><span style="color:black">-- Co-Chairs suggest allowing WG members to take the survey as a way to inform, but not direct, WG discussions.</span><u></u><u></u></p>
<p><span style="color:black">ACTION: WG members are requested to continue discussion on the email list.
</span><u></u><u></u></p>
<p> <u></u><u></u></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<p>_______________________________________________<br>
GNSO-RPM-WG mailing list<br>
<a href="mailto:GNSO-RPM-WG@icann.org" target="_blank">GNSO-RPM-WG@icann.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drpm-2Dwg&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=TTiRUNcHancDG25EHZlgZ0NcoWSHqYswk83501fN1ts&s=gLklLCmQ9CrX0IIhLh-aHOhTTQSKINfHa0epimXml2s&e=" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
_______________________________________________<br>
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=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=V14dND_NlbDkts6UqGxY9-Oiv1Am0AYJlx1aPO6h3T4&s=9qNruu4DKSe937u1utyaHLXLBL7nvxK8FforPwQZ-P8&e=" target="_blank">https://www.icann.org/privacy/policy
[icann.org]</a>) and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=V14dND_NlbDkts6UqGxY9-Oiv1Am0AYJlx1aPO6h3T4&s=JlO3C-ftcwbUbwcwy4D9ZrGwH1TyDoctxR9I7kAThXc&e=" target="_blank">https://www.icann.org/privacy/tos
[icann.org]</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.<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div></blockquote></div></blockquote></div></div></div></div></div>
</div></blockquote></div></div></blockquote></div></div>
_______________________________________________<br>
GNSO-RPM-WG mailing list<br>
<a href="mailto:GNSO-RPM-WG@icann.org" target="_blank">GNSO-RPM-WG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
_______________________________________________<br>
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://www.icann.org/privacy/policy" target="_blank" rel="noreferrer">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank" rel="noreferrer">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.</blockquote></div>
</blockquote></div>