repo: gemini-site
action: commit
revision: 
path_from: 
revision_from: 1e52e4bff34120424a0f5060040961f9bc492fcb:
path_to: 
revision_to: 

commit 1e52e4bff34120424a0f5060040961f9bc492fcb
Author: Solderpunk 
Date:   Sun Nov 14 18:58:21 2021 +0100

    Clarify that MUST etc. are to be interpreted as per BCP14.

diff --git a/docs/specification.gmi b/docs/specification.gmi

--- a/docs/specification.gmi
+++ b/docs/specification.gmi
@@ -10,6 +10,10 @@ This is provided mostly so that people can quickly get up to speed on what I'm t

 Feedback on any part of this is extremely welcome, please email solderpunk@posteo.net.

+# Conventions used in this document
+
+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 BCP14.
+
 # 1 Overview

 Gemini is a client-server protocol featuring request-response transactions, broadly similar to gopher or HTTP.  Connections are closed at the end of a single transaction and cannot be reused.  When Gemini is served over TCP/IP, servers should listen on port 1965 (the first manned Gemini mission, Gemini 3, flew in March '65).  This is an unprivileged port, so it's very easy to run a server as a "nobody" user, even if e.g. the server is written in Go and so can't drop privileges in the traditional fashion.

-----END OF PAGE-----