RE: [Dime] [AAA-DOCTORS] AD Review of dime-qos-parameters-06.txt

["David B. Nelson" <dnelson@elbrysnetworks.com>]

Hi Hannes,

> I don't think that attributes can be opaque to the RADIUS 
> client since the client has todo something with them.

Maybe this is a matter of semantics.  Just as the RADIUS Server does not
comprise the complete set of server-side AAA functionality (e.g. policy
servers, location servers, authentication back-ends, etc. are logically
separate), the RADIUS Client does not comprise the complete set of AAA
functionality in the NAS.  The RADIUS Client delivers authorization
information to the components of the NAS that enforce access control.

When you define the RADIUS Server and RADIUS Client in this narrow sense,
i.e. the code that deals with RADIUS PDUs, I think you can claim the certain
attributes are opaque to the RADIUS Client (but certainly not to the NAS).

-- Dave



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>