Change Extension Mapping for the Extensible Provisioning Protocol

Introduction This document describes the change extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This mapping, an extension of the domain name mapping described in , and an extension of the host mapping described in , is specified using the Extensible Markup Language (XML) 1.0 as described in and XML Schema notation as described in and . This document describes an Extensible Provisioning Protocol (EPP) extension of the domain name mapping described in and the host mapping described in to link transform commands to a change request described in the EPP Change Mapping - Add link TBD.

Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in when, and only when, they appear in all capitals, as shown here. In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples is provided only to illustrate element relationships and is not a REQUIRED feature of this specification. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented to develop a conforming implementation. The XML namespace prefix "changeExt" is used for the namespace "http://www.verisign-grs.com/epp/changeExt-1.0", but implementations MUST NOT depend on it; instead, they should employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.

This extension adds additional elements to the domain name mapping described in and the host mapping described in . Only new elements are described here.

The request identifier is used to identify the target Change Request object that the EPP operation is intended for. The request identifier uses the <changeExt:requestId> element, and is defined in section 2.1 of the EPP Change Mapping - Add link TBD.

EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification .

EPP Query Commands EPP provides three commands to retrieve object information: <check> to determine if an object is known to the server, <info> to retrieve detailed information associated with an object, and <transfer> to retrieve object transfer status information. The syntax of the Change extension is identical for all types of EPP commands.

EPP <check> Command This extension does not add any elements to the EPP <check> command or <check> response described in the EPP domain mapping and the EPP host mapping .

EPP <info> Command This extension does not add any elements to the EPP <info> command or <info> response described in the EPP domain mapping and the EPP host mapping .

EPP <transfer> Command This extension does not add any elements to the EPP <transfer> query command or <transfer> query response described in the EPP domain mapping and the EPP host mapping .

EPP Transform Commands EPP provides five commands to transform objects: <create> to create an instance of an object, <delete> to delete an instance of an object, <renew> to extend the validity period of an object, <transfer> to manage object sponsorship changes, and <update> to change information associated with an object. The syntax of the Change extension is identical for all types of EPP commands. Please see the <create> Command, in section 3.2.1, for a detailed description of command syntax.

EPP <create> Command This extension defines additional elements for the EPP <create> command. The EPP <create> command provides a transform operation that allows a client to create a domain or host object. In addition to the EPP command elements described in [EPP-D] and [EPP-H], the command MAY contain an <extension> element. The <extension> element MUST contain a child <changeExt:changeExt> element that contains the following child elements:

A <changeExt:requestID> element that MUST contain a request identifier, defined in section 2.1, specifying the target Change Request object.

Example <create> command:

C: C: C: C: C: example C: 1 C: C: ns1.example.com C: ns1.example.net C: C: C: 2fooBAR C: C: C: C: C: C: tk421 C: C: C: ABC-12345 C: C:]]>

EPP <create> Response When a <create> command has been processed successfully, the server MUST respond with an EPP response with no <resData> element. Example <create> response:

S: S: S: Command completed successfully; action pending S: S: S: ABC-12345 S: SRV-43659 S: S: S:]]> An EPP error response MUST be returned if a <create> command can not be processed for any reason TBD - The response has a pending action and the server MUST notify the client when offline processing of the action has been completed using the Change Request Poll message as defined by the EPP Change Mapping - Add link TBD.

EPP <delete> Command (see section 3.2.1)

EPP <delete> Response (see section 3.2.2)

EPP <renew> Command (see section 3.2.1)

EPP <renew> Response (see section 3.2.2)

EPP <transfer> Command (see section 3.2.1)

EPP <transfer> Response (see section 3.2.2)

EPP <update> Command (see section 3.2.1)

EPP <update> Response (see section 3.2.2)

Formal Syntax An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. Extensible Provisioning Protocol v1.0 Change extension schema END]]>

IANA Considerations

XML Namespace This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . The following URI assignment has been made by IANA: Registration request for the Change Extension namespace:

URI:: http://www.verisign-grs.com/epp/changeExt-1.0
Registrant Contact:: VeriSign Inc., <epp-registry@verisign.com>
XML:: None. Namespace URIs do not represent an XML specification.

Registration request for the Change Extension XML Schema:

URI:: http://www.verisign-grs.com/epp/changeExt-1.0
Registrant Contact:: VeriSign Inc., <epp-registry@verisign.com>
XML:: See the "Formal Syntax" section of this document.

EPP Extension Registry The EPP extension described in this document has been registered by IANA in the "Extensions for the Extensible Provisioning Protocol (EPP)" registry described in . The details of the registration are as follows:

Name of Extension:: "Change Extension Mapping for the Extensible Provisioning Protocol"
Document Status:: Informational
Reference:: (insert reference to RFC version of this document)
Registrant Name and Email Address:: VeriSign Inc., <epp-registry@verisign.com>
TLDs:: Any
IPR Disclosure:: None
Status:: Active
Notes:: None

Security Considerations The mapping extensions described in this document do not provide any security services beyond those described by EPP , the EPP domain name mapping , the EPP host mapping and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well.