Re: WGLC for draft-ietf-dime-qos-parameters-01

Hi Hannes and all,

Hannes Tschofenig wrote:

> http://tools.ietf.org/html/draft-ietf-dime-qos-parameters-01

I'm not a AAA expert, so probably I don't get the point.
Unfortunately, I'm not very content with the draft, so I have some major
comments:
1) The draft says:
   "The payloads used to carry these QoS parameters are opaque for the
   AAA client and the AAA server itself and interpreted by the
   respective Resource Management Function."

   Since the rest of the draft seems to contain larger copy&paste
   regions from the NSIS-QSPEC-Draft I'd like to ask: why is it not
   sufficient to use a QSPEC object as it is. To me it makes no sense
   to do another format rewriting when creating a Diameter request
   (QAR) from an NSIS RESERVE for example. Is there any technical
   reason to not use a QSPEC object as it is? This would allow for
   an easy interworking between NSIS and AAA and to re-use larger parts
   of the RMF code. Conveying the parameters for AAA
   in a different way is IMHO not necessary and source for new
   implementation errors...
   If there are technical reasons why using the QSPEC directly doesn't
   work, please state it in the draft.

2) The draft doesn't provide a meaningful definition of which parameters
   should be present together etc. It is only an unstructured list of
   parameter objects and there is no hint given about which combinations
   are allowed or meaningful etc.

Regards,
 Roland