[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: better dht wording
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: better dht wording |
Date: |
Sun, 19 Dec 2021 12:02:55 +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 e3dd5e3 better dht wording
e3dd5e3 is described below
commit e3dd5e32dbf1894395fb59230ac2ca04b3fd4d71
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sun Dec 19 12:02:52 2021 +0100
better dht wording
---
draft-schanzen-gns.xml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index f8d45d3..dd76c25 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -137,11 +137,12 @@
<t>
This document defines the normative wire format of resource records,
resolution processes,
cryptographic routines and security considerations for use by
implementors.
- GNS requires a distributed hash table (DHT) for record storage.
In general any API which allows storing a value under a key and
retrieving
- a value from the key can be used.
- Specification of the DHT is out of scope of this document.
- Possible implementation of such a service include <xref
target="RFC7363" />
+ 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).
+ Specification of such a DHT 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>
@@ -1114,8 +1115,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
<section anchor="publish" numbered="true" toc="default">
<name>Publishing Records</name>
<t>
- GNS resource records are published in a distributed hash table (DHT).
- We assume that a DHT provides two functions: GET(key) and
PUT(key,value).
+ We assume that a storage API provides two functions: GET(key) and
PUT(key,value).
In GNS, resource records are grouped by their respective labels,
encrypted and published together in a single resource records block
(RRBLOCK) in the DHT under a key "q": PUT(q, RRBLOCK).
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lsd0001] branch master updated: better dht wording,
gnunet <=