draft-ietf-eppext-launchphase-02.txt   draft-ietf-eppext-launchphase-03.txt 
Internet Engineering Task Force J. Gould Internet Engineering Task Force J. Gould
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Intended status: Standards Track W. Tan Intended status: Standards Track W. Tan
Expires: March 29, 2015 Cloud Registry Expires: August 2, 2015 Cloud Registry
G. Brown G. Brown
CentralNic Ltd CentralNic Ltd
September 25, 2014 January 29, 2015
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-eppext-launchphase-02 draft-ietf-eppext-launchphase-03
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
extension mapping for the provisioning and management of domain name extension mapping for the provisioning and management of domain name
registrations and applications during the launch of a domain name registrations and applications during the launch of a domain name
registry. registry.
Status of This Memo Status of This Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 March 29, 2015. This Internet-Draft will expire on August 2, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 4 1.1. Conventions Used in This Document . . . . . . . . . . . . 4
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Application Identifier . . . . . . . . . . . . . . . . . 4 2.1. Application Identifier . . . . . . . . . . . . . . . . . 5
2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5 2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5
2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 5
2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 6 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 6
2.4.1. State Transition . . . . . . . . . . . . . . . . . . 7 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 7
2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 8 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 8
2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 11 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 11
2.6.1. <launch:codeMark> element . . . . . . . . . . . . . . 12 2.6.1. <launch:codeMark> element . . . . . . . . . . . . . . 12
2.6.2. <mark:mark> element . . . . . . . . . . . . . . . . . 13 2.6.2. <mark:mark> element . . . . . . . . . . . . . . . . . 13
2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 13 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 13
2.6.3.1. <smd:signedMark> element . . . . . . . . . . . . 13 2.6.3.1. <smd:signedMark> element . . . . . . . . . . . . 13
2.6.3.2. <smd:encodedSignedMark> element . . . . . . . . . 13 2.6.3.2. <smd:encodedSignedMark> element . . . . . . . . . 13
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 13 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 13
3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 14 3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 14
3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 14 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 14
3.1.2. Availability Check Form . . . . . . . . . . . . . . . 17 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 17
3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 19 3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 19
3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 22 3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 22
3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 22 3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 25
3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 28 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 25
3.3.3. General Create Form . . . . . . . . . . . . . . . . . 31 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 31
3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 32 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 34
3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 34 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 35
3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 35 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 37
3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 36 3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 38
3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 37 3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 39
3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 38 3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 40
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 38 3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 41
4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 38 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 41
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 45 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 41
6. Change History . . . . . . . . . . . . . . . . . . . . . . . 46 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
6.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 46 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 48
6.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 46 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 49
6.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 46 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 49
6.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 46 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 50
6.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 47 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 50
6.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 47 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 51
6.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 47 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 51
6.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 47 7. Security Considerations . . . . . . . . . . . . . . . . . . . 52
6.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 48 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 52
6.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 48 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 49 9.1. Normative References . . . . . . . . . . . . . . . . . . 52
6.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 49 9.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 49 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 53
6.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 50 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 53
6.15. Change WG 01 to WG 02 . . . . . . . . . . . . . . . . . . 50 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 53
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 53
8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 54
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 51 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 54
9.1. Normative References . . . . . . . . . . . . . . . . . . 51 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 54
9.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 51 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 51 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 55
A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 55
A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 56
A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 56
A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 57
A.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 57
A.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 57
A.15. Change WG 01 to WG 02 . . . . . . . . . . . . . . . . . . 57
A.16. Change WG 02 to WG 03 . . . . . . . . . . . . . . . . . . 57
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58
1. Introduction 1. Introduction
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping
specifies a flexible schema that can be used to implement several specifies a flexible schema that can be used to implement several
common use cases related to the provisioning and management of domain common use cases related to the provisioning and management of domain
name registrations and applications during the launch of a domain name registrations and applications during the launch of a domain
name registry. name registry.
skipping to change at page 14, line 13 skipping to change at page 14, line 13
any interpretation by the client or server. Such processing is any interpretation by the client or server. Such processing is
typically highly policy-dependent and therefore specific to typically highly policy-dependent and therefore specific to
implementations. implementations.
Operations on application objects are done via one or more of the Operations on application objects are done via one or more of the
existing EPP verbs defined in the EPP domain name mapping [RFC5731]. existing EPP verbs defined in the EPP domain name mapping [RFC5731].
Registries MAY choose to support a subset of the operations. Registries MAY choose to support a subset of the operations.
3.1. EPP <check> Command 3.1. EPP <check> Command
There are two forms of the extension to the EPP <check> command: the There are three forms of the extension to the EPP <check> command:
Claims Check Form (Section 3.1.1) and the Availability Check Form the Claims Check Form (Section 3.1.1), the Availability Check Form
(Section 3.1.2). The <launch:check> element "type" attribute defines (Section 3.1.2), and the Trademark Check Form (Section 3.1.3). The
the form, with the value of "claims" for the Claims Check Form <launch:check> element "type" attribute defines the form, with the
(Section 3.1.1) and with the value of "avail" for the Availability value of "claims" for the Claims Check Form (Section 3.1.1), with the
Check Form (Section 3.1.2). The default value of the "type" value of "avail" for the Availability Check Form (Section 3.1.2), and
attribute is "claims". The forms supported by the server is with the value of "trademark" for the Trademark Check Form
determined by server policy. The server MUST return an EPP error (Section 3.1.3). The default value of the "type" attribute is
result code of 2307 if it receives a check form that is not "claims". The forms supported by the server is determined by server
supported. policy. The server MUST return an EPP error result code of 2307 if
it receives a check form that is not supported.
3.1.1. Claims Check Form 3.1.1. Claims Check Form
The Claims Check Form defines a new command called the Claims Check The Claims Check Form defines a new command called the Claims Check
Command that is used to determine whether or not there are any Command that is used to determine whether or not there are any
matching trademarks, in the specified launch phase, for each domain matching trademarks, in the specified launch phase, for each domain
name passed in the command. The availability check information name passed in the command, that requires the use of the "Claims
defined in the EPP domain name mapping [RFC5731] MUST NOT be returned Create Form" on a Domain Create Command. The availability check
for the Claims Check Command. This form is the default form and MAY information defined in the EPP domain name mapping [RFC5731] MUST NOT
be explicitly identified by setting the <launch:check> "type" be returned for the Claims Check Command. This form is the default
attribute to "claims". form and MAY be explicitly identified by setting the <launch:check>
"type" attribute to "claims".
Instead of returning whether the domain name is available, the Claims Instead of returning whether the domain name is available, the Claims
Check Command will return whether or not at least one matching Check Command will return whether or not at least one matching
trademark exists for the domain name. If there is at least one trademark exists for the domain name, that requires the use of the
matching trademark that exists for the domain name, a "Claims Create Form" on a Domain Create Command. If there is at
least one matching trademark that exists for the domain name, a
<launch:claimKey> element is returned. The client MAY then use the <launch:claimKey> element is returned. The client MAY then use the
value of the <launch:claimKey> element to obtain information needed value of the <launch:claimKey> element to obtain information needed
to generate the Trademark Claims Notice from Trademark Validator to generate the Trademark Claims Notice from Trademark Validator
based on the Validator Identifier (Section 2.2). The unique notice based on the Validator Identifier (Section 2.2). The unique notice
identifier of the Trademark Claims Notice MUST be passed in the identifier of the Trademark Claims Notice MUST be passed in the
<launch:noticeID> element of the extension to the Create Command <launch:noticeID> element of the extension to the Create Command
(Section 3.3). (Section 3.3).
The <domain:name> elements in the EPP <check> command of EPP domain The <domain:name> elements in the EPP <check> command of EPP domain
name mapping [RFC5731] define the domain names to check for matching name mapping [RFC5731] define the domain names to check for matching
trademarks. The <launch:check> element contains the following child trademarks. The <launch:check> element contains the following child
elements: elements:
<launch:phase> The launch phase that SHOULD be "claims". <launch:phase> Contains the value of the active launch phase of the
server. The server SHOULD validate the value against the active
server launch phase.
Example Claims Check command using the <check> domain command and the Example Claims Check command using the <check> domain command and the
<launch:check> extension with the "type" explicitly set to "claims", <launch:check> extension with the "type" explicitly set to "claims",
to determine if "example1.tld" and "example2.tld" have any matching to determine if "example1.tld", "example2.tld", and "example3.tld"
trademarks during the "claims" launch phase: require claims notices during the "claims" launch phase:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <check> C: <check>
C: <domain:check C: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example1.tld</domain:name> C: <domain:name>example1.tld</domain:name>
C: <domain:name>example2.tld</domain:name> C: <domain:name>example2.tld</domain:name>
C: <domain:name>example3.tld</domain:name>
C: </domain:check> C: </domain:check>
C: </check> C: </check>
C: <extension> C: <extension>
C: <launch:check C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="claims"> C: type="claims">
C: <launch:phase>claims</launch:phase> C: <launch:phase>claims</launch:phase>
C: </launch:check> C: </launch:check>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
If the <check> command has been processed successfully, the EPP If the <check> command has been processed successfully, the EPP
<response> MUST contain an <extension> <launch:chkData> element that <response> MUST contain an <extension> <launch:chkData> element that
identifies the launch namespace. The <launch:chkData> element identifies the launch namespace. The <launch:chkData> element
contains the following child elements: contains the following child elements:
<launch:phase> The launch phase that SHOULD be "claims". <launch:phase> The phase that mirrors the <launch:phase> element
included in the <launch:check>.
<launch:cd> One or more <launch:cd> elements that contain the <launch:cd> One or more <launch:cd> elements that contain the
following child elements: following child elements:
<launch:name> Contains the fully qualified name of the queried <launch:name> Contains the fully qualified name of the queried
domain name. This element MUST contain an "exists" attribute domain name. This element MUST contain an "exists" attribute
whose value indicates if a matching trademark exists for the whose value indicates if a matching trademark exists for the
domain name. A value of "1" (or "true") means that a domain name that requires the use of the "Claims Create Form"
matching trademark does exist for the claims launch phase. A on a Domain Create Command. A value of "1" (or "true") means
value of "0" (or "false") means that a matching trademark that a matching trademark does exist and that the "Claims
does not exist. Create Form" is required on a Domain Create Command. A value
of "0" (or "false") means that a matching trademark does not
exist or that the "Claims Create Form" is NOT required on a
Domain Create Command.
<launch:claimKey> Zero or more OPTIONAL claim keys that MAY be <launch:claimKey> Zero or more OPTIONAL claim keys that MAY be
passed to a third-party trademark validator such as the passed to a third-party trademark validator such as the
Trademark Clearinghouse (TMCH) for querying the information Trademark Clearinghouse (TMCH) for querying the information
needed to generate a Trademark Claims Notice. The needed to generate a Trademark Claims Notice. The
<launch:claimKey> is used as the key for the query in place <launch:claimKey> is used as the key for the query in place
of the domain name to securely query the service without of the domain name to securely query the service without
using a well-known value like a domain name. The OPTIONAL using a well-known value like a domain name. The OPTIONAL
"validatorID" attribute is the Validator Identifier "validatorID" attribute is the Validator Identifier
(Section 2.2) whose value indicates which Trademark Validator (Section 2.2) whose value indicates which Trademark Validator
to query for the Claims Notice information, with the default to query for the Claims Notice information, with the default
being the ICANN TMCH. The "validatorID" attribute MAY being the ICANN TMCH. The "validatorID" attribute MAY
reference a non-trademark claims clearinghouse identifer to reference a non-trademark claims clearinghouse identifer to
support other forms of claims notices. support other forms of claims notices.
Example Claims Check response when no matching trademarks are found Example Claims Check response when a claims notice is not required
for the domain name example1.tld, matching trademarks are found for for the domain name example1.tld, a claims notice is required for the
the domain name example2.tld in the "tmch", matching trademarks are domain name example2.tld in the "tmch", and a claims notice is
found for domain name example3.tld in the "tmch" and "custom-tmch", required for the domain name example3.tld in the "tmch" and "custom-
for the "claims" launch phase: tmch", for the "claims" launch phase:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <launch:chkData S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
skipping to change at page 19, line 5 skipping to change at page 19, line 5
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
The Availability Check Form does not define any extension to the The Availability Check Form does not define any extension to the
response of an <check> domain command. After processing the command, response of an <check> domain command. After processing the command,
the server replies with a standard EPP response as defined in the EPP the server replies with a standard EPP response as defined in the EPP
domain name mapping [RFC5731]. domain name mapping [RFC5731].
3.1.3. Trademark Check Form
The Trademark Check Form defines a new command called the Trademark
Check Command that is used to determine whether or not there are any
matching trademarks for each domain name passed in the command,
independent of the active launch phase of the server and whether the
"Claims Create Form" is required on a Domain Create Command. The
availability check information defined in the EPP domain name mapping
[RFC5731] MUST NOT be returned for the Claims Check Command. This
form MUST be identified by setting the <launch:check> "type"
attribute to "trademark".
Instead of returning whether the domain name is available, the
Trademark Check Command will return whether or not at least one
matching trademark exists for the domain name. If there is at least
one matching trademark that exists for the domain name, a
<launch:claimKey> element is returned. The client MAY then use the
value of the <launch:claimKey> element to obtain Trademark Claims
Notice information from Trademark Validator based on the Validator
Identifier (Section 2.2).
The <domain:name> elements in the EPP <check> command of EPP domain
name mapping [RFC5731] define the domain names to check for matching
trademarks. The <launch:check> element does not contain any child
elements with the "Trademark Check Form":
Example Trademark Check command using the <check> domain command and
the <launch:check> extension with the "type" set to "trademark", to
determine if "example1.tld", "example2.tld", and "example3.tld" have
any matching trademarks:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <check>
C: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example1.tld</domain:name>
C: <domain:name>example2.tld</domain:name>
C: <domain:name>example3.tld</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="trademark"/>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
If the <check> command has been processed successfully, the EPP
<response> MUST contain an <extension> <launch:chkData> element that
identifies the launch namespace. The <launch:chkData> element
contains the following child elements:
<launch:cd> One or more <launch:cd> elements that contain the
following child elements:
<launch:name> Contains the fully qualified name of the queried
domain name. This element MUST contain an "exists" attribute
whose value indicates if a matching trademark exists for the
domain name. A value of "1" (or "true") means that a
matching trademark does exist. A value of "0" (or "false")
means that a matching trademark does not exist.
<launch:claimKey> Zero or more OPTIONAL claim keys that MAY be
passed to a third-party trademark validator such as the
Trademark Clearinghouse (TMCH) for querying the information
needed to generate a Trademark Claims Notice. The
<launch:claimKey> is used as the key for the query in place
of the domain name to securely query the service without
using a well-known value like a domain name. The OPTIONAL
"validatorID" attribute is the Validator Identifier
(Section 2.2) whose value indicates which Trademark Validator
to query for the Claims Notice information, with the default
being the ICANN TMCH. The "validatorID" attribute MAY
reference a non-trademark claims clearinghouse identifer to
support other forms of claims notices.
Example Trademark Check response when no matching trademarks are
found for the domain name example1.tld, matching trademarks are found
for the domain name example2.tld in the "tmch", matching trademarks
are found for domain name example3.tld in the "tmch" and "custom-
tmch", for the "claims" launch phase:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <extension>
S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:cd>
S: <launch:name exists="0">example1.tld</launch:name>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">example2.tld</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">example3.tld</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: <launch:claimKey validatorID="custom-tmch">
S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
S: </launch:claimKey>
S: </launch:cd>
S: </launch:chkData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
3.2. EPP <info> Command 3.2. EPP <info> Command
This extension defines additional elements to extend the EPP <info> This extension defines additional elements to extend the EPP <info>
command and response to be used in conjunction with the EPP domain command and response to be used in conjunction with the EPP domain
name mapping [RFC5731]. name mapping [RFC5731].
The EPP <info> command is used to retrieve information for a launch The EPP <info> command is used to retrieve information for a launch
phase registration or application. The Application Identifier phase registration or application. The Application Identifier
(Section 2.1) returned in the <launch:creData> element of the create (Section 2.1) returned in the <launch:creData> element of the create
response (Section 3.3) is used for retrieving information for a response (Section 3.3) is used for retrieving information for a
skipping to change at page 22, line 28 skipping to change at page 25, line 28
landrush The EPP <create> command with the "landrush" launch phase landrush The EPP <create> command with the "landrush" launch phase
MAY use the General Create Form (Section 3.3.3) to explicitly MAY use the General Create Form (Section 3.3.3) to explicitly
specify the phase and optionally define the expected type of specify the phase and optionally define the expected type of
object to create. object to create.
claims The EPP <create> command with the "claims" launch phase is claims The EPP <create> command with the "claims" launch phase is
used to pass the information associated with the presentation and used to pass the information associated with the presentation and
acceptance of the Claims Notice. The Claims Create Form acceptance of the Claims Notice. The Claims Create Form
(Section 3.3.2) is used and the General Create Form (Section 3.3.2) is used and the General Create Form
(Section 3.3.3) MAY be used for the "claims" launch phase. (Section 3.3.3) MAY be used for the "claims" launch phase.
open The EPP <create> command with the "open" launch phase is open The EPP <create> command with the "open" launch phase is
undefined but the form supported is up to server policy. undefined but the form supported is up to server policy. Use of
the Claims Create Form (Section 3.3.2) MAY be used to pass the
information associated with the presentation and acceptance of the
Claims Notice if required for the domain name.
custom The EPP <create> command with the "custom" launch phase is custom The EPP <create> command with the "custom" launch phase is
undefined but the form supported is up to server policy. undefined but the form supported is up to server policy.
3.3.1. Sunrise Create Form 3.3.1. Sunrise Create Form
The Sunrise Create Form of the extension to the EPP domain name The Sunrise Create Form of the extension to the EPP domain name
mapping [RFC5731] includes the verifiable trademark information that mapping [RFC5731] includes the verifiable trademark information that
the server uses to match against the domain name to authorize the the server uses to match against the domain name to authorize the
domain create. A server MUST support one of four models in Claim domain create. A server MUST support one of four models in Claim
Validation Models (Section 2.6) to verify the trademark information Validation Models (Section 2.6) to verify the trademark information
skipping to change at page 28, line 41 skipping to change at page 31, line 41
C: </launch:create> C: </launch:create>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
3.3.2. Claims Create Form 3.3.2. Claims Create Form
The Claims Create Form of the extension to the EPP domain name The Claims Create Form of the extension to the EPP domain name
mapping [RFC5731] includes the information related to the mapping [RFC5731] includes the information related to the
registrant's acceptance of the Claims Notice for the "claims" launch registrant's acceptance of the Claims Notice.
phase.
A <launch:create> element is sent along with the regular <create> A <launch:create> element is sent along with the regular <create>
domain command. The <launch:create> element has an OPTIONAL "type" domain command. The <launch:create> element has an OPTIONAL "type"
attribute that defines the expected type of object ("application" or attribute that defines the expected type of object ("application" or
"registration") to create. The server SHOULD validate the "type" "registration") to create. The server SHOULD validate the "type"
attribute, when passed, against the type of object that will be attribute, when passed, against the type of object that will be
created. The <launch:create> element contains the following child created. The <launch:create> element contains the following child
elements: elements:
<launch:phase> MUST contain the value of "claims" to indicate the <launch:phase> Contains the value of the active launch phase of the
claims launch phase. server. The server SHOULD validate the value against the active
server launch phase.
<launch:notice> One or more <launch:notice> elements that contain <launch:notice> One or more <launch:notice> elements that contain
the following child elements: the following child elements:
<launch:noticeID> Unique notice identifier for the Claims <launch:noticeID> Unique notice identifier for the Claims
Notice. The <launch:noticeID> element has an OPTIONAL Notice. The <launch:noticeID> element has an OPTIONAL
"validatorID" attribute is the Validator Identifier "validatorID" attribute is the Validator Identifier
(Section 2.2) whose value indicates which Trademark Validator (Section 2.2) whose value indicates which Trademark Validator
is the source of the Claims Notice, with the default being is the source of the claims notice, with the default being
the ICANN TMCH. the ICANN TMCH.
<launch:notAfter> Expiry of the claims notice. <launch:notAfter> Expiry of the claims notice.
<launch:acceptedDate> Contains the date and time that the Claims <launch:acceptedDate> Contains the date and time that the claims
Notice was accepted. notice was accepted.
The following is an example <create> domain command using the The following is an example <create> domain command using the
<launch:create> extension with the <launch:notice> information for <launch:create> extension with the <launch:notice> information for
the "tmch" and the "custom-tmch" validators, for the "claims" launch the "tmch" and the "custom-tmch" validators, for the "claims" launch
phase: phase:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <create> C: <create>
skipping to change at page 39, line 16 skipping to change at page 42, line 16
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema <schema
targetNamespace="urn:ietf:params:xml:ns:launch-1.0" targetNamespace="urn:ietf:params:xml:ns:launch-1.0"
xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:mark="urn:ietf:params:xml:ns:mark-1.0" xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0" xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
schemaLocation="eppcom-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:mark-1.0"/>
<import namespace="urn:ietf:params:xml:ns:signedMark-1.0"/>
<import namespace="urn:ietf:params:xml:ns:mark-1.0"
schemaLocation="mark-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:signedMark-1.0"
schemaLocation="signedMark-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
Extensible Provisioning Protocol v1.0 Extensible Provisioning Protocol v1.0
domain name extension schema domain name extension schema
for the launch phase processing. for the launch phase processing.
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
skipping to change at page 43, line 35 skipping to change at page 46, line 29
<element name="notAfter" type="dateTime"/> <element name="notAfter" type="dateTime"/>
<element name="acceptedDate" type="dateTime"/> <element name="acceptedDate" type="dateTime"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Child elements of check (Claims Check Command). Child elements of check (Claims Check Command).
--> -->
<complexType name="checkType"> <complexType name="checkType">
<sequence> <sequence>
<element name="phase" type="launch:phaseType"/> <element name="phase" type="launch:phaseType"
minOccurs="0"/>
</sequence> </sequence>
<attribute name="type" type="launch:checkFormType" <attribute name="type" type="launch:checkFormType"
default="claims"/> default="claims"/>
</complexType> </complexType>
<!-- <!--
Type of check form Type of check form
(claims check or availability check) (claims check or availability check)
--> -->
<simpleType name="checkFormType"> <simpleType name="checkFormType">
<restriction base="token"> <restriction base="token">
<enumeration value="claims"/> <enumeration value="claims"/>
<enumeration value="avail"/> <enumeration value="avail"/>
<enumeration value="trademark"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!--
Child elements of info command. Child elements of info command.
--> -->
<complexType name="infoType"> <complexType name="infoType">
<sequence> <sequence>
<element name="phase" type="launch:phaseType"/> <element name="phase" type="launch:phaseType"/>
<element name="applicationID" <element name="applicationID"
type="launch:applicationIDType" type="launch:applicationIDType"
minOccurs="0"/> minOccurs="0"/>
</sequence> </sequence>
skipping to change at page 44, line 33 skipping to change at page 47, line 30
--> -->
<element name="chkData" type="launch:chkDataType"/> <element name="chkData" type="launch:chkDataType"/>
<element name="creData" type="launch:idContainerType"/> <element name="creData" type="launch:idContainerType"/>
<element name="infData" type="launch:infDataType"/> <element name="infData" type="launch:infDataType"/>
<!-- <!--
<check> response elements. <check> response elements.
--> -->
<complexType name="chkDataType"> <complexType name="chkDataType">
<sequence> <sequence>
<element name="phase" type="launch:phaseType"/> <element name="phase" type="launch:phaseType"
minOccurs="0"/>
<element name="cd" type="launch:cdType" <element name="cd" type="launch:cdType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<complexType name="cdType"> <complexType name="cdType">
<sequence> <sequence>
<element name="name" type="launch:cdNameType"/> <element name="name" type="launch:cdNameType"/>
<element name="claimKey" type="launch:claimKeyType" <element name="claimKey" type="launch:claimKeyType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
skipping to change at page 45, line 37 skipping to change at page 48, line 35
<element name="status" type="launch:statusType" <element name="status" type="launch:statusType"
minOccurs="0"/> minOccurs="0"/>
<element ref="mark:abstractMark" <element ref="mark:abstractMark"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</schema> </schema>
END END
5. Acknowledgements 5. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. One URI
assignment has been registered by the IANA.
Registration request for the Launch namespace:
URI: urn:ietf:params:xml:ns:launch-1.0
Registrant Contact: See the "Author's Address" section of this
document.
XML: None. Namespace URIs do not represent an XML specification.
6. Implementation Status
Note to RFC Editor: Please remove this section and the reference to
RFC 6982 [RFC6982] before publication.
This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in RFC 6982
[RFC6982]. The description of implementations in this section is
intended to assist the IETF in its decision processes in progressing
drafts to RFCs. Please note that the listing of any individual
implementation here does not imply endorsement by the IETF.
Furthermore, no effort has been spent to verify the information
presented here that was supplied by IETF contributors. This is not
intended as, and must not be construed to be, a catalog of available
implementations or their features. Readers are advised to note that
other implementations may exist.
According to RFC 6982 [RFC6982], "this will allow reviewers and
working groups to assign due consideration to documents that have the
benefit of running code, which may serve as evidence of valuable
experimentation and feedback that have made the implemented protocols
more mature. It is up to the individual working groups to use this
information as they see fit".
6.1. Verisign EPP SDK
Organization: Verisign Inc.
Name: Verisign EPP SDK
Description: The Verisign EPP SDK includes both a full client
implementation and a full server stub implementation of draft-ietf-
eppext-launchphase.
Level of maturity: Production
Coverage: All aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License
Contact: jgould@verisign.com
URL: http://www.verisigninc.com/en_US/channel-resources/domain-
registry-products/epp-sdks
6.2. Verisign Consolidated Top Level Domain (CTLD) SRS
Organization: Verisign Inc.
Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry
System (SRS)
Description: The Verisign Consolidated Top Level Domain (CTLD) Shared
Registry System (SRS) implements the server-side of draft-ietf-
eppext-launchphase for a variety of Top Level Domains (TLD's).
Level of maturity: Production
Coverage: The "signed mark" Mark Validation Model, the Claims Check
Form for the EPP <check> Command, the Sunrise and Claims Forms for
the EPP <create> Command of Launch Registrations and Launch
Applications. For Launch Applications the Poll Messaging, the EPP
<info> Command, the EPP <update> Command, and the EPP <delete>
Command is covered.
Licensing: Proprietary
Contact: jgould@verisign.com
6.3. Verisign .COM / .NET SRS
Organization: Verisign Inc.
Name: Verisign .COM / .NET Shared Registry System (SRS)
Description: The Verisign Shared Registry System (SRS) for .COM, .NET
and other IDN TLD's implements the server-side of draft-ietf-eppext-
launchphase.
Level of maturity: Operational Test Environment (OTE)
Coverage: The "signed mark" Mark Validation Model, the Claims Check
Form for the EPP <check> Command, the Sunrise and Claims Forms for
the EPP <create> Command of Launch Registrations.
Licensing: Proprietary
Contact: jgould@verisign.com
6.4. REngin v3.7
Organization: Domain Name Services (Pty) Ltd
Name: REngin v3.7
Description: Server side implementation only
Level of maturity: Production
Coverage: All features from version 12 have been implemented
Licensing: Proprietary Licensing with Maintenance Contracts
Contact: info@dnservices.co.za
URL: https://www.registry.net.za and soon http://dnservices.co.za
6.5. RegistryEngine EPP Service
Organization: CentralNic
Name: RegistryEngine EPP Service
Description: Generic high-volume EPP service for gTLDs, ccTLDs and
SLDs
Level of maturity: Deployed in CentralNic's production environment as
well as two other gTLD registry systems, and two ccTLD registry
systems.
Coverage: Majority of elements including TMCH sunrise, landrush and
TM claims as well as sunrise applications validated using codes.
Licensing: Proprietary In-House software
Contact: epp@centralnic.com
URL: https://www.centralnic.com
6.6. Neustar EPP SDK
Organization: Neustar
Name: Neustar EPP SDK
Description: The Neustar EPP SDK includes client implementation of
draft-ietf-eppext-launchphase in both Java and C++.
Level of maturity: Production
Coverage: All aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License
Contact: trung.tran@neustar.biz
7. Security Considerations
The mapping extensions described in this document do not provide any
security services beyond those described by EPP [RFC5730], the EPP
domain name mapping [RFC5731], and protocol layers used by EPP. The
security considerations described in these other specifications apply
to this specification as well.
Updates to, and deletion of an application object must be restricted
to clients authorized to perform the said operation on the object.
As information contained within an application, or even the mere fact
that an application exists may be confidential. Any attempt to
operate on an application object by an unauthorized client MUST be
rejected with an EPP 2201 (authorization error) return code. Server
policy may allow <info> operation with filtered output by clients
other than the sponsoring client, in which case the <domain:infData>
and <launch:infData> response SHOULD be filtered to include only
fields that are publicly accessible.
8. Acknowledgements
The authors wish to acknowledge the efforts of the leading The authors wish to acknowledge the efforts of the leading
participants of the Community TMCH Model that led to many of the participants of the Community TMCH Model that led to many of the
changes to this document, which include Chris Wright, Jeff Neuman, changes to this document, which include Chris Wright, Jeff Neuman,
Jeff Eckhaus, and Will Shorter. Jeff Eckhaus, and Will Shorter.
Special suggestions that have been incorporated into this document Special suggestions that have been incorporated into this document
were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Jan were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Michael
Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus Malorny, Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus
Alexander Mayrhofer, Patrick Mevzek, James Mitchell, Francisco Malorny, Alexander Mayrhofer, Patrick Mevzek, James Mitchell,
Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung Tran, Ulrich Francisco Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung
Wisser and Sharon Wodjenski. Tran, Ulrich Wisser and Sharon Wodjenski.
6. Change History 9. References
6.1. Change from 00 to 01 9.1. Normative References
[I-D.ietf-eppext-tmch-smd]
Lozano, G., "Mark and Signed Mark Objects Mapping", draft-
ietf-eppext-tmch-smd-00 (work in progress), January 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, August 2009.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", RFC 6982, July
2013.
9.2. URIs
[1] http://tools.ietf.org/html/draft-lozano-tmch-func-spec
[2] http://tools.ietf.org/html/draft-lozano-tmch-func-spec
Appendix A. Change History
A.1. Change from 00 to 01
1. Changed to use camel case for the XML elements. 1. Changed to use camel case for the XML elements.
2. Replaced "cancelled" status to "rejected" status. 2. Replaced "cancelled" status to "rejected" status.
3. Added the child elements of the <claim> element. 3. Added the child elements of the <claim> element.
4. Removed the XML schema and replaced with "[TBD]". 4. Removed the XML schema and replaced with "[TBD]".
6.2. Change from 01 to 02 A.2. Change from 01 to 02
1. Added support for both the ICANN and ARI/Neustar TMCH models. 1. Added support for both the ICANN and ARI/Neustar TMCH models.
2. Changed the namespace URI and prefix to use "launch" instead of 2. Changed the namespace URI and prefix to use "launch" instead of
"launchphase". "launchphase".
3. Added definition of multiple claim validation models. 3. Added definition of multiple claim validation models.
4. Added the <launch:signedClaim> and <launch:signedNotice> 4. Added the <launch:signedClaim> and <launch:signedNotice>
elements. elements.
5. Added support for Claims Info Command 5. Added support for Claims Info Command
6.3. Change from 02 to 03 A.3. Change from 02 to 03
1. Removed XSI namespace per Keith Gaughan's suggestion on the 1. Removed XSI namespace per Keith Gaughan's suggestion on the
provreg list. provreg list.
2. Added extensibility to the launch:status element and added the 2. Added extensibility to the launch:status element and added the
pendingAuction status per Trung Tran's feedback on the provreg pendingAuction status per Trung Tran's feedback on the provreg
list. list.
3. Added support for the Claims Check Command, updated the location 3. Added support for the Claims Check Command, updated the location
and contents of the signedNotice, and replaced most references of and contents of the signedNotice, and replaced most references of
Claim to Mark based on the work being done on the ARI/Neustar Claim to Mark based on the work being done on the ARI/Neustar
launch model. launch model.
6.4. Change from 03 to 04 A.4. Change from 03 to 04
1. Removed references to the ICANN model. 1. Removed references to the ICANN model.
2. Removed support for the Claims Info Command. 2. Removed support for the Claims Info Command.
3. Removed use of the signedClaim. 3. Removed use of the signedClaim.
4. Revised the method for referring to the signedClaim from the XML 4. Revised the method for referring to the signedClaim from the XML
Signature using the IDREF URI. Signature using the IDREF URI.
5. Split the launch-1.0.xsd into three XML schemas including launch- 5. Split the launch-1.0.xsd into three XML schemas including launch-
1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd.
6. Split the "claims" launch phase to the "claims1" and "claims2" 6. Split the "claims" launch phase to the "claims1" and "claims2"
launch phases. launch phases.
7. Added support for the encodedSignedMark with base64 encoded 7. Added support for the encodedSignedMark with base64 encoded
signedMark. signedMark.
8. Changed the elements in the createNoticeType to include the 8. Changed the elements in the createNoticeType to include the
noticeID, timestamp, and the source elements. noticeID, timestamp, and the source elements.
9. Added the class and effectiveDate elements to mark. 9. Added the class and effectiveDate elements to mark.
6.5. Change from 04 to 05 A.5. Change from 04 to 05
1. Removed reference to <smd:zone> in the <smd:signedMark> example. 1. Removed reference to <smd:zone> in the <smd:signedMark> example.
2. Incorporated feedback from Bernhard Reutner-Fischer on the 2. Incorporated feedback from Bernhard Reutner-Fischer on the
provreg mail list. provreg mail list.
3. Added missing launch XML prefix to applicationIDType reference in 3. Added missing launch XML prefix to applicationIDType reference in
the idContainerType of the Launch Schema. the idContainerType of the Launch Schema.
4. Added missing description of the <mark:pc> element in the 4. Added missing description of the <mark:pc> element in the
<mark:addr> element. <mark:addr> element.
5. Updated note on replication of the EPP contact mapping elements 5. Updated note on replication of the EPP contact mapping elements
in the Mark Contact section. in the Mark Contact section.
6.6. Change from 05 to 06 A.6. Change from 05 to 06
1. Removed the definition of the mark-1.0 and signedMark-1.0 and 1. Removed the definition of the mark-1.0 and signedMark-1.0 and
replaced with reference to draft-lozano-smd, that contains the replaced with reference to draft-lozano-smd, that contains the
definition for the mark, signed marked, and encoded signed mark. definition for the mark, signed marked, and encoded signed mark.
2. Split the <launch:timestamp> into <launch:generatedDate> and 2. Split the <launch:timestamp> into <launch:generatedDate> and
<launch:acceptedDate> based on feedback from Trung Tran. <launch:acceptedDate> based on feedback from Trung Tran.
3. Added the "includeMark" optional attribute to the <launch:info> 3. Added the "includeMark" optional attribute to the <launch:info>
element to enable the client to request whether or not to include element to enable the client to request whether or not to include
the mark in the info response. the mark in the info response.
4. Fixed state diagram to remove redundant transition from "invalid" 4. Fixed state diagram to remove redundant transition from "invalid"
to "rejected"; thanks Klaus Malorny. to "rejected"; thanks Klaus Malorny.
6.7. Change from 06 to 07 A.7. Change from 06 to 07
1. Proof-read grammar and spelling. 1. Proof-read grammar and spelling.
2. Changed "pendingAuction" status to "pendingAllocation", changed 2. Changed "pendingAuction" status to "pendingAllocation", changed
"pending" to "pendingValidation" status, per proposal from Trung "pending" to "pendingValidation" status, per proposal from Trung
Tran and seconded by Rubens Kuhl. Tran and seconded by Rubens Kuhl.
3. Added text related to the use of RFC 5731 pendingCreate to the 3. Added text related to the use of RFC 5731 pendingCreate to the
Application Identifier section. Application Identifier section.
4. Added the Poll Messaging section to define the use of poll 4. Added the Poll Messaging section to define the use of poll
messaging for intermediate state transitions and pending action messaging for intermediate state transitions and pending action
poll messaging for final state transitions. poll messaging for final state transitions.
6.8. Change from 07 to 08 A.8. Change from 07 to 08
1. Added support for use of the launch statuses and poll messaging 1. Added support for use of the launch statuses and poll messaging
for Launch Registrations based on feedback from Sharon Wodjenski for Launch Registrations based on feedback from Sharon Wodjenski
and Trung Tran. and Trung Tran.
2. Incorporated changes based on updates or clarifications in draft- 2. Incorporated changes based on updates or clarifications in draft-
lozano-tmch-func-spec-01, which include: lozano-tmch-func-spec-01, which include:
1. Removed the unused <launch:generatedDate> element. 1. Removed the unused <launch:generatedDate> element.
2. Removed the <launch:source> element. 2. Removed the <launch:source> element.
3. Added the <launch:notAfter> element based on the required 3. Added the <launch:notAfter> element based on the required
<tmNotice:notAfter> element. <tmNotice:notAfter> element.
6.9. Change from 08 to 09 A.9. Change from 08 to 09
1. Made <choice> element optional in <launch:create> to allow 1. Made <choice> element optional in <launch:create> to allow
passing just the <launch:phase> in <launch:create> per request passing just the <launch:phase> in <launch:create> per request
from Ben Levac. from Ben Levac.
2. Added optional "type" attribute in <launch:create> to enable the 2. Added optional "type" attribute in <launch:create> to enable the
client to explicitly define the desired type of object client to explicitly define the desired type of object
(application or registration) to create to all forms of the (application or registration) to create to all forms of the
create extension. create extension.
3. Added text that the server SHOULD validate the <launch:phase> 3. Added text that the server SHOULD validate the <launch:phase>
element in the Launch Phases section. element in the Launch Phases section.
skipping to change at page 48, line 36 skipping to change at page 56, line 5
Claims Create Model), where a trademark (encoded signed mark, Claims Create Model), where a trademark (encoded signed mark,
etc.) and notice can be passed, based on a request from James etc.) and notice can be passed, based on a request from James
Mitchell. Mitchell.
8. Added text for the handling of the overlapping "claims" and 8. Added text for the handling of the overlapping "claims" and
"landrush" launch phases. "landrush" launch phases.
9. Added support for two check forms (claims check form and 9. Added support for two check forms (claims check form and
availability check form) based on a request from James Mitchell. availability check form) based on a request from James Mitchell.
The availability check form was based on the text in draft-rbp- The availability check form was based on the text in draft-rbp-
application-epp-mapping. application-epp-mapping.
6.10. Change from 09 to 10 A.10. Change from 09 to 10
1. Changed noticeIDType from base64Binary to token to be compatible 1. Changed noticeIDType from base64Binary to token to be compatible
with draft-lozano-tmch-func-spec-05. with draft-lozano-tmch-func-spec-05.
2. Changed codeType from base64Binary to token to be more generic. 2. Changed codeType from base64Binary to token to be more generic.
3. Updated based on feedback from Alexander Mayrhofer, which 3. Updated based on feedback from Alexander Mayrhofer, which
include: include:
1. Changed "extension to the domain name extension" to 1. Changed "extension to the domain name extension" to
"extension to the domain name mapping". "extension to the domain name mapping".
2. Changed use of 2004 return code to 2306 return code when 2. Changed use of 2004 return code to 2306 return code when
skipping to change at page 49, line 28 skipping to change at page 56, line 45
name are supported" in the "Create Response" section. name are supported" in the "Create Response" section.
11. Changed the reference of 2303 (object does not exist) in the 11. Changed the reference of 2303 (object does not exist) in the
"Security Considerations" section to 2201 (authorization "Security Considerations" section to 2201 (authorization
error). error).
12. Added arrow from "invalid" status to "pendingValidation" 12. Added arrow from "invalid" status to "pendingValidation"
status and "pendingAllocation" status to "rejected" status status and "pendingAllocation" status to "rejected" status
in the State Transition Diagram. in the State Transition Diagram.
4. Added the "C:" and "S:" example prefixes and related text in the 4. Added the "C:" and "S:" example prefixes and related text in the
"Conventions Used in This Document" section. "Conventions Used in This Document" section.
6.11. Change from 10 to 11 A.11. Change from 10 to 11
1. Moved the claims check response <launch:chkData> element under 1. Moved the claims check response <launch:chkData> element under
the <extension> element instead of the <resData> element based on the <extension> element instead of the <resData> element based on
the request from Francisco Obispo. the request from Francisco Obispo.
6.12. Change from 11 to 12 A.12. Change from 11 to 12
1. Added support for multiple validator identifiers for claims 1. Added support for multiple validator identifiers for claims
notices and marks based on a request and text provided by Mike notices and marks based on a request and text provided by Mike
O'Connell. O'Connell.
2. Removed domain:exDate element from example in section 3.3.5 based 2. Removed domain:exDate element from example in section 3.3.5 based
on a request from Seth Goldman on the provreg list. on a request from Seth Goldman on the provreg list.
3. Added clarifying text for clients not passing the launch 3. Added clarifying text for clients not passing the launch
extension on update and delete commands to servers that do not extension on update and delete commands to servers that do not
support launch applications based on a request from Sharon support launch applications based on a request from Sharon
Wodjenski on the provreg list. Wodjenski on the provreg list.
6.13. Change from 12 to WG 00 A.13. Change from 12 to WG 00
1. Changed to eppext working group draft by changing draft-tan-epp- 1. Changed to eppext working group draft by changing draft-tan-epp-
launchphase to draft-ietf-eppext-launchphase and by changing launchphase to draft-ietf-eppext-launchphase and by changing
references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch- references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch-
smd. smd.
6.14. Change WG 00 to WG 01 A.14. Change WG 00 to WG 01
1. Removed text associated with support for the combining of status 1. Removed text associated with support for the combining of status
values based on feedback from Patrick Mevzek on the provreg values based on feedback from Patrick Mevzek on the provreg
mailing list, discussion on the eppext mailing list, and mailing list, discussion on the eppext mailing list, and
discussion at the eppext IETF meeting on March 6, 2014. discussion at the eppext IETF meeting on March 6, 2014.
6.15. Change WG 01 to WG 02 A.15. Change WG 01 to WG 02
1. Changed the <launch:claim> element to be zero or more elements 1. Changed the <launch:claim> element to be zero or more elements
and the <launch:notice> element to be one or more elements in the and the <launch:notice> element to be one or more elements in the
Claims Create Form. These changes were needed to be able to Claims Create Form. These changes were needed to be able to
support more than one concurrent claims services. support more than one concurrent claims services.
7. IANA Considerations A.16. Change WG 02 to WG 03
This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. One URI
assignment has been registered by the IANA.
Registration request for the Launch namespace:
URI: urn:ietf:params:xml:ns:launch-1.0
Registrant Contact: See the "Author's Address" section of this
document.
XML: None. Namespace URIs do not represent an XML specification.
8. Security Considerations
The mapping extensions described in this document do not provide any
security services beyond those described by EPP [RFC5730], the EPP
domain name mapping [RFC5731], and protocol layers used by EPP. The
security considerations described in these other specifications apply
to this specification as well.
Updates to, and deletion of an application object must be restricted
to clients authorized to perform the said operation on the object.
As information contained within an application, or even the mere fact
that an application exists may be confidential. Any attempt to
operate on an application object by an unauthorized client MUST be
rejected with an EPP 2201 (authorization error) return code. Server
policy may allow <info> operation with filtered output by clients
other than the sponsoring client, in which case the <domain:infData>
and <launch:infData> response SHOULD be filtered to include only
fields that are publicly accessible.
9. References
9.1. Normative References
[I-D.ietf-eppext-tmch-smd]
Lozano, G., "Mark and Signed Mark Objects Mapping", draft-
ietf-eppext-tmch-smd-00 (work in progress), January 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, August 2009.
9.2. URIs
[1] http://tools.ietf.org/html/draft-lozano-tmch-func-spec
[2] http://tools.ietf.org/html/draft-lozano-tmch-func-spec 1. Added the "Implementation Status" section based on an action item
from the eppext IETF-91 meeting.
2. Moved Section 7 "IANA Considerations" and Section 9 "Security
Considerations" before Section 5 "Acknowledgements". Moved
"Change Log" Section to end.
3. Updated the text for the Claims Check Form and the Claims Create
Form to support checking for the need of the claims notice and
passing the claims notice outside of the "claims" phase.
4. Added the new Trademark Check Form to support determining whether
or not a trademark exists that matches the domain name
independent of whether a claims notice is required on create.
This was based on a request from Trung Tran and a discussion on
the eppext mailing list.
Authors' Addresses Authors' Addresses
James Gould James Gould
VeriSign, Inc. VeriSign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US US
Email: jgould@verisign.com Email: jgould@verisign.com
 End of changes. 50 change blocks. 
175 lines changed or deleted 479 lines changed or added

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