diff options
author | Elias Summermatter <elias.summermatter@seccom.ch> | 2021-06-16 13:20:49 +0200 |
---|---|---|
committer | Elias Summermatter <elias.summermatter@seccom.ch> | 2021-06-16 13:20:49 +0200 |
commit | ad0ed3e3d108fe618732c65dc25cdda9e87fe4ee (patch) | |
tree | 40cd03bda0a9313c934c29b4364548ef8d9c1d83 | |
parent | 3217f39e11167ccf51517996642001c9ef3ce3af (diff) | |
download | lsd0003-ad0ed3e3d108fe618732c65dc25cdda9e87fe4ee.tar.gz lsd0003-ad0ed3e3d108fe618732c65dc25cdda9e87fe4ee.zip |
Corrected some gramar
-rw-r--r-- | draft-summermatter-set-union.xml | 36 |
1 files changed, 15 insertions, 21 deletions
diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml index 10a5ce0..270bad2 100644 --- a/draft-summermatter-set-union.xml +++ b/draft-summermatter-set-union.xml | |||
@@ -2542,25 +2542,23 @@ peers set +---------+ +---------+ +---------+ | |||
2542 | ===>: Always answer needed. | 2542 | ===>: Always answer needed. |
2543 | ]]></artwork> | 2543 | ]]></artwork> |
2544 | </figure> | 2544 | </figure> |
2545 | <!-- CORRECT --> | ||
2546 | <t> | 2545 | <t> |
2547 | In the message control flow its important to ensure that no duplicated message are received | 2546 | In the message control flow its important to ensure that no duplicated messages are received |
2548 | (Except inquiries where collisions are possible) and only messages are received which are compliant | 2547 | (Except inquiries where collisions are possible) and only messages are received which are compliant |
2549 | with the flow in <xref target="security_generic_functions_mfc_chain" format="default" />. | 2548 | with the flow in <xref target="security_generic_functions_mfc_chain" format="default" />. |
2550 | To link messages the SHA-512 element hashes that are part of all messages except in the | 2549 | To link messages the SHA-512 element hashes, that are part of all messages, except in the |
2551 | <em><xref target="messages_inquiry" format="title" /></em> message can be used. | 2550 | <em><xref target="messages_inquiry" format="title" /></em> messages, can be used. |
2552 | To link an <em><xref target="messages_inquiry" format="title" /></em> message to an | 2551 | To link an <em><xref target="messages_inquiry" format="title" /></em> message to an |
2553 | <em><xref target="messages_offer" format="title" /></em> message | 2552 | <em><xref target="messages_offer" format="title" /></em> message |
2554 | the SHA-512 hash from the offer has to be salted and converted to the IBF-Key (as described in | 2553 | the SHA-512 hash from the offer has to be salted and converted to the IBF-Key (as described in |
2555 | <xref target="ibf_format_id_generation_pseudo_code" format="default" />) this then can | 2554 | <xref target="ibf_format_id_generation_pseudo_code" format="default" />). The IBF-Key can |
2556 | be matched against the received <em><xref target="messages_inquiry" format="title" /></em> message. | 2555 | be matched with the received <em><xref target="messages_inquiry" format="title" /></em> message. |
2557 | </t> | 2556 | </t> |
2558 | <t> | 2557 | <t> |
2559 | In the end of the set reconciliation operation after receiving and sending the | 2558 | At the end of the set reconciliation operation after receiving and sending the |
2560 | <em><xref target="messages_done" format="title" /></em> message it should be checked | 2559 | <em><xref target="messages_done" format="title" /></em> message, it should be checked |
2561 | that all demands have been satisfied and all elements have been received. | 2560 | that all demands have been satisfied and all elements have been received. |
2562 | </t> | 2561 | </t> |
2563 | <!-- CORRECT --> | ||
2564 | <t> | 2562 | <t> |
2565 | This is based on <xref target="byzantine_fault_tolerant_set_reconciliation" format="default"/>, section 5.3 (Message Control Flow). | 2563 | This is based on <xref target="byzantine_fault_tolerant_set_reconciliation" format="default"/>, section 5.3 (Message Control Flow). |
2566 | </t> | 2564 | </t> |
@@ -2748,20 +2746,18 @@ END FUNCTION | |||
2748 | abort the protocol if its resource limits are likely to be | 2746 | abort the protocol if its resource limits are likely to be |
2749 | exceeded, or if the size is implausible for the given operation. | 2747 | exceeded, or if the size is implausible for the given operation. |
2750 | </t> | 2748 | </t> |
2751 | <!-- CORRECT --> | ||
2752 | <t> | 2749 | <t> |
2753 | It needs to be checked that that the offset (message field "OFFSET") | 2750 | It needs to be checked that the offset (message field "OFFSET") |
2754 | for every received <em><xref target="messages_ibf" format="title" /></em> message | 2751 | for every received <em><xref target="messages_ibf" format="title" /></em> message |
2755 | is strictly monotonic increasing and is a multiple of the MAX_BUCKETS_PER_MESSAGE | 2752 | is strictly monotonic increasing and is a multiple of the MAX_BUCKETS_PER_MESSAGE |
2756 | defined in the <xref target="constants" format="title" /> section otherwise the | 2753 | defined in the <xref target="constants" format="title" /> section, otherwise the |
2757 | connection MUST be aborted. | 2754 | connection MUST be aborted. |
2758 | </t> | 2755 | </t> |
2759 | <t> | 2756 | <t> |
2760 | An other sanity check is to ensure that the "OFFSET" message field never | 2757 | An other sanity check is to ensure that the "OFFSET" message field never |
2761 | is a higher than the "IBF SIZE" field in the <em><xref target="messages_ibf" format="title" /></em> | 2758 | is higher than the "IBF SIZE" field in the <em><xref target="messages_ibf" format="title" /></em> |
2762 | message. | 2759 | message. |
2763 | </t> | 2760 | </t> |
2764 | <!-- CORRECT --> | ||
2765 | </dd> | 2761 | </dd> |
2766 | <dt><xref target="messages_ibf_last" format="title" /></dt> | 2762 | <dt><xref target="messages_ibf_last" format="title" /></dt> |
2767 | <dd> | 2763 | <dd> |
@@ -2771,22 +2767,20 @@ END FUNCTION | |||
2771 | should conclude the transmission of the IBF and a change to the <strong>Active Decoding</strong> | 2767 | should conclude the transmission of the IBF and a change to the <strong>Active Decoding</strong> |
2772 | phase should be ensured. | 2768 | phase should be ensured. |
2773 | </t> | 2769 | </t> |
2774 | <!-- CORRECT --> | ||
2775 | <t> | 2770 | <t> |
2776 | To verify that all IBFs have been received a simple validation can be made | 2771 | To verify that all IBFs have been received, a simple validation can be made. |
2777 | the number of buckets in the <em><xref target="messages_ibf_last" format="title" /></em> message | 2772 | The number of buckets in the <em><xref target="messages_ibf_last" format="title" /></em> message |
2778 | added to the value in the message OFFSET field should always be equal to the "IBF SIZE". | 2773 | added to the value in the message OFFSET field should always be equal to the "IBF SIZE". |
2779 | </t> | 2774 | </t> |
2780 | <t> | 2775 | <t> |
2781 | Further plausibility checks can be made. One is to ensure that after each active/passive | 2776 | Further plausibility checks can be made. One is to ensure that after each active/passive |
2782 | switch the IBF can never more than double in size. An other plausibility check is | 2777 | switch the IBF can never be more than double in size. Another plausibility check is |
2783 | is that an IBF probably never will be bigger than the byzantine upperbound multiplied by two. | 2778 | that an IBF probably never will be larger than the byzantine upperbound multiplied by two. |
2784 | The third plausibility check is to take successfully decoded IBF keys (received offers and demands) | 2779 | The third plausibility check is to take successfully decoded IBF keys (received offers and demands) |
2785 | into account and validating the size of the received IBF with the in <xref target="performance_formula_ibf_parameters_code" format="default" /> | 2780 | into account and to validate the size of the received IBF with the in <xref target="performance_formula_ibf_parameters_code" format="default" /> |
2786 | described function get_next_ibf_size(). If any of these three checks fail the operation | 2781 | described function get_next_ibf_size(). If any of these three checks fail the operation |
2787 | must be aborted. | 2782 | must be aborted. |
2788 | </t> | 2783 | </t> |
2789 | <!-- CORRECT --> | ||
2790 | </dd> | 2784 | </dd> |
2791 | </dl> | 2785 | </dl> |
2792 | </section> | 2786 | </section> |