RFC 1804: Schema Publishing in X.500 Directory
In plain English — editorial summary, not part of the RFC
In this document we propose a solution using the existing mechanisms of the directory [1] itself. We present a naming scheme for naming schema objects and a meta-schema for storing schema objects in the directory. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1804
- Published
- June 1995
- Authors
- G. Mansfield; P. Rajeev; S. Raghavan; T. Howes
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 10
- Also known as
- —
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 1802Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 RoutingCurrent
June 1995
- RFC 1801MHS use of the X.500 Directory to support MHS RoutingCurrent
June 1995
- RFC 1798Connection-less Lightweight X.500 Directory Access ProtocolObsoleted
June 1995
- RFC 1794DNS Support for Load BalancingCurrent
April 1995
- RFC 1785TFTP Option Negotiation AnalysisCurrent
March 1995
- RFC 1784TFTP Timeout Interval and Transfer Size OptionsObsoleted
March 1995
- RFC 1783TFTP Blocksize OptionObsoleted
March 1995
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?