Re: [Reap] [Emu] EAP - TLS 1.3

Jari Arkko <jari.arkko@piuha.net> Thu, 16 November 2017 12:02 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: reap@ietfa.amsl.com
Delivered-To: reap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48607129435; Thu, 16 Nov 2017 04:02:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Nj9nC2H7ivrL; Thu, 16 Nov 2017 04:02:35 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B5CF0128B44; Thu, 16 Nov 2017 04:02:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DF9BD2D199; Thu, 16 Nov 2017 14:02:32 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6mmxdeeXxkbN; Thu, 16 Nov 2017 14:02:31 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 6292B2CD0D; Thu, 16 Nov 2017 14:02:30 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAOW+2ds2CwkogUJz-p8TRMdWs283BVhvrJWqFj1Upm9=8RboCg@mail.gmail.com>
Date: Thu, 16 Nov 2017 20:02:28 +0800
Cc: reap@ietf.org, Security Area Advisory Group <saag@ietf.org>, emu@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <58815EFC-3CF9-4F62-A7E3-6E76FBAA295A@piuha.net>
References: <3dbe94b9-4b2d-1479-8433-8b040cb1cfba@ericsson.com> <CAOW+2ds9Sez7otrs682hqzzXR8qbJYAdPwW8A8TEL+ms_a0=UA@mail.gmail.com> <ACE2CDE6-4D04-4049-BB15-1E82C214A553@gmail.com> <4c6c9bc8-6056-c03d-a0f6-f1f32fabef39@ericsson.com> <CAOW+2dtzq4d5p3JxwbbdwHqrS+0TpRveJkGb3vYzmdmLVvdcFQ@mail.gmail.com> <m2d1558xyi.wl-randy@psg.com> <CAOW+2du+teg8nicw6eDoSCKx_ZfAAXKtpLb0ogPUTk1Bzr1n_A@mail.gmail.com> <00d401d35114$de589760$9b09c620$@augustcellars.com> <8D84F942-5D10-4DB8-8EB7-3EB8A8AEE17E@gmail.com> <c740099f-4635-0853-5542-3d02eadf6ead@ericsson.com> <CAOW+2ds2CwkogUJz-p8TRMdWs283BVhvrJWqFj1Upm9=8RboCg@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>, Mohit Sethi <mohit.m.sethi@ericsson.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/reap/HqZXSMdYAA2SQ8ARbIln-tiW2ak>
Subject: Re: [Reap] [Emu] EAP - TLS 1.3
X-BeenThere: reap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "REAP \(RENEW\) EAP" <reap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/reap>, <mailto:reap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/reap/>
List-Post: <mailto:reap@ietf.org>
List-Help: <mailto:reap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/reap>, <mailto:reap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2017 12:02:37 -0000

I don’t want to push the decision in either direction without looking into the details.

But I wanted to point out that there’s usually a third alternative between “no need for new documents” and “need a new RFC to describe the new version”. Explaining that the old protocol can be used and what the implications are may by itself be a useful document. In the specific example, is not immediately obvious to me for instance if the security consideration would somehow change, or if 0-RTT can or can not be used, etc.

Jari