RFC 4876 on A Configuration Profile Schema for Lightweight Directory Access Protocol (LDAP)-Based Agents
rfc-editor@rfc-editor.org Sat, 19 May 2007 00:32 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HpCsO-0000v3-KD; Fri, 18 May 2007 20:32:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HpCsN-0000uh-9D for ietf-announce@ietf.org; Fri, 18 May 2007 20:32:51 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HpCsL-00004t-Tl for ietf-announce@ietf.org; Fri, 18 May 2007 20:32:51 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l4J0WnUn015260; Fri, 18 May 2007 17:32:49 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l4J0WnWu015259; Fri, 18 May 2007 17:32:49 -0700
Date: Fri, 18 May 2007 17:32:49 -0700
Message-Id: <200705190032.l4J0WnWu015259@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4876 on A Configuration Profile Schema for Lightweight Directory Access Protocol (LDAP)-Based Agents
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 4876 Title: A Configuration Profile Schema for Lightweight Directory Access Protocol (LDAP)-Based Agents Author: B. Neal-Joslin, Ed., L. Howard, M. Ansari Status: Informational Date: May 2007 Mailbox: bob_joslin@hp.com, lukeh@padl.com, morteza@infoblox.com Pages: 39 Characters: 73468 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-joslin-config-schema-17.txt URL: http://www.rfc-editor.org/rfc/rfc4876.txt This document consists of two primary components, a schema for agents that make use of the Lightweight Directory Access protocol (LDAP) and a proposed use case of that schema, for distributed configuration of similar directory user agents. A set of attribute types and an object class are proposed. In the proposed use case, directory user agents (DUAs) can use this schema to determine directory data location and access parameters for specific services they support. In addition, in the proposed use case, attribute and object class mapping allows DUAs to reconfigure their expected (default) schema to match that of the end user's environment. This document is intended to be a skeleton for future documents that describe configuration of specific DUA services. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce