On Tue, Apr 27, 2004 at 11:30:47PM +1000, Brett Watson wrote:
The usual principle is "Postel's Robustness Principle", which states that an
endpoint should be strict in what it sends, but liberal in what it accepts.
*ARGL*
Have you ever read RFC1812, 1.3.2 Robustness Principle?
It is not about accepting every bullshit and trying to get some sense
from it. It is about stability and that applications must be prepared
to receive packets violating the protocol, but that the application
should not crash on receipt of such packets, but deal with them.
[ ... ] If the protocol
specification defines four possible error codes, the software must
not break when a fifth code is defined. An undefined code might be
logged, but it must not cause a failure.
It is not about building workarounds for broken implementations by lousy
or careless programmers breaking the protocol.
\Maex
--
SpaceNet AG | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development | D-80807 Muenchen | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
proportional to the amount of vacuity between the ears of the admin"