IETF Logo Mail Archive

Re: [admin-discuss] Moving the IETF network to WPA3.

Alan DeKok <aland@deployingradius.com> Wed, 09 August 2023 19:38 UTC

Return-Path: <aland@deployingradius.com>
X-Original-To: admin-discuss@ietfa.amsl.com
Delivered-To: admin-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4AAC1522C2 for <admin-discuss@ietfa.amsl.com>; Wed, 9 Aug 2023 12:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 FoI6QKVEwO1G for <admin-discuss@ietfa.amsl.com>; Wed, 9 Aug 2023 12:38:28 -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 3D4C5C1522AF for <admin-discuss@ietf.org>; Wed, 9 Aug 2023 12:38:27 -0700 (PDT)
Received: from smtpclient.apple (unknown [75.98.136.130]) by mail.networkradius.com (Postfix) with ESMTPSA id EC2E2380; Wed, 9 Aug 2023 19:38:24 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <CAHw9_iJ3DXRTQqhOzuhD97U0G80hq9vBx8JCtPnz_3-W6p17dQ@mail.gmail.com>
Date: Wed, 09 Aug 2023 15:38:23 -0400
Cc: Admin Discuss at IETF <admin-discuss@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <98AE2779-58AD-4722-8547-19827AD09F2B@deployingradius.com>
References: <CAHw9_iJ3DXRTQqhOzuhD97U0G80hq9vBx8JCtPnz_3-W6p17dQ@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/cMk9JopvivwCmZYoMT6s9Vk7_6k>
Subject: Re: [admin-discuss] Moving the IETF network to WPA3.
X-BeenThere: admin-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss/>
List-Post: <mailto:admin-discuss@ietf.org>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Aug 2023 19:38:32 -0000

On Aug 9, 2023, at 2:34 PM, Warren Kumari <warren@kumari.net> wrote:
> As a recap, the primary reason that we are doing this is to improve the user experience — 802.1X with RADIUS requires the use of certificates, and this causes significant friction for the user.

  While 802.1X is useful, the end-user experience has been terrible for decades.  There have been multiple attempts to address this including [1], with minimal up-take.

  In the mean time, moving to WPA3 with fallback to WPA2 is a reasonable approach.

  Alan DeKok.

[1] https://datatracker.ietf.org/doc/html/draft-winter-opsawg-eap-metadata-00

v2.23.0 | Report a Bug | By Email