[Dime] Clarification: ABNF for error messages ?
Sebastien Decugis <sdecugis@nict.go.jp> Tue, 08 December 2009 08:17 UTC
Return-Path: <sdecugis@nict.go.jp>
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 839C13A6883 for <dime@core3.amsl.com>; Tue, 8 Dec 2009 00:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.134
X-Spam-Level: *
X-Spam-Status: No, score=1.134 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_40=-0.185, HELO_EQ_JP=1.244]
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 5WzjfTmd2h8s for <dime@core3.amsl.com>; Tue, 8 Dec 2009 00:17:51 -0800 (PST)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:2f8:29::2]) by core3.amsl.com (Postfix) with ESMTP id 063623A68A8 for <dime@ietf.org>; Tue, 8 Dec 2009 00:17:50 -0800 (PST)
Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp with ESMTP id nB88HcAS007260 for <dime@ietf.org>; Tue, 8 Dec 2009 17:17:38 +0900 (JST)
Received: from gw1.nict.go.jp (localhost [127.0.0.1]) by gw1.nict.go.jp with ESMTP id nB88Hcoe015243 for <dime@ietf.org>; Tue, 8 Dec 2009 17:17:38 +0900 (JST)
Received: from mail3.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp with ESMTP id nB88HcVP015240 for <dime@ietf.org>; Tue, 8 Dec 2009 17:17:38 +0900 (JST)
Received: from mail3.nict.go.jp (localhost [127.0.0.1]) by mail3.nict.go.jp (NICT Mail) with ESMTP id 1BFD916911 for <dime@ietf.org>; Tue, 8 Dec 2009 17:17:38 +0900 (JST)
Received: from [133.243.146.206] (5gou2f-dhcp46.nict.go.jp [133.243.146.206]) by mail3.nict.go.jp (NICT Mail) with ESMTP id 14ACB1690F for <dime@ietf.org>; Tue, 8 Dec 2009 17:17:38 +0900 (JST)
Message-ID: <4B1E0B9C.3080906@nict.go.jp>
Date: Tue, 08 Dec 2009 17:17:32 +0900
From: Sebastien Decugis <sdecugis@nict.go.jp>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: dime@ietf.org
X-Enigmail-Version: 0.96.0
OpenPGP: id=33D9F61D
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Dime] Clarification: ABNF for error messages ?
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, 08 Dec 2009 08:17:52 -0000
Hello all, RFC3588 section 7.2 (and still in bis document) requires an answer message to conform to its ABNF, unless the E bit is set, in which case the ABNF may be different. I would like to point that this requirement cannot always be satisfied, for example when the Result-Code is being set to DIAMETER_COMMAND_UNSUPPORTED in which case the local peer does not know anything about the ABNF. I am wondering if the correct behavior would be to set the E bit for this Result-Code value (in which case a relay would try to send it to an alternate peer) or assume that the ABNF has to be checked only in case of Success (2xxx) and Informational (1xxx) Result-Code values ? Does someone have any comment on this ? Thank you in advance. Best regards, Sebastien. -- Sebastien Decugis Research fellow Network Architecture Group NICT (nict.go.jp)
- [Dime] Clarification: ABNF for error messages ? Sebastien Decugis