Technology and engineering · 1998
RFC 2294: Representing the O/R Address hierarchy in the X.500 Directory Information Tree
by S. Kille
This document defines a representation of the O/R Address hierarchy in the Directory Information Tree. [STANDARDS-TRACK]
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 1998
- Status
- Proposed Standard
- Pages
- 13
- Obsoletes
- RFC 1836
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.
Ask Micwyn about this book
Try asking
If you like this one
RFC 1137: Mapping between full RFC 822 and RFC 822 with restricted encodingRFC 1779: A String Representation of Distinguished NamesRFC 1781: Using the OSI Directory to Achieve User Friendly NamingRFC 1801: MHS use of the X.500 Directory to support MHS RoutingRFC 1836: Representing the O/R Address hierarchy in the X.500 Directory Information TreeRFC 1837: Representing Tables and Subtrees in the X.500 DirectoryRFC 1838: Use of the X.500 Directory to support mapping between X.400 and RFC 822 AddressesRFC 2156: MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMERFC 2164: Use of an X.500/LDAP directory to support MIXER address mappingRFC 2293: Representing Tables and Subtrees in the X.500 Directory