PROTOCOL: Document plan to treat some errors as bogus

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>

diff --git a/PROTOCOL.md b/PROTOCOL.md
index d60f3b42fab995b04ded15d1a74d013c601194d0..4625e2b63ed3bc756d1d2e1daafa997a4eb47d2b 100644 (file)
--- a/PROTOCOL.md
+++ b/PROTOCOL.md
@@ -300,3 +300,6 @@ _impossible_ rather than _bogus_.  So we err on the side of treating
 client mistakes as due to synchronisation and incomplete modelling:
 ie, we only treat a client update as _bogus_ if it is patently
 obviously wrong (for example, it is syntactically invalid).
+
+Fatal errors which the client could not have predicted, but which are
+not recoverable, can also be treated as bogus.