idnits 2.17.1 draft-zeilenga-ldapnsref-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): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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? 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 177 has weird spacing: '...for the purpo...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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 (17 November 2000) is 8559 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'RFC 2251' is mentioned on line 47, but not defined ** Obsolete undefined reference: RFC 2251 (Obsoleted by RFC 4510, RFC 4511, RFC 4512, RFC 4513) == Unused Reference: 'RFC2119' is defined on line 131, but no explicit reference was found in the text == Unused Reference: 'RFC2251' is defined on line 134, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2251 (Obsoleted by RFC 4510, RFC 4511, RFC 4512, RFC 4513) ** Obsolete normative reference: RFC 2253 (Obsoleted by RFC 4510, RFC 4514) ** Obsolete normative reference: RFC 2255 (Obsoleted by RFC 4510, RFC 4516) -- No information found for draft-ietf-ldapext-locate-xx - is the name correct? -- No information found for draft-ietf-zeilenga-namedref-xx - is the name correct? Summary: 9 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Kurt D. Zeilenga 3 Intended Category: Experimental OpenLDAP Foundation 4 Expires: 17 May 2001 17 November 2000 6 Use of DNS SRV in LDAP Named Subordinate References 7 9 1. Status of this Memo 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. 14 This document is intended to be, after appropriate review and 15 revision, submitted to the RFC Editor as an Experimental document. 16 Distribution of this memo is unlimited. Technical discussion of this 17 document will take place on the IETF LDAP Extension Working Group 18 mailing list . Please send editorial 19 comments directly to the author . 21 Internet-Drafts are working documents of the Internet Engineering Task 22 Force (IETF), its areas, and its working groups. Note that other 23 groups may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as ``work in progress.'' 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft 31 Shadow Directories can be accessed at http://www.ietf.org/shadow.html. 33 Copyright 2000, The Internet Society. All Rights Reserved. 35 Please see the Copyright section near the end of this document for 36 more information. 38 2. Abstract 40 This document describes how LDAP service location information stored 41 on DNS SRV resource records may be used to in conjunction with named 42 subordinate referral objects. This document defines the dNSReferral 43 object class. 45 3. Background and intended usage 46 Named subordinate referral [NAMEDREF] defines a specific method for 47 representing subordinate references in LDAP [RFC 2251] directories. 48 This document describes a mechanism for using LDAP service location 49 information [LOCATE] available in DNS SRV resource records [RFC2782] 50 to rewrite select LDAP URLs [RFC2255] returned to clients as referrals 51 and search continuations. 53 4. Schema 55 A dNSReferral object is a directory entry whose structural object 56 class is the dNSreferral object class. 58 ( OID.TBD 59 NAME 'dNSReferral' 60 DESC 'DNS SRV aware named subordinate reference object' 61 STRUCTURAL 62 SUP referral ) 64 dNSReferral object behave like referral objects except as detailed in 65 the following section. 67 5. Construction of Referrals and Search References 69 In the referral processing described by [NAMEDREF], if a LDAP URL with 70 no hostpart is to be returned to the client as part of a referral or 71 search continuation, it is replaced with one or more LDAP URLs based 72 upon service location information. 74 The server SHOULD obtain service location information for the DN 75 [RFC2253] present in (or implied by) the LDAP URL. If no service 76 location is available, the server MUST return the LDAP URL. 78 If no service host port pairs are provided by the service location, 79 the server MUST return the LDAP URL. 81 Otherwise, the server SHALL replace the LDAP URL with a set of 82 constructed LDAP URLs. For each service host port pair provided, the 83 server constructs an LDAP URL by replacing the empty hostport with 84 concatenation of the service host, ":", and the port. 86 6. Example 88 Suppose a directory server contains: 90 dn: uid=jsmith,dc=example,dc=net 91 uid: jsmith 92 objectClass: dNSReferral 93 objectClass: extensibleObject 94 ref: ldap:/// 95 ref: ldap://backup/ 97 and DNS holds the following SRV records: 99 _ldap._tcp.example.net. IN SRV 0 0 389 l1.example.net. 100 _ldap._tcp.example.net. IN SRV 0 0 389 l2.example.net. 102 and a client requests a compareRequest with a target DN of 103 "uid=jsmith,dc=example,dc=net". In response to this request, the 104 server may return: 106 compareResponse "referral" { 107 ldap://l1.example.net:389/uid=jsmith,dc=example,dc=net 108 ldap://l2.example.net:389/uid=jsmith,dc=example,dc=net 109 ldap://host/uid=jsmith,dc=example,dc=net 110 } 112 or, if the server chooses to trim the DNs: 114 compareResponse "referral" { 115 ldap://l1.example.net:389/ 116 ldap://l2.example.net:389/ 117 ldap://backup/ 118 } 120 7. Security Considerations 122 This mechanism extends [NAMEDREF] based upon [LOCATE]. The security 123 considerations discussed in these documents generally apply to the 124 specification described in this document. 126 In addition, this mechanism requires the server to make DNS queries. 127 These may require significant time and resources. Caching may help. 129 8. References 131 [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate 132 Requirement Levels", RFC 2119 (Also BCP0014), March 1997. 134 [RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access 135 Protocol (v3)", RFC 2251, December 1997. 137 [RFC2253] M. Wahl, S. Kille, T. Howes, "Lightweight Directory Access 138 Protocol (v3): UTF-8 String Representation of Distinguished 139 Names", RFC 2253, December 1997. 141 [RFC2255] T. Howes, M. Smith, "The LDAP URL Format", RFC 2255, 142 December, 1997. 144 [RFC2782] A. Gulbrandsen, P. Vixie, L. Esibov, "A DNS RR for 145 specifying the location of services (DNS SRV)", RFC 2782, 146 February 2000. 148 [LOCATE] M. Armijo, P. Leach, L Esibov, RL Morgan. "Discovering LDAP 149 Services with DNS", draft-ietf-ldapext-locate-xx.txt (work 150 in progress). 152 [NAMEDREF] K. Zeilenga (editor), "Named Subordinate References in LDAP 153 Directories" draft-ietf-zeilenga-namedref-xx.txt (work in 154 progress) 156 9. Acknowledgments 158 This document is borrows heavily from previous work by IETF LDAPext 159 working group. 161 10. Author's Address 163 Kurt D. Zeilenga 164 OpenLDAP Foundation 165 167 Copyright 2000, The Internet Society. All Rights Reserved. 169 This document and translations of it may be copied and furnished to 170 others, and derivative works that comment on or otherwise explain it 171 or assist in its implementation may be prepared, copied, published and 172 distributed, in whole or in part, without restriction of any kind, 173 provided that the above copyright notice and this paragraph are 174 included on all such copies and derivative works. However, this 175 document itself may not be modified in any way, such as by removing 176 the copyright notice or references to the Internet Society or other 177 Internet organizations, except as needed for the purpose of 178 developing Internet standards in which case the procedures for 179 copyrights defined in the Internet Standards process must be followed, 180 or as required to translate it into languages other than English. 182 The limited permissions granted above are perpetual and will not be 183 revoked by the Internet Society or its successors or assigns. 185 This document and the information contained herein is provided on an 186 "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET 187 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, 188 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 189 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 190 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.