commit f00eaa10867f74d08a5eadac13e10322cc8ec3fa
parent eef2e9b5d44bd0aa4af8719bdae28c601e25cdee
Author: Schanzenbach, Martin <mschanzenbach@posteo.de>
Date: Sun, 6 Oct 2019 04:32:59 +0200
revert nick 0-terminated
Diffstat:
3 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html
@@ -1394,7 +1394,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
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
+ resolver 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:<a href="#section-3.2-1" class="pilcrow">¶</a></p>
<div id="figure_gns2dnsrecord">
@@ -1466,7 +1466,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
PKEY <a href="#gnsrecords_pkey" class="xref">Section 3.1</a> record containing this zone's
public zone key.
A NICK resource record contains an UTF-8 string
- (0-terminated) representing the preferred label.
+ (not 0-terminated) representing the preferred label.
This string may NOT inlcude a ".".
This record SHOULD only be stored under the empty label "@".
A NICK DATA entry has the following format:<a href="#section-3.4-1" class="pilcrow">¶</a></p>
@@ -2113,7 +2113,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
00000000
- BLOCK :=
+ RRBLOCK :=
055cb070e05fe6de SIGNATURE
ad694a50e5b4dedd
b9fdcbdbae004f65
diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
@@ -296,7 +296,7 @@ Internet-Draft The GNU Name System July 2019
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
+ may be stored under the same label, in which case the resolver 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:
@@ -358,10 +358,10 @@ Internet-Draft The GNU Name System July 2019
indication on what label this zone prefers to be referred to. This
is a suggestion to other zones what label to use when creating a PKEY
Section 3.1 record containing this zone's public zone key. A NICK
- resource record contains an UTF-8 string (0-terminated) representing
- the preferred label. This string may NOT inlcude a ".". This record
- SHOULD only be stored under the empty label "@". A NICK DATA entry
- has the following format:
+ resource record contains an UTF-8 string (not 0-terminated)
+ representing the preferred label. This string may NOT inlcude a ".".
+ This record SHOULD only be stored under the empty label "@". A NICK
+ DATA entry has the following format:
0 8 16 24 32 40 48 56
+-----+-----+-----+-----+-----+-----+-----+-----+
@@ -922,7 +922,7 @@ Internet-Draft The GNU Name System July 2019
00000000
- BLOCK :=
+ RRBLOCK :=
055cb070e05fe6de SIGNATURE
ad694a50e5b4dedd
b9fdcbdbae004f65
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -351,7 +351,7 @@
PKEY <xref target="gnsrecords_pkey" /> record containing this zone's
public zone key.
A NICK resource record contains an UTF-8 string
- (0-terminated) representing the preferred label.
+ (not 0-terminated) representing the preferred label.
This string may NOT inlcude a ".".
This record SHOULD only be stored under the empty label "@".
A NICK DATA entry has the following format:
