On May 17, 2025, at 7:27 PM, John C Klensin <[email protected]> wrote: > ... I'd encourage the WG, the IESG, > and the IAB to think carefully about whether there is any chance of > additional EAP-related identifier groups being needed and, if there > is even a slight possibility, moving toward an eap.arpa with a > subdomain for this application ("realm"?) and the potential for > additional subdomains as needed.
The intent of this specification was to have only one "eap.arpa". There would then should be no need for additional domains for "eap-*.arpa". This can be made clearer in the document if necessary. Due to the way EAP works, there is a need to partition the eap.arpa domain by EAP method. So "tls.eap.arpa", "peap.eap.arpa", "fast.eap.arpa", etc. Any additional functionality can be carried as either subdomains "foo.tls.eap.arpa", or as NAIs "[email protected] <mailto:[email protected]>". If the EMU WG needs additional functionality from the "eap.arpa" domain, then it's possible to create subdomains which are independent of existing EAP methods. e.g. "_function.eap.arpa". I'll take a pass at updating the document. There has been significant feedback from outside of EMU for it. This is unusual, but welcome. Alan DeKok. _______________________________________________ Emu mailing list -- [email protected] To unsubscribe send an email to [email protected]
