RFC 1632: A Revised Catalog of Available X.500 Implementations
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2116.
Current document in this lineage: RFC 2116 — X.500 Implementations Catalog-96
In plain English — editorial summary, not part of the RFC
This document is the result of a survey that gathered new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. This document is a revision of RFC 1292. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1632
- Published
- May 1994
- Authors
- A. Getchell; S. Sataluri
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 94
- Also known as
- —
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) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
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 1714Referral Whois Protocol (RWhois)Obsoleted
November 1994
- RFC 1943Building an X.500 Directory Service in the USCurrent
May 1996
- RFC 2377Naming Plan for Internet Directory-Enabled ApplicationsUpdated
September 1998
- RFC 1564DSA Metrics (OSI-DS 34 (v3))Current
January 1994
- RFC 1491A Survey of Advanced Usages of X.500Current
July 1993
- RFC 1959An LDAP URL FormatObsoleted
June 1996
- 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?