Robustness principle
E519647
The Robustness principle is a design guideline in network and software engineering that advises systems to be conservative in what they send and liberal in what they accept to maximize interoperability and resilience.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Robustness principle canonical | 1 |
| robustness principle | 1 |
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
design principle
ⓘ
network protocol design guideline ⓘ software engineering design guideline ⓘ |
| aimsTo |
allow interoperability despite minor specification deviations
ⓘ
reduce communication failures ⓘ |
| alsoKnownAs |
Postel principle
NERFINISHED
ⓘ
Postel's law NERFINISHED ⓘ be conservative in what you send, be liberal in what you accept ⓘ |
| appliesTo |
APIs
NERFINISHED
ⓘ
communication protocols ⓘ data format parsers ⓘ network protocols ⓘ software interfaces ⓘ |
| associatedWith |
IETF culture
ⓘ
Internet protocol suite NERFINISHED ⓘ TCP NERFINISHED ⓘ Transmission Control Protocol NERFINISHED ⓘ |
| criticizedFor |
encouraging acceptance of invalid inputs
ⓘ
increasing security risks ⓘ leading to interoperability quirks ⓘ making protocol evolution harder ⓘ |
| field |
computer networking
ⓘ
protocol design ⓘ software engineering ⓘ |
| goal |
enable backward compatibility
ⓘ
enable forward compatibility ⓘ improve resilience to variations in input ⓘ increase robustness of systems ⓘ maximize interoperability ⓘ |
| hasAspect |
conservative output generation
ⓘ
liberal input acceptance ⓘ |
| influenced |
HTTP implementations
ⓘ
design of many Internet protocols ⓘ email protocol implementations ⓘ web browser behavior ⓘ |
| influencedBy | need for interoperability between heterogeneous systems ⓘ |
| mentionedIn |
RFC 1122
NERFINISHED
ⓘ
RFC 761 NERFINISHED ⓘ TCP specification NERFINISHED ⓘ |
| originator | Jon Postel NERFINISHED ⓘ |
| relatedConcept |
backward compatibility
ⓘ
defensive programming ⓘ fault tolerance ⓘ graceful degradation ⓘ resilience ⓘ robustness ⓘ |
| statedAs | Be conservative in what you send, be liberal in what you accept ⓘ |
| timePeriod |
early Internet design
ⓘ
late 1970s ⓘ |
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
Postel’s law
this entity surface form:
robustness principle