Clarifying IETF Document Status
draft-nottingham-where-does-that-come-from-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Mark Nottingham | ||
| Last updated | 2021-09-12 (Latest revision 2021-03-11) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-nottingham-where-does-that-come-from-00.txt
https://www.ietf.org/archive/id/draft-nottingham-where-does-that-come-from-00.txt
Abstract
There is widespread confusion about the status of Internet-Drafts and RFCs, especially regarding their association with the IETF and other streams. This document recommends several interventions to more closely align reader perceptions with actual document status.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)