[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: improve English
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: improve English |
Date: |
Fri, 30 Jun 2023 23:37:00 +0200 |
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 6c54a72 improve English
6c54a72 is described below
commit 6c54a724bd64d781d4395ee2f8afdbc4b2caeecf
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Jun 30 23:36:54 2023 +0200
improve English
---
draft-schanzen-gns.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 1a0363d..76957ba 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -2077,12 +2077,12 @@ q := SHA-512 (ZKDF(zk, label))
Recursive in this context means that a resolver does not provide
intermediate results for a query to the application.
Instead, it <bcp14>MUST</bcp14> respond to a resolution request with
either the
- requested resource record or an error message in case the resolution
+ requested resource record or an error message in case resolution
fails.
<xref target="figure_resolution"/> illustrates how an application
requests the lookup of a GNS name (1).
The application <bcp14>MAY</bcp14> provide a desired record type to the
resolver.
- Subsequently, the Start Zone is determined (2) and the recursive
+ Subsequently, a Start Zone is determined (2) and the recursive
resolution process started.
This is where the desired record type is used to guide processing.
For example, if a zone delegation record type is requested, the
@@ -2091,8 +2091,8 @@ q := SHA-512 (ZKDF(zk, label))
Details on how the resolution process is initiated and each iterative
result (3a,3b) in the resolution is processed are provided in the
sections below.
The results of the lookup are eventually returned to the application
(4).
- The implementation <bcp14>MUST NOT</bcp14> filter results
- according to the desired record type.
+ The implementation <bcp14>MUST NOT</bcp14> filter the returned resource
+ record sets according to the desired record type.
Filtering of record sets is typically done by the application.
</t>
<figure anchor="figure_resolution" title="The recursive GNS resolution
process.">
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
- [lsd0001] branch master updated: improve English, gnunet, 2023/06/30
- [lsd0001] branch master updated: improve English, gnunet, 2023/06/30
- [lsd0001] branch master updated: improve English, gnunet, 2023/06/30
- [lsd0001] branch master updated: improve English, gnunet, 2023/06/30
- [lsd0001] branch master updated: improve English,
gnunet <=
- [lsd0001] branch master updated: improve English, gnunet, 2023/06/30
- [lsd0001] branch master updated: improve English, gnunet, 2023/06/30