RFC 2116: X.500 Implementations Catalog-96
In plain English — editorial summary, not part of the RFC
This document is a revision to [RFC 1632]: A Revised Catalog of Available X.500 Implementations and is based on the results of data collection via a WWW home page that enabled implementors to submit new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. [RFC 1632] is a revision of [RFC 1292]. This document contains detailed description of 31 X.500 implementations - DSAs, DUAs, and DUA interfaces. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2116
- Published
- April 1997
- Authors
- C. Apple; K. Rossen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 164
- Also known as
- FYI11
- Obsoletes:
- RFC 1632
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1292 (1992)
- RFC 1632 (1994)
- RFC 2116 (1997)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1803Recommendations for an X.500 Production Directory ServiceCurrent
June 1995
- RFC 1564DSA Metrics (OSI-DS 34 (v3))Current
January 1994
- RFC 2079Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)Current
January 1997
- RFC 2164Use of an X.500/LDAP directory to support MIXER address mappingCurrent
January 1998
- RFC 2255The LDAP URL FormatObsoleted
December 1997
- RFC 2256A Summary of the X.500(96) User Schema for use with LDAPv3Obsoleted
December 1997
- RFC 2258Internet Nomenclator ProjectCurrent
January 1998
- RFC 1960A String Representation of LDAP Search FiltersObsoleted
June 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?