IETF Logo Mail Archive

Re: [Emu] Adoption call for eap.arpa

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 22 March 2024 03:58 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 1D7EFC14F5F9 for <emu@ietfa.amsl.com>; Thu, 21 Mar 2024 20:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 WdEOVeiXwCg3 for <emu@ietfa.amsl.com>; Thu, 21 Mar 2024 20:58:15 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (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 79B5DC14F5F4 for <emu@ietf.org>; Thu, 21 Mar 2024 20:58:14 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [IPv6:2001:67c:370:1998:183d:bb4b:6aab:5819]) by relay.sandelman.ca (Postfix) with ESMTPS id 3D8611F4A8 for <emu@ietf.org>; Fri, 22 Mar 2024 03:58:13 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="DlU3rRM6"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id AC288A190E; Fri, 22 Mar 2024 13:58:10 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711079890; bh=gdXJNKP7kobyQayRYTaspyrucon936STsE61eu+3cVY=; h=From:To:Subject:In-reply-to:References:Date:From; b=DlU3rRM658UF5xjGTKztAtQ2WfcVeXtdaN7AJ0K9kWc6GPadmUFmB52L9LALO5z8T O/PEMqHSTctY4aZWYH92qy69OuVNIkVc2GuuyyzC4EWbKNO4Yv+a2/i2HDWsT4tPHQ +g6Q0zJXcgsxzVJfwX5srsjVjTdalU86H+0QwHeLUXmmYsFaWod6DbC2KajemmISxB GBraUR16v71qCe+uQcjdeOQ18PyUnwZVr7gBwhauXti1ZtcySn+kaeDnamEjYsMtEA BzK8NUOeANx5gMPmS2FuL6LJtiW+JNUpQ6oU8SlWQ8ONg4ybQeHjvKmaTRcN+/njJ8 NYYoBE+pa1tuw==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id A9F60A0C77 for <emu@ietf.org>; Fri, 22 Mar 2024 13:58:10 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "emu@ietf.org" <emu@ietf.org>
In-reply-to: <06836614-D52C-4CC4-B26C-1D66BC049C55@deployingradius.com>
References: <F1FD786F-D0B1-494B-B384-95BBB4B7790B@akayla.com> <6752380a-0155-4ba4-9aee-107162538a4b@iki.fi> <06836614-D52C-4CC4-B26C-1D66BC049C55@deployingradius.com>
Comments: In-reply-to Alan DeKok <aland@deployingradius.com> message dated "Fri, 22 Mar 2024 10:50:41 +1000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 22 Mar 2024 13:58:10 +1000
Message-ID: <235509.1711079890@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/9Qu69C4zzLIio8XvjA6zag3mm6w>
Subject: Re: [Emu] Adoption call for eap.arpa
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, 22 Mar 2024 03:58:20 -0000

Alan DeKok <aland@deployingradius.com> wrote:
    > 1. Instead of servers deciding the EAP method based on the username
    >part of the NAI, the EAP method could be decided based on the sub domain
    >under eap.arpa in the realm portion of the NAI. Thus a peer wanting to
    >be provisioned would use provisioning@noob.eap.arpa or
    >provisioning@tls.eap.arpa depending on whether it supports: EAP-NOOB or
    >EAP-TLS for provisioning. Leaving the username semantics to individual
    >provisioning drafts (example: draft-ietf-emu-bootstrapped-tls) might be
    >beneficial in the long run as explained below.

    > That's a good idea.  My once concern is if IANA / IAB would allow for a
    > separate sub-registry for the subdomains, and allow EMU to control that
    > registry.

I think its an IAB question.  IANA with implement whatever we ask for.
It would be EMU's Expert Reviewers that would decide, I guess.
It's late in the week to pigeon hole someone, but ... maybe we can find
someone.

Is a sub-domain the only technical solution?
I'm sure we will need to answer that.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.23.0 | Report a Bug | By Email