[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0003] branch master updated: Clarified some stuff in the sec message
From: |
gnunet |
Subject: |
[lsd0003] branch master updated: Clarified some stuff in the sec message |
Date: |
Mon, 14 Jun 2021 09:15:27 +0200 |
This is an automated email from the git hooks/post-receive script.
elias-summermatter pushed a commit to branch master
in repository lsd0003.
The following commit(s) were added to refs/heads/master by this push:
new 1c19f63 Clarified some stuff in the sec message
1c19f63 is described below
commit 1c19f6363ff42d501bc2f85991ef84b1b1f86388
Author: Elias Summermatter <elias.summermatter@seccom.ch>
AuthorDate: Mon Jun 14 09:12:32 2021 +0200
Clarified some stuff in the sec message
---
draft-summermatter-set-union.xml | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml
index a995743..85b47a4 100644
--- a/draft-summermatter-set-union.xml
+++ b/draft-summermatter-set-union.xml
@@ -1093,7 +1093,7 @@ hashSum | 0x0101 | 0x5151 | 0x5050 |
0x0000 |
the offered element is missing in the active peers set,
the active peer sends a <em><xref
target="messages_demand" format="title" /></em> message to the
passive peer. The demand needs to be added to a list of
unsatisfied demands.
- In case the received offer is for an element that is
already in the set of the peer, the offer MUST BE ignored. <!-- FIXME: what do
we do if the offer does not match any demand we ever issued? Is that OK? Worth
checking? @Christian: Demand? Demands come after offers.... You mean inquiry?
In this case no because its possible that we get offers without an inquiry
first... -->
+ In case the received offer is for an element that is
already in the set of the peer, the offer MUST BE ignored.
</dd>
<dt><em><xref target="messages_demand" format="title"
/></em> message:</dt>
<dd>
@@ -1910,17 +1910,22 @@ hashSum | 0x0101 | 0x5151 | 0x5050 |
0x0000 |
<section anchor="messages_sec_description" numbered="true"
toc="default">
<name>Description</name>
<t>
- The Strata Estimator can be compressed (the SE-Slices are
compressed, the header stays uncompressed) with gzip as
+ The Strata Estimator can be compressed with gzip as
described in <xref target="RFC1951"/> to improve
performance. This can be recognized
by the different message type number from <xref
target="gana" format="title" />.
</t>
- <t>
- Since the content of the message is the same as the
uncompressed Strata Estimator, the details
- are not repeated here. For details see section <xref
target="messages_se" format="counter" />.
- </t>
- <!-- FIXME: keep the 'structure' subsection , and also needs
to clarify WHAT is being @Christian but then the Structure section is just a
copy of the one above? Isn't this pointless?
- compressed, and should cite the RFC on the compression
method used! (IIRC gzip deflate
- mode); note that the header is not subject to
compression, so this must be clarified!) -->
+ <section anchor="messages_se_structure" numbered="true"
toc="default">
+ <name>Structure</name>
+ <t>
+ The key difference between the compressed and the
uncompressed Strata Estimator is that the
+ SE slices are compressed with gzip (<xref
target="RFC1951"/>) in the compressed SE.
+ But the header remains uncompressed with both.
+ </t>
+ <t>
+ Since the content of the message is the same as
the uncompressed Strata Estimator, the details
+ are not repeated here. For details see section
<xref target="messages_se" format="counter" />.
+ </t>
+ </section>
</section>
</section>
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lsd0003] branch master updated: Clarified some stuff in the sec message,
gnunet <=