draft-ietf-eppext-launchphase-06.txt   draft-ietf-eppext-launchphase-07.txt 
Internet Engineering Task Force J. Gould Internet Engineering Task Force J. Gould
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Intended status: Standards Track W. Tan Intended status: Standards Track W. Tan
Expires: February 4, 2016 Cloud Registry Expires: May 5, 2016 Cloud Registry
G. Brown G. Brown
CentralNic Ltd CentralNic Ltd
August 3, 2015 November 2, 2015
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-eppext-launchphase-06 draft-ietf-eppext-launchphase-07
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
extension mapping for the provisioning and management of domain name extension mapping for the provisioning and management of domain name
registrations and applications during the launch of a domain name registrations and applications during the launch of a domain name
registry. registry.
Status of This Memo Status of This Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 4, 2016. This Internet-Draft will expire on May 5, 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 14 skipping to change at page 3, line 14
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. Normative References . . . . . . . . . . . . . . . . . . . . 54 9. Normative References . . . . . . . . . . . . . . . . . . . . 54
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 . . . . . . . . . . . . . . . . . . 57
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 A.19. Change WG 05 to WG 06 . . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60 A.20. Change WG 06 to WG 07 . . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 61
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 [I-D.lozano-tmch-func-spec], in which a Claims Specification [I-D.ietf-eppext-tmch-func-spec], in which a Claims
Notice must be displayed to a prospective registrant of a domain Notice must be displayed to a prospective registrant of a domain
name that matches trademarks. 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 defined in the TMCH Functional Specification
[I-D.lozano-tmch-func-spec], and to support a traditional "landrush" [I-D.ietf-eppext-tmch-func-spec], and to support a traditional
launch phase. The overlap of the "claims" and "landrush" launch "landrush" launch phase. The overlap of the "claims" and "landrush"
phases SHOULD be handled by setting "claims" as the <launch:phase> launch phases SHOULD be handled by setting "claims" as the
value and setting "landrush" as the sub-phase with the "name" <launch:phase> value and setting "landrush" as the sub-phase with the
attribute. For example, the <launch:phase> element SHOULD be "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 54, line 48 skipping to change at page 54, line 48
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. Normative References 9. Normative References
[I-D.ietf-eppext-tmch-func-spec]
Lozano, G., "TMCH functional specifications", draft-ietf-
eppext-tmch-func-spec-00 (work in progress), October 2015.
[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-02 (work in progress), July 2015. ietf-eppext-tmch-smd-03 (work in progress), September
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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <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,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-editor.org/info/rfc3688>.
skipping to change at page 60, line 45 skipping to change at page 60, line 47
1. Removed duplicate "TMCH Functional Specification" URIs based on 1. Removed duplicate "TMCH Functional Specification" URIs based on
feedback from Scott Hollenbeck on the eppext mailing list. feedback from Scott Hollenbeck on the eppext mailing list.
2. Changed references of example?.tld to domain?.example to be 2. Changed references of example?.tld to domain?.example to be
consistent with RFC 6761 based on feedback from Scott Hollenbeck consistent with RFC 6761 based on feedback from Scott Hollenbeck
on the eppext mailing list. on the eppext mailing list.
3. A template was added to section 5 to register the XML schema in 3. A template was added to section 5 to register the XML schema in
addition to the namespace based on feedback from Scott Hollenbeck addition to the namespace based on feedback from Scott Hollenbeck
on the eppext mailing list. on the eppext mailing list.
A.20. Change WG 06 to WG 07
1. Changed reference of lozano-tmch-func-spec to ietf-eppext-tmch-
func-spec.
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
 End of changes. 12 change blocks. 
17 lines changed or deleted 25 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/