Re: [TLS] 答复 : New "Fast-Track" draft posted
Stefan Santesson <stefan@aaa-sec.com> Mon, 20 April 2009 16:27 UTC
Return-Path: <stefan@aaa-sec.com>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6144A3A6F50 for <tls@core3.amsl.com>; Mon, 20 Apr 2009 09:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.162
X-Spam-Level:
X-Spam-Status: No, score=-0.162 tagged_above=-999 required=5 tests=[AWL=-1.413, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kSBQF1zLMUvS for <tls@core3.amsl.com>; Mon, 20 Apr 2009 09:27:09 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.112]) by core3.amsl.com (Postfix) with ESMTP id 3D5613A6F7E for <TLS@ietf.org>; Mon, 20 Apr 2009 09:27:08 -0700 (PDT)
Received: (qmail 48921 invoked from network); 20 Apr 2009 16:28:28 -0000
Received: from s34.loopia.se (HELO s24.loopia.se) ([194.9.94.70]) (envelope-sender <stefan@aaa-sec.com>) by s87.loopia.se (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for <TLS@ietf.org>; 20 Apr 2009 16:28:28 -0000
Received: (qmail 45804 invoked from network); 20 Apr 2009 16:28:21 -0000
Received: from 90-229-233-249-no153.tbcn.telia.com (HELO [192.168.0.17]) (stefan@fiddler.nu@[90.229.233.249]) (envelope-sender <stefan@aaa-sec.com>) by s24.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <huangmin123@huaweisymantec.com>; 20 Apr 2009 16:28:21 -0000
User-Agent: Microsoft-Entourage/12.17.0.090302
Date: Mon, 20 Apr 2009 18:28:20 +0200
From: Stefan Santesson <stefan@aaa-sec.com>
To: Min Huang <huangmin123@huaweisymantec.com>, "'Joseph Salowey (jsalowey)'" <jsalowey@cisco.com>, martin.rex@sap.com
Message-ID: <C6126F44.18E2%stefan@aaa-sec.com>
Thread-Topic: 答复: [TLS] New "Fast-Track" draft posted
Thread-Index: Acm9NuIaqNzM0NwHRu2DPH9wzfajtgBGhc3QAMbaT5AAGihsxg==
In-Reply-To: <000601c9c197$621ed4e0$909a1b0a@china.huawei.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: stefans@exmsft.com, TLS@ietf.org
Subject: Re: [TLS] 答复 : New "Fast-Track" draft posted
X-BeenThere: tls@ietf.org
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." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Apr 2009 16:27:10 -0000
I think we agree but why would the client send an empty cashedInformationHash instead of sending a hash over the cached information? /Stefan On 09-04-20 11:07 AM, "Min Huang" <huangmin123@huaweisymantec.com> wrote: > The > client may cache this information sent by the specific server at the first > time they > communicate with each other. The corresponding CachedInformationHash > contained in the extension of the Client hello message may be empty. It > indicates that the client has already known the trusted CA list of the > server and it > has certificates trusted by the server.
- Re: [TLS] 答复 : New "Fast-Track" draft posted Stefan Santesson
- [TLS] Mobi-d next steps Michael.G.Williams