Long-Term Viability of Protocol Extension Mechanisms
RFC 9170
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['Extensions', 'versions', 'grease']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "T. Pauly": changed name from "Tommy Pauly" to "T. Pauly", cleared affiliation (was "Apple") |
|
2026-05-20
|
(System) | Changed author "M. Thomson": changed name from "Martin Thomson" to "M. Thomson", cleared affiliation (was "Mozilla") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2021-12-30
|
(System) | Received changes through RFC Editor sync (created alias RFC 9170, changed title to 'Long-Term Viability of Protocol Extension Mechanisms', changed abstract to 'The ability … Received changes through RFC Editor sync (created alias RFC 9170, changed title to 'Long-Term Viability of Protocol Extension Mechanisms', changed abstract to 'The ability to change protocols depends on exercising the extension and version-negotiation mechanisms that support change. This document explores how regular use of new protocol features can ensure that it remains possible to deploy changes to a protocol. Examples are given where lack of use caused changes to be more difficult or costly.', changed pages to 17, changed standardization level to Informational, changed state to RFC, added RFC published event at 2021-12-30, changed IAB state to Published RFC) |
|
2021-12-30
|
(System) | RFC published |