Clarifying the Historic RFC Maturity Level
draft-yevstifeyev-genarea-historic-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mykyta Yevstifeyev | ||
| Last updated | 2011-03-02 | ||
| 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
This document defined what the Historic RFC maturity level means, what are the criteria for Historic RFCs, describes procedures for republication and reclassification of RFCs in Historic maturity level and discusses other issues related to Historic RFCs. It updates RFC 2026.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)