RFC 3045 on LDAP Root DSE to Display Vendor Information
RFC Editor <rfc-ed@ISI.EDU> Tue, 30 January 2001 00:49 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12804; Mon, 29 Jan 2001 19:49:35 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA19546 for ietf-123-outbound.10@ietf.org; Mon, 29 Jan 2001 19:45:02 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA19472 for <all-ietf@loki.ietf.org>; Mon, 29 Jan 2001 19:33:30 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA12605 for <all-ietf@ietf.org>; Mon, 29 Jan 2001 19:33:29 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA11123; Mon, 29 Jan 2001 16:33:27 -0800 (PST)
Message-Id: <200101300033.QAA11123@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3045 on LDAP Root DSE to Display Vendor Information
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 29 Jan 2001 16:33:27 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3045 Title: Storing Vendor Information in the LDAP root DSE Author(s): M. Meredith Status: Informational Date: January 2001 Mailbox: mark_meredith@novell.com Pages: 6 Characters: 10518 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mmeredith-rootdse-vendor-info-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3045.txt This document specifies two Lightweight Directory Access Protocol (LDAP) attributes, vendorName and vendorVersion that MAY be included in the root DSA-specific Entry (DSE) to advertise vendor-specific information. These two attributes supplement the attributes defined in section 3.4 of RFC 2251. The information held in these attributes MAY be used for display and informational purposes and MUST NOT be used for feature advertisement or discovery. 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.echo 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.