RE: [Dime] [AAA-DOCTORS] AD Review of dime-qos-parameters-06.txt

["Glen Zorn" <glenzorn@comcast.net>]

> Hi Bernard,
> 
> We have currently three documents in DIME that relate to QoS: The
> Diameter
> QoS application specifies, as the name indicates, a Diameter
> application for
> usage with QoS. The QoS attribute draft provides the encoding of
> classifiers
> and AVPs relevant for QoS. The actual QoS parameters for an initial
> profile
> are defined in the QoS parameters draft. These drafts in DIME focus on
> Diameter usage. We have dependencies from the 3GPP on these documents.
> 
> It is, however, quite easy to imagine that QoS parameters might also be
> useful in a RADIUS context. In fact we had a document some time ago
> that
> described how to re-use the same QoS parameter format for RADIUS. The
> document is, however, expired now and would need a significant update
> given
> the changes we have seen in the DIME documents.

It's very simple: if these attributes/AVPs are meant to be used in RADIUS
then do the work in radext (or at the very least, follow the RADIUS design
guidelines); note that those attributes could be carried w/o any fuss in
Diameter as well.  If they are meant to be used in Diameter, then design
them as Diameter AVPs, using the features that Diameter enables (grouped
AVPs, etc.).  What you have done is neither, and have (predictably) ended up
with a mess.

> 
> When it comes to the format then our believe so far was that the format
> of
> the QoS parameters was not really important as the authorization
> decision
> and related admission control procedures by the AAA server will require
> code
> changes. Code changes to the AAA client will be needed as well since
> the
> parameters need to be feed into a Traffic Control module.
> 
> Ciao
> Hannes
> 
> 
> >-----Original Message-----
> >From: aaa-doctors-bounces@ietf.org
> >[mailto:aaa-doctors-bounces@ietf.org] On Behalf Of Bernard Aboba
> >Sent: 10 November, 2008 06:50
> >To: 'ext Romascanu, Dan (Dan)'; dime@ietf.org
> >Cc: aaa-doctors@ietf.org; radiusext@ops.ietf.org
> >Subject: Re: [AAA-DOCTORS] [Dime] AD Review of
> >dime-qos-parameters-06.txt
> >
> >Glen Zorn said:
> >
> >"Still looks like (bad) RADIUS to me."
> >
> >Can someone explain the relationship of this document to (bad
> >or good) RADIUS?
> >
> >Looking at the DIME WG charter, there is an item for the
> >Diameter QoS application
> >(http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-q
> >os-06.txt),
> >Which in turn has normative references to QoS Attributes for Diameter
> >(http://www.ietf.org/internet-drafts/draft-ietf-dime-qos-attrib
> >utes-08.txt)
> >and this document.
> >
> >None of these documents request allocation of any RADIUS
> >attributes, or describe RADIUS Attribute formats.
> >
> >
> >
> >_______________________________________________
> >AAA-DOCTORS mailing list
> >AAA-DOCTORS@ietf.org
> >https://www.ietf.org/mailman/listinfo/aaa-doctors
> >
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime


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