RFCs and the "Historical" Category
draft-klensin-historical-definition-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. John C. Klensin , Scott O. Bradner | ||
| Last updated | 2014-08-18 (Latest revision 2014-02-14) | ||
| 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 "Historical" category has been used to identify some documents in the RFC Series for many years, but has never been precisely defined except in various oral traditions. More important, with one exception that is now obsolete, the conditions under which documents should be reclassified as Historic and the procedures for doing so have never been defined, leading to a number of ad hoc and inconsistent actions. This document clarifies both the category and procedures for putting documents into it.
Authors
Dr. John C. Klensin
Scott O. Bradner
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)