CurrentPROPOSED STANDARDIETF stream

RFC 2293: Representing Tables and Subtrees in the X.500 Directory

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

This document defines techniques for representing two types of information mapping in the OSI Directory: Mapping from a key to a value (or set of values), as might be done in a table lookup, and mapping from a distinguished name to an associated value (or values), where the values are not defined by the owner of the entry. This is achieved by use of a directory subtree. [STANDARDS-TRCK]

Document record

Document ID
RFC2293
Published
March 1998
Authors
S. Kille
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
8
Also known as
Obsoletes:
RFC 1837

Topics

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/2293-representing-tables-and-subtrees-in-the-x-500-directory