lsd0001

commit d164177f4de7ec0a1a45ab979708c333082f1354
parent 1531ffae4f58fac438f5c3299b7829ee67e85d77
Author: Christian Grothoff <christian@grothoff.org>
Date:   Tue,  1 Feb 2022 19:00:53 +0100

should, not must (for embedded use-cases, MUST makes no sense); also fix FMT

Diffstat:
M
draft-schanzen-gns.xml
 | 
8
++++----

1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -759,11 +759,11 @@ zTLD := zkl[126..129].zkl[63..125].zkl[0..62]
    <section anchor="rrecords" numbered="true" toc="default">
      <name>Resource Records</name>
      <t>
-       A GNS implementer MUST provide a mechanism to create and manage resource
+       A GNS implementer SHOULD provide a mechanism to create and manage resource
        records for local zones. A local zone is established by selecting a
        zone type and creating a zone key pair.
-       As records may be added to each created zone, a (local) persistence
-       mechanism such as a database for resource records and zones must be provided.
+       As records may be added to each zone by its owner, a (local) persistence
+       mechanism such as a database for resource records and zones SHOULD be provided.
        This local zone database is used by the name resolution logic and serves
        as a basis for publishing zones into the GNS storage (see <xref target="publish"/>).
      </t>
@@ -2798,7 +2798,7 @@ b9ae0482cdaa9095
          ]]>
        </artwork>
      </section>
-     <section pn="section-acks">
+     <section>
         <name>Acknowledgements</name>
         <t>
           The authors thank D. J. Bernstein, A. Farrel and S. Bortzmeyer for their