RE: Issue 226: RFC 3576bis and Renumbering

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

Alan DeKok writes...

>   It would be just as easy to update implementations to permit
> accounting STOP messages to be sent to authentication servers.  Some
> implementations already support this.  It doesn't require a new command,
> and it has all of the features of the logoff draft.

Yes, but you'd need Accounting START messages, as well.  With all due
respect to Glen, his draft is oddly named, as it encompasses more than
notification of session termination.  It also includes notification of
session origination, presumably including sessions that were spontaneously
created at the NAS without the benefit of a directly corresponding
Access-Request/Accept exchange.

While I agree that one _could_ start sending Accounting-Request messages to
RADIUS Servers, that seems to be a muddling of the authentication and
authorization vs. accounting roles.  Maybe that is acceptable for the
special case of Dynamic RADIUS support.  What do others think?



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