Maintaining Robust Protocols¶
Thomson, M., & Schinazi, D. (2023). Maintaining Robust Protocols. RFC 9413.
Cited by¶
5 citations across 5 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Asymmetric Interface Tolerance
- In network protocols, the canonical home, the robustness principle and its modern reassessment make the four-cell space explicit: the early-internet choice of sender-strict, receiver-liberal produced rapid interoperability and the specification drift that later ossified the protocols, as de-facto behavior calcified in middleboxes.
This sourceDocuments how sender-strict/receiver-liberal policy drove early-internet interoperability and later protocol ossification as de-facto behavior calcified in middleboxes.
Supported in partVerified against the work's full text
RFC 9413 covers early-Internet leniency and entrenchment of flaws as de facto standards, but does not discuss ossification or middleboxes.
“Tolerating unexpected input might be an expedient tool for systems in early phases of deployment, which was the case for the early Internet.”
- In network protocols, the canonical home, the robustness principle and its modern reassessment make the four-cell space explicit: the early-internet choice of sender-strict, receiver-liberal produced rapid interoperability and the specification drift that later ossified the protocols, as de-facto behavior calcified in middleboxes.
Mechanisms¶
- Conformance Test Suite
- And a suite that is too lenient about what it accepts quietly rewards implementations for being permissive rather than correct — the well-known hazard behind Postel's robustness principle, where accepting sloppy input masks nonconformance and lets divergence accumulate.
This sourceExplains that excessive tolerance lets implementation errors and noncompliance succeed, become entrenched, and drive accumulating divergence across a protocol ecosystem.
- And a suite that is too lenient about what it accepts quietly rewards implementations for being permissive rather than correct — the well-known hazard behind Postel's robustness principle, where accepting sloppy input masks nonconformance and lets divergence accumulate.
- Decode Error Taxonomy
- Tolerance improves interoperability, but the "liberal in what you accept" half of the robustness principle is a well-documented attack surface.
This sourceExplains the interoperability rationale for tolerant input handling while warning that permissive acceptance can create security and protocol-evolution hazards.
- Tolerance improves interoperability, but the "liberal in what you accept" half of the robustness principle is a well-documented attack surface.
- Lenient Parser with Canonicalizer
- The subtler cost is that broad silent tolerance teaches producers the written contract does not matter, so variants proliferate and the real contract quietly becomes "whatever the parser happens to accept."
This sourceExplains how permissive handling can entrench variants until deployed implementations supersede the formal specification as the de facto contract.
- The subtler cost is that broad silent tolerance teaches producers the written contract does not matter, so variants proliferate and the real contract quietly becomes "whatever the parser happens to accept."
- Tolerant Reader / Strict Writer Policy
- The interface-design canon is Postel's robustness principle — "be conservative in what you send, be liberal in what you accept"
This sourceRestates Postel’s robustness principle and explains how broad acceptance can entrench malformed behavior as a de facto contract that other implementations must reproduce.
- The interface-design canon is Postel's robustness principle — "be conservative in what you send, be liberal in what you accept"
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 5 citations: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
Registry ID ref:04df1c9c1a74 · see in the full table