Re: [TLS] AD Review of draft-ietf-tls-tls13

Bill Frantz <frantz@pwpconsult.com> Tue, 23 May 2017 04:19 UTC

Return-Path: <frantz@pwpconsult.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE1E6124BFA for <tls@ietfa.amsl.com>; Mon, 22 May 2017 21:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QG5Ag8eSVjNO for <tls@ietfa.amsl.com>; Mon, 22 May 2017 21:19:32 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5CC9127868 for <tls@ietf.org>; Mon, 22 May 2017 21:19:32 -0700 (PDT)
Received: from [47.143.125.207] (helo=Williams-MacBook-Pro.local) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <frantz@pwpconsult.com>) id 1dD1IB-0004lf-2Z for tls@ietf.org; Tue, 23 May 2017 00:19:31 -0400
Date: Mon, 22 May 2017 21:19:30 -0700
From: Bill Frantz <frantz@pwpconsult.com>
To: TLS WG <tls@ietf.org>
X-Priority: 3
In-Reply-To: <1A619330-282A-44F0-871B-DF6D15850394@dukhovni.org>
Message-ID: <r470Ps-10124i-4126E6020A9F407EB18E86674748440A@Williams-MacBook-Pro.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Mailsmith 2.4 (470)
X-ELNK-Trace: 3a5e54fa03f1b3e21aa676d7e74259b7b3291a7d08dfec7984ef9363539b6c8596f3c22f5838e7de350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 47.143.125.207
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/OkGvOdzYzso9aZXZXm3jmcVoyYk>
Subject: Re: [TLS] AD Review of draft-ietf-tls-tls13
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
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/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 23 May 2017 04:19:35 -0000

On 5/22/17 at 10:46 AM, ietf-dane@dukhovni.org (Viktor Dukhovni) wrote:

>>On May 22, 2017, at 1:37 PM, Salz, Rich <rsalz@akamai.com> wrote:
>>
>>I strongly believe the text should stay as it is, for the most good to the most people.  Viktor is in the weeds, arguably by himself.
>
>Right, all by myself...  With support from Nico, Ilari, and others who've upthread
>accepted that certificate verification is properly RFC5280 and not TLS, before I
>suggested removal of the text in question (which solves no real problem, but does
>create needless interoperability issues for various TLS use-cases).

Please allow me to add my voice to Viktor's. When I wrote the E 
language communication protocol, many people said I should use 
SSL. Some of the reasons we did not use SSL are in a 1998 
document <http://www.erights.org/elib/distrib/vattp/SSLvsDataComm.html>.

Our protocol started with a hash of the peer's public key. With 
that bit of information, other authentications are unnecessary. 
If I were starting today, we could use TLS with PSKs by asking 
the other side for it's key and then using it with a TLS library 
(I think).

Cheers - Bill

---------------------------------------------------------------------------
Bill Frantz        |"Web security is like medicine - trying to 
do good for
408-356-8506       |an evolved body of kludges" - Mark Miller
www.pwpconsult.com |