[lsd0001] branch master updated: add leho gns2dns hhandling

[gnunet]

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 ffc766c  add leho gns2dns hhandling
ffc766c is described below

commit ffc766ce63d67eb8500f413161d4329ef2800ca8
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Fri Dec 20 21:51:33 2019 +0900

    add leho gns2dns hhandling
---
 draft-schanzen-gns.html | 5 ++++-
 draft-schanzen-gns.txt  | 6 +++---
 draft-schanzen-gns.xml  | 3 +++
 3 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html
index 339aa53..3a810ae 100644
--- a/draft-schanzen-gns.html
+++ b/draft-schanzen-gns.html
@@ -2165,7 +2165,10 @@ async function addMetadata(){try{const 
e=document.styleSheets[0].cssRules;for(le
              support recursive resolution and MUST NOT delegate this to the
              authoritative DNS servers.
              The first successful recursive name resolution result
-             is returned to the client.<a href="#section-6.2.2-4" 
class="pilcrow">¶</a></p>
+             is returned to the client.
+             In addition, the resolver returns the queried DNS name as a LEHO
+             record (<a href="#gnsrecords_leho" class="xref">Section 3.4</a>) 
with a relative
+             expiration time of one hour.<a href="#section-6.2.2-4" 
class="pilcrow">¶</a></p>
 <p id="section-6.2.2-5">
       GNS resolvers SHOULD offer a configuration
       option to disable DNS processing to avoid information leakage
diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
index f462ead..b13f497 100644
--- a/draft-schanzen-gns.txt
+++ b/draft-schanzen-gns.txt
@@ -943,9 +943,9 @@ Internet-Draft             The GNU Name System             
November 2019
    As the DNS servers specified are possibly authoritative DNS servers,
    the GNS resolver MUST support recursive resolution and MUST NOT
    delegate this to the authoritative DNS servers.  The first successful
-   recursive name resolution result is returned to the client.
-
-
+   recursive name resolution result is returned to the client.  In
+   addition, the resolver returns the queried DNS name as a LEHO record
+   (Section 3.4) with a relative expiration time of one hour.
 
 
 
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 6fa6b15..be3c791 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -995,6 +995,9 @@
              authoritative DNS servers.
              The first successful recursive name resolution result
              is returned to the client.
+             In addition, the resolver returns the queried DNS name as a LEHO
+             record (<xref target="gnsrecords_leho" />) with a relative
+             expiration time of one hour.
            </t>
           <t>
             GNS resolvers SHOULD offer a configuration

-- 
To stop receiving notification emails like this one, please contact
address@hidden.