Internet-Drafts Don't Expire
draft-thomson-gendispatch-no-expiry-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Thomson | ||
| Last updated | 2020-05-07 (Latest revision 2019-11-04) | ||
| RFC stream | (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
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)