From 638f8676d65f8dc82dce67253f67e80819dfbd00 Mon Sep 17 00:00:00 2001 From: Ivan FB Date: Thu, 9 Apr 2026 22:41:53 +0200 Subject: [PATCH] clarify and make IEncrypt description more concise --- standards/application/reliable-channel-api.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/standards/application/reliable-channel-api.md b/standards/application/reliable-channel-api.md index 82b429f..184c148 100644 --- a/standards/application/reliable-channel-api.md +++ b/standards/application/reliable-channel-api.md @@ -152,10 +152,8 @@ types: IEncryption: type: object description: "Interface for a pluggable encryption mechanism. - When IEncryption is provided, see ReliableChannelConfig, the encrypt and decrypt operations MUST be provided by the API consumer. - Notice that the encrypt/decrypt signatures may defer from what are described below but the important - point is that both operations MUST have a mechanism to accept an byte array as input and return a - byte array as an output." + When provided, see ReliableChannelConfig, the API consumer MUST implement both encrypt and decrypt operations. + Implementations MAY use different signatures than those described below, as long as each operation accepts a byte array and returns a byte array." fields: encrypt: type: function