Hi,
Section 3.8 of the draft says:
TLS implementations (both client- and server-side) MUST support the
Application-Layer Protocol Negotiation (ALPN) extension [RFC7301].
This looks fine to me. I assume it is still up to application protocols
to decide whether or not use of ALPN is require
Hi Alexey!
On 7/28/21 7:31 AM, Alexey Melnikov wrote:
> Hi,
>
> Section 3.8 of the draft says:
> TLS implementations (both client- and server-side) MUST support the
> Application-Layer Protocol Negotiation (ALPN) extension [RFC7301].
>
> This looks fine to me. I assume it is still up to ap
Hi Akexey,
This is about different protocol servers sharing the same IP, but *not* the
same port. There's nothing to bind the encrypted TLS connection to a particular
port, and that's the problem addressed here - an IMAP client being forced to
talk to an FTP server. Obviously you can have IMAP
On 7/28/21 8:27 AM, Yaron Sheffer wrote:
This is about different protocol servers sharing the same IP, but*not*
the same port. There's nothing to bind the encrypted TLS connection
to a particular port, and that's the problem addressed here
Is there something that binds the encrypted TLS connec
Yes, of course it would.
Thanks,
Yaron
On 7/28/21, 20:24, "Uta on behalf of Grant Taylor" wrote:
On 7/28/21 8:27 AM, Yaron Sheffer wrote:
> This is about different protocol servers sharing the same IP, but*not*
> the same port. There's nothing to bind the encrypted TLS con
