[lsd0001] branch master updated: bcp14 annotations, understanding CRITICAL and SHADOW is non-optional

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new ba82339  bcp14 annotations, understanding CRITICAL and SHADOW is 
non-optional
ba82339 is described below

commit ba8233929346e1456c79a59400de50c9dad066d8
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Jun 30 21:03:09 2023 +0200

    bcp14 annotations, understanding CRITICAL and SHADOW is non-optional
---
 draft-schanzen-gns.xml | 21 ++++++++++++---------
 1 file changed, 12 insertions(+), 9 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 961978a..6a2b775 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -342,12 +342,12 @@
            A secure mapping from names to records:
            GNS allows zone owners to map labels to resource records or to
            delegate authority of names in the subdomain induced by a label to 
other zones.
-           Zone owners MAY choose to publish this information to make it
+           Zone owners <bcp14>MAY</bcp14> choose to publish this information 
to make it
            available to other users.
-           To publishing mappings, mappings MUST be signed and encrypted
+           To publishing mappings, mappings <bcp14>MUST</bcp14> be signed and 
encrypted
            using keys derived from the respective label.
            When names are resolved, signatures on resource records
-           including delegations MUST be verified by the implementation.
+           including delegations <bcp14>MUST</bcp14> be verified by the 
implementation.
          </li>
        </ol>
        <t>
@@ -742,7 +742,7 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
        </t>
        <t>
          Given an average difficulty of D, the proofs have an
-         expiration time of EPOCH.  Applications MAY calculate proofs
+         expiration time of EPOCH.  Applications <bcp14>MAY</bcp14> calculate 
proofs
          with a difficulty that is higher than D by providing POW
          values where there are (on average) more than D bits of leading zeros.
          With each additional bit of difficulty, the
@@ -984,7 +984,8 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
        </dd>
        <dt>FLAGS</dt>
        <dd>
-         is a 16-bit resource record flags field (see below).
+         is a 16-bit bit field indicating special properties of the resource 
record.
+         The semantics of the different bits are defined below.
        </dd>
        <dt>TYPE</dt>
        <dd>
@@ -1006,15 +1007,17 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
        </dd>
      </dl>
      <t>
-       Flags indicate metadata surrounding the resource record.
+       The FLAGS field is used to indicate special properties of the resource 
record.
        An application creating resource records <bcp14>MUST</bcp14> set all 
bits
-       to 0 unless it wants to set the respective flag.
+       in FLAGS to 0 unless it specifically understands and
+       wants to set the respective flag.
        As additional flags can be defined in future protocol versions,
        if an application or implementation encounters a flag which it does not
-       recognize, it <bcp14>MUST</bcp14> be ignored.
+       recognize, it <bcp14>MUST</bcp14> be ignored.  However, all 
implementations
+       <bcp14>MUST</bcp14> understand the SHADOW and CRITICAL flags defined 
below.
        Any combination of the flags specified below are valid.
        <xref target="figure_flag"/>
-       illustrates the flag distribution in the 16-bit flag field of a
+       illustrates the flag distribution in the 16-bit FLAGS field of a
        resource record:
      </t>
      <figure anchor="figure_flag" title="The Resource Record Flag Wire 
Format.">

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.