: RE: Diameter base protocol messages used by DCCA

"Harri Hakala (TU/LMF)" <[email protected]> Thu, 15 Jun 2006 09:06:08 +0200
Newsgroups gmane.ietf.aaa
Message-ID <D60C37C9EF5C39459E0F4EF508E560A20319F322@esealmw113.eemea.ericsson.se>
Hi Glen,

The DCCA document defines two different approaches to perform the first =
credit control=20
interrogation to be used in different network architectures. The first =
approach=20
uses credit-control messages after the user's authorization and =
authentication=20
takes place. The second approach uses service specific authorization =
messages=20
(such as AAA/AAR) to perform the first interrogation during the user's=20
authorization/authentication phase, and credit-control messages for the=20
intermediate and final interrogations.=20

AA Request/AA Answer are not necessarily equal to AAR/AAA messages in =
NASREQ but=20
they mean in DCCA document a general authorization/authentication =
request/answer=20
in any Diameter authorization/authentication application. Bad name =
example, as it=20
seems to collide with the message name in NASREQ.

If the CCA client supports the second approach and e.g. NASREQ is used =
for service
authorization, then the CCA client sends/receives AAR/AAA messages.

As this "AA Request/AA Answer" is a general message, not explicit NASREQ =
message,=20
we did not include it the table in section 10.=20

regards............Harri


> -----Original Message-----
> From: Glen Zorn (gwz) [mailto:[email protected]]=20
> Sent: 15. kes=E4kuuta 2006 3:59
> To: Harri Hakala (TU/LMF); Leena Mattila (TU/LMF);=20
> [email protected]; [email protected];=20
> [email protected]
> Cc: Glen Zorn (gwz); [email protected]; [email protected]
> Subject: Diameter base protocol messages used by DCCA
>=20
> In the process of attempting to construct a MIB for the=20
> credit control application, I have been trying to figure out=20
> which messages from Diameter base are used by DCCA, so that=20
> they can be counted appropriately.  Some are obvious: STR/STA=20
> & RAR/RAA, for example.  One has me rather puzzled, though:=20
> the AAR/AAA exchange is explicitly listed in the first state=20
> machine in section 7 as being sent/received by the CCA=20
> client, but the AVPs allowed in AAR/AAA are not listed in=20
> section 10 (though the APS for RAR/RAA ARE).  Does the CCA=20
> client actually send/receive AAR/AAA (i.e., should the be=20
> counted in the DCCA MIB) or not?
>=20
> ~gwz
>=20
> Treat the Earth well.=20
> It was not given to you by your parents.
> It was loaned to you by your children.
>   -- Kenyan Proverb
>=20
> Humankind has not woven the web of life.
> We are but one thread within it.
> Whatever we do to the web, we do to ourselves.
> All things are bound together.
> All things connect.
>   -- Chief Seattle
>=20