Re: [Dime] diameter-api draft comparison
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 02 November 2008 11:16 UTC
Return-Path: <dime-bounces@ietf.org>
X-Original-To: dime-archive@megatron.ietf.org
Delivered-To: ietfarch-dime-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9ECA53A68A8; Sun, 2 Nov 2008 03:16:36 -0800 (PST)
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 21F503A6846 for <dime@core3.amsl.com>; Sun, 2 Nov 2008 03:16:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.68
X-Spam-Level:
X-Spam-Status: No, score=-2.68 tagged_above=-999 required=5 tests=[AWL=-0.081, 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 3lGwsJHPyZP8 for <dime@core3.amsl.com>; Sun, 2 Nov 2008 03:16:34 -0800 (PST)
Received: from co300216-co-outbound.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id B2AA628C101 for <dime@ietf.org>; Sun, 2 Nov 2008 03:16:08 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,529,1220241600"; d="scan'208";a="149613982"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.avaya.com with ESMTP; 02 Nov 2008 06:15:41 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 02 Nov 2008 06:15:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 02 Nov 2008 12:15:39 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040109B0FD@307622ANEX5.global.avaya.com>
In-Reply-To: <alpine.LNX.1.10.0811010421060.4743@fbirervta.pbzchgretzou.qr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Dime] diameter-api draft comparison
Thread-Index: Ack76UIw/nj73UrmQM++sAu9A/fnkQA8fZqQ
References: <alpine.LNX.1.10.0811010421060.4743@fbirervta.pbzchgretzou.qr>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jan Engelhardt <jengelh@medozas.de>, dave@frascone.com
Cc: dime@ietf.org
Subject: Re: [Dime] diameter-api draft comparison
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org
Hi Jan, I cannot find any comment from you on the list concerning draft-ietf-dime-diameter-api neither during the month of July or during the IETF Last Call. If I missed something please point me to your messages. It certainly does not suffices to just say 'I am in disagreement' - you need to provide detailed comments and arguments about what aspects (technical or editorial) you find as problematic. Please try to do so as soon as possible, as this document is planned to be submitted for review and approval to the IESG after the publication of the I-D revision following the IETF Last Call. Dan > -----Original Message----- > From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On > Behalf Of Jan Engelhardt > Sent: Saturday, November 01, 2008 6:23 AM > To: dave@frascone.com > Cc: dime@ietf.org > Subject: [Dime] diameter-api draft comparison > > > I have monitored this list before but I did not quite see a > reason for taking part until I finished our implementation of > Diameter and WebAuth. > > I see that my earlier disagreement mail about > draft-ietf-dime-diameter-api-06 from July has not been > forwarded here; but it probably suffices to say that I am at > a disagreement with that draft, both from a technical > standpoint, and not less from a cosmetical one. While > camelcase is something one can debate infinitely, I have to > condemn the silly use of typedefs and long names. Some > specified functions like AAAValueFromAVPCode do not make any > sense at all. > > Our API, which actually goes in line with an actual > implementation around it, is described in its Developers > Guide; a web copy is at > http://circum.sf.net/circum_devguide.pdf . I especially > encourage the draft's authors to compare. > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime > _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime
- [Dime] diameter-api draft comparison Jan Engelhardt
- Re: [Dime] diameter-api draft comparison Romascanu, Dan (Dan)
- Re: [Dime] diameter-api draft comparison Jan Engelhardt
- Re: [Dime] diameter-api draft comparison Glen Zorn
- Re: [Dime] diameter-api draft comparison Jan Engelhardt
- Re: [Dime] diameter-api draft comparison Romascanu, Dan (Dan)
- Re: [Dime] diameter-api draft comparison Glen Zorn
- Re: [Dime] diameter-api draft comparison Jan Engelhardt
- Re: [Dime] diameter-api draft comparison Sebastien Decugis
- Re: [Dime] diameter-api draft comparison Jan Engelhardt
- Re: [Dime] diameter-api draft comparison Sebastien Decugis
- Re: [Dime] diameter-api draft comparison Jan Engelhardt
- Re: [Dime] diameter-api draft comparison Sebastien Decugis