draft-ietf-regext-validate-01.txt   draft-ietf-regext-validate-02.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: December 6, 2017 June 4, 2017 Expires: February 4, 2018 August 3, 2017
Validate Mapping for the Extensible Provisioning Protocol (EPP) Validate Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-validate-01 draft-ietf-regext-validate-02
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 December 6, 2017. This Internet-Draft will expire on February 4, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 2 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Key Value . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Key Value . . . . . . . . . . . . . . . . . . . . . . . . 3
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 3 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 3
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 3 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 3
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 3 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 4
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 . . . . . . . . . . . . . . . . . 8
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 7 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 7 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 8
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 7 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 8
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 7 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 8
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 7 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 8
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8 4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11
7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 11 7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 12
7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 11 7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
9. Change History . . . . . . . . . . . . . . . . . . . . . . . 12 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 12
9.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 12 9.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 12
9.2. Change from carney-regext 01 to ietf-regext 00 . . . . . 12 9.2. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 13
10. Normative References . . . . . . . . . . . . . . . . . . . . 12 9.3. Change from carney-regext 01 to ietf-regext 00 . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 10. Normative References . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
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
data points (license, ids, etc.) to register a domain name, a way to data points (license, ids, etc.) to register a domain name, a way to
skipping to change at page 4, line 48 skipping to change at page 5, line 6
C: <contact:name>John Doe</contact:name> C: <contact:name>John Doe</contact:name>
C: <contact:org>Example Inc.</contact:org> C: <contact:org>Example Inc.</contact:org>
C: <contact:addr> C: <contact:addr>
C: <contact:street>123 Example Dr.</contact:street> C: <contact:street>123 Example Dr.</contact:street>
C: <contact:street>Suite 100</contact:street> C: <contact:street>Suite 100</contact:street>
C: <contact:city>Dulles</contact:city> C: <contact:city>Dulles</contact:city>
C: <contact:sp>VA</contact:sp> C: <contact:sp>VA</contact:sp>
C: <contact:pc>20166-6503</contact:pc> C: <contact:pc>20166-6503</contact:pc>
C: <contact:cc>US</contact:cc> C: <contact:cc>US</contact:cc>
C: </contact:addr> C: </contact:addr>
C: </validate:postalInfo> C: </validate:postalInfo>
C: <validate:voice>+1.7035555555</validate:voice> C: <validate:voice>+1.7035555555</validate:voice>
C: <validate:fax>+1.7035555556</validate:fax> C: <validate:fax>+1.7035555556</validate:fax>
C: <validate:email>jdoe@example.com</validate:email> C: <validate:email>jdoe@example.com</validate:email>
C: <validate:authInfo> C: <validate:authInfo>
C: <contact:pw>2fooBAR</contact:pw> C: <contact:pw>2fooBAR</contact:pw>
C: </validate:authInfo> C: </validate:authInfo>
C: <validate:disclose flag="0"> C: <validate:disclose flag="0">
C: <contact:voice/> C: <contact:voice/>
C: <contact:email/> C: <contact:email/>
C: </validate:disclose> C: </validate:disclose>
C: </validate:cd> C: </validate:cd>
C: <validate:kv key="VAT" value="1234567890"/> C: <validate:kv key="VAT" value="1234567890"/>
C: </validate:contact> C: </validate:contact>
C: <validate:contact contactType="tech" tld="COM"> C: <validate:contact contactType="tech" tld="COM">
C: <validate:cd> C: <validate:cd>
C: <validate:id>sh8013</validate:id> C: <validate:id>sh8013</validate:id>
C: </validate:cd> C: </validate:cd>
C: </validate:contact> C: </validate:contact>
C: <validate:contact contactType="admin" tld="COM"> C: <validate:contact contactType="admin" tld="COM">
C: <validate:cd> C: <validate:cd>
C: <validate:id>sh8014</validate:id> C: <validate:id>sh8014</validate:id>
C: <validate:postalInfo type="int"> C: <validate:postalInfo type="int">
C: <contact:name>John Doe</contact:name> C: <contact:name>John Doe</contact:name>
C: <contact:org>Example Inc.</contact:org> C: <contact:org>Example Inc.</contact:org>
C: <contact:addr> C: <contact:addr>
C: <contact:street>123 Example Dr.</contact:street> C: <contact:street>123 Example Dr.</contact:street>
C: <contact:street>Suite 100</contact:street> C: <contact:street>Suite 100</contact:street>
C: <contact:city>Dulles</contact:city> C: <contact:city>Dulles</contact:city>
C: <contact:sp>VA</contact:sp> C: <contact:sp>VA</contact:sp>
C: <contact:pc>20166-6503</contact:pc> C: <contact:pc>20166-6503</contact:pc>
C: <contact:cc>US</contact:cc> C: <contact:cc>US</contact:cc>
C: </contact:addr> C: </contact:addr>
C: </validate:postalInfo> C: </validate:postalInfo>
C: <validate:voice>+1.7035555555</validate:voice> C: <validate:voice>+1.7035555555</validate:voice>
C: <validate:fax>+1.7035555556</validate:fax> C: <validate:fax>+1.7035555556</validate:fax>
C: <validate:email>jdoe@example.com</validate:email> C: <validate:email>jdoe@example.com</validate:email>
C: <validate:authInfo> C: <validate:authInfo>
C: <contact:pw>2fooBAR</contact:pw> C: <contact:pw>2fooBAR</contact:pw>
C: </validate:authInfo> C: </validate:authInfo>
C: <validate:disclose flag="0"> C: <validate:disclose flag="0">
C: <contact:voice/> C: <contact:voice/>
C: <contact:email/> C: <contact:email/>
C: </validate:disclose> C: </validate:disclose>
C: </validate:cd> C: </validate:cd>
C: </validate:contact> C: </validate:contact>
C: <validate:contact contactType="billing" tld="COM"> C: <validate:contact contactType="billing" tld="COM">
C: <validate:cd> C: <validate:cd>
C: <validate:id>sh8014</validate:id> C: <validate:id>sh8014</validate:id>
C: </validate:cd> C: </validate:cd>
C: </validate:contact> C: </validate:contact>
C: </validate:check> C: </validate:check>
C: </check> C: </check>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When a <check> command has been processed succesfully, the EPP When a <check> command has been processed succesfully, the EPP
<resData> element MUST contain a child <validate:chkData> element <resData> element MUST contain a child <validate:chkData> element
that identifies the validate namespace. The <validate:chkData> that identifies the validate namespace. The <validate:chkData>
element MUST contain a <validate:cd> element for each element MUST contain a <validate:cd> element for each
<validate:check> element contained in the <check> command. The <validate:check> element contained in the <check> command. The
skipping to change at page 12, line 4 skipping to change at page 12, line 40
7.1. To Be Filled In 7.1. To Be Filled In
Add implementation details once available. Add implementation details once available.
8. Acknowledgements 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
9. Change History 9. Change History
9.1. Change from 00 to 01 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 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 using the <check> command and response framework. Stubbed command to using the <check> 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 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.
10. 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,
 End of changes. 14 change blocks. 
75 lines changed or deleted 79 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/