Re: [TLS] TLS 1.2 hash agility

Eric Rescorla <ekr@networkresonance.com> Wed, 26 September 2007 17:20 UTC

Return-path: <tls-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IaaYd-0007ru-1P; Wed, 26 Sep 2007 13:20:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IaaYb-0007kj-If for tls@ietf.org; Wed, 26 Sep 2007 13:20:17 -0400
Received: from [74.95.2.169] (helo=delta.rtfm.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IaaYb-0006R6-8O for tls@ietf.org; Wed, 26 Sep 2007 13:20:17 -0400
Received: from delta.rtfm.com (localhost.rtfm.com [127.0.0.1]) by delta.rtfm.com (Postfix) with ESMTP id 824D433C23; Wed, 26 Sep 2007 10:16:28 -0700 (PDT)
Date: Wed, 26 Sep 2007 10:16:27 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: Mike <mike-list@pobox.com>
Subject: Re: [TLS] TLS 1.2 hash agility
In-Reply-To: <46FA91E8.5020303@pobox.com>
References: <46ABB82D.8090709@pobox.com> <46ACCCCB.8000201@pobox.com> <B356D8F434D20B40A8CEDAEC305A1F24046B2496@esebe105.NOE.Nokia.com> <20070914215611.0342933C21@delta.rtfm.com> <46EB102E.2070900@pobox.com> <20070914225606.9E9B433C21@delta.rtfm.com> <46EC2AE7.9040903@pobox.com> <20070917185820.6E7CC33C3A@delta.rtfm.com> <46FA745A.3070305@pobox.com> <20070926152907.8A60B33C23@delta.rtfm.com> <46FA91E8.5020303@pobox.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20070926171628.824D433C23@delta.rtfm.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: tls@ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org

At Wed, 26 Sep 2007 10:07:52 -0700,
Mike wrote:
> 
> >> At the risk of being redundant, I assert that making this extension
> >> symmetric and allowing the server to respond with its own list of
> >> supported algorithms, is better than having the server send its
> >> list every place where it is needed (now and in the future).  Send
> >> it once in ServerHello, and use it where it's needed.
> > 
> > There is only one place where it's needed: CertificateRequest.
> 
> That is true at the moment, but if a future addition to the protocol
> also requires a signature, you will need to send the list twice.

Or simply make the change then.


> While I agree that this is in general good design, my opinion is
> that the other factors outweigh it.  Gentlemen can disagree.

Yes.

-Ekr


_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls