RE: SIP AAA and QoS Attributes

["Roy, Radhika R, ALABS" <rrroy@att.com>]

Wolfgang:

I did NOT say for "authentication" of SIP QoS attributes or parameters.

What I said is as follows:

SIP resources (may including QoS) "MAY" need to be authorized for the
user who has been "authenticated." 

For example, a user may not be authorized for using video, if it is long
distance call. If even one is authorized to use video, the user may not
be authorized to use "bandwidth" more than 128 kbps, etc., etc.

Similarly, the accounting/billing may also be dependent on the above.

However, it is a fair question: Where do we capture all those things for
"authorization" and "accounting/billing" information of all those
resources/QoS attributes? Should we deal in AAA/RADIUS/DIAMETER or some
other standards?

Radhika

PS: I am aware about the works of the SIP session policy works (URL of
the slides that you have provided).

-----Original Message-----
From: Wolfgang Beck [mailto:wolfgang.beck01@t-online.de]
Sent: Sunday, January 04, 2004 5:49 PM
To: radiusext@ops.ietf.org
Subject: RE: SIP AAA and QoS Attributes


Radhika,

You wrote:
> > - SIP UASs (eg. SIP Proxies, PSTN Gateways, Application Servers) use
> > SIP specific RADIUS (or DIAMETER) attributes to do AAA for SIP
specific
> > services (I am working on an updated version of the sterman draft
which
> > should be available at the beginning of february).
> > 
> [RRR] Good. Will it also include QoS abstraction/attributes for each
> media (audio, video, data) that will be a part of the SDP messages
> in SIP?
Are you thinking of a SIP session policy framework like the one
described in
http://www.softarmor.com/sipping/meets/ietf58/slides/pres-hilt-session-p
olicy.ppt ?
This work is in a very early stage.

I don't quite understand why you would need to authenticate QoS
parameters
in a SIP system. This is up to your resource reservation protocol of
choice (which can, of course, be part of a device which uses SIP for
call signalling).

Given the absence of public networks providing dynamic resource
reservation, I'd give media accounting priority over QoS
authentication.

--
Wolfgang Beck
T-Systems GmbH

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