Validate Extension for the Extensible Provisioning Protocol (EPP)

This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This EPP mapping specifies a flexible schema by which EPP clients and servers can reliably validate contact and eligibility data. With the increased number of restrictions on contacts and required data points (license, ids, etc.) to register a domain name, a way to validate the data points prior to issuing a transform command is becoming more important.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. 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 are provided only to illustrate element relationships and are not a REQUIRED feature of this protocol.

This extension adds additional elements to EPP object mappings like the EPP domain name mapping . Only those new elements are described here. Key Value provides a flexible mechanism to share data between the client and the server. The <validate:kv> element defines the data, with two required simple attributes, key and value, and an optional contactType attribute for specificity in the response, more details below. An example <validate:kv key="VATID" value="0123456789"/>. An example <validate:kv contactType="Admin" key="contact:cc" value="Invalid country code for admin contact, must be MX."/>.

A detailed description of the EPP syntax and semantics can be found in . The command mappings described here are specifically for the Validate Extension

EPP provides four 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, <poll> to discover and retrieve service messages queued by the server, and <transfer> to retrieve object transfer status information.

This extension defines additional elements for the EPP <check> command. The command frame MAY contain an <extension> element which MAY contain one child <validate:check> element with the following child element(s): one or more <validate:contact> element(s) for each contact that is to be validated that contains the contact type of the contact to be validated. The <validate:contact> element MUST contain the following child elements: one <validate:cd> element. zero or more <validate:kv> elements. The <validate:cd> element MUST contain the following child elements: one <validate:id> element. an OPTIONAL <validate:postalInfo> element. an OPTIONAL <validate:voice> element. an OPTIONAL <validate:fax> element. an OPTIONAL <validate:email> element. an OPTIONAL <validate:authInfo> element. an OPTIONAL <validate:disclose> element.

The following is an example of the <check> command using the <validate> extension. C: C: C: C: C: C: C: sh8013 C: C: John Doe C: Example Inc. C: C: 123 Example Dr. C: Suite 100 C: Dulles C: VA C: 20166-6503 C: US C: C: C: +1.7035555555 C: +1.7035555556 C: jdoe@example.com C: C: 2fooBAR C: C: C: C: C: C: C: C: C: C: C: sh8013 C: C: C: C: C: sh8014 C: C: John Doe C: Example Inc. C: C: 123 Example Dr. C: Suite 100 C: Dulles C: VA C: 20166-6503 C: US C: C: C: +1.7035555555 C: +1.7035555556 C: jdoe@example.com C: C: 2fooBAR C: C: C: C: C: C: C: C: C: C: sh8014 C: C: C: C: C: ABC-12345 C: C:]]> When the server receives a <check> command that includes the extension elements described above, its response MUST contain an <extension> element, which MUST contain a child <validate:chkData> element. The <validate:chkData> element MUST contain a <validate:cd> element for each <validate:check> element contained in the <check> command. The <validate:cd> element MUST contain the following child elements: one <validate:id> element. one <validate:response> element. zero or more <validate:kv> elements.

The following is an example of the <check> response using the <validate> extension. S: S: S: S: Command completed successfully S: S: S: S: S: sh8013 S: 1000 S: S: S: sh8014 S: 2306 S: S: S: S: S: S: S: S: ABC-12345 S: 54321-ZYX S: S: S:]]>

This extension does not add any elements to the EPP <info> command or <info> response.

This extension does not add any elements to the EPP <poll> command or <poll> response.

This extension does not add any elements to the EPP <transfer> command or <transfer> response.

EPP provides five commands to transform objects: <create> to create an instance of an object with a server, <delete> to remove an instance of an object from a server, <renew> to extend the validity period of an object, <transfer> to manage changes in client sponsorship of an object, and <update> to change information.

This extension does not add any elements to the EPP <create> command or <create> response.

This extension does not add any elements to the EPP <delete> command or <delete> response.

This extension does not add any elements to the EPP <renew> command or <renew> response.

This extension does not add any elements to the EPP <transfer> command or <transfer> response.

This extension does not add any elements to the EPP <update> command or <update> response.

One schema is presented here that is the EPP Validate Extension schema. 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 Validate Object Extension END]]>

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . The following URI assignment is requested of IANA: URI: ietf:params:xml:ns:validate-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: See the "Formal Syntax" section of this document.

The EPP extension described in this document should be registered by the IANA in the EPP Extension Registry described in . The details of the registration are as follows: Name of Extension: "Validate Extension 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

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

The authors wish to thank the following persons for their feedback and suggestions: Kevin Allendorf of GoDaddy Inc. Jody Kolker of GoDaddy Inc. James Gould of Verisign Inc

After review and broad feedback, extensive changes have been made transforming the original document from a standalone extension command to an extension using the <check> command and response framework.