Re: Rationalizing the RADIUS data model

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

jari.arkko@piuha.net wrote:
> But is that all, or should we also be worried about
> code changes (not just attribute number changes in
> a dictionary) when moving between the vendor, SDO,
> and extended IETF attribute space.

  Code changes aren't the problem.  The software which knows about new
features can be updated to handle "vendor-id == 0".

  I'm more concerned about legacy software.  Some people have old
servers which proxy requests to new servers.  With a vendor-id of
zero, the old servers may not be able to proxy the requests.  With a
non-zero vendor id, the older servers will be able to proxy the
requests.

  This is a daily concern for some people I work with.  Deployment of
*any* new feature has to be done in a way which doesn't break old
systems, which they can't/won't upgrade.

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