I’m not sure what I missed and I’ll listen to the recording; as per ICANN practice, agreements aren’t just reached by who is on particular call - it needs to include input from members on the list who missed the call. <div><br></div><div>I’m fine with parking this until after initial report is published, but we didn’t reconcile some open questions and they require further work at some point.<br><br>On Wednesday, October 16, 2019, claudio di gangi <<a href="mailto:ipcdigangi@gmail.com">ipcdigangi@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I missed the first ten minutes of the call. It’s not clear to me what final language was settled upon, can someone clarify this?<div><br></div><div>Thanks <br><div><br></div><div>Best regards,<div>Claudio</div><div><br>On Wednesday, October 16, 2019, Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Correct Rebecca. Per the WG agreement on the call today, this item is closed.<br>
<br>
Best,<br>
Julie<br>
<br>
On 10/16/19, 3:41 PM, "GNSO-RPM-WG on behalf of Tushnet, Rebecca" <<a href="mailto:gnso-rpm-wg-bounces@icann.org" target="_blank">gnso-rpm-wg-bounces@icann.org</a> on behalf of <a href="mailto:rtushnet@law.harvard.edu" target="_blank">rtushnet@law.harvard.edu</a>> wrote:<br>
<br>
My understanding was that this was closed per our discussion on the call. Can Chairs or staff provide guidance? Claudio’s message came in during the call for me. <br>
<br>
Rebecca Tushnet<br>
Frank Stanton Professor of First Amendment Law, Harvard Law School<br>
<br>
Sent from my phone. Apologies for terseness/typos. <br>
<br>
> On Oct 16, 2019, at 1:43 PM, Paul Tattersfield <<a href="mailto:gpmgroup@gmail.com" target="_blank">gpmgroup@gmail.com</a>> wrote:<br>
> <br>
> Claudio, Thank you for the archive link. Under Rebecca’s and your<br>
> proposal, including these latest thoughts on section 3.2.4, which<br>
> section do you feel a mark like UNHCR would be entered in under the<br>
> proposal/recommendation?<br>
> <br>
>> On 10/16/19, claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>> wrote:<br>
>> All,<br>
>> <br>
>> I am very happy that ICANN is transparent and transcribes is meetings,<br>
>> which is particularly essential in this fluid and complex environment.<br>
>> <br>
>> Since I was involved in the ICANN committee that developed the proposal for<br>
>> the Trademark Clearinghouse, which was called the IP Clearinghouse, I have<br>
>> known from the start that the concept of allowing other forms of IP in the<br>
>> Clearinghouse was always part of the concept, because there was always<br>
>> broad agreement that the ICANN-imposed Mandatory RPMs, were the ceiling and<br>
>> not the floor.<br>
>> <br>
>> The new gTLD Registry controls the allocation of all domain names within<br>
>> its TLD, and can therefore establish voluntary mechanisms, consistent with<br>
>> local laws, to protect consumers from confusion and harm from malicious<br>
>> actors.<br>
>> <br>
>> Since the Clearinghouse database is just an administrative tool to support<br>
>> the implementation of these mechanisms, both mandatory and voluntary, there<br>
>> was never a reason to exclude certain forms of IP in the Clearinghouse for<br>
>> the sole purpose of supporting the voluntary RPMS that a specific Registry<br>
>> may adopt.<br>
>> <br>
>> We have reached consensus on this point, in particular through the<br>
>> ancillary database concept, but have gotten snagged on the wording of<br>
>> particular provisions, including 3.2.3 and 3.2.4<br>
>> <br>
>> Section 3.2.4 currently states: "Other marks that constitute intellectual<br>
>> property" - and this category: 3.2.4 - is NOT for the mandatory Sunrise or<br>
>> Claims period, but for voluntary registry-specific RPMs.<br>
>> <br>
>> I located the transcript from the ICANN meeting when the Applicant<br>
>> Guidebook was essentially completed; it had reach the near final stage.<br>
>> <br>
>> 3.2.4 was specifically discussing during this meeting; the confusion with<br>
>> the language was identified (and it was even predicted that it was going to<br>
>> cause confusion) and ICANN staff and General Counsel agreed that 3.2.4<br>
>> extended to other forms of IP beyond trademarks. In other words, we have<br>
>> been confused on this clause simply because of imprecise drafting of this<br>
>> provision.<br>
>> <br>
>> Please see the transcript here: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.icann.org_en_&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=dMQQGBWfWo48zFbvOyLacmM0-clVWIm-GBUZA-g1PQ0&s=JxrlTJQ81REjQU12K21t83qqhIWNXo70RXqH8jzRNtQ&e=" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__archive<wbr>.icann.org_en_&d=DwIGaQ&c=FmY1<wbr>u3PJp6wrcrwll3mSVzgfkbPSS6sJms<wbr>7xcl4I5cM&r=adDIs0WEx_lLwFfrsd<wbr>ovxTYY8GkRHo5ibc8SR3Npdh8&m=dM<wbr>QQGBWfWo48zFbvOyLacmM0-clVWIm-<wbr>GBUZA-g1PQ0&s=JxrlTJQ81REjQU12<wbr>K21t83qqhIWNXo70RXqH8jzRNtQ&e=</a> <br>
>> meetings/singapore2011/bitcach<wbr>e/Trademark%20Clearinghouse%20<wbr>Implementation%20Plan-vid=2600<wbr>5&disposition=attachment&op=<wbr>download.txt<br>
>> <br>
>> I am quoting the relevant section:<br>
>> <br>
>> "J. Scott Evans: Another comment to Amy. Amy, I think that the guidebook's<br>
>> use of "other marks" confusing, and that needs to be changed to "other<br>
>> indicia," because we're already talking about marks in trademarks, and if<br>
>> you just make that<br>
>> one change, because I think the idea is there are other indicia other than<br>
>> trademarks that might be protected by the local registry, and we just need<br>
>> to make that clear. Because I think there's some confusion, well, if<br>
>> trademarks are here, what are other marks.<br>
>> <br>
>>>> AMY STATHOS: Right. And with respect to the assignment issue, sometimes<br>
>> the database that has the assignment documents may be different than the<br>
>> actual database that has the actual registration, so looks like it's<br>
>> something that --<br>
>> <br>
>> -------<br>
>> <br>
>> So 3.2.4. was always intended to allow other forms of IP to be recorded in<br>
>> the main TMCH database for implementation of voluntary Registry-specific<br>
>> voluntary RPMs. I hope this closes the debate on 3.2.4. and here is my<br>
>> proposed modification to bring clarity to its meaning:<br>
>> <br>
>> "3.2.4 Other Signs or Indicia that constitute intellectual property"<br>
>> <br>
>> Best regards,<br>
>> Claudio<br>
>> <br>
> ______________________________<wbr>_________________<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">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rpm-wg</a><br>
> ______________________________<wbr>_________________<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=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=dMQQGBWfWo48zFbvOyLacmM0-clVWIm-GBUZA-g1PQ0&s=Z4lUybf_C0oJ0kGG8iO2ckOHuHQh0vbmanznAZ6t7mI&e=" target="_blank">https://urldefense.proofpoint<wbr>.com/v2/url?u=https-3A__www.<wbr>icann.org_privacy_policy&d=<wbr>DwIGaQ&c=FmY1u3PJp6wrcrwll3mSV<wbr>zgfkbPSS6sJms7xcl4I5cM&r=<wbr>adDIs0WEx_lLwFfrsdovxTYY8GkRHo<wbr>5ibc8SR3Npdh8&m=dMQQGBWfWo48zF<wbr>bvOyLacmM0-clVWIm-GBUZA-g1PQ0&<wbr>s=Z4lUybf_C0oJ0kGG8iO2ckOHuHQh<wbr>0vbmanznAZ6t7mI&e=</a> ) and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=dMQQGBWfWo48zFbvOyLacmM0-clVWIm-GBUZA-g1PQ0&s=tvNM1mJDs6Z8kzHPkvGO5VT6P92qBIcnp3gNG2I3zzw&e=" target="_blank">https://urldefense.proofpoint<wbr>.com/v2/url?u=https-3A__www.<wbr>icann.org_privacy_tos&d=<wbr>DwIGaQ&c=FmY1u3PJp6wrcrwll3mSV<wbr>zgfkbPSS6sJms7xcl4I5cM&r=<wbr>adDIs0WEx_lLwFfrsdovxTYY8GkRHo<wbr>5ibc8SR3Npdh8&m=dMQQGBWfWo48zF<wbr>bvOyLacmM0-clVWIm-GBUZA-g1PQ0&<wbr>s=tvNM1mJDs6Z8kzHPkvGO5VT6P92q<wbr>BIcnp3gNG2I3zzw&e=</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.<br>
______________________________<wbr>_________________<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">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rpm-wg</a><br>
______________________________<wbr>_________________<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=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=dMQQGBWfWo48zFbvOyLacmM0-clVWIm-GBUZA-g1PQ0&s=Z4lUybf_C0oJ0kGG8iO2ckOHuHQh0vbmanznAZ6t7mI&e=" target="_blank">https://urldefense.proofpoint<wbr>.com/v2/url?u=https-3A__www.<wbr>icann.org_privacy_policy&d=<wbr>DwIGaQ&c=FmY1u3PJp6wrcrwll3mSV<wbr>zgfkbPSS6sJms7xcl4I5cM&r=<wbr>adDIs0WEx_lLwFfrsdovxTYY8GkRHo<wbr>5ibc8SR3Npdh8&m=dMQQGBWfWo48zF<wbr>bvOyLacmM0-clVWIm-GBUZA-g1PQ0&<wbr>s=Z4lUybf_C0oJ0kGG8iO2ckOHuHQh<wbr>0vbmanznAZ6t7mI&e=</a> ) and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=dMQQGBWfWo48zFbvOyLacmM0-clVWIm-GBUZA-g1PQ0&s=tvNM1mJDs6Z8kzHPkvGO5VT6P92qBIcnp3gNG2I3zzw&e=" target="_blank">https://urldefense.proofpoint<wbr>.com/v2/url?u=https-3A__www.<wbr>icann.org_privacy_tos&d=<wbr>DwIGaQ&c=FmY1u3PJp6wrcrwll3mSV<wbr>zgfkbPSS6sJms7xcl4I5cM&r=<wbr>adDIs0WEx_lLwFfrsdovxTYY8GkRHo<wbr>5ibc8SR3Npdh8&m=dMQQGBWfWo48zF<wbr>bvOyLacmM0-clVWIm-GBUZA-g1PQ0&<wbr>s=tvNM1mJDs6Z8kzHPkvGO5VT6P92q<wbr>BIcnp3gNG2I3zzw&e=</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.<br>
<br>
______________________________<wbr>_________________<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">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rpm-wg</a><br>
______________________________<wbr>_________________<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">https://www.icann.org/privacy<wbr>/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy<wbr>/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></div></div>
</blockquote></div>