Referencing Internet-Drafts in RFCs
draft-hoffman-id-references-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Paul E. Hoffman | ||
| Last updated | 2016-05-26 (Latest revision 2015-11-23) | ||
| 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
RFC 2026 places restrictions on how Internet-Drafts can be referred to in RFCs. Over time, the way that the IETF community uses Internet-Drafts has changed. The restrictions from RFC 2026 sometimes make RFCs inaccurate (because many drafts that are referred to are not actually "works in progress", and also make references to Internet-Drafts nearly useless to RFC readers. This document updates the one part of RFC 2026, and the one part of RFC 7322, that covers referencing Internet-Drafts.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)