This update includes guidelines for DNS operators and implementors. > Begin forwarded message: > > From: internet-dra...@ietf.org > Subject: New Version Notification for draft-dekok-emu-eap-arpa-01.txt > Date: February 25, 2024 at 5:23:32 PM EST > To: "Alan DeKok" <al...@freeradius.org> > > A new version of Internet-Draft draft-dekok-emu-eap-arpa-01.txt has been > successfully submitted by Alan DeKok and posted to the > IETF repository. > > Name: draft-dekok-emu-eap-arpa > Revision: 01 > Title: The eap.arpa domain and EAP provisioning > Date: 2024-02-25 > Group: Individual Submission > Pages: 14 > URL: https://www.ietf.org/archive/id/draft-dekok-emu-eap-arpa-01.txt > Status: https://datatracker.ietf.org/doc/draft-dekok-emu-eap-arpa/ > HTML: https://www.ietf.org/archive/id/draft-dekok-emu-eap-arpa-01.html > HTMLized: https://datatracker.ietf.org/doc/html/draft-dekok-emu-eap-arpa > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-dekok-emu-eap-arpa-01 > > Abstract: > > This document defines the eap.arpa domain as a way for EAP peers to > signal to EAP servers that they wish to obtain limited, and > unauthenticated, network access. EAP peers leverage user identifier > portion of the Network Access Identifier (NAI) format of RFC7542 in > order to describe what kind of provisioning they need. A table of > identifiers and meanings is defined. > > > > The IETF Secretariat > >
_______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
