Subject: nasreq Re: On Demand Accounting...

From: Nenad Trifunovic <[email-masked]>
Date: Wed, 17 Nov 1999 12:51 -0800 (PST)

I doubt that one can get rid of On Demand Accounting as described 
in 8.4.1.6 of <draft-ietf-nasreq-criteria-03.txt>. The issue is 
the ability to query state of existing sessions on the NAS. 
Accounting subsystem might be one user of that information 
(or particular information elements that would depend on NAS 
and service type).

regards,
nenad

>Date: Wed, 17 Nov 1999 10:45 -0800 (PST)
>From: [email-masked] (Patrice Calhoun)
>To: [email-masked],
>    [email-masked]
>Sender: [email-masked]
>Reply-to: [email-masked]
>Delivered-to: [email-masked]
>Subject: On Demand Accounting...
>
>All,
>
>Given the arguments that have recently been discussed against the use of
>On-Demand Accounting, and specifically how it doesn't scale well in an
>Inter-Domain network, should it *still* be a requirement?
>
>I believe that NASREQ is the only WG that had such a requirement. Can we
>eliminate this from the matrix?
>
>PatC
>
>