RFC 1617: Naming and Structuring Guidelines for X.500 Directory Pilots
In plain English — editorial summary, not part of the RFC
This document defines a number of naming and structuring guidelines focused on White Pages usage. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1617
- Published
- May 1994
- Authors
- P. Barker; S. Kille; T. Lenggenhager
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 28
- Also known as
- —
- Obsoletes:
- RFC 1384
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1616X.400(1988) for the Academic and Research Community in EuropeCurrent
May 1994
- RFC 1615Migrating from X.400(84) to X.400(88)Current
May 1994
- RFC 1614Network Access to Multimedia InformationCurrent
May 1994
- RFC 1357A Format for E-mailing Bibliographic RecordsObsoleted
July 1992
- RFC 2968Mesh of Multiple DAG servers - Results from TISDAGCurrent
October 2000
- RFC 2969Wide Area Directory Deployment - Experiences from TISDAGCurrent
October 2000
- RFC 3130Notes from the State-Of-The-Technology: DNSSECCurrent
June 2001
- RFC 2970Architecture for Integrated Directory Services - Result from TISDAGCurrent
October 2000
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?