On Sep 10, 2023, at 6:56 PM, Alan DeKok wrote:
> There have been long discussions about not tying EAP to DHCP. I forget
> which RFC it is, but there's an IAB architectural document which says this is
> a bad idea.
https://www.rfc-editor.org/rfc/rfc5505.html
The use of @eap.arpa is explicit
Alan DeKok wrote:
>> I think that this is a mistake to be so specific.
>> I don't think the supplicant should know/care, at this point, what kind
of
>> access it is going to get. I liked what we we had done with
eap-onboarding
>> where you get limited network, and then if DHCP
On Sep 11, 2023, at 12:38 PM, Michael Richardson wrote:
> There is no connection here.
> EAP(nobody) gets you a useable L2.
> L2 makes DHCP possible. There is no link, and they are not tied.
I suspect the kind of provisioning you need is related to the kind of network
access you get.
The a
