Re: [Emu] WG last call for draft-ietf-emu-tls-eap-types ?

Alan DeKok <aland@deployingradius.com> Fri, 12 August 2022 20:25 UTC

Return-Path: <aland@deployingradius.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5D67C14CF01 for <emu@ietfa.amsl.com>; Fri, 12 Aug 2022 13:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ag5rFd3zZdhM for <emu@ietfa.amsl.com>; Fri, 12 Aug 2022 13:24:56 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30208C14F741 for <emu@ietf.org>; Fri, 12 Aug 2022 13:24:55 -0700 (PDT)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id 3F92F115; Fri, 12 Aug 2022 20:24:51 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <CAOgPGoAYTe0qtFbJhq7S71FpX+k+1=0Gqqq+pwa+1QnBnQ3wrw@mail.gmail.com>
Date: Fri, 12 Aug 2022 16:24:49 -0400
Cc: EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <94154D9C-F880-42DB-B881-38B04F76E196@deployingradius.com>
References: <325659CB-E36E-4D18-A59C-B5EA54324201@deployingradius.com> <CAOgPGoAYTe0qtFbJhq7S71FpX+k+1=0Gqqq+pwa+1QnBnQ3wrw@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Kyq5r_hV8WxyR4Eenq462Ezx8Ys>
Subject: Re: [Emu] WG last call for draft-ietf-emu-tls-eap-types ?
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2022 20:25:00 -0000

On Aug 12, 2022, at 4:00 PM, Joseph Salowey <joe@salowey.net> wrote:
> [Joe] The chairs are reviewing the status and will have an update next week.

  Thanks.

> [Joe]  Is the statement in the draft about lack of implementation experience with EAP-FAST and TEAP still accurate?  

  Yes.  I haven't seen any progress on EAP-FAST.  TEAP might actually work, as implementors are working on interoperability.  But the base TEAP spec still has issues unrelated to TLS 1.3.  So that might take a while to get finished.

> You mentioned some interop issues in the meeting, are those issues on the path to getting resolved? 

  The interop issues were (a) a crash which is being worked on, and (b) a choice to not support session tickets for TTLS, which has been reported and is being addressed.

  So not so much interop issues as implementation issues.

  At this point. everything we know is in the document and is up to date.  I think it's worth publishing.  Given the lack of interest in FAST / TEAP with TLS 1.3, I think that shouldn't be a barrier to publication.

  Alan DeKok.