draft-ietf-eppext-launchphase-04.txt   draft-ietf-eppext-launchphase-05.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: August 31, 2015 Cloud Registry Expires: October 2, 2015 Cloud Registry
G. Brown G. Brown
CentralNic Ltd CentralNic Ltd
February 27, 2015 March 31, 2015
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-eppext-launchphase-04 draft-ietf-eppext-launchphase-05
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 August 31, 2015. This Internet-Draft will expire on October 2, 2015.
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 4 skipping to change at page 3, line 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 49 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 49
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 50 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 50
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
7. Security Considerations . . . . . . . . . . . . . . . . . . . 53 7. Security Considerations . . . . . . . . . . . . . . . . . . . 54
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 54 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 54
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 54 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 54
9.1. Normative References . . . . . . . . . . . . . . . . . . 54 9.1. Normative References . . . . . . . . . . . . . . . . . . 55
9.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . 55 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 56
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 55 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 . . . . . . . . . . . . . . . . . . 56 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 57
A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 56 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 . . . . . . . . . . . . . . . . . . 57 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 58
A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 58 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 59
A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 58 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 . . . . . . . . . . . . . . . . . . 59 A.16. Change WG 02 to WG 03 . . . . . . . . . . . . . . . . . . 60
A.17. Change WG 03 to WG 04 . . . . . . . . . . . . . . . . . . 59 A.17. Change WG 03 to WG 04 . . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59 A.18. Change WG 04 to WG 05 . . . . . . . . . . . . . . . . . . 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 33 skipping to change at page 6, line 33
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 [1], in which a Claims Notice must be displayed to a
prospective registrant of a domain name that matches trademarks. 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 [2], and to support a
traditional "landrush" launch phase. The overlap of the "claims" and traditional "landrush" launch phase. The overlap of the "claims" and
"landrush" launch phases SHOULD be handled by setting "claims" as the "landrush" launch phases SHOULD be handled by setting "claims" as the
<launch:phase> value and setting "landrush" as the sub-phase with the <launch:phase> value and setting "landrush" as the sub-phase with the
"name" attribute. For example, the <launch:phase> element SHOULD be "name" attribute. For example, the <launch:phase> element SHOULD be
skipping to change at page 18, line 17 skipping to change at page 18, line 17
domain name example2.tld in the "tmch", and a claims notice is domain name example2.tld 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 example3.tld in the "tmch" and "custom-
tmch", for the "claims" launch phase: tmch", for the "claims" launch phase:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <launch:chkData S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
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">example1.tld</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">example2.tld</launch:name>
S: <launch:claimKey validatorID="tmch"> S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
skipping to change at page 22, line 22 skipping to change at page 22, line 22
for the domain name example2.tld in the "tmch", matching trademarks for the domain name example2.tld in the "tmch", matching trademarks
are found for domain name example3.tld in the "tmch" and "custom- are found for domain name example3.tld in the "tmch" and "custom-
tmch", for the "claims" launch phase: tmch", for the "claims" launch phase:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <launch:chkData S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:cd> S: <launch:cd>
S: <launch:name exists="0">example1.tld</launch:name> S: <launch:name exists="0">example1.tld</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">example2.tld</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>
skipping to change at page 28, line 39 skipping to change at page 28, line 39
C: <launch:code validatorID="sample1"> C: <launch:code validatorID="sample1">
C: 49FD46E6C4B45C55D4AC</launch:code> C: 49FD46E6C4B45C55D4AC</launch:code>
C: </launch:codeMark> C: </launch:codeMark>
C: <launch:codeMark> C: <launch:codeMark>
C: <launch:code>49FD46E6C4B45C55D4AD</launch:code> C: <launch:code>49FD46E6C4B45C55D4AD</launch:code>
C: </launch:codeMark> C: </launch:codeMark>
C: <launch:codeMark> C: <launch:codeMark>
C: <launch:code validatorID="sample2"> C: <launch:code validatorID="sample2">
C: 49FD46E6C4B45C55D4AE</launch:code> C: 49FD46E6C4B45C55D4AE</launch:code>
C: </launch:codeMark> C: </launch:codeMark>
C: </launch:create> C: </launch:create>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
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">
skipping to change at page 53, line 34 skipping to change at page 53, line 34
draft-ietf-eppext-launchphase in both Java and C++. draft-ietf-eppext-launchphase in both Java and C++.
Level of maturity: Production Level of maturity: Production
Coverage: All aspects of the protocol are implemented. Coverage: All aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License Licensing: GNU Lesser General Public License
Contact: trung.tran@neustar.biz Contact: trung.tran@neustar.biz
6.7. gTLD Shared Registry System
Organization: Stichting Internet Domeinnaamregistratie Nederland
(SIDN)
Name: gTLD Shared Registry System
Description: The gTLD SRS implements the server side of the draft-
ietf-eppext-launchphase.
Level of maturity: (soon) Production
Coverage: The following parts of the draft are supported:
Signed mark validation model using Digital Signature
(Section 2.6.3)
Claims Check Form (Section 3.1.1)
Sunrise Create Form (Section 3.3.1)
Claims Create Form (Section 3.3.2)
The parts of the document not described here are not implemented.
Licensing: Proprietary
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.
skipping to change at page 59, line 47 skipping to change at page 60, line 26
or not a trademark exists that matches the domain name or not a trademark exists that matches the domain name
independent of whether a claims notice is required on create. independent of whether a claims notice is required on create.
This was based on a request from Trung Tran and a discussion on This was based on a request from Trung Tran and a discussion on
the eppext mailing list. the eppext mailing list.
A.17. Change WG 03 to WG 04 A.17. Change WG 03 to WG 04
1. Amended XML Namespace section of IANA Considerations, added EPP 1. Amended XML Namespace section of IANA Considerations, added EPP
Extension Registry section. Extension Registry section.
A.18. Change WG 04 to WG 05
1. Added a missing comma to the descripton of the <launch:phase>
element, based on feedback from Keith Gaughan on the eppext
mailing list.
2. Added the SIDN implementation status information.
3. Fixed a few indentation issues in the samples.
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
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. 18 change blocks. 
22 lines changed or deleted 57 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/