From eb115b31375034725e8ad492e276da685b675d8f Mon Sep 17 00:00:00 2001 From: Alexandros Frantzis Date: Mon, 2 May 2022 14:54:40 +0300 Subject: readme: Mandate proper use of RFC 2119 keywords This mandate makes explicit a practice that's already established in the writing of the protocol descriptions, and officially clarifies the meaning of the keywords for readers. Signed-off-by: Alexandros Frantzis --- README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.md b/README.md index 5af76d9..f88716f 100644 --- a/README.md +++ b/README.md @@ -141,6 +141,26 @@ corresponding interface version bump. Backward incompatible changes can only be done by creating a new major version of the extension. ``` +## Use of RFC 2119 keywords + +Descriptions of all new protocols must use (in lowercase) and adhere to the +proper meaning of the keywords described in +[RFC 2119](https://www.rfc-editor.org/info/rfc2119). + +All protocol descriptions that follow the guidelines in RFC 2119 must +incorporate the following text in their toplevel protocol description section: + +``` +The key words "must", "must not", "required", "shall", "shall not", "should", +"should not", "recommended", "may", and "optional" in this document are to +be interpreted as described in IETF RFC 2119. +``` + +Note that not all existing protocol descriptions conform to RFC 2119. Protocol +maintainers are encouraged to audit their descriptions, update them as needed +to follow RFC 2119 guidelines, and mark them as conformant in the way described +in the previous paragraph. + ## Backward compatible protocol changes A protocol may receive backward compatible additions and changes. This -- cgit v1.2.3