commit dcb3ce77a601bbbab8321ddbd3a7f022464b7c54
parent f906fcff9d8ff6a3b475096d06295ae22d745cf5
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Wed, 9 Mar 2022 21:22:51 +0100
typos
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -567,8 +567,8 @@ ztype||zkey := Base32GNS-Decode(zTLD)
the least significant bytes in the leftmost label of the resulting string. This allows the
resolver to determine the ztype and zTLD length from the rightmost
label and to subsequently determine how many labels the zTLD should span.
- A GNS implementation <bcp14>MUST</bcp14> support the division of zTLD in DNS compatible
- label lengths.
+ A GNS implementation <bcp14>MUST</bcp14> support the division of zTLDs
+ in DNS compatible label lengths.
For example, assuming a zTLD of 130 characters, the division is:
</t>
<!-- FIXME: Is this really really necessary? Really? -->
@@ -849,7 +849,7 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
evict then from the local store at any time.
</t>
<t>
- Implementations <bcp14>MUST</bcp14> broadcast received revocations to
+ Implementations <bcp14>MUST</bcp14> broadcast received revocations
if they are valid and not stale.
Should the calculated validity period differ from the TTL field value,
the calculated value <bcp14>MUST</bcp14> be used as TTL field value
