draft-ietf-regext-launchphase-05.txt   draft-ietf-regext-launchphase-06.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: December 24, 2017 Cloud Registry Expires: February 22, 2018 Cloud Registry
G. Brown G. Brown
CentralNic Ltd CentralNic Ltd
June 22, 2017 August 21, 2017
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-launchphase-05 draft-ietf-regext-launchphase-06
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 December 24, 2017. This Internet-Draft will expire on February 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 31 skipping to change at page 2, line 31
2.6.2. <mark:mark> element . . . . . . . . . . . . . . . . . 16 2.6.2. <mark:mark> element . . . . . . . . . . . . . . . . . 16
2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 16 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 16
2.6.3.1. <smd:signedMark> element . . . . . . . . . . . . 16 2.6.3.1. <smd:signedMark> element . . . . . . . . . . . . 16
2.6.3.2. <smd:encodedSignedMark> element . . . . . . . . . 16 2.6.3.2. <smd:encodedSignedMark> element . . . . . . . . . 16
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 16 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 16
3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 17 3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 17
3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 17 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 17
3.1.2. Availability Check Form . . . . . . . . . . . . . . . 20 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 20
3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 22 3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 22
3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 25 3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 25
3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 28 3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 29
3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 28 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 29
3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 34 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 35
3.3.3. General Create Form . . . . . . . . . . . . . . . . . 37 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 38
3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 38 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 39
3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 40 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 41
3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 41 3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 42
3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 42 3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 43
3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 43 3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 44
3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 44 3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 45
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 44 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 45
4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 44 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 45
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 51 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 52
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 52 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 53
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 52 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 53
6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 53 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 54
6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 53 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 54
6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 54 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 55
6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 54 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 55
6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 54 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 55
6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 55 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 56
6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 55 6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 56
7. Security Considerations . . . . . . . . . . . . . . . . . . . 56 7. Security Considerations . . . . . . . . . . . . . . . . . . . 57
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 56 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 58
9.1. Normative References . . . . . . . . . . . . . . . . . . 57 9.1. Normative References . . . . . . . . . . . . . . . . . . 58
9.2. Informative References . . . . . . . . . . . . . . . . . 57 9.2. Informative References . . . . . . . . . . . . . . . . . 58
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 57 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 58
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 57 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 59
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 58 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 59
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 58 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 59
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 58 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 59
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 58 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 60
A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 59 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 60
A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 59 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 60
A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 59 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 60
A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 59 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 61
A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 60 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 61
A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 61 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 62
A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 61 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 62
A.13. Change from 12 to EPPEXT 00 . . . . . . . . . . . . . . . 61 A.13. Change from 12 to EPPEXT 00 . . . . . . . . . . . . . . . 62
A.14. Change EPPEXT 00 to EPPEXT 01 . . . . . . . . . . . . . . 61 A.14. Change EPPEXT 00 to EPPEXT 01 . . . . . . . . . . . . . . 63
A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 62 A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 63
A.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 62 A.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 63
A.17. Change EPPEXT 03 to EPPEXT 04 . . . . . . . . . . . . . . 62 A.17. Change EPPEXT 03 to EPPEXT 04 . . . . . . . . . . . . . . 63
A.18. Change EPPEXT 04 to EPPEXT 05 . . . . . . . . . . . . . . 62 A.18. Change EPPEXT 04 to EPPEXT 05 . . . . . . . . . . . . . . 63
A.19. Change EPPEXT 05 to EPPEXT 06 . . . . . . . . . . . . . . 62 A.19. Change EPPEXT 05 to EPPEXT 06 . . . . . . . . . . . . . . 63
A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 63 A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 64
A.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 63 A.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 64
A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 63 A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 64
A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 63 A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 64
A.24. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 63 A.24. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 64
A.25. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 63 A.25. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 64
A.26. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 64 A.26. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 65
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 64 A.27. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 65
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65
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 4, line 40 skipping to change at page 4, line 41
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the and examples provided in this document MUST be interpreted in the
character case presented in order to develop a conforming character case presented in order to develop a conforming
implementation. implementation.
In examples, "C:" represents lines sent by a protocol client and "S:" In examples, "C:" represents lines sent by a protocol client and "S:"
represents lines returned by a protocol server. Indentation and represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element white space in examples are provided only to illustrate element
relationships and are not a REQUIRED feature of this protocol. relationships and are not a REQUIRED feature of this protocol.
A Launch Registration is a domain name registration during a launch
phase when the server uses a "first-come, first-served" model. Only
a single registration for a domain name can exist in the server at a
time.
A Launch Application represents the intent to register a domain name
during a launch phase when the server accepts multiple applications
for a domain name and the server later selects one of the
applications to allocate as a registration. Many Launch Applications
for a domain name can exist in the server at a time.
"launch-1.0" is used as an abbreviation for "launch-1.0" is used as an abbreviation for
"urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix
"launch" is used, but implementations MUST NOT depend on it and "launch" is used, but implementations MUST NOT depend on it and
instead employ a proper namespace-aware XML parser and serializer to instead employ a proper namespace-aware XML parser and serializer to
interpret and output the XML documents. interpret and output the XML documents.
"signedMark-1.0" is used as an abbreviation for "signedMark-1.0" is used as an abbreviation for
"urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [RFC7848]. "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [RFC7848].
The XML namespace prefix "smd" is used, but implementations MUST NOT The XML namespace prefix "smd" is used, but implementations MUST NOT
depend on it and instead employ a proper namespace-aware XML parser depend on it and instead employ a proper namespace-aware XML parser
skipping to change at page 5, line 32 skipping to change at page 5, line 44
corresponding to the request, assign an application identifier for corresponding to the request, assign an application identifier for
the Launch Application, set the [RFC5731] pendingCreate status, and the Launch Application, set the [RFC5731] pendingCreate status, and
return the application identifier to the client with the return the application identifier to the client with the
<launch:applicationID> element. In order to facilitate correlation, <launch:applicationID> element. In order to facilitate correlation,
all subsequent launch operations on the Launch Application MUST be all subsequent launch operations on the Launch Application MUST be
qualified by the previously assigned application identifier using the qualified by the previously assigned application identifier using the
<launch:applicationID> element. <launch:applicationID> element.
2.2. Validator Identifier 2.2. Validator Identifier
The Validator Identifier is the unique identifier for a Trademark The Validator Identifier is the identifier, that is unique to the
Validator that validates marks and has a repository of validated server, for a Trademark Validator that validates marks and has a
marks. The OPTIONAL "validatorID" attribute is used to define the repository of validated marks. The OPTIONAL "validatorID" attribute
Validator Identifier of the Trademark Validator. Registries MAY is used to define the Validator Identifier of the Trademark
support more than one Third Party Trademark Validator. The Internet Validator. Registries MAY support more than one Third Party
Trademark Validator. The unique set of Validator Identifier values
supported by the server is up to server policy. The Internet
Corporation for Assigned Names and Numbers (ICANN) Trademark Corporation for Assigned Names and Numbers (ICANN) Trademark
Clearinghouse (TMCH) is the default Trademark Validator and is Clearinghouse (TMCH) is the default Trademark Validator and is
reserved the Validator Identifier of "tmch". If the ICANN TMCH is reserved the Validator Identifier of "tmch". If the ICANN TMCH is
not used or multiple Trademark Validators are used, the Validator not used or multiple Trademark Validators are used, the Validator
Identifier MUST be defined using the "validatorID" attribute. Identifier MUST be defined using the "validatorID" attribute.
The Validator Identifier MAY be related to one or more issuer The Validator Identifier MAY be related to one or more issuer
identifiers of the <mark:id> element and the <smd:id> element defined identifiers of the <mark:id> element and the <smd:id> element defined
in [RFC7848]. Both the Validator Identifier and the Issuer in [RFC7848]. Both the Validator Identifier and the Issuer
Identifier used MUST be unique. If the ICANN TMCH is not used or Identifier used MUST be unique. If the ICANN TMCH is not used or
skipping to change at page 6, line 15 skipping to change at page 6, line 27
The Validator Identifier MAY define a non-Trademark Validator that The Validator Identifier MAY define a non-Trademark Validator that
supports a form of claims. supports a form of claims.
2.3. Launch Phases 2.3. Launch Phases
The server MAY support multiple launch phases sequentially or The server MAY support multiple launch phases sequentially or
simultaneously. The <launch:phase> element MUST be included by the simultaneously. The <launch:phase> element MUST be included by the
client to define the target launch phase of the command. The server client to define the target launch phase of the command. The server
SHOULD validate the phase and MAY validate the sub-phase of the SHOULD validate the phase and MAY validate the sub-phase of the
<launch:phase> element against the active phase and OPTIONAL sub- <launch:phase> element against the active phase and OPTIONAL sub-
phase of the server on a create command, and return an EPP error phase of the server, and return an EPP error result code of 2306 if
result code of 2306 if there is a mismatch. there is a mismatch.
The following launch phase values are defined: The following launch phase values are defined:
sunrise The phase during which trademark holders can submit sunrise The phase during which trademark holders can submit
registrations or applications with trademark information that can registrations or applications with trademark information that can
be validated by the server. be validated by the server.
landrush A post-Sunrise phase when non-trademark holders are allowed landrush A post-Sunrise phase when non-trademark holders are allowed
to register domain names with steps taken to address a large to register domain names with steps taken to address a large
volume of initial registrations. volume of initial registrations.
claims The phase, as defined in the Section 2.3.1, in which a Claims claims The phase, as defined in the Section 2.3.1, in which a Claims
skipping to change at page 7, line 9 skipping to change at page 7, line 17
launch phase. The overlap of the "claims" and "landrush" launch launch phase. The overlap of the "claims" and "landrush" launch
phases SHOULD be handled by setting "claims" as the <launch:phase> phases SHOULD be handled by setting "claims" as the <launch:phase>
value and setting "landrush" as the sub-phase with the "name" value and setting "landrush" as the sub-phase with the "name"
attribute. For example, the <launch:phase> element SHOULD be attribute. For example, the <launch:phase> element SHOULD be
<launch:phase name="landrush">claims</launch:phase>. <launch:phase name="landrush">claims</launch:phase>.
2.3.1. Trademark Claims Phase 2.3.1. Trademark Claims Phase
The Trademark Claims Phase is when a Claims Notice MUST be displayed The Trademark Claims Phase is when a Claims Notice MUST be displayed
to a prospective registrant of a domain name that matches trademarks. to a prospective registrant of a domain name that matches trademarks.
The source of the trademarks is a Trademark Validator and the source See [I-D.ietf-regext-tmch-func-spec] for additional details of
of the Claims Notice information is a Claim Notice Information trademark claims handling. The source of the trademarks is a
Service (CNIS), which MAY be directly linked to a Trademark Trademark Validator and the source of the Claims Notice information
Validator. The client interfaces with the server to determine if a is a Claim Notice Information Service (CNIS), which MAY be directly
trademark exists for a domain name, interfaces with a CNIS to get the linked to a Trademark Validator. The client interfaces with the
Claims Notice information, and interfaces with the server to pass the server to determine if a trademark exists for a domain name,
Claims Notice acceptance information in a create command. This interfaces with a CNIS to get the Claims Notice information, and
document supports the Trademark Claims Phase in two ways including: interfaces with the server to pass the Claims Notice acceptance
information in a create command. This document supports the
Trademark Claims Phase in two ways including:
Claims Check Form Claims Check Form (Section 3.1.1) is used to Claims Check Form Claims Check Form (Section 3.1.1) is used to
determine whether or not there are any matching trademarks for a determine whether or not there are any matching trademarks for a
domain name. If there is at least one matching trademark that domain name. If there is at least one matching trademark that
exists for the domain name, a claims key is returned. The mapping exists for the domain name, a claims key is returned. The mapping
of domain names and the claims keys is based on an out-of-band of domain names and the claims keys is based on an out-of-band
interface between the server and the Trademark Validator. The interface between the server and the Trademark Validator. The
CNIS associated with the claims key Validator Identifier CNIS associated with the claims key Validator Identifier
(Section 2.2) MUST accept the claims key as the basis for (Section 2.2) MUST accept the claims key as the basis for
retrieving the claims information. retrieving the claims information.
Claims Create Form Claims Create Form (Section 3.3.2) is used to Claims Create Form Claims Create Form (Section 3.3.2) is used to
pass the Claims Notice acceptance information in a create command. pass the Claims Notice acceptance information in a create command.
The notice identifier (<launch:noticeID>) format, validation The notice identifier (<launch:noticeID>) format, validation
rules, and server processing is up to the interface between the rules, and server processing is up to the interface between the
server and the Trademark Validator. The CNIS associated with the server and the Trademark Validator. The CNIS associated with the
Validator Identifier (Section 2.2) MUST generate a notice Validator Identifier (Section 2.2) MUST generate a notice
identifier compliant with the <launch:noticeID> element. identifier compliant with the <launch:noticeID> element.
The following shows the Trademark Claims Phase registration flow: The following shows the Trademark Claims Phase registration flow:
.------------. .--------. .--------. .------. .------------. .--------. .--------. .------.
| Registrant | | Client | | Server | | CNIS | | Registrant | | Client | | Server | | CNIS |
'------------' '--------' '--------' '------' '------------' '--------' '--------' '------'
| Request Domain | | | | Request Domain | | |
| Registration | | | | Registration | | |
|--------------->| Domain Check | | |--------------->| Domain Check | |
| |--------------------------->| | | |--------------------------->| |
| Domain | Domain Unavailable .------------. | | Domain | Domain Unavailable .------------. |
| Unavailable |<---------------------( Available? ) | | Unavailable |<---------------------( Available? ) |
|<---------------| No '------------' | |<---------------| No '------------' |
| | Domain Available | Yes | | | Domain Available | Yes |
| |<---------------------------| | | |<---------------------------| |
| | Domain Claims Check | | | | Domain Claims Check | |
| |--------------------------->| | | |--------------------------->| |
| | .---------. | | | .---------. |
| | / Does \ | | | Claims Don't Exist / Does \ |
| |<--------------------( Domain have ) | | |<--------------------( Domain have ) |
| | No \ Claims? / | | | No \ Claims? / |
| | '---------' | | | '---------' |
| | Domain Create | | Yes | | | Domain Create | | Yes |
| |--------------------------->| | | | |--------------------------->| | |
| Domain | Domain Registered | | | | Domain | Domain Registered | | |
| Registered |<---------------------------| | | | Registered |<---------------------------| | |
|<---------------| | | |<---------------| | |
| | | | | |
| | Claims Key | | | | Claims Exist with Claims Keys | |
| |<------------------------------' | | |<------------------------------' |
| | | | | |
.-----. | | Request Claims Info with Claims Key | .-----. | | Request Claims Info with Claims Key |
|Abort| | Display |-------------------------------------->| |Abort| | Display |-------------------------------------->|
'-----' | Claims | Return Claims Info | '-----' | Claims | Return Claims Info |
^ | Notice |<--------------------------------------| ^ | Notice |<--------------------------------------|
| No |<---------------| | | No |<---------------| |
| .------. Yes | | | .------. Yes | |
'-( Ack? )----------->| Domain Claims Create Form | | '-( Ack? )----------->| Domain Claims Create Form | |
'------' |--------------------------->| | '------' |--------------------------->| |
| Registration | Error .----------------------. | | Registration | Error .----------------------. |
| Error |<-----------( Validation Successful? ) | | Error |<-----------( Validation Successful? ) |
|<---------------| No '----------------------' | |<---------------| No '----------------------' |
| | | Yes | | | | Yes |
| Domain | Domain Registered | | | Domain | Domain Registered | |
| Registered |<---------------------------| | | Registered |<---------------------------| |
|<---------------| | | |<---------------| | |
Figure 1 Figure 1
2.4. Status Values 2.4. Status Values
A Launch Application or Launch Registration object MAY have a launch A Launch Application or Launch Registration object MAY have a launch
status value. The <launch:status> element is used to convey the status value. The <launch:status> element is used to convey the
launch status pertaining to the object, beyond what is specified in launch status pertaining to the object, beyond what is specified in
the object mapping. A Launch Application or Launch Registration MUST the object mapping. A Launch Application or Launch Registration MUST
set the [RFC5731] "pendingCreate" status if a launch status is set the [RFC5731] "pendingCreate" status if a launch status is
skipping to change at page 12, line 29 skipping to change at page 12, line 29
S: <domain:infData S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name> S: <domain:name>domain.example</domain:name>
S: ... S: ...
S: </domain:infData> S: </domain:infData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <launch:infData S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase> S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID> S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="pendingAllocation"/> S: <launch:status s="pendingAllocation"/>
S: </launch:infData> S: </launch:infData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
The following is an example <domain:panData> poll message for an The following is an example <domain:panData> poll message for an
"allocated" Launch Application. "allocated" Launch Application.
skipping to change at page 13, line 32 skipping to change at page 13, line 32
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID> S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate> S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData> S: </domain:panData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <launch:infData S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase> S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID> S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="allocated"/> S: <launch:status s="allocated"/>
S: </launch:infData> S: </launch:infData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>BCD-23456</clTRID> S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID> S: <svTRID>65432-WXY</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
The following is an example <domain:panData> poll message for an The following is an example <domain:panData> poll message for an
"allocated" Launch Registration. "allocated" Launch Registration.
skipping to change at page 14, line 32 skipping to change at page 14, line 32
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID> S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate> S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData> S: </domain:panData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <launch:infData S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase> S: <launch:phase>sunrise</launch:phase>
S: <launch:status s="allocated"/> S: <launch:status s="allocated"/>
S: </launch:infData> S: </launch:infData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>BCD-23456</clTRID> S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID> S: <svTRID>65432-WXY</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
2.6. Mark Validation Models 2.6. Mark Validation Models
skipping to change at page 18, line 6 skipping to change at page 18, line 6
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> Contains the value of the active launch phase of the <launch:phase> Contains the value of the active launch phase of the
server. The server SHOULD validate the value against the active server. The server SHOULD validate the value according to
server launch phase. Section 2.3.
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 "domain1.example", "domain2.example", and to determine if "domain1.example", "domain2.example", and
"domain3.example" require claims notices during the "claims" launch "domain3.example" require claims notices during 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>
skipping to change at page 21, line 15 skipping to change at page 21, line 15
"type" attribute to "avail". "type" attribute to "avail".
The EPP <check> command is used to determine if an object can be The EPP <check> command is used to determine if an object can be
provisioned within a repository. Domain names may be made available provisioned within a repository. Domain names may be made available
only in unique launch phases, whilst remaining unavailable for only in unique launch phases, whilst remaining unavailable for
concurrent launch phases. In addition to the elements expressed in concurrent launch phases. In addition to the elements expressed in
the <domain:check>, the command is extended with the <launch:check> the <domain:check>, the command is extended with the <launch:check>
element that contains the following child elements: element that contains the following child elements:
<launch:phase> The launch phase to which domain name availability <launch:phase> The launch phase to which domain name availability
should be determined. should be determined. The server SHOULD validate the value and
return an EPP error result code of 2306 if it is invalid.
Example Availability Check Form command using the <check> domain Example Availability Check Form command using the <check> domain
command and the <launch:check> extension with the "type" set to command and the <launch:check> extension with the "type" set to
"avail", to determine the availability of two domain names in the "avail", to determine the availability of two domain names in the
"idn-release" custom launch phase: "idn-release" custom 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>
skipping to change at page 25, line 14 skipping to change at page 25, line 14
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) can be used for retrieving information for a
Launch Application. A <launch:info> element is sent along with the Launch Application. A <launch:info> element is sent along with the
regular <info> domain command. The <launch:info> element includes an regular <info> domain command. The <launch:info> element includes an
OPTIONAL "includeMark" boolean attribute, with a default value of OPTIONAL "includeMark" boolean attribute, with a default value of
"false", to indicate whether or not to include the mark in the "false", to indicate whether or not to include the mark in the
response. The <launch:info> element contains the following child response. The <launch:info> element contains the following child
elements: elements:
<launch:phase> The phase during which the application or <launch:phase> The phase during which the application or
registration was submitted or is associated with. Server policy registration was submitted or is associated with. Server policy
defines the phases that are supported. defines the phases that are supported. The server SHOULD
validate the value and return an EPP error result code of 2306 if
it is invalid.
<launch:applicationID> OPTIONAL application identifier of the Launch <launch:applicationID> OPTIONAL application identifier of the Launch
Application. Application.
Example <info> domain command with the <launch:info> extension to Example <info> domain command with the <launch:info> extension to
retrieve information for the sunrise application for domain.example retrieve information for the sunrise application for domain.example
and application identifier "abc123": and application identifier "abc123":
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>
skipping to change at page 26, line 37 skipping to change at page 27, line 15
<launch:infData> element along with the regular EPP <resData>. The <launch:infData> element along with the regular EPP <resData>. The
<launch:infData> contains the following child elements: <launch:infData> contains the following child elements:
<launch:phase> The phase during which the application was submitted, <launch:phase> The phase during which the application was submitted,
or is associated with, that matches the associated <info> command or is associated with, that matches the associated <info> command
<launch:phase>. <launch:phase>.
<launch:applicationID> OPTIONAL Application Identifier of the Launch <launch:applicationID> OPTIONAL Application Identifier of the Launch
Application. Application.
<launch:status> OPTIONAL status of the Launch Application using one <launch:status> OPTIONAL status of the Launch Application using one
of the supported status values (Section 2.4). of the supported status values (Section 2.4).
<mark:mark> Zero or more <mark:mark> (Section 2.6.2) elements. <mark:mark> Zero or more <mark:mark> (Section 2.6.2) elements only
if the "includeMark" attribute is "true" in the command.
Example <info> domain response using the <launch:infData> extension Example <info> domain response using the <launch:infData> extension
with the mark information: with the mark information:
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>
skipping to change at page 28, line 49 skipping to change at page 29, line 49
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
passed by the client. passed by the client.
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, and return an EPP error result code of 2306 if the type is
incorrect. The <launch:create> element contains the following child
elements: elements:
<launch:phase> The identifier for the launch phase. <launch:phase> The identifier for the launch phase. The server
SHOULD validate the value according to Section 2.3.
<launch:codeMark> or <smd:signedMark> or <smd:encodedSignedMark> <launch:codeMark> or <smd:signedMark> or <smd:encodedSignedMark>
<launch:codeMark> Zero or more <launch:codeMark> elements. The <launch:codeMark> Zero or more <launch:codeMark> elements. The
<launch:codeMark> child elements are defined in the <launch:codeMark> child elements are defined in the
<launch:codeMark> element (Section 2.6.1) section. <launch:codeMark> element (Section 2.6.1) section.
<smd:signedMark> Zero or more <smd:signedMark> elements. The <smd:signedMark> Zero or more <smd:signedMark> elements. The
<smd:signedMark> child elements are defined in the <smd:signedMark> child elements are defined in the
<smd:signedMark> element (Section 2.6.3.1) section. <smd:signedMark> element (Section 2.6.3.1) section.
<smd:encodedSignedMark> Zero or more <smd:encodedSignedMark> <smd:encodedSignedMark> Zero or more <smd:encodedSignedMark>
elements. The <smd:encodedSignedMark> child elements are elements. The <smd:encodedSignedMark> child elements are
skipping to change at page 34, line 48 skipping to change at page 35, line 48
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. registrant's acceptance of the Claims Notice.
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, and return an EPP error result code of 2306 if the type is
incorrect. The <launch:create> element contains the following child
elements: elements:
<launch:phase> Contains the value of the active launch phase of the <launch:phase> Contains the value of the active launch phase of the
server. The server SHOULD validate the value against the active server. The server SHOULD validate the value according to
server launch phase. Section 2.3.
<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.
skipping to change at page 37, line 12 skipping to change at page 38, line 12
C: </command> C: </command>
C:</epp> C:</epp>
3.3.3. General Create Form 3.3.3. General Create Form
The General Create Form of the extension to the EPP domain name The General Create Form of the extension to the EPP domain name
mapping [RFC5731] includes the launch phase and optionally the object mapping [RFC5731] includes the launch phase and optionally the object
type to create. The OPTIONAL "type" attribute defines the expected type to create. The OPTIONAL "type" attribute defines the expected
type of object ("application" or "registration") to create. The type of object ("application" or "registration") to create. The
server SHOULD validate the "type" attribute, when passed, against the server SHOULD validate the "type" attribute, when passed, against the
type of object that will be created. type of object that will be created, and return an EPP error result
code of 2306 if the type is incorrect.
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 contains the following domain command. The <launch:create> element contains the following
child elements: child elements:
<launch:phase> Contains the value of the active launch phase of the <launch:phase> Contains the value of the active launch phase of the
server. The server SHOULD validate the value against the active server. The server SHOULD validate the value according to
server launch phase. Section 2.3.
The following is an example <create> domain command using the The following is an example <create> domain command using the
<launch:create> extension for a "landrush" launch phase application: <launch:create> extension for a "landrush" launch phase application:
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>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
skipping to change at page 40, line 7 skipping to change at page 41, line 7
C: </launch:acceptedDate> C: </launch:acceptedDate>
C: </launch:notice> C: </launch:notice>
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.5. Create Response 3.3.5. Create Response
If the create was successful, the server MAY reply with the If the create was successful, the server MAY add a <launch:creData>
<launch:creData> element along with the regular EPP <resData> to element along to the regular EPP <resData> to indicate the server
indicate the server generated Application Identifier (Section 2.1), generated Application Identifier (Section 2.1), when multiple
when multiple applications of a given domain name are supported; applications of a given domain name are supported; otherwise no
otherwise no extension is included with the regular EPP <resData>. extension is included with the regular EPP <resData>. The
The <launch:creData> element contains the following child elements: <launch:creData> element contains the following child elements:
<launch:phase> The phase of the application that mirrors the <launch:phase> The phase of the application that mirrors the
<launch:phase> element included in the <launch:create>. <launch:phase> element included in the <launch:create>.
<launch:applicationID> The application identifier of the <launch:applicationID> The application identifier of the
application. application.
An example response when multiple overlapping applications are An example response when multiple overlapping applications are
supported by the server: supported by the server:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
skipping to change at page 41, line 23 skipping to change at page 42, line 23
an EPP error result code of 2102 when receiving an EPP <update> an EPP error result code of 2102 when receiving an EPP <update>
command with the extension. command with the extension.
Registry policies permitting, clients may update an application Registry policies permitting, clients may update an application
object by submitting an EPP <update> command along with a object by submitting an EPP <update> command along with a
<launch:update> element to indicate the application object to be <launch:update> element to indicate the application object to be
updated. The <launch:update> element contains the following child updated. The <launch:update> element contains the following child
elements: elements:
<launch:phase> The phase during which the application was submitted <launch:phase> The phase during which the application was submitted
or is associated with. or is associated with. The server SHOULD validate the value and
return an EPP error result code of 2306 if it is invalid.
<launch:applicationID> The application identifier for which the <launch:applicationID> The application identifier for which the
client wishes to update. client wishes to update.
The following is an example <update> domain command with the The following is an example <update> domain command with the
<launch:update> extension to add and remove a name server of a <launch:update> extension to add and remove a name server of a
sunrise application with the application identifier "abc123": sunrise application with the application identifier "abc123":
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>
skipping to change at page 43, line 13 skipping to change at page 44, line 13
not support launch applications during its launch phase MUST return not support launch applications during its launch phase MUST return
an EPP error result code of 2102 when receiving an EPP <delete> an EPP error result code of 2102 when receiving an EPP <delete>
command with the extension. command with the extension.
Registry policies permitting, clients MAY withdraw an application by Registry policies permitting, clients MAY withdraw an application by
submitting an EPP <delete> command along with a <launch:delete> submitting an EPP <delete> command along with a <launch:delete>
element to indicate the application object to be deleted. The element to indicate the application object to be deleted. The
<launch:delete> element contains the following child elements: <launch:delete> element contains the following child elements:
<launch:phase> The phase during which the application was submitted <launch:phase> The phase during which the application was submitted
or is associated with. or is associated with. The server SHOULD validate the value and
return an EPP error result code of 2306 if it is invalid.
<launch:applicationID> The application identifier for which the <launch:applicationID> The application identifier for which the
client wishes to delete. client wishes to delete.
The following is an example <delete> domain command with the The following is an example <delete> domain command with the
<launch:delete> extension: <launch:delete> extension:
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: <delete> C: <delete>
skipping to change at page 46, line 13 skipping to change at page 47, line 13
<!-- <!--
Definition for application identifier Definition for application identifier
--> -->
<simpleType name="applicationIDType"> <simpleType name="applicationIDType">
<restriction base="token"/> <restriction base="token"/>
</simpleType> </simpleType>
<!-- <!--
Definition for launch phase. Name is an optional attribute Definition for launch phase. Name is an optional attribute
used to extend the phase type. For example, when used to extend the phase type. For example, when
using the phase type value of &qt;custom&gt;, the name using the phase type value of "custom", the name
can be used to specify the custom phase. can be used to specify the custom phase.
--> -->
<complexType name="phaseType"> <complexType name="phaseType">
<simpleContent> <simpleContent>
<extension base="launch:phaseTypeValue"> <extension base="launch:phaseTypeValue">
<attribute name="name" type="token"/> <attribute name="name" type="token"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
skipping to change at page 51, line 45 skipping to change at page 52, line 45
5. IANA Considerations 5. IANA Considerations
5.1. XML Namespace 5.1. XML Namespace
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]. conforming to a registry mechanism described in [RFC3688].
Registration request for the launch namespace: Registration request for the launch namespace:
URI: urn:ietf:params:xml:ns:launch-1.0 URI: urn:ietf:params:xml:ns:launch-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IESG
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the launch XML schema: Registration request for the launch XML schema:
URI: urn:ietf:params:xml:schema:launch-1.0 URI: urn:ietf:params:xml:schema:launch-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IESG
document.
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
5.2. EPP Extension Registry 5.2. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows: details of the registration are as follows:
Name of Extension: "Launch Phase Mapping for the Extensible Name of Extension: "Launch Phase Mapping for the Extensible
Provisioning Protocol (EPP)" Provisioning Protocol (EPP)"
skipping to change at page 56, line 23 skipping to change at page 57, line 23
The mapping extensions described in this document do not provide any The mapping extensions described in this document do not provide any
security services beyond those described by EPP [RFC5730], the EPP security services beyond those described by EPP [RFC5730], the EPP
domain name mapping [RFC5731], and protocol layers used by EPP. The domain name mapping [RFC5731], and protocol layers used by EPP. The
security considerations described in these other specifications apply security considerations described in these other specifications apply
to this specification as well. to this specification as well.
Updates to, and deletion of an application object must be restricted Updates to, and deletion of an application object must be restricted
to clients authorized to perform the said operation on the object. to clients authorized to perform the said operation on the object.
As information contained within an application, or even the mere fact Information contained within an application, or even the mere fact
that an application exists may be confidential. Any attempt to that an application exists may be confidential. Any attempt to
operate on an application object by an unauthorized client MUST be operate on an application object by an unauthorized client MUST be
rejected with an EPP 2201 (authorization error) return code. Server rejected with an EPP 2201 (authorization error) return code. Server
policy may allow <info> operation with filtered output by clients policy may allow <info> operation with filtered output by clients
other than the sponsoring client, in which case the <domain:infData> other than the sponsoring client, in which case the <domain:infData>
and <launch:infData> response SHOULD be filtered to include only and <launch:infData> response SHOULD be filtered to include only
fields that are publicly accessible. fields that are publicly accessible.
8. Acknowledgements 8. Acknowledgements
skipping to change at page 57, line 11 skipping to change at page 58, line 11
Some of the description of the Trademark Claims Phase was based on Some of the description of the Trademark Claims Phase was based on
the work done by Gustavo Lozano in the ICANN TMCH functional the work done by Gustavo Lozano in the ICANN TMCH functional
specifications. specifications.
9. References 9. References
9.1. Normative References 9.1. Normative References
[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, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc2119>. 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, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<http://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009, DOI 10.17487/RFC5731, August 2009, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5731>. editor.org/info/rfc5731>.
[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>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<http://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-regext-tmch-func-spec]
Lozano, G., "ICANN TMCH functional specifications", draft-
ietf-regext-tmch-func-spec-03 (work in progress), July
2017.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <http://www.rfc-editor.org/info/rfc7451>. February 2015, <https://www.rfc-editor.org/info/rfc7451>.
Appendix A. Change History Appendix A. Change History
A.1. Change from 00 to 01 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]".
A.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.
skipping to change at page 64, line 12 skipping to change at page 65, line 16
object in RFC 5731. object in RFC 5731.
6. Updated the copyright to 2017 in section 4.1. 6. Updated the copyright to 2017 in section 4.1.
A.26. Change from REGEXT 04 to REGEXT 05 A.26. Change from REGEXT 04 to REGEXT 05
1. Updates based on feedback from Ulrich Wisser that include: 1. Updates based on feedback from Ulrich Wisser that include:
1. Updated reference to obsoleted RFC 6982 with RFC 7942. 1. Updated reference to obsoleted RFC 6982 with RFC 7942.
2. Moved RFC 7451 reference from normative to informative. 2. Moved RFC 7451 reference from normative to informative.
A.27. Change from REGEXT 05 to REGEXT 06
1. Updates based on feedback from Adam Roach that include:
1. Added an informative reference to draft-ietf-regext-tmch-
func-spec in section 2.3.1 "Trademark Claims Phase".
2. Added formal definition of a Launch Registration and Launch
Application to section 1.1.
3. Updated the description of the Validator Identifier to
indicate that the uniqueness is based on server policy.
4. Updated "Does Domain have Claims?" "No" and "Yes" branch
labels in Figure 1.
5. Updated the description of the <launch:phase> element in the
commands to explicitly specify the return of a 2306 EPP
error result when invalid or referring to section 2.3 for
validation.
6. Fixed indentation of the <launch:applicationID> and
<launch:status> elements in the section 2.5 examples.
7. Updated the description of the <mark:mark> element in the
info response.
8. Added returning an EPP error result code of 2306 if the
"type" attribute is incorrect in section 3.3.1, 3.3.2, and
3.3.3.
9. Made small change in the description of the Create Response
in section 3.3.5.
10. Updated the Registrant Contact in section 7 to the IESG.
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
URI: http://www.verisigninc.com URI: http://www.verisigninc.com
 End of changes. 41 change blocks. 
163 lines changed or deleted 217 lines changed or added

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