draft-ietf-eppext-launchphase-05.txt   draft-ietf-eppext-launchphase-06.txt 
Internet Engineering Task Force J. Gould Internet Engineering Task Force J. Gould
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Intended status: Standards Track W. Tan Intended status: Standards Track W. Tan
Expires: October 2, 2015 Cloud Registry Expires: February 4, 2016 Cloud Registry
G. Brown G. Brown
CentralNic Ltd CentralNic Ltd
March 31, 2015 August 3, 2015
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-eppext-launchphase-05 draft-ietf-eppext-launchphase-06
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
extension mapping for the provisioning and management of domain name extension mapping for the provisioning and management of domain name
registrations and applications during the launch of a domain name registrations and applications during the launch of a domain name
registry. registry.
Status of This Memo Status of This Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 2, 2015. This Internet-Draft will expire on February 4, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 7 skipping to change at page 3, line 7
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 50 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 50
6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 51 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 51
6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 51 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 51
6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 52 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 52
6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 52 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 52
6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 52 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 52
6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 53 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 53
6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 53 6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 53
7. Security Considerations . . . . . . . . . . . . . . . . . . . 54 7. Security Considerations . . . . . . . . . . . . . . . . . . . 54
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 54 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 54
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 54 9. Normative References . . . . . . . . . . . . . . . . . . . . 54
9.1. Normative References . . . . . . . . . . . . . . . . . . 55
9.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 55 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 55
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 55 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 55
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 55 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 55
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 56 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 56
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 56 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 56
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 56 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 56
A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 56 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 56
A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 57 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 57
A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 57 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 57
A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 57 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 57
A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 58 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 58
A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 59 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 59
A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 59 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 59
A.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 59 A.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 59
A.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 59 A.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 59
A.15. Change WG 01 to WG 02 . . . . . . . . . . . . . . . . . . 59 A.15. Change WG 01 to WG 02 . . . . . . . . . . . . . . . . . . 59
A.16. Change WG 02 to WG 03 . . . . . . . . . . . . . . . . . . 60 A.16. Change WG 02 to WG 03 . . . . . . . . . . . . . . . . . . 60
A.17. Change WG 03 to WG 04 . . . . . . . . . . . . . . . . . . 60 A.17. Change WG 03 to WG 04 . . . . . . . . . . . . . . . . . . 60
A.18. Change WG 04 to WG 05 . . . . . . . . . . . . . . . . . . 60 A.18. Change WG 04 to WG 05 . . . . . . . . . . . . . . . . . . 60
A.19. Change WG 05 to WG 06 . . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60
1. Introduction 1. Introduction
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping
specifies a flexible schema that can be used to implement several specifies a flexible schema that can be used to implement several
common use cases related to the provisioning and management of domain common use cases related to the provisioning and management of domain
name registrations and applications during the launch of a domain name registrations and applications during the launch of a domain
name registry. name registry.
skipping to change at page 6, line 24 skipping to change at page 6, line 24
The following launch phase values are defined: The following launch phase values are defined:
sunrise The phase during which trademark holders can submit sunrise The phase during which trademark holders can submit
registrations or applications with trademark information that can registrations or applications with trademark information that can
be validated by the server. be validated by the server.
landrush A post-Sunrise phase when non-trademark holders are allowed landrush A post-Sunrise phase when non-trademark holders are allowed
to register domain names with steps taken to address a large to register domain names with steps taken to address a large
volume of initial registrations. volume of initial registrations.
claims The Trademark Claims phase, as defined in the TMCH Functional claims The Trademark Claims phase, as defined in the TMCH Functional
Specification [1], in which a Claims Notice must be displayed to a Specification [I-D.lozano-tmch-func-spec], in which a Claims
prospective registrant of a domain name that matches trademarks. Notice must be displayed to a prospective registrant of a domain
name that matches trademarks.
open A post-launch phase that is also referred to as "steady state". open A post-launch phase that is also referred to as "steady state".
Servers MAY require additional trademark protection during this Servers MAY require additional trademark protection during this
phase. phase.
custom A custom server launch phase that is defined using the "name" custom A custom server launch phase that is defined using the "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 TMCH Functional Specification [2], and to support a defined in the TMCH Functional Specification
traditional "landrush" launch phase. The overlap of the "claims" and [I-D.lozano-tmch-func-spec], and to support a traditional "landrush"
"landrush" launch phases SHOULD be handled by setting "claims" as the launch phase. The overlap of the "claims" and "landrush" launch
<launch:phase> value and setting "landrush" as the sub-phase with the phases SHOULD be handled by setting "claims" as the <launch:phase>
"name" attribute. For example, the <launch:phase> element SHOULD be value and setting "landrush" as the sub-phase with the "name"
attribute. For example, the <launch:phase> element SHOULD be
<launch:phase name="landrush">claims</launch:phase>. <launch:phase name="landrush">claims</launch:phase>.
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,
skipping to change at page 10, line 21 skipping to change at page 10, line 21
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>
S: <msgQ count="5" id="12345"> S: <msgQ count="5" id="12345">
S: <qDate>2013-04-04T22:01:00.0Z</qDate> S: <qDate>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Application pendingAllocation.</msg> S: <msg>Application pendingAllocation.</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <domain:infData S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>example.tld</domain:name> S: <domain:name>domain.example</domain:name>
S: ... S: ...
S: </domain:infData> S: </domain:infData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <launch:infData S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase> S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID> S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="pendingAllocation"/> S: <launch:status s="pendingAllocation"/>
S: </launch:infData> S: </launch:infData>
skipping to change at page 11, line 20 skipping to change at page 11, line 20
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>
S: <msgQ count="5" id="12345"> S: <msgQ count="5" id="12345">
S: <qDate>2013-04-04T22:01:00.0Z</qDate> S: <qDate>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Application successfully allocated.</msg> S: <msg>Application successfully allocated.</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <domain:panData S: <domain:panData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name paResult="1">example.tld</domain:name> S: <domain:name paResult="1">domain.example</domain:name>
S: <domain:paTRID> S: <domain:paTRID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID> S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate> S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData> S: </domain:panData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <launch:infData S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
skipping to change at page 12, line 20 skipping to change at page 12, line 20
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>
S: <msgQ count="5" id="12345"> S: <msgQ count="5" id="12345">
S: <qDate>2013-04-04T22:01:00.0Z</qDate> S: <qDate>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Registration successfully allocated.</msg> S: <msg>Registration successfully allocated.</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <domain:panData S: <domain:panData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name paResult="1">example.tld</domain:name> S: <domain:name paResult="1">domain.example</domain:name>
S: <domain:paTRID> S: <domain:paTRID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID> S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate> S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData> S: </domain:panData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <launch:infData S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
skipping to change at page 16, line 13 skipping to change at page 16, line 13
name mapping [RFC5731] define the domain names to check for matching name mapping [RFC5731] define the domain names to check for matching
trademarks. The <launch:check> element contains the following child trademarks. The <launch:check> element contains the following child
elements: elements:
<launch:phase> Contains the value of the active launch phase of the <launch:phase> Contains the value of the active launch phase of the
server. The server SHOULD validate the value against the active server. The server SHOULD validate the value against the active
server launch phase. server launch phase.
Example Claims Check command using the <check> domain command and the Example Claims Check command using the <check> domain command and the
<launch:check> extension with the "type" explicitly set to "claims", <launch:check> extension with the "type" explicitly set to "claims",
to determine if "example1.tld", "example2.tld", and "example3.tld" to determine if "domain1.example", "domain2.example", and
require claims notices during the "claims" launch phase: "domain3.example" require claims notices during the "claims" launch
phase:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <check> C: <check>
C: <domain:check C: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example1.tld</domain:name> C: <domain:name>domain1.example</domain:name>
C: <domain:name>example2.tld</domain:name> C: <domain:name>domain2.example</domain:name>
C: <domain:name>example3.tld</domain:name> C: <domain:name>domain3.example</domain:name>
C: </domain:check> C: </domain:check>
C: </check> C: </check>
C: <extension> C: <extension>
C: <launch:check C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="claims"> C: type="claims">
C: <launch:phase>claims</launch:phase> C: <launch:phase>claims</launch:phase>
C: </launch:check> C: </launch:check>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
skipping to change at page 18, line 6 skipping to change at page 18, line 6
of the domain name to securely query the service without of the domain name to securely query the service without
using a well-known value like a domain name. The OPTIONAL using a well-known value like a domain name. The OPTIONAL
"validatorID" attribute is the Validator Identifier "validatorID" attribute is the Validator Identifier
(Section 2.2) whose value indicates which Trademark Validator (Section 2.2) whose value indicates which Trademark Validator
to query for the Claims Notice information, with the default to query for the Claims Notice information, with the default
being the ICANN TMCH. The "validatorID" attribute MAY being the ICANN TMCH. The "validatorID" attribute MAY
reference a non-trademark claims clearinghouse identifer to reference a non-trademark claims clearinghouse identifer to
support other forms of claims notices. support other forms of claims notices.
Example Claims Check response when a claims notice is not required Example Claims Check response when a claims notice is not required
for the domain name example1.tld, a claims notice is required for the for the domain name domain1.example, a claims notice is required for
domain name example2.tld 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 example3.tld in the "tmch" and "custom- required for the domain name domain3.example in the "tmch" and
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">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <launch:chkData S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>claims</launch:phase> S: <launch:phase>claims</launch:phase>
S: <launch:cd> S: <launch:cd>
S: <launch:name exists="0">example1.tld</launch:name> S: <launch:name exists="0">domain1.example</launch:name>
S: </launch:cd> S: </launch:cd>
S: <launch:cd> S: <launch:cd>
S: <launch:name exists="1">example2.tld</launch:name> S: <launch:name exists="1">domain2.example</launch:name>
S: <launch:claimKey validatorID="tmch"> S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey> S: </launch:claimKey>
S: </launch:cd> S: </launch:cd>
S: <launch:cd> S: <launch:cd>
S: <launch:name exists="1">example3.tld</launch:name> S: <launch:name exists="1">domain3.example</launch:name>
S: <launch:claimKey validatorID="tmch"> S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey> S: </launch:claimKey>
S: <launch:claimKey validatorID="custom-tmch"> S: <launch:claimKey validatorID="custom-tmch">
S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
S: </launch:claimKey> S: </launch:claimKey>
S: </launch:cd> S: </launch:cd>
S: </launch:chkData> S: </launch:chkData>
S: </extension> S: </extension>
S: <trID> S: <trID>
skipping to change at page 19, line 28 skipping to change at page 19, line 28
command and the <launch:check> extension with the "type" set to command and the <launch:check> extension with the "type" set to
"avail", to determine the availability of two domain names in the "avail", to determine the availability of two domain names in the
"idn-release" custom launch phase: "idn-release" custom launch phase:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <check> C: <check>
C: <domain:check C: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example1.tld</domain:name> C: <domain:name>domain1.example</domain:name>
C: <domain:name>example2.tld</domain:name> C: <domain:name>domain2.example</domain:name>
C: </domain:check> C: </domain:check>
C: </check> C: </check>
C: <extension> C: <extension>
C: <launch:check C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="avail"> C: type="avail">
C: <launch:phase name="idn-release">custom</launch:phase> C: <launch:phase name="idn-release">custom</launch:phase>
C: </launch:check> C: </launch:check>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
skipping to change at page 21, line 7 skipping to change at page 21, line 7
Notice information from Trademark Validator based on the Validator Notice information from Trademark Validator based on the Validator
Identifier (Section 2.2). Identifier (Section 2.2).
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 does not contain any child trademarks. The <launch:check> element does not contain any child
elements with the "Trademark Check Form": elements with the "Trademark Check Form":
Example Trademark Check command using the <check> domain command and Example Trademark Check command using the <check> domain command and
the <launch:check> extension with the "type" set to "trademark", to the <launch:check> extension with the "type" set to "trademark", to
determine if "example1.tld", "example2.tld", and "example3.tld" have determine if "domain1.example", "domain2.example", and
any matching trademarks: "domain3.example" have any matching trademarks:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <check> C: <check>
C: <domain:check C: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example1.tld</domain:name> C: <domain:name>domain1.example</domain:name>
C: <domain:name>example2.tld</domain:name> C: <domain:name>domain2.example</domain:name>
C: <domain:name>example3.tld</domain:name> C: <domain:name>domain3.example</domain:name>
C: </domain:check> C: </domain:check>
C: </check> C: </check>
C: <extension> C: <extension>
C: <launch:check C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="trademark"/> C: type="trademark"/>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
skipping to change at page 22, line 11 skipping to change at page 22, line 11
of the domain name to securely query the service without of the domain name to securely query the service without
using a well-known value like a domain name. The OPTIONAL using a well-known value like a domain name. The OPTIONAL
"validatorID" attribute is the Validator Identifier "validatorID" attribute is the Validator Identifier
(Section 2.2) whose value indicates which Trademark Validator (Section 2.2) whose value indicates which Trademark Validator
to query for the Claims Notice information, with the default to query for the Claims Notice information, with the default
being the ICANN TMCH. The "validatorID" attribute MAY being the ICANN TMCH. The "validatorID" attribute MAY
reference a non-trademark claims clearinghouse identifer to reference a non-trademark claims clearinghouse identifer to
support other forms of claims notices. support other forms of claims notices.
Example Trademark Check response when no matching trademarks are Example Trademark Check response when no matching trademarks are
found for the domain name example1.tld, matching trademarks are found found for the domain name domain1.example, matching trademarks are
for the domain name example2.tld in the "tmch", matching trademarks found for the domain name domain2.example in the "tmch", matching
are found for domain name example3.tld in the "tmch" and "custom- trademarks are found for domain name domain3.example in the "tmch"
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">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <launch:chkData S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:cd> S: <launch:cd>
S: <launch:name exists="0">example1.tld</launch:name> S: <launch:name exists="0">domain1.example</launch:name>
S: </launch:cd> S: </launch:cd>
S: <launch:cd> S: <launch:cd>
S: <launch:name exists="1">example2.tld</launch:name> S: <launch:name exists="1">domain2.example</launch:name>
S: <launch:claimKey validatorID="tmch"> S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey> S: </launch:claimKey>
S: </launch:cd> S: </launch:cd>
S: <launch:cd> S: <launch:cd>
S: <launch:name exists="1">example3.tld</launch:name> S: <launch:name exists="1">domain3.example</launch:name>
S: <launch:claimKey validatorID="tmch"> S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey> S: </launch:claimKey>
S: <launch:claimKey validatorID="custom-tmch"> S: <launch:claimKey validatorID="custom-tmch">
S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
S: </launch:claimKey> S: </launch:claimKey>
S: </launch:cd> S: </launch:cd>
S: </launch:chkData> S: </launch:chkData>
S: </extension> S: </extension>
S: <trID> S: <trID>
skipping to change at page 23, line 29 skipping to change at page 23, line 29
response. The <launch:info> element contains the following child response. The <launch:info> element contains the following child
elements: elements:
<launch:phase> The phase during which the application or <launch:phase> The phase during which the application or
registration was submitted or is associated with. Server policy registration was submitted or is associated with. Server policy
defines the phases that are supported. defines the phases that are supported.
<launch:applicationID> OPTIONAL application identifier of the Launch <launch:applicationID> OPTIONAL application identifier of the Launch
Application. Application.
Example <info> domain command with the <launch:info> extension to Example <info> domain command with the <launch:info> extension to
retrieve information for the sunrise application for example.tld and retrieve information for the sunrise application for domain.example
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
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.tld</domain:name> C: <domain:name>domain.example</domain:name>
C: </domain:info> C: </domain:info>
C: </info> C: </info>
C: <extension> C: <extension>
C: <launch:info C: <launch:info
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: includeMark="true"> C: includeMark="true">
C: <launch:phase>sunrise</launch:phase> C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID> C: <launch:applicationID>abc123</launch:applicationID>
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>
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 registration for example.tld: retrieve information for the sunrise registration for domain.example:
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
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.tld</domain:name> C: <domain:name>domain.example</domain:name>
C: </domain:info> C: </domain:info>
C: </info> C: </info>
C: <extension> C: <extension>
C: <launch:info C: <launch:info
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
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>
skipping to change at page 25, line 17 skipping to change at page 25, line 17
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <domain:infData S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>example.tld</domain:name> S: <domain:name>domain.example</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid> S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="pendingCreate"/> S: <domain:status s="pendingCreate"/>
S: <domain:registrant>jd1234</domain:registrant> S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact> S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact> S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:clID>ClientX</domain:clID> S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID> S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>2012-04-03T22:00:00.0Z</domain:crDate> S: <domain:crDate>2012-04-03T22:00:00.0Z</domain:crDate>
S: <domain:authInfo> S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw> S: <domain:pw>2fooBAR</domain:pw>
skipping to change at page 28, line 15 skipping to change at page 28, line 15
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">
C: <command> C: <command>
C: <create> C: <create>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.tld</domain:name> C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant> C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <launch:create C: <launch:create
skipping to change at page 29, line 14 skipping to change at page 29, line 14
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 "mark" validation model, <launch:create> extension, following the "mark" validation model,
with the mark information: with the mark information:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <create> C: <create>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>exampleone.tld</domain:name> C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant> C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <launch:create C: <launch:create
skipping to change at page 30, line 14 skipping to change at page 30, line 14
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 with mark" validation <launch:create> extension, following the "code with mark" validation
model, with a code and mark information: model, with a code and mark information:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <create> C: <create>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.tld</domain:name> C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant> C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <launch:create C: <launch:create
skipping to change at page 31, line 14 skipping to change at page 31, line 14
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 "signed mark" validation <launch:create> extension, following the "signed mark" validation
model, with the signed mark information for a sunrise application: model, with the signed mark information for a sunrise application:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <create> C: <create>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>exampleone.tld</domain:name> C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant> C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <launch:create C: <launch:create
skipping to change at page 32, line 14 skipping to change at page 32, line 14
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 "signed mark" validation <launch:create> extension, following the "signed mark" validation
model, with the base64 encoded signed mark information: model, with the base64 encoded signed mark information:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <create> C: <create>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>exampleone.tld</domain:name> C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant> C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <launch:create C: <launch:create
skipping to change at page 34, line 16 skipping to change at page 34, line 16
<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>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.tld</domain:name> C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant> C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <launch:create C: <launch:create
skipping to change at page 35, line 31 skipping to change at page 35, line 31
The following is an example <create> domain command using the The following is an example <create> domain command using the
<launch:create> extension for a "landrush" launch phase application: <launch:create> extension for a "landrush" launch phase application:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <create> C: <create>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.tld</domain:name> C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant> C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <launch:create C: <launch:create
skipping to change at page 37, line 16 skipping to change at page 37, line 16
<launch:create> extension, with using a mix of the Sunrise Create <launch:create> extension, with using a mix of the Sunrise Create
Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by
including both a mark and a notice: including both a mark and a notice:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <create> C: <create>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>exampleone.tld</domain:name> C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant> C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <launch:create C: <launch:create
skipping to change at page 38, line 31 skipping to change at page 38, line 31
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>
S: </result> S: </result>
S: <resData> S: <resData>
S: <domain:creData S: <domain:creData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>example.tld</domain:name> S: <domain:name>domain.example</domain:name>
S: <domain:crDate>2010-08-10T15:38:26.623854Z</domain:crDate> S: <domain:crDate>2010-08-10T15:38:26.623854Z</domain:crDate>
S: </domain:creData> S: </domain:creData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <launch:creData S: <launch:creData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase> S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>2393-9323-E08C-03B1 S: <launch:applicationID>2393-9323-E08C-03B1
S: </launch:applicationID> S: </launch:applicationID>
S: </launch:creData> S: </launch:creData>
skipping to change at page 40, line 15 skipping to change at page 40, line 15
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>
C: <domain:update C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.tld</domain:name> C: <domain:name>domain.example</domain:name>
C: <domain:add> C: <domain:add>
C: <domain:ns> C: <domain:ns>
C: <domain:hostObj>ns2.example.tld</domain:hostObj> C: <domain:hostObj>ns2.domain.example</domain:hostObj>
C: </domain:ns> C: </domain:ns>
C: </domain:add> C: </domain:add>
C: <domain:rem> C: <domain:rem>
C: <domain:ns> C: <domain:ns>
C: <domain:hostObj>ns1.example.tld</domain:hostObj> C: <domain:hostObj>ns1.domain.example</domain:hostObj>
C: </domain:ns> C: </domain:ns>
C: </domain:rem> C: </domain:rem>
C: </domain:update> C: </domain:update>
C: </update> C: </update>
C: <extension> C: <extension>
C: <launch:update C: <launch:update
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase> C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID> C: <launch:applicationID>abc123</launch:applicationID>
C: </launch:update> C: </launch:update>
skipping to change at page 41, line 26 skipping to change at page 41, line 26
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
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.tld</domain:name> C: <domain:name>domain.example</domain:name>
C: </domain:delete> C: </domain:delete>
C: </delete> C: </delete>
C: <extension> C: <extension>
C: <launch:delete C: <launch:delete
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase> C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID> C: <launch:applicationID>abc123</launch:applicationID>
C: </launch:delete> C: </launch:delete>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
skipping to change at page 49, line 40 skipping to change at page 49, line 40
</complexType> </complexType>
</schema> </schema>
END END
5. IANA Considerations 5. IANA Considerations
5.1. XML Namespace 5.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. The conforming to a registry mechanism described in [RFC3688].
following URI assignment is requested of IANA:
URI: urn:ietf:params:xml:ns:launch-1.0 Registration request for the launch namespace:
Registrant Contact: See the "Author's Address" section of this URI: urn:ietf:params:xml:ns:launch-1.0
document. Registrant Contact: See the "Author's Address" section of this
document.
XML: None. Namespace URIs do not represent an XML specification.
XML: See the "Formal Syntax" section of this document. Registration request for the launch XML schema:
URI: urn:ietf:params:xml:schema:launch-1.0
Registrant Contact: See the "Author's Address" section of this
document.
XML: See the "Formal Syntax" section of this document.
5.2. EPP Extension Registry 5.2. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows: details of the registration are as follows:
Name of Extension: "Launch Phase Mapping for the Extensible Name of Extension: "Launch Phase Mapping for the Extensible
Provisioning Protocol (EPP)" Provisioning Protocol (EPP)"
skipping to change at page 54, line 46 skipping to change at page 54, line 46
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, Michael were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Michael
Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus
Malorny, Alexander Mayrhofer, Patrick Mevzek, James Mitchell, Malorny, Alexander Mayrhofer, Patrick Mevzek, James Mitchell,
Francisco Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung Francisco Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung
Tran, Ulrich Wisser and Sharon Wodjenski. Tran, Ulrich Wisser and Sharon Wodjenski.
9. References 9. Normative References
9.1. Normative References
[I-D.ietf-eppext-tmch-smd] [I-D.ietf-eppext-tmch-smd]
Lozano, G., "Mark and Signed Mark Objects Mapping", draft- Lozano, G., "Mark and Signed Mark Objects Mapping", draft-
ietf-eppext-tmch-smd-01 (work in progress), February 2015. ietf-eppext-tmch-smd-02 (work in progress), July 2015.
[I-D.lozano-tmch-func-spec]
Lozano, G., "TMCH functional specifications", draft-
lozano-tmch-func-spec-10 (work in progress), July 2015.
[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, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009. STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<http://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, August 2009. Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009,
<http://www.rfc-editor.org/info/rfc5731>.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", RFC 6982, July Code: The Implementation Status Section", RFC 6982,
2013. DOI 10.17487/RFC6982, July 2013,
<http://www.rfc-editor.org/info/rfc6982>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, February 2015. Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <http://www.rfc-editor.org/info/rfc7451>.
9.2. URIs
[1] http://tools.ietf.org/html/draft-lozano-tmch-func-spec
[2] http://tools.ietf.org/html/draft-lozano-tmch-func-spec
Appendix A. Change History Appendix A. Change History
A.1. Change from 00 to 01 A.1. Change from 00 to 01
1. Changed to use camel case for the XML elements. 1. Changed to use camel case for the XML elements.
2. Replaced "cancelled" status to "rejected" status. 2. Replaced "cancelled" status to "rejected" status.
3. Added the child elements of the <claim> element. 3. Added the child elements of the <claim> element.
4. Removed the XML schema and replaced with "[TBD]". 4. Removed the XML schema and replaced with "[TBD]".
skipping to change at page 60, line 34 skipping to change at page 60, line 34
Extension Registry section. Extension Registry section.
A.18. Change WG 04 to WG 05 A.18. Change WG 04 to WG 05
1. Added a missing comma to the descripton of the <launch:phase> 1. Added a missing comma to the descripton of the <launch:phase>
element, based on feedback from Keith Gaughan on the eppext element, based on feedback from Keith Gaughan on the eppext
mailing list. mailing list.
2. Added the SIDN implementation status information. 2. Added the SIDN implementation status information.
3. Fixed a few indentation issues in the samples. 3. Fixed a few indentation issues in the samples.
Authors' Addresses A.19. Change WG 05 to WG 06
1. Removed duplicate "TMCH Functional Specification" URIs based on
feedback from Scott Hollenbeck on the eppext mailing list.
2. Changed references of example?.tld to domain?.example to be
consistent with RFC 6761 based on feedback from Scott Hollenbeck
on the eppext mailing list.
3. A template was added to section 5 to register the XML schema in
addition to the namespace based on feedback from Scott Hollenbeck
on the eppext mailing list.
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
Wil Tan Wil Tan
Cloud Registry Cloud Registry
Suite 32 Seabridge House Suite 32 Seabridge House
377 Kent St 377 Kent St
Sydney, NSW 2000 Sydney, NSW 2000
AU AU
Phone: +61 414 710899 Phone: +61 414 710899
Email: wil@cloudregistry.net Email: wil@cloudregistry.net
URI: http://www.cloudregistry.net URI: http://www.cloudregistry.net
 End of changes. 57 change blocks. 
85 lines changed or deleted 109 lines changed or added

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