IETF Logo Mail Archive

Re: [Emu] POST WGLC Comments draft-ietf-emu-eap-tls13

Joseph Salowey <joe@salowey.net> Wed, 30 October 2019 05:23 UTC

Return-Path: <joe@salowey.net>
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 82AD71200E3 for <emu@ietfa.amsl.com>; Tue, 29 Oct 2019 22:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 uj2liK3eKrza for <emu@ietfa.amsl.com>; Tue, 29 Oct 2019 22:22:59 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35A6C12003E for <emu@ietf.org>; Tue, 29 Oct 2019 22:22:59 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id t26so1609625qtr.5 for <emu@ietf.org>; Tue, 29 Oct 2019 22:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aA90i/vIj3qvJZy9RA9DJiSqdFolbasb5mlbgBR9yn0=; b=AMO8R6rWV/pmTa0Ne/Bk0twQQUpxWAbvenih1vyLKdniWJfJfY8Z4c712Bl68u0qT/ 9ssCUKbBvTyRhESiws33snSJia7dtHeeRKtUxumD9SluN5ocC0Zo9nLUmQgwB/VkU0e5 +MXYmRSs+cnJFKPKjhN5NtMkkFV1eKrlGN/YknQJp88W8oFb9/UzGLuywcWSkbyfPa2u ciY2iGNKq1eDyPnpgfQmv8u/i261PyP6/yTiZ+RZpgBE/gHJUMmHwkLyJ2LKVe61lyY6 5ddE4EfPzIf2AREqkzkD5+VmHOjaeJsTbjbcqRV9YPN2vSBJHnjhp7elJSM5xjY53god aEZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aA90i/vIj3qvJZy9RA9DJiSqdFolbasb5mlbgBR9yn0=; b=CGnoMPI6o80JfJWKNO9YBX09NRdGahtboOMJ+k7IIgJjgRUBLaeddMX/hiwaZ2yyS+ Cqb8nq6a+Iu3PCNgYNmoeJGRvKAzL3Vx4g2NvZS9lPPoog88XyuXUVUsZymFlk6bs9pT 20wU/pjp2Jc4d4zgwqh0ermRrNLKt5Lmia1pEJASyrG2fyYKEtPthnoYxNidVlJAyDRm cO1Blb0lKctqfYczoe17ehlSy/DQQJ+Kt0ckRSDTuLyCFH0ci0vaEEXAKihmVgLj40We /hWUlTrUVvSHbw7WHcvc8h5pA9F7NpMAu5MXHhchdaVmjtkOGkEDTB0Gwj1v80/MQ2s/ r5FA==
X-Gm-Message-State: APjAAAVhtlUvW/pNdA3u8NteNaKEbAMZzt3PR7YOX1+Vr9UUX7Z+7/UD UcOhiU1lGNX3zBTga6potNZ+FzL/L4cgeIkgOBzAbQ==
X-Google-Smtp-Source: APXvYqwFyYgPhr9pyuPYxaxU2Q0dsnDTHEgHp4zVBBGvTPsdPhVw6U5YvENkc+fBXXkuADeSi1Jv1dsbbM5zOKGe2zA=
X-Received: by 2002:a0c:b59b:: with SMTP id g27mr20728926qve.184.1572412978060; Tue, 29 Oct 2019 22:22:58 -0700 (PDT)
MIME-Version: 1.0
References: <7828_1564869242_5D46027A_7828_348_1_02e001d54a45$e92ae900$bb80bb00$@augustcellars.com> <20b118932a4843b6b88e605799fafea8@aalto.fi> <211AD83C-D111-4EEB-AAF0-D9B5E521F4CF@deployingradius.com> <8F355C6F-DF1E-4E03-B75E-0F1D2508B9D4@ericsson.com> <246280B8-6E5C-484B-95BD-9C940C98C507@deployingradius.com> <CY4PR1101MB22781AB8C8982ACF99B61544DB8E0@CY4PR1101MB2278.namprd11.prod.outlook.com> <17E08795-4E4E-4507-8384-836020966BCF@deployingradius.com> <634C375D-FBF3-4297-A5C0-E68C903CA34A@ericsson.com> <CAOgPGoBko6N_JebmisoSk_EJ=Hq21sV3xoXjLw4r7D+OFSsdZA@mail.gmail.com> <CC58A292-03D6-4D70-A11F-B8FEE7311E78@cisco.com> <26738.1570791861@dooku.sandelman.ca> <AD799A14-8268-4BAF-8925-3567973C7507@cisco.com> <9501.1570802988@dooku.sandelman.ca> <DCC85780-B079-4AD0-8870-7528270B70D8@cisco.com>
In-Reply-To: <DCC85780-B079-4AD0-8870-7528270B70D8@cisco.com>
From: Joseph Salowey <joe@salowey.net>
Date: Tue, 29 Oct 2019 22:22:46 -0700
Message-ID: <CAOgPGoA0RCY+J5bDOyUiKtFy5Vk=C11yvE8O=rsJPQeS8Fzk0A@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: Michael Richardson <mcr@sandelman.ca>, "draft-ietf-emu-eap-tls13@ietf.org" <draft-ietf-emu-eap-tls13@ietf.org>, John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ff777f059619ec01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/N4Ibk5-v3FyAHu-9zivUNWaW_M8>
Subject: Re: [Emu] POST WGLC Comments draft-ietf-emu-eap-tls13
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 30 Oct 2019 05:23:01 -0000

On Fri, Oct 11, 2019 at 7:34 AM Eliot Lear <lear@cisco.com> wrote:

>
>
> > On 11 Oct 2019, at 16:09, Michael Richardson <mcr@sandelman.ca> wrote:
> >
> > So, can wired just be a degenerate version of wifi, where there can be
> only
> > one "ESSID", and there are no beacons to consider?
>
>
> On the whole that has been my thought.  But it is a matter of which
> mechanism to degenerate to.  Is it TLS-PSK?  eDPP++?  TLS with naked public
> keys++?  And again, this is the on-prem case.  For cloud, we are well along.
>

[Joe] We are currently in a holding pattern with EAP-TLS.  It does not seem
right to delay it for functionality that we are not sure we have a use case
for.  If a use case develops then we can publish an update to EAP-TLS 1.3.
Do we have a use case for EAP-TLS-PSK that is blocked in the current
situation?



> Eliot
>

v2.23.0 | Report a Bug | By Email