RE: RFC 3576bis Question: DAC and RADIUS server not co-located

["Glen Zorn" <glenzorn@comcast.net>]

...

>> > Since the DAC needs access to a database of State in order to track
>> > sessions, that database could contain the required State attribute.
>>
>>   The RADIUS server already tracks sessions.  
[gwz] 

How is that possible, given that there is no "logoff" message in RADIUS?
Surely you mean that the RADIUS _Accounting_ server tracks sessions, no?

[gwz] 

>>I would recommend against
>> DACs re-implementing that.
> 
> Some how the DAC needs to know which NAS to send the
> CoA/Disconnect-Request to, correct?

  Normally, yes.  If it sends the request to the RADIUS server, we
presume that the RADIUS server figures it out.
[gwz] 

OK, I give: how does the DAC even know that there is a session to modify if
it has no access to session state?

[gwz] 

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