diff options
| author | Martin Schanzenbach <schanzen@gnunet.org> | 2022-03-09 21:22:51 +0100 |
|---|---|---|
| committer | Martin Schanzenbach <schanzen@gnunet.org> | 2022-03-09 21:22:51 +0100 |
| commit | dcb3ce77a601bbbab8321ddbd3a7f022464b7c54 (patch) | |
| tree | ff1fe667148338f723d727a423c8a2987ec996c2 | |
| parent | f906fcff9d8ff6a3b475096d06295ae22d745cf5 (diff) | |
| download | lsd0001-dcb3ce77a601bbbab8321ddbd3a7f022464b7c54.tar.gz lsd0001-dcb3ce77a601bbbab8321ddbd3a7f022464b7c54.zip | |
typos
| -rw-r--r-- | draft-schanzen-gns.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml index 4b08e76..91abda4 100644 --- a/draft-schanzen-gns.xml +++ b/draft-schanzen-gns.xml | |||
| @@ -567,8 +567,8 @@ ztype||zkey := Base32GNS-Decode(zTLD) | |||
| 567 | the least significant bytes in the leftmost label of the resulting string. This allows the | 567 | the least significant bytes in the leftmost label of the resulting string. This allows the |
| 568 | resolver to determine the ztype and zTLD length from the rightmost | 568 | resolver to determine the ztype and zTLD length from the rightmost |
| 569 | label and to subsequently determine how many labels the zTLD should span. | 569 | label and to subsequently determine how many labels the zTLD should span. |
| 570 | A GNS implementation <bcp14>MUST</bcp14> support the division of zTLD in DNS compatible | 570 | A GNS implementation <bcp14>MUST</bcp14> support the division of zTLDs |
| 571 | label lengths. | 571 | in DNS compatible label lengths. |
| 572 | For example, assuming a zTLD of 130 characters, the division is: | 572 | For example, assuming a zTLD of 130 characters, the division is: |
| 573 | </t> | 573 | </t> |
| 574 | <!-- FIXME: Is this really really necessary? Really? --> | 574 | <!-- FIXME: Is this really really necessary? Really? --> |
| @@ -849,7 +849,7 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62] | |||
| 849 | evict then from the local store at any time. | 849 | evict then from the local store at any time. |
| 850 | </t> | 850 | </t> |
| 851 | <t> | 851 | <t> |
| 852 | Implementations <bcp14>MUST</bcp14> broadcast received revocations to | 852 | Implementations <bcp14>MUST</bcp14> broadcast received revocations |
| 853 | if they are valid and not stale. | 853 | if they are valid and not stale. |
| 854 | Should the calculated validity period differ from the TTL field value, | 854 | Should the calculated validity period differ from the TTL field value, |
| 855 | the calculated value <bcp14>MUST</bcp14> be used as TTL field value | 855 | the calculated value <bcp14>MUST</bcp14> be used as TTL field value |