draft-ietf-regext-validate-00.txt | draft-ietf-regext-validate-01.txt | |||
---|---|---|---|---|
Registration Protocols Extensions R. Carney | Registration Protocols Extensions R. Carney | |||
Internet-Draft J. Snitker | Internet-Draft J. Snitker | |||
Intended status: Standards Track GoDaddy Inc. | 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) | Validate Mapping for the Extensible Provisioning Protocol (EPP) | |||
draft-ietf-regext-validate-00 | draft-ietf-regext-validate-01 | |||
Abstract | Abstract | |||
This document describes an Extensible Provisioning Protocol (EPP) | This document describes an Extensible Provisioning Protocol (EPP) | |||
mapping for the validation of contact and eligibility data. | mapping for the validation of contact and eligibility data. | |||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
skipping to change at page 1, line 31 ¶ | skipping to change at page 1, line 31 ¶ | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | 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 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. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
skipping to change at page 2, line 23 ¶ | skipping to change at page 2, line 23 ¶ | |||
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 3 | 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 3 | |||
3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 7 | 3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 7 | |||
3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 7 | 3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 7 | |||
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 7 | 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 7 | |||
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 7 | 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 7 | |||
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 7 | 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 7 | |||
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 7 | 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 7 | |||
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 7 | 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 7 | |||
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 7 | 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 7 | |||
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 7 | 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
4.1. Validate Extension Schema . . . . . . . . . . . . . . . . 8 | 4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8 | |||
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 | 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 | |||
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 10 | 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 | |||
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 | 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11 | |||
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 | 7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 11 | |||
8. Change History . . . . . . . . . . . . . . . . . . . . . . . 11 | 7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 11 | |||
8.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 11 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 | |||
8.2. Change from carney-regext 01 to ietf-regext 00 . . . . . 11 | 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 12 | |||
9. Normative References . . . . . . . . . . . . . . . . . . . . 11 | 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 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 | |||
1. Introduction | 1. Introduction | |||
This document describes a Validate mapping for version 1.0 of the | This document describes a Validate mapping for version 1.0 of the | |||
Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping | Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping | |||
specifies a flexible schema by which EPP clients and servers can | specifies a flexible schema by which EPP clients and servers can | |||
reliably validate contact and eligibility data. | reliably validate contact and eligibility data. | |||
With the increased number of restrictions on contacts and required | With the increased number of restrictions on contacts and required | |||
skipping to change at page 3, line 37 ¶ | skipping to change at page 3, line 37 ¶ | |||
below. | below. | |||
o An example <validate:kv key="VATID" value="0123456789"/>. | o An example <validate:kv key="VATID" value="0123456789"/>. | |||
o An example <validate:kv contactType="Admin" key="contact:cc" | o An example <validate:kv contactType="Admin" key="contact:cc" | |||
value="Invalid country code for admin contact, must be MX."/>. | value="Invalid country code for admin contact, must be MX."/>. | |||
3. EPP Command Mapping | 3. EPP Command Mapping | |||
A detailed description of the EPP syntax and semantics can be found | A detailed description of the EPP syntax and semantics can be found | |||
in [RFC5730]. The command mappings described here are specifically | in [RFC5730]. The command mappings described here are specifically | |||
for the Validate Extension | for the Validate Extension. | |||
3.1. EPP Query Commands | 3.1. EPP Query Commands | |||
EPP provides three commands to retrieve object information: <check> | EPP provides three commands to retrieve object information: <check> | |||
to determine if an object is known to the server, <info> to retrieve | to determine if an object is known to the server, <info> to retrieve | |||
detailed information associated with an object, and <transfer> to | detailed information associated with an object, and <transfer> to | |||
retrieve object transfer status information. | retrieve object transfer status information. | |||
3.1.1. EPP <check> Command | 3.1.1. EPP <check> Command | |||
skipping to change at page 7, line 50 ¶ | skipping to change at page 7, line 50 ¶ | |||
Transfer semantics do not apply to validate objects, so there is no | Transfer semantics do not apply to validate objects, so there is no | |||
mapping defined for the EPP <transfer> command. | mapping defined for the EPP <transfer> command. | |||
3.2.5. EPP <update> Command | 3.2.5. EPP <update> Command | |||
Update semantics do not apply to validate objects, so there is no | Update semantics do not apply to validate objects, so there is no | |||
mapping defined for the EPP <update> command. | mapping defined for the EPP <update> command. | |||
4. Formal Syntax | 4. Formal Syntax | |||
One schema is presented here that is the EPP Validate Extension | One schema is presented here that is the EPP Validate schema. | |||
schema. | ||||
The formal syntax presented here is a complete schema representation | The formal syntax presented here is a complete schema representation | |||
of the object mapping suitable for automated validation of EPP XML | of the object mapping suitable for automated validation of EPP XML | |||
instances. The BEGIN and END tags are not part of the schema; they | 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 | are used to note the beginning and ending of the schema for URI | |||
registration purposes. | registration purposes. | |||
4.1. Validate Extension Schema | 4.1. Validate Schema | |||
BEGIN | BEGIN | |||
<?xml version="1.0" encoding="UTF-8"?> | <?xml version="1.0" encoding="UTF-8"?> | |||
<schema | <schema | |||
targetNamespace="urn:ietf:params:xml:ns:validate-0.1" | targetNamespace="urn:ietf:params:xml:ns:validate-0.1" | |||
xmlns:validate="urn:ietf:params:xml:ns:validate-0.1" | xmlns:validate="urn:ietf:params:xml:ns:validate-0.1" | |||
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" | xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" | |||
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" | xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" | |||
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" | xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" | |||
xmlns="http://www.w3.org/2001/XMLSchema" | xmlns="http://www.w3.org/2001/XMLSchema" | |||
elementFormDefault="qualified"> | elementFormDefault="qualified"> | |||
<annotation> | <annotation> | |||
<documentation> | <documentation> | |||
Extensible Provisioning Protocol v1.0 | Extensible Provisioning Protocol v1.0 | |||
Validate Object Extension | Validate Object | |||
</documentation> | </documentation> | |||
</annotation> | </annotation> | |||
<!-- Import common element types. --> | <!-- Import common element types. --> | |||
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" | <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" | |||
schemaLocation="eppcom-1.0.xsd"/> | schemaLocation="eppcom-1.0.xsd"/> | |||
<import namespace="urn:ietf:params:xml:ns:epp-1.0" | <import namespace="urn:ietf:params:xml:ns:epp-1.0" | |||
schemaLocation="epp-1.0.xsd"/> | schemaLocation="epp-1.0.xsd"/> | |||
<import namespace="urn:ietf:params:xml:ns:contact-1.0" | <import namespace="urn:ietf:params:xml:ns:contact-1.0" | |||
schemaLocation="contact-1.0.xsd"/> | schemaLocation="contact-1.0.xsd"/> | |||
skipping to change at page 10, line 40 ¶ | skipping to change at page 10, line 40 ¶ | |||
type="epp:resultCodeType" /> | type="epp:resultCodeType" /> | |||
<element name="kv" | <element name="kv" | |||
type="validate:kvType" | type="validate:kvType" | |||
minOccurs="0" maxOccurs="unbounded" /> | minOccurs="0" maxOccurs="unbounded" /> | |||
</sequence> | </sequence> | |||
</complexType> | </complexType> | |||
</schema> | </schema> | |||
END | 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 | This document uses URNs to describe XML namespaces and XML schemas | |||
conforming to a registry mechanism described in [RFC3688]. The | conforming to a registry mechanism described in [RFC3688]. The | |||
following URI assignment is requested of IANA: | following URI assignment is requested of IANA: | |||
URI: ietf:params:xml:ns:validate-1.0 | URI: ietf:params:xml:ns:validate-1.0 | |||
Registrant Contact: See the "Author's Address" section of this | Registrant Contact: See the "Author's Address" section of this | |||
document. | document. | |||
XML: See the "Formal Syntax" 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 | Note to RFC Editor: Please remove this section and the reference to | |||
security services beyond those described by EPP [RFC5730] and | [RFC6982] before publication. | |||
protocol layers used by EPP. The security considerations described | ||||
in these other specifications apply to this specification as well. | ||||
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 | The authors wish to thank the following persons for their feedback | |||
and suggestions: | and suggestions: | |||
o Kevin Allendorf of GoDaddy Inc. | o Kevin Allendorf of GoDaddy Inc. | |||
o Jody Kolker of GoDaddy Inc. | o Jody Kolker of GoDaddy Inc. | |||
o James Gould of Verisign 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 | After review and broad feedback, extensive changes have been made | |||
transforming the original document from a standalone extension | transforming the original document from a standalone extension | |||
command to an extension using the <check> command and response | command to using the <check> command and response framework. Stubbed | |||
framework. | 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 | Updated miscellaneous verbiage to reflect the change from an | |||
extension and changed to ietf naming as REGEXT WG will assume this | extension and changed to ietf naming as REGEXT WG will assume this | |||
work. | work. | |||
9. Normative References | 10. Normative References | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
<http://www.rfc-editor.org/info/rfc2119>. | <http://www.rfc-editor.org/info/rfc2119>. | |||
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | |||
DOI 10.17487/RFC3688, January 2004, | DOI 10.17487/RFC3688, January 2004, | |||
<http://www.rfc-editor.org/info/rfc3688>. | <http://www.rfc-editor.org/info/rfc3688>. | |||
End of changes. 20 change blocks. | ||||
32 lines changed or deleted | 62 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |