RFC 1274: The COSINE and Internet X.500 Schema
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4524.
Current version: RFC 4524 — COSINE LDAP/X.500 Schema
In plain English — editorial summary, not part of the RFC
This document suggests an X.500 Directory Schema, or Naming Architecture, for use in the COSINE and Internet X.500 pilots. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1274
- Published
- November 1991
- Authors
- P. Barker; S. Kille
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 60
- Also known as
- —
- Obsoleted by:
- RFC 4524
Topics
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 1279X.500 and DomainsCurrent
November 1991
- RFC 9464Internet Key Exchange Protocol Version 2 (IKEv2) Configuration for Encrypted DNSCurrent
November 2023
- RFC 1275Replication Requirements to provide an Internet Directory using X.500Current
November 1991
- RFC 1276Replication and Distributed Operations extensions to provide an Internet Directory using X.500Current
November 1991
- RFC 1277Encoding Network Addresses to Support Operation over Non-OSI Lower LayersCurrent
November 1991
- RFC 1278A string encoding of Presentation AddressCurrent
November 1991
- RFC 1255A Naming Scheme for c=USObsoleted
September 1991
- RFC 1314A File Format for the Exchange of Images in the InternetCurrent
April 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?