[lsd0001] branch master updated: start zone

[gnunet]

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

martin-schanzenbach pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new bd47a61  start zone
bd47a61 is described below

commit bd47a611a2c52bcc9cb98fc4787416f64b031dbf
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Fri May 20 21:37:40 2022 +0200

    start zone
---
 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 f33fc77..9901932 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -3259,20 +3259,21 @@ Value       Symbol            Symbol
          </t>
        </section>
        <section>
-         <name>Suffix-to-zone Configuration</name>
+         <name>Start Zone Configuration</name>
          <t>
            A user is expected to install a GNS implementation if it is not 
already
            provided through other means such as the operating system
            or the browser.
-           It is likely that the implementation ships with a configurable
-           default suffix-to-name mapping.
+           It is likely that the implementation ships with a
+           default start zone configuration.
            This means that the user is able to resolve GNS names ending on a
-           zTLD or ending on a configured suffix-to-name mapping.
+           zTLD or ending on any suffix-to-name mapping that is part of the
+           default start zone configuration.
            At this point the user may delete or otherwise modify the
-           implementation's default suffix-to-name mapping:
+           implementation's default configuration:
           </t>
           <t>
-            Deletion of mappings may become necessary of the
+            Deletion of suffix-to-zone mappings may become necessary of the
             zone owner referenced by the mapping has lost the trust of the 
user.
             For example, this could be due to lax registration policies 
resulting
             in phishing activities.
@@ -3287,6 +3288,8 @@ Value       Symbol            Symbol
             GNS zone of the bank.
             Other examples include scanning the QR off the device of a friend,
             from a storefront, or an advertisement.
+            The information contained within such QR code is not in scope
+            of this document.
             The level of trust in the respective zone is contextual and likely
             varies from user to user.
             Trust in a zone provided through a letter from a bank which
@@ -3296,9 +3299,9 @@ Value       Symbol            Symbol
             be reflected in the local naming as well.
           </t>
           <t>
-            User clients should facilitate the suffix-to-name modification
-            process, for example by providing a QR code reader or other import
-            mechanisms.
+            User clients should facilitate the modification of the start zone
+            configuration, for example by providing a QR code reader or other
+            import mechanisms.
             Implementations are ideally implemented
             according to best practices and addressing applicable points
             from <xref target="security"/>.

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