RE: QoS attributes

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

Hi, Avi, John, and all:

It is good that QOS attributes need to be addressed.

The question is: What would be the attributes for QoS t consider by the
AAA server?

Let us consider a call scenario. SIP INVITE message contains SDP where
audio, video, and data (application) need to be supported. Like security
(authentication), an AAA (RADIUS/DIAMETER) needs to do something.

Step 1: Each media will have their QoS attributes. What are those?

However, unlike security (authentication), the QoS attributes are
"end-to-end" specific. That is, the information that is available within
the AAA server is NOT sufficient to take the decision.

Step 2: Now, the question is this: Even if the QoS attributes are known,
what decision that an AAA server needs to take? How do we solve this
puzzle of an "end-to-end" attribute (e.g., bandwidth or delay) with the
AAA server? Does the AAA server need to take the help of other entities?
If so, what are those and how?

Let us focus on the above points: Step 2 (First) and Step 1 (Second).

Have a Happy New Year!

Best regards,

Radhika R. Roy
rrroy@att.com


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