A new Request for Comments is now available in online RFC libraries.
RFC 9965
Title: The eap.arpa. Domain and Extensible
Authentication Protocol (EAP) Provisioning
Author: A. DeKok
Status: Standards Track
Stream: IETF
Date: May 2026
Mailbox: [email protected]
Pages: 21
Updates: RFC 5216, RFC 9140, RFC 9190
I-D Tag: draft-ietf-emu-eap-arpa-10.txt
URL: https://www.rfc-editor.org/info/rfc9965
DOI: 10.17487/RFC9965
This document defines the eap.arpa. domain for use only in Network
Access Identifiers (NAIs) as a way for Extensible Authentication
Protocol (EAP) peers to signal to EAP servers that they wish to
obtain limited, and unauthenticated, network access. EAP peers
signal which kind of access is required via certain predefined
identifiers that use the NAI format of RFC 7542. A table of
identifiers and meanings is defined, which includes entries for RFC
9140.
This document updates RFCs 5216 and 9190 to define an unauthenticated
provisioning method. Those specifications suggest that such a method
is possible, but they do not define how it would be done. This
document also updates RFC 9140 to deprecate "eap-noob.arpa" and
replace it with "@noob.eap.arpa".
This document is a product of the EAP Method Update Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
