Representing Tables and Subtrees in the X.500 Directory, March 1998
- Canonical URL:
- File formats:
- PROPOSED STANDARD
- RFC 1837
- S. Kille
- mixer (app)
Discuss this RFC: Send questions or comments to email@example.com
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.