lsd0001

commit 865f4bbaa2073d12844862ac6ff59b8458739d67
parent b2e912c7968fa795d7001a6867c40f6a588d6ea3
Author: Christian Grothoff <christian@grothoff.org>
Date:   Fri,  4 Oct 2019 11:40:47 +0200

clarify GNS2DNS records

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

1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -192,7 +192,7 @@
   <t>In GNS, a delegation of a label to a zone is represented through a PKEY
     record. A PKEY resource record contains the public key of the zone to
     delegate to. A PKEY record MUST be the only record under a label. No other
-    records are allowed. The a PKEY DATA entry has the following format:</t>
+    records are allowed. A PKEY DATA entry has the following format:</t>
   <figure anchor="figure_pkeyrecord">
     <artwork name="" type="" align="left" alt=""><![CDATA[
       0     8     16    24    32    40    48    56
@@ -213,9 +213,19 @@
     in DNS followed by a DNS server. Both names are in the format defined in
     <xref target="RFC1034" /> for DNS names.
     If a resolver encounters a GNS2DNS record it is expected that it first
-    resolves the IP(s) of the DNS servers using DNS. Then, the encountered DNS
-    name is resolved by querying the name server(s).
-    The a GNS2DNS DATA entry has the following format:</t>
+    resolves the IP(s) of the DNS server(s).  GNS2DNS records MAY contain
+    numeric IPv4 or IPv6 addresses, allowing the resolver to skip this step.
+    The DNS server names may themselves be names in GNS or DNS.  If the
+    DNS server name ends in ".+", the rest of the name is to be interpreted
+    relative to the zone of the GNS2DNS record.
+    Then, the DNS name from the GNS2DNS record is appended
+    to the remainder of the name to be resolved, and
+    resolved by querying the name server(s).
+    Multiple
+    GNS2DNS records may be stored under the same label, in which case the
+    resolve MUST try all of them.  However, if multiple GNS2DNS records
+    are present, the DNS name MUST be identical for all of them.
+    A GNS2DNS DATA entry has the following format:</t>
   <figure anchor="figure_gns2dnsrecord">
     <artwork name="" type="" align="left" alt=""><![CDATA[
       0     8     16    24    32    40    48    56