Extensible Provisioning Protocol (EPP) Domain Name Mapping
RFC 3731

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

• Versions
• 07

Network Working Group                                      S. Hollenbeck
Request for Comments: 3731                                VeriSign, Inc.
Category: Standards Track                                     March 2004

       Extensible Provisioning Protocol (EPP) Domain Name Mapping

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.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

Abstract

   This document describes an Extensible Provisioning Protocol (EPP)
   mapping for the provisioning and management of Internet domain names
   stored in a shared central repository.  Specified in XML, the mapping
   defines EPP command syntax and semantics as applied to domain names.

Table of Contents

   1.  Introduction. . . . . . . . . . . . . . . . . . . . . . . . .   2
       1.1.  Relationship of Domain Objects and Host Objects . . . .   2
       1.2.  Conventions Used In This Document . . . . . . . . . . .   4
   2.  Object Attributes . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.  Domain and Host Names . . . . . . . . . . . . . . . . .   4
       2.2.  Contact and Client Identifiers. . . . . . . . . . . . .   5
       2.3.  Status Values . . . . . . . . . . . . . . . . . . . . .   5
       2.4.  Dates and Times . . . . . . . . . . . . . . . . . . . .   7
       2.5.  Validity Periods. . . . . . . . . . . . . . . . . . . .   7
       2.6.  Authorization Information . . . . . . . . . . . . . . .   7
       2.7.  Other DNS Resource Record Attributes. . . . . . . . . .   7
   3.  EPP Command Mapping . . . . . . . . . . . . . . . . . . . . .   8
       3.1.  EPP Query Commands. . . . . . . . . . . . . . . . . . .   8
             3.1.1.  EPP <check> Command . . . . . . . . . . . . . .   8
             3.1.2.  EPP <info> Command. . . . . . . . . . . . . . .  10
             3.1.3.  EPP <transfer> Query Command. . . . . . . . . .  16
       3.2.  EPP Transform Commands. . . . . . . . . . . . . . . . .  18
             3.2.1.  EPP <create> Command. . . . . . . . . . . . . .  19
             3.2.2.  EPP <delete> Command. . . . . . . . . . . . . .  21
             3.2.3.  EPP <renew> Command . . . . . . . . . . . . . .  23

Hollenbeck                  Standards Track                     [Page 1]
RFC 3731                EPP Domain Name Mapping               March 2004

             3.2.4.  EPP <transfer> Command. . . . . . . . . . . . .  24
             3.2.5.  EPP <update> Command. . . . . . . . . . . . . .  27
             3.2.6.  Offline Review of Requested Actions . . . . . .  29
   4.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .  32
   5.  Internationalization Considerations . . . . . . . . . . . . .  41
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  42
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  42
   8.  Acknowledgements. . . . . . . . . . . . . . . . . . . . . . .  42
   9.  References. . . . . . . . . . . . . . . . . . . . . . . . . .  43
       9.1.  Normative References. . . . . . . . . . . . . . . . . .  43
       9.2.  Informative References. . . . . . . . . . . . . . . . .  43
   10. Author's Address. . . . . . . . . . . . . . . . . . . . . . .  44
   11. Full Copyright Statement. . . . . . . . . . . . . . . . . . .  45

1.  Introduction

   This document describes an Internet domain name mapping for version
   1.0 of the Extensible Provisioning Protocol (EPP).  This mapping is
   specified using the Extensible Markup Language (XML) 1.0 as described
   in [XML] and XML Schema notation as described in [XMLS-1] and
   [XMLS-2].

   [RFC3730] 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.

   XML is case sensitive.  Unless stated otherwise, XML specifications
   and examples provided in this document MUST be interpreted in the
   character case presented to develop a conforming implementation.

1.1.  Relationship of Domain Objects and Host Objects

   The EPP mapping for host objects is described in [RFC3732].  This
   document assumes that domain name objects have a superordinate
   relationship to subordinate host name objects.  For example, domain
   name "example.com" has a superordinate relationship to host name
   "ns1.example.com".  EPP actions (such as object transfers) that do
   not preserve this relationship MUST be explicitly disallowed.

   A host name object can be created in a repository for which no
   superordinate domain name object exists.  For example, host name
   "ns1.example.com" can be created in the ".example" repository so that