: RE: [Dime] RE: Diameter base protocol messages used by DCCA

Actualy, shouldn't ApplicationId in the message header be 4 (ApplicationId
for DCCA) , for such an AAR?

    Tolga

> -----Original Message-----
> From: Anders Kristensen [mailto:[email protected]]
> Sent: Thursday, June 15, 2006 4:38 PM
> To: Tolga Asveren
> Cc: [email protected]; [email protected]
> Subject: Re: [Dime] RE: Diameter base protocol messages used by DCCA
>
>
> OK, so at least there's a way to tell which app the AAR really is for.
> In my view it's a poor solution, though, since the code maintaining peg
> counts could very well belong to a generic Diameter stack which doesn't
> necessarily know about the particulars of DCCA. It's sort of reasonable
> to expect the stack to do something on the basis of Auth-Application-Id
> but not really for DCCA specific AVPs. It makes it unnecessarily
> difficult to layer the server code.
>
> Thanks,
> Anders
>
> Tolga Asveren wrote:
>
> > RFC4006 5.2.2 states that Credit-Control AVP  MUST be added to AAR to
> > indicate credit-control capabilities.
> >
> >
> >>-----Original Message-----
> >>From: Anders Kristensen [mailto:[email protected]]
> >>Sent: Thursday, June 15, 2006 4:13 PM
> >>To: Glen Zorn (gwz)
> >>Cc: [email protected]; [email protected];
> >>[email protected]; [email protected]; [email protected]
> >>Subject: Re: [Dime] RE: Diameter base protocol messages used by DCCA
> >>
> >>
> >>
> >>
> >>Glen Zorn (gwz) wrote:
> >>
> >>>Harri Hakala (TU/LMF) <mailto:[email protected]>
> >>
> >>supposedly scribbled:
> >>
> >>>...
> >>>
> >>>
> >>>
> >>>>AA Request/AA Answer are not necessarily equal to AAR/AAA messages in
> >>>>NASREQ but they mean in DCCA document a general
> >>>>authorization/authentication request/answer in any Diameter
> >>>>authorization/authentication application. Bad name example, as it
> >>>>seems to collide with the message name in NASREQ.
> >>>>
> >>>
> >>>
> >>>This would seem to make it quite difficult to monitor/manage
> >>
> >>DCCA via SNMP, since presumably one would wish to keep track of
> >>all the interrogations & the generic auth message is actually the
> >>first interrogation.   This implies that all & any such messages
> >>should be allocated a counter in the DCCA MIB, but the membership
> >>of this set of messages is not static.  Any suggestions?
> >>
> >>Have clients include an Auth-Application-Id AVP in the AAR with the DCC
> >>app id? It's not clear to me from the specs whether this is the
> >>intention or not but IMHO there really ought to be a way for the server
> >>to tell whether the AAR is for a NAS or DCC session - not just for
> >>management reasons.
> >>
> >>Anders
> >>
> >>
> >>>...
> >>>
> >>>~gwz
> >>>
> >>>Why is it that most of the world's problems can't be solved by simply
> >>>  listening to John Coltrane? -- Henry Gabriel
> >>>
> >>>_______________________________________________
> >>>DiME mailing list
> >>>[email protected]
> >>>https://www1.ietf.org/mailman/listinfo/dime
> >>>
> >>
> >>_______________________________________________
> >>DiME mailing list
> >>[email protected]
> >>https://www1.ietf.org/mailman/listinfo/dime
> >
> >
> >
> > _______________________________________________
> > DiME mailing list
> > [email protected]
> > https://www1.ietf.org/mailman/listinfo/dime
> >