3.6.3 Session tickets

To resume a TLS session the server normally store session parameters. This complicates deployment, and could be avoiding by delegating the storage to the client. Because session parameters are sensitive they are encrypted and authenticated with a key only known to the server and then sent to the client. The Session Ticket extension implements this idea, and it is documented in RFC 5077 [TLSTKT].

This document was generated on January 4, 2012 using texi2html 5.0.