lsd0001

commit f802e9a3415c09d469ae00df322292261e8104b7
parent 151647654c961b3a2cb9af222dedea65087e5d7b
Author: Schanzenbach, Martin <mschanzenbach@posteo.de>
Date:   Sun, 15 Dec 2019 19:20:24 +0100

update entry zone

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

1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -872,14 +872,18 @@
          <t>
            In each step of the recursive name resolution, there is an
            authoritative zone zk and a name to resolve which may be empty.
-           Initially, the authoritative zone is the entry zone. If the name
+           Initially, the authoritative zone is the root entry zone. If the name
            is empty, it is interpreted as the apex label "@".
          </t>
+         <t>
+           From here, the following steps are recursively executed, in order:
+         </t>
          <ol>
            <li>Extract the right-most label from the name to look up.</li>
            <li>Calculate q using the label and zk.</li>
            <li>Perform a DHT query GET(q) to retrieve the RRBLOCK.</li>
-           <li>Verify the RRBLOCK and decrypt the BDATA contained in it.</li>
+           <li>Verify and process the RRBLOCK and decrypt the BDATA contained
+             in it.</li>
          </ol>
          <t>
            Upon receiving the RRBLOCK from the DHT, apart from verifying the