ENUM Validation Information Mapping for the Extensible Provisioning Protocol
RFC 5076

Network Working Group                                       B. Hoeneisen
Request for Comments: 5076                                        SWITCH
Category: Standards Track                                  December 2007

                  ENUM Validation Information Mapping
                for the Extensible Provisioning Protocol

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Abstract

   This document describes an Extensible Provisioning Protocol (EPP)
   extension framework for mapping information about the validation
   process that has been applied for the E.164 number (or number range)
   that the E.164 Number Mapping (ENUM) domain name is based on.
   Specified in the Extensible Markup Language (XML), this mapping
   extends the EPP domain name mapping to provide an additional feature
   required for the provisioning of ENUM Domain Names.

Hoeneisen                   Standards Track                     [Page 1]
RFC 5076            ENUM Validation Mapping for EPP        December 2007

Table of Contents
   1. Introduction ....................................................2
   2. Terminology .....................................................3
   3. Requirements ....................................................4
   4. Object Attributes ...............................................4
      4.1. ENUM Domain Names ..........................................4
      4.2. Validation Information Commands ............................4
      4.3. Id .........................................................4
      4.4. Validation Information .....................................5
      4.5. Validation Elements in the Example .........................5
           4.5.1. Method Identifier ...................................5
           4.5.2. Validation Entity Identifier ........................5
           4.5.3. Registrar Identifier ................................5
           4.5.4. Execution Date ......................................6
           4.5.5. Expiration Date .....................................6
   5. EPP Command Mapping .............................................6
      5.1. EPP Query Commands .........................................6
           5.1.1. EPP <check> Command .................................6
           5.1.2. EPP <info> Command ..................................6
           5.1.3. EPP <transfer> Command ..............................8
      5.2. EPP Transform Commands .....................................9
           5.2.1. EPP <create> Command ................................9
           5.2.2. EPP <delete> Command ...............................11
           5.2.3. EPP <renew> Command ................................11
           5.2.4. EPP <transfer> Command .............................13
           5.2.5. EPP <update> Command ...............................15
   6. Formal Syntax ..................................................16
   7. IANA Considerations ............................................21
   8. Security Considerations ........................................21
   9. Acknowledgements ...............................................22
   10. References ....................................................22
      10.1. Normative References .....................................22
      10.2. Informative References ...................................23

1.  Introduction

   This document describes a framework for an ENUM [2] validation
   information mapping for version 1.0 of EPP [3].  This mapping, an
   extension of the EPP domain name mapping described in [4], is
   specified using XML 1.0, as described in [5], and XML Schema
   notation, as described in [6] and [7].

   The EPP core protocol specification [3] provides a complete
   description of EPP command and response structures.  A thorough
   understanding of the base protocol specification is necessary to
   understand the mapping described in this document.

Hoeneisen                   Standards Track                     [Page 2]
RFC 5076            ENUM Validation Mapping for EPP        December 2007

   ENUM [2] describes how the Domain Name System (DNS) can be used to
   identify services associated with an E.164 number.

   As described in RFC 4725 [9], usually only the Assignee of the E.164
   number (or number range) has the right to register the corresponding
   ENUM domain name.  Therefore, an ENUM validation process has to be
   applied before the ENUM domain name can be inserted into the DNS.