Hi Alan,
>> An interesting usecase for EAP-SASL with all this would be WiFi and LAN
>> authentication (EAPOL or 802.1x) passed over Diameter to *any* domain on
>> the Internet, and receiving back tunnel information.
>
> Or RADIUS
That's what everyone is thinking ;-)
The reason for Diamete
On Apr 18, 2020, at 2:05 PM, Rick van Rein wrote:
> The reason for Diameter is that it scales up to the Internet (in terms
> of connection pooling / efficiency and in terms of security). RADIUS is
> really useful for internal networks, but becomes rather clumsy when
> crossing the Internet -- it
Hi,
This is turning into a discussion about RADIUS versus Diameter. Please
note that this is not implied by my proposal of SASL over EAP; that I
merely want to be somewhat clear about how the use case could look.
I do thank you for evaluating these details, and am aware that the
anticipated adva
The EMU WG has placed draft-aura-eap-noob in state
Candidate for WG Adoption (entered by Joseph Salowey)
The document is available at
https://datatracker.ietf.org/doc/draft-aura-eap-noob/
___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman
This is a call for adoption of draft-aura-eap-noob-08.txt [1] as a working
group item. This draft has been discussed in several IETF meetings and
would be the starting point for the working group deliverable for an EAP
method based on "mutual authentication between a peer and a server that is
base
On Apr 18, 2020, at 3:55 PM, Rick van Rein wrote:
> This is turning into a discussion about RADIUS versus Diameter.
I'm suggesting that since EAP runs over AAA protocols, it helps to understand
where each AAA protocol is used, and why.
The alternative is to have a solution which isn't appli
