draft-ietf-eppext-launchphase-03.txt   draft-ietf-eppext-launchphase-04.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 2, 2015 Cloud Registry Expires: August 31, 2015 Cloud Registry
G. Brown G. Brown
CentralNic Ltd CentralNic Ltd
January 29, 2015 February 27, 2015
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-eppext-launchphase-03 draft-ietf-eppext-launchphase-04
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 2, 2015. This Internet-Draft will expire on August 31, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 4 1.1. Conventions Used in This Document . . . . . . . . . . . . 4
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 6
2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 6 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 6
2.4.1. State Transition . . . . . . . . . . . . . . . . . . 7 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 8
2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 8 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 9
2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 11 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 12
2.6.1. <launch:codeMark> element . . . . . . . . . . . . . . 12 2.6.1. <launch:codeMark> element . . . . . . . . . . . . . . 13
2.6.2. <mark:mark> element . . . . . . . . . . . . . . . . . 13 2.6.2. <mark:mark> element . . . . . . . . . . . . . . . . . 14
2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 13 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 14
2.6.3.1. <smd:signedMark> element . . . . . . . . . . . . 13 2.6.3.1. <smd:signedMark> element . . . . . . . . . . . . 14
2.6.3.2. <smd:encodedSignedMark> element . . . . . . . . . 13 2.6.3.2. <smd:encodedSignedMark> element . . . . . . . . . 14
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 13 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 14
3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 14 3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 15
3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 14 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 15
3.1.2. Availability Check Form . . . . . . . . . . . . . . . 17 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 18
3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 19 3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 20
3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 22 3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 23
3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 25 3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 26
3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 25 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 26
3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 31 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 32
3.3.3. General Create Form . . . . . . . . . . . . . . . . . 34 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 35
3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 35 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 36
3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 37 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 38
3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 38 3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 39
3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 39 3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 40
3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 40 3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 41
3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 41 3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 42
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 41 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 42
4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 41 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 42
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 48 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 49
6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 49 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 50
6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 49 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 50
6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 50 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 51
6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 50 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 51
6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 51 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 52
6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 51 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 52
7. Security Considerations . . . . . . . . . . . . . . . . . . . 52 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 52
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 52 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 53
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 52
9.1. Normative References . . . . . . . . . . . . . . . . . . 52 7. Security Considerations . . . . . . . . . . . . . . . . . . . 53
9.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 53 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 54
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 53 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 54
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 53 9.1. Normative References . . . . . . . . . . . . . . . . . . 54
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 53 9.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 55
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 53 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 55
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 54 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 55
A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 54 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 55
A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 54 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 55
A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 54 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 55
A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 55 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 56
A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 55 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 56
A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 56 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 56
A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 56 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 56
A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 57 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 57
A.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 57 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 57
A.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 57 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 58
A.15. Change WG 01 to WG 02 . . . . . . . . . . . . . . . . . . 57 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 58
A.16. Change WG 02 to WG 03 . . . . . . . . . . . . . . . . . . 57 A.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 59
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58 A.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 59
A.15. Change WG 01 to WG 02 . . . . . . . . . . . . . . . . . . 59
A.16. Change WG 02 to WG 03 . . . . . . . . . . . . . . . . . . 59
A.17. Change WG 03 to WG 04 . . . . . . . . . . . . . . . . . . 59
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59
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 48, line 37 skipping to change at page 49, line 37
<element ref="mark:abstractMark" <element ref="mark:abstractMark"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
</schema> </schema>
END END
5. IANA Considerations 5. IANA Considerations
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]. One URI conforming to a registry mechanism described in [RFC3688]. The
assignment has been registered by the IANA. following URI assignment is requested of IANA:
Registration request for the Launch namespace: URI: urn:ietf:params:xml:ns:launch-1.0
URI: urn:ietf:params:xml:ns:launch-1.0 Registrant Contact: See the "Author's Address" section of this
Registrant Contact: See the "Author's Address" section of this document.
document.
XML: None. Namespace URIs do not represent an XML specification. XML: See the "Formal Syntax" section of this document.
5.2. EPP Extension Registry
The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows:
Name of Extension: "Launch Phase Mapping for the Extensible
Provisioning Protocol (EPP)"
Document status: Standards Track
Reference: (insert reference to RFC version of this document)
Registrant Name and Email Address: IESG, <iesg@ietf.org>
TLDs: Any
IPR Disclosure: None
Status: Active
Notes: None
6. Implementation Status 6. Implementation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
RFC 6982 [RFC6982] before publication. RFC 6982 [RFC6982] before publication.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in RFC 6982 Internet-Draft, and is based on a proposal described in RFC 6982
[RFC6982]. The description of implementations in this section is [RFC6982]. The description of implementations in this section is
skipping to change at page 52, line 45 skipping to change at page 54, line 27
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. References
9.1. 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-00 (work in progress), January 2014. ietf-eppext-tmch-smd-01 (work in progress), February 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, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009. STD 69, RFC 5730, August 2009.
[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, August 2009.
[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, July
2013. 2013.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, February 2015.
9.2. URIs 9.2. URIs
[1] http://tools.ietf.org/html/draft-lozano-tmch-func-spec [1] http://tools.ietf.org/html/draft-lozano-tmch-func-spec
[2] 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
skipping to change at page 58, line 5 skipping to change at page 59, line 42
"Change Log" Section to end. "Change Log" Section to end.
3. Updated the text for the Claims Check Form and the Claims Create 3. Updated the text for the Claims Check Form and the Claims Create
Form to support checking for the need of the claims notice and Form to support checking for the need of the claims notice and
passing the claims notice outside of the "claims" phase. passing the claims notice outside of the "claims" phase.
4. Added the new Trademark Check Form to support determining whether 4. Added the new Trademark Check Form to support determining whether
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.
Authors' Addresses A.17. Change WG 03 to WG 04
1. Amended XML Namespace section of IANA Considerations, added EPP
Extension Registry section.
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
 End of changes. 15 change blocks. 
72 lines changed or deleted 108 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/