Skip to main content

Long-term Viability of Protocol Extension Mechanisms
draft-thomson-use-it-or-lose-it-02

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Author Martin Thomson
Last updated 2018-12-31 (Latest revision 2018-06-29)
Replaces draft-thomson-protocol-freedom
Replaced by draft-iab-use-it-or-lose-it, RFC 9170
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 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

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)