gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0001] branch master updated: clarify nick and supplemental processin


From: gnunet
Subject: [lsd0001] branch master updated: clarify nick and supplemental processing
Date: Sun, 20 Feb 2022 20:48:10 +0100

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 b9ca4a2  clarify nick and supplemental processing
b9ca4a2 is described below

commit b9ca4a223fef0111db454ba39470d3d2aed6fb9c
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sun Feb 20 20:48:04 2022 +0100

    clarify nick and supplemental processing
---
 draft-schanzen-gns.xml | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index d1bbc15..4864182 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -2031,12 +2031,15 @@ example.com = zTLD2 := Base32GNS(ztype2||zk2)
          <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.
+           the record set is the final result.
+           If any NICK records are in the final result set, it MUST be
+           processed according to <xref target="nick_processing" />.
+           Otherwise, the final result set is returned.
          </li>
          <li>
-           Otherwise, resolution fails and the resolver MUST return an empty 
record set.
-        </li>
+           Finally, if none of the above is applicable resolution fails and the
+           resolver MUST return an empty record set.
+         </li>
         </ul>
          <section anchor="redirect_processing" numbered="true" toc="default">
            <name>REDIRECT</name>

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]