Long-term Viability of Protocol Extension Mechanisms
draft-thomson-use-it-or-lose-it-04
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-07-07 | ||
| Replaces | draft-thomson-protocol-freedom | ||
| Replaced by | draft-iab-use-it-or-lose-it | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-iab-use-it-or-lose-it | |
| Telechat date | |||
| 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-thomson-use-it-or-lose-it-04.txt
https://www.ietf.org/archive/id/draft-thomson-use-it-or-lose-it-04.txt
Abstract
The ability to change protocols depends on exercising the extension and version negotiation mechanisms that support change. Protocols that don't use these mechanisms can find that deploying changes can be difficult and costly.
Authors
Martin Thomson (mt@lowentropy.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)