metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3983: Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)

Still current, but amended. Parts of this document are changed or extended by RFC 8996. Read both.

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

This document specifies how to use the Blocks Extensible Exchange Protocol (BEEP) as the application transport substrate for the Internet Registry Information Service (IRIS). [STANDARDS-TRACK]

Document record

Document ID
RFC3983
Published
January 2005
Authors
A. Newton; M. Sanz
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
12
Also known as
—
Updated by:
RFC 8996

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/3983-using-the-internet-registry-information-service-iris-over-the-blocks-extensible