[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QoS attributes

john.loughney@nokia.com wrote:
Hi Jari,

My issue still is (without getting into specifics of QoS or WLAN parameters) how can bundle the parameters in a way that not every
single parameter has to be listed in a RADIUS RFC?

Oh that's easy -- we can just put it in some opaque string, vendor
specific attribute, or design some OID hierarchy around the parameters.

Not that easy.  Lets take the case of bandwidth.  Lets say we allow
a single QoS parameter called bandwidth.  Sounds simple.  What does
the parameter denote? Average bandwidth (over what time?), instanteous
bw, minimum bw, maximum bw, maximum sustained bw, bw from the point of
monitor, bw to the end user?  How do the roaming partners agree on this.

After we settle this, I am sure some folks will want to add more QoS
paramter, like delay, jitter, packet loss, throughput, goodput ...
and so on.  At the end of the day, this becomes extremely complex and
(IMO) unmanagable.

I agree -- but I was just responding that it is easy to provide parameter space so that it doesn't have to be listed in the IETF RFCs. Its another question if that would make sense, and yet another question if we could agree what the parameters are in the first place.


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