Naming and Structuring Guidelines for X.500 Directory Pilots

Abstract

Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Domain Administrative Data in Lightweight Directory Access Protocol (LDAP)

“…The root of a name server DIT is an entry of objectclass organization as specified by RFC 1617 [2]. It has no significance other than to serve as the root of the DIT.…”

Deployment of the Internet White Pages Service

“…The currently preferable way for publishing the information is by using X.500 as its data structure and naming scheme (defined in [4] and discussed in [3], but some countries use a refinement nationally, like [15] for the US). The organization MAY additionally publish it using additional data structures such as whois++.…”

“…The individual's name -The individual's e-mail address, in RFC-822 format; if not present, some other contact information is to be included -Some indication of the individual's relationship with the maintainer When X.500 is used as directory services protocol the last requirement may be fulfilled by using the "organizationalStatus" attribute (see [3]) or by adding a special organizational unit to the local X.500 name space that reflects the relation (like ou=students or ou=employees).…”

“…It should follow the Internet recommendations for structuring the information. Besides the criteria in the previous section, [3] and [4] should be followed if X.500 is used as directory services protocol.…”

“…For recommendations on which attributes to use in X.500 and how to use them (either for public IWPS information or additional local information the reader is referred to [3] and [4]. For specific nonpublic local purposes also new attributes (and object classes) may be defined.…”