Representing the O/R Address hierarchy in the X.500 Directory Information Tree (RFC1836)
Original Publication Date: 1995-Aug-01
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
This document defines a representation of the O/R Address hierarchy in the Directory Information Tree [6, 1]. This is useful for a range of purposes, including:
Network Working Group S. Kille
Request for Comments: 1836 ISODE Consortium
Category: Experimental August 1995
Representing the O/R Address hierarchy in the
X.500 Directory Information Tree
Status of this Memo
This memo defines an Experimental Protocol for the Internet
community. This memo does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This document defines a representation of the O/R Address hierarchy
in the Directory Information Tree [6, 1]. This is useful for a range
of purposes, including:
o Support for MHS Routing .
o Support for X.400/RFC 822 address mappings [2, 5].
Object Class Mandatory
Table 1: Order of O/R Address Directory Components
1. The O/R Address Hierarchy
An O/R Address hierarchy is represented in the X.500 directory by
associating directory name components with O/R Address components.
An example of this is given in Figure 1. The object classes and
attributes required to support this representation are defined in
Figure 2. The schema, which defines the hierarchy in which these
objects are represented in the directory information tree is
specified in Table 1. A given object class defined in the table will
always be higher in the DIT than an object class defined lower down
the table. Valid combinations of O/R Address components are defined
C=GB / \ Numeric-C=234
| Country | | |