Proposed mechanics for document advancement
draft-hardie-advance-mechanics-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ted Hardie | ||
| Last updated | 2010-09-16 | ||
| 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 IETF has maintained a three-stage standards track for some time, with basic mechanics set out in RFC 2026 [RFC2026]. The mechanics as described, however, are not currently used in practice and advancement along the standards track is both unusual and more difficult than many IETF participants find reasonable. This document proposes an update to those mechanics, in the interest of improving the overall functioning of the IETF. It is compatible with, but does not require, a move to a two-stage standards track.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)