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 <[email protected]> > 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 <[email protected]> wrote: >> >> It's all good. Thanks! >> >>> On May 11, 2026, at 2:39 PM, Megan Ferguson >>> <[email protected]> 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 <[email protected]> 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 >>>>> <[email protected]> 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 <[email protected]> wrote: >>>>>> >>>>>> Thanks. Some minor nits: >>>>>> >>>>>> Section 4.2 >>>>>> >>>>>> OLD >>>>>> This document defines an NAI called "[email protected]", whi >>>>>> >>>>>> NEW >>>>>> This document defines an NAI "[email protected]", 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 >>>>>> "[email protected] <mailto:[email protected]>" >>>>>> >>>>>> >>>>>> The [IEEE802.1X] reference can be updated to point to the 2020 version. >>>>>> >>>>>> >>>>>>> On May 5, 2026, at 8:16 PM, Megan Ferguson >>>>>>> <[email protected]> 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 <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> On May 5, 2026, at 12:54 PM, Dhruv Dhody <[email protected]> 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. >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
signature.asc
Description: Message signed with OpenPGP
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
