[gtld-tech] RPM Requirement of Supporting Claims Service for Release or Allocation of Reserved Domain Names

Mon May 19 13:44:20 UTC 2014

We suggested many alternatives similar to this idea during RPM Negotiations with ICANN, with no avail. It's a burden indeed, but one that we have to live with it for the time being; we could perhaps start a PDP so a new consensus policy can override the current agreement with something agreeable by the whole community. 

Rubens

Em 19/05/2014, à(s) 10:38:000, Dykes, Roy <Roy.Dykes at neustar.biz> escreveu:

> One way of dealing with this is to have the registry notify the TMCH (not using the LORDN file) but something similar to the TMCH if there's a registration of a domain name matching that of a claim.
> 
> --Neustar Registry Product Management
> 
> -----Original Message-----
> From: gtld-tech-bounces at icann.org [mailto:gtld-tech-bounces at icann.org] On Behalf Of gtld-tech-request at icann.org
> Sent: Monday, May 19, 2014 8:00 AM
> To: gtld-tech at icann.org
> Subject: gtld-tech Digest, Vol 13, Issue 1
> 
> Send gtld-tech mailing list submissions to
> 	gtld-tech at icann.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://urldefense.proofpoint.com/v1/url?u=https://mm.icann.org/mailman/listinfo/gtld-tech&k=lQ50IrZ4n2wmPbDBDzKBYw%3D%3D%0A&r=ltQ01elRBpTiAAu3PBAB%2FCClpNW2eBk%2Fh3quV%2BehdXA%3D%0A&m=PWZn64FuFcEjlElRvgQhEkADnSnGRWnxw8NCB7vGTa8%3D%0A&s=4e6f8a1ddee42ab1a55a8ffe648ce99366959b34488ad873a775eabaf8e95fc3
> or, via email, send a message with subject or body 'help' to
> 	gtld-tech-request at icann.org
> 
> You can reach the person managing the list at
> 	gtld-tech-owner at icann.org
> 
> When replying, please edit your Subject line so it is more specific than "Re: Contents of gtld-tech digest..."
> 
> 
> Today's Topics:
> 
>   1.  RPM Requirement of Supporting Claims Service for Release or
>      Allocation of Reserved Domain Names (Gould, James)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 19 May 2014 11:53:01 +0000
> From: "Gould, James" <JGould at verisign.com>
> To: "gtld-tech at icann.org" <gtld-tech at icann.org>, "tmch-tech at icann.org"
> 	<tmch-tech at icann.org>
> Subject: [gtld-tech] RPM Requirement of Supporting Claims Service for
> 	Release or Allocation of Reserved Domain Names
> Message-ID: <CF9F6885.5F071%jgould at verisign.com>
> Content-Type: text/plain; charset="utf-8"
> 
> According to section 2.4.3 of the Rights Protection Mechanism (RPM) Requirements, it states:
> 
> If 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.
> 
> For registries that plan on releasing domain names after the Claims Period, such as to support the release of premium domain names or 2 character domain names, they will have to support the Claims Services well past the Claims Period (potentially years).  This represents a costly burden to the registries having to indefinitely download the DNL list, support the claims check, validating the domain creates against the DNL list for a subset of domain names, and support the TMCH LORDN interface.  This also represents a costly burden to registrars or discourages registrar participation in supporting the release of reserved domain names.  The registrars would need to know to use the claims check, use the CNIS for presenting the claims notice, and passing the claims acknowledgement indefinitely.
> 
> Since this is a complex issue impacting registries and registrars, what approaches are being considered?  Do the registries and registrars have any issues with supporting the Claims Service indefinitely?
> 
> Please respond with your thoughts and concerns.
> 
> Thanks,
> 
> --
> 
> JG
> 
> [cid:81958BBD-962A-4D7D-AB87-1A2BDB076D74]
> 
> James Gould
> Principal Software Engineer
> jgould at verisign.com<mailto:jgould at verisign.com>
> 
> 703-948-3271 (Office)
> 12061 Bluemont Way
> Reston, VA 20190
> VerisignInc.com
> ?This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://urldefense.proofpoint.com/v1/url?u=http://mm.icann.org/pipermail/gtld-tech/attachments/20140519/1065c47b/attachment-0001.html&k=lQ50IrZ4n2wmPbDBDzKBYw%3D%3D%0A&r=ltQ01elRBpTiAAu3PBAB%2FCClpNW2eBk%2Fh3quV%2BehdXA%3D%0A&m=PWZn64FuFcEjlElRvgQhEkADnSnGRWnxw8NCB7vGTa8%3D%0A&s=a4f5791c421fe031cdc9fc9f92354158322955ee2c6f07bd40bbffbf486bfd44>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[99].png
> Type: image/png
> Size: 4109 bytes
> Desc: 3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[99].png
> URL: <https://urldefense.proofpoint.com/v1/url?u=http://mm.icann.org/pipermail/gtld-tech/attachments/20140519/1065c47b/3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B7499-0001.png&k=lQ50IrZ4n2wmPbDBDzKBYw%3D%3D%0A&r=ltQ01elRBpTiAAu3PBAB%2FCClpNW2eBk%2Fh3quV%2BehdXA%3D%0A&m=PWZn64FuFcEjlElRvgQhEkADnSnGRWnxw8NCB7vGTa8%3D%0A&s=7e0fb2ccc8853c9446a0b56a4255f998e57180728154e1778a0b2482d94135d0>
> 
> ------------------------------
> 
> _______________________________________________
> gtld-tech mailing list
> gtld-tech at icann.org
> https://urldefense.proofpoint.com/v1/url?u=https://mm.icann.org/mailman/listinfo/gtld-tech&k=lQ50IrZ4n2wmPbDBDzKBYw%3D%3D%0A&r=ltQ01elRBpTiAAu3PBAB%2FCClpNW2eBk%2Fh3quV%2BehdXA%3D%0A&m=PWZn64FuFcEjlElRvgQhEkADnSnGRWnxw8NCB7vGTa8%3D%0A&s=4e6f8a1ddee42ab1a55a8ffe648ce99366959b34488ad873a775eabaf8e95fc3
> 
> 
> End of gtld-tech Digest, Vol 13, Issue 1
> ****************************************