commit 52d50e7eb48fad3b990486243ec621322e901ce5
parent 5b68667dc8e9e04b0aa01e46879920414afb7213
Author: Elias Summermatter <elias.summermatter@seccom.ch>
Date: Mon, 21 Dec 2020 12:41:28 +0100
Added some Mode operation text
Diffstat:
1 file changed, 13 insertions(+), 20 deletions(-)
diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml
@@ -376,9 +376,6 @@
by the expected number of elements (E) in the remaining unencoded IBF's (C*E=[estimated count of objects]).
If no of the SE decoded choose a smaller stratum or try a other hash function.
- ### Wie berechne ich den strata estimator Decodieren wie ist die formal um die
- ### 2^n*k k=elemente (Durchnitt duch alle die estimatoren) Systamatischer pyas
- ### Wie ist die formel sein?
</t>
</section>
</section>
@@ -400,26 +397,18 @@
</t>
<t>
- The initiating peer starts in the "Expect SE" state and the receiving peer starts in the "Expecting IBF" state. ### Afer connectiong to the server the initaiting peer is in state
- In a first step of the protocol the initiating peer opens a connection to the receiving peer, requests a Strata ### Anpassen nach state maschine
- Estimator from the receiving peer. The receiving peer answers with the Strata Estimator. ### Wie unten nach states gliederm
- After the initiating peer has received the Strata Estimator he decides which sync mode is optimal for the
- the estimated set difference.
- To ensure that ...... the difference is multiplied by 1.5 if there are more than 200 elements differences between the sets (WHY? line 1398). ### Tradeoff faktoren nach oben
- The Full Synchronisation Mode is used if the flag to force full sync is set, the estimated difference between the two sets is bigger
- than 25% or the set size of the receiving peer is zero. Otherwise the Individual Element Synchronisation Mode is used.
-
- the tradeoff between the two is explained in 5.3 ########## Ausformulieren
-
+ The initiating peer is initially in the <strong>Initiating Connection</strong> state and the receiving peer in the <strong>Expecting Connection</strong>
+ state. The first step of the protocol for the initiating peer is to send an <em>Operation Request</em> to the receiving peer and
+ change into <strong>Expect SE</strong> state. After receiving the <em>Operation Request</em> the receiving peer changes in <strong>Expecting IBF"</strong> state and answers with the
+ Strata Estimator (<em>SE</em>) . After the initiating peer has received the Strata Estimator the initiating peer decides
+ with heuristics which operation mode is best fitted for the the estimated set difference and the environment.
+ The detailed tradeoff between the "Full Synchronisation Mode" and the "Individual Element Synchronisation Mode"
+ is explained in the section "Combined Mode".
</t>
<section anchor="modeofoperation_full-sync-client-with-bigger-set" numbered="true" toc="default">
<name>Full Synchronisation Mode</name>
<t>
- The decision to enter the full sync mode ... en
- </t>
-
- <t>
In full synchronisation mode, if the set of the initiating peer is bigger than the set of the receiving peer, the initiating ### Nachrichten und states ander darstellen
peer sends a "Request Full" message and change from "Expecting SE" in "Full Receiving" State. ### Refferenz auf nachrichten und all elements = message type anstat beschreibung
In all other cases the initiating peer sends all set elements to the other peer
@@ -449,8 +438,12 @@
<t>--- TEXT HERE ---</t>
</section>
<section anchor="modeofoperation_combined-mode" numbered="true" toc="default">
- <name>Combined mode</name>
- <t>--- TEXT HERE ---</t>
+ <name>Combined Mode</name>
+ <t>
+ To ensure that ...... the difference is multiplied by 1.5 if there are more than 200 elements differences between the sets (WHY? line 1398).
+ The Full Synchronisation Mode is used if the flag to force full sync is set, the estimated difference between the two sets is bigger
+ than 25% or the set size of the receiving peer is zero. Otherwise the Individual Element Synchronisation Mode is used.
+ </t>
</section>
</section>
