RFC 1292: A 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 1632.
Current document in this lineage: RFC 2116 — X.500 Implementations Catalog-96
In plain English — editorial summary, not part of the RFC
The goal of this document is to provide information regarding the availability and capability of implementations of X.500. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1292
- Published
- January 1992
- Authors
- R. Lang; R. Wright
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- usv
- Pages
- 103
- Also known as
- —
- Obsoleted by:
- RFC 1632
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 1302Building a Network Information Services InfrastructureCurrent
February 1992
- RFC 1308Executive Introduction to Directory Services Using the X.500 ProtocolCurrent
March 1992
- RFC 1309Technical Overview of Directory Services Using the X.500 ProtocolCurrent
March 1992
- RFC 1355Privacy and Accuracy Issues in Network Information Center DatabasesCurrent
August 1992
- RFC 1392Internet Users' GlossaryObsoleted
January 1993
- RFC 1175FYI on where to start: A bibliography of internetworking informationCurrent
August 1990
- RFC 1147FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected DevicesObsoleted
April 1990
- RFC 1463FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking ReadingsCurrent
May 1993
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?