Skip to main content

Long-term Viability of Protocol Extension Mechanisms

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Martin Thomson
Last updated 2019-07-07
Replaces draft-thomson-protocol-freedom
Replaced by draft-iab-use-it-or-lose-it
RFC stream (None)
Intended RFC status (None)
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 (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:


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.


Martin Thomson

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