RE: QoS attributes

[<john.loughney@nokia.com>]

Hi Avi, Pasi,

> I agree with this in general.
> 
> I don't think the intent was to have RADIUS do the signaling.

This is part of my confusion - I haven't seen a crisp statement
about how QoS & AAA are related.

If you think of it as bandwidth limiting, or more aptly authorization
for certain bandwidth, then I'm OK with that.

John

> > Hi,
> > 
> > I think at least some people are intending to use the 
> > bandwidth RADIUS attributes for configuring some sort of 
> > "bandwidth limiting" mechanism in a WLAN access point. This 
> > is very different 
> > from QoS signalling for, e.g., reserving bandwidth along the route 
> > to some destination.
> > 
> > I agree with John in that using AAA protocols for QoS 
> > signalling is not a good idea; however, using them to provide 
> > parameters for some "bandwidth limiting" mechanism seems very 
> > appropriate. 
> > 
> > Diameter even provides an AVP data format (QoSFilterRule) for 
> > exactly this purpose. It seems that this AVP data format is 
> > not yet used by any AVP type, though. It is quite complex, so 
> > perhaps something like a simple "maximum uplink/downlink bandwidth" 
> > attribute would be sufficient for many purposes.
> > 
> > BTW, it seems the actual text describing the "dscp" and 
> > "metering" options is missing from RFC 3588. The latest draft 
> > that still explains their parameters seems to be -09, 
> > available from: 
> > http://www.watersprings.org/pub/id/draft-ietf-aaa-diameter-09.txt
> > 
> > Best regards,
> > Pasi
> > 
> > > -----Original Message-----
> > > From: owner-radiusext@ops.ietf.org On Behalf Of ext Avi Lior
> > > Sent: Monday, January 05, 2004 6:18 PM
> > > To: Loughney John (Nokia-NRC/Helsinki); rrroy@att.com; 
> > > jari.arkko@piuha.net; Madjid.Nakhjiri@motorola.com
> > > Cc: Avi Lior; radiusext@ops.ietf.org
> > > Subject: RE: QoS attributes
> > > 
> > > 
> > > Good question John,
> > > 
> > > Well what do you call Bandwidth attributes and transporting 
> > them? We 
> > > are certainly talking about tranpsorting Bandwidth 
> parameters in a 
> > > RADIUS message.  It certainly makes sense to me to include 
> > Bandwidth 
> > > attributes as part of the authorization of a given service.
> > > 
> > > Is Bandwidth part of QoS?  I think it is.
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> > > > Sent: Sunday, January 04, 2004 3:52 AM
> > > > To: rrroy@att.com; jari.arkko@piuha.net; 
> > Madjid.Nakhjiri@motorola.com
> > > > Cc: avi@bridgewatersystems.com; radiusext@ops.ietf.org
> > > > Subject: RE: QoS attributes
> > > > 
> > > > 
> > > > Roy, Avi,
> > > > 
> > > > I am getting quite confused by this discussion.  Could 
> I ask what
> > > > we are actually discussing?  RADIUS/Diameter are not 
> > > > signaling protocols, they are AAA protocols.  RADIUS/Diameter 
> > > > should not transport QoS information.  My expectation is that 
> > > > they would be involved in authorization for QoS for some 
> > > > services, but doing more would seem to be out of scope for 
> > > > AAA protocols.
> > > > 
> > > > Am I missing something?
> > > > 
> > > > 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/>