RFC 9170: Long-Term Viability of Protocol Extension Mechanisms
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9170
- Published
- December 2021
- Authors
- M. Thomson; T. Pauly
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8809Registries for Web Authentication (WebAuthn)Current
August 2020
- RFC 8701Applying Generate Random Extensions And Sustain Extensibility (GREASE) to TLS ExtensibilityCurrent
January 2020
- RFC 8684TCP Extensions for Multipath Operation with Multiple AddressesCurrent
March 2020
- RFC 9748Updating the NTP RegistriesCurrent
February 2025
- RFC 9897Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple AddressesCurrent
January 2026
- RFC 7578Returning Values from Forms: multipart/form-dataCurrent
July 2015
- RFC 5751Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message SpecificationObsoleted
January 2010
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?