[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: padding tombston => record
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: padding tombston => record |
Date: |
Sat, 19 Feb 2022 17:03:45 +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 47300a1 padding tombston => record
47300a1 is described below
commit 47300a16e5cb219bfdf8a19f1d4d042d3a349ae7
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sat Feb 19 17:03:40 2022 +0100
padding tombston => record
---
draft-schanzen-gns.xml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 4e1068b..9dad73a 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -2373,9 +2373,10 @@ NICK: john (Supplemental)
by a single microsecond even if the user did not request a change.
In case of deletion of all resource records under a label, the
implementation MUST keep track of the last absolute expiration time
- of the last published resource block. Implementations MAY use a
PADDING
- record as a tombstone that preserves the last absolute expiration
time,
- but then MUST take care to not publish a block with just a PADDING
record.
+ of the last published resource block. Implementations MAY define
+ and use a special record type as a tombstone that preserves the last
+ absolute expiration time, but then MUST take care to not publish a
+ block with this record.
When new records are added under this label later, the
implementation
MUST ensure that the expiration times are after the last published
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: padding tombston => record,
gnunet <=