[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Issue 226: RFC 3576bis and Renumbering



Alan,

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

No.  Class Attribute perhaps but not Acct-Session-Id.  Accounting
Session Id changes all the time. While the Authetnication Session
remains constant.

> The NAS does not currently share this information with the
authentication server.  It SHOULD make > this information available to
the authentication server.

No.  It is useless in cases where you have multiple Starts/Stops and
multiple Accounting sessions.

>  Once the Acct-Session-Id is available to the authentication server,
it can be used to tie 
>authentication sessions to accounting sessions in a better way than
what is done right now.  It can >also be used as a key to control
parameters related to the session... like CoA.

No. For the reason above. And we have Class attribute to do just that.

Avi

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