Re: [TLS] New cached info draft 02 posted

Martin Rex <> Tue, 29 September 2009 01:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 178603A68F4 for <>; Mon, 28 Sep 2009 18:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.919
X-Spam-Status: No, score=-5.919 tagged_above=-999 required=5 tests=[AWL=0.330, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iSs7+zuMfrcO for <>; Mon, 28 Sep 2009 18:06:02 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 19B2E3A62C1 for <>; Mon, 28 Sep 2009 18:06:01 -0700 (PDT)
Received: from by (26) with ESMTP id n8T17I2p008889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Sep 2009 03:07:18 +0200 (MEST)
From: Martin Rex <>
Message-Id: <>
To: (Stefan Santesson)
Date: Tue, 29 Sep 2009 03:07:17 +0200 (MEST)
In-Reply-To: <> from "Stefan Santesson" at Sep 15, 9 01:04:58 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Scanner: Virus Scanner virwal06
X-SAP: out
Subject: Re: [TLS] New cached info draft 02 posted
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: Tue, 29 Sep 2009 01:06:03 -0000

Stefan Santesson wrote:
> I have just posted a new version 02 of the cached info draft.
> As there has been no further comments on the draft responding to my
> questions after last IETF, I have nothing further to add.
> I think this document is ready for a WGLC.

I already mentioned twice in the discussion of this document
that I would REALLY appreciate if it was enhanced to provide
a much better cache control (for the client, that is).

The extension should allow the client to determine
 (a) whether the server supports the caching extension
 (b) for which elements the server supports caching
 (c) which hash algorithm the server supports for caching

on the first connect to a server, so that the client does
not have to make guesses and populate/maintain its cache
for servers that do not support this extension.