RFC Series Model Process
draft-flanagan-rseme-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Heather Flanagan | ||
| Last updated | 2020-05-22 (Latest revision 2019-11-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 RFC Series has come to a crossroads where questions must be answered regarding how the Series should be managed, the role of the RFC Series Editor, and the oversight of the RFC Editor function. This draft offers a proposal to form a new IAB program called the RFC Editor Future Development Program. This proposal is based on the discussions held during three virtual meetings in September and October 2019, as well as the RSEME session at IETF 106, and requests a new, open IAB program that will drive consensus around any changes to the RFC Editor model. The program will require extensive community engagement and outreach to a broad set of stakeholder communities.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)