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

Alan DeKok <alan.dekok@inkbridge.io> Wed, 13 May 2026 16:04 UTC

Return-Path: <alan.dekok@inkbridge.io>
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 C3DCBEDD0619; Wed, 13 May 2026 09:04:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778688280; bh=HU4g9dJfC3TTIhDDex8t66iiPPcGaerRkBsLg7sZ+4g=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=apl1Y8qn+ai6mjYyPirkjpCFOam+ZbrWIw0D0pm1Ept42osWsKdG02iQI31knPxJO gns8w9FqiBmKiuwPJUCywNXztI+Vzk2AvVV/UCaX5BGWNLHY2Fvnxs77DEPOD2Dowy tdJuMTS7emPA/uzfGr5lGnfIBZ9/BndhqnORPe7w=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=inkbridge.io header.b="XR5Au80r"; dkim=pass (2048-bit key) header.d=inkbridge.io header.b="kAxVgXGG"
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 HnmIMS3GQm7E; Wed, 13 May 2026 09:04:36 -0700 (PDT)
Received: from mail2.networkradius.com (mail2.networkradius.com [184.95.211.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4D9BBEDD05F4; Wed, 13 May 2026 09:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=inkbridge.io; s=sep2024; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VMyoRDIaKN6Xq43CgnB4lYiCmjlIIZOitXtg5GPDCOk=; b=XR5Au80rb9Pnfxoore9Ft7k3xF w+Cr3PclbD5qqNZU1fkiccICM3Mw/a0BUPrwoe0+FiZjriZGBZb0t1OfADLvcYtx/bebD+EnqoLvJ Jnj4e+t1pwQhu5SPWMqx/pwonENbkXTFXFp8Sw967cGvkf/abb4+0Yam5P4PAPv0o/ixlBZF2eAV1 tKTxhtG4rxuCm97gdbx+s3bCCsUp8CQPyPH8dSoohmpnb6nQiYPTUu+8VlyLCe8e7OaYrhGwqvqLW zv4csRmYUylcUSPOCbLFkBNqDAGcNopi9ZYYdOo5xWtUf/NHZ9/8kJ+HcvI//s9PlL5yufucKzTdR MQQ+Ue+Q==;
Received: from mail.servers.fr.internal.networkradius.com ([192.168.42.56]:56198 helo=mail.networkradius.com) by mail2.networkradius.com with esmtp (Exim 4.97) (envelope-from <alan.dekok@inkbridge.io>) id 1wNC4R-000000007zT-3Rav; Wed, 13 May 2026 16:04:28 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inkbridge.io; s=sep2024; t=1778688267; bh=VMyoRDIaKN6Xq43CgnB4lYiCmjlIIZOitXtg5GPDCOk=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=kAxVgXGGP5da8idaxPczrDesKMsGLNSS6Q2zwprE8jd3sfsGheR3y9cXjNx1Xy+9o 20Ly9kYldxwF+qXLObPWwsMkqNGK6S1+0QXLcZhp6UdDIuu8KXgt1D1Z9vZjjzQa8C VlUav9Ft79tcZlKSnwuC33G2x36H/p3OCrJBU8jH4jCD3yWZTDMNIRo6Ya/jrw9922 ayNkS3R8gXqSCI6J5U7xw/4uh3FKtCwPkV0SPTgJg2U1JR8Bu/GPeS6kNbqYGXO0oA doO64ay0mFtMXU0JUD+jyvKg90jfrkAC8qcMLfSk0LQwGdWf2nOMwdGlnsc2ulVHtu 7pMXTtP+DKvvw==
Received: from smtpclient.apple (unknown [72.138.118.251]) by mail.networkradius.com (Postfix) with ESMTPSA id AB7DA1B9; Wed, 13 May 2026 16:04:25 +0000 (UTC)
Content-Type: multipart/signed; boundary="Apple-Mail=_278A7A51-DD17-4ECA-93F6-AE44E213628B"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81.1.4\))
From: Alan DeKok <alan.dekok@inkbridge.io>
In-Reply-To: <B1A1F188-39A5-4ABA-93EC-302295AF1E40@staff.rfc-editor.org>
Date: Wed, 13 May 2026 09:04:13 -0700
Message-Id: <049BC8C8-181A-4179-906F-2901DD5EF9A6@inkbridge.io>
References: <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> <341B1A31-FAEA-4986-8B62-CF49D09E4902@staff.rfc-editor.org> <CAP7zK5ZR7cTB0utg5iQji1n+Kw8pWVPVYrfwiLGR--bLUm==ZQ@mail.gmail.com> <AC1264A1-D72B-45C8-A296-DD26ADC1D659@staff.rfc-editor.org> <CAP7zK5b4NfpK+2nvgnYeFe4vL4zZ8P8H0Su8+uXgdNZ6WEQXCQ@mail.gmail.com> <F0D5B3E8-3F86-4A00-932F-82C9BD9808D9@inkbridge.io> <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> <AAF55262-E5E9-47E1-8073-17BA2C59CD9D@staff.rfc-editor.org> <E0088D9D-7132-4947-8B42-559C1BAC2833@inkbridge.io> <B1A1F188-39A5-4ABA-93EC-302295AF1E40@staff.rfc-editor.org>
To: Megan Ferguson <mferguson@staff.rfc-editor.org>
X-Mailer: Apple Mail (2.3826.700.81.1.4)
Message-ID-Hash: 6XMOAQ4ZXWNN45MLNNZYPKGDNBFB6EAC
X-Message-ID-Hash: 6XMOAQ4ZXWNN45MLNNZYPKGDNBFB6EAC
X-MailFrom: alan.dekok@inkbridge.io
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: Dhruv Dhody <dd@dhruvdhody.com>, Dhruv Dhody <iab-chair@iab.org>, rfc-editor@rfc-editor.org, emu-ads@ietf.org, emu-chairs@ietf.org, peter@akayla.com, paul.wouters@aiven.io, auth48archive@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [auth48] Re: 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/9zaO3srfpK_NlYbRKd_TuijQZjs>
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>

  It's Maria Ines Robles.  "Ignes" is a typo.  Please update the acknowledgements with her preferred name, and it's good to go.

