From: Simon Josefsson <simon@josefsson.org>
Date: Wed, 19 Aug 2009 13:11:06 +0000 (+0200)
Subject: Add.
X-Git-Tag: gnutls_2_9_3~10
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=609c4311c73f5cff64fb5dca4fe9e351892464d3;p=thirdparty%2Fgnutls.git

Add.
---

diff --git a/doc/gnutls.texi b/doc/gnutls.texi
index b3a1ee9710..2bea31266d 100644
--- a/doc/gnutls.texi
+++ b/doc/gnutls.texi
@@ -974,6 +974,7 @@ in @acronym{GnuTLS} are:
 @itemize
 @item Maximum fragment length negotiation
 @item Server name indication
+@item Session tickets
 @end itemize
 
 and they will be discussed in the subsections that follow.
@@ -1005,6 +1006,21 @@ begins within the first handshake packet.  The functions
 used to enable this extension, or to retrieve the name sent by a
 client.
 
+@subsection Session Tickets
+@cindex TLS Extensions
+@cindex Session Tickets
+@cindex Ticket
+
+To resume a TLS session the server normally store some state.  This
+complicates deployment, and typical situations the client can cache
+information and send it to the server instead.  The Session Ticket
+extension implements this idea, and it is documented in RFC 4507/5077.
+
+Clients can enable support for TLS tickets with
+@ref{gnutls_session_ticket_enable_client} and servers use
+@ref{gnutls_session_ticket_key_generate} to generate a key and
+@ref{gnutls_session_ticket_enable_server} to enable the extension.
+
 @node Selecting cryptographic key sizes
 @section Selecting Cryptographic Key Sizes
 @cindex key sizes