[lsd0001] branch master updated: correct case order to handle special APEX case described in 7.3.1

[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 3b90fbc  correct case order to handle special APEX case described in 
7.3.1
3b90fbc is described below

commit 3b90fbcf41d4462dcd482897db7e6a7862f72eb1
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Wed Feb 2 16:48:36 2022 +0100

    correct case order to handle special APEX case described in 7.3.1
---
 draft-schanzen-gns.xml | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 406fc0b..c275624 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -1952,24 +1952,24 @@ example.com = zk2
          </li>
          <li>
            Case 3:
-           If the remainder of the name to resolve is empty
-           the record set (including supplemental records)
-           is the final result and the recursion is concluded.
-         </li>
-         <li>
-           Case 4:
            If the remainder of the name to be resolved is of the format
            "_SERVICE._PROTO" and the record set contains one or more matching 
BOX
            records, the records in the BOX records are the final result and 
the recursion
            is concluded (<xref target="box_processing" />).
          </li>
          <li>
-           Case 5:
+           Case 4:
            If the current record set
            consist of a single delegation record (<xref 
target="delegation_processing" />),
            resolution of the remainder of the name is delegated to
            the target zone as described in <xref 
target="delegation_processing" />.
          </li>
+         <li>
+           Case 5:
+           If the remainder of the name to resolve is empty
+           the record set (including supplemental records)
+           is the final result and the recursion is concluded.
+         </li>
          <li>
            Otherwise, resolution fails and the resolver MUST return an empty 
record set.
         </li>
@@ -2006,7 +2006,8 @@ example.com = zk2
              received a record set containing only a single delegation record, 
the
              recursion is continued with the record value as authoritative zone
              and the empty apex label "@" as remaining name, except in the case
-             where the desired record type is equal to the zone type, in which
+             where the desired record type as specified by the client
+             is equal to the ztype, in which
              case the delegation record is returned and the resolution is 
concluded without
              resolving the empty apex label.
            </t>

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