metasystema.org
UpdatedINFORMATIONALIETF stream

RFC 2377: Naming Plan for Internet Directory-Enabled Applications

Still current, but amended. Parts of this document are changed or extended by RFC 4519. Read both.

In plain English — editorial summary, not part of the RFC

Application of the conventional X.500 approach to naming has heretofore, in the experience of the authors, proven to be an obstacle to the wide deployment of directory-enabled applications on the Internet. We propose a new directory naming plan that leverages the strengths of the most popular and successful Internet naming schemes for naming objects in a hierarchical directory. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

Document record

Document ID
RFC2377
Published
September 1998
Authors
A. Grimstad; R. Huber; S. Sataluri; M. Wahl
Status
INFORMATIONAL
Stream
IETF
Area
app
Pages
18
Also known as
—
Updated by:
RFC 4519

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.

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?

canonical URL: /rfc/2377-naming-plan-for-internet-directory-enabled-applications