Extensible Provisioning Protocol (EPP) Domain Name Mapping
RFC 4931
Document | Type |
RFC - Draft Standard
(May 2007; No errata)
Obsoleted by RFC 5731
Obsoletes RFC 3731
Was draft-hollenbeck-epp-rfc3731bis (individual in app area)
|
|
---|---|---|---|
Author | Scott Hollenbeck | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4931 (Draft Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ted Hardie | ||
Send notices to | (None) |
Network Working Group S. Hollenbeck Request for Comments: 4931 VeriSign, Inc. Obsoletes: 3731 May 2007 Category: Standards Track 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 IETF Trust (2007). 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. This document obsoletes RFC 3731. Hollenbeck Standards Track [Page 1] RFC 4931 EPP Domain Name Mapping May 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Relationship of Domain Objects and Host Objects . . . . . 3 1.2. Conventions Used in This Document . . . . . . . . . . . . 5 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Domain and Host Names . . . . . . . . . . . . . . . . . . 5 2.2. Contact and Client Identifiers . . . . . . . . . . . . . . 5 2.3. Status Values . . . . . . . . . . . . . . . . . . . . . . 5 2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 7 2.5. Validity Periods . . . . . . . . . . . . . . . . . . . . . 8 2.6. Authorization Information . . . . . . . . . . . . . . . . 8 2.7. Other DNS Resource Record Attributes . . . . . . . . . . . 8 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 9 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 9 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 9 3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . . 11 3.1.3. EPP <transfer> Query Command . . . . . . . . . . . . . 15 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 17 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 18 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 20 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 23 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 25 3.3. Offline Review of Requested Actions . . . . . . . . . . . 28 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 31 5. Internationalization Considerations . . . . . . . . . . . . . 40 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 7. Security Considerations . . . . . . . . . . . . . . . . . . . 41 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 41 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 42 9.1. Normative References . . . . . . . . . . . . . . . . . . . 42 9.2. Informative References . . . . . . . . . . . . . . . . . . 43 Appendix A. Changes from RFC 3731 . . . . . . . . . . . . . . . . 44 Hollenbeck Standards Track [Page 2] RFC 4931 EPP Domain Name Mapping May 2007 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 [W3C.REC-xml-20040204] and XML Schema notation as described in [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. This document obsoletes RFC 3731 [RFC3731]. [RFC4930] 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 [RFC4932]. 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 doShow full document text