I-D ACTION:draft-ietf-asid-ldap-domains-01.txt
Internet-Drafts@ietf.org Tue, 11 February 1997 15:18 UTC
Received: from ietf.org by ietf.org id aa06068; 11 Feb 97 10:18 EST
Received: from ietf.ietf.org by ietf.org id aa03091; 11 Feb 97 9:36 EST
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
cc: ietf-asid@umich.edu
Sender: ietf-announce-request@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-asid-ldap-domains-01.txt
Date: Tue, 11 Feb 1997 09:36:45 -0500
X-Orig-Sender: cclark@ietf.org
Message-ID: <9702110936.aa03091@ietf.org>
A Revised Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Access, Searching and Indexing of Directories Working Group of the IETF. Title : An Approach for Using Domains in LDAP Distinguished Names Author(s) : S. Kille, M. Wahl Filename : draft-ietf-asid-ldap-domains-01.txt Pages : 4 Date : 02/10/1997 The Lightweight Directory Access Protocol (LDAP) uses X.500-compatible distinguished names for providing unique identification of entries. distinguished names in currently-deployed X.500 directories have the properties that they are descriptive, hierarchical, and follow common organizational models. However, there is not today a registration mechanism to permit individuals and organizations to obtain distinguished names, regardless of their physical location. This document defines a mechanism by which a name registered with the Internet Domain Name Service [1], for which there are active registration services, can be represented as a distinguished name so that it may be used with the LDAP protocol. This is not intended to have LDAP replace the DNS protocol, but to permit further deployment of LDAP into organizations connected to the Internet. This algorithm automatically assigns a distinguished name to any enterprise which has obtained a domain name for use in the Internet. This distinguished name may be used as a prefix for their names of entries in that enterprise. This document does not define how to represent objects which do not have domain names. Several RFCs, such as [3] and [4], and more recent documents provide additional guidance on representing and structuring information in these entries. Nor does this document define the procedure to locate an enterprises' LDAP directory server, given their domain name. Such as procedure may be defined in future RFCs. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-asid-ldap-domains-01.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-asid-ldap-domains-01.txt Internet-Drafts directories are located at: o Africa: ftp.is.co.za o Europe: ftp.nordu.net ftp.nis.garr.it o Pacific Rim: munnari.oz.au o US East Coast: ds.internic.net o US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-asid-ldap-domains-01.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e., documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
- I-D ACTION:draft-ietf-asid-ldap-domains-01.txt Internet-Drafts