From fd7e52dc5b4188b27044b37a62d61b84c20a0e07 Mon Sep 17 00:00:00 2001 From: Ivan FB Date: Fri, 1 May 2026 11:54:05 +0200 Subject: [PATCH] make it more clear when encryption should be implemented --- 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 90bce37..cb5eddc 100644 --- a/standards/application/reliable-channel-api.md +++ b/standards/application/reliable-channel-api.md @@ -135,7 +135,7 @@ The Encryption Hook provides a pluggable interface for upper layers to inject en - The hook is optional; when not provided, messages are sent unencrypted. - Encryption is applied per segment, after segmentation and SDS. - Decryption is applied per segment before being processed by SDS. -- The `Encryption` interface MUST be implemented by the caller. +- The `Encryption` interface MUST be implemented by the caller when the hook is provided. - The Reliable Channel API MUST NOT impose any specific encryption scheme. ## Procedures