-----Original Message-----
From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
Sent: Sunday, September 15, 2002 2:27 PM
To: McDonald, Ira; 'srvloc-discuss at lists.sourceforge.net'
Subject: [Srvloc-discuss] RE: Editors: RFC 3377 - single authoritative
LDAPv3 reference
Hi,
Oops - I left off the last (most important) paragraph of section 2:
"The term "LDAPv3" is often used informally to refer to the protocol
specified by the above set of RFCs, or subsets thereof. However, the
>> LDAPv3 protocol suite, as defined here, should be formally identified
>> in other documents by a normative reference to this document."
Cheers,
- Ira McDonald
High North Inc
-----Original Message-----
From: McDonald, Ira
Sent: Sunday, September 15, 2002 2:20 PM
To: srvloc-discuss at lists.sourceforge.net
Subject: Editors: RFC 3377 - single authoritative LDAPv3 reference
SLP document editors,
Just published - the LDAPv3 "roadmap":
RFC 3377 Lightweight Directory Access Protocol (v3): Technical
Specification. J. Hodges, R. Morgan. September 2002. (Format:
TXT=9981 bytes) (Status: PROPOSED STANDARD)
ftp://ftp.isi.edu/in-notes/rfc3377
Cheers,
- Ira McDonald
High North Inc
------------------------------------------------------------------------
[excerpt from RFC 3377]
Abstract
This document specifies the set of RFCs comprising the Lightweight
Directory Access Protocol Version 3 (LDAPv3), and addresses the "IESG
Note" attached to RFCs 2251 through 2256.
1. Background and Motivation
The specification for the Lightweight Directory Access Protocol
version 3 (LDAPv3) nominally comprises eight RFCs which were issued
in two distinct subsets at separate times -- RFCs 2251 through 2256
first, then RFCs 2829 and 2830 following later.
RFC 2251 through 2256 do not mandate the implementation of any
satisfactory authentication mechanisms and hence were published with
an "IESG Note" discouraging implementation and deployment of LDAPv3
clients or servers implementing update functionality until a Proposed
Standard for mandatory authentication in LDAPv3 is published.
RFC 2829 was subsequently published in answer to the IESG Note.
The purpose of this document is to explicitly specify the set of RFCs
comprising LDAPv3, and formally address the IESG Note through
explicit inclusion of RFC 2829.
2. Specification of LDAPv3
The Lightweight Directory Access Protocol version 3 (LDAPv3) is
specified by this set of nine RFCs:
[RFC2251] Lightweight Directory Access Protocol (v3) [the
specification of the LDAP on-the-wire protocol]
[RFC2252] Lightweight Directory Access Protocol (v3): Attribute
Syntax Definitions
[RFC2253] Lightweight Directory Access Protocol (v3): UTF-8
String Representation of Distinguished Names
[RFC2254] The String Representation of LDAP Search Filters
[RFC2255] The LDAP URL Format
[RFC2256] A Summary of the X.500(96) User Schema for use with
LDAPv3
[RFC2829] Authentication Methods for LDAP
[RFC2830] Lightweight Directory Access Protocol (v3): Extension
for Transport Layer Security
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Srvloc-discuss mailing list
Srvloc-discuss at lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/srvloc-discuss