[TLS] I-D Action: draft-ietf-tls-ticketrequests-00.txt

internet-drafts@ietf.org Sat, 19 January 2019 00:32 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: tls@ietf.org
Delivered-To: tls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF40F130F8B; Fri, 18 Jan 2019 16:32:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: tls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.3
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: tls@ietf.org
Message-ID: <154785795557.17452.3793151756514602603@ietfa.amsl.com>
Date: Fri, 18 Jan 2019 16:32:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/fc2KzwRb_Yw--UF9fQ1O3HU0B1Y>
Subject: [TLS] I-D Action: draft-ietf-tls-ticketrequests-00.txt
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2019 00:32:36 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Layer Security WG of the IETF.

        Title           : TLS Ticket Requests
        Authors         : Tommy Pauly
                          David Schinazi
                          Christopher A. Wood
	Filename        : draft-ietf-tls-ticketrequests-00.txt
	Pages           : 6
	Date            : 2019-01-18

Abstract:
   TLS session tickets enable stateless connection resumption for
   clients without server-side per-client state.  Servers vend session
   tickets to clients, at their discretion, upon connection
   establishment.  Clients store and use tickets when resuming future
   connections.  Moreover, clients should use tickets at most once for
   session resumption, especially if such keying material protects early
   application data.  Single-use tickets bound the number of parallel
   connections a client may initiate by the number of tickets received
   from a given server.  To address this limitation, this document
   describes a mechanism by which clients may specify the desired number
   of tickets needed for future connections.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tls-ticketrequests/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tls-ticketrequests-00
https://datatracker.ietf.org/doc/html/draft-ietf-tls-ticketrequests-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/