RFC 1836: Representing the O/R Address hierarchy in the X.500 Directory Information Tree
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2294.
Current version: RFC 2294 — Representing the O/R Address hierarchy in the X.500 Directory Information Tree
In plain English — editorial summary, not part of the RFC
This document defines a representation of the O/R Address hierarchy in the Directory Information Tree [6, 1]. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1836
- Published
- August 1995
- Authors
- S. Kille
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 11
- Also known as
- —
- Obsoleted by:
- RFC 2294
Topics
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.
- RFC 1837Representing Tables and Subtrees in the X.500 DirectoryObsoleted
August 1995
- RFC 1838Use of the X.500 Directory to support mapping between X.400 and RFC 822 AddressesObsoleted
August 1995
- RFC 1802Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 RoutingCurrent
June 1995
- RFC 1801MHS use of the X.500 Directory to support MHS RoutingCurrent
June 1995
- RFC 1649Operational Requirements for X.400 Management Domains in the GO-MHS CommunityCurrent
July 1994
- RFC 1733Distributed Electronic Mail Models in IMAP4Current
December 1994
- RFC 1732IMAP4 Compatibility with IMAP2 and IMAP2bisCurrent
December 1994
- RFC 1731IMAP4 Authentication MechanismsCurrent
December 1994
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?