From 1d1ec0324bd41cabfb696ed9cd1dfdd01310da96 Mon Sep 17 00:00:00 2001 From: Daira Emma Hopwood Date: Thu, 14 Dec 2023 18:05:49 +0000 Subject: [PATCH] ZIP 321: clarify the usage of ``req-``. Signed-off-by: Daira Emma Hopwood --- zip-0321.rst | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/zip-0321.rst b/zip-0321.rst index 99a720da..ecfbe34e 100644 --- a/zip-0321.rst +++ b/zip-0321.rst @@ -15,9 +15,9 @@ Terminology =========== -The key words "MUST", "MUST NOT", "SHOULD", "RECOMMENDED", and "MAY" in this -document are to be interpreted as described in BCP 14 [#BCP14]_ when, and only -when, they appear in all capitals. +The key words "MUST", "REQUIRED", "MUST NOT", "SHOULD", "RECOMMENDED", and "MAY" +in this document are to be interpreted as described in BCP 14 [#BCP14]_ when, and +only when, they appear in all capitals. The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.11 of the Zcash Protocol Specification [#protocol-networks]_. @@ -291,6 +291,13 @@ parser does not recognize any variables which are prefixed with ``req-``, it MUST consider the entire URI invalid. Any other variables that are not recognized, but that are not prefixed with a ``req-``, SHOULD be ignored. +``req-`` is potentially part of a given parameter name that may be defined +in a future version of this ZIP, not a modifier that can be applied to an +arbitrary parameter. None of the originally defined parameters (``address``, +``amount``, ``label``, ``memo``, and ``message``) include the ``req-`` +prefix, because these parameters are REQUIRED to be understood by all +conformant ZIP 321 URI parsers. + Backward compatibility ----------------------