Re: RADIUS work items

[Bernard Aboba <aboba@internaut.com>]

Yes, SIPPING does want support for HTTP digest as well as SIP accounting.
However, they've expressed a preference for doing this work in SIPPING
WG, with potential review by a RADIUS-related WG.  SIPPING also requested
work on RADIUS reliability improvements,  to support the accounting work.
The question is whether a modest "transport profile" for RADIUS would
actually get them the improved reliability they're looking for.  My take
is that it won't unless there is some work on failover as well as basic
transport behavior.

Coexistence with the equivalent Diameter applications is important.

---------- Forwarded message ----------
Date: Tue, 12 Aug 2003 10:22:14 +0000
From: owner-radiusext@ops.ietf.org
To: radiusext@ops.ietf.org
Subject: Re: Potential RADIUS-related work items
References: <Pine.LNX.4.53.0308112236070.7351@internaut.com>
In-Reply-To: <Pine.LNX.4.53.0308112236070.7351@internaut.com>

Bernard Aboba wrote:

> It appears that  we have 4 potential work items:
>
> a. Attribute space extension   ETA: 06/04
> b. RADIUS Transport Profile    ETA: 06/04
> c. RADIUS Prepaid              ETA: 09/04?
> d. RADIUS attributes for WLAN  ETA: 12/04?
>
> Comments?

Looks good. I'd scope the transport draft very, very
narrowly. Didn't the SIPPING group ask for
RADIUS HTTP Digest? Also, it since there is
ongoing Diameter work on prepaid and digest,
it would be useful to coordinate the digest/prepaid
and maybe wlan work so that co-existence of the
protocols can be assured without spending too
much effort on the translation devices. That is,
please do not invent widely different schemes
for the two protocols ;-)

--Jari



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