Validate Mapping for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-validate-04

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04

Registration Protocols Extensions                              R. Carney
Internet-Draft                                                J. Snitker
Intended status: Standards Track                            GoDaddy Inc.
Expires: April 14, 2019                                 October 11, 2018

    Validate Mapping for the Extensible Provisioning Protocol (EPP)
                     draft-ietf-regext-validate-04

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 https://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 April 14, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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 April 14, 2019                 [Page 1]
Internet-Draft                  Validate                    October 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   3
   2.  Object Attributes . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Key Value . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Validate Id . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Validate PostalInfo, Voice, Fax, Email, AuthInfo  . . . .   4
   3.  EPP Command Mapping . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  EPP Query Commands  . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  EPP <check> Command . . . . . . . . . . . . . . . . .   4
       3.1.2.  EPP <info> Command  . . . . . . . . . . . . . . . . .   8
       3.1.3.  EPP <transfer> Command  . . . . . . . . . . . . . . .   8
     3.2.  EPP Transform Commands  . . . . . . . . . . . . . . . . .   9
       3.2.1.  EPP <create> Command  . . . . . . . . . . . . . . . .   9
       3.2.2.  EPP <delete> Command  . . . . . . . . . . . . . . . .   9
       3.2.3.  EPP <renew> Command . . . . . . . . . . . . . . . . .   9
       3.2.4.  EPP <transfer> Command  . . . . . . . . . . . . . . .   9
       3.2.5.  EPP <update> Command  . . . . . . . . . . . . . . . .   9
   4.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Validate Schema . . . . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  XML Namespace . . . . . . . . . . . . . . . . . . . . . .  13
   7.  Implemntation Status  . . . . . . . . . . . . . . . . . . . .  13
     7.1.  To Be Filled In . . . . . . . . . . . . . . . . . . . . .  14
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   9.  Change History  . . . . . . . . . . . . . . . . . . . . . . .  14
     9.1.  Change from 03 to 04  . . . . . . . . . . . . . . . . . .  14
     9.2.  Change from 02 to 03  . . . . . . . . . . . . . . . . . .  14
     9.3.  Change from 01 to 02  . . . . . . . . . . . . . . . . . .  14
     9.4.  Change from 00 to 01  . . . . . . . . . . . . . . . . . .  14
     9.5.  Change from carney-regext 01 to ietf-regext 00  . . . . .  15
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

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