Re: New Technical Issues RE: WG last call in progress on VLAN/Priority Draft

["Alan DeKok" <aland@ox.org>]

"Avi Lior" <avi@bridgewatersystems.com> wrote:
> So whether or not the attribute is compound or not, if the server needs
> to "interact" with that attribute then it needs to have new code added.
> This applies to any server or client that needs to "interact" with that
> attribute.

  For clients, yes.  For servers, though, many have complex policy
configuration files.  So the policy has to be updated to deal with a
new attribute, but the server code does not need to change.

  In many cases, the policy is GUI driven, and is "if you see FOO with
value BAR in the request, respond with FOOD with value BARD".

> So the notion of dictionary driven code and using existing radius types
> really speaks only about not adding any code to the RADIUS packet
> encoder/decoder.

  Dictionaries also allow the creation of complex policy languages, by
separating the language syntax from the data and types the language
operates on.

  Alan DeKok.

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