From 330e58ce4bf61592267e172df362ffefc5e14848 Mon Sep 17 00:00:00 2001 From: Ivan FB Date: Tue, 28 Apr 2026 00:59:05 +0200 Subject: [PATCH] rm retransmission section --- standards/application/reliable-channel-api.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/standards/application/reliable-channel-api.md b/standards/application/reliable-channel-api.md index 35ea2d0..bf48b57 100644 --- a/standards/application/reliable-channel-api.md +++ b/standards/application/reliable-channel-api.md @@ -20,7 +20,6 @@ editor: Logos Messaging Team * [Procedures](#procedures) * [Outgoing message processing](#outgoing-message-processing) * [Incoming message processing](#incoming-message-processing) - * [Retransmission](#retransmission) * [Rate limiting](#rate-limiting) * [Encryption](#encryption) * [The Reliable Channel API](#the-reliable-channel-api) @@ -114,13 +113,6 @@ When a chunk is received from the network, the implementation MUST process it in 2. **Apply [SDS](https://lip.logos.co/ift-ts/raw/sds.html)**: Deliver the chunk to the SDS layer, which emits acknowledgements and detects gaps. 3. **Reassemble**: Once all chunks for a message have been received, reassemble and emit a `reliable:message:received` event. -### Retransmission - -A certain Reliable Channel MUST retransmit unacknowledged chunks after `acknowledgementTimeoutMs`, -according to the [SDS](https://lip.logos.co/ift-ts/raw/sds.html) channel state, -up to `maxRetransmissions` times. -If a chunk is not acknowledged after all retransmission attempts, a `reliable:message:send-error` event MUST be emitted. - ### Rate limiting When `RateLimitConfig.enabled` is `true`, the implementation MUST space chunk transmissions