Add TLS Session Ticket support to reduce data exchange during TLS connection
Since many IOT devices could use SIM cards with limited internet data contract, I think it could be a great idea to support TLS Session Ticket to reduce the data exchanged by peers at each Iothub connection/disconnection: certificates exchange can be ignored if the peers are already paired by a previously successful connection, so we can avoid about 10kB of data each connection.
"When the server sends the “Server Hello” message, it can include a session identifier. The client should store it and present it in the “Client Hello” message of the next session. If the server finds the corresponding session in its cache and accepts to resume the session, it will send back the same session identifier and will continue with the abbreviated SSL handshake. Otherwise, it will issue a new session identifier and switch to a full handshake. This mechanism is detailed in RFC 5246. It is the most common mechanism because it exists since earlier versions of SSL." ( https://stackoverflow.com/questions/19939247/ssl-session-tickets-vs-session-ids )
Actually I increased the SAS TOKEN expiration, but I consider this a workaround