draft-ietf-regext-launchphase-06.txt   draft-ietf-regext-launchphase-07.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: February 22, 2018 Cloud Registry Expires: June 15, 2018 Cloud Registry
G. Brown G. Brown
CentralNic Ltd CentralNic Ltd
August 21, 2017 December 12, 2017
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-launchphase-06 draft-ietf-regext-launchphase-07
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 February 22, 2018. This Internet-Draft will expire on June 15, 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 18 skipping to change at page 2, line 18
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 . . . . . . . . . . . . . . . . . . . . . . 5 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Application Identifier . . . . . . . . . . . . . . . . . 5 2.1. Application Identifier . . . . . . . . . . . . . . . . . 5
2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5 2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5
2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 6 2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 6
2.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 7 2.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 7
2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 9 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 9
2.4.1. State Transition . . . . . . . . . . . . . . . . . . 10 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 10
2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 11 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 12
2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 14 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 15
2.6.1. <launch:codeMark> element . . . . . . . . . . . . . . 15 2.6.1. <launch:codeMark> element . . . . . . . . . . . . . . 16
2.6.2. <mark:mark> element . . . . . . . . . . . . . . . . . 16 2.6.2. <mark:mark> element . . . . . . . . . . . . . . . . . 17
2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 16 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 17
2.6.3.1. <smd:signedMark> element . . . . . . . . . . . . 16 2.6.3.1. <smd:signedMark> element . . . . . . . . . . . . 17
2.6.3.2. <smd:encodedSignedMark> element . . . . . . . . . 16 2.6.3.2. <smd:encodedSignedMark> element . . . . . . . . . 17
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 16 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 17
3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 17 3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 18
3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 17 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 18
3.1.2. Availability Check Form . . . . . . . . . . . . . . . 20 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 21
3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 22 3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 23
3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 25 3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 26
3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 29 3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 30
3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 29 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 30
3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 35 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 36
3.3.3. General Create Form . . . . . . . . . . . . . . . . . 38 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 39
3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 39 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 40
3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 41 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 42
3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 42 3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 43
3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 43 3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 44
3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 44 3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 45
3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 45 3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 46
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 45 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 46
4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 45 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 46
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 52 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 54
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 53 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 54
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 53 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 55
6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 54 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 55
6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 54 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 56
6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 55 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 56
6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 55 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 57
6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 55 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 57
6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 56 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 58
6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 56 6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 58
7. Security Considerations . . . . . . . . . . . . . . . . . . . 57 7. Security Considerations . . . . . . . . . . . . . . . . . . . 58
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 59
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 58 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 59
9.1. Normative References . . . . . . . . . . . . . . . . . . 58 9.1. Normative References . . . . . . . . . . . . . . . . . . 59
9.2. Informative References . . . . . . . . . . . . . . . . . 58 9.2. Informative References . . . . . . . . . . . . . . . . . 60
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 58 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 60
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 59 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 60
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 59 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 60
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 59 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 61
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 59 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 61
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 60 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 61
A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 60 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 62
A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 60 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 62
A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 60 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 62
A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 61 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 62
A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 61 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 63
A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 62 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 64
A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 62 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 64
A.13. Change from 12 to EPPEXT 00 . . . . . . . . . . . . . . . 62 A.13. Change from 12 to EPPEXT 00 . . . . . . . . . . . . . . . 64
A.14. Change EPPEXT 00 to EPPEXT 01 . . . . . . . . . . . . . . 63 A.14. Change EPPEXT 00 to EPPEXT 01 . . . . . . . . . . . . . . 64
A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 63 A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 64
A.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 63 A.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 65
A.17. Change EPPEXT 03 to EPPEXT 04 . . . . . . . . . . . . . . 63 A.17. Change EPPEXT 03 to EPPEXT 04 . . . . . . . . . . . . . . 65
A.18. Change EPPEXT 04 to EPPEXT 05 . . . . . . . . . . . . . . 63 A.18. Change EPPEXT 04 to EPPEXT 05 . . . . . . . . . . . . . . 65
A.19. Change EPPEXT 05 to EPPEXT 06 . . . . . . . . . . . . . . 63 A.19. Change EPPEXT 05 to EPPEXT 06 . . . . . . . . . . . . . . 65
A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 64 A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 65
A.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 64 A.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 66
A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 64 A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 66
A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 64 A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 66
A.24. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 64 A.24. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 66
A.25. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 64 A.25. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 66
A.26. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 65 A.26. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 66
A.27. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 65 A.27. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 67
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65 A.28. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 67
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 70
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.
It is typical for domain registries to operate in special modes It is typical for domain registries to operate in special modes as
during their initial launch to facilitate allocation of domain names, they begin operation to facilitate allocation of domain names, often
often according to special rules. This document uses the term according to special rules. This document uses the term "launch
"launch phase" and the shorter form "launch" to refer to such a phase" and the shorter form "launch" to refer to such a period.
period. Multiple launch phases and multiple models are supported to enable
the launch of a domain name registry. What is supported and what is
validated is up to server policy. Communication of the server policy
is typically performed using an out-of-band mechanism that is not
specified in this document.
The EPP domain name mapping [RFC5731] is designed for the steady- The EPP domain name mapping [RFC5731] is designed for the steady-
state operation of a registry. During a launch period, the model in state operation of a registry. During a launch period, the model in
place may be different from what is defined in the EPP domain name place may be different from what is defined in the EPP domain name
mapping [RFC5731]. For example, registries often accept multiple mapping [RFC5731]. For example, registries often accept multiple
applications for the same domain name during the "Sunrise" launch applications for the same domain name during the "Sunrise" launch
phase, referred to as a Launch Application. A Launch Registration phase, referred to as a Launch Application. A Launch Registration
refers to a registration made during a launch phase when the server refers to a registration made during a launch phase when the server
uses a "first-come, first-served" model. Even in a "first-come, uses a "first-come, first-served" model. Even in a "first-come,
first-served" model, additional steps and information might be first-served" model, additional steps and information might be
skipping to change at page 4, line 39 skipping to change at page 4, line 46
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
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. The
use of "..." is used as shorthand for elements defined outside this
document.
A Launch Registration is a domain name registration during a launch A Launch Registration is a domain name registration during a launch
phase when the server uses a "first-come, first-served" model. Only 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 a single registration for a domain name can exist in the server at a
time. time.
A Launch Application represents the intent to register a domain name A Launch Application represents the intent to register a domain name
during a launch phase when the server accepts multiple applications during a launch phase when the server accepts multiple applications
for a domain name and the server later selects one of the for a domain name and the server later selects one of the
applications to allocate as a registration. Many Launch Applications applications to allocate as a registration. Many Launch Applications
for a domain name can exist in the server at a time. for a domain name can exist in the server at a time.
"launch-1.0" is used as an abbreviation for The XML namespace prefix "launch" is used for the namespace
"urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix "urn:ietf:params:xml:ns:launch-1.0", but implementations MUST NOT
"launch" is used, but implementations MUST NOT depend on it and depend on it and instead employ a proper namespace-aware XML parser
instead employ a proper namespace-aware XML parser and serializer to and serializer to interpret and output the XML documents.
interpret and output the XML documents.
"signedMark-1.0" is used as an abbreviation for The XML namespace prefix "smd" is used for the [RFC7848] namespace
"urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [RFC7848]. "urn:ietf:params:xml:ns:signedMark-1.0", 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
and serializer to interpret and output the XML documents. and serializer to interpret and output the XML documents.
"mark-1.0" is used as an abbreviation for The XML namespace prefix "mark" is used for the [RFC7848] namespace
"urn:ietf:params:xml:ns:mark-1.0" that is defined in [RFC7848]. The "urn:ietf:params:xml:ns:mark-1.0", but implementations MUST NOT
XML namespace prefix "mark" 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
and serializer to interpret and output the XML documents. and serializer to interpret and output the XML documents.
2. Object Attributes 2. Object Attributes
This extension adds additional elements to the EPP domain name This extension adds additional elements to the EPP domain name
mapping [RFC5731]. Only those new elements are described here. mapping [RFC5731]. Only those new elements are described here.
2.1. Application Identifier 2.1. Application Identifier
skipping to change at page 5, line 44 skipping to change at page 5, line 49
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 identifier, that is unique to the The Validator Identifier is the identifier unique to the server, for
server, for a Trademark Validator that validates marks and has a a Trademark Validator that validates marks and has a repository of
repository of validated marks. The OPTIONAL "validatorID" attribute validated marks. The OPTIONAL "validatorID" attribute is used to
is used to define the Validator Identifier of the Trademark define the Validator Identifier of the Trademark Validator.
Validator. Registries MAY support more than one Third Party Registries MAY support more than one Third Party Trademark Validator.
Trademark Validator. The unique set of Validator Identifier values The unique set of Validator Identifier values supported by the server
supported by the server is up to server policy. The Internet is up to server policy. The Internet Corporation for Assigned Names
Corporation for Assigned Names and Numbers (ICANN) Trademark and Numbers (ICANN) Trademark Clearinghouse (TMCH) is the default
Clearinghouse (TMCH) is the default Trademark Validator and is Trademark Validator and is reserved the Validator Identifier of
reserved the Validator Identifier of "tmch". If the ICANN TMCH is "tmch". If the ICANN TMCH is not used or multiple Trademark
not used or multiple Trademark Validators are used, the Validator Validators are used, the Validator Identifier MUST be defined using
Identifier MUST be defined using the "validatorID" attribute. 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 in the server. If the ICANN TMCH is
multiple Trademark Validators are used, the server MUST define the not used or multiple Trademark Validators are used, the server MUST
list of supported validator identifiers and MUST make this define the list of supported validator identifiers and MUST make this
information available to clients using a mutually acceptable, out-of- information available to clients using a mutually acceptable, out-of-
band mechanism. band mechanism.
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, where claims and a Validator Identifier
can be used for purposes beyond trademarks.
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, and return an EPP error result code of 2306 if phase of the server, and return an EPP error 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
to register domain names with steps taken to address a large allowed to register domain names with steps taken to address a
volume of initial registrations. large 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
Notice MUST be displayed to a prospective registrant of a domain Claims Notice must be displayed to a prospective registrant of a
name that matches trademarks. domain name that matches trademarks.
open A post-launch phase that is also referred to as "steady state". open: A phase that is also referred to as "steady state". Servers
Servers MAY require additional trademark protection during this may require additional trademark protection during this phase.
phase. custom: A custom server launch phase that is defined using the
custom A custom server launch phase that is defined using the "name" "name" attribute.
attribute.
For extensibility, the <launch:phase> element includes an OPTIONAL For extensibility, the <launch:phase> element includes an OPTIONAL
"name" attribute that can define a sub-phase, or the full name of the "name" attribute that can define a sub-phase, or the full name of the
phase when the <launch:phase> element has the "custom" value. For phase when the <launch:phase> element has the "custom" value. For
example, the "claims" launch phase could have two sub-phases that example, the "claims" launch phase could have two sub-phases that
include "landrush" and "open". include "landrush" and "open".
Launch phases MAY overlap to support the "claims" launch phase, Launch phases MAY overlap to support the "claims" launch phase,
defined in the Section 2.3.1, and to support a traditional "landrush" defined in the Section 2.3.1, and to support a traditional "landrush"
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.
See [I-D.ietf-regext-tmch-func-spec] for additional details of See [I-D.ietf-regext-tmch-func-spec] for additional details of
trademark claims handling. The source of the trademarks is a trademark claims handling. The source of the trademarks is a
Trademark Validator and the source of the Claims Notice information Trademark Validator and the source of the Claims Notice information
is a Claim Notice Information Service (CNIS), which MAY be directly is a Claim Notice Information Service (CNIS), which may be directly
linked to a Trademark Validator. The client interfaces with the linked to a Trademark Validator. The client interfaces with the
server to determine if a trademark exists for a domain name, server to determine if a trademark exists for a domain name,
interfaces with a CNIS to get the Claims Notice information, and interfaces with a CNIS to get the Claims Notice information, and
interfaces with the server to pass the Claims Notice acceptance interfaces with the server to pass the Claims Notice acceptance
information in a create command. This document supports the information in a create command. This document supports the
Trademark Claims Phase in two ways including: Trademark Claims Phase in two ways including:
Claims Check Form Claims Check Form (Section 3.1.1) is used to Claims Check Form: Is defined in Section 3.1.1 and 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: Is defined in Section 3.3.2 and is used to pass
pass the Claims Notice acceptance information in a create command. the Claims Notice acceptance information in a create command. The
The notice identifier (<launch:noticeID>) format, validation notice identifier (<launch:noticeID>) format, validation rules,
rules, and server processing is up to the interface between the and server processing is up to the interface between the server
server and the Trademark Validator. The CNIS associated with the 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 | | |
skipping to change at page 9, line 12 skipping to change at page 9, line 12
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
supported and the launch status is not one of the final statuses, supported and the launch status is not one of the final statuses
including the "allocated" and "rejected" statuses. ("allocated" and "rejected").
The following status values are defined using the required "s" The following status values are defined using the required "s"
attribute: attribute:
pendingValidation: The initial state of a newly-created application pendingValidation: The initial state of a newly-created application
or registration object. The application or registration requires or registration object. The application or registration requires
validation, but the validation process has not yet completed. validation, but the validation process has not yet completed.
validated: The application or registration meets relevant registry validated: The application or registration meets relevant registry
rules. rules.
invalid: The application or registration does not validate according invalid: The application or registration does not validate according
to registry rules. Server policies permitting, it may transition to registry rules. Server policies permitting, it may transition
back into "pendingValidation" for revalidation, after back into "pendingValidation" for revalidation, after
modifications are made to ostensibly correct attributes that modifications are made to ostensibly correct attributes that
caused the validation failure. caused the validation failure.
pendingAllocation: The allocation of the application or registration pendingAllocation: The allocation of the application or registration
is pending based on the results of some out-of-band process (for is pending based on the results of some out-of-band process (for
example, an auction). example, an auction).
allocated: The object corresponding to the application or allocated: The object corresponding to the application or
registration has been provisioned. Is a possible end state of an registration has been provisioned. This is a possible end state
application or registration object. of an application or registration object.
rejected: The application or registration object was not rejected: The application or registration object was not
provisioned. Is a possible end state of an application or provisioned. This is a possible end state of an application or
registration object. registration object.
custom: A custom status that is defined using the "name" attribute. custom: A custom status that is defined using the "name" attribute.
Each status value MAY be accompanied by a string of human-readable Each status value MAY be accompanied by a string of human-readable
text that describes the rationale for the status applied to the text that describes the rationale for the status applied to the
object. The OPTIONAL "lang" attribute MAY be present to identify the object. The OPTIONAL "lang" attribute, as defined in [RFC5646], MAY
language if the negotiated value is something other than the default be present to identify the language if the negotiated value is
value of "en" (English). something other than the default value of "en" (English).
For extensibility the <launch:status> element includes an OPTIONAL For extensibility the <launch:status> element includes an OPTIONAL
"name" attribute that can define a sub-status or the full name of the "name" attribute that can define a sub-status or the full name of the
status when the status value is "custom". The server SHOULD NOT use status when the status value is "custom". The server SHOULD use one
the "custom" status value. of the non-"custom" status values.
Status values MAY be skipped. For example, an application or Status values MAY be skipped. For example, an application or
registration MAY immediately start at the "allocated" status or an registration MAY immediately start at the "allocated" status or an
application or registration MAY skip the "pendingAllocation" status. application or registration MAY skip the "pendingAllocation" status.
If the launch phase does not require validation of a request, an If the launch phase does not require validation of a request, an
application or registration MAY immediately skip to application or registration MAY immediately skip to
"pendingAllocation". "pendingAllocation".
2.4.1. State Transition 2.4.1. State Transition
The transitions between the states is a matter of server policy.
This diagram defines one possible set of permitted transitions.
| request | request
| |
| +--------------------------+ | +--------------------------+
| | | | | |
v v | v v |
+-------------------+ | +-------------------+ |
| | | | | |
| pendingValidation +--------------+ | | pendingValidation +--------------+ |
| | | | | | | |
skipping to change at page 11, line 7 skipping to change at page 12, line 7
+---------+ +--------+ +---------+ +--------+
/ \ / \ / \ / \
| allocated | | rejected | | allocated | | rejected |
\ / \ / \ / \ /
+---------+ +--------+ +---------+ +--------+
Figure 2 Figure 2
2.5. Poll Messaging 2.5. Poll Messaging
A Launch Application MUST and a Launch Registration MAY be handled as A Launch Application MUST be handled as an EPP domain name object as
an EPP domain name object as specified in RFC 5731 [RFC5731] in specified in RFC 5731 [RFC5731], with the "pendingCreate" status and
"pendingCreate" status, with the launch status values defined in with the launch status values defined in Section 2.4. A Launch
Section 2.4. As a Launch Application or Launch Registration Registration MUST be handled as an EPP domain name object as
transitions between the status values defined in Section 2.4, the specified in RFC 5731 [RFC5731], with the "pendingCreate" status and
server SHOULD insert poll messages, per [RFC5730], for the applicable with the launch status values defined in Section 2.4 As a Launch
intermediate statuses, including the "pendingValidation", Application or Launch Registration transitions between the status
"validated", "pendingAllocation, and "invalid" statuses, using the values defined in Section 2.4, the server SHOULD insert poll
<domain:infData> element with the <launch:infData> extension. The messages, per [RFC5730], for the applicable intermediate statuses,
<domain:infData> element MAY contain non-mandatory information, like including the "pendingValidation", "validated", "pendingAllocation,
contact and name server information. Also, further extensions that and "invalid" statuses, using the <domain:infData> element with the
would normally be included in the response of a <domain:info> <launch:infData> extension. The <domain:infData> element MAY contain
command, per [RFC5731], MAY be included. For the final statuses, non-mandatory information, like contact and name server information.
including the "allocated" and "rejected" statuses, the server MUST Also, further extensions that would normally be included in the
insert a <domain:panData> poll message, per [RFC5731], with the response of a <domain:info> command, per [RFC5731], MAY be included.
<launch:infData> extension. For the final statuses, including the "allocated" and "rejected"
statuses, the server MUST insert a <domain:panData> poll message, per
[RFC5731], with the <launch:infData> extension.
The following is an example poll message for a Launch Application The following is an example poll message for a Launch Application
that has transitioned to the "pendingAllocation" state. that has transitioned to the "pendingAllocation" state.
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="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
skipping to change at page 14, line 47 skipping to change at page 15, line 47
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
A server MUST support at least one of the following models for A server MUST support at least one of the following models for
validating trademark information: validating trademark information:
code Use of a mark code by itself to validate that the mark matches code: Use of a mark code by itself to validate that the mark matches
the domain name. This model is supported using the the domain name. This model is supported using the
<launch:codeMark> element with just the <launch:code> element. <launch:codeMark> element with just the <launch:code> element.
mark The mark information is passed without any other validation mark: The mark information is passed without any other validation
element. The server will use some custom form of validation to element. The server will use some custom form of validation to
validate that the mark information is authentic. This model is validate that the mark information is authentic. This model is
supported using the <launch:codeMark> element with just the supported using the <launch:codeMark> element with just the
<mark:mark> (Section 2.6.2) element. <mark:mark> (Section 2.6.2) element.
code with mark: A code is used along with the mark information by code with mark: A code is used along with the mark information by
the server to validate the mark utilizing an external party. The the server to validate the mark utilizing an external party. The
code represents some form of secret that matches the mark code represents some form of secret that matches the mark
information passed. This model is supported using the information passed. This model is supported using the
<launch:codeMark> element that contains both the <launch:code> and <launch:codeMark> element that contains both the <launch:code> and
the <mark:mark> (Section 2.6.2) elements. the <mark:mark> (Section 2.6.2) elements.
skipping to change at page 15, line 28 skipping to change at page 16, line 28
(Section 2.6.3.1) and <smd:encodedSignedMark> (Section 2.6.3.2) (Section 2.6.3.1) and <smd:encodedSignedMark> (Section 2.6.3.2)
elements. elements.
More than one <launch:codeMark>, <smd:signedMark> (Section 2.6.3.1), More than one <launch:codeMark>, <smd:signedMark> (Section 2.6.3.1),
or <smd:encodedSignedMark> (Section 2.6.3.2) element MAY be or <smd:encodedSignedMark> (Section 2.6.3.2) element MAY be
specified. The maximum number of marks per domain name is up to specified. The maximum number of marks per domain name is up to
server policy. server policy.
2.6.1. <launch:codeMark> element 2.6.1. <launch:codeMark> element
The <launch:codeMark> element that is used by the "code", "mark", and The <launch:codeMark> element is used by the "code", "mark", and
"code with mark" validation models, has the following child elements: "code with mark" validation models, has the following child elements:
<launch:code>: OPTIONAL mark code used to validate the <mark:mark> <launch:code>: OPTIONAL mark code used to validate the <mark:mark>
(Section 2.6.2) information. The mark code is be a mark-specific (Section 2.6.2) information. The mark code is be a mark-specific
secret that the server can verify against a third party. The secret that the server can verify against a third party. The
OPTIONAL "validatorID" attribute is the Validator Identifier OPTIONAL "validatorID" attribute is the Validator Identifier
(Section 2.2) whose value indicates which Trademark Validator that (Section 2.2) whose value indicates which Trademark Validator that
the code originated from, with no default value. the code originated from, with no default value.
<mark:mark>: OPTIONAL mark information with child elements defined <mark:mark>: OPTIONAL mark information with child elements defined
in the Mark (Section 2.6.2) section. in the Mark (Section 2.6.2) section.
skipping to change at page 16, line 16 skipping to change at page 17, line 16
A <mark:mark> element describes an applicant's prior right to a given A <mark:mark> element describes an applicant's prior right to a given
domain name that is used with the "mark", "mark with code", and the domain name that is used with the "mark", "mark with code", and the
"signed mark" validation models. The <mark:mark> element is defined "signed mark" validation models. The <mark:mark> element is defined
in [RFC7848]. A new mark format can be supported by creating a new in [RFC7848]. A new mark format can be supported by creating a new
XML schema for the mark that has an element that substitutes for the XML schema for the mark that has an element that substitutes for the
<mark:abstractMark> element from [RFC7848]. <mark:abstractMark> element from [RFC7848].
2.6.3. Digital Signature 2.6.3. Digital Signature
Digital signatures MAY be used by the server to validate either the Digital signatures MAY be used by the server to validate the mark
mark information, when using the "signed mark" validation model with information, when using the "signed mark" validation model with the
the <smd:signedMark> (Section 2.6.3.1) element or the <smd:signedMark> (Section 2.6.3.1) element and the
<smd:encodedSignedMark> (Section 2.6.3.2) element. <smd:encodedSignedMark> (Section 2.6.3.2) element. When using
digital signatures the server MUST validate the digital signature.
2.6.3.1. <smd:signedMark> element 2.6.3.1. <smd:signedMark> element
The <smd:signedMark> element contains the digitally signed mark The <smd:signedMark> element contains the digitally signed mark
information. The <smd:signedMark> element is defined in [RFC7848]. information. The <smd:signedMark> element is defined in [RFC7848].
A new signed mark format can be supported by creating a new XML A new signed mark format can be supported by creating a new XML
schema for the signed mark that has an element that substitutes for schema for the signed mark that has an element that substitutes for
the <smd:abstractSignedMark> element from [RFC7848]. the <smd:abstractSignedMark> element from [RFC7848].
2.6.3.2. <smd:encodedSignedMark> element 2.6.3.2. <smd:encodedSignedMark> element
skipping to change at page 18, line 5 skipping to change at page 19, line 5
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> 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 according to server. The server SHOULD validate the value according to
Section 2.3. 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"?>
skipping to change at page 18, line 42 skipping to change at page 19, line 42
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 phase that mirrors the <launch:phase> element <launch:phase>: The phase that mirrors the <launch:phase> element
included in the <launch:check>. 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 that requires the use of the "Claims Create Form" domain name that requires the use of the "Claims Create Form"
on a Domain Create Command. A value of "1" (or "true") means on a Domain Create Command. A value of "1" (or "true") means
that a matching trademark does exist and that the "Claims that a matching trademark does exist and that the "Claims
Create Form" is required on a Domain Create Command. A value Create Form" is required on a Domain Create Command. A value
of "0" (or "false") means that a matching trademark does not of "0" (or "false") means that a matching trademark does not
exist or that the "Claims Create Form" is NOT required on a exist or that the "Claims Create Form" is NOT required on a
Domain Create Command. 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 ICANN passed to a third-party Trademark Validator such as the ICANN
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 identifier to
support other forms of claims notices. support other forms of claims notices.
Example Claims Check response when a claims notice is not required Example Claims Check response when a claims notice is not required
for the domain name domain1.example, a claims notice is required for for the domain name domain1.example, a claims notice is required for
the domain name domain2.example in the "tmch", and a claims notice is the domain name domain2.example in the "tmch", and a claims notice is
required for the domain name domain3.example in the "tmch" and required for the domain name domain3.example in the "tmch" and
"custom-tmch", for the "claims" launch phase: "custom-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">
skipping to change at page 21, line 14 skipping to change at page 22, line 14
response. This form MUST be identified by setting the <launch:check> response. This form MUST be identified by setting the <launch:check>
"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. The server SHOULD validate the value and should be determined. The server SHOULD validate the value and
return an EPP error result code of 2306 if it is invalid. 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">
skipping to change at page 23, line 35 skipping to change at page 24, line 35
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: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. A value of "1" (or "true") means that a
matching trademark does exist. A value of "0" (or "false") matching trademark does exist. A value of "0" (or "false")
means that a matching trademark does not exist. means that a matching trademark does not exist.
<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 ICANN passed to a third-party Trademark Validator such as the ICANN
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 identifier to
support other forms of claims notices. support other forms of claims notices.
Example Trademark Check response when no matching trademarks are Example Trademark Check response when no matching trademarks are
found for the domain name domain1.example, matching trademarks are found for the domain name domain1.example, matching trademarks are
found for the domain name domain2.example in the "tmch", matching found for the domain name domain2.example in the "tmch", matching
trademarks are found for domain name domain3.example in the "tmch" trademarks are found for domain name domain3.example in the "tmch"
and "custom-tmch", for the "claims" launch phase: and "custom-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">
skipping to change at page 25, line 22 skipping to change at page 26, line 22
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) can be 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. The server SHOULD defines the phases that are supported. The server SHOULD
validate the value and return an EPP error result code of 2306 if validate the value and return an EPP error result code of 2306 if
it is invalid. it is invalid.
<launch:applicationID> OPTIONAL application identifier of the Launch <launch:applicationID>: OPTIONAL application identifier of the
Application. Launch 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>
C: <info> C: <info>
C: <domain:info C: <domain:info
skipping to change at page 27, line 8 skipping to change at page 28, line 8
C: <launch:phase>sunrise</launch:phase> C: <launch:phase>sunrise</launch:phase>
C: </launch:info> C: </launch:info>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
If the query was successful, the server replies with a If the query was successful, the server replies with a
<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
or is associated with, that matches the associated <info> command submitted, or is associated with, that matches the associated
<launch:phase>. <info> command <launch:phase>.
<launch:applicationID> OPTIONAL Application Identifier of the Launch <launch:applicationID>: OPTIONAL Application Identifier of the
Application. Launch 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 only <mark:mark>: Zero or more <mark:mark> (Section 2.6.2) elements only
if the "includeMark" attribute is "true" in the command. 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>
skipping to change at page 29, line 13 skipping to change at page 30, line 13
S:</epp> S:</epp>
3.3. EPP <create> Command 3.3. EPP <create> Command
There are four forms of the extension to the EPP <create> command There are four forms of the extension to the EPP <create> command
that include the Sunrise Create Form (Section 3.3.1), the Claims that include the Sunrise Create Form (Section 3.3.1), the Claims
Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), Create Form (Section 3.3.2), the General Create Form (Section 3.3.3),
and the Mixed Create Form (Section 3.3.4). The form is dependent on and the Mixed Create Form (Section 3.3.4). The form is dependent on
the supported launch phases (Section 2.3) as defined below. the supported launch phases (Section 2.3) as defined below.
sunrise The EPP <create> command with the "sunrise" launch phase is sunrise: The EPP <create> command with the "sunrise" launch phase is
used to submit a registration with trademark information that can used to submit a registration with trademark information that can
be verified by the server with the <domain:name> value. The be verified by the server with the <domain:name> value. The
Sunrise Create Form (Section 3.3.1) is used for the "sunrise" Sunrise Create Form (Section 3.3.1) is used for the "sunrise"
launch phase. launch phase.
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. Use of 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 the Claims Create Form (Section 3.3.2) MAY be used to pass the
information associated with the presentation and acceptance of the information associated with the presentation and acceptance of the
Claims Notice if required for the domain name. 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
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, and return an EPP error result code of 2306 if the type is created, and return an EPP error result code of 2306 if the type is
incorrect. The <launch:create> element contains the following child incorrect. The <launch:create> element contains the following child
elements: elements:
<launch:phase> The identifier for the launch phase. The server <launch:phase>: The identifier for the launch phase. The server
SHOULD validate the value according to Section 2.3. 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
defined in the <smd:encodedSignedMark> element defined in the <smd:encodedSignedMark> element
(Section 2.6.3.2) section. (Section 2.6.3.2) section.
The following is an example <create> domain command using the The following is an example <create> domain command using the
<launch:create> extension, following the "code" validation model, <launch:create> extension, following the "code" validation model,
with multiple sunrise codes: with multiple sunrise codes:
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">
skipping to change at page 36, line 5 skipping to change at page 37, line 5
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, and return an EPP error result code of 2306 if the type is created, and return an EPP error result code of 2306 if the type is
incorrect. The <launch:create> element contains the following child 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 according to server. The server SHOULD validate the value according to
Section 2.3. 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.
<launch:acceptedDate> Contains the date and time that the claims <launch:acceptedDate>: Contains the date and time that the
notice was accepted. claims 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 38, line 19 skipping to change at page 39, line 19
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, and return an EPP error result type of object that will be created, and return an EPP error result
code of 2306 if the type is incorrect. 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 according to server. The server SHOULD validate the value according to
Section 2.3. 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>
skipping to change at page 41, line 14 skipping to change at page 42, line 14
3.3.5. Create Response 3.3.5. Create Response
If the create was successful, the server MAY add a <launch:creData> If the create was successful, the server MAY add a <launch:creData>
element along to the regular EPP <resData> to indicate the server element along to the regular EPP <resData> to indicate the server
generated Application Identifier (Section 2.1), when multiple generated Application Identifier (Section 2.1), when multiple
applications of a given domain name are supported; otherwise no applications of a given domain name are supported; otherwise no
extension is included with the regular EPP <resData>. The extension is included with the regular EPP <resData>. 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"?>
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="1001"> S: <result code="1001">
S: <msg>Command completed successfully; action pending</msg> S: <msg>Command completed successfully; action pending</msg>
skipping to change at page 42, line 10 skipping to change at page 43, line 10
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
3.4. EPP <update> Command 3.4. EPP <update> Command
This extension defines additional elements to extend the EPP <update> This extension defines additional elements to extend the EPP <update>
command to be used in conjunction with the domain name mapping. command to be used in conjunction with the domain name mapping.
A client MUST NOT pass the extension on an EPP <update> command to a An EPP <update> command with the extension sent to a server that does
server that does not support launch applications. A server that does not support launch applications will fail. A server that does not
not support launch applications during its launch phase MUST return support launch applications during its launch phase MUST return an
an EPP error result code of 2102 when receiving an EPP <update> EPP error result code of 2102 when receiving an EPP <update> command
command with the extension. 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. The server SHOULD validate the value and or is associated with. The server SHOULD validate the value and
return an EPP error result code of 2306 if it is invalid. 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>
C: <update> C: <update>
skipping to change at page 44, line 12 skipping to change at page 45, line 12
server that does not support launch applications. A server that does server that does not support launch applications. A server that does
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. The server SHOULD validate the value and or is associated with. The server SHOULD validate the value and
return an EPP error result code of 2306 if it is invalid. 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>
C: <domain:delete C: <domain:delete
skipping to change at page 46, line 14 skipping to change at page 47, line 14
BEGIN BEGIN
<?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"/>
<import namespace="urn:ietf:params:xml:ns:mark-1.0"/> <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:signedMark-1.0"/>
<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>
<!-- <!-- Child elements found in EPP commands -->
Child elements found in EPP commands. <element
--> name="check"
<element name="check" type="launch:checkType"/> type="launch:checkType"/>
<element name="info" type="launch:infoType"/> <element
<element name="create" type="launch:createType"/> name="info"
<element name="update" type="launch:idContainerType"/> type="launch:infoType"/>
<element name="delete" type="launch:idContainerType"/> <element
name="create"
type="launch:createType"/>
<element
name="update"
type="launch:idContainerType"/>
<element
name="delete"
type="launch:idContainerType"/>
<!-- <!-- Common container of id (identifier) element -->
Common container of id (identifier) element
-->
<complexType name="idContainerType"> <complexType name="idContainerType">
<sequence> <sequence>
<element name="phase" <element
type="launch:phaseType"/> name="phase"
<element name="applicationID" type="launch:phaseType"/>
type="launch:applicationIDType"/> <element
name="applicationID"
type="launch:applicationIDType"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!-- 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
Definition for launch phase. Name is an optional attribute optional attribute used to extend the phase type.
used to extend the phase type. For example, when For example, when using the phase type value
using the phase type value of "custom", the name of "custom", the name can be used to specify the
can be used to specify the custom phase. 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>
<!-- <!-- Enumeration of launch phase values -->
Enumeration of for launch phase values.
-->
<simpleType name="phaseTypeValue"> <simpleType name="phaseTypeValue">
<restriction base="token"> <restriction base="token">
<enumeration value="sunrise"/> <enumeration value="sunrise"/>
<enumeration value="landrush"/> <enumeration value="landrush"/>
<enumeration value="claims"/> <enumeration value="claims"/>
<enumeration value="open"/> <enumeration value="open"/>
<enumeration value="custom"/> <enumeration value="custom"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!-- Definition for the sunrise code -->
Definition for the sunrise code
-->
<simpleType name="codeValue"> <simpleType name="codeValue">
<restriction base="token"> <restriction base="token">
<minLength value="1"/> <minLength value="1"/>
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="codeType"> <complexType name="codeType">
<simpleContent> <simpleContent>
<extension base="launch:codeValue"> <extension base="launch:codeValue">
<attribute name="validatorID" <attribute
type="launch:validatorIDType" use="optional"/> name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!-- Definition for the notice identifier -->
Definition for the notice identifier
-->
<simpleType name="noticeIDValue"> <simpleType name="noticeIDValue">
<restriction base="token"> <restriction base="token">
<minLength value="1"/> <minLength value="1"/>
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="noticeIDType"> <complexType name="noticeIDType">
<simpleContent> <simpleContent>
<extension base="launch:noticeIDValue"> <extension base="launch:noticeIDValue">
<attribute name="validatorID" <attribute
type="launch:validatorIDType" use="optional"/> name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!-- Definition for the validator identifier -->
Definition for the validator identifier
-->
<simpleType name="validatorIDType"> <simpleType name="validatorIDType">
<restriction base="token"> <restriction base="token">
<minLength value="1"/> <minLength value="1"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!-- Possible status values for sunrise application -->
Possible status values for sunrise application <simpleType name="statusValueType">
-->
<simpleType name="statusValueType">
<restriction base="token"> <restriction base="token">
<enumeration value="pendingValidation"/> <enumeration value="pendingValidation"/>
<enumeration value="validated"/> <enumeration value="validated"/>
<enumeration value="invalid"/> <enumeration value="invalid"/>
<enumeration value="pendingAllocation"/> <enumeration value="pendingAllocation"/>
<enumeration value="allocated"/> <enumeration value="allocated"/>
<enumeration value="rejected"/> <enumeration value="rejected"/>
<enumeration value="custom"/> <enumeration value="custom"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!-- Status type definition -->
Status type definition
-->
<complexType name="statusType"> <complexType name="statusType">
<simpleContent> <simpleContent>
<extension base="normalizedString"> <extension base="normalizedString">
<attribute name="s" type="launch:statusValueType" <attribute
name="s"
type="launch:statusValueType"
use="required"/> use="required"/>
<attribute name="lang" type="language" <attribute
name="lang"
type="language"
default="en"/> default="en"/>
<attribute name="name" type="token"/> <attribute
name="name"
type="token"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!-- codeMark Type that contains an optional
codeMark Type that contains an optional code code with mark information -->
with mark information.
-->
<complexType name="codeMarkType"> <complexType name="codeMarkType">
<sequence> <sequence>
<element name="code" type="launch:codeType" <element
minOccurs="0"/> name="code"
<element ref="mark:abstractMark" type="launch:codeType"
minOccurs="0"/> minOccurs="0"/>
</sequence> <element
ref="mark:abstractMark"
minOccurs="0"/>
</sequence>
</complexType> </complexType>
<!-- <!-- Child elements for the create command -->
Child elements for the create command
-->
<complexType name="createType"> <complexType name="createType">
<sequence> <sequence>
<element name="phase" type="launch:phaseType"/> <element
name="phase"
type="launch:phaseType"/>
<choice minOccurs="0"> <choice minOccurs="0">
<element name="codeMark" type="launch:codeMarkType" <element
name="codeMark"
type="launch:codeMarkType"
maxOccurs="unbounded"/>
<element
ref="smd:abstractSignedMark"
maxOccurs="unbounded"/>
<element
ref="smd:encodedSignedMark"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<element ref="smd:abstractSignedMark"
maxOccurs="unbounded"/>
<element ref="smd:encodedSignedMark"
maxOccurs="unbounded"/>
</choice> </choice>
<element name="notice" <element
type="launch:createNoticeType" name="notice"
minOccurs="0" maxOccurs="unbounded"/> type="launch:createNoticeType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence> </sequence>
<attribute name="type" type="launch:objectType"/> <attribute
name="type"
type="launch:objectType"/>
</complexType> </complexType>
<!-- <!-- Type of launch object -->
Type of launch object
-->
<simpleType name="objectType"> <simpleType name="objectType">
<restriction base="token"> <restriction base="token">
<enumeration value="application"/> <enumeration value="application"/>
<enumeration value="registration"/> <enumeration value="registration"/>
</restriction> </restriction>
</simpleType> </simpleType>
<!-- <!-- Child elements of the create notice element -->
Child elements of the create notice element.
-->
<complexType name="createNoticeType"> <complexType name="createNoticeType">
<sequence> <sequence>
<element name="noticeID" type="launch:noticeIDType"/> <element
<element name="notAfter" type="dateTime"/> name="noticeID"
<element name="acceptedDate" type="dateTime"/> type="launch:noticeIDType"/>
<element
name="notAfter"
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"/> minOccurs="0"/>
</sequence> </sequence>
<attribute name="type" type="launch:checkFormType" <attribute
default="claims"/> name="type"
type="launch:checkFormType"
default="claims"/>
</complexType> </complexType>
<!-- <!-- Type of check form (Claims Check or Availability Check) -->
Type of check form
(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"/> <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
<element name="applicationID" name="phase"
type="launch:phaseType"/>
<element
name="applicationID"
type="launch:applicationIDType" type="launch:applicationIDType"
minOccurs="0"/> minOccurs="0"/>
</sequence> </sequence>
<attribute name="includeMark" type="boolean" <attribute
name="includeMark"
type="boolean"
default="false"/> default="false"/>
</complexType> </complexType>
<!-- <!-- Child response elements. -->
Child response elements. <element
--> name="chkData"
<element name="chkData" type="launch:chkDataType"/> type="launch:chkDataType"/>
<element name="creData" type="launch:idContainerType"/> <element
<element name="infData" type="launch:infDataType"/> name="creData"
type="launch:idContainerType"/>
<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
minOccurs="0"/> name="phase"
<element name="cd" type="launch:cdType" type="launch:phaseType"
maxOccurs="unbounded"/> minOccurs="0"/>
<element
name="cd"
type="launch:cdType"
maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<complexType name="cdType"> <complexType name="cdType">
<sequence> <sequence>
<element name="name" type="launch:cdNameType"/> <element
<element name="claimKey" type="launch:claimKeyType" name="name"
minOccurs="0" maxOccurs="unbounded"/> type="launch:cdNameType"/>
<element
name="claimKey"
type="launch:claimKeyType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<complexType name="cdNameType"> <complexType name="cdNameType">
<simpleContent> <simpleContent>
<extension base="eppcom:labelType"> <extension base="eppcom:labelType">
<attribute name="exists" type="boolean" <attribute
use="required"/> name="exists"
type="boolean"
use="required"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<complexType name="claimKeyType"> <complexType name="claimKeyType">
<simpleContent> <simpleContent>
<extension base="token"> <extension base="token">
<attribute name="validatorID" <attribute
type="launch:validatorIDType" use="optional"/> name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!-- <info> response elements -->
<info> response elements
-->
<complexType name="infDataType"> <complexType name="infDataType">
<sequence> <sequence>
<element name="phase" type="launch:phaseType"/> <element
<element name="applicationID" name="phase"
type="launch:applicationIDType" type="launch:phaseType"/>
minOccurs="0"/> <element
<element name="status" type="launch:statusType" name="applicationID"
minOccurs="0"/> type="launch:applicationIDType"
<element ref="mark:abstractMark" minOccurs="0"/>
minOccurs="0" maxOccurs="unbounded"/> <element
name="status"
type="launch:statusType"
minOccurs="0"/>
<element
ref="mark:abstractMark"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</schema> </schema>
END END
5. IANA Considerations 5. IANA Considerations
5.1. XML Namespace 5.1. XML Namespace
skipping to change at page 57, line 20 skipping to change at page 59, line 7
Contact: rik.ribbers@sidn.nl Contact: rik.ribbers@sidn.nl
7. Security Considerations 7. Security Considerations
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.
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
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, Scott were provided by Harald Alvestrand, Ben Campbell, Spencer Dawkins,
Hollenbeck, Michael Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, Jothan Frakes, Keith Gaughan, Seth Goldman, Scott Hollenbeck, Michael
Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Patrick Mevzek, Holloway, Jan Jansen, Rubens Kuhl, Mirja Kuhlewind, Warren Kumari,
James Mitchell, Francisco Obispo, Mike O'Connell, Bernhard Reutner- Ben Levac, Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Alexey
Fischer, Trung Tran, Ulrich Wisser and Sharon Wodjenski. Melnikov, Patrick Mevzek, James Mitchell, Francisco Obispo, Mike
O'Connell, Eric Rescoria, Bernhard Reutner-Fischer, Sabrina Tanamal,
Trung Tran, Ulrich Wisser and Sharon Wodjenski.
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, <https://www.rfc- DOI 10.17487/RFC2119, March 1997, <https://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, <https://www.rfc- DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,
September 2009, <https://www.rfc-editor.org/info/rfc5646>.
[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,
<https://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, <https://www.rfc- DOI 10.17487/RFC5731, August 2009, <https://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",
skipping to change at page 65, line 43 skipping to change at page 67, line 32
<launch:status> elements in the section 2.5 examples. <launch:status> elements in the section 2.5 examples.
7. Updated the description of the <mark:mark> element in the 7. Updated the description of the <mark:mark> element in the
info response. info response.
8. Added returning an EPP error result code of 2306 if the 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 "type" attribute is incorrect in section 3.3.1, 3.3.2, and
3.3.3. 3.3.3.
9. Made small change in the description of the Create Response 9. Made small change in the description of the Create Response
in section 3.3.5. in section 3.3.5.
10. Updated the Registrant Contact in section 7 to the IESG. 10. Updated the Registrant Contact in section 7 to the IESG.
A.28. Change from REGEXT 06 to REGEXT 07
1. Updates based on feedback from Mirja Kuhlewind that include:
1. In the Security Considerations section, change must to MUST
in "Updates to, and deletion of an application object MUST be
restricted to clients authorized to perform the said
operation on the object".
2. Updates based on feedback from Warren Kumari that include:
1. Removed the comma from "The Validator Identifier is the
identifier, that is unique..." not needed due to change from
Harald Alvestrand's feedback.
3. Updates based on feedback from Alexey Melnikov that include:
1. Added a Normative Reference to RFC 5646 for the "language"
attribute.
2. Replace identifer with identifier".
3. Remove "for" in "Enumeration of for launch phase values"
4. Updates based on feedback from Harald Alvestrand that include:
1. Removed the references to the unused "launch-1.0",
"signedMark-1.0", and "mark-1.0" abbreviations and revised
the XML namespace prefix definitions for "launch", "smd", and
"mark".
2. Replace "that is unique to the server" to "unique to the
server" in the Validator Identifier section.
3. Replaced ", including the "allocated" and "rejected"
statuses" with "("allocated" and "rejected")" in the Status
Values section.
4. Replaced "Is a possible end state" with "This is a possible
end state" in the definition of the "allocated" and
"rejected" statuses in the Status Values section.
5. Add the preamble "The transitions between the states is a
matter of server policy. This diagram defines one possible
set of permitted transitions." to the State Transition
diagram.
6. Split the first sentence of the Poll Messaging section into
two sentences, one for the Launch Application and one for the
Launch Registration.
7. Remove "either" and replace "or" with an "and" in the first
sentence of the Digital Signature section for clarity and to
be more consistent with the description of the "signed mark"
validation model.
5. Updates based on feedback from Ben Campbell that include:
1. Replacement of "that" with "which" in the first sentence of
the Validator Identifier section not needed due change from
Harald Alvestrand's feedback.
2. Avoid using RFC 2119 in the Launch Phases definitions, which
resulted in change MAY to may in the definition of the
"open" phase and MUST to must in the definition of the
"claims" phase.
3. Change "SHOULD" to "should" in the sentence "For example,
the <launch:phase> element SHOULD be <launch:phase
name="landrush">claims</launch:phase>".
4. Change "MUST" to "must" in the sentence "The Trademark
Claims Phase is when a Claims Notice MUST be displayed to a
prospective registrant of a domain name that matches
trademarks".
5. Change "MAY" to "may" in the sentence "Claim Notice
Information Service (CNIS), which MAY be directly linked to
a Trademark Validator.", where MAY can be lowercase may".
6. Remove "that" from the sentence "The <launch:codeMark>
element that is used by the "code", "mark", and "code with
mark" validation models, has the following child elements".
7. Added the consistent use of colons ":" at the end of the
hangText labels to address adding whitespace between handing
indent list entries.
8. Revised the first sentence, of the second paragraph, of the
"EPP <update> Command" section, to read "An EPP <update>
command with the extension sent to a server that does not
support launch applications will fail.".
9. Revised the "The server SHOULD NOT use the "custom" status
value" to "The server SHOULD use one of the non-"custom"
status values" in the Status Values section.
10. Revised "Both the Validator Identifier and the Issuer
Identifier used MUST be unique" to "Both the Validator
Identifier and the Issuer Identifier used MUST be unique in
the server" in the Validator Identifier section.
11. Revised "The Validator Identifier MAY define a non-Trademark
Validator that supports a form of claims" to "The Validator
Identifier may define a non-Trademark Validator that
supports a form of claims, where claims and a Validator
Identifier can be used for purposes beyond trademarks" in
the Validator Identifier section.
6. Updates based on feedback from Eric Rescoria that include:
1. Replaced the duplicate Claims Check Form and Claims Create
Form in the list of the two ways the document supports the
Trademark Claims Phase, to refer to the section by number
instead of by name.
2. Added "The use of "..." is used as shorthand for elements
defined outside this document" added to the "In examples,..."
paragraph of the Conventions Used in This Document section.
3. Added "When using digital signatures the server MUST validate
the digital signature" to the Digital Signature section.
4. Removed "post-launch" to the description of the "open" phase
in the Launch Phases section.
5. Add the sentences "Multiple launch phases and multiple models
are supported to enable the launch of a domain name registry.
What is supported and what is validated is up to server
policy. Communication of the server policy is typically
performed using an out-of-band mechanism that is not
specified in this document." to the second paragraph of the
Introduction section.
7. Updates based on feedback from Spencer Dawkins that include:
1. Replace "during their initial launch" with "as they begin
operation" in the Introduction section.
8. Updates based on feedback from Sabrina Tanamal that include:
1. Pretty print the XML schema to address inconsistent
indenting.
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. 123 change blocks. 
375 lines changed or deleted 543 lines changed or added

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