RE: [TLS] TLS 1.2 hash agility

<Pasi.Eronen@nokia.com> Fri, 28 September 2007 09:02 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 1IbBk9-0004BL-2B; Fri, 28 Sep 2007 05:02:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IbBk7-0004Ay-Ts for tls@ietf.org; Fri, 28 Sep 2007 05:02:39 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IbBk7-00084O-E6 for tls@ietf.org; Fri, 28 Sep 2007 05:02:39 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l8S92Zjf015880; Fri, 28 Sep 2007 12:02:37 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Sep 2007 12:02:23 +0300
Received: from esebe105.NOE.Nokia.com ([172.21.143.53]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Sep 2007 12:02:22 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [TLS] TLS 1.2 hash agility
Date: Fri, 28 Sep 2007 12:02:22 +0300
Message-ID: <B356D8F434D20B40A8CEDAEC305A1F2404A52690@esebe105.NOE.Nokia.com>
In-Reply-To: <20070927161005.7CB8C33C28@delta.rtfm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [TLS] TLS 1.2 hash agility
Thread-Index: AcgBIk/HwNcAv3f6RvSwwZ5YkvYMNAAi5GNA
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> <46FB4397.6040203@pobox.com><46FBBBBE.7000108@pobox.com><20070927143028.7EF4433C21@delta.rtfm.com><46FBC5A1.7020501@pobox.com> <20070927161005.7CB8C33C28@delta.rtfm.com>
From: Pasi.Eronen@nokia.com
To: ekr@networkresonance.com, mike-list@pobox.com
X-OriginalArrivalTime: 28 Sep 2007 09:02:22.0918 (UTC) FILETIME=[484FB660:01C801AE]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
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

Eric Rescorla wrote:

> This is a WG document, so it's actually the WG's position that
> matters. But given that you and I are the people who have
> expressed opinions...

<all hats off>

Either alternative seems to work technically -- but as the server
already indicates in CertificateRequest what kind of public key
the cert should contain, and which CA issued it, putting the
signature algorithm list there as well seems slightly nicer to me.

Best regards,
Pasi

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