IETF Logo Mail Archive

Re: [Emu] Provisioning, configuration, etc. and EAP

Alan DeKok <aland@deployingradius.com> Mon, 28 March 2022 21:35 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 94F483A157C for <emu@ietfa.amsl.com>; Mon, 28 Mar 2022 14:35:32 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] 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 Q6Y2uMp0LsZ9 for <emu@ietfa.amsl.com>; Mon, 28 Mar 2022 14:35:27 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84B3F3A1571 for <emu@ietf.org>; Mon, 28 Mar 2022 14:35:27 -0700 (PDT)
Received: from smtpclient.apple (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id D87D329F; Mon, 28 Mar 2022 21:35:21 +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 15.0 \(3693.60.0.1.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <94640.1648472403@dooku>
Date: Mon, 28 Mar 2022 17:35:20 -0400
Cc: EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <501558C4-7829-4144-8966-52B79358367E@deployingradius.com>
References: <8C03CE4A-B987-4962-9AA3-5DF8FB32ECB5@deployingradius.com> <69280.1648310501@dooku> <BC205D3A-DCDD-4C43-AF88-9031622FCAFA@deployingradius.com> <94640.1648472403@dooku>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/hUs4lWNMvNHhXXab52_VQoWOGJM>
Subject: Re: [Emu] Provisioning, configuration, etc. and EAP
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: Mon, 28 Mar 2022 21:35:33 -0000

On Mar 28, 2022, at 9:00 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> Well, this is not something I'd do as part of onboarding, but rather as part
> of _configuration_, and I agree that it would be better to just use IP for that.

  I'd argue that onboarding is just a special case of configuration.

> The issue is that new SSIDs have to deployed over hundreds of access points.

  Use the normal SSID.  Unauthenticated EAP-TLS.  User ID of "provisioning@eap.arpa".

> This new "LAN" has to have VLANs deployed for it,  and if done wrong, might
> need DHCPv4.

  Yes.  I'm not sure that VLANs are a limited resource, or are difficult to provision.  GVRP has existed for a while...

  Alan DeKok.

v2.23.0 | Report a Bug | By Email