draft-ietf-eppext-launchphase-00.txt   draft-ietf-eppext-launchphase-01.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: July 25, 2014 Cloud Registry Expires: September 18, 2014 Cloud Registry
G. Brown G. Brown
CentralNic Ltd CentralNic Ltd
January 21, 2014 March 17, 2014
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-eppext-launchphase-00 draft-ietf-eppext-launchphase-01
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 July 25, 2014. This Internet-Draft will expire on September 18, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 9 skipping to change at page 3, line 9
6.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . . 46 6.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . . 46
6.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . . 47 6.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . . 47
6.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . . 47 6.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . . 47
6.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . . 47 6.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . . 47
6.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . . 47 6.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . . 47
6.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . . 48 6.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . . 48
6.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . . 48 6.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . . 48
6.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . . 49 6.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . . 49
6.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . . 49 6.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . . 49
6.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 49 6.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 49
6.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 50
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 8. Security Considerations . . . . . . . . . . . . . . . . . . . 50
9. Normative References . . . . . . . . . . . . . . . . . . . . . 50 9. Normative References . . . . . . . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51
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
skipping to change at page 8, line 8 skipping to change at page 8, line 8
text that describes the rationale for the status applied to the text that describes the rationale for the status applied to the
object. The OPTIONAL "lang" attribute MAY be present to identify the object. The OPTIONAL "lang" attribute MAY be present to identify the
language if the negotiated value is something other than the default language if the negotiated value is something other than the default
value of "en" (English). value of "en" (English).
For extensibility the <launch:status> element includes an OPTIONAL For extensibility the <launch:status> element includes an OPTIONAL
"name" attribute that can define a sub-status or the full name of the "name" attribute that can define a sub-status or the full name of the
status when the status value is "custom". The server SHOULD NOT use status when the status value is "custom". The server SHOULD NOT use
the "custom" status value. the "custom" status value.
Certain status values MAY be combined. For example, an application Status values MAY be skipped. For example, an application or
or registration may be both "invalid" and "rejected". Additionally,
certain statuses MAY be skipped. For example, an application or
registration MAY immediately start at the "allocated" status or an registration MAY immediately start at the "allocated" status or an
application or registration MAY skip the "pendingAllocation" status. application or registration MAY skip the "pendingAllocation" status.
If the launch phase does not require validation of a request, an If the launch phase does not require validation of a request, an
application or registration MAY immediately skip to application or registration MAY immediately skip to
"pendingAllocation". "pendingAllocation".
2.4.1. State Transition 2.4.1. State Transition
| request | request
| |
skipping to change at page 50, line 5 skipping to change at page 50, line 5
support launch applications based on a request from Sharon support launch applications based on a request from Sharon
Wodjenski on the provreg list. Wodjenski on the provreg list.
6.13. Change from 12 to WG 00 6.13. Change from 12 to WG 00
1. Changed to eppext working group draft by changing 1. Changed to eppext working group draft by changing
draft-tan-epp-launchphase to draft-ietf-eppext-launchphase and by draft-tan-epp-launchphase to draft-ietf-eppext-launchphase and by
changing references of draft-lozano-tmch-smd to changing references of draft-lozano-tmch-smd to
draft-ietf-eppext-tmch-smd. draft-ietf-eppext-tmch-smd.
6.14. Change WG 00 to WG 01
1. Removed text associated with support for the combining of status
values based on feedback from Patrick Mevzek on the provreg
mailing list, discussion on the eppext mailing list, and
discussion at the eppext IETF meeting on March 6, 2014.
7. IANA Considerations 7. IANA Considerations
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]. One URI
assignment has been registered by the IANA. assignment has been registered by the IANA.
Registration request for the Launch namespace: 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
 End of changes. 7 change blocks. 
7 lines changed or deleted 13 lines changed or added

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