Representing the O/R Address hierarchy in the X.500 Directory Information Tree (RFC2294)

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Kille: AUTHOR

Abstract

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: 2294 Isode Ltd.

Obsoletes: 1836 March 1998

Category: Standards Track

Representing the O/R Address hierarchy in the

X.500 Directory Information Tree

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

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 [4].

o Support for X.400/RFC 822 address mappings [2, 5].

Please send comments to the author or to the discussion group

ds@mercury.udev.cdc.com>.

Object Class Mandatory

------------ ---------

mHSCountry M

aDMD M

pRMD O

mHSX121 O

mHSNumericUserIdentifier O

mHSOrganization O

mHSOrganizationalUnit O

mHSPerson O

mHSNamedObject O

mHSTerminalID O

mHSDomainDefinedAttribute O

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

in X.400.

/\

/ \

C=GB / \ Numeric-C=234...