ObsoletedDRAFT STANDARDIETF stream

RFC 4933: Extensible Provisioning Protocol (EPP) Contact Mapping

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

Current document in this lineage: RFC 5733 — Extensible Provisioning Protocol (EPP) Contact 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 individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in Extensible Markup Language (XML), the mapping defines EPP command syntax and semantics as applied to contacts. This document obsoletes RFC 3733. [STANDARDS-TRACK]

Document record

Document ID: RFC4933
Published: May 2007
Authors: S. Hollenbeck
Status: DRAFT STANDARD
Stream: IETF
Area: —
Pages: 43
Also known as: —

Obsoletes:: RFC 3733
Obsoleted by:: RFC 5733

Topics

Standards lineage

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

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

Referenced by

One later RFC formally updates or obsoletes part of this document.

RFC 5733Extensible Provisioning Protocol (EPP) Contact MappingCurrent
August 2009

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 23 August 2026. RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?