Re: acct-stop w/o acct-start

[Alan DeKok <aland@deployingradius.com>]

Alper Yegin wrote:
> And if the network entry does not complete despite the NAS receiving an
> access-accept (e.g., host abandoning the procedure, or one of the steps
> failing), then the acct-start is not sent to the AAA server. AAA server
> can let the session timeout. But an explicit message from the NAS
> indicating failure would yield a better resource management on the AAA
> server side.

  Similarly, if the session lasts less than a second.  Should the NAS
send a start, immediately followed by a stop?

> For such a case, is it OK to send an acct-stop without sending an
> acct-start after the access-accept?

  People are using it this way in practice.

  It's not forbidden by the specs, but the RADIUS specs are silent on a
large number of topics.

> Or, is there another/better way of using a RADIUS message for this purpose?

  I don't think so, no.

  Alan DeKok.

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