Requirements for Internet Hosts -- Communication Layers¶
Braden, R. (1989). Requirements for Internet Hosts -- Communication Layers: *Requirements for Internet Hosts—Communication Layers. RFC Editor / IETF.
Cited by¶
11 citations across 11 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Layered Accumulation
This sourceInternet Engineering Task Force.
- Layering
This sourceInternet Engineering Task Force.
- Maintenance Rehearsal
- The re-asserting refresh action is the keep-alive probe — a tiny packet that carries no application data and merely signals "still here," re-asserting the binding without enriching or migrating it.
This sourceSpecifies TCP keep-alive probes -- empty segments sent on idle connections to verify the peer and hold path state -- with the keep-alive interval as a tunable refresh against reaping.
- The re-asserting refresh action is the keep-alive probe — a tiny packet that carries no application data and merely signals "still here," re-asserting the binding without enriching or migrating it.
Domain-specific¶
- Internet Protocol Suite
- Network Protocol
- Listed in the references but not attached to a specific claim.
- Protocol Stack
Mechanisms¶
- Data Import Validator
- Normalized Endpoint Contract
- The contract follows the spirit of Postel's robustness principle on the consuming side — accept any conformant delivery
This sourceStates the robustness principle that implementations should be liberal in what they accept.
- The contract follows the spirit of Postel's robustness principle on the consuming side — accept any conformant delivery
- Schema or Protocol Contract
- The robustness principle
This sourceDocuments be conservative in what you send, liberal in what you accept; taken too far it papers over real errors that should have been rejected.
- The robustness principle
- Type Signature
- … signature implies: overly liberal parameters (`Any`, `object`, stringly-typed inputs) and escape hatches (`as`, unchecked casts) that accept out-of-domain values while the signature still looks strict — the robustness-principle temptation to be liberal in what you accept, which quietly enlarges the effective domain.
This sourceStates the robustness principle as being liberal in what is accepted and conservative in what is sent.
- … signature implies: overly liberal parameters (`Any`, `object`, stringly-typed inputs) and escape hatches (`as`, unchecked casts) that accept out-of-domain values while the signature still looks strict — the robustness-principle temptation to be liberal in what you accept, which quietly enlarges the effective domain.
- Usability Tolerance Testing
- … mode is recruiting convenience: pull in colleagues and confident volunteers and the envelope quietly narrows back to nominal, so the test passes precisely the case it was meant to stress, a self-defeating echo of Postel's robustness principle — be liberal in what you accept — applied to people rather than protocols.
This sourceThe protocol Robustness Principle says to be liberal in what an Internet host accepts and conservative in what it sends.
- … mode is recruiting convenience: pull in colleagues and confident volunteers and the envelope quietly narrows back to nominal, so the test passes precisely the case it was meant to stress, a self-defeating echo of Postel's robustness principle — be liberal in what you accept — applied to people rather than protocols.
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? Not recorded. Neither this nor any other of the 11 citations of this work carries a recorded support check.
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 3 other ways.
- https://doi.org/10.17487/RFC1122 ×3
- https://www.rfc-editor.org/info/rfc1122 ×2
- https://www.rfc-editor.org/rfc/rfc1122 ×2
Registry ID ref:bb660bdd588f · see in the full table