--- 1/draft-ietf-regext-validate-01.txt 2017-08-03 12:13:08.980822506 -0700 +++ 2/draft-ietf-regext-validate-02.txt 2017-08-03 12:13:09.000822761 -0700 @@ -1,18 +1,18 @@ Registration Protocols Extensions R. Carney Internet-Draft J. Snitker Intended status: Standards Track GoDaddy Inc. -Expires: December 6, 2017 June 4, 2017 +Expires: February 4, 2018 August 3, 2017 Validate Mapping for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-validate-01 + draft-ietf-regext-validate-02 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. @@ -20,67 +20,68 @@ 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 December 6, 2017. + This Internet-Draft will expire on February 4, 2018. Copyright Notice Copyright (c) 2017 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 - 1.1. Conventions Used in This Document . . . . . . . . . . . . 2 + 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 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.1. EPP Command . . . . . . . . . . . . . . . . . 4 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 + 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 + 3.2.1. EPP Command . . . . . . . . . . . . . . . . 8 + 3.2.2. EPP Command . . . . . . . . . . . . . . . . 8 + 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 8 + 3.2.4. EPP Command . . . . . . . . . . . . . . . 8 + 3.2.5. EPP Command . . . . . . . . . . . . . . . . 8 + 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 - 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 + 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11 - 7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 11 - 7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 11 - 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 + 7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 12 + 7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 12 + 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 12 9.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 12 - 9.2. Change from carney-regext 01 to ietf-regext 00 . . . . . 12 - 10. Normative References . . . . . . . . . . . . . . . . . . . . 12 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 + 9.2. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 13 + 9.3. Change from carney-regext 01 to ietf-regext 00 . . . . . 13 + 10. Normative References . . . . . . . . . . . . . . . . . . . . 13 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 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 @@ -514,34 +516,37 @@ 7.1. To Be Filled In Add implementation details once available. 8. 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 9. Change History 9.1. Change from 00 to 01 + Corrected some formatting issues + +9.2. 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 using the command and response framework. Stubbed - in an Implementation section for later documentation + in an Implementation section for later documentation. -9.2. Change from carney-regext 01 to ietf-regext 00 +9.3. 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. 10. 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,