Is it the expectation of the TLS work group, that any TCP-based protocol that listens on a well-known port, and now wants a TLS-secured version, obtain another well-known port for that purpose? Or are there other strategies that you could suggest. For example, would it be frowned on to have a TLS implementation that dynamically distinguishes ClientHello from the (insecure) Application Protocol on a given port (assuming this can be done deterministically)? john_h_wilson@ccm.jf.intel.comReceived on Tuesday, 29 October 1996 15:07:44 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:17:12 UTC