RFC 1276: Replication and Distributed Operations extensions to provide an Internet Directory using X.500
In plain English — editorial summary, not part of the RFC
Some requirements on extensions to X.500 are described in the RFC[HK91b], in order to build an Internet Directory using X.500(1988). This document specifies a set of solutions to the problems raised. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1276
- Published
- November 1991
- Authors
- S.E. Hardcastle-Kille
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 17
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1277Encoding Network Addresses to Support Operation over Non-OSI Lower LayersCurrent
November 1991
- RFC 1275Replication Requirements to provide an Internet Directory using X.500Current
November 1991
- RFC 1278A string encoding of Presentation AddressCurrent
November 1991
- RFC 1274The COSINE and Internet X.500 SchemaObsoleted
November 1991
- RFC 1279X.500 and DomainsCurrent
November 1991
- RFC 1314A File Format for the Exchange of Images in the InternetCurrent
April 1992
- RFC 1341MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message BodiesObsoleted
June 1992
- RFC 1342Representation of Non-ASCII Text in Internet Message HeadersObsoleted
June 1992
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?