draft-ietf-regext-tmch-func-spec-03.txt | draft-ietf-regext-tmch-func-spec-04.txt | |||
---|---|---|---|---|
Internet Engineering Task Force G. Lozano | Internet Engineering Task Force G. Lozano | |||
Internet-Draft ICANN | Internet-Draft ICANN | |||
Intended status: Informational July 18, 2017 | Intended status: Informational Jun 13, 2018 | |||
Expires: January 19, 2018 | Expires: December 15, 2018 | |||
ICANN TMCH functional specifications | ICANN TMCH functional specifications | |||
draft-ietf-regext-tmch-func-spec-03 | draft-ietf-regext-tmch-func-spec-04 | |||
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 | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
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 https://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 January 19, 2018. | This Internet-Draft will expire on December 15, 2018. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2017 IETF Trust and the persons identified as the | Copyright (c) 2018 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 | (https://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 | |||
described in the Simplified BSD License. | described in the Simplified BSD License. | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
skipping to change at page 3, line 28 ¶ | skipping to change at page 3, line 28 ¶ | |||
6.2. SMD Revocation List . . . . . . . . . . . . . . . . . . . 33 | 6.2. SMD Revocation List . . . . . . . . . . . . . . . . . . . 33 | |||
6.3. List of Registered Domain Names (LORDN) file . . . . . . 35 | 6.3. List of Registered Domain Names (LORDN) file . . . . . . 35 | |||
6.3.1. LORDN Log file . . . . . . . . . . . . . . . . . . . 40 | 6.3.1. LORDN Log file . . . . . . . . . . . . . . . . . . . 40 | |||
6.3.1.1. LORDN Log Result Codes . . . . . . . . . . . . . 42 | 6.3.1.1. LORDN Log Result Codes . . . . . . . . . . . . . 42 | |||
6.4. Signed Mark Data (SMD) File . . . . . . . . . . . . . . . 46 | 6.4. Signed Mark Data (SMD) File . . . . . . . . . . . . . . . 46 | |||
6.5. Trademark Claims Notice (TCN) . . . . . . . . . . . . . . 47 | 6.5. Trademark Claims Notice (TCN) . . . . . . . . . . . . . . 47 | |||
6.6. Sunrise List (SURL) . . . . . . . . . . . . . . . . . . . 54 | 6.6. Sunrise List (SURL) . . . . . . . . . . . . . . . . . . . 54 | |||
7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 55 | 7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 55 | |||
7.1. Trademark Claims Notice (TCN) . . . . . . . . . . . . . . 55 | 7.1. Trademark Claims Notice (TCN) . . . . . . . . . . . . . . 55 | |||
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 58 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 58 | |||
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58 | 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 58 | |||
10. Security Considerations . . . . . . . . . . . . . . . . . . . 59 | 9.1. Version 04 . . . . . . . . . . . . . . . . . . . . . . . 58 | |||
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 59 | 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58 | |||
11.1. Normative References . . . . . . . . . . . . . . . . . . 59 | 11. Security Considerations . . . . . . . . . . . . . . . . . . . 59 | |||
11.2. Informative References . . . . . . . . . . . . . . . . . 60 | 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 59 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 61 | 12.1. Normative References . . . . . . . . . . . . . . . . . . 59 | |||
12.2. Informative References . . . . . . . . . . . . . . . . . 60 | ||||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 62 | ||||
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 58, line 29 ¶ | skipping to change at page 58, line 29 ¶ | |||
participants in the ICANN community. Bernie Hoeneisen participated | participants in the ICANN community. Bernie Hoeneisen participated | |||
as co-author until version 02 providing invaluable support for this | as co-author until version 02 providing invaluable support for this | |||
document. This specification is based on a model spearheaded by: | document. This specification is based on a model spearheaded by: | |||
Chris Wright, Jeff Neuman, Jeff Eckhaus and Will Shorter. The author | Chris Wright, Jeff Neuman, Jeff Eckhaus and Will Shorter. The author | |||
would also like to thank the thoughtful feedbak provided by many in | would also like to thank the thoughtful feedbak provided by many in | |||
the tmch-tech mailing list, but particularly the extensive help | the tmch-tech mailing list, but particularly the extensive help | |||
provided by James Gould, James Mitchell and Francisco Arias. This | provided by James Gould, James Mitchell and Francisco Arias. This | |||
document includes feedback received from the following individuals: | document includes feedback received from the following individuals: | |||
Paul Hoffman. | Paul Hoffman. | |||
9. IANA Considerations | 9. Change History | |||
[[RFC Editor: Please remove this section.]] | ||||
9.1. Version 04 | ||||
1. Ping update. | ||||
10. IANA Considerations | ||||
This document uses URNs to describe XML namespaces and XML schemas | This document uses URNs to describe XML namespaces and XML schemas | |||
conforming to a registry mechanism described in [RFC3688]. One URI | conforming to a registry mechanism described in [RFC3688]. One URI | |||
assignment have been registered by the IANA. | assignment have been registered by the IANA. | |||
Registration request for the Trademark Claims Notice namespace: | Registration request for the Trademark Claims Notice namespace: | |||
URI: urn:ietf:params:xml:ns:tmNotice-1.0 | URI: urn:ietf:params:xml:ns:tmNotice-1.0 | |||
Registrant Contact: See the "Author's Address" section of this | Registrant Contact: See the "Author's Address" section of this | |||
skipping to change at page 59, line 7 ¶ | skipping to change at page 59, line 14 ¶ | |||
Registration request for the Trademark Claims Notice XML schema: | Registration request for the Trademark Claims Notice XML schema: | |||
URI: urn:ietf:params:xml:ns:tmNotice-1.0 | URI: urn:ietf:params:xml:ns:tmNotice-1.0 | |||
Registrant Contact: See the "Author's Address" section of this | Registrant Contact: See the "Author's Address" section of this | |||
document. | document. | |||
XML: See Section 7.1 of this document. | XML: See Section 7.1 of this document. | |||
10. Security Considerations | 11. Security Considerations | |||
This specification uses HTTP Basic Authentication to provide a simple | This specification uses HTTP Basic Authentication to provide a simple | |||
application-layer authentication service. HTTPS is used in all | application-layer authentication service. HTTPS is used in all | |||
interfaces in order to protect against most common attacks. In | interfaces in order to protect against most common attacks. In | |||
addition, the client identifier is tied to a set of IP addresses that | addition, the client identifier is tied to a set of IP addresses that | |||
are allowed to connect to the interfaces described in this document, | are allowed to connect to the interfaces described in this document, | |||
providing an extra security measure. | providing an extra security measure. | |||
The TMDB MUST provide credentials to the appropriate Registries and | The TMDB MUST provide credentials to the appropriate Registries and | |||
Registrars. | Registrars. | |||
The TMDB MUST require the use of strong passwords by Registries and | The TMDB MUST require the use of strong passwords by Registries and | |||
Registrars. | Registrars. | |||
The TMDB, Registries and Registrars MUST use the best practices | The TMDB, Registries and Registrars MUST use the best practices | |||
described in RFC 7525 or its successors. | described in RFC 7525 or its successors. | |||
11. References | 12. References | |||
11.1. Normative References | 12.1. Normative References | |||
[Claims50] | [Claims50] | |||
ICANN, "Implementation Notes: Trademark Claims Protection | ICANN, "Implementation Notes: Trademark Claims Protection | |||
for Previously Abused Names", July 2013, | for Previously Abused Names", July 2013, | |||
<https://newgtlds.icann.org/en/about/trademark- | <https://newgtlds.icann.org/en/about/trademark- | |||
clearinghouse/previously-abused-16jul13-en.pdf>. | clearinghouse/previously-abused-16jul13-en.pdf>. | |||
[MatchingRules] | [MatchingRules] | |||
ICANN, "Memorandum on Implementing Matching Rules", | ICANN, "Memorandum on Implementing Matching Rules", | |||
September 2012, <https://newgtlds.icann.org/en/about/ | September 2012, <https://newgtlds.icann.org/en/about/ | |||
trademark-clearinghouse/matching-rules-24sep12-en.pdf>. | trademark-clearinghouse/matching-rules-24sep12-en.pdf>. | |||
[QLP-Addendum] | [QLP-Addendum] | |||
ICANN, "Qualified Launch Program Addendum", April 2014, | ICANN, "Qualified Launch Program Addendum", April 2014, | |||
<https://newgtlds.icann.org/en/about/trademark- | <https://newgtlds.icann.org/en/about/trademark- | |||
clearinghouse/rpm-requirements-qlp-addendum- | clearinghouse/ | |||
10apr14-en.pdf>. | rpm-requirements-qlp-addendum-10apr14-en.pdf>. | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
<http://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | |||
DOI 10.17487/RFC3688, January 2004, | DOI 10.17487/RFC3688, January 2004, | |||
<http://www.rfc-editor.org/info/rfc3688>. | <https://www.rfc-editor.org/info/rfc3688>. | |||
[RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", | [RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", | |||
RFC 7848, DOI 10.17487/RFC7848, June 2016, | RFC 7848, DOI 10.17487/RFC7848, June 2016, | |||
<http://www.rfc-editor.org/info/rfc7848>. | <https://www.rfc-editor.org/info/rfc7848>. | |||
[RPM-Requirements] | [RPM-Requirements] | |||
ICANN, "Rights Protection Mechanism Requirements", | ICANN, "Rights Protection Mechanism Requirements", | |||
September 2013, <https://newgtlds.icann.org/en/about/ | September 2013, <https://newgtlds.icann.org/en/about/ | |||
trademark-clearinghouse/rpm-requirements-30sep13-en.pdf>. | trademark-clearinghouse/rpm-requirements-30sep13-en.pdf>. | |||
11.2. Informative References | 12.2. Informative References | |||
[ICANN-GTLD-AGB-20120604] | [ICANN-GTLD-AGB-20120604] | |||
ICANN, "gTLD Applicant Guidebook Version 2012-06-04", June | ICANN, "gTLD Applicant Guidebook Version 2012-06-04", June | |||
2012, <http://newgtlds.icann.org/en/applicants/agb/ | 2012, <http://newgtlds.icann.org/en/applicants/agb/ | |||
guidebook-full-04jun12-en.pdf>. | guidebook-full-04jun12-en.pdf>. | |||
[ISO3166-2] | [ISO3166-2] | |||
ISO, "International Standard for country codes and codes | ISO, "International Standard for country codes and codes | |||
for their subdivisions", 2006, | for their subdivisions", 2006, | |||
<http://www.iso.org/iso/home/standards/country_codes.htm>. | <http://www.iso.org/iso/home/standards/country_codes.htm>. | |||
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, | [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, | |||
DOI 10.17487/RFC2818, May 2000, | DOI 10.17487/RFC2818, May 2000, | |||
<http://www.rfc-editor.org/info/rfc2818>. | <https://www.rfc-editor.org/info/rfc2818>. | |||
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: | [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: | |||
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, | Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, | |||
<http://www.rfc-editor.org/info/rfc3339>. | <https://www.rfc-editor.org/info/rfc3339>. | |||
[RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- | [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- | |||
Separated Values (CSV) Files", RFC 4180, | Separated Values (CSV) Files", RFC 4180, | |||
DOI 10.17487/RFC4180, October 2005, | DOI 10.17487/RFC4180, October 2005, | |||
<http://www.rfc-editor.org/info/rfc4180>. | <https://www.rfc-editor.org/info/rfc4180>. | |||
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data | [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data | |||
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, | Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, | |||
<http://www.rfc-editor.org/info/rfc4648>. | <https://www.rfc-editor.org/info/rfc4648>. | |||
[RFC4880] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R. | [RFC4880] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R. | |||
Thayer, "OpenPGP Message Format", RFC 4880, | Thayer, "OpenPGP Message Format", RFC 4880, | |||
DOI 10.17487/RFC4880, November 2007, | DOI 10.17487/RFC4880, November 2007, | |||
<http://www.rfc-editor.org/info/rfc4880>. | <https://www.rfc-editor.org/info/rfc4880>. | |||
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., | [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., | |||
Housley, R., and W. Polk, "Internet X.509 Public Key | Housley, R., and W. Polk, "Internet X.509 Public Key | |||
Infrastructure Certificate and Certificate Revocation List | Infrastructure Certificate and Certificate Revocation List | |||
(CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, | (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, | |||
<http://www.rfc-editor.org/info/rfc5280>. | <https://www.rfc-editor.org/info/rfc5280>. | |||
[RFC5890] Klensin, J., "Internationalized Domain Names for | [RFC5890] Klensin, J., "Internationalized Domain Names for | |||
Applications (IDNA): Definitions and Document Framework", | Applications (IDNA): Definitions and Document Framework", | |||
RFC 5890, DOI 10.17487/RFC5890, August 2010, | RFC 5890, DOI 10.17487/RFC5890, August 2010, | |||
<http://www.rfc-editor.org/info/rfc5890>. | <https://www.rfc-editor.org/info/rfc5890>. | |||
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | |||
Protocol (HTTP/1.1): Message Syntax and Routing", | Protocol (HTTP/1.1): Message Syntax and Routing", | |||
RFC 7230, DOI 10.17487/RFC7230, June 2014, | RFC 7230, DOI 10.17487/RFC7230, June 2014, | |||
<http://www.rfc-editor.org/info/rfc7230>. | <https://www.rfc-editor.org/info/rfc7230>. | |||
[RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | |||
Protocol (HTTP/1.1): Semantics and Content", RFC 7231, | Protocol (HTTP/1.1): Semantics and Content", RFC 7231, | |||
DOI 10.17487/RFC7231, June 2014, | DOI 10.17487/RFC7231, June 2014, | |||
<http://www.rfc-editor.org/info/rfc7231>. | <https://www.rfc-editor.org/info/rfc7231>. | |||
[RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | |||
Protocol (HTTP/1.1): Authentication", RFC 7235, | Protocol (HTTP/1.1): Authentication", RFC 7235, | |||
DOI 10.17487/RFC7235, June 2014, | DOI 10.17487/RFC7235, June 2014, | |||
<http://www.rfc-editor.org/info/rfc7235>. | <https://www.rfc-editor.org/info/rfc7235>. | |||
[RFC7719] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS | [RFC7719] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS | |||
Terminology", RFC 7719, DOI 10.17487/RFC7719, December | Terminology", RFC 7719, DOI 10.17487/RFC7719, December | |||
2015, <http://www.rfc-editor.org/info/rfc7719>. | 2015, <https://www.rfc-editor.org/info/rfc7719>. | |||
[WIPO-NICE-CLASSES] | [WIPO-NICE-CLASSES] | |||
WIPO, "WIPO Nice Classification", 2015, | WIPO, "WIPO Nice Classification", 2015, | |||
<http://www.wipo.int/classifications/nice/en>. | <http://www.wipo.int/classifications/nice/en>. | |||
[WIPO.ST3] | [WIPO.ST3] | |||
WIPO, "Recommended standard on two-letter codes for the | WIPO, "Recommended standard on two-letter codes for the | |||
representation of states, other entities and | representation of states, other entities and | |||
intergovernmental organizations", March 2007, | intergovernmental organizations", March 2007, | |||
<http://www.iso.org/iso/home/standards/country_codes.htm>. | <http://www.iso.org/iso/home/standards/country_codes.htm>. | |||
End of changes. 27 change blocks. | ||||
34 lines changed or deleted | 44 lines changed or added | |||
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |