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

[Avi Lior <avi@bridgewatersystems.com>]

Folks are throwing around terms like RADIUS server and RADIUS client all over the place.

What is really lacking is a defintion - that we can all agree - of what is a RADIUS Server and a RADIUS Client.



> -----Original Message-----
> From: owner-radiusext@ops.ietf.org
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of David B. Nelson
> Sent: November 11, 2008 9:14 AM
> To: dime@ietf.org
> Cc: aaa-doctors@ietf.org; radiusext@ops.ietf.org
> Subject: RE: [Dime] [AAA-DOCTORS] AD Review of
> dime-qos-parameters-06.txt
>
> 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/>
>

--
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/>