[Dime] draft-ietf-dime-diameter-api in AD-Follow-Up
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 18 June 2009 16:27 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 9C52128C3FB for <dime@core3.amsl.com>; Thu, 18 Jun 2009 09:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level:
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[AWL=0.147, 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 MpDCOfoN0coa for <dime@core3.amsl.com>; Thu, 18 Jun 2009 09:27:25 -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 9930028C142 for <dime@ietf.org>; Thu, 18 Jun 2009 09:27:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,245,1243828800"; d="scan'208";a="174369492"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 Jun 2009 12:27:37 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Jun 2009 12:27:37 -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: Thu, 18 Jun 2009 18:27:26 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04017D31B7@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-ietf-dime-diameter-api in AD-Follow-Up
Thread-Index: AcnwHouYJplfBRLsQSaM0SGnNTIgOgAEnJsw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: dime@ietf.org
Subject: [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: Thu, 18 Jun 2009 16:27:26 -0000
The IESG did not approve in the telechat today draft-ietf-dime-diameter-api. There are several DISCUSSes on this I-D, but the most fundamental question was asked by Pasi Eronen. Pasi questions whether the publication of this document is useful at all, and suggests publication as Historic or no publication as possible options. Pasi writes: > The writeup mentions there being two implementations, but apparently both of them are prototype code from around 2001 that have been abandoned >5 years ago. OpenDiameter (an open source Diameter implementation by the main author of this draft) does not use this API, and to me it looks very unlikely that anyone would ever implement this (and it's questionable whether anyone should even attempt). 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? Dan
- [Dime] draft-ietf-dime-diameter-api in AD-Follow-… Romascanu, Dan (Dan)
- Re: [Dime] draft-ietf-dime-diameter-api in AD-Fol… Sebastien Decugis
- Re: [Dime] draft-ietf-dime-diameter-api in AD-Fol… Romascanu, Dan (Dan)
- Re: [Dime] draft-ietf-dime-diameter-api in AD-Fol… David Frascone