The Harmful Consequences of the Robustness Principle
draft-iab-protocol-maintenance-04

Document Type Expired Internet-Draft
Last updated 2020-05-06 (latest revision 2019-11-03)
Replaces draft-thomson-postel-was-wrong
Stream IAB
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream IAB state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-iab-protocol-maintenance-04.txt

Abstract

The robustness principle, often phrased as "be conservative in what you send, and liberal in what you accept", has long guided the design and implementation of Internet protocols. The posture this statement advocates promotes interoperability in the short term, but can negatively affect the protocol ecosystem over time. For a protocol that is actively maintained, the robustness principle can, and should, be avoided.

Authors

Martin Thomson (mt@lowentropy.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)