> 1) Moving to RFC 3961 MIC tokens +1
> 3) Moving to RADIUS attributes from draft-ietf-radext-radius-extensions I agree this is more elegant, particularly for fragmented attributes. OTOH it may make it may restrict the use of existing RADIUS client implementations (although, I suppose, as extended attributes are still valid RADIUS attributes, it could be implemented by the mechanism itself). -- Luke _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
