STD Numbers and the IETF Standards Track
draft-klensin-std-numbers-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. John C. Klensin | ||
| Last updated | 2019-01-02 (Latest revision 2018-07-01) | ||
| 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
STD numbers are assigned to IETF Standards Track specifications in order to provide a stable reference even when RFCs are revised and the underlying documents change. However, the numbers are only assigned when the specifications reach Full Standard maturity level, significantly reducing their utility in the contemporary world in which few specifications advance beyond the first standardization maturity level. For that reason, one recent proposal suggested eliminating the numbers entirely. This document argues that stable references for Standards Track specifications are actually useful and that the solution is not to abolish the numbers but to change the point at which they are assigned.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)