RE: QoS attributes

["Nelson, David" <dnelson@enterasys.com>]

Nakhjiri writes...
 
> Shouldn't there be
> a method to bundle paramters regarding each application, given the
fact
> that attribute space is so limited??

I don't think it has been demonstrated that the current attribute
address space will be exhausted by the set of current [reasonable]
proposals.  Given that, I see no great pressure for sub-types,
sub-encodings or other methods to "bundle" multiple parameters in a
single attribute.

> So again the question is, whether there needs to be one attribute
> for every QoS parameter under the sun, or is there a way to do
grouping?

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. 

-- Dave



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