[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: QoS attributes
thank you john for the pointers.
qos is more than just shuffling some bandwidth parameters around.
comments to the drafts are highly appreciated.
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]
> Sent: Thursday, December 18, 2003 10:40 AM
> To: firstname.lastname@example.org; email@example.com
> Subject: RE: QoS attributes
> Hi all,
> My 2 cents are as follows: RADext/AAAext (or whatever)
> shouldn't define QoS signaling,
> NSIS is already doing that:
> There has been some discussion on AAA issues for QoS:
> Looking into QoS issues, my feeling is that we want to
> specify QoS classes.
> These classes may support a set of QoS parameters. I think that QoS
> will be an area that vendors try to differentiate on; service
> may create services that support different QoS parameters,
> etc. I don't
> think that we can get into the QoS signaling / provisioning /
> of QoS parameters, as that excedes the scope of AAA (either RADIUS or
> Diameter). I would prefer that RADIUS / Diameter would contain a
> QoS class parameter, which could make use something like a IANA QoS
> class registry.
> Different SDOs have different plans ITU-T, 3GPP, 3GPP2, etc. all have
> defined seperate QOS classes. One could imagine registering
> these classes
> in IANA, and service providers could support, in various
> degrees, different
> QoS classes. It would then be in scope of AAA to provide
> authorization for
> these classes.
> to unsubscribe send a message to firstname.lastname@example.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 email@example.com with
the word 'unsubscribe' in a single line as the message text body.