idnits 2.17.1 draft-wahl-ldap-adminaddr-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 210. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 236. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 247. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 254. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 260. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1, updated by RFC 4748 (on line 224), which is fine, but *also* found old RFC 3978, Section 5.4, paragraph 1 text on line 210. ** Found boilerplate matching RFC 3978, Section 5.5, updated by RFC 4748 (on line 236), which is fine, but *also* found old RFC 3978, Section 5.5 text on line 210. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == In addition to RFC 3978, Section 5.5 boilerplate, a section with a similar start was also found: This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The copyright year in the IETF Trust Copyright Line does not match the current year == 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 (September 6, 2007) is 6078 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) ** Obsolete normative reference: RFC 1738 (ref. '3') (Obsoleted by RFC 4248, RFC 4266) Summary: 4 errors (**), 0 flaws (~~), 4 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Wahl 3 Internet-Draft Informed Control Inc. 4 Intended status: Standards Track September 6, 2007 5 Expires: March 9, 2008 7 LDAP Administrators Address Attribute 8 draft-wahl-ldap-adminaddr-05 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on March 9, 2008. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2007). 39 Abstract 41 Organizations with multiple or outsourced directory servers need the 42 ability for administrators to determine who is responsible for a 43 particular directory server. This document defines an attribute with 44 contact information for a directory server's responsible party, 45 conceptually similar to the 'sysContact' object of SNMP, which can be 46 retrieved from the directory server using the Lightweight Directory 47 Access Protocol. 49 1. Introduction 51 This document defines an attribute type, administratorsAddress, for 52 use in LDAP [1] directory deployments. 54 The values of attributes of this attribute type are used to provide 55 contact information of the responsible party for an LDAP server, or 56 of the responsible party for a naming context (or other directory 57 administrative division) within a LDAP server. 59 This attribute is intended to be used by management tools that are 60 LDAP clients. For example, a management tool for checking the state 61 of a replication or referral topology might use this attribute to 62 send email to the manager of a particular server when it detects an 63 error. 65 (This attribute type was originally defined in the mid-1990s for 66 inclusion in the LDAPv3 data model, but was omitted from the LDAPv3 67 root DSE specification as there was only one implementation of a 68 server supporting that attribute at that time.) 70 The words "MUST", "SHOULD" and "MAY" are used as defined in RFC 2119 71 [2]. 73 Please send comments to the author at mark.wahl@informed-control.com. 75 2. The administratorsAddress attribute 77 The attribute type is defined as follows (with lines wrapped for 78 readability): 80 ( 1.3.6.1.4.1.1466.101.120.1 NAME 'administratorsAddress' 81 EQUALITY caseExactIA5Match 82 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 83 USAGE directoryOperation ) 85 Attributes of this type can contain one or more values, and each 86 value is a URI [3]. Each URI is encoded using the IA5 string syntax 87 [4]. 89 Unlike the labeledURI attribute [6], these values do not have a 90 label. 92 In existing practice, this URI can be of the 'mailto:' form 93 identifying a personal or role email address, such as 94 "mailto:helpdesk@example.com". 96 To obtain the responsible party for a directory server, the attribute 97 is read from the root DSE, using a baseObject search requesting the 98 attribute of this type be returned, as described in RFC 4512 [5]. 100 To obtain the responsible party for a naming context, the attribute 101 is read from the entry at the base of the naming context, using a 102 baseObject search requesting the attribute of this type be returned. 103 Note that these addresses need not be the same as that of the 104 directory server administrator, or of a data administrator. 106 An attribute of this type MAY be present in other entries and 107 subentries in a directory information tree. For example, an 108 attribute might be present in a collective attribute subentry. 109 (Collective attribute subentries are defined in RFC 3671 [7] and RFC 110 3672 [8]). 112 A client SHOULD treat values of this attribute type which do not 113 contain a valid URI as non-resolvable. 115 This document only specifies how a client can read this attribute. 116 Some servers MAY support updating this attribute over protocol, 117 subject to access control. Other servers might instead provide this 118 value read only, if it is configured through the server's out-of-band 119 management interface, such as in a configuration file. 121 3. Security Considerations 123 Generally, the information provided by this attribute in a particular 124 organization's directory service is intended to be visible to all the 125 directory service administrators and to all the administrators of 126 directory-enabled applications in the organization. Since one use of 127 this attribute is to find who is responsible for a directory server 128 that is not making authentication decisions properly, in some 129 deployments it might be appropriate to allow any user, including 130 anonymous (unauthenticated) users, to read the values of an attribute 131 of this type from the root DSE. Thus, it is good practice that the 132 email addresses chosen for use in this attribute avoid revealing 133 personal information. Applications setting values of this attribute 134 SHOULD NOT encode passwords or other secret information within the 135 URIs, and MUST allow the administrator to choose not to provide a 136 value for this attribute. 138 4. IANA Considerations 140 The LDAP Parameter registration for this attribute type has already 141 been reviewed by the Directorate and processed by IANA. This 142 attribute type object identifier is registered as follows: 144 Descriptor: administratorsAddress 146 Object Identifier: 1.3.6.1.4.1.1466.101.120.1 148 Person & email address to contact for further information: 149 Mark Wahl 151 Usage: attribute type 153 Author/Change Controller: Mark Wahl 155 5. Changes from previous versions 157 In an earlier Internet-Draft of the ASID working group, the 158 administratorsAddress attribute was defined to only be present in the 159 root DSE, the definition did not specify an equality matching rule 160 and had usage "dSAOperation", and the values of the attribute were 161 limited to being URLs of the mailto form. 163 6. Acknowledgments 165 The contents of this document is based on earlier work of the ASID 166 Working Group of the IETF. The contributions of its members is 167 greatly appreciated. 169 7. References 171 7.1. Normative References 173 [1] Zeilenga, K., "Lightweight Directory Access Protocol (LDAP): 174 Technical Specification Road Map", RFC 4510, June 2006. 176 [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement 177 Levels", RFC 2119, BCP 14, March 1997. 179 [3] Berners-Lee, T., "Uniform Resource Identifier (URI): Generic 180 Syntax", RFC 1738, STD 66, January 2005. 182 [4] Legg, S., "Lightweight Directory Access Protocol (LDAP): 183 Syntaxes and Matching Rules", RFC 4517, June 2006. 185 [5] Zeilenga, K., "Lightweight Directory Access Protocol (LDAP): 186 Directory Information Models", RFC 4512, June 2006. 188 7.2. Informative References 190 [6] Smith, M., "Definition of an X.500 Attribute Type and Object 191 Class to Hold Uniform Resource Identifiers (URIs)", RFC 2079. 193 [7] Zeilenga, K., "Collective Attributes in the Lightweight 194 Directory Access Protocol (LDAP)", RFC 3671. 196 [8] Zeilenga, K. and S. Legg, "Subentries in the Lightweight 197 Directory Access Protocol (LDAP)", RFC 3672. 199 Appendix A. Copyright 201 Copyright (C) The Internet Society 2007. This document is subject to 202 the rights, licenses and restrictions contained in BCP 78, and except 203 as set forth therein, the authors retain all their rights. This 204 document and the information contained herein are provided on an "AS 205 IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 206 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 207 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 208 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 209 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 210 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 212 Author's Address 214 Mark Wahl 215 Informed Control Inc. 216 PO Box 90626 217 Austin, TX 78709 218 US 220 Email: mark.wahl@informed-control.com 222 Full Copyright Statement 224 Copyright (C) The IETF Trust (2007). 226 This document is subject to the rights, licenses and restrictions 227 contained in BCP 78, and except as set forth therein, the authors 228 retain all their rights. 230 This document and the information contained herein are provided on an 231 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 232 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 233 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 234 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 235 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 236 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 238 Intellectual Property 240 The IETF takes no position regarding the validity or scope of any 241 Intellectual Property Rights or other rights that might be claimed to 242 pertain to the implementation or use of the technology described in 243 this document or the extent to which any license under such rights 244 might or might not be available; nor does it represent that it has 245 made any independent effort to identify any such rights. Information 246 on the procedures with respect to rights in RFC documents can be 247 found in BCP 78 and BCP 79. 249 Copies of IPR disclosures made to the IETF Secretariat and any 250 assurances of licenses to be made available, or the result of an 251 attempt made to obtain a general license or permission for the use of 252 such proprietary rights by implementers or users of this 253 specification can be obtained from the IETF on-line IPR repository at 254 http://www.ietf.org/ipr. 256 The IETF invites any interested party to bring to its attention any 257 copyrights, patents or patent applications, or other proprietary 258 rights that may cover technology that may be required to implement 259 this standard. Please address the information to the IETF at 260 ietf-ipr@ietf.org. 262 Acknowledgment 264 Funding for the RFC Editor function is provided by the IETF 265 Administrative Support Activity (IASA).