Hi, Dmitry:
We want to switch the TLS connection quickly to another address of the same server, to keep the following transaction traffic stick to the same server, that is to say, keep the service affinity during the network fluctuations.
The previous address of the server is one ANYCAST address that are shared by several servers that can provide the same service.
Once the network entry device selects the optimal server to communicate(based on the network conditions and server’s capabilities in real time), we want to keep the following transaction traffic stick to this server, then we should use one unique address of this server.
Do I correctly understand that you are proposing the mechanism to save some traffic and computation when we have a previously happened communication? Hi, All TLS experts:
We are seeking the experts from the TLS WG, who is/are familiar with the TLS protocol itself and know how to extend it to accommodate new features within TLS.
If you have such experiences and interested to cooperate with us, please contact me, via mail, or on-site at Bangkok during the IETF 122 meeting.
I can explain the background of such extensions with you and discuss the futures cooperation expectations.
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]
|
_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]
