idnits 2.17.1 draft-ietf-lsd-client-finding-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 3 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 1998) is 9598 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '4' Summary: 8 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft Ryan Moats 3 draft-ietf-lsd-client-finding-00.txt AT&T 4 Expires in six months January 1998 6 LDAP Clients Finding LDAP Servers 7 Filename: draft-ietf-lsd-client-finding-00.txt 9 Status of This Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its 13 areas, and its working groups. Note that other groups may also 14 distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- 19 Drafts as reference material or to cite them other than as ``work 20 in progress.'' 22 To learn the current status of any Internet-Draft, please check 23 the ``1id-abstracts.txt'' listing contained in the Internet- 24 Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net 25 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 26 Coast), or ftp.isi.edu (US West Coast). 28 Abstract 30 This document discusses methods available for LDAP clients to 31 discover the existance and location of LDAP servers. It is based on 32 previous and ongoing IETF work. 34 1. Introduction 36 The Lightweight Directory Access Protocol (LDAP) [1] can be used to 37 build "islands" of servers that are not a priori tied into a single 38 Directory Information Tree (DIT.) Here, it is necessary to determine 39 how a client can discover LDAP servers. This documents discusses the 40 available methods 42 2. Client Discovery of LDAP Servers 44 LDAP clients may have a list of preconfigured LDAP servers included 45 with them that a user can select from. Here, some of the servers in 46 the preconfigured list might provide the functionality described in 47 this document, to allow for simpler clients. 49 If not configured with a LDAP server, a non-DHCP client should follow 50 the sequence of steps specified in [1] (which uses DNS [2] and the 51 Service Location Protocol [3]) with the target service being LDAP in 52 order to find an LDAP server. If a DNS record is found for a name 53 that begins with ldap (i.e. ldap.tcp.foo.com or ldap.foo.com) a 54 further DNS lookup for a TXT record under that name would return the 55 root of that server's subtree. A DHCP-aware client may use the DHCP 56 extension specified in [4] to locate LDAP servers as an alternative 57 to the sequence specified in [1]. 59 3. Security Considerations 61 Since this draft only summarizes available methods, it adds no 62 additional security considerations to those inherent in the 63 referenced documents. Implementors are strongly recommended to read 64 and follow the security considerations provided in the referenced 65 documents. 67 4. Acknowledgments 69 Many thanks to the members of the LSD working group, for their 70 contributions to previous drafts. The work described in this document 71 is partially supported by the National Science Foundation, 72 Cooperative Agreement NCR-9218179. 74 5. References 76 Request For Comments (RFC) and Internet Drafts documents are 77 available from and numerous mirror 78 sites. 80 [1] R. Moats, M. Hamilton, P. Leach, "Finding Stuff (How to dis- 81 cover services)," Internet Draft (work in progress), June 82 1997. 84 [2] P. V. Mockapetris. "Domain names - concepts and facilities," 85 RFC 1034. November 1987. 87 [3] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, "Service 88 Location Protocol," RFC 2165, June 1997. 90 [4] L. Hedstrom, L. Howard, "DHCP Options for Locating LDAP 91 Servers," Internet Draft (work in progress), July 1997 93 6. Author's address 95 Ryan Moats 96 AT&T 97 15621 Drexel Circle 98 Omaha, NE 68135-2358 99 USA 101 Phone: +1 402 894-9456 102 EMail: jayhawk@att.com