Re: [TLS] TLS 1.2 hash agility

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

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>
Cc: tls@ietf.org
Precedence: list
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

[TLS] TLS 1.2 Eric Rescorla
Re: [TLS] TLS 1.2 Steven M. Bellovin
Re: [TLS] TLS 1.2 Peter Gutmann
Re: [TLS] TLS 1.2 Steven M. Bellovin
Re: [TLS] TLS 1.2 Bodo Moeller
[TLS] TLS 1.2 Mike
[TLS] TLS 1.2 Mike
[TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 Mike
[TLS] TLS 1.2 MAC calculation Mike
Antwort: [TLS] TLS 1.2 MAC calculation Axel.Heider
Re: Antwort: [TLS] TLS 1.2 MAC calculation Bodo Moeller
Re: [TLS] TLS 1.2 interoperating Mike
RE: [TLS] TLS 1.2 hash agility Pasi.Eronen
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
RE: [TLS] TLS 1.2 hash agility Pasi.Eronen
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Mike
RE: [TLS] TLS 1.2 hash agility Pasi.Eronen
RE: [TLS] TLS 1.2 hash agility Pasi.Eronen
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Mike
Re: [TLS] TLS 1.2 hash agility Eric Rescorla
RE: [TLS] TLS 1.2 hash agility Russ Housley
RE: [TLS] TLS 1.2 hash agility Pasi.Eronen
RE: [TLS] TLS 1.2 hash agility Pasi.Eronen