metasystema.org
ObsoletedDRAFT STANDARDIETF stream

RFC 4934: Extensible Provisioning Protocol (EPP) Transport Over TCP

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

Current document in this lineage: RFC 5734 — Extensible Provisioning Protocol (EPP) Transport over TCP

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

This document describes how an Extensible Provisioning Protocol (EPP) session is mapped onto a single Transmission Control Protocol (TCP) connection. This mapping requires use of the Transport Layer Security (TLS) protocol to protect information exchanged between an EPP client and an EPP server. This document obsoletes RFC 3734. [STANDARDS-TRACK]

Document record

Document ID
RFC4934
Published
May 2007
Authors
S. Hollenbeck
Status
DRAFT STANDARD
Stream
IETF
Area
—
Pages
10
Also known as
—
Obsoletes:
RFC 3734
Obsoleted by:
RFC 5734

Topics

Standards lineage

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

  1. RFC 3734 (2004)
  2. RFC 4934 (2007)
  3. RFC 5734 (2009) ✓

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

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/4934-extensible-provisioning-protocol-epp-transport-over-tcp