[lsd0001] branch master updated: clarify how remote storage should use expiration

[gnunet]

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

grothoff pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new c58286d  clarify how remote storage should use expiration
c58286d is described below

commit c58286d2cab2cc8c6f1998ba1b5ad8b4980aa845
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Jun 30 23:02:33 2023 +0200

    clarify how remote storage should use expiration
---
 draft-schanzen-gns.xml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 9282942..347f7d3 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -1784,7 +1784,9 @@ GET(key) -> block
      <t>
        There is no mechanism to explicitly delete individual blocks from 
remote storage.
        However, blocks include an EXPIRATION field which guides remote
-       storage implementations to decide when to delete blocks.
+       storage implementations to decide when to delete blocks.  Given 
multiple blocks
+       for the same key, remote storage implementations <bcp14>SHOULD</bcp14> 
try
+       to preserve and return the block with the largest EXPIRATION value.
      </t>
      <t>
        All resource records from the same zone sharing the same label are

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