commit 33b7c4306e5bc8ea695b7e265136c9f42bfc9fe0
parent 36a567839e0609e432392676dd99d8c5342fdce0
Author: Christian Grothoff <christian@grothoff.org>
Date: Fri, 30 Jun 2023 22:33:06 +0200
move section title storage key to where discussion of storage key begins
Diffstat:
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -1785,10 +1785,12 @@ GET(key) -> block
remote storage.
</t>
<t>
- Resource records are grouped by their respective labels,
+ All resource records from the same zone sharing the same label are
encrypted and published together in a single records block
- (RRBLOCK) in the storage under a storage key q as illustrated in <xref target="figure_storage_publish"/>.
- The implementation <bcp14>MUST</bcp14> use the PUT storage procedure in order to update the zone contents accordingly.
+ (RRBLOCK) in the remote storage under a key q as illustrated
+ in <xref target="figure_storage_publish"/>.
+ The implementation <bcp14>MUST</bcp14> use the PUT storage procedure
+ to update the zone contents accordingly.
</t>
<figure anchor="figure_storage_publish" title="Management and publication of local zones in the distributed storage.">
<artwork name="" type="" align="left" alt=""><![CDATA[
@@ -1817,6 +1819,8 @@ GET(key) -> block
+---------+ |
]]></artwork>
</figure>
+ <section anchor="blinding" numbered="true" toc="default">
+ <name>The Storage Key</name>
<t>
The storage key is derived from the zone key and the respective
label of the contained records.
@@ -1854,8 +1858,6 @@ GET(key) -> block
+------+ +-------------+
]]></artwork>
</figure>
- <section anchor="blinding" numbered="true" toc="default">
- <name>The Storage Key</name>
<t>
Given a label, the storage key q is derived as follows:
</t>