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

Document Type Active Internet-Draft (regext WG)
Last updated 2017-06-05
Replaces draft-carney-regext-validate
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Registration Protocols Extensions                              R. Carney
Internet-Draft                                                J. Snitker
Intended status: Standards Track                            GoDaddy Inc.
Expires: December 6, 2017                                   June 4, 2017

    Validate Mapping for the Extensible Provisioning Protocol (EPP)
                     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.

   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.

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.

Carney & Snitker        Expires December 6, 2017                [Page 1]
Internet-Draft                  Validate                       June 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   2
   2.  Object Attributes . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Key Value . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  EPP Command Mapping . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  EPP Query Commands  . . . . . . . . . . . . . . . . . . .   3
       3.1.1.  EPP <check> Command . . . . . . . . . . . . . . . . .   3
       3.1.2.  EPP <info> Command  . . . . . . . . . . . . . . . . .   7
       3.1.3.  EPP <transfer> Command  . . . . . . . . . . . . . . .   7
     3.2.  EPP Transform Commands  . . . . . . . . . . . . . . . . .   7
       3.2.1.  EPP <create> Command  . . . . . . . . . . . . . . . .   7
       3.2.2.  EPP <delete> Command  . . . . . . . . . . . . . . . .   7
       3.2.3.  EPP <renew> Command . . . . . . . . . . . . . . . . .   7
       3.2.4.  EPP <transfer> Command  . . . . . . . . . . . . . . .   7
       3.2.5.  EPP <update> Command  . . . . . . . . . . . . . . . .   7
   4.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .   7
     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
   data points (license, ids, etc.) to register a domain name, a way to
   validate the data points prior to issuing a transform command is
   becoming more important.

1.1.  Conventions Used in This Document
Show full document text