draft-ietf-regext-tmch-func-spec-07.txt   draft-ietf-regext-tmch-func-spec-08.txt 
Internet Engineering Task Force G. Lozano Internet Engineering Task Force G. Lozano
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Informational Apr 06, 2020 Intended status: Informational Apr 07, 2020
Expires: October 8, 2020 Expires: October 9, 2020
ICANN TMCH functional specifications ICANN TMCH functional specifications
draft-ietf-regext-tmch-func-spec-07 draft-ietf-regext-tmch-func-spec-08
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 https://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 October 8, 2020. This Internet-Draft will expire on October 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://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
skipping to change at page 3, line 33 skipping to change at page 3, line 33
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. Change History . . . . . . . . . . . . . . . . . . . . . . . 58 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 58
9.1. Version 04 . . . . . . . . . . . . . . . . . . . . . . . 58 9.1. Version 04 . . . . . . . . . . . . . . . . . . . . . . . 58
9.2. Version 05 . . . . . . . . . . . . . . . . . . . . . . . 58 9.2. Version 05 . . . . . . . . . . . . . . . . . . . . . . . 58
9.3. Version 06 . . . . . . . . . . . . . . . . . . . . . . . 58 9.3. Version 06 . . . . . . . . . . . . . . . . . . . . . . . 58
9.4. Version 07 . . . . . . . . . . . . . . . . . . . . . . . 58 9.4. Version 07 . . . . . . . . . . . . . . . . . . . . . . . 58
9.5. Version 08 . . . . . . . . . . . . . . . . . . . . . . . 59
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 59 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 59
11. Security Considerations . . . . . . . . . . . . . . . . . . . 59 11. Security Considerations . . . . . . . . . . . . . . . . . . . 59
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 59 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 60
12.1. Normative References . . . . . . . . . . . . . . . . . . 59 12.1. Normative References . . . . . . . . . . . . . . . . . . 60
12.2. Informative References . . . . . . . . . . . . . . . . . 61 12.2. Informative References . . . . . . . . . . . . . . . . . 61
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 62 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
skipping to change at page 32, line 48 skipping to change at page 32, line 48
number>, where: number>, where:
- YYYY: year that the TCN was generated. - YYYY: year that the TCN was generated.
- MM: zero-padded month that the TCN was generated. - MM: zero-padded month that the TCN was generated.
- DD: zero-padded day that the TCN was generated. - DD: zero-padded day that the TCN was generated.
- vv: version of the TCN, possible values are 00 and 01. - vv: version of the TCN, possible values are 00 and 01.
- X: one hexadecimal digit [0-9A-F]. This is the first, - X: one hex character. This is the first, second and
second and third hexadecimal digit of encoding the third hex character of encoding the <Random bits> in
<Random bits> in base16 as specified in [RFC4648]. base16 as specified in [RFC4648].
- Random bits: 144 random bits encoded in base64url as - Random bits: 144 random bits encoded in base64url as
specified in [RFC4648]. specified in [RFC4648].
- Sequential number: zero-padded natural number in the - Sequential number: zero-padded natural number in the
range 0000000001 to 2147483647. range 0000000001 to 2147483647.
+ <DNL insertion datetime>, datetime in UTC that the DNL was + <DNL insertion datetime>, datetime in UTC that the DNL was
first inserted into the DNL List. The possible two values first inserted into the DNL List. The possible two values
of time for inserting a DNL to the DNL List are 00:00:00 and of time for inserting a DNL to the DNL List are 00:00:00 and
skipping to change at page 41, line 47 skipping to change at page 41, line 47
processing by the TMDB. Possible values are "accepted" or processing by the TMDB. Possible values are "accepted" or
"rejected". "rejected".
+ <Warning flag>, whether the LORDN Log has any warning result + <Warning flag>, whether the LORDN Log has any warning result
codes. Possible values are "no-warnings" or "warnings- codes. Possible values are "no-warnings" or "warnings-
present". present".
+ <Number of DN Lines>, number of DNs effective allocations + <Number of DN Lines>, number of DNs effective allocations
processed in the LORDN file. processed in the LORDN file.
A Registry Operator is NOT REQUIRED to process a LORDN Log with A Registry Operator is not required to process a LORDN Log with
a <Status flag>="accepted" and <Warning flag>="no-warnings". a <Status flag>="accepted" and <Warning flag>="no-warnings".
o second line: a header line as specified in [RFC4180] o second line: a header line as specified in [RFC4180]
With the header names as follows: With the header names as follows:
roid,result-code roid,result-code
o One or more lines with: <roid>,<result code> o One or more lines with: <roid>,<result code>
skipping to change at page 44, line 47 skipping to change at page 44, line 47
3614 TCNID does not exist 3614 TCNID does not exist
The TCNID has never existed in the central repository. The TCNID has never existed in the central repository.
3615 Recent-dnl-insertion outside of the time window 3615 Recent-dnl-insertion outside of the time window
The DN registration is reported as a recent-dnl-insertion, The DN registration is reported as a recent-dnl-insertion,
but the (re) insertion into the DNL occurred more than but the (re) insertion into the DNL occurred more than
24 hours ago. 24 hours ago.
3616 Registration Date of DN in Claims before the end of Sunrise Period 3616 Registration Date of DN in Claims before the end of Sunrise Period
The registration date of the DN is before the end of Sunrise Period The registration date of the DN is before the end of
and the DN was reported in a Trademark Claims LORDN file. the Sunrise Period and the DN was reported in a
Trademark Claims LORDN file.
3617 Registrar has not been approved by the TMDB 3617 Registrar has not been approved by the TMDB
Registrar ID in DN Line has not completed Trademark Claims integration Registrar ID in DN Line has not completed Trademark Claims
testing with the TMDB. integration testing with the TMDB.
3618 Registration Date of DN in a QLP LORDN file outside of the QLP Period 3618 Registration Date of DN in QLP LORDN file out of the QLP Period
The registration date of the DN in a QLP LORDN file is outside The registration date of the DN in a QLP LORDN file is outside
of the QLP Period. of the QLP Period.
3619 TCN was not valid 3619 TCN was not valid
The TCN was not valid (based on the <tmNotice:notBefore> The TCN was not valid (based on the <tmNotice:notBefore>
field of the TCN) at the datetime of acknowledgement. field of the TCN) at the datetime of acknowledgement.
4501 Syntax Error in DN Line 4501 Syntax Error in DN Line
Syntax Error in DN Line. Syntax Error in DN Line.
skipping to change at page 52, line 22 skipping to change at page 52, line 22
<tmNotice:street>123 Example Dr.</tmNotice:street> <tmNotice:street>123 Example Dr.</tmNotice:street>
<tmNotice:street>Suite 100</tmNotice:street> <tmNotice:street>Suite 100</tmNotice:street>
<tmNotice:city>Reston</tmNotice:city> <tmNotice:city>Reston</tmNotice:city>
<tmNotice:sp>VA</tmNotice:sp> <tmNotice:sp>VA</tmNotice:sp>
<tmNotice:pc>20190</tmNotice:pc> <tmNotice:pc>20190</tmNotice:pc>
<tmNotice:cc>US</tmNotice:cc> <tmNotice:cc>US</tmNotice:cc>
</tmNotice:addr> </tmNotice:addr>
<tmNotice:voice x="4321">+1.7035555555</tmNotice:voice> <tmNotice:voice x="4321">+1.7035555555</tmNotice:voice>
<tmNotice:email>jdoe@example.com</tmNotice:email> <tmNotice:email>jdoe@example.com</tmNotice:email>
</tmNotice:contact> </tmNotice:contact>
<tmNotice:jurDesc jurCC="US">UNITED STATES OF AMERICA</tmNotice:jurDesc> <tmNotice:jurDesc jurCC="US">USA</tmNotice:jurDesc>
<tmNotice:classDesc classNum="35"> <tmNotice:classDesc classNum="35">
Advertising; business management; business administration. Advertising; business management; business administration.
</tmNotice:classDesc> </tmNotice:classDesc>
<tmNotice:classDesc classNum="36"> <tmNotice:classDesc classNum="36">
Insurance; financial affairs; monetary affairs; real estate. Insurance; financial affairs; monetary affairs; real estate.
</tmNotice:classDesc> </tmNotice:classDesc>
<tmNotice:goodsAndServices> <tmNotice:goodsAndServices>
Bardus populorum circumdabit se cum captiosus populum. Bardus populorum circumdabit se cum captiosus populum.
Smert populorum circumdabit se cum captiosus populum qui eis differimus. Smert populorum circumdabit se cum captiosus populum.
</tmNotice:goodsAndServices> </tmNotice:goodsAndServices>
</tmNotice:claim> </tmNotice:claim>
<tmNotice:claim> <tmNotice:claim>
<tmNotice:markName>Example-One</tmNotice:markName> <tmNotice:markName>Example-One</tmNotice:markName>
<tmNotice:holder entitlement="owner"> <tmNotice:holder entitlement="owner">
<tmNotice:org>Example S.A. de C.V.</tmNotice:org> <tmNotice:org>Example S.A. de C.V.</tmNotice:org>
<tmNotice:addr> <tmNotice:addr>
<tmNotice:street>Calle conocida #343</tmNotice:street> <tmNotice:street>Calle conocida #343</tmNotice:street>
<tmNotice:city>Conocida</tmNotice:city> <tmNotice:city>Conocida</tmNotice:city>
<tmNotice:sp>SP</tmNotice:sp> <tmNotice:sp>SP</tmNotice:sp>
<tmNotice:pc>82140</tmNotice:pc> <tmNotice:pc>82140</tmNotice:pc>
<tmNotice:cc>BR</tmNotice:cc> <tmNotice:cc>BR</tmNotice:cc>
</tmNotice:addr> </tmNotice:addr>
</tmNotice:holder> </tmNotice:holder>
<tmNotice:jurDesc jurCC="BR">BRAZIL</tmNotice:jurDesc> <tmNotice:jurDesc jurCC="BR">BRAZIL</tmNotice:jurDesc>
<tmNotice:goodsAndServices> <tmNotice:goodsAndServices>
Bardus populorum circumdabit se cum captiosus populum. Bardus populorum circumdabit se cum captiosus populum.
Smert populorum circumdabit se cum captiosus populum qui eis differimus. Smert populorum circumdabit se cum captiosus populum.
</tmNotice:goodsAndServices> </tmNotice:goodsAndServices>
</tmNotice:claim> </tmNotice:claim>
<tmNotice:claim> <tmNotice:claim>
<tmNotice:markName>One</tmNotice:markName> <tmNotice:markName>One</tmNotice:markName>
<tmNotice:holder entitlement="owner"> <tmNotice:holder entitlement="owner">
<tmNotice:org>One Corporation</tmNotice:org> <tmNotice:org>One Corporation</tmNotice:org>
<tmNotice:addr> <tmNotice:addr>
<tmNotice:street>Otra calle</tmNotice:street> <tmNotice:street>Otra calle</tmNotice:street>
<tmNotice:city>Otra ciudad</tmNotice:city> <tmNotice:city>Otra ciudad</tmNotice:city>
<tmNotice:sp>OT</tmNotice:sp> <tmNotice:sp>OT</tmNotice:sp>
<tmNotice:pc>383742</tmNotice:pc> <tmNotice:pc>383742</tmNotice:pc>
<tmNotice:cc>CR</tmNotice:cc> <tmNotice:cc>CR</tmNotice:cc>
</tmNotice:addr> </tmNotice:addr>
</tmNotice:holder> </tmNotice:holder>
<tmNotice:jurDesc jurCC="CR">COSTA RICA</tmNotice:jurDesc> <tmNotice:jurDesc jurCC="CR">COSTA RICA</tmNotice:jurDesc>
<tmNotice:goodsAndServices> <tmNotice:goodsAndServices>
Bardus populorum circumdabit se cum captiosus populum. Bardus populorum circumdabit se cum captiosus populum.
Smert populorum circumdabit se cum captiosus populum qui eis differimus. Smert populorum circumdabit se cum captiosus populum.
</tmNotice:goodsAndServices> </tmNotice:goodsAndServices>
<tmNotice:notExactMatch> <tmNotice:notExactMatch>
<tmNotice:court> <tmNotice:court>
<tmNotice:refNum>234235</tmNotice:refNum> <tmNotice:refNum>234235</tmNotice:refNum>
<tmNotice:cc>CR</tmNotice:cc> <tmNotice:cc>CR</tmNotice:cc>
<tmNotice:courtName>Supreme Court of Justice of Costa Rica</tmNotice:courtName> <tmNotice:courtName>Supreme Court of Spain</tmNotice:courtName>
</tmNotice:court> </tmNotice:court>
</tmNotice:notExactMatch> </tmNotice:notExactMatch>
</tmNotice:claim> </tmNotice:claim>
<tmNotice:claim> <tmNotice:claim>
<tmNotice:markName>One Inc</tmNotice:markName> <tmNotice:markName>One Inc</tmNotice:markName>
<tmNotice:holder entitlement="owner"> <tmNotice:holder entitlement="owner">
<tmNotice:org>One SA de CV</tmNotice:org> <tmNotice:org>One SA de CV</tmNotice:org>
<tmNotice:addr> <tmNotice:addr>
<tmNotice:street>La calle</tmNotice:street> <tmNotice:street>La calle</tmNotice:street>
<tmNotice:city>La ciudad</tmNotice:city> <tmNotice:city>La ciudad</tmNotice:city>
<tmNotice:sp>CD</tmNotice:sp> <tmNotice:sp>CD</tmNotice:sp>
<tmNotice:pc>34323</tmNotice:pc> <tmNotice:pc>34323</tmNotice:pc>
<tmNotice:cc>AR</tmNotice:cc> <tmNotice:cc>AR</tmNotice:cc>
</tmNotice:addr> </tmNotice:addr>
</tmNotice:holder> </tmNotice:holder>
<tmNotice:jurDesc jurCC="AR">ARGENTINA</tmNotice:jurDesc> <tmNotice:jurDesc jurCC="AR">ARGENTINA</tmNotice:jurDesc>
<tmNotice:goodsAndServices> <tmNotice:goodsAndServices>
Bardus populorum circumdabit se cum captiosus populum. Bardus populorum circumdabit se cum captiosus populum.
Smert populorum circumdabit se cum captiosus populum qui eis differimus. Smert populorum circumdabit se cum captiosus populum.
</tmNotice:goodsAndServices> </tmNotice:goodsAndServices>
<tmNotice:notExactMatch> <tmNotice:notExactMatch>
<tmNotice:udrp> <tmNotice:udrp>
<tmNotice:caseNo>D2003-0499</tmNotice:caseNo> <tmNotice:caseNo>D2003-0499</tmNotice:caseNo>
<tmNotice:udrpProvider>WIPO</tmNotice:udrpProvider> <tmNotice:udrpProvider>WIPO</tmNotice:udrpProvider>
</tmNotice:udrp> </tmNotice:udrp>
</tmNotice:notExactMatch> </tmNotice:notExactMatch>
</tmNotice:claim> </tmNotice:claim>
</tmNotice:notice> </tmNotice:notice>
skipping to change at page 55, line 41 skipping to change at page 55, line 41
The BEGIN and END tags are not part of the schema; they are used to The BEGIN and END tags are not part of the schema; they are used to
note the beginning and ending of the schema for URI registration note the beginning and ending of the schema for URI registration
purposes. purposes.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:tmNotice-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:tmNotice-1.0"
xmlns:tmNotice="urn:ietf:params:xml:ns:tmNotice-1.0" xmlns:tmNotice="urn:ietf:params:xml:ns:tmNotice-1.0"
xmlns:mark="urn:ietf:params:xml:ns:mark-1.0" xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation> <annotation>
<documentation> <documentation>
Schema for representing a Trademark Claim Notice. Schema for representing a Trademark Claim Notice.
</documentation> </documentation>
</annotation> </annotation>
<import namespace="urn:ietf:params:xml:ns:mark-1.0"/> <import namespace="urn:ietf:params:xml:ns:mark-1.0"/>
<element name="notice" type="tmNotice:noticeType"/> <element name="notice" type="tmNotice:noticeType"/>
<complexType name="holderType"> <complexType name="holderType">
<sequence> <sequence>
skipping to change at page 56, line 51 skipping to change at page 57, line 4
<simpleContent> <simpleContent>
<extension base="token"> <extension base="token">
<attribute name="jurCC" type="mark:ccType" use="required"/> <attribute name="jurCC" type="mark:ccType" use="required"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<complexType name="classDescType"> <complexType name="classDescType">
<simpleContent> <simpleContent>
<extension base="token"> <extension base="token">
<attribute name="classNum" type="integer" use="required"/> <attribute name="classNum" type="integer" use="required"/>
</extension>
</extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<complexType name="noExactMatchType"> <complexType name="noExactMatchType">
<choice maxOccurs="unbounded"> <choice maxOccurs="unbounded">
<element name="udrp" type="tmNotice:udrpType"/> <element name="udrp" type="tmNotice:udrpType"/>
<element name="court" type="tmNotice:courtType"/> <element name="court" type="tmNotice:courtType"/>
</choice> </choice>
</complexType> </complexType>
<complexType name="udrpType"> <complexType name="udrpType">
<sequence> <sequence>
skipping to change at page 57, line 52 skipping to change at page 58, line 4
<element name="voice" type="mark:e164Type"/> <element name="voice" type="mark:e164Type"/>
<element name="fax" type="mark:e164Type" minOccurs="0"/> <element name="fax" type="mark:e164Type" minOccurs="0"/>
<element name="email" type="mark:minTokenType"/> <element name="email" type="mark:minTokenType"/>
</sequence> </sequence>
<attribute name="type" type="mark:contactTypeType"/> <attribute name="type" type="mark:contactTypeType"/>
</complexType> </complexType>
<simpleType name="idType"> <simpleType name="idType">
<restriction base="token"> <restriction base="token">
<pattern value="[a-fA-F0-9]{8}\d{1,19}"/> <pattern value="[a-fA-F0-9]{8}\d{1,19}"/>
</restriction> </restriction>
</simpleType>
</simpleType>
</schema> </schema>
END END
8. Acknowledgements 8. Acknowledgements
This specification is a collaborative effort from several This specification is a collaborative effort from several
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
skipping to change at page 59, line 5 skipping to change at page 59, line 5
9.4. Version 07 9.4. Version 07
1. Changes based on the feedback provided here: 1. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/ https://mailarchive.ietf.org/arch/msg/regext/
xcZPOAajlUJzgPgZBuqlIWRcFZg/ xcZPOAajlUJzgPgZBuqlIWRcFZg/
2. Changes based on the feedback provided here: 2. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/ https://mailarchive.ietf.org/arch/msg/regext/
MdOhSomd6_djLcthfw5mxWZkbWY MdOhSomd6_djLcthfw5mxWZkbWY
9.5. Version 08
1. Fixed issues detected by idnits tool.
10. IANA Considerations 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]. Two URI conforming to a registry mechanism described in [RFC3688]. Two URI
assignments have been registered by the IANA. assignments 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
 End of changes. 22 change blocks. 
24 lines changed or deleted 31 lines changed or added

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