Internet-Drafts Don't Expire
draft-thomson-gendispatch-no-expiry-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2020-05-07 (latest revision 2019-11-04) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
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) | ||
https://www.ietf.org/archive/id/draft-thomson-gendispatch-no-expiry-00.txt
Abstract
The long-standing insistence that Internet-Drafts carry expiration dates is a concept that is no longer necessary. This document removes requirements for expiration for Internet-Drafts from RFC 2418/BCP 25. Note to Readers Discussion of this document takes place on the GENDISPATCH Working Group mailing list (gendispatch@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/gendispatch/ [1]. Source for this draft and an issue tracker can be found at https://github.com/martinthomson/no-expiry [2].
Authors
Martin Thomson (mt@lowentropy.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)