RE: QoS attributes

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

John:

I think that COPS is a policy protocol, and policies related to QOS can also be used for distribution and enforcements. Similar may also be the case for security and accounting.

However, DIAMETER/RADIUS is also used for authentication, authorization, and accounting (AAA).

Here are the interesting points: 

1. COPS for policies of authentication, authorization, and accounting including QOS.

2. DIAMETER/RADIUS for offering actual services for authentication, authorization, and accounting including QoS.

In item 2, I am lacking clear wordings here.

The question is this: Can we not develop standards complementing both COPS and DIAMETER/RADIUS as they are also a part of IETF standard protocols?

BR,

Radhika R. Roy
rrroy@att.com

-----Original Message-----
From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
Sent: Monday, December 22, 2003 2:26 AM
To: avi@bridgewatersystems.com; dnelson@enterasys.com;
radiusext@ops.ietf.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.

John

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