> Bernard Aboba wrote, around 6/11/07 11:11 AM: > >> But let's have a fair evaluation. If we decide that PANA fits the > >> requirements perfectly, the above objections apply equally well to it. > > > > Actually, I'm not clear that the objections apply equally well to PANA. > > > > On the Windows platform at least, there is an API that permits > > integration of new EAP lower layers. That means that PANA support can > > be added by a third party with no required changes to the operating > > system. > > > > Since DHCP/EAP requires change to the DHCP state machine, the work > > required would be considerably greater. > > > > > > > Does PANA not also require changes to the DHCP state machine to stop it > running until PANA has authenticated on the link local address?
You don't have to stop the DHCP state machine. PANA authentication would normally complete while DHCP client is still retrying. In case it does not, then all we need to do is to trigger the DHCP client to trying again. No changes to the DHCP state machine. Another solution for the dealing with legacy hosts can be to not gate the DHCP configuration, but still require PANA authentication. Alper _______________________________________________ Int-area mailing list [email protected] https://www1.ietf.org/mailman/listinfo/int-area
