Re: [TLS] First TLS cached information draft posted

To: Simon Josefsson <simon at josefsson.org>
Subject: Re: [TLS] First TLS cached information draft posted
From: Stefan Santesson <stefan at aaa-sec.com>
Date: Fri, 05 Jun 2009 19:04:22 +0200
Cc: TLS wg <TLS at ietf.org>
Delivered-to: tls at core3.amsl.com
In-reply-to: <87vdnavowa.fsf at mocca.josefsson.org>
List-archive: <http://www.ietf.org/mail-archive/web/tls>
List-help: <mailto:tls-request@ietf.org?subject=help>
List-id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-post: <mailto:tls@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
Thread-index: Acnl/6vjK7l0ISAUJESeaAbYqsB53Q==
Thread-topic: First TLS cached information draft posted
User-agent: Microsoft-Entourage/12.17.0.090302

Simon,

The specification allows you to specify and use any hash algorithm that is
supported by the TLS hash algorithm registry.

SHA-1 is the only MUST support algorithm, and I think that is correct.

/Stefan

On 09-06-05 2:36 PM, "Simon Josefsson" <simon at josefsson.org> wrote:

> A minor discussion would be whether adding support for SHA-256/384/512
> is worthwhile, but I don't feel strongly either way.

Follow-Ups:
- Re: [TLS] First TLS cached information draft posted
  - From: Simon Josefsson

References:
- Re: [TLS] First TLS cached information draft posted
  - From: Simon Josefsson

Prev by Date: Re: [TLS] First TLS cached information draft posted
Next by Date: Re: [TLS] First TLS cached information draft posted
Previous by thread: Re: [TLS] First TLS cached information draft posted
Next by thread: Re: [TLS] First TLS cached information draft posted
Index(es):
- Date
- Thread

Re: [TLS] First TLS cached information draft posted

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.