RFC 3732: Extensible Provisioning Protocol (EPP) Host Mapping
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4932.
Current document in this lineage: RFC 5732 — Extensible Provisioning Protocol (EPP) Host Mapping
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3732
- Published
- March 2004
- Authors
- S. Hollenbeck
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 28
- Also known as
- —
- Obsoleted by:
- RFC 4932
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3732 (2004)
- RFC 4932 (2007)
- RFC 5732 (2009) ✓
Read the full history of Extensible Provisioning Protocol (EPP) Host Mapping →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3731Extensible Provisioning Protocol (EPP) Domain Name MappingObsoleted
March 2004
- RFC 3733Extensible Provisioning Protocol (EPP) Contact MappingObsoleted
March 2004
- RFC 2718Guidelines for new URL SchemesObsoleted
November 1999
- RFC 2717Registration Procedures for URL Scheme NamesObsoleted
November 1999
- RFC 4395Guidelines and Registration Procedures for New URI SchemesObsoleted
February 2006
- RFC 4931Extensible Provisioning Protocol (EPP) Domain Name MappingObsoleted
May 2007
- RFC 4933Extensible Provisioning Protocol (EPP) Contact MappingObsoleted
May 2007
- RFC 3859Common Profile for Presence (CPP)Current
August 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?