[auth48] [IANA #1451989] Re: [IANA] AUTH48: RFC-to-be 9965 <draft-ietf-emu-eap-arpa-10> for your review

Amanda Baber via RT <iana-matrix@iana.org> Tue, 12 May 2026 19:27 UTC

Return-Path: <iana-shared@iana.org>
X-Original-To: auth48archive@mail2.ietf.org
Delivered-To: auth48archive@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 33920ED4FA8E; Tue, 12 May 2026 12:27:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778614043; bh=GR5i5clcSuLxkQB8k+1Y3tmF5u/h95P9pmYmldlIs+Q=; h=Subject:From:Reply-To:In-Reply-To:References:To:CC:Date; b=Cy09o/9bu3wjHmPJo+FQ1E+8W2IKMJ++dDfIHItZngr0WyCcohaazy0PMWVNEI+Ex sh36ke1exd6wZ81n0HmJxajGn4xl5mZufaljXis8G/qysGEpc09HRI6f+Pc3y72XDT t8dPesQLIzNKtUoSIq/TvCKQHQ5E2z0T0YCygxjo=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.396
X-Spam-Level:
X-Spam-Status: No, score=-4.396 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_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=iana.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cv1av-jwMvC1; Tue, 12 May 2026 12:27:18 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2B84BED4FA7B; Tue, 12 May 2026 12:27:18 -0700 (PDT)
Received: from request7.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 80288E1B35; Tue, 12 May 2026 19:27:17 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.lax.icann.org 80288E1B35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iana.org; s=202509s; t=1778614037; bh=BiLBcgVED/z/pe2omYoE5B/FNNBHxrYf4v5ssR47AiA=; h=Subject:From:Reply-To:In-Reply-To:References:To:CC:Date:From; b=U8m930xyKVdBgO5IKamElLW2PsmZVG1uYQp1Q2geazm+G/P9A4G9EHFCffHp6z3ig W5TZPCgmXlvOecIAFcGQpASMa3xANujutkR/HYVeHMu/QyYPvNe5DpR2k8nJ6wq6I7 NQFPEFinbGXgHORj5YtA0wsts2tzSCDHHmZCjWzA=
Received: by request7.lax.icann.org (Postfix, from userid 48) id 7C8B7C097508; Tue, 12 May 2026 19:27:17 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-matrix@iana.org>
In-Reply-To: <F03D4A0D-B7F6-4229-8165-62C9F1273389@staff.rfc-editor.org>
References: <RT-Ticket-1451989@icann.org> <20260428045200.5BB6B2CCE7A@rfcpa.rfc-editor.org> <AE4F1940-DED6-4B7E-B409-A7E9AA6103A7@inkbridge.io> <4DE71DD0-6566-4F50-AE4B-C90A4390956C@staff.rfc-editor.org> <CAP7zK5Y=YKNPVVsGU4vNGBCQpMchGDpwcyiKzBQ+zKofAU9gYg@mail.gmail.com> <21BDF298-48C5-449F-96E2-235A4A779D3A@staff.rfc-editor.org> <984E53FC-C70C-4CD6-BD0B-119D65F708D1@inkbridge.io> <9069D129-4FBE-43AD-80B4-12F64CCB4ADF@staff.rfc-editor.org> <BE02B411-5A7B-4F32-A08F-BAC8284A9145@inkbridge.io> <F03D4A0D-B7F6-4229-8165-62C9F1273389@staff.rfc-editor.org>
Message-ID: <rt-5.0.3-416774-1778614037-1171.1451989-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1451989
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
To: mferguson@staff.rfc-editor.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Tue, 12 May 2026 19:27:17 +0000
MIME-Version: 1.0
Message-ID-Hash: X7HOITIIDYM4O4C4PO3B6M3RJP2RCHWY
X-Message-ID-Hash: X7HOITIIDYM4O4C4PO3B6M3RJP2RCHWY
X-MailFrom: iana-shared@iana.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, peter@akayla.com, paul.wouters@aiven.io, iab-chair@iab.org, emu-chairs@ietf.org, emu-ads@ietf.org, dd@dhruvdhody.com, auth48archive@rfc-editor.org, alan.dekok@inkbridge.io
X-Mailman-Version: 3.3.9rc6
Reply-To: iana-matrix@iana.org
Subject: [auth48] [IANA #1451989] Re: [IANA] AUTH48: RFC-to-be 9965 <draft-ietf-emu-eap-arpa-10> for your review
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/n6tXeXx2lYjaJ3YV0BYwlXdKNmY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Owner: <mailto:auth48archive-owner@rfc-editor.org>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Subscribe: <mailto:auth48archive-join@rfc-editor.org>
List-Unsubscribe: <mailto:auth48archive-leave@rfc-editor.org>

Hi,

This change is complete:

https://www.iana.org/assignments/eap-numbers

thanks,
Amanda

On Mon May 11 21:36:54 2026, mferguson@staff.rfc-editor.org wrote:
> IANA,
> 
> We’d like to request the following update for uniformity with this
> document:
> 
> At https://www.iana.org/assignments/eap-numbers/eap-numbers.xhtml#eap-
> provisioning-ids, an update to the column heading:
> 
> Old:
> Method-Type
> 
> New:
>  Method Type
> 
> Please let us know when the updates have been completed.
> 
> Thank you.
> 
> Megan Ferguson
> RFC Production Center
> 
> > On May 10, 2026, at 5:03 AM, Alan DeKok <alan.dekok@inkbridge.io>
> > wrote:
> >
> > One last nit:
> >
> > OLD - Section 4
> > ...
> > Certificate Authorities (CAs) locally configured.
> >
> > NEW
> > ...
> > Certification Authorities (CAs) locally configured.
> >
> > I have no other comments.  The document is approved once the above
> > change is made.
> >
> >> On May 6, 2026, at 10:35 AM, Megan Ferguson <mferguson@staff.rfc-
> >> editor.org> wrote:
> >>
> >> Thanks, Alan.
> >>
> >> We have updated as suggested.  Let us know if any further changes
> >> are necessary.
> >>
> >> Once we have your approval, we will contact IANA with any changes to
> >> make their registries consistent with the document.
> >>
> >> The files have been posted here (please refresh):
> >> https://www.rfc-editor.org/authors/rfc9965.txt
> >> https://www.rfc-editor.org/authors/rfc9965.pdf
> >> https://www.rfc-editor.org/authors/rfc9965.html
> >> https://www.rfc-editor.org/authors/rfc9965.xml
> >>
> >> The diff files have been posted here (please refresh):
> >> https://www.rfc-editor.org/authors/rfc9965-diff.html
> >> https://www.rfc-editor.org/authors/rfc9965-rfcdiff.html (side by
> >> side)
> >> https://www.rfc-editor.org/authors/rfc9965-auth48diff.html
> >> https://www.rfc-editor.org/authors/rfc9965-auth48rfcdiff.html (side
> >> by side)
> >>
> >> The AUTH48 status page is available here:
> >> https://www.rfc-editor.org/auth48/rfc9965
> >>
> >> The AUTH48 cluster information is available here:
> >> https://www.rfc-editor.org/auth48/C558
> >>
> >> Thank you.
> >>
> >> Megan Ferguson
> >> RFC Production Center
> >>
> >>> On May 5, 2026, at 6:50 PM, Alan DeKok <alan.dekok@inkbridge.io>
> >>> wrote:
> >>>
> >>> Thanks.  Some minor nits:
> >>>
> >>> Section 4.2
> >>>
> >>> OLD
> >>> This document defines an NAI called "portal@tls.eap.arpa", whi
> >>>
> >>> NEW
> >>> This document defines an NAI "portal@tls.eap.arpa", whi
> >>>
> >>> The word "called" was added during the editorial process.  The NAI
> >>> isn't "called" something.  The document defines an NAI which has
> >>> the value "portal@tls.eap.arpa <mailto:portal@tls.eap.arpa>"
> >>>
> >>>
> >>> The  [IEEE802.1X] reference can be updated to point to the 2020
> >>> version.
> >>>
> >>>
> >>>> On May 5, 2026, at 8:16 PM, Megan Ferguson <mferguson@staff.rfc-
> >>>> editor.org> wrote:
> >>>>
> >>>> Alan and Dhruv,
> >>>>
> >>>> Thank you for your guidance.  We have cut the sentence as
> >>>> requested.
> >>>>
> >>>> Alan - Please let us know if the [IEEE802.1X] reference entry
> >>>> should be updated to point to the 2020 version (I believe we asked
> >>>> about this in the companion document).  And please let us know if
> >>>> any further updates to the document are necessary.
> >>>>
> >>>> Note - Once we have AUTH48 changes complete, we will send over any
> >>>> requests for IANA updates to IANA (prior to moving the document
> >>>> forward in the publication process).
> >>>>
> >>>> The files have been posted here (please refresh):
> >>>> https://www.rfc-editor.org/authors/rfc9965.txt
> >>>> https://www.rfc-editor.org/authors/rfc9965.pdf
> >>>> https://www.rfc-editor.org/authors/rfc9965.html
> >>>> https://www.rfc-editor.org/authors/rfc9965.xml
> >>>>
> >>>> The diff files have been posted here (please refresh):
> >>>> https://www.rfc-editor.org/authors/rfc9965-diff.html
> >>>> https://www.rfc-editor.org/authors/rfc9965-rfcdiff.html (side by
> >>>> side)
> >>>> https://www.rfc-editor.org/authors/rfc9965-auth48diff.html
> >>>> https://www.rfc-editor.org/authors/rfc9965-auth48rfcdiff.html
> >>>> (side by side)
> >>>>
> >>>> The AUTH48 status page is available here:
> >>>> https://www.rfc-editor.org/auth48/rfc9965
> >>>>
> >>>> The AUTH48 cluster information is available here:
> >>>> https://www.rfc-editor.org/auth48/C558
> >>>>
> >>>> Thank you.
> >>>>
> >>>> Megan Ferguson
> >>>> RFC Production Center
> >>>>
> >>>>> On May 5, 2026, at 11:32 AM, Alan DeKok <alan.dekok@inkbridge.io>
> >>>>> wrote:
> >>>>>
> >>>>> On May 5, 2026, at 12:54 PM, Dhruv Dhody <dd@dhruvdhody.com>
> >>>>> wrote:
> >>>>>> Based on this, the best way forward is to remove the sentence:
> >>>>>> “NOTE: As the controller of the arpa domain, the IAB has
> >>>>>> approved the allocation of eap.arpa.”
> >>>>>> Please let us know if you see any concerns with that.
> >>>>>
> >>>>> +1 from me.
> >>>>>
> >>>>> Alan DeKok.
> >>>>>
> >>>>
> >>>
> >>
> >