X.500
Click on the red underlined text to get to the source
...
In the late 1980s, X.500 Directory Services were standardized by the
CCITT (Commite' Consultatif International de Telegraphique et
Telephonique), now a part of the ITU ...
... RFC1274].
In the years that followed, X.500 Directory Services have evolved to
incorporate new capabilities and even new protocols. In particular,
...
... the schema elements lack standardized schema descriptions for use in
modern X.500 and LDAP directory services despite the fact that these
...
... documentTitle: COSINE LDAP/X.500 Schema
documentAuthor: cn=Kurt D. Zeilenga,cn=Persons,dc=Example,dc=COM
documentLocation: http://www.rfc-editor.org/rfc/rfc4524.txt
...
... represent DNS domains that are "equivalent" to an X.500 domain, e.g.,
an organization or organizational unit.
...
... Kille, S., Wahl, M., Grimstad, A., Huber, R., and S. Sataluri, "Using Domains in LDAP/X.500 Distinguished Names", RFC 2247prop, January 1998. ...
... Barker, P. and S. Kille, "The COSINE and Internet X.500 Schema", RFC 1274prop(-> 4524prop), November 1991. ...
... Yeong, W., Howes, T., and S. Kille, "X.500 Lightweight Directory Access Protocol", RFC 1487(-> 3494 | 1777hist(-> 3494)), July 1993. ...
... implementations may (for legacy reasons [RFC3494]) recognize the
attribute type by its X.500 name. Hence, the X.500 names have been
reserved solely for this purpose.
...
... RFC3494]) recognize the
attribute type by its X.500 name. Hence, the X.500 names have been
reserved solely for this purpose.
...
... object class was not brought forward as its
function is largely replaced by operational attributes introduced in
X.500(93) [X.501] and version 3 of LDAP ...