RFCs and the "Historical" Category
draft-klensin-historical-definition-01

Document Type Expired Internet-Draft (individual)
Last updated 2014-08-18 (latest revision 2014-02-14)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-klensin-historical-definition-01.txt

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

John Klensin (john-ietf@jck.com)
Scott Bradner (sob@harvard.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)