Jacob Hoffman-Andrews detailing Twitter's TLS session tickets implementation for session resumption with forward secrecy:
We have a set of key generator machines, of which one is the leader. The leader generates a fresh session ticket key every twelve hours and zeroes old keys after thirty-six hours. Keys are stored in tmpfs (a RAM-based filesystem), with no swap partitions configured. It's important that there be no swap, because tmpfs will use swap if available, which could write keys to long-term disk storage.
Every five minutes, our frontends fetch the latest ticket keys from a key generator machine via SSH.
The course is intended for graduate students in cryptography and mathematics. Introductory topics on elliptic curves and cryptographic applications will be covered, with an emphasis on providing a strong background in support of the research talks at ECC.
Slides are available online and it's very good, it covers the main fields related to EC.
And, don't miss the rule 34 of crypto from the lecture on pairings:
Rule 34 of crypto. If you can think of a crypto scenario, there is already a pairing-based article about it.