[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: deletion
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: deletion |
Date: |
Wed, 22 Dec 2021 18:13:16 +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 a17233b deletion
a17233b is described below
commit a17233b7a12ad1c0f5313cc2ad961e1f8b8c851e
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Wed Dec 22 18:13:11 2021 +0100
deletion
---
draft-schanzen-gns.xml | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 9dd5e63..c732a64 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -1412,6 +1412,15 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
PUT(key,value)
GET(key) -> value
]]></artwork>
+ <t>
+ There is no explicit delete function as the deletion of a non-expired
+ record would require a revocation of the record.
+ In GNS, zones can only be revoked as a whole. Records automatically
+ expire and it is under the discretion of the storage as to when to
delete
+ the record. The GNS implementation MUST NOT publish expired resource
+ records. Any GNS resolver MUST discard expired records returned from
+ the storage.
+ </t>
<t>
Resource records are grouped by their respective labels,
encrypted and published together in a single resource records block
--
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: deletion,
gnunet <=