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

["STURA, Marco, VF-IT" <Marco.STURA at vodafone.com>]

Hi Glen,

Sorry for the late answer I was in business trip with no access to my
emails.

>So, in other words, in order to implement a e.g., [NASREQ], [DIAMMIP]
peer >intended for general distribution, one must include CCA client
>functionality.

Not necessarily. One could provide communication means to enable a CCA
functionality module to add relevant AVPs to the initial AA request and
process relevant AVPs from AA answer.

>Or, that there were no intermediate interrogations; also, what about
the >case of a one-time event (balance check, etc.)?  Although this kind
of >activity doesn't seem to be included in any of the examples in RFC
4006, >neither does it appear to be prohibited.  If a balance check or
other type >of one-time event was included in the AAR it seems that
there would be no >client-side counter incremented.

One time events always use CCR/CCA messages. In section 6 of RFC4006 it
is stated in first paragraph "The use of a one-time event implies
   that the user has been authenticated and authorized beforehand."

Examples of one time event usage are given in Flow III, IV and V within
the appendix.

One time event uses Request-type of EVENT.

>I hadn't planned to, no.  However, if it is necessary to use this data
to >infer the existence of an initial interrogation from its absence
(does >anybody else see something odd about this?), I suppose I will
have to do >so.

I'm afraid DCCA MIB should be able at least to differentiate between
EVENT, INITIAL, UPDATE and TERMINATION requests.
If you want to go further and also count what type of event the request
was sent for then you would need to consider the Requested-Action.

However, all these are unfortunately DCCA specific AVP based
information.

Regards
Marco


_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime