Re: [Dime] WGLC for draft-ietf-dime-extended-naptr

[Mark Jones <[e-mail]>]

Hi Sebastian,

On Mon, Jan 10, 2011 at 8:44 PM, Sebastien Decugis <[e-mail]> wrote:
> Hi,
>
>>> Since The Diameter Base
>>> protocol includes rudimentary accounting functionality it doesn't seem
>>> completely unreasonable that Diameter Base might be used as a stand-alone
>>> app.
>> Ok, I hadn't appreciated that stand-alone usage of Base. Looking at
>> section 7.1, it appears to be missing two entries: one for "aaa" and
>> one for "aaa+ap0". The "aaa" entry could be deleted if rfc3588bis is
>> published first.
> If I understand correctly the discussion, I think you mean here
> "aaa+ap3". Application 0 is used for the "one hop only" messages
> (CER/CEA, DWR/DWA...) and is supported by ALL peers (so there is no
> point in having it defined here). Application 3 is the "rudimentary
> accounting functionality" defined in rfc3588(bis).
>

Good catch. I mistakenly thought base accounting used app id 0. As you
point out, an app id of 0 is only used for CER/CEA, DWR/DWA, DPR/DPA
so it does not appear useful as a stand-alone app. Unless someone has
an example where "aaa+ap0" would be useful, I won't add it to the next
rev.

> I apologize if my remark is irrelevant...
>

Highly relevant. Thank you.

Regards
Mark