[no subject]

[<jouni.korhonen@teliasonera.com>]

John, Jari,
 
> > By the way, what would be the meaning of CUI for "pay as you go"
> > type of approaches, e.g., micropayments or the like over EAP?
> > There might not be any billable user identity; the only thing
> > that could be provided in those cases is some kind of a session
> > identifier so that the home AAA and the NAS can correlate their
> > accounting records.
> 
> Correct, it could provide a session identifier; or more correctly
> a temporary billable session identity.  I haven't thought of all of
> the implications.
> 
> Actually, taking a step back, if there is a billable user identity,
> which is still needed in the pay-as-you-go case, then the CUI can
> be used to track & correlate accounting records.  This would be useful
> in cases when the user connects and disconnects several times, but
> the 'session' is longer than just one of the connection times. 
> For example, if you in a hotel and fire-up WLAN in the morning, then
> in the afternoon, then in the evening.  The 'session' might be your
> entire stay.

One of the intended additional uses for CUI (at least in our roaming
scenarios)
at the home AAA is indeed to be able to help correlating related
(shorter)
accounting sessions into longer "user experienced session" -- e.g.
something
acct-multi-session-id could also be used for but extended to multiple
disconnect & reconnect cases as well.

/Jouni


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

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