Practical guidance for naming and interconnectivity
draft-ietf-lsd-nandi-00
| Document | Type |
Expired Internet-Draft
(candidate for lsd-old WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Chris Weider , Mark Wahl , Anne Brown | ||
| Last updated | 1998-04-10 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
There are existing communities of LDAP, X.500 and Whois++ servers on the Internet. An LDAPv3 server can be a part of one of more of these communities. LDAP directory services would benefit from reduced naming conflicts and increased ability to locate servers and information both within LDAP islands and between LDAP and other communities. This document recommends guidelines for naming and interconnection of LDAP servers to enable the existence of communities of a loosely coupled LDAP-based directory service that can leverage the X.500 knowledge model and the existing infrastructure of names from the Domain Name System (DNS). This will facilitate the establishment of a global naming plan and the interconnection of a global directory.
Authors
Chris Weider
Mark Wahl
Anne Brown
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)