RFC 1943: Building an X.500 Directory Service in the US
In plain English — editorial summary, not part of the RFC
This document provides definition and recommends considerations that must be undertaken to operate a X.500 Directory Service in the United States. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1943
- Published
- May 1996
- Authors
- B. Jennings
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 22
- Also known as
- —
Topics
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 1632A Revised Catalog of Available X.500 ImplementationsObsoleted
May 1994
- RFC 2377Naming Plan for Internet Directory-Enabled ApplicationsUpdated
September 1998
- RFC 1714Referral Whois Protocol (RWhois)Obsoleted
November 1994
- RFC 1942HTML TablesObsoleted
May 1996
- RFC 1945Hypertext Transfer Protocol -- HTTP/1.0Current
May 1996
- 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?