Repurposing the STD Designation
draft-klensin-newtrk-std-repurposing-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. John C. Klensin | ||
| Last updated | 2004-06-07 | ||
| 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
Over the years, it has been repeatedly observed that the STD nnnn and BCP nnnn designation for IETF Standards has not worked well, either as a stable reference for external specifications or as a combined reference for multiple documents that are linked together into a single specification. This document proposes two changes that have been discussed on and off for some time, but never written up or considered as specific proposals. The first of these would assign a STD (or BCP) number to a specification when it enters the first level of the Standards Track (or is first designated as a BCP). The second would turn STDs and BCPs into actual documents that describe what they identify and their publication and change history.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)