idnits 2.17.1 draft-ietf-asid-ldapv3-url-00.txt: ** The Abstract section seems to be numbered 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-25) 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 4 longer pages, the longest (page 2) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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.) ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. == The 'Obsoletes: ' line in the draft header should list only the _numbers_ of the RFCs which will be obsoleted by this document (if approved); it should not include the word 'RFC' in the list. -- The draft header indicates that this document obsoletes RFC1959, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 12 has weird spacing: '...fts are worki...' == Line 13 has weird spacing: '...ments of the ...' == Line 14 has weird spacing: '...t other group...' == Line 18 has weird spacing: '...and may be ...' == Line 22 has weird spacing: '...atus of any ...' == (28 more instances...) -- 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 (March 1997) is 9903 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) -- Missing reference section? '2' on line 163 looks like a reference -- Missing reference section? '3' on line 166 looks like a reference -- Missing reference section? '1' on line 159 looks like a reference -- Missing reference section? '4' on line 170 looks like a reference -- Missing reference section? '6' on line 176 looks like a reference -- Missing reference section? '5' on line 173 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 9 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Tim Howes 3 INTERNET DRAFT Mark Smith 4 OBSOLETES: RFC 1959 Netscape Communications Corp. 5 March 1997 7 The LDAP URL Format 8 10 1. Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working docu- 13 ments of the Internet Engineering Task Force (IETF), its areas, and its 14 working groups. Note that other groups may also distribute working 15 documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet- Drafts as reference material 20 or to cite them other than as ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check the 23 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 24 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 25 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 27 2. Abstract 29 LDAP is the Lightweight Directory Access Protocol, defined in [2] and 30 [3]. This document describes a format for an LDAP Uniform Resource 31 Locator. The format describes an LDAP search operation to perform to 32 retrieve information from an LDAP directory. This document replaces RFC 33 1959. It updates the LDAP URL format for version 3 of LDAP and defines a 34 way to indicate whether the URL references a master or slave server. 35 This document also defines a second URL scheme prefix for LDAP running 36 over the secure sockets layer protocol. 38 3. URL Definition 40 An LDAP URL begins with the protocol prefix "ldap" (or the prefix 41 "ldaps" for LDAP over SSL) and is defined by the following grammar. 43 ::= "://" [ ] "/" 44 [ [ "?" [ ] [ "?" [ ] 45 [ "?" [ ] [ "?" ] ] ] ] ] 47 ::= "ldap" | "ldaps" 49 ::= [ ":" ] 51 ::= a distinguished name string as defined in [1] 53 ::= NULL 54 | 55 | [ "," ] 57 ::= an AttributeDescription string as defined in [3] 59 ::= "base" | "one" | "sub" 61 ::= a filter string as defined in [4] 63 ::= "master" | "slave" 65 The "ldap" and "ldaps" prefixes indicate an entry or entries residing in 66 the LDAP server running on the given at the given . For regular LDAP servers, the default port is TCP port 389. 68 For LDAP servers running over secure sockets layer transport [6], the 69 default port is 636. 71 The is an LDAP Distinguished Name using the string format described 72 in [1]. It identifies the base object of the LDAP search. 74 The construct is used to indicate which attributes should 75 be returned from the entry or entries. Individual names 76 are as defined for AttributeType in RFC 1777. If the part 77 is omitted, all attributes of the entry or entries should be returned. 79 The construct is used to specify the scope of the search to per- 80 form in the given LDAP server. The allowable scopes are "base" for a 81 base object search, "one" for a one-level search, or "sub" for a subtree 82 search. If is omitted, a scope of "base" is assumed. 84 The is used to specify the search filter to apply to entries 85 within the specified scope during the search. It has the format 86 specified in [4]. If is omitted, a filter of "(objectClass=*)" 87 is assumed. 89 The construct is optionally used to indicate whether the 90 LDAP URL refers to a master LDAP server (i.e., one able to update the 91 data referenced) or a slave LDAP server (i.e., one unable to update the 92 data referenced). 94 Note that if the entry or entries reside in the X.500 namespace, they 95 should be reachable from any LDAP server that is providing front-end 96 access to the X.500 directory. If the part of the URL is 97 missing, the URL can be resolved by contacting any X.500-back-ended LDAP 98 server. 100 Note that any any URL-illegal characters (e.g., spaces) occurring inside 101 a , , or other element of an LDAP URL must be escaped using 102 the % method described in RFC 1738. 104 4. Examples 106 The following are some example LDAP URLs using the format defined above. 107 An LDAP URL referring to the University of Michigan entry, available 108 from any X.500-capable LDAP server: 110 ldap:///o=University%20of%20Michigan,c=US 112 An LDAP URL referring to the University of Michigan entry in a particu- 113 lar ldap server: 115 ldap://ldap.itd.umich.edu/o=University%20of%20Michigan,c=US 117 This URL corresponds to a base object search of the "o=University of 118 Michigan, c=US" entry using a filter of (objectclass=*), requesting all 119 attributes. 121 An LDAP URL referring to only the postalAddress attribute of the Univer- 122 sity of Michigan entry: 124 ldap://ldap.itd.umich.edu/o=University%20of%20Michigan,c=US?postalAddress 126 The corresponding LDAP search operation is the same as in the previous 127 example, except that only the postalAddress attribute is requested. 129 An LDAP URL referring to the set of entries found by querying any 130 X.500-capable LDAP server and doing a subtree search of the University 131 of Michigan for any entry with a common name of "Babs Jensen", retriev- 132 ing all attributes: 134 ldap:///o=University%20of%20Michigan,c=US??sub?(cn=Babs%20Jensen) 136 A secure LDAP URL referring to the master server containing all children 137 of the c=GB entry: 139 ldaps://ldap.itd.umich.edu/c=GB?objectClass?one??master 141 The objectClass attribute is requested to be returned along with the 142 entries, and the default filter of "(objectclass=*)" is used. 144 5. Security Considerations 146 The LDAP URL format does not provide a way to specify credentials to use 147 when resolving the URL. Therefore, it is expected that such requests 148 will be unauthenticated, unless some out-of-band mechanism is used. 150 The LDAP URL format allows the specification of an arbitrary LDAP search 151 operation to be performed when evaluating the LDAP URL. Following an 152 LDAP URL may cause unexpected results, for example, the retrieval of 153 large amounts of data, the initiation of a long-lived search, etc. The 154 security implications of resolving an LDAP URL are the same as those of 155 resolving an LDAP search query. 157 6. Bibliography 159 [1] Lightweight Directory Access Protocol (v3): UTF-8 String Represen- 160 tation of Distinguished Names. M. Wahl, S. Kille, draft-ietf- 161 asid-ldapv3-dn-02.txt, March 1997. 163 [2] Lightweight Directory Access Protocol (v3). M. Wahl, T. Howes, S. 164 Kille, draft-ietf-asid-ldapv3-protocol-04.txt, March 1997. 166 [3] Lightweight Directory Access Protocol (v3): Attribute Syntax Defin- 167 itions. M. Wahl, A. Coulbeck, T. Howes, S. Kille, draft-ietf- 168 asid-ldapv3-attributes-04.txt, March 1997. 170 [4] A String Representation of LDAP Search Filters. T. Howes, draft- 171 ietf-asid-ldapv3-filter.00.txt, March 1997. 173 [5] Uniform Resource Locators (URL). T. Berners-Lee, L. Masinter, M. 174 McCahill, Request for Comment (RFC) 1738, December 1994. 176 [6] The SSL Protocol Version 3.0. A. Freier, P. Karlton, P. Kocher, 177 draft-ietf-tls-ssl-version3-00.txt, November 1996. 179 7. Author's Address 181 Tim Howes 182 University of Michigan 183 ITD Research Systems 184 535 W William St. 185 Ann Arbor, MI 48103-4943 186 USA 187 +1 313 747-4454 188 tim@umich.edu 190 Mark Smith 191 University of Michigan 192 ITD Research Systems 193 535 W William St. 194 Ann Arbor, MI 48103-4943 195 USA 196 +1 313 764-2277 197 mcs@umich.edu