RE: Re-auth failure

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

Alper Yegin writes...

> For that reason and others, I think it's not RADIUS "protocol"
> specification's role to dictate what a NAS should be doing with
> the output of this protocol's execution.

Since RADIUS is all about authorization and service provisioning, you would
not be able to get multi-vendor interoperability at a behavioral level if
every NAS interpreted the standardized RADIUS messages in an implementation
dependent fashion.

The *semantics* of the messages, in terms of what they dictate for NAS
behavior is all part of the RADIUS specification.

> I think the reaction to a RADIUS state is an "architectural" decision,
> and belongs to the users of this protocol.

If you want to re-use RADIUS messaging formats in an implementation
featuring user customized actions for each message, then feel free to do so,
but please don't call it RADIUS.  :-)



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