Missing sslEnabledProtocols configuration for Binary Transport in official documentation

Description

The following configuration appears to be missing from the official documentation. While similar settings are documented for transport.https.sslHostConfig.properties, this specific configuration for the binary transport is not included in [1] and [2].

Due to this, some customers are misled and end up using incorrect configurations for the binary transport, which leads to issues.

Could you please consider updating the official documentation to include the following transport.binary.receiver ?

Sample :

[transport.binary.receiver]
sslEnabledProtocols = "TLSv1.2"
ciphers = ["TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256", "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"]

This would help avoid misconfigurations and ensure better clarity for users working with secure binary transport.

Suggested Improvement

add

[transport.binary.receiver]
sslEnabledProtocols = "TLSv1.2"
ciphers = ["TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256", "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"]

Version(s)

3.1.0 to latest

Start with the official documentation referenced as [1] and [2], comparing the existing transport.https.sslHostConfig.properties settings with the binary transport section. Add the shown transport.binary.receiver sslEnabledProtocols and ciphers example, then verify the documentation clearly covers secure binary transport configuration.