RFC 3732 (rfc3732) - Page 2 of 28
Extensible Provisioning Protocol (EPP) Host Mapping
Alternative Format: Original Text Document
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].
[RFC 3730] 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 repository
in which the host is being used for delegation purposes.
Whether a host is external or internal relates to the repository in
which the host is being used for delegation purposes. Whether an
internal host is subordinate or not relates to a domain within the
Hollenbeck Standards Track