Thanks Lori volunteering again.

You were going to provide language we could add to FAQ in lay persons term for the rather legalistic language we used for the implementation note we added regarding RPM

Provided below for your convenience.

4. Rights Protection Mechanism Requirements Applicability

4.1 Section 2.4.3 of the Rights Protection Mechanism Requirements provides that, “[i]f Registry Operator reserves a domain name from registration in accordance with Section 2.6 of the Agreement and Specification 5 of the Agreement and thereafter (i) releases for Allocation or registration such reserved domain name at any time prior to the start date of the Claims Period, such domain name MUST be treated like any other domain name for any applicable Sunrise Period, Limited Registration Period, Launch Program or Claims Period, or (ii) releases for Allocation or registration such reserved domain name at any time following the start date of the Claims Period, such domain name MUST be subject to the Claims Services (as defined in Section 3) for a period of ninety (90) calendar days following the date Registry Operator releases such domain name for registration as long as the Trademark Clearinghouse (or any ICANN-designated successor thereto) remains in operation.” (emphasis added) As noted above, Section 2.4.3 provides specific requirements for names reserved in accordance with Section 2.6 of the Registry Agreement and Specification 5 of the Registry Agreement. The GNSO Policy for the Protection of IGO and INGO Identifiers in All gTLDs (the “Policy”), in section 3.1, requires registry operators to reserve “the second-level domain names corresponding to all identifiers recorded on the Red Cross, IOC and IGOs Identifier List”. Because these names are reserved in accordance with the Policy, and not reserved in accordance with Section 2.6 of the Registry Agreement and Specification 5 of the Registry Agreement, Section 2.4.3 of the RPM Requirements Document does not apply to the second-level domain names corresponding to all identifiers recorded on the Red Cross, IOC and IGOs Identifier List.

btw, Mr. Tanaka mentioned to me that the implementation note is helpful and appreciated it being added.

Thanks

Dennis Chang

From: Lori Schulman <lschulman@inta.org>
Date: Wednesday, October 11, 2017 at 9:59 AM
To: Dennis Chang <dennis.chang@icann.org>, "gnso-igo-ingo-ip-irt@icann.org" <gnso-igo-ingo-ip-irt@icann.org>
Cc: "dtantanaka@verisign.com" <dtantanaka@verisign.com>
Subject: [Ext] RE: New iRT member: Dennis Tanaka - Verisign

Welcome Mr. Tanaka. Happy to have you in our merry little band. Dennis, I think I owe you some language. I apologize for the delay. Can you remind me of the deliverable?

Lori S. Schulman

Senior Director, Internet Policy

International Trademark Association (INTA)

+1-202-704-0408, Skype: lsschulman

017-esig

From: gnso-igo-ingo-ip-irt-bounces@icann.org [mailto:gnso-igo-ingo-ip-irt-bounces@icann.org] On Behalf Of Dennis Chang
Sent: Wednesday, October 11, 2017 12:21 PM
To: gnso-igo-ingo-ip-irt@icann.org
Cc: dtantanaka@verisign.com
Subject: [Gnso-igo-ingo-ip-irt] New iRT member: Dennis Tanaka - Verisign

Dear IGO&INGO IRT,

Mr. Dennis Tanaka from Verisign has joined our IRT.

Mr. Tanaka is from Verisign and has been following the IGO/INGO policy item having taken it over from Chuck Gomes.

I’ll refer to him as Mr. Tanaka to avoid confusion now we have two Dennis’ on the Implementation Team.

Michelle,

Please add him to the email group and the IRT wiki membership list

Dennis Tanaka

<dtantanaka@verisign.com>

—

Kind Regards,

Dennis S. Chang

GDD Services & Engagement Program Director

+1 213 293 7889

Skype: dennisSchang