The RADIUS RFC says nothing about the consistency requirements of the user
profile.
That is strictly a NAS implementation issue.
Note that the User-Service attribute is missing, leaving the user with no
forced service type. The NAS could either drop the user into a command
line interface, or a menu, and save the extra attributes for application
given either choice, or ignore them all together and start with a blank
slate. It could even reject the user (for having a "bad" profile).
>Ascend has done a lot of extensions.
This doesn't require any extentions, of the protocol.
Dave.
>And the Ascend-Idle-Limit is an Ascend attribute that doesn't work with
>Livingston. I don't believe Ascend supports the standard RFC attrib
>for the same thing (we do).
>
>-MZ
>--
--------------------------------------------------------------
David Mitton 508-670-8888 Main
Consulting Engineer 508-916-4570 Direct
Bay Networks, Internet/Telcom BG 508-916-4789 FAX
Billerica, MA 01821 dmitton@baynetworks.com