commit c58286d2cab2cc8c6f1998ba1b5ad8b4980aa845 parent 06c26eb5f46a20f23a10aa6042f4a5c68f3563f6 Author: Christian Grothoff <christian@grothoff.org> Date: Fri, 30 Jun 2023 23:02:33 +0200 clarify how remote storage should use expiration Diffstat:
| M | draft-schanzen-gns.xml | | | 4 | +++- |
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git 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