[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: QoS attributes
A question for my clarification. What happens if the service that needs
a specific QoS is a third party Service i.e. it is not being
delivered/offered by the home network and therefore W/ISP does not have
a AAA relationship as such with the 3rd party.
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of Avi Lior
Sent: Monday, December 22, 2003 8:19 AM
To: 'email@example.com'; Avi Lior; firstname.lastname@example.org;
Subject: RE: QoS attributes
Okay we are starting to converge here a bit.
I understand the concept of having AAA authorize a certain QoS class.
And I agree with you on that.
The simple use cases (if I got it right ) would be:
Joe authenticates and the Access Accept message returns back a QoS
class; alternatively Joe requests a new service instance with a certain
QoS class, and the NAS authorizes the use of a QoS class with the AAA
using an Authorize Only scheme.
This is all good.
But I don't belive that those are the only use cases. What about when
the QoS classes are not configured such in cases when we cross
administrative domains where we don't have the QoS class configured or
completely configured. You would then need to actually transport the
actual parameters. After all, isnt the QoS class an alias for QoS
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org]
> Sent: December 22, 2003 2:26 AM
> To: email@example.com; firstname.lastname@example.org;
> Subject: RE: QoS attributes
> Hi Avi,
> > I agree that we need a QoS Class Id, (or QoS-Bundle-Id).
> > Would RADIUS only ever transport the QoS-Class-Id?
> My thoughts are that a AAA system would only authorize for
> a certain QoS Class, not necessarily authorize specific
> QoS parameters.
> > Also reading through some of the drafts you point to. I noticed
> > that COPS is used. I think that at least in certain cases that
> > RADIUS/Diameter should be utilized instead of COPS. There certainly
> > have been discussion on this.
> I agree. I don't think that COPS is the proper mechanism,
> though some people use it. Most of the discussions I have
> heard, as of late, seem to be about migrating to AAA
> mechanisms for QoS authorization.
to unsubscribe send a message to email@example.com with the
word 'unsubscribe' in a single line as the message text body.
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.