Alan DeKok <[email protected]> wrote: > The only solution which entirely avoids the 253 octet limit is to just > define a DHCPv6-Options attribute in RADIUS. It can carry a blob of > DHCPv6 options, encoded as DHCPv6 options. This is behavior is > permitted by https://www.rfc-editor.org/rfc/rfc6158#section-3.2.4:
If I understand you correctly, the DHCPv6 option bytes would just be sliced
up into 253 byte fragments, and then reassembled into DHCPv6 options.
The radius part need not respect the DHCPv6 option boundaries, but can fill
each DHCPv6-Options with as much as the fragment as fits.
> Since the encoding is now DHCPv6 options, all limitations other than
> the 4K RADIUS "maximum packet size" limitation disappear. And many
> RADIUS implementations support packets larger than 4K, so that limit is
> not concrete either. The specification defining DHCPv6-Options could
> suggest that implementations SHOULD support 64K RADIUS packets.
Does Radius over TCP relax any of the 4K issue?
--
Michael Richardson <[email protected]> . o O ( IPv6 IΓΈT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
