IETF Logo Mail Archive

Re: [Emu] Adoption call for eap.arpa

Alan DeKok <aland@deployingradius.com> Fri, 22 March 2024 04:00 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 51F25C14F69E for <emu@ietfa.amsl.com>; Thu, 21 Mar 2024 21:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_DBL_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 aahxTqVuzrZ3 for <emu@ietfa.amsl.com>; Thu, 21 Mar 2024 21:00:27 -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 296A7C14F61F for <emu@ietf.org>; Thu, 21 Mar 2024 21:00:26 -0700 (PDT)
Received: from smtpclient.apple (dhcp-8619.meeting.ietf.org [31.133.134.25]) by mail.networkradius.com (Postfix) with ESMTPSA id ED3319D3; Fri, 22 Mar 2024 04:00:22 +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.120.41.1.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <235509.1711079890@dyas>
Date: Fri, 22 Mar 2024 14:00:19 +1000
Cc: "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD4D848F-0E37-48D8-913D-4A7C2063F33C@deployingradius.com>
References: <F1FD786F-D0B1-494B-B384-95BBB4B7790B@akayla.com> <6752380a-0155-4ba4-9aee-107162538a4b@iki.fi> <06836614-D52C-4CC4-B26C-1D66BC049C55@deployingradius.com> <235509.1711079890@dyas>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/CD2bcXxRiW6tVZpDxzI_jdvEGro>
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 04:00:31 -0000

On Mar 22, 2024, at 1:58 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 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.

  OK.

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

  I don't think it's the only technical solution.  But it's a very good one.

  If we don't use subdomains, then we have to use user portions in a well-known format.  e.g.

	provisioning.teap@eap.arpa

instead of

	provisioning@teap.eap.arpa

  I think the second looks clearer to me.

  Alan DeKok,

v2.23.0 | Report a Bug | By Email