[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: QoS attributes
Hi Avi, all
We need to have some consensus on what is the rationale/use of QoS
attributes for RADIUS/DIAMETER before moving forward on the topic. It
seems that we have more than one perspective on it. I for example see it
as static information during an authorized session i.e. QoS information
gets exchanged only during session setup where AN informs AAA of its
capabilities and AAA server tells the AN of user QoS susbcription. I do
not think RADIUS/DIAMETER servers should be involved in provisioning QoS
for individual services running in an already authorized session later
on. However Avi's email suggests it is somewhat more dynamic than this.
Avi, can you pls clarify if I understood your comments correctly.....
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of Avi Lior
Sent: Tuesday, December 16, 2003 1:42 PM
To: 'Nelson, David'; email@example.com
Subject: RE: QoS attributes
David Nelso wrote:
> Provisioning detailed, and more importantly, potentially
> dynamic, QoS parameters as authorization information in
> RADIUS or any other AAA protocol is probably not the right
> thing to do. What ought to be provisioned is a "level of
> service" indication (e.g. bronze, silver, gold, platinum)
> that can be used by each NAS to modify the QoS parameter
> negotiation process for each session.
It requires that each Hot Spot for example understand what to deliver to
a Bronze User or a Gold user etc.....
Like filter id, this just does not scale!
We need a way to explicitly push attributes down to the NAS. Equally
important is to make sure that the NAS tell us what it can currently
honour. This will alow the home RADIUS to make an appropriate policy
to unsubscribe send a message to firstname.lastname@example.org with the
word 'unsubscribe' in a single line as the message text body.
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.