From 59e225dc4ab0baabc4fea87082ff1dd2215c5936 Mon Sep 17 00:00:00 2001 From: Sasha Date: Tue, 9 Jul 2024 23:58:38 +0200 Subject: [PATCH] add regular pings to Filter --- informational/req-res-reliability.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/informational/req-res-reliability.md b/informational/req-res-reliability.md index 140b2a6..2ddbdf1 100644 --- a/informational/req-res-reliability.md +++ b/informational/req-res-reliability.md @@ -91,6 +91,12 @@ Our advice to do periodic Store queries once per 30 seconds. ### Filter +#### Regular pings +To ensure that subscription is maintained by a service node and not closed - light node should do recurring [pings](https://github.com/vacp2p/rfc-index/blob/7b443c1aab627894e3f22f5adfbb93f4c4eac4f6/waku/standards/core/12/filter.md#subscriber_ping). +Our advice for light node to send ping requests once per minute. +In case light node does not receive OK response or it times out 3 times - such service node should be replaced as part of maintenance of [pool of reliable service nodes](./req-res-reliability.md#pool-of-reliable-service-nodes). +Right after such replace light node must create new subscription to newly connected service node as described in [Filter specification](https://github.com/vacp2p/rfc-index/blob/7b443c1aab627894e3f22f5adfbb93f4c4eac4f6/waku/standards/core/12/filter.md). + - To decrease chances of missing messages a light node can initiate more than one subscription through Filter protocol to the same content topic to different service nodes and filter out duplicates. This will increase bandwidth consumption and would depend on the information exchanged under content topic in use.