gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0001] branch master updated: wording


From: gnunet
Subject: [lsd0001] branch master updated: wording
Date: Mon, 20 Dec 2021 11:59:54 +0100

This is an automated email from the git hooks/post-receive script.

martin-schanzenbach pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new 364f9da  wording
364f9da is described below

commit 364f9dae52c3cf9007482caa28ef8e0ff858b2f3
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Mon Dec 20 11:59:51 2021 +0100

    wording
---
 draft-schanzen-gns.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index eac69fb..e54f27b 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -1116,11 +1116,11 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
      <t>
        In general any API which allows storing a value under a key and 
retrieving
        a value from the key can be used by an implementation for record 
storage.
-       It is expected that a GNS implementation is using a distributed
-       hash table (DHT) in order to facilitate availability within a network
-       without the need of servers.
-       Specification of such a DHT is out of scope of this document but
-       possible existing implementations include <xref target="RFC7363" />,
+       It is expected that a GNS implementations use distributed or 
decentralized
+       storages such as distributed hash tables (DHT) in order to facilitate
+       availability within a network without the need of servers.
+       Specification of such a distributed or decentralized storage is out of
+       scope of this document but possible existing implementations include 
<xref target="RFC7363" />,
        <xref target="Kademlia" />, <xref target="R5N" /> or <xref 
target="Ipfs" />.
      </t>
      <t>

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]