Registration Protocols Extensions R. Carney Internet-Draft J. Snitker Intended status: Standards Track GoDaddy Inc. Expires: June 5, 2017 December 2, 2016 Validate Mapping for the Extensible Provisioning Protocol (EPP) draft-ietf-regext-validate-00 Abstract This document describes an Extensible Provisioning Protocol (EPP) mapping for the validation of contact and eligibility data. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on June 5, 2017. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Carney & Snitker Expires June 5, 2017 [Page 1] Internet-Draft Validate December 2016 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Conventions Used in This Document . . . . . . . . . . . . 2 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Key Value . . . . . . . . . . . . . . . . . . . . . . . . 3 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 3 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 3 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 3 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 7 3.1.3. EPP Command . . . . . . . . . . . . . . . 7 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 7 3.2.1. EPP Command . . . . . . . . . . . . . . . . 7 3.2.2. EPP Command . . . . . . . . . . . . . . . . 7 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 7 3.2.4. EPP Command . . . . . . . . . . . . . . . 7 3.2.5. EPP Command . . . . . . . . . . . . . . . . 7 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. Validate Extension Schema . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 8. Change History . . . . . . . . . . . . . . . . . . . . . . . 11 8.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 11 8.2. Change from carney-regext 01 to ietf-regext 00 . . . . . 11 9. Normative References . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 1. Introduction This document describes a Validate mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. 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. 1.1. Conventions Used in This Document 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 [RFC2119]. Carney & Snitker Expires June 5, 2017 [Page 2] Internet-Draft Validate December 2016 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. 2. Object Attributes A EPP validation object has attributes and associated values that can be viewed by the client. This section describes each attribute type in detail. 2.1. Key Value Key Value provides a flexible mechanism to share data between the client and the server. The 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. o An example . o An example . 3. EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in [RFC5730]. The command mappings described here are specifically for the Validate Extension 3.1. EPP Query Commands EPP provides three commands to retrieve object information: to determine if an object is known to the server, to retrieve detailed information associated with an object, and to retrieve object transfer status information. 3.1.1. EPP Command The EPP command is used to validate a list of contact information. The command MUST contain a element that identifies the validate namespace. The element contains the following child elements: Carney & Snitker Expires June 5, 2017 [Page 3] Internet-Draft Validate December 2016 o one or more element(s) for each contact that is to be validated that contains the contact type of the contact to be validated. The element MUST contain the following child elements: o one element. o zero or more elements. The element MUST contain the following child elements: o one element. o an OPTIONAL element. o an OPTIONAL element. o an OPTIONAL element. o an OPTIONAL element. o an OPTIONAL element. o an OPTIONAL element. The following is an example command. C: 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: Carney & Snitker Expires June 5, 2017 [Page 4] Internet-Draft Validate December 2016 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: Carney & Snitker Expires June 5, 2017 [Page 5] Internet-Draft Validate December 2016 C: ABC-12345 C: C: When a command has been processed succesfully, the EPP element MUST contain a child element that identifies the validate namespace. The element MUST contain a element for each element contained in the command. The element MUST contain the following child elements: o one element. o one element. o zero or more elements. The following is an example of the response. S: 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: Carney & Snitker Expires June 5, 2017 [Page 6] Internet-Draft Validate December 2016 3.1.2. EPP Command Info semantics do not apply to validate objects, so there is no mapping defined for the EPP command. 3.1.3. EPP Command Transfer semantics do not apply to validate objects, so there is no mapping defined for the EPP command. 3.2. EPP Transform Commands EPP provides five commands to transform objects: to create an instance of an object with a server, to remove an instance of an object from a server, to extend the validity period of an object, to manage changes in client sponsorship of an object, and to change information. 3.2.1. EPP Command Create semantics do not apply to validate objects, so there is no mapping defined for the EPP command. 3.2.2. EPP Command Delete semantics do not apply to validate objects, so there is no mapping defined for the EPP command. 3.2.3. EPP Command Renew semantics do not apply to validate objects, so there is no mapping defined for the EPP command. 3.2.4. EPP Command Transfer semantics do not apply to validate objects, so there is no mapping defined for the EPP command. 3.2.5. EPP Command Update semantics do not apply to validate objects, so there is no mapping defined for the EPP command. 4. Formal Syntax One schema is presented here that is the EPP Validate Extension schema. Carney & Snitker Expires June 5, 2017 [Page 7] Internet-Draft Validate December 2016 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. 4.1. Validate Extension Schema BEGIN Extensible Provisioning Protocol v1.0 Validate Object Extension Carney & Snitker Expires June 5, 2017 [Page 8] Internet-Draft Validate December 2016 Carney & Snitker Expires June 5, 2017 [Page 9] Internet-Draft Validate December 2016 END 5. IANA Considerations 5.1. XML Namespace This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. 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. Carney & Snitker Expires June 5, 2017 [Page 10] Internet-Draft Validate December 2016 XML: See the "Formal Syntax" section of this document. 6. Security Considerations The mapping extensions described in this document do not provide any security services beyond those described by EPP [RFC5730] and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. 7. Acknowledgements The authors wish to thank the following persons for their feedback and suggestions: o Kevin Allendorf of GoDaddy Inc. o Jody Kolker of GoDaddy Inc. o James Gould of Verisign Inc 8. Change History 8.1. Change from 00 to 01 After review and broad feedback, extensive changes have been made transforming the original document from a standalone extension command to an extension using the command and response framework. 8.2. Change from carney-regext 01 to ietf-regext 00 Updated miscellaneous verbiage to reflect the change from an extension and changed to ietf naming as REGEXT WG will assume this work. 9. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . Carney & Snitker Expires June 5, 2017 [Page 11] Internet-Draft Validate December 2016 Authors' Addresses Roger Carney GoDaddy Inc. 14455 N. Hayden Rd. #219 Scottsdale, AZ 85260 US Email: rcarney@godaddy.com URI: http://www.godaddy.com Joseph Snitker GoDaddy Inc. 14455 N. Hayden Rd. #219 Scottsdale, AZ 85260 US Email: jsnitker@godaddy.com URI: http://www.godaddy.com Carney & Snitker Expires June 5, 2017 [Page 12]