Lightweight Directory Access Protocol v3):Applicability Statement
draft-hodges-ldapv3-as-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bob L. Morgan , Jeff Hodges | ||
| Last updated | 2000-06-23 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The specification for the Lightweight Directory Access Protocol version 3 (LDAPv3) nominally comprises eight separte RFCs which were issued in two distinct subsets at separate times (RFCs 2251..2256 first, then RFCs 2229 and 2830 following later), but this has never been formally stated. Additionally, RFCs 2251..2256 each are embellished with an 'IESG Note' warning implementors and deployers of potential interoperability prob- lems due to the lack of a specification of mandatory-to-implement authentication mechanism(s). This document corrects both situations by explicitly specifying the set of RFCs comprising LDAPv3 and rescinding the 'IESG Note' due to the specification of mandatory-to-implement authentication mechanisms in RFC 2829.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)