[Emu] Adoption call for eap.arpa
Peter Yee <peter@akayla.com> Thu, 07 March 2024 22:38 UTC
Return-Path: <peter@akayla.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 DDBACC14F6A8 for <emu@ietfa.amsl.com>; Thu, 7 Mar 2024 14:38:31 -0800 (PST)
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_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=akayla.com
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 e0l7HCjx95FS for <emu@ietfa.amsl.com>; Thu, 7 Mar 2024 14:38:27 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 06A27C14F6AF for <emu@ietf.org>; Thu, 7 Mar 2024 14:38:24 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id F074B1B25A9 for <emu@ietf.org>; Thu, 7 Mar 2024 17:38:23 -0500 (EST)
Received: from [192.168.168.205] (server.houseofyee.com [173.8.184.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id ABFCF1B2050 for <emu@ietf.org>; Thu, 7 Mar 2024 17:38:23 -0500 (EST)
User-Agent: Microsoft-MacOutlook/16.82.24021813
Date: Thu, 07 Mar 2024 14:38:21 -0800
From: Peter Yee <peter@akayla.com>
To: "emu@ietf.org" <emu@ietf.org>
Message-ID: <F1FD786F-D0B1-494B-B384-95BBB4B7790B@akayla.com>
Thread-Topic: Adoption call for eap.arpa
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akayla.com; h=date:subject:from:to:message-id:mime-version:content-type:content-transfer-encoding; s=pair-202402141610; bh=ubkHAJtOGsCmT8qNhcxYhfyHnjpVxkloMeR4FSDYb5Q=; b=NZmIG/d8pv/sF3XZp1dU6OOHpnpdzkDBfd8F2EiX9eByfuLUY4F6nxPCufo+mtaAKwWsF0Zz3TxZfxLnW4BGUXWEfdX65DJNbY7dBBJSlsXOGe0FB3yCLQfBOPAJmJx51wFTPVwmUfqai5fDUDes7qq4yF7KVN0HcXc/VxNlPAe0UEgv97bxDxMBarDIpleKE51xk5axyur1HHkMK9gEuDtj5YHy9Ek+BeIXXyvkiLkPdF3ya+iUsZt09Zi57TmnjhezqTZyKzzutGikQBXiPaQi9Wk3YWBI0jKwakDXJdF6+3D5rxv60HOfjP4ajVKlPhlOSyvF9oDIsIk1vBaNHg==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/aXj3iPJIwHppFoiKT5y3XO4My6w>
Subject: [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: Thu, 07 Mar 2024 22:38:32 -0000
This is an adoption call for the eap.arpa Internet-Draft (draft-dekok-emu-eap-arpa). This is an ancillary draft that Alan DeKok briefed during the Prague (IETF 118) meeting. Seeing as it primarily exists as a forward-looking extraction of certain descriptive material and IAB .arpa domanrequests from other EMU documents, we consider it within the scope of the WG charter. Alan did a recent minor update to the document and will speak briefly about it during IETF 119. With that said, your WG chairs would appreciate hearing your feedback on whether this document is adopted or not. While it's not critical to adopt, it really simplifies the domain registration for things like TLS-POK and would have been great back when we did EAP-NOOB. We are particularly interested in hearing from parties who are willing to review the specification. So, if you've got interest in seeing the work adopted, please formalize that by responding to the EMU mailing list with your position. The deadline for feedback is March 21st. Yes, that's during IETF 119 but after the EMU time slot, so hopefully you will have formed an opinion by then, if not sooner. We hope to hear from lots of you! Joe and Peter 1) https://datatracker.ietf.org/doc/draft-dekok-emu-eap-arpa/
- [Emu] Adoption call for eap.arpa Peter Yee
- Re: [Emu] Adoption call for eap.arpa Michael Richardson
- Re: [Emu] Adoption call for eap.arpa Jan-Frederik Rieckers
- Re: [Emu] Adoption call for eap.arpa Alexander Clouter
- Re: [Emu] Adoption call for eap.arpa Yanlei(Ray)
- Re: [Emu] Adoption call for eap.arpa Alexander Clouter
- Re: [Emu] Adoption call for eap.arpa Jan-Frederik Rieckers
- Re: [Emu] Adoption call for eap.arpa Alexander Clouter
- Re: [Emu] Adoption call for eap.arpa Michael Richardson
- Re: [Emu] Adoption call for eap.arpa Alan DeKok
- Re: [Emu] Adoption call for eap.arpa Heikki Vatiainen
- Re: [Emu] Adoption call for eap.arpa Mohit Sethi
- Re: [Emu] Adoption call for eap.arpa Alan DeKok
- Re: [Emu] Adoption call for eap.arpa Mohit Sethi
- Re: [Emu] Adoption call for eap.arpa Michael Richardson
- Re: [Emu] Adoption call for eap.arpa Alan DeKok
- Re: [Emu] Adoption call for eap.arpa Michael Richardson
- Re: [Emu] Adoption call for eap.arpa Mohit Sethi