--- 1/draft-ietf-regext-validate-00.txt 2017-06-05 12:13:09.432414777 -0700 +++ 2/draft-ietf-regext-validate-01.txt 2017-06-05 12:13:09.456415349 -0700 @@ -1,18 +1,18 @@ Registration Protocols Extensions R. Carney Internet-Draft J. Snitker Intended status: Standards Track GoDaddy Inc. -Expires: June 5, 2017 December 2, 2016 +Expires: December 6, 2017 June 4, 2017 Validate Mapping for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-validate-00 + draft-ietf-regext-validate-01 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,25 +20,25 @@ 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. + This Internet-Draft will expire on December 6, 2017. Copyright Notice - Copyright (c) 2016 IETF Trust and the persons identified as the + 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 @@ -55,29 +55,31 @@ 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 + 4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 + 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 + 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11 + 7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 11 + 7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 11 + 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 + 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 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 @@ -116,21 +118,21 @@ 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 + 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 @@ -322,46 +324,45 @@ 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. + One schema is presented here that is the EPP Validate 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. -4.1. Validate Extension Schema +4.1. Validate Schema BEGIN Extensible Provisioning Protocol v1.0 - Validate Object Extension + Validate Object @@ -457,67 +458,96 @@ type="epp:resultCodeType" /> END -5. IANA Considerations +5. Security Considerations -5.1. XML Namespace + 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. + +6. IANA Considerations +6.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. XML: See the "Formal Syntax" section of this document. -6. Security Considerations +7. Implemntation Status - 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. + Note to RFC Editor: Please remove this section and the reference to + [RFC6982] before publication. -7. Acknowledgements + This section records the status of known implementations of the + protocol defined by this specification at the time of posting of this + Internet-Draft, and is based on a proposal described in [RFC6982]. + The description of implementations in this section is intended to + assist the IETF in its decision processes in progressing drafts to + RFCs. Please note that the listing of any individual implementation + here does not imply endorsement by the IETF. Furthermore, no effort + has been spent to verify the information presented here that was + supplied by IETF contributors. This is not intended as, and must not + be construed to be, a catalog of available implementations or their + features. Readers are advised to note that other implementations may + exist. + + According to [RFC6982], "this will allow reviewers and working groups + to assign due consideration to documents that have the benefit of + running code, which may serve as evidence of valuable experimentation + and feedback that have made the implemented protocols more mature. + It is up to the individual working groups to use this information as + they see fit". + +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 -8. Change History +9. Change History -8.1. Change from 00 to 01 +9.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. + command to using the command and response framework. Stubbed + in an Implementation section for later documentation -8.2. Change from carney-regext 01 to ietf-regext 00 +9.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 +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, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, .