Extensible Provisioning Protocol (EPP) Host Mapping
RFC 3732
Document | Type |
RFC - Proposed Standard
(March 2004; No errata)
Obsoleted by RFC 4932
|
|
---|---|---|---|
Author | Scott Hollenbeck | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3732 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ted Hardie | ||
Send notices to | (None) |
Network Working Group S. Hollenbeck Request for Comments: 3732 VeriSign, Inc. Category: Standards Track March 2004 Extensible Provisioning Protocol (EPP) Host 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 host names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to host names. Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Relationship of Host Objects and Domain Objects . . . . 2 1.2. Conventions Used In This Document . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Host Names. . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Client Identifiers. . . . . . . . . . . . . . . . . . . 3 2.3. Status Values . . . . . . . . . . . . . . . . . . . . . 3 2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . 5 2.5. IP Addresses. . . . . . . . . . . . . . . . . . . . . . 5 3. EPP Command Mapping. . . . . . . . . . . . . . . . . . . . . . 6 3.1. EPP Query Commands. . . . . . . . . . . . . . . . . . . 6 3.1.1. EPP <check> Command . . . . . . . . . . . . . . 6 3.1.2. EPP <info> Command. . . . . . . . . . . . . . . 8 3.1.3. EPP <transfer> Query Command. . . . . . . . . . 10 3.2. EPP Transform Commands. . . . . . . . . . . . . . . . . 11 3.2.1. EPP <create> Command. . . . . . . . . . . . . . 11 3.2.2. EPP <delete> Command. . . . . . . . . . . . . . 13 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . 14 3.2.4. EPP <transfer> Command. . . . . . . . . . . . . 14 3.2.5. EPP <update> Command. . . . . . . . . . . . . . 15 Hollenbeck Standards Track [Page 1] RFC 3732 EPP Host Mapping March 2004 3.2.6. Offline Review of Requested Actions . . . . . . 17 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 19 5. Internationalization Considerations . . . . . . . . . . . . . 24 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 7. Security Considerations . . . . . . . . . . . . . . . . . . . 25 8. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 25 9. References. . . . . . . . . . . . . . . . . . . . . . . . . . 26 9.1. Normative References. . . . . . . . . . . . . . . . . . 26 9.2. Informative References. . . . . . . . . . . . . . . . . 27 10. Author's Address. . . . . . . . . . . . . . . . . . . . . . . 27 11. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 28 1. Introduction This document describes an Internet host 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 Host Objects and Domain Objects This document assumes that host name objects have a subordinate relationship to a superordinate domain name object. For example, host name "ns1.example.com" has a subordinate relationship to domain name "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 DNS domains in ".example" can be delegated to the host. Such hosts are described as "external" hosts in this specification since the name of the host does not belong to the name space of the repositoryShow full document text