Robustness principle: Difference between revisions

Revision as of 23:25, 9 December 2019

Revision as of 04:47, 5 March 2020

Line 11:

== Interpretation ==

RFC 1122 (1989) expanded on Postel's principle by recommending that programmers "assume that the network is filled with malevolent entities that will send in packets designed to have the worst possible effect".<ref>{{cite IETF |title=Requirements for Internet Hosts: Communication Layers |rfc=1122 |editor1-last=Braden |editor1-first=R. |editor1-link=Bob Braden |date=October 1989 |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=June 9, 2014}}</ref> Protocols should allow for the addition of new codes for existing fields in future versions of protocols by accepting messages with unknown codes (possibly logging them). Programmers should avoid sending messages with "legal but obscure protocol features" that might expose deficiencies in receivers, and design their code "not just to survive other misbehaving hosts, but also to cooperate to limit the amount of disruption such hosts can cause to the shared communication facility".<ref name="Wilde2012">{{cite book |last=Wilde |first=Erik |title=Wilde's WWW: Technical Foundations of the World Wide Web |url=https://booksarchive.google.comorg/books?id=w7mrCAAAQBAJ&pg=PA26details/springer_10.1007-978-3-642-95855-7 |date=2012 |orig-year=1999 |publisher=Springer‑Verlag |doi=10.1007/978-3-642-95855-7 |isbn=978-3-642-95855-7| page=[https://archive.org/details/springer_10.1007-978-3-642-95855-7/page/n48 26]}}</ref>

== Criticism ==