IETF Logo Mail Archive

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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 23 June 2009 09:17 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54BCB3A68AB for <dime@core3.amsl.com>; Tue, 23 Jun 2009 02:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level:
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCY-n3o7jT9W for <dime@core3.amsl.com>; Tue, 23 Jun 2009 02:17:56 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id C9AD43A6AFE for <dime@ietf.org>; Tue, 23 Jun 2009 02:17:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,274,1243828800"; d="scan'208";a="174765071"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 Jun 2009 05:18:12 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 23 Jun 2009 05:18:11 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Jun 2009 11:17:50 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04017D380E@307622ANEX5.global.avaya.com>
In-Reply-To: <4A408565.6000106@nict.go.jp>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Dime] draft-ietf-dime-diameter-api in AD-Follow-Up
thread-index: Acnz1RP1+oWld6MoRHuh379nnBsbYQADle1g
References: <EDC652A26FB23C4EB6384A4584434A04017D31B7@307622ANEX5.global.avaya.com> <4A408565.6000106@nict.go.jp>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Sebastien Decugis <sdecugis@nict.go.jp>
Cc: dime@ietf.org
Subject: Re: [Dime] draft-ietf-dime-diameter-api in AD-Follow-Up
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2009 09:17:58 -0000

Thank you, Sebastien. 

Other opinions? 

Dan
 

> -----Original Message-----
> From: Sebastien Decugis [mailto:sdecugis@nict.go.jp] 
> Sent: Tuesday, June 23, 2009 10:34 AM
> To: Romascanu, Dan (Dan)
> Cc: dime@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)
> 
>

v2.23.0 | Report a Bug | By Email