RE: Issue 226: RFC 3576bis and Renumbering

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

Alan DeKok writes...

>   What I'm saying is that the NAS knows what a session is: the user is
> connected to it.  The NAS has the information that ties authentication
> packets to accounting packets:  the Acct-Session-Id.  The NAS does not
> currently share this information with the authentication server.  It
> SHOULD make this information available to the authentication server.

It is entirely possible that RADIUS client implementations that do not
include RADIUS Accounting may not have implemented the Acct-Session-Id
attribute. They would have no need to.

OTOH, I don't think we need to get too hung up about the nomenclature of the
attribute.  The fact at the prefix is Acct should not be sufficient to
disqualify its usage as a session identifier for the authentication server
as well as the accounting server.  A session ID is a session ID.



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