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.
- RFC 2294Representing the O/R Address hierarchy in the X.500 Directory Information TreeCurrent
March 1998
- RFC 2314PKCS #10: Certification Request Syntax Version 1.5Obsoleted
March 1998
- RFC 2254The String Representation of LDAP Search FiltersObsoleted
December 1997
- RFC 2253Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished NamesObsoleted
December 1997
- RFC 2252Lightweight Directory Access Protocol (v3): Attribute Syntax DefinitionsObsoleted
December 1997
- RFC 2251Lightweight Directory Access Protocol (v3)Obsoleted
December 1997
- RFC 2219Use of DNS Aliases for Network ServicesCurrent
October 1997
- RFC 2377Naming Plan for Internet Directory-Enabled ApplicationsUpdated
September 1998
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?