Long-Term Viability of Protocol Extension Mechanisms
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 17
- Abstract
- 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.
- Publication Date
- 2021-12-01
- Status Note
- Informational
- DOI
10.17487/RFC9170- Link
- https://doi.org/10.17487/RFC9170
- Author(s)
- Martin ThomsonTommy Pauly
- Keyword(s)
- Extensions, GREASE
Latest version of IETF RFC 9170
Document Versions — IETF RFC 9170
-
▶ IETF RFC 9170 (2021-12-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- 10.1016-j.comnet.2020.107211 — NEW-PROTOCOLS EXTERNAL
- 10.1145-2068816.2068834 — IMC11 EXTERNAL
- IETF.draft-ietf-httpbis-messaging-19 — I-D.ietf-httpbis-messaging EXTERNAL
- IETF.draft-ietf-httpbis-semantics-19 — I-D.ietf-httpbis-semantics EXTERNAL
- Raiciu, C., Paasch, C., Barre, S., Ford, A., Honda, M., Duchene, F., Bonaventure, O., and M. Handley, "How Hard Can It Be? Designing and Implementing a Deployable Multipath TCP", April 2012, <https://www.usenix.org/conference/nsdi12/technical-sessions/presentation/raiciu>. EXTERNAL
- Kario, H., "Re: [TLS] Thoughts on Version Intolerance", July 2016, <https://mailarchive.ietf.org/arch/msg/tls/bOJ2JQc3HjAHFFWCiNTIb0JuMZc>. EXTERNAL
- "DNS Flag Day 2019", May 2019, <https://dnsflagday.net/2019/>. EXTERNAL
- Bellovin, S. and E. Rescorla, "Deploying a New Hash Algorithm", Proceedings of NDSS, 2006, <https://www.cs.columbia.edu/~smb/papers/new-hash.pdf>. EXTERNAL
- Langley, A., "[TLS] Accepting that other SNI name types will never work.", March 2016, <https://mailarchive.ietf.org/arch/msg/tls/1t79gzNItZd71DwwoaqcQQ_4Yxc>. EXTERNAL
- IETF RFC 791 [Active*]
- IETF RFC 793 [Superseded*]
- IETF RFC 1112 [Active*]
- IETF RFC 1157 [Active*]
- IETF RFC 2113 [Active*]
- IETF RFC 2464 [Active*]
- IETF RFC 2711 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3597 [Active*]
- IETF RFC 5218 [Active*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 5321 [Active*]
- IETF RFC 5704 [Active*]
- IETF RFC 6066 [Active*]
- IETF RFC 6709 [Active*]
- IETF RFC 6733 [Active*]
- IETF RFC 6891 [Active*]
- IETF RFC 7208 [Active*]
- IETF RFC 7301 [Active*]
- IETF RFC 7413 [Active*]
- IETF RFC 7489 [Superseded*]
- IETF RFC 7696 [Active*]
- IETF RFC 7838 [Active*]
- RFC8170 — RFC8170 EXTERNAL
- IETF RFC 8446 [Superseded*]
- IETF RFC 8460 [Active*]
- IETF RFC 8558 [Active*]
- IETF RFC 8684 [Active*]
- IETF RFC 8701 [Active*]
- IETF RFC 8941 [Superseded*]
- IETF RFC 8999 [Active*]
- IETF RFC 9000 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9170.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9170, Long-Term Viability of Protocol Extension Mechanisms. Available at https://doi.org/10.17487/RFC9170
Snippet:
IETF RFC 9170, Long-Term Viability of Protocol Extension Mechanisms. Available at https://doi.org/10.17487/RFC9170
HTML (ISO 690 compliant)
Preview:
IETF RFC 9170, Long-Term Viability of Protocol Extension Mechanisms. Available at https://doi.org/10.17487/RFC9170
Snippet:
<span class="citation"><cite>IETF RFC 9170</cite>, Long-Term Viability of Protocol Extension Mechanisms. Available at <a href="https://doi.org/10.17487/RFC9170" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9170</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9170, Long-Term Viability of Protocol Extension Mechanisms
doi: 10.17487/RFC9170
url: https://doi.org/10.17487/RFC9170
doi: 10.17487/RFC9170
url: https://doi.org/10.17487/RFC9170
Snippet:
<li> <cite id="bib-rfc9170">IETF RFC 9170</cite>, Long-Term Viability of Protocol Extension Mechanisms <span class="doi">10.17487/RFC9170</span> </li>
Referenced By
- IETF RFC 9287 [Active*]
- IETF RFC 9293 [Active*]