I-D ACTION:draft-ietf-lsd-client-finding-00.txt

Internet-Drafts@ns.ietf.org Tue, 27 January 1998 15:37 UTC

Delivery-Date: Tue, 27 Jan 1998 10:40:45 -0500
Return-Path: adm
Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id KAA07021 for ietf-123-outbound.10@ietf.org; Tue, 27 Jan 1998 10:37:03 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost []) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id JAA05422; Tue, 27 Jan 1998 09:51:24 -0500 (EST)
Message-Id: <199801271451.JAA05422@ns.ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce
Cc: ietf-lsd@listserv.umu.se
From: Internet-Drafts@ns.ietf.org
Reply-to: Internet-Drafts@ns.ietf.org
Subject: I-D ACTION:draft-ietf-lsd-client-finding-00.txt
Date: Tue, 27 Jan 1998 09:51:20 -0500
Sender: cclark@cnri.reston.va.us

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the LDAP Service Deployment Working Group of the IETF.

	Title		: LDAP Clients Finding LDAP Servers
	Author(s)	: R. Moats
	Filename	: draft-ietf-lsd-client-finding-00.txt
	Pages		: 3
	Date		: 17-Nov-97
   This document discusses methods available for LDAP clients to
   discover the existance and location of LDAP servers. It is based on
   previous and ongoing IETF work.

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-lsd-client-finding-00.txt".
A URL for the Internet-Draft is:

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	Europe: ftp.nordu.net
	Pacific Rim: munnari.oz.au
	US East Coast: ds.internic.net
	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-lsd-client-finding-00.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