metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 3730: Extensible Provisioning Protocol (EPP)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4930.

Current document in this lineage: RFC 5730 — Extensible Provisioning Protocol (EPP)

In plain English — editorial summary, not part of the RFC

This document describes an application layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document includes a protocol specification, an object mapping template, and an XML media type registration. [STANDARDS-TRACK]

Document record

Document ID
RFC3730
Published
March 2004
Authors
S. Hollenbeck
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
69
Also known as
—
Obsoleted by:
RFC 4930

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 3730 (2004)
  2. RFC 4930 (2007)
  3. RFC 5730 (2009) ✓

Read the full history of Extensible Provisioning Protocol (EPP) →

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.

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?

canonical URL: /rfc/3730-extensible-provisioning-protocol-epp