This revision addresses review comments from Éric Vyncke.

  The changes are mainly editorial and using consistent terminology.

> On Aug 27, 2025, at 4:27 PM, [email protected] wrote:
> 
> Internet-Draft draft-ietf-emu-eap-arpa-09.txt is now available. It is a work
> item of the EAP Method Update (EMU) WG of the IETF.
> 
>   Title:   The eap.arpa. domain and EAP provisioning
>   Author:  Alan DeKok
>   Name:    draft-ietf-emu-eap-arpa-09.txt
>   Pages:   25
>   Dates:   2025-08-27
> 
> Abstract:
> 
>   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 which use the Network Access Identifier (NAI) format of
>   RFC 7542.  A table of identifiers and meanings is defined, which
>   includes entries for RFC 9140.
> 
>   This document updates RFC5216 and RFC9190 to define an
>   unauthenticated provisioning method.  Those specifications suggested
>   that such a method has possible, but they did not define how it would
>   be done.  This document also updates RFC9140 to deprecate "eap-
>   noob.arpa", and replace it with "[email protected]"
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-emu-eap-arpa/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-emu-eap-arpa-09.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-emu-eap-arpa-09
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> Emu mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
Emu mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to