hi, this document was reposted. I went through and edited out parts that are now replaced by ietf-emu-eap-arpa. Maybe "Use of eap.arpa" section should go.
I didn't get the IANA Considerations right. In reading the ietf-emu-eap-arpa IANA/Designated Expert considerations, I was uncertain what this document needs for NAI. Maybe it's [email protected]? [email protected]? Or is it a new foo.eap.arpa. I don't think so, because it assumes EAP-TLS is used. I'm working on slides. [email protected] wrote: > A new version of Internet-Draft > draft-richardson-emu-eap-onboarding-04.txt has been successfully > submitted by Michael Richardson and posted to the IETF repository. > Name: draft-richardson-emu-eap-onboarding Revision: 04 Title: EAP > defaults for devices that need to onboard Date: 2025-07-06 Group: > Individual Submission Pages: 10 URL: > https://www.ietf.org/archive/id/draft-richardson-emu-eap-onboarding-04.txt > Status: > https://datatracker.ietf.org/doc/draft-richardson-emu-eap-onboarding/ > HTML: > https://www.ietf.org/archive/id/draft-richardson-emu-eap-onboarding-04.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-richardson-emu-eap-onboarding > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-richardson-emu-eap-onboarding-04 > Abstract: > This document describes a method by which an unconfigured device can > use EAP-TLS to join a network on which further device onboarding, > network attestation or other remediation can be done. While RFC 5216 > supports EAP-TLS without a client certificate, that document defines no > method by which unauthenticated EAP-TLS can be used. This draft > addresses that issue. > The IETF Secretariat
signature.asc
Description: PGP signature
_______________________________________________ Emu mailing list -- [email protected] To unsubscribe send an email to [email protected]
