Development Plan for Reissuing Existing LDAPv3 RFCs In CY2001
draft-wahl-ldapv3-2001plan-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark Wahl | ||
| Last updated | 2000-07-19 | ||
| 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 IESG prefers to avoid having RFCs linger in Proposed Standard Status. In general, RFCs which have demonstratable interoperability and usefulness should become Draft Standards, and eventually may become full Standards, as described in RFC 2026 [1] section 6.2. When a Proposed Standard RFC is reissued to become Draft, corrections, clarifications and other changes can be integrated into the update. However, if changes to the protocol are 'very significant', then the document needs to be issued as Proposed Standard again. This document describes an approach to reissue the core RFCs which describe LDAPv3, all of which are currently at Proposed Standard status. It also summarizes the status of other existing and upcoming standards-track LDAP RFCs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)