On Tue, Oct 7, 2014 at 6:55 AM, <Valdis.Kletnieks@xxxxxx> wrote:
Also, if you're documenting a protocol that's not an IETF Standard, the protocol
description can still benefit from RFC2119 semantics. If there's a spot
where the protocol semantic should have a 'MUST NOT', and a client does it
anyhow, what happens?
Sure. But this is not a protocol, this is a recommended set of features.