From 27324bb90b9f968964a22037527c7af3108c5000 Mon Sep 17 00:00:00 2001 From: Ivan FB <128452529+Ivansete-status@users.noreply.github.com> Date: Tue, 28 Apr 2026 00:14:48 +0200 Subject: [PATCH] Update standards/application/reliable-channel-api.md Co-authored-by: Igor Sirotin --- standards/application/reliable-channel-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/application/reliable-channel-api.md b/standards/application/reliable-channel-api.md index 85e169c..2b199d2 100644 --- a/standards/application/reliable-channel-api.md +++ b/standards/application/reliable-channel-api.md @@ -53,7 +53,7 @@ The [MESSAGING-API](/standards/application/messaging-api.md) provides peer-to-pe but does not provide high end-to-end delivery guarantees from sender to recipient. This API addresses that gap by introducing: -- **[SEGMENTATION-API](/standards/application/segmentation-api.md)** to handle large messages exceeding network size limits. +- **[SEGMENTATION-API](/standards/application/segmentation.md)** to handle large messages exceeding network size limits. - **[SDS](https://lip.logos.co/ift-ts/raw/sds.html)** to provide causal-history-based end-to-end acknowledgement and retransmission. - **Rate Limit Manager** to comply with [RLN](https://lip.logos.co/messaging/standards/core/17/rln-relay.html) constraints when sending segmented messages. - **Encryption Hook** to allow upper layers to provide a pluggable encryption mechanism. The main motivation for encryption is to protect the payload.