Reserving field names in the uri specification grammar

uri/redis.txt

@@ -98,6 +98,16 @@ Scheme semantics:
   The semantics of "query" URI field key-value pairs other than those
   previously mentioned are implementation-defined.
 
+Reserved URI fields:
+
+  The following field names are reserved within the URI context.
+These are expressed using RGC 5234 ABNF, and are reserved as follows:
+
+  protocol       = DIGIT / "."
+                 ; this is optional, corresponding to the version of
+                 ; the RESP protocol requested.
+                 ; the digits 0-9, and a period
+
 Encoding considerations:
   Unknown, use with care.
 
@@ -185,4 +195,4 @@ Security considerations:
 Acknowledgments:
   The author of this registration document gratefully acknowledges the
   feedback provided by Graham Klyne of Nine by Nine and Itamar Haber of
-  Redis Labs on drafts of this document.
+  Redis Labs on drafts of this document.

uri/rediss.txt

@@ -58,6 +58,16 @@ Scheme semantics:
   semantics as the redis: scheme.  See the IANA registration for the
   redis: scheme for details.
 
+Reserved URI fields:
+
+  The following field names are reserved within the URI context.
+These are expressed using RGC 5234 ABNF, and are reserved as follows:
+
+  protocol       = DIGIT / "."
+                 ; this is optional, corresponding to the version of
+                 ; the RESP protocol requested.
+                 ; the digits 0-9, and a period
+
 Encoding considerations:
   Unknown, use with care.
 
@@ -91,4 +101,4 @@ Security considerations:
   and data integrity.  It is theoretically possible to use client
   certificates as an alternative Redis-level authentication/login
   mechanism in place of the username/password-based "AUTH" RESP
-  command.
+  command.