[lsd0001] branch master updated: add fixme on client resolver

[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 c7b45d4  add fixme on client resolver
c7b45d4 is described below

commit c7b45d4eef77fb512c9b1c92750ba1f978e84644
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sat Feb 5 23:52:17 2022 +0100

    add fixme on client resolver
---
 draft-schanzen-gns.xml | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 6d50df2..8063830 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -266,6 +266,13 @@
          A GNS resource record contains information as defined by its
          resource record type.
        </dd>
+       <dt>Client (Resolver)</dt>
+       <dd>
+         FIXME: We are using the word "client" often and it is not clearly
+         defined what a client is. Sometimes it is a "client resolver".
+         Is there another part of the resolver? What is it called?
+         This is mostly an issue in the name resolution section.
+       </dd>
      </dl>
    </section>
    <section anchor="overview" numbered="true" toc="default">
@@ -1840,7 +1847,8 @@ q := SHA-512 (ZKDF-Public(zk, label))
        provided by the client to guide processing.
        <!-- FIXME: Is this still necessary? Clarify the purpose of the
        provided record type and normatively define that resolver MUST NOT
-       filter? -->
+       filter? THe normative statement for the CLIENT does not make sense.
+       We need a normative statement for the implementer of GNS. -->
        However, filtering of record sets according to the required record
        types MUST still be done by the client after the resource record set
        is retrieved.
@@ -1849,13 +1857,14 @@ q := SHA-512 (ZKDF-Public(zk, label))
        <name>Start Zones</name>
        <t>
          <!-- FIXME: This is a mess -->
-         The resolution of a GNS name must start in a given start zone
-         indicated to the resolution algorithm using a (public) zone key.
-         The local resolver may have one or more local start zones 
configured/hard-coded
-         which point to local or remote zone public keys.
+         The resolution of a GNS name starts in an initial start zone.
+         The local resolver may have one or more local start zones configured
+         which point to local or remote zone keys.
          A resolver may also determine the start zone from the
          suffix of the name given for resolution, or using information
          retrieved out of band.
+       </t>
+       <t>
          The governance model of any zone is at the sole discretion
          of the zone owner.
          However, the choice of start zone(s) is at the sole

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