Explicitly state, that Discovery Proxy uses HTTP(S)

[DominikST95]

In https://profiles.ihe.net/DEV/SDPi/#vol1_clause_sdpi_p_option_managed_discovery, the use of HTTPS is only introduced indirectly:

The default "ad hoc" approach using the [Section 2:3.23] and [Section 2:3.24] transactions, requires use of unsecured multicast messaging; however, some deployments do not support or allow this mode of discovery. The addition of a [Discovery Proxy] Actor enables a secure and non-multicast means for managing system discovery across the network.

Also, the transactions do not mention HTTPS explicitly

[JavierEspina]

SDPi call - 20 March 2026:
Need to check how implicit or not it is (before adding new requirements). Note that besides the sentence quoted in the comment, the diagrams show that the transactions / steps are secured.

[DominikST95]

R0502 A SOMDS Participant shall use HTTPS with mutual authentication for those transactions that are required to be secured.

Defines "Secured" to be HTTPS. So maybe a note instead of a requirement should suffice, so that the image is not the only source of this information