As per Relevance of the word identifier, we have this rfc below:
Network Working Group S.
Request for Comments: 1836 ISODE
Category: Experimental August 1995
Representing the O/R Address hierarchy in
X.500 Directory Information
Status of this
This memo defines an Experimental Protocol for the
community. This memo does not specify an Internet standard of
kind. Discussion and suggestions for improvement are requested
Distribution of this memo is unlimited
This document defines a representation of the O/R Address
in the Directory Information Tree [6, 1]. This is useful for a
of purposes, including
o Support for MHS Routing [4].
o Support for X.400/RFC 822 address mappings [2, 5].
Object Class
------------ ---------
mHSCountry
aDMD
pRMD
mHSX121
mHSNumericUserIdentifier
mHSOrganization
mHSOrganizationalUnit
mHSPerson
mHSNamedObject
mHSTerminalID
mHSDomainDefinedAttribute
Table 1: Order of O/R Address Directory
1. The O/R Address
An O/R Address hierarchy is represented in the X.500 directory
associating directory name components with O/R Address components
An example of this is given in Figure 1. The object classes
attributes required to support this representation are defined
Figure 2. The schema, which defines the hierarchy in which
Kille Experimental [Page 1]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
objects are represented in the directory information tree
specified in Table 1. A given object class defined in the table
always be higher in the DIT than an object class defined lower
the table. Valid combinations of O/R Address components are
in X.400.
/\
/ \
C=GB / \ Numeric-C=234
/ \
/ \
/ \
+------------+<----------------+----+
| Country | | |
+------------+ +----+
/\
/ \
/ \
/ \
ADMD=" " / \ ADMD=Gold 400
+-------------+ +------------+
| ADMD | | ADMD |
+-------------+ +------------+
\ \
\ \
\ PRMD=UK.AC \ PRMD=UK.
\ \
+----------+ +----+
| PRMD |< -----------| |
+----------+ +----+
/
/
O=
/
/
+------------+
| MHS-Org |
+------------+
\
\ OU=
\
\
+-----------+
| MHS-OU |
+-----------+
Figure 1: Example O/R Address
Kille Experimental [Page 2]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
ub-domain-name-length, ub-organization-name-length
ub-organizational-unit-name-length, ub-common-name-length
ub-x121-address-length, ub-domain-defined-attribute-type-length
ub-domain-defined-attribute-value-length, ub-terminal-id-length
ub-numeric-user-id-length, ub-country-name-numeric-length
ub-surname-length, ub-given-name-length, ub-initials-length
ub-generation-qualifier-
FROM MTSUpperBounds {joint-iso-ccitt mhs-motis(6) mts(3) 10
modules(0) upper-bounds(3) };
mHSCountry OBJECT-CLASS ::= {
SUBCLASS OF {country
MAY CONTAIN {mHSNumericCountryName
ID oc-mhs-country
mHSNumericCountryName ATTRIBUTE ::= {
WITH SYNTAX NumericString (SIZE (1..ub-country-name-numeric-length))
SINGLE VALUE 20
ID at-mhs-numeric-country-name
aDMD OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {aDMDName
ID oc-admd
aDMDName ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-domain-name-length} 30
ID at-admd-name
pRMD OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {pRMDName
ID oc-prmd
pRMDName ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-domain-name-length} 40
ID at-prmd-name
mHSOrganization OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {mHSOrganizationName }
ID oc-mhs-organization
Kille Experimental [Page 3]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
mHSOrganizationName ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-organization-name-length} 50
ID at-mhs-organization-name
mHSOrganizationalUnit OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {mHSOrganizationalUnitName
ID oc-mhs-organizational-unit
mHSOrganizationalUnitName ATTRIBUTE ::= {
SUBTYPE OF organizationalUnitName 60
WITH SYNTAX DirectoryString {ub-organizational-unit-name-length
ID at-mhs-organizational-unit-name
mHSPerson OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {mHSSurname
MAY CONTAIN {mHSGivenName
mHSInitials
mHSGenerationalQualifier
ID oc-mhs-person} 70
mHSSurname ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-surname-lenght
ID at-mhs-surname
mHSGivenName ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-given-name-length
ID at-mhs-given-name} 80
mHSInitials ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-initials-length
ID at-mhs-initials
mHSGenerationQualifier ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-generation-qualifier-length
ID at-mhs-generation-qualifier} 90
mHSNamedObject OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {mHSCommonName
ID oc-mhs-named-object
Kille Experimental [Page 4]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
mHSCommonName ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-common-name-length
ID at-mhs-common-name} 100
mHSX121 OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {mHSX121Address
ID oc-mhs-x121}
mHSX121Address ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-x121-address-length
ID at-x121-address} 110
mHSDomainDefinedAttribute OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {
mHSDomainDefinedAttributeType
mHSDomainDefinedAttributeValue
ID oc-mhs-domain-defined-attribute
mHSDomainDefinedAttributeType ATTRIBUTE ::= {
SUBTYPE OF name 120
WITH SYNTAX DirectoryString {ub-domain-defined-attribute-type-length
SINGLE
ID at-mhs-domain-defined-attribute-type
mHSDomainDefinedAttributeValue ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-domain-defined-attribute-value-length
SINGLE
ID at-mhs-domain-defined-attribute-value
130
mHSTerminalID OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {mHSTerminalIDName
ID oc-mhs-terminal-id
mHSTerminalIDName ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-terminal-id-length
ID at-mhs-terminal-id-name} 140
mHSNumericUserIdentifier OBJECT-CLASS ::= {
SUBCLASS OF {top
MUST CONTAIN {mHSNumericUserIdentifierName
ID oc-mhs-numeric-user-id
Kille Experimental [Page 5]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
mHSNumericeUserIdentifierName ATTRIBUTE ::= {
SUBTYPE OF
WITH SYNTAX DirectoryString {ub-numeric-user-id-length} 150
ID at-mhs-numeric-user-id-name
Figure 2: O/R_Address
The hierarchy is defined so that
1. The representation is defined so that it is straightforward
make a mechanical transformation in either direction.
requires that each node is named by an attribute whose type
determine the mapping
2. Where there are multiple domain defined attributes, the first
the sequence is the most significant
3. Physical Delivery (postal) addresses are not represented in
hierarchy. This is primarily because physical delivery can
handled by the Access Unit routing mechanisms defined in [4],
there is no need for this representation
4. Terminal and network forms of address are not handled, except
X.121 form, which is useful for addressing faxes
5. MHSCountry is defined as a subclass of Country, and so the
entry will be used for MHS Routing as for the rest of the DIT
6. The numeric country code will be an alias
7. ADMD will always be present in the hierarchy. This is true in
case of " " and of "0". This facilitates an easy
transformation between the two forms of address
8. Each node is named by the relevant part of the O/R Address
9. Aliases may be used in other parts of the tree, in order
normalise alternate values. Where an alias is used, the value
the alias should be present as an alternate value in the
aliased to. Aliases may not be used for domain
attributes
10. Domain Defined Attributes are named by a multi-valued
(Relative Distinguished Name), consisting of the type and value
This is done so that standard attribute syntaxes can be used
Kille Experimental [Page 6]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
11. Where an O/R Address has a valid Printable String and T.61 form
both must be present, with one as an alias for the other. This
so that direct lookup of the name will work, independent of
variant used. When both are present in an O/R Address
looked up, either may be used to construct the distinguished name
12. Personal name is handled by use of the mHSPerson object class
Each of the components of the personal name will be present in
relative distinguished name, which will usually be multi-valued
The relationship between X.400 O/R Addresses and the X.400
(Attribute Type and Object Class) are given in Table 2. Where
are multiple Organizational Units or Domain Defined Attributes,
component is mapped onto a single X.500 entry
Note: When an X.121 address is used for addressing fax transmission
this may only be done relative to the PRMD or ADMD. This is
line with the current X.400 standards position. This means
it is not possible to use this form of addressing for
organisational or departmental fax gateway service
O/R Address Object Class Naming
----------- ------------ ----------------
C mHSCountry
A aDMD
P pRMD
O mHSOrganization
OU/OU1/OU2 mHSOrganizationalUnit
OU3/OU
PN mHSPerson
CN mHSNamedObject
X121 mHSX121 mHSX121
T-ID mHSTerminalID
UA-ID mHSNumericUserIdentifier
DDA mHSDomainDefinedAttribute
Table 2: O/R Address relationship to Directory
Kille Experimental [Page 7]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
2.
O/R Addresses are written in the standard X.400 Notation
Distinguished Names use the string representation of
names defined in [3]. The keywords used for the attributes
in this specification are given in Table 3.
3. Example
The O/R Address
I=S; S=Kille; OU1=CS; O=UCL
P=UK.AC; A=Gold 400; C=GB
would be represented in the directory as
MHS-I=S + MHS-S=Kille, MHS-OU=CS, MHS-O=UCL
Attribute
--------- -------
mHSNumericCountryName MHS-Numeric-
aDMDName
pRMDName
mHSOrganizationName MHS-
mHSOrganizationalUnitName MHS-
mHSSurname MHS-
mHSGivenName MHS-
mHSInitials MHS-
mHSGenerationalQualifier MHS-
mHSCommonName MHS-
mHSX121Address MHS-X121
mHSDomainDefinedAttributeType MHS-DDA-
mHSDomainDefinedAttributeValue MHS-DDA-
mHSTerminalIDName MHS-T-
mHSNumericeUserIdentifierName MHS-UA-
Table 3: Keywords for String DN
PRMD=UK.AC, ADMD=Gold 400, C=
Kille Experimental [Page 8]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
4. Mapping from O/R Address to Directory
The primary application of this mapping is to take an X.400
O/R Address and to generate an equivalent directory name.
mapping is only used for selected types of O/R Address
o Mnemonic
o Numeric
o Terminal form, where country is present and X121 addressing
Other forms of O/R address are handled by Access Unit mechanisms
The O/R Address is treated as an ordered list, with the order
defined in Table 1. For each O/R Address attribute, generate
equivalent directory naming attribute. In most cases, the mapping
mechanical. Printable String or Teletex encodings are chosen
appropriate. Where both forms are present in the O/R Address,
form may be used to generate the distinguished name. Both will
represented in the DIT. There are two special cases
1. A DDA generates a multi-valued
2. The Personal Name is mapped to a multi-valued
In many cases, an O/R Address will be provided, and only the
components of the address will be represented in the DIT. In
case, the "longest possible match" should be returned
5. Mapping from Directory Name to O/R
The reverse mapping is also needed in some cases. All of the
attributes are unique, so the mapping is mechanically reversible
6.
Acknowledgements for work on this document are given in [4].
Kille Experimental [Page 9]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
[1] The Directory --- overview of concepts, models and services
1993. CCITT X.500 Series Recommendations
[2] Kille, S., "Mapping between X.400(1988)/ISO 10021 and RFC 822",
RFC 1327, Department of Computer Science, University
London, May 1992.
[3] Kille, S., "A String Representation of Distinguished Names",
RFC 1779, Department of Computer Science, University
London, March 1995.
[4] Kille, S., "MHS Use of the X.500 Directory to Support
Routing, RFC 1801, ISODE Consortium, June 1995.
[5] Kille, S., "Use of the X.500 Directory to Support Mapping
X.400 and RFC 822 Addresses, RFC 1838, ISODE Consortium
August 1995.
[6] CCITT recommendations X.400 / ISO 10021, April 1988.
SG 5/VII / ISO/IEC JTC1, Message Handling: System and
Overview
7. Security
Security issues are not discussed in this memo
8. Author's
Steve
ISODE
The
The
TW9 1
Phone: +44-81-332-9091
Internet EMail: S.Kille@ISODE.
X.400: I=S; S=Kille; O=ISODE Consortium; P=ISODE
A=Mailnet; C=FI
DN: CN=Steve Kille
O=ISODE Consortium, C=
UFN: S. Kille, ISODE Consortium,
Kille Experimental [Page 10]
RFC 1836 O/R Addresses in the X.500 DIT August 1995
A. Object Identifier
-----------------------------------------------------------------------
mhs-ds OBJECT IDENTIFIER ::= {iso(1) org(3) dod(6) internet(1)
private(4) enterprises(1) isode-consortium (453) mhs-ds (7)}
tree OBJECT IDENTIFIER ::= {mhs-ds 2}
oc OBJECT IDENTIFIER ::= {tree 1}
at OBJECT IDENTIFIER ::= {tree 2}
oc-admd OBJECT IDENTIFIER ::= {oc 1} 10
oc-mhs-country OBJECT IDENTIFIER ::= {oc 2}
oc-mhs-domain-defined-attribute OBJECT IDENTIFIER ::= {oc 3}
oc-mhs-named-object OBJECT IDENTIFIER ::= {oc 4}
oc-mhs-organization OBJECT IDENTIFIER ::= {oc 5}
oc-mhs-organizational-unit OBJECT IDENTIFIER ::= {oc 6}
oc-mhs-person OBJECT IDENTIFIER ::= {oc 7}
oc-mhs-x121 OBJECT IDENTIFIER ::= {oc 8}
oc-prmd OBJECT IDENTIFIER ::= {oc 9}
oc-mhs-terminal-id OBJECT IDENTIFIER ::= {oc 10}
oc-mhs-numeric-user-id OBJECT IDENTIFIER ::= {oc 11} 20
at-admd-name OBJECT IDENTIFIER ::= {at 1}
at-mhs-common-name OBJECT IDENTIFIER ::= {at 2}
at-mhs-domain-defined-attribute-type OBJECT IDENTIFIER ::= {at 3}
at-mhs-domain-defined-attribute-value OBJECT IDENTIFIER ::= {at 4}
at-mhs-numeric-country-name OBJECT IDENTIFIER ::= {at 5}
at-mhs-organization-name OBJECT IDENTIFIER ::= {at 6}
at-mhs-organizational-unit-name OBJECT IDENTIFIER ::= {at 7}
at-prmd-name OBJECT IDENTIFIER ::= {at 10}
at-x121-address OBJECT IDENTIFIER ::= {at 12} 30
at-mhs-terminal-id-name OBJECT IDENTIFIER ::= {at 13}
at-mhs-numeric-user-id-name OBJECT IDENTIFIER ::= {at 14}
at-mhs-surname OBJECT IDENTIFIER ::= {at 15}
at-mhs-given-name OBJECT IDENTIFIER ::= {at 16}
at-mhs-initials OBJECT IDENTIFIER ::= {at 17}
at-mhs-generation-qualifier OBJECT IDENTIFIER ::= {at 18}
Figure 3: Object Identifier
Kille Experimental [Page 11]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
