commit 81880ef835e9b0e4e7716cb77b24d14d7438c521
parent 84251fc22f707a613ea129b4f1b86e1dbbbc5485
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Thu, 3 Feb 2022 13:22:26 +0100
fix
Diffstat:
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -1951,18 +1951,21 @@ example.com = zk2
If the redirect name ends in ".+",
resolution continues in GNS with the new name in the
current zone.
- Otherwise, the resulting name is resolved via the
+ Otherwise, the redirect name treated as a GNS name
+ and resolution restarts.
+ <!-- FIXME Otherwise, the resulting name is resolved via the
default operating system name resolution process.
This may in turn trigger a GNS name resolution process depending
- on the system configuration.
+ on the system configuration.-->
<!-- Note: this permits non-DNS resolvers to be triggered via NSS! -->
</t>
+ <t>
In order to prevent infinite loops, the resolver MUST
implement loop detections or limit the number of recursive
resolution steps.
- The loop detection MUST be effective even
+ <!-- FIXME The loop detection MUST be effective even
if a REDIRECT found in GNS triggers subsequent GNS lookups via
- the default operating system name resolution process.
+ the default operating system name resolution process.-->
</t>
</section>
<section anchor="gns2dns_processing" numbered="true" toc="default">
