idnits 2.17.1 draft-wahl-ldap-adminaddr-02.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 201. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 212. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 219. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 225. ** 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 (August 30, 2006) is 6439 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 August 30, 2006 5 Expires: March 3, 2007 7 LDAP Administrator Address Attribute 8 draft-wahl-ldap-adminaddr-02 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 3, 2007. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 Organizations running multiple directory servers need an ability for 42 administrators to determine who is responsible for a particular 43 server. An attribute, conceptually similar to the 'sysContact' 44 object of SNMP, is defined which can retrieved from the directory 45 server using the Lightweight Directory Access Protocol. 47 1. Introduction 49 This document defines an optional attribute for use in LDAP [1]. 51 This attribute was originally defined in the mid-1990s for inclusion 52 in the LDAPv3 data model, but was omitted from the LDAPv3 root DSE 53 specification as there was only one implementation of a server 54 supporting that attribute at that time. 56 The words "MUST", "SHOULD" and "MAY" are used as defined in RFC 2119 57 [2]. 59 Please send comments to the author at mark.wahl@informed-control.com. 61 2. The administratorsAddress attribute 63 This attribute allows a server administrator to provide the contact 64 information of the responsible party for an LDAP server or naming 65 context. This can be used by management clients which are, for 66 example, checking the state of a replication or referral topology, to 67 provide a way for the user of the management client to send email to 68 manager of a particular server. 70 The attribute is defined as follows (with lines wrapped for 71 readability): 73 ( 1.3.6.1.4.1.1466.101.120.1 NAME 'administratorsAddress' 74 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 75 USAGE directoryOperation ) 77 This attribute can contain one or more values, and each value is a 78 URI [3]. Each URI is encoded using the IA5 string syntax [5]. 80 Unlike the labeledURI attribute [6], these values do not have a 81 label. 83 This document only specifies how a client can read this attribute. 84 Some servers MAY support updating this attribute over protocol, 85 subject to access control, however for many servers it is anticipated 86 that the values of this attribute would be configured through the 87 server's out-of-band management interface, such as in a configuration 88 file. 90 In existing practice, this URI is commonly of the 'mailto:' form 91 identifying a role mail 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 as described in 96 RFC 4512 [4]. 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. Note that 100 these addresses need not be the same as that of the directory server 101 administrator, or of a data administrator. 103 3. Security Considerations 105 The server's access control policy SHOULD allow this information to 106 be visible to any suitable administrator in the same organization. 107 Since one use of this attribute is to find who is responsible if the 108 server is not making authentication decisions properly, it MAY be 109 visible to all users who are permitted to access the directory 110 server. The administrator SHOULD choose addresses for use in this 111 attribute that are already publically known within the organization, 112 and SHOULD NOT encode passwords or other secret information within 113 the URIs. 115 4. IANA Considerations 117 This attribute will be registered as follows: 119 Subject: Request for LDAP Descriptor Registration 121 Descriptor: administratorsAddress 123 Object Identifier: 1.3.6.1.4.1.1466.101.120.1 125 Person & email address to contact for further information: 126 Mark Wahl 128 Usage: attribute type 130 Specification: (I-D) RFC XXXX 132 Author/Change Controller: Mark Wahl 134 5. Acknowledgments 136 The contents of this document is based on earlier work of the ASID 137 Working Group of the IETF. The contributions of its members is 138 greatly appreciated. 140 6. References 142 6.1. Normative References 144 [1] Zeilenga, K., "Lightweight Directory Access Protocol (LDAP): 145 Technical Specification Road Map", RFC 4510, June 2006. 147 [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement 148 Levels", RFC 2119, BCP 14, March 1997. 150 [3] Berners-Lee, T., "Uniform Resource Identifier (URI): Generic 151 Syntax", RFC 1738, STD 66, January 2005. 153 [4] Zeilenga, K., "Lightweight Directory Access Protocol (LDAP): 154 Directory Information Models", RFC 4512, June 2006. 156 [5] Legg, S., "Lightweight Directory Access Protocol (LDAP): 157 Syntaxes and Matching Rules", RFC 4517, June 2006. 159 6.2. Informative References 161 [6] Smith, M., "Definition of an X.500 Attribute Type and Object 162 Class to Hold Uniform Resource Identifiers (URIs)", RFC 2079. 164 Appendix A. Copyright 166 Copyright (C) The Internet Society 2006. This document is subject to 167 the rights, licenses and restrictions contained in BCP 78, and except 168 as set forth therein, the authors retain all their rights. This 169 document and the information contained herein are provided on an "AS 170 IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 171 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 172 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 173 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 174 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 175 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 177 Author's Address 179 Mark Wahl 180 Informed Control Inc. 181 PO Box 90626 182 Austin, TX 78709 183 US 185 Email: mark.wahl@informed-control.com 187 Full Copyright Statement 189 Copyright (C) The Internet Society (2006). 191 This document is subject to the rights, licenses and restrictions 192 contained in BCP 78, and except as set forth therein, the authors 193 retain all their rights. 195 This document and the information contained herein are provided on an 196 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 197 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 198 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 199 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 200 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 201 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 203 Intellectual Property 205 The IETF takes no position regarding the validity or scope of any 206 Intellectual Property Rights or other rights that might be claimed to 207 pertain to the implementation or use of the technology described in 208 this document or the extent to which any license under such rights 209 might or might not be available; nor does it represent that it has 210 made any independent effort to identify any such rights. Information 211 on the procedures with respect to rights in RFC documents can be 212 found in BCP 78 and BCP 79. 214 Copies of IPR disclosures made to the IETF Secretariat and any 215 assurances of licenses to be made available, or the result of an 216 attempt made to obtain a general license or permission for the use of 217 such proprietary rights by implementers or users of this 218 specification can be obtained from the IETF on-line IPR repository at 219 http://www.ietf.org/ipr. 221 The IETF invites any interested party to bring to its attention any 222 copyrights, patents or patent applications, or other proprietary 223 rights that may cover technology that may be required to implement 224 this standard. Please address the information to the IETF at 225 ietf-ipr@ietf.org. 227 Acknowledgment 229 Funding for the RFC Editor function is provided by the IETF 230 Administrative Support Activity (IASA).