--- 1/draft-ietf-regext-tmch-func-spec-02.txt 2017-07-19 10:13:13.283416855 -0700 +++ 2/draft-ietf-regext-tmch-func-spec-03.txt 2017-07-19 10:13:13.391419423 -0700 @@ -1,18 +1,18 @@ Internet Engineering Task Force G. Lozano Internet-Draft ICANN -Intended status: Informational October 3, 2016 -Expires: April 6, 2017 +Intended status: Informational July 18, 2017 +Expires: January 19, 2018 ICANN TMCH functional specifications - draft-ietf-regext-tmch-func-spec-02 + draft-ietf-regext-tmch-func-spec-03 Abstract This document describes the requirements, the architecture and the interfaces between the ICANN Trademark Clearinghouse (TMCH) and Domain Name Registries as well as between the ICANN TMCH and Domain Name Registrars for the provisioning and management of domain names during Sunrise and Trademark Claims Periods. Status of This Memo @@ -23,25 +23,25 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 6, 2017. + This Internet-Draft will expire on January 19, 2018. Copyright Notice - Copyright (c) 2016 IETF Trust and the persons identified as the + Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -94,44 +94,44 @@ 5.2.5. TMDB Sunrise Services for Registrars . . . . . . . . 22 5.3. Trademark Claims Period . . . . . . . . . . . . . . . . . 23 5.3.1. Domain Registration . . . . . . . . . . . . . . . . . 23 5.3.2. Trademark Claims Domain Name registration by Registries . . . . . . . . . . . . . . . . . . . . . 24 5.3.3. TMBD Trademark Claims Services for Registries . . . . 25 5.3.3.1. Domain Name Label (DNL) List . . . . . . . . . . 25 5.3.3.2. Notice of Registered Domain Names (NORN) . . . . 26 5.3.4. Trademark Claims Domain Name registration by Registrars . . . . . . . . . . . . . . . . . . . . . 26 - 5.3.5. TMBD Trademark Claims Services for Registrars . . . . 27 - 5.3.5.1. Claims Notice Information Service (CNIS) . . . . 27 + 5.3.5. TMBD Trademark Claims Services for Registrars . . . . 28 + 5.3.5.1. Claims Notice Information Service (CNIS) . . . . 28 5.4. Qualified Launch Program (QLP) Period . . . . . . . . . . 28 5.4.1. Domain Registration . . . . . . . . . . . . . . . . . 28 - 5.4.2. TMBD QLP Services for Registries . . . . . . . . . . 30 - 5.4.2.1. Sunrise List (SURL) . . . . . . . . . . . . . . . 30 - 6. Data Format Descriptions . . . . . . . . . . . . . . . . . . 30 - 6.1. Domain Name Label (DNL) List . . . . . . . . . . . . . . 30 - 6.2. SMD Revocation List . . . . . . . . . . . . . . . . . . . 32 - 6.3. List of Registered Domain Names (LORDN) file . . . . . . 34 - 6.3.1. LORDN Log file . . . . . . . . . . . . . . . . . . . 39 - 6.3.1.1. LORDN Log Result Codes . . . . . . . . . . . . . 41 - 6.4. Signed Mark Data (SMD) File . . . . . . . . . . . . . . . 45 - 6.5. Trademark Claims Notice (TCN) . . . . . . . . . . . . . . 46 - 6.6. Sunrise List (SURL) . . . . . . . . . . . . . . . . . . . 53 - 7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 54 - 7.1. Trademark Claims Notice (TCN) . . . . . . . . . . . . . . 54 - 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57 - 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57 - 10. Security Considerations . . . . . . . . . . . . . . . . . . . 58 - 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 58 - 11.1. Normative References . . . . . . . . . . . . . . . . . . 58 - 11.2. Informative References . . . . . . . . . . . . . . . . . 59 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 60 + 5.4.2. TMBD QLP Services for Registries . . . . . . . . . . 31 + 5.4.2.1. Sunrise List (SURL) . . . . . . . . . . . . . . . 31 + 6. Data Format Descriptions . . . . . . . . . . . . . . . . . . 31 + 6.1. Domain Name Label (DNL) List . . . . . . . . . . . . . . 31 + 6.2. SMD Revocation List . . . . . . . . . . . . . . . . . . . 33 + 6.3. List of Registered Domain Names (LORDN) file . . . . . . 35 + 6.3.1. LORDN Log file . . . . . . . . . . . . . . . . . . . 40 + 6.3.1.1. LORDN Log Result Codes . . . . . . . . . . . . . 42 + 6.4. Signed Mark Data (SMD) File . . . . . . . . . . . . . . . 46 + 6.5. Trademark Claims Notice (TCN) . . . . . . . . . . . . . . 47 + 6.6. Sunrise List (SURL) . . . . . . . . . . . . . . . . . . . 54 + 7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 55 + 7.1. Trademark Claims Notice (TCN) . . . . . . . . . . . . . . 55 + 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 58 + 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58 + 10. Security Considerations . . . . . . . . . . . . . . . . . . . 59 + 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 59 + 11.1. Normative References . . . . . . . . . . . . . . . . . . 59 + 11.2. Informative References . . . . . . . . . . . . . . . . . 60 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 61 1. Introduction Domain Name Registries (DNRs) may operate in special modes for certain periods of time enabling trademark holders to protect their rights during the introduction of a Top Level Domain (TLD). Along with the introduction of new generic TLDs (gTLD), two special modes came into effect: @@ -1029,22 +1029,26 @@ If the three elements mentioned above are not provided by the Registrar for a DN matching a DNL of a PRM, but the DNL was inserted (or re-inserted) for the first time into DNL List less than 24 hours ago, the registration MAY continue without this data and the tests listed below are not required to be performed. 2. The TCN has not expired (according to the expiration datetime sent by the Registrar). - 3. The acceptance datetime is no more than 48 hours in the past, - or a different value defined by ICANN policy. + 3. The acceptance datetime is within the window of time defined + by ICANN policy. In the gTLD round of 2012, Registrars + verified that the acceptance datetime was less than or equal + to 48 hours in the past, as there were no defined ICANN + policies at that time. Implementers should be aware that + ICANN policy may define this value in the future. 4. Using the leftmost DNL of the DN being effectively allocated, the expiration datetime provided by the Registrar, and the TMDB Notice Identifier extracted from the TCNID provided by the Registrar compute the TCN Checksum. Verify that the computed TCN Checksum match the TCN Checksum present in the TCNID. For example, if the DN "xn--mgbachtv.xn--mgbh0fb" is being effectively allocated, the leftmost DNL would be "xn-- mgbachtv". @@ -1139,30 +1143,34 @@ 6. Send the registration to the Registry (ry interface, Section 4.3.5) and include the following information: * TCNID () * Expiration date of the TCN () * Acceptance datetime of the TCN. - TCNs are generated twice a day. The expiration date - () of each TCN MUST be set to 48 hours (or a - different value if defined by ICANN policy) in the future by the - TMDB, allowing the implementation of a cache by Registrars and enough - time for acknowledging the TCN. Registrars SHOULD implement a cache - of TCNs to minimize the number of queries sent to the TMDB. A cached - TCN MUST be removed from the cache after the expiration date of the - TCN as defined by . The TMDB MAY implement rate- - limiting as one of the protection mechanisms to mitigate the risk of - performance degradation. + Currently TCNs are generated twice a day by the TMDB. The expiration + date () of each TCN MUST be set to a value defined + by ICANN policy. In the gTLD round of 2012, the TMDB set the + expiration value to 48 hours in to the future as there were no + defined ICANN policies at that time. Implementers should be aware + that ICANN policy may define this value in the future. + + Registrars SHOULD implement a cache of TCNs to minimize the number of + queries sent to the TMDB. A cached TCN MUST be removed from the + cache after the expiration date of the TCN as defined by + . + + The TMDB MAY implement rate-limiting as one of the protection + mechanisms to mitigate the risk of performance degradation. 5.3.5. TMBD Trademark Claims Services for Registrars 5.3.5.1. Claims Notice Information Service (CNIS) The TCNs are provided by the TMDB online and are fetched by the Registrar via the dr interface (Section 4.3.6). To get access to the TCNs, the Registrar needs the credentials provided by the TMDB (Section 5.1.2.1) and the Lookup Key received