1 files changed, 9 insertions, 4 deletions

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index aab257d..9a10d19 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -1743,7 +1743,7 @@ q := SHA-512 (ZKDF-Public(zk, label))
          <dd>
            When publishing an RDATA block, the implementation MUST ensure that
            the size of the RDATA is a power of two
-           using the padding field. The field MUST be set to zero and MUST be
+           using the padding field. The field MAY be set to zero and MUST be
            ignored on receipt.
            As a special exception, record sets with (only) a zone delegation
            record type are never padded.
@@ -1950,14 +1950,19 @@ example.com = zk2
              REDIRECT, in which case the resolution concludes with the REDIRECT record.
              If the redirect name ends in ".+",
              resolution continues in GNS with the new name in the
-             current zone. Otherwise, the redirect name treated as a GNS name
-             and resolution restarts.
+             current zone.
+             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.
              <!-- 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
+             if a REDIRECT found in GNS triggers subsequent GNS lookups via
+             the default operating system name resolution process.
            </t>
          </section>
          <section anchor="gns2dns_processing" numbered="true" toc="default">