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

Re: RADEXT charter, Take 8

To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: RADEXT charter, Take 8
From: Bernard Aboba <aboba@internaut.com>
Date: Wed, 24 Mar 2004 18:51:23 -0800 (PST)
Cc: radiusext@ops.ietf.org
In-reply-to: <Pine.LNX.4.56.0403241842170.31518@internaut.com>
References: <F17FB067A86B2D488382C923C532EAA7024A492D@exch01.bridgewatersys.com> <4061F867.3040404@piuha.net> <Pine.LNX.4.56.0403241842170.31518@internaut.com>

> > features minimal. By the way, are there some external
> > SDO requirements for this prepaid work? If so, is
> > the charter definition for prepaid functions compatible
> > with their requirements?
>
> Actually, the features (including event-related charging) came from a
> liaison request from 3GPP2.

Correction. I went back over my notes and the request came in as a comment
from a participant on the RADEXT mailing list.  I will let the person who
made the suggestion provide the logic behind it.

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

References:
- RE: RADEXT charter, Take 8
  - From: Avi Lior <avi@bridgewatersystems.com>
- Re: RADEXT charter, Take 8
  - From: Jari Arkko <jari.arkko@piuha.net>
- Re: RADEXT charter, Take 8
  - From: Bernard Aboba <aboba@internaut.com>

Prev by Date: Re: RADEXT charter, Take 8
Next by Date: RE: RADEXT charter, Take 8
Previous by thread: Re: RADEXT charter, Take 8
Next by thread: RE: RADEXT charter, Take 8
Index(es):
- Date
- Thread