No, PANA would not require changes to the DHCP client behavior if the
first hop relay agent is configured to discard DHCP messages until
PANA authentication is complete. Presumably whatever mechanism is
used to allow IP traffic after PANA authentication could also trigger
the relay agent to allow DHCP forwarding.
Of course, I'm speculating wildly here about implementation details
without the benefit of any system architecture docs...
- Ralph
On Nov 5, 2007, at Nov 5, 2007,8:33 PM, Richard Pruss wrote:
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?
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
