Re: [Dime] draft-ietf-dime-diameter-api in AD-Follow-Up
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Dime] draft-ietf-dime-diameter-api in AD-Follow-Up



The API was derived from the Sun implementation of a diameter stack.
They had released the stack for applications developers to write
applications, using the API.  So, while there may be compilation
errors in the draft -- the API does (or did) exist, and was
functional.  However, I do not think the Sun implementation has been
kept up to date.  I can not find it, even on their research site.

So, as a biased author :) , I do still think there is some benefit in
the API.  I think it is an example of how a diameter application can
be implemented, even with a closed-source stack.  Since it is C, it is
lightweight, and could probably be used on embedded devices.

But, since it seems that the only working implementation is no longer
available, I would certainly understand it if the WG decides not to
pursue the API further.

Just my $.02 worth,


-Dave

On Tue, Jun 23, 2009 at 5:17 AM, Romascanu, Dan (Dan)<dromasca at avaya.com> wrote:
> Thank you, Sebastien.
>
> Other opinions?
>
> Dan
>
>
>> -----Original Message-----
>> From: Sebastien Decugis [mailto:sdecugis at nict.go.jp]
>> Sent: Tuesday, June 23, 2009 10:34 AM
>> To: Romascanu, Dan (Dan)
>> Cc: dime at ietf.org
>> Subject: Re: [Dime] draft-ietf-dime-diameter-api in AD-Follow-Up
>>
>> Hello,
>>
>> > I would like to get feedback from the authors and the WG. Is the
>> > document useful? If yes, for what? Who will use it? Do today's
>> > implementations and deployments follow the API that this document
>> > describes?
>> >
>> As far as I am concerned, I don't follow this API in my
>> implementation.
>> I studied the API when I started this work and came to the
>> conclusion that it is not appropriate for general-purpose
>> implementations (not easy to implement agents functions for
>> example). Anyway, people with different requirements might
>> find it useful for other situations. I personally believe
>> that this API can only be used for "simple"
>> client-sides of applications, but I may be mistaken.
>>
>> Best regards,
>> Sebastien.
>>
>> --
>> Sebastien Decugis
>> Research fellow
>> Network Architecture Group
>> NICT (nict.go.jp)
>>
>>
> _______________________________________________
> DiME mailing list
> DiME at ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.