Ideas for changes to the IETF document approval process
draft-bradner-ietf-proc-ideas-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Scott O. Bradner | ||
Last updated | 2003-07-28 | ||
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 problem working group has shown that a number of IETF participants feel that the current process by which the IETF approves documents for publication as RFCs needs to be changed. There does not seem to be consensus on specific reasons that change is needed but there seems to be consensus that change is needed. This document is designed to provide some ideas on different ways that the current processes could be revised. My intent is to spur discussion on possibilities, not to say (at this time) what my preference is.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)