zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

ZIP 321: clarify the usage of ``req-``. 

Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Emma Hopwood 2023-12-14 18:05:49 +00:00
parent 57d2d72003
commit 1d1ec0324b
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
zip-0321.rst
View File

@ -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
----------------------