RE: Issue 313: Security Exemption

["Dave Nelson" <d.b.nelson@comcast.net>]

Bernard wrote...

> > If the RADIUS server has to parse it, then complex attributes are
> > allowed for authentication and security...
>
> I think the question is why the exemption should be so broad.  The
> security and authentication attributes described in Appendix B required
> computation.  That is the RADIUS server had to add code in order to
> compare the authentication result presented by the RADIUS client with the
> result it calculated based on its own data. 
>
> However, if the RADIUS server doesn't have to do any computation (e.g.
> if it is just sending security or authentication-related data to the
> RADIUS client), then there is no intrinsic reason why RADIUS server
> code needs to change.  In that case, why should the exemption apply?

I don't think I ever saw an answer to this on the list.  Could we close out
this discussion, and perhaps craft some revised text, before the next draft
version is submitted?


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