idnits 2.17.1 draft-wahl-ldap-adminaddr-04.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 207. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 218. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 225. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 231. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. 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: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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 (November 17, 2006) is 6370 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 (~~), 2 warnings (==), 7 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 November 17, 2006 5 Expires: May 21, 2007 7 LDAP Administrator Address Attribute 8 draft-wahl-ldap-adminaddr-04 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 May 21, 2007. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 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 this this attribute are used to provide contact 55 information of the responsible party for an LDAP server, or of the 56 responsible party for a naming context within a LDAP server. 58 This attribute is intended to be used by management tools that are 59 LDAP clients. For example, a management tool for checking the state 60 of a replication or referral topology might use this attribute to 61 send email to the manager of a particular server when it detects an 62 error. 64 (This attribute type was originally defined in the mid-1990s for 65 inclusion in the LDAPv3 data model, but was omitted from the LDAPv3 66 root DSE specification as there was only one implementation of a 67 server supporting that attribute at that time.) 69 The words "MUST", "SHOULD" and "MAY" are used as defined in RFC 2119 70 [2]. 72 Please send comments to the author at mark.wahl@informed-control.com. 74 2. The administratorsAddress attribute 76 The attribute type is defined as follows (with lines wrapped for 77 readability): 79 ( 1.3.6.1.4.1.1466.101.120.1 NAME 'administratorsAddress' 80 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 81 USAGE directoryOperation ) 83 Attributes of this type can contain one or more values, and each 84 value is a URI [3]. Each URI is encoded using the IA5 string syntax 85 [4]. 87 Unlike the labeledURI attribute [6], these values do not have a 88 label. 90 In existing practice, this URI can be of the 'mailto:' form 91 identifying a personal or role email address, such as 92 "mailto:helpdesk@example.com". 94 To obtain the responsible party for a directory server, the attribute 95 is read from the root DSE, using a baseObject search requesting this 96 attribute by returned, as described in RFC 4512 [5]. 98 To obtain the responsible party for a naming context, the attribute 99 is read from the entry at the base of the naming context, using a 100 baseObject search requesting this attribute be returned. Note that 101 these addresses need not be the same as that of the directory server 102 administrator, or of a data administrator. 104 This document only specifies how a client can read this attribute. 105 Some servers MAY support updating this attribute over protocol, 106 subject to access control. Other servers might instead provide this 107 value read only, if it is configured through the server's out-of-band 108 management interface, such as in a configuration file. 110 3. Security Considerations 112 The server's access control policy SHOULD allow this information to 113 be visible to a suitable administrator in the same organization. 114 Since one use of this attribute is to find who is responsible if the 115 server is not making authentication decisions properly, a directory 116 server configuration SHOULD cause the attribute in the root DSE, if 117 present, to be able to be returned in a search response to all users 118 who are permitted to access the directory server. The administrator 119 SHOULD choose addresses for use in this attribute that are already 120 publicly known within the organization, and SHOULD NOT encode 121 passwords or other secret information within the URIs. 123 4. IANA Considerations 125 The LDAP Parameter registration for this attribute has already been 126 reviewed by the Directorate and processed by IANA. This attribute 127 object identifier is registered as follows: 129 Descriptor: administratorsAddress 131 Object Identifier: 1.3.6.1.4.1.1466.101.120.1 133 Person & email address to contact for further information: 134 Mark Wahl 136 Usage: attribute type 138 Author/Change Controller: Mark Wahl 140 5. Acknowledgments 142 The contents of this document is based on earlier work of the ASID 143 Working Group of the IETF. The contributions of its members is 144 greatly appreciated. 146 6. References 148 6.1. Normative References 150 [1] Zeilenga, K., "Lightweight Directory Access Protocol (LDAP): 151 Technical Specification Road Map", RFC 4510, June 2006. 153 [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement 154 Levels", RFC 2119, BCP 14, March 1997. 156 [3] Berners-Lee, T., "Uniform Resource Identifier (URI): Generic 157 Syntax", RFC 1738, STD 66, January 2005. 159 [4] Legg, S., "Lightweight Directory Access Protocol (LDAP): 160 Syntaxes and Matching Rules", RFC 4517, June 2006. 162 [5] Zeilenga, K., "Lightweight Directory Access Protocol (LDAP): 163 Directory Information Models", RFC 4512, June 2006. 165 6.2. Informative References 167 [6] Smith, M., "Definition of an X.500 Attribute Type and Object 168 Class to Hold Uniform Resource Identifiers (URIs)", RFC 2079. 170 Appendix A. Copyright 172 Copyright (C) The Internet Society 2006. This document is subject to 173 the rights, licenses and restrictions contained in BCP 78, and except 174 as set forth therein, the authors retain all their rights. This 175 document and the information contained herein are provided on an "AS 176 IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 177 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 178 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 179 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 180 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 181 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 183 Author's Address 185 Mark Wahl 186 Informed Control Inc. 187 PO Box 90626 188 Austin, TX 78709 189 US 191 Email: mark.wahl@informed-control.com 193 Full Copyright Statement 195 Copyright (C) The Internet Society (2006). 197 This document is subject to the rights, licenses and restrictions 198 contained in BCP 78, and except as set forth therein, the authors 199 retain all their rights. 201 This document and the information contained herein are provided on an 202 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 203 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 204 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 205 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 206 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 207 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 209 Intellectual Property 211 The IETF takes no position regarding the validity or scope of any 212 Intellectual Property Rights or other rights that might be claimed to 213 pertain to the implementation or use of the technology described in 214 this document or the extent to which any license under such rights 215 might or might not be available; nor does it represent that it has 216 made any independent effort to identify any such rights. Information 217 on the procedures with respect to rights in RFC documents can be 218 found in BCP 78 and BCP 79. 220 Copies of IPR disclosures made to the IETF Secretariat and any 221 assurances of licenses to be made available, or the result of an 222 attempt made to obtain a general license or permission for the use of 223 such proprietary rights by implementers or users of this 224 specification can be obtained from the IETF on-line IPR repository at 225 http://www.ietf.org/ipr. 227 The IETF invites any interested party to bring to its attention any 228 copyrights, patents or patent applications, or other proprietary 229 rights that may cover technology that may be required to implement 230 this standard. Please address the information to the IETF at 231 ietf-ipr@ietf.org. 233 Acknowledgment 235 Funding for the RFC Editor function is provided by the IETF 236 Administrative Support Activity (IASA).