commit a17233b7a12ad1c0f5313cc2ad961e1f8b8c851e parent 925f114801aa6a8cc0a483c251dfa8faa3c3d116 Author: Martin Schanzenbach <schanzen@gnunet.org> Date: Wed, 22 Dec 2021 18:13:11 +0100 deletion Diffstat:
| M | draft-schanzen-gns.xml | | | 9 | +++++++++ |
1 file changed, 9 insertions(+), 0 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml @@ -1413,6 +1413,15 @@ 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 (RRBLOCK) in the storage under a key q: PUT(q, RRBLOCK).