> On May 13, 2026, at 8:57 AM, Megan Ferguson <mferguson@staff.rfc-editor.org> wrote:
> 
> Alan,
> 
> A quick pre-publication question:
> 
> In the Acknowledgments, I see "Ignes Robles”.  I happen to be working on another document that is acknowledging a “Maria Ines Robles” (who confirmed she prefers Maria Ines instead of just Ines just this week).  Is this the same person or should this remain Ignes?
> 
> Thank you.
> 
> Megan Ferguson
> RFC Production Center
> 
>> On May 11, 2026, at 3:52 PM, Alan DeKok <alan.dekok@inkbridge.io> wrote:
>> 
>> It's all good.  Thanks!
>> 
>>> On May 11, 2026, at 2:39 PM, Megan Ferguson <mferguson@staff.rfc-editor.org> wrote:
>>> 
>>> Hi Alan,
>>> 
>>> Thanks for sending.  We’ve rolled this change into our files linked below and updated your AUTH48 status to “Approved”.  We will send a separate request to IANA to update any necessary registry information to match the document.
>>> 
>>> One further pointer, we have updated the citations/references:
>>> 
>>> Was:
>>> [EAP-METHOD]IANA, "Extensible Authentication Protocol (EAP) Registry", <https://www.iana.org/assignments/eap-numbers>. 
>>> 
>>> [EAPREG]IANA, "Extensible Authentication Protocol (EAP) Registry", <https://www.iana.org/assignments/eap-numbers>. 
>>> 
>>> Now (just one entry with the sub-registry names in running text):
>>> [EAP-REG]IANA, "Extensible Authentication Protocol (EAP) Registry", <https://www.iana.org/assignments/eap-numbers>.
>>> 
>>> Apologies for not spotting that these references were otherwise identical before.  If you have any objections, please let us know.  Otherwise, once we hear back from IANA, this document will be ready to move 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 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.
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>