IETF Logo Mail Archive

Re: [Emu] Adoption call for eap.arpa

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 22 March 2024 05:54 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 948A4C14F6BF for <emu@ietfa.amsl.com>; Thu, 21 Mar 2024 22:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_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, 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 M_H7AdYL5EVS for <emu@ietfa.amsl.com>; Thu, 21 Mar 2024 22:54:07 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 83DCAC14F69E for <emu@ietf.org>; Thu, 21 Mar 2024 22:54:06 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [IPv6:2001:67c:370:1998:11ba:33e3:ceb1:aeac]) by relay.sandelman.ca (Postfix) with ESMTPS id 4436F1F4A8; Fri, 22 Mar 2024 05:54:05 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="kkTZOUAh"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 94CF0A190E; Fri, 22 Mar 2024 15:54:02 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711086842; bh=qz3HFui2F0+MhoCL0iOMlcQUtVyopmaaGcWFejaJC4g=; h=From:To:Subject:In-reply-to:References:Date:From; b=kkTZOUAhVsw8XeaySNQtpSAs2pyrA1dxMCB4SHtMy3i2f2i1et/j7IlYxYcnMqs7f 9OqURkQSn+aI+egBN5gdBNaBuIQ7VLntaKM+UzUlanpyoAxkcCQhZj9Iz5bRWCEjyZ 99UCpA9jWb4HTunYCnjmTbDGG52LrCGXYoTnkHOIgljakL3Nt9yWmPa1wgzl70Gt1r y3pCY1SMwaC6vA1FHL+7iAFTH7KvzRY8jrihBnBBFHNJ0rUBVhZrQhykLVyrFhc7Iu fKPaKwLTJykkyI2Wi0B0JhHepUcTLkw5lWftoCfFX1fN9G11Uivq7mVaPcnDKDYvwU MVGMf0c6Z+8RA==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 924C4A0C77; Fri, 22 Mar 2024 15:54:02 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mohit Sethi <mohit@iki.fi>, Alan DeKok <aland@deployingradius.com>, "emu@ietf.org" <emu@ietf.org>
In-reply-to: <4a5b64fc-5dfd-471b-b672-eb6a2ea65e59@iki.fi>
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> <FD4D848F-0E37-48D8-913D-4A7C2063F33C@deployingradius.com> <4a5b64fc-5dfd-471b-b672-eb6a2ea65e59@iki.fi>
Comments: In-reply-to Mohit Sethi <mohit@iki.fi> message dated "Fri, 22 Mar 2024 11:08:19 +0530."
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 15:54:02 +1000
Message-ID: <241138.1711086842@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Ti75E3pNCD0exeBly75tY8l-yFs>
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 05:54:12 -0000

Mohit Sethi <mohit@iki.fi> wrote:
    > As far as I can tell, we will not be the first ones using such a
    > scheme. ".home.arpa." defined in RFC 8375
    > (https://www.rfc-editor.org/rfc/rfc8375.html) allows sub domains. It says:
    > "For an administrative domain that uses subdomains of 'home.arpa.', such as a
    > homenet, the recursive resolvers provided by that domain will be able to
    > answer queries for subdomains of 'home.arpa.'"

It's not at all the same thing :-)
home.arpa is a real anchor which home routers can serve names into using DNS.
(Replacing ".local" [which implies mDNS], and .lan, which some home routers use)

    > We are taking a more conservative approach where subdomains need expert
    > review and registration before they are allocated and can be used in
    > deployments.

I would not characterize it this way at all.
I suspect we can have what we want, we just need to explain it to the IAB
well enough.  Unfortunately too late in the week for a hallway conversation.
I found some IESG to talk to at the last break, but no IAB.

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

v2.23.0 | Report a Bug | By Email