[lsd0001] branch master updated: more revocation

[gnunet]

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 20e233e  more revocation
20e233e is described below

commit 20e233e73c5d2a93dcdcff4e2cb2d21c1392597a
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Wed Feb 2 19:50:23 2022 +0100

    more revocation
---
 draft-schanzen-gns.xml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 2fd775f..ff79b42 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -745,13 +745,13 @@ zTLD := zkl[126..129].zkl[63..125].zkl[0..62]
            (D'-D) * EPOCH * 1.1. The EPOCH is extended by
            10% in order to deal with unsynchronized clocks.
            The TTL added on top of the TIMESTAMP yields the
-           expiration date.</li>
-         <!-- FIXME: what if the TTL in the message disagrees with our 
calculations? What should be done?
-              What if floating point rounding errors cause a disagreement in 
TTL calculations?
-              IMO we should simply mandate that when FORWARDING a message, the 
sender should
-              use the TTL they calculated themselves. -->
-         <li>The current time MUST be between TIMESTAMP and
-           TIMESTAMP+TTL.</li>
+         expiration date.
+           Should the verifier calculate the TTL and find that it differs from
+           the field value, the verifier MUST continue and
+           use the calculated value when forwarding the revocation.
+         </li>
+         <li>The current time SHOULD be between TIMESTAMP and
+           TIMESTAMP+TTL. Implementations MAY process the revocation without 
validating this.</li>
        </ol>
      </section>
 

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