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

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/