Re: [TLS] Redefine Finished message for TLS 1.3 ?

Nelson Bolyard <nelson@bolyard.me> Tue, 17 November 2009 23:31 UTC

Return-Path: <nelson@bolyard.me>
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 F3DCA3A69C3 for <tls@core3.amsl.com>; Tue, 17 Nov 2009 15:31:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Wq8+IDSFwTzI for <tls@core3.amsl.com>; Tue, 17 Nov 2009 15:31:13 -0800 (PST)
Received: from smtpauth22.prod.mesa1.secureserver.net (smtpauth22.prod.mesa1.secureserver.net [64.202.165.44]) by core3.amsl.com (Postfix) with SMTP id CEFE43A67DA for <tls@ietf.org>; Tue, 17 Nov 2009 15:31:13 -0800 (PST)
Received: (qmail 23785 invoked from network); 17 Nov 2009 23:31:10 -0000
Received: from unknown (192.18.120.70) by smtpauth22.prod.mesa1.secureserver.net (64.202.165.44) with ESMTP; 17 Nov 2009 23:31:10 -0000
Message-ID: <4B03323C.7020900@bolyard.me>
Date: Tue, 17 Nov 2009 15:31:08 -0800
From: Nelson Bolyard <nelson@bolyard.me>
Organization: Network Security Services
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a5pre) Gecko/20070527 SeaMonkey/1.5a
MIME-Version: 1.0
To: tls@ietf.org
References: <20091112181844.GE1105@Sun.COM> <200911122036.nACKa96m016227@fs4113.wdf.sap.corp> <20091112203847.GL1105@Sun.COM> <20091113082235.C55F469F381@kilo.networkresonance.com> <20091113164608.GT1105@Sun.COM> <4AFF0153.3090005@bolyard.me> <3EFE80FB-AB07-4BB3-ABDD-E836D27B7E54@acm.org> <4B01B1D5.3030005@bolyard.me> <B4108ED3-EBCB-477E-9D9A-9CA4B92240E5@acm.org>
In-Reply-To: <B4108ED3-EBCB-477E-9D9A-9CA4B92240E5@acm.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [TLS] Redefine Finished message for TLS 1.3 ?
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: Tue, 17 Nov 2009 23:31:15 -0000

Bodo Moeller wrote:
> On Nov 16, 2009, at 12:11 PM, Nelson B Bolyard wrote:
>> On 2009-11-15 11:13 PDT, Bodo Moeller wrote:
>>> On Nov 14, 2009, at 11:13 AM, Nelson B Bolyard wrote:
> 
>>>> Others in the meeting responded that changing the definition of the
>>>> computation of the Finished messages was a change to the base protocol
>>>> specification (which adding an extension is not), and thus the change
>>>> I proposed would make TLS become (say) TLS 1.3.
>>>
>>> In that proposal, would there have been any explicit indicator sent by
>>> the client and server to indicate that they intend to use the the
>>> modified Finished message?
>>
>> Yes, the protocol version number.
> 
> Well, obviously -- I was asking about the proposal *before* others had
> suggested that this would require a new protocol version.
> 
> I gather that there was no other indicator, and *thus* they thought the
> protocol version would have to change.

I had something else in mind, but I never presented it, because I concurred
with the assessment that it was a base protocol change and really deserved
a new protocol version number.