lsd0001

commit a1516799e727e38b154a76f0c43dc0a34cc5e597
parent 9c5368e062c5886bc50166704b6d87714152fe68
Author: Christian Grothoff <christian@grothoff.org>
Date:   Fri, 30 Jun 2023 18:30:17 +0200

use 'remote storage' to stick with terminology in figure

Diffstat:
M
draft-schanzen-gns.xml
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -390,7 +390,7 @@ example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884
        </t>
        <t>
          Zone contents are encrypted and signed
-         before being published in a distributed key-value storage (see <xref target="publish"/>)
+         before being published in a remote key-value storage (see <xref target="publish"/>)
          as illustrated in <xref target="figure_arch_publish"/>.
          In this process, unique zone identification is hidden from the network
          through the use of key blinding.
@@ -403,7 +403,7 @@ example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884
          Specifically, the zone owner can derive blinded private keys for each record
          set published under a label, and a
          resolver can derive the corresponding blinded public keys.
-         It is expected that GNS implementations use distributed or decentralized
+         It is expected that GNS implementations use decentralized remote
          storages such as distributed hash tables (DHT) in order to facilitate
          availability within a network without the need for dedicated infrastructure.
          Specification of such a distributed or decentralized storage is out of