Stig Venaas wrote, around 24/10/07 7:23 PM:
It's not as simple as just putting credentials into option 82 though.
For one thing there are strict limits on the size of DHCP messages that
will limit what EAP or other mechanisms you can use. When the EAP
MTU is too small for the EAP message, you need multiple requests and
responses to transport the message. This is not possible without
major DHCP changes. Hence you are not free to use what EAP mechanisms
or credentials you like without major changes to DHCP. While with say
PANA you could do that.
Stig section 6.3 of the currently posted -01 draft addresses the size
issue of EAP in some detail, it is not clear if you are saying the
proposed mechanism would not work.
Regardless of the mechanism if one thinks of this from the
implementation it should be no big deal as for EAP and RADIUS one has to
chop EAP into small enough chunks to get through limitations in RADIUS
(<253 bytes). While DHCP has similar problems (<255 bytes), and one
could can expect that most networking companies would have implemented
the lower common denominator of RADIUS here.
Regards,
Ric
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
