From 3249e7d6e8ac0e5e022259ee84dd08f4ecd2dc32 Mon Sep 17 00:00:00 2001 From: Sasha Date: Thu, 27 Jun 2024 02:08:09 +0200 Subject: [PATCH] up considerations: --- informational/req-res-reliability.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/informational/req-res-reliability.md b/informational/req-res-reliability.md index f057132..12532ae 100644 --- a/informational/req-res-reliability.md +++ b/informational/req-res-reliability.md @@ -5,6 +5,8 @@ category: Best Current Practice tags: [informational] editor: Oleksandr Kozlov contributors: +- Prem Chaitanya Prathi +- Danish Arora --- ## Abstract @@ -37,7 +39,9 @@ As a useful metric to define and implement for determining quality of provided s ### Light Push -In case sending message failed - node should try to re-send message after some interval. +- While sending message with Light Push - it is advised to use more than 1 peer in order to increase changes of delivering message. + +- If sending message is failed to all of the peers - node should try to re-send message after some interval and continue doing so while OK response is received. ### Filter @@ -51,13 +55,8 @@ In case sending message failed - node should try to re-send message after some i ## Security/Privacy Considerations -If there are none, this section MAY state that fact. -This section MAY contain additional relevant information, e.g. an explanation as to why there are no security consideration for the respective document. +None of the mentioned recommendations incur privacy or security tradeoffs and in some cases increase k-anonymity (e.g having unique peers for Filter subscriptions). ## Copyright Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). - -## References - -A list of references.