Alternative Proposed Model for RFC Editing and Publication
draft-carpenter-rfced-model-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|---|---|---|
| Author | Brian E. Carpenter | |
| Last updated | 2021年02月21日 (Latest revision 2020年08月20日) | |
| 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 finishing process for a document that is approved for publication as an RFC currently involves a somewhat detailed and lengthy process. The system that executes that process involves a number of different actors, each bringing competency with different aspects of the overall process. Ensuring that this process functions smoothly is critical to the mission of the organizations that publish documents in the RFC series. This document proposes a framework for that system that aims to provide clear delineations of accountability and responsibility for each of the actors in this system. It would require significant updates to RFC 8728 and RFC 8729, and minor updates to RFC 2850 and RFC 7841. Discussion of this document takes place on the RFC Editor Futures mailing list (rfced-future@iab.org).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)