diff options
author | Christian Grothoff <christian@grothoff.org> | 2023-06-30 22:29:41 +0200 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2023-06-30 22:29:41 +0200 |
commit | 36a567839e0609e432392676dd99d8c5342fdce0 (patch) | |
tree | c0087ada43afbf152b1b1e28416b63fb3695739a /draft-schanzen-gns.xml | |
parent | 25fba13862614191da5c6b00b33f1f6689a90255 (diff) | |
download | lsd0001-36a567839e0609e432392676dd99d8c5342fdce0.tar.gz lsd0001-36a567839e0609e432392676dd99d8c5342fdce0.zip |
use 'block' consisently, and not sometimes 'value'
Diffstat (limited to 'draft-schanzen-gns.xml')
-rw-r--r-- | draft-schanzen-gns.xml | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml index 980c601..b8d97d7 100644 --- a/draft-schanzen-gns.xml +++ b/draft-schanzen-gns.xml | |||
@@ -1763,31 +1763,31 @@ S-Decrypt(zk,label,expiration,ciphertext): | |||
1763 | <section anchor="publish" numbered="true" toc="default"> | 1763 | <section anchor="publish" numbered="true" toc="default"> |
1764 | <name>Record Encoding for Remote Storage</name> | 1764 | <name>Record Encoding for Remote Storage</name> |
1765 | <t> | 1765 | <t> |
1766 | Any API which allows storing a value under a 512-bit key and retrieving | 1766 | Any API which allows storing a block under a 512-bit key and retrieving |
1767 | one or more values from the key can be used by an implementation for record storage. | 1767 | one or more blocks from a key can be used by an implementation for remote storage. |
1768 | To be useful, the API <bcp14>MUST</bcp14> permit storing at least 176 byte values | 1768 | To be useful, the API <bcp14>MUST</bcp14> permit storing at least 176 byte blocks |
1769 | to be able to support the defined zone delegation record encodings, | 1769 | to be able to support the defined zone delegation record encodings, |
1770 | and <bcp14>SHOULD</bcp14> allow at least 1024 byte values. | 1770 | and <bcp14>SHOULD</bcp14> allow at least 1024 byte blocks. |
1771 | In the following, it is assumed that an implementation realizes two | 1771 | In the following, it is assumed that an implementation realizes two |
1772 | procedures on top of a storage: | 1772 | procedures on top of a storage: |
1773 | </t> | 1773 | </t> |
1774 | <artwork name="" type="" align="left" alt=""><![CDATA[ | 1774 | <artwork name="" type="" align="left" alt=""><![CDATA[ |
1775 | PUT(key,value) | 1775 | PUT(key,block) |
1776 | GET(key) -> value | 1776 | GET(key) -> block |
1777 | ]]></artwork> | 1777 | ]]></artwork> |
1778 | <t> | 1778 | <t> |
1779 | There is no explicit delete function as the deletion of a non-expired | 1779 | There is no mechanism to explicitly delete individual blocks from remote storage. |
1780 | record would require a revocation of the record. | 1780 | However, blocks in remote storage include an expiration time |
1781 | In GNS, zones can only be revoked as a whole. Records automatically | 1781 | and it is under the discretion of the storage implementation as to when to |
1782 | expire and it is under the discretion of the storage as to when to delete | 1782 | actually delete an expired block. |
1783 | the record. The GNS implementation <bcp14>MUST NOT</bcp14> publish expired resource | 1783 | The GNS implementation <bcp14>MUST NOT</bcp14> include expired resource |
1784 | records. Any GNS resolver <bcp14>MUST</bcp14> discard expired records returned from | 1784 | records in blocks. Any GNS resolver <bcp14>MUST</bcp14> disregard expired records returned from |
1785 | the storage. | 1785 | remote storage. |
1786 | </t> | 1786 | </t> |
1787 | <t> | 1787 | <t> |
1788 | Resource records are grouped by their respective labels, | 1788 | Resource records are grouped by their respective labels, |
1789 | encrypted and published together in a single records block | 1789 | encrypted and published together in a single records block |
1790 | (RRBLOCK) in the storage under a storage key q as illustrated in <xref target="figure_storage_publish"/>. | 1790 | (RRBLOCK) in the storage under a storage key q as illustrated in <xref target="figure_storage_publish"/>. |
1791 | The implementation <bcp14>MUST</bcp14> use the PUT storage procedure in order to update the zone contents accordingly. | 1791 | The implementation <bcp14>MUST</bcp14> use the PUT storage procedure in order to update the zone contents accordingly. |
1792 | </t> | 1792 | </t> |
1793 | <figure anchor="figure_storage_publish" title="Management and publication of local zones in the distributed storage."> | 1793 | <figure anchor="figure_storage_publish" title="Management and publication of local zones in the distributed storage."> |
@@ -1823,7 +1823,7 @@ GET(key) -> value | |||
1823 | The required knowledge of both zone key and label in combination | 1823 | The required knowledge of both zone key and label in combination |
1824 | with the similarly derived symmetric secret keys and blinded zone keys | 1824 | with the similarly derived symmetric secret keys and blinded zone keys |
1825 | ensure query privacy (see <xref target="RFC8324"/>, Section 3.5). | 1825 | ensure query privacy (see <xref target="RFC8324"/>, Section 3.5). |
1826 | The storage Key derivation and records | 1826 | The storage key derivation and records |
1827 | block creation using is specified in the following sections and a high-level | 1827 | block creation using is specified in the following sections and a high-level |
1828 | overview is illustrated in <xref target="figure_storage_derivations"/>. | 1828 | overview is illustrated in <xref target="figure_storage_derivations"/>. |
1829 | </t> | 1829 | </t> |
@@ -3739,7 +3739,7 @@ Host: 000G0037FH3QTBCK15Y8BCCNRVWPV17ZC7TSGB1C9ZG2TPGHZVFV1GMG3W | |||
3739 | <t> | 3739 | <t> |
3740 | This table defines the encode and decode symbols for a given | 3740 | This table defines the encode and decode symbols for a given |
3741 | symbol value. | 3741 | symbol value. |
3742 | Each symbol value is 5 bit. | 3742 | Each symbol value encodes 5 bits. |
3743 | It can be used to implement the encoding by reading it as: | 3743 | It can be used to implement the encoding by reading it as: |
3744 | A symbol "A" or "a" is decoded to a 5 bit value 10 when decoding. | 3744 | A symbol "A" or "a" is decoded to a 5 bit value 10 when decoding. |
3745 | A 5 bit block with a value of 18 is encoded to the character "J" when encoding. | 3745 | A 5 bit block with a value of 18 is encoded to the character "J" when encoding. |