gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0001] branch master updated: more revocationing #2


From: gnunet
Subject: [lsd0001] branch master updated: more revocationing #2
Date: Mon, 21 Feb 2022 16:03:14 +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 bb51da0  more revocationing #2
bb51da0 is described below

commit bb51da0d5d12a1bb213dece7aa9e8cd74c1c710b
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Mon Feb 21 16:03:10 2022 +0100

    more revocationing #2
---
 draft-schanzen-gns.xml | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index a02251c..eddb298 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -785,22 +785,22 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
          Stale revocations <bcp14>MAY</bcp14> be discarded.
        </t>
        <t>
-         Verified revocations <bcp14>SHOULD</bcp14> be cached locally.
-         An implementation without a local revocations cache will be unable
-         to effectively process zone revocations.
-         The implementation <bcp14>MAY</bcp14> evict revocations from the local
-         cache at any time using an eviction strategy.
+         Verified revocations <bcp14>MUST</bcp14> be stored locally.
+         The implementation <bcp14>MAY</bcp14> evict stale revocations from the
+         local store at any time.
        </t>
        <t>
          Implementations <bcp14>MUST</bcp14> forward received revocations to
          other peers if they are valid and not stale.
-         Should the calculated validity period differs from the TTL field 
value,
+         Should the calculated validity period differ from the TTL field value,
          the calculated value <bcp14>MUST</bcp14> be used as TTL field value
          when forwarding the revocation message.
-         Any valid revocation MAY be used during delegation record
+         Any valid revocation MAY be considered during delegation record
          processing (<xref target="delegation_processing"/>).
-         Implementations <bcp14>MAY</bcp14> use stale but otherwise valid
-         revocations and <bcp14>MAY</bcp14> forward them to other peers.
+         Systems may disagree on the current time, so implementations
+         <bcp14>MAY</bcp14> use stale but otherwise valid
+         revocations but <bcp14>SHOULD NOT</bcp14> forward them to other peers.
+         Forwarded stale revocations may be discarded.
        </t>
      </section>
 

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]