Re: [TLS] Session Lifetime

Martin Rex <> Thu, 18 November 2010 02:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2CF5B3A6778 for <>; Wed, 17 Nov 2010 18:50:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.12
X-Spam-Status: No, score=-10.12 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ylcG2XjiIp+E for <>; Wed, 17 Nov 2010 18:50:40 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id CDAA63A635F for <>; Wed, 17 Nov 2010 18:50:39 -0800 (PST)
Received: from by (26) with ESMTP id oAI2pOkR005364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Nov 2010 03:51:25 +0100 (MET)
From: Martin Rex <>
Message-Id: <>
Date: Thu, 18 Nov 2010 03:51:23 +0100
In-Reply-To: <> from "Michael D'Errico" at Nov 17, 10 05:44:17 pm
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Scanner: Virus Scanner virwal08
X-SAP: out
Subject: Re: [TLS] Session Lifetime
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 18 Nov 2010 02:50:41 -0000

Michael D'Errico wrote:
> Can someone point me to a document that explains why TLS
> sessions should expire within minutes of creation, as is
> the current practice (that I'm aware of)?

I am only aware of an upper lifetime limit of 24h for cached TLS session
in the SSLv3 and TLS specs, e.g. here:

For our apps I'm currently shipping a default session cache lifetime
of 15 minutes for the server and 30 minutes for the client.
Although this is a fairly short lifetime, it is perfectly sufficient
to achieve an acceptable ratio of full-HS/resume-HS.
Customers can finetune session cache size and cache lifetime.

I don't know what other implementations and apps are using.