There is no binding to an IP or port. The only relevant binding here is to a TLS connection.
On Thu, Jul 29, 2021, at 04:16, Yaron Sheffer wrote: > Yes, of course it would. > > Thanks, > Yaron > > On 7/28/21, 20:24, "Uta on behalf of Grant Taylor" > <uta-boun...@ietf.org on behalf of > gtaylor=40tnetconsulting....@dmarc.ietf.org> 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 connection > > to a particular port, and that's the problem addressed here > > Is there something that binds the encrypted TLS connection to a > particular IP? > > What if the certificate & key is used on multiple IPs on the same or > different systems? Won't the same problem exist? > > > > -- > Grant. . . . > unix || die > > _______________________________________________ > Uta mailing list > Uta@ietf.org > https://www.ietf.org/mailman/listinfo/uta > > > _______________________________________________ > Uta mailing list > Uta@ietf.org > https://www.ietf.org/mailman/listinfo/uta > _______________________________________________ Uta mailing list Uta@ietf.org https://www.ietf.org/mailman/listinfo/uta
