 |
 |
Hello, I don't suppose xrootd clients do support (or potentially could support without much effort) Server Name Indication? The potential use case is layer 4 TCP load balancing and routing on Kubernetes using an ingress provider. If xrootd clients use SNI during the TCP handshake to request a specific xrootd server name, then the ingress controller could know which backing server to direct the traffic to (which is otherwise not possible for a TCP router listening on a single (IP:port) combination), without having to know anything about the xrootd protocol. This question only regards xrootd clients; the server (actually EOS pods) would not need to do anything. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1951 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1