RE: [Megaco] descriptor order and error descriptors
"Kevin Boyle" <kboyle@nortelnetworks.com> Thu, 02 December 2004 07:55 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16963 for <megaco-archive@lists.ietf.org>; Thu, 2 Dec 2004 02:55:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZlYF-0008Hn-6E; Thu, 02 Dec 2004 02:38:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZksr-0000WH-2V for megaco@megatron.ietf.org; Thu, 02 Dec 2004 01:56:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27018 for <megaco@ietf.org>; Thu, 2 Dec 2004 01:56:07 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZkyK-0001YV-EY for megaco@ietf.org; Thu, 02 Dec 2004 02:01:48 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id iB26tZr18090 for <megaco@ietf.org>; Thu, 2 Dec 2004 01:55:35 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id <XQM2PS5N>; Thu, 2 Dec 2004 01:55:35 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536010B1B28@zrtphxm2>
From: Kevin Boyle <kboyle@nortelnetworks.com>
To: Troy Cauble <troy@bell-labs.com>, megaco@ietf.org
Subject: RE: [Megaco] descriptor order and error descriptors
Date: Thu, 02 Dec 2004 01:55:19 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Wouldn't the command processing stop at the first error? I believe the intent is to enforce order, since that is how the sender can align where errors occurred with the command. Christian may be able to provide more detail on the history of how this was intended to work... Whatever we decide, we should document the fix into the Implementors' Guides for V1 and V2, and fix the text in V3. Kevin -----Original Message----- From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Troy Cauble Sent: Wednesday, December 01, 2004 12:46 PM To: megaco@ietf.org Subject: [Megaco] descriptor order and error descriptors Hi, I recently ran into the exchange below. I think it points out a weakness in the protocol w.r.t. associating descriptor level errors with the appropriate descriptor. I could find nothing in the docs that say a response's descriptors should be in the same order as the request's descriptors. I could find nothing in the docs that say the AuditValue's response's descriptors should be in the same order as the request tokens. In fact, the V2 doc has examples of AuditValue returning descriptors in an order other than the request tokens. I didn't check to see if there are similar issues in the other lists that an errorDescriptor can be used in. It seems likely though. Forcing the order to be maintained and using that for context is ugly, IMO. But it's probably the minimal change solution. The real problem is lack of info in the errorDescriptor. (Relying on the text of the error descriptor field would also be a bad idea, IMO.) -troy MEGACO/1 [135.112.125.109]:55555 Transaction = 50007 { Context = - {AuditValue = aaln/2 { Audit{ Packages, Statistics , DigitMap, Signals, Events, Media }}}} MEGACO/1 [135.112.125.214] Reply = 50007 { Context = - { AuditValue = aaln/2 { Media { TerminationState { Buffer = OFF}, Stream = 1 { LocalControl { } } }, Events = 2222 { al/of }, Error = 447 { "Descriptor not legal in this command" }, Error = 447 { "Descriptor not legal in this command" }, Packages { g-1, tonegen-1, tonedet-1, dg-1, dd-1, cg-1, cd-1, al-1, ct-1, rtp-1, tdmc-1, ftmd-1, ctyp-1, an-1, bau-1, aau-1, xal-1 }, Error = 501 { "Not implemented" } } } } _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco
- [Megaco] descriptor order and error descriptors Troy Cauble
- RE: [Megaco] descriptor order and error descripto… Kevin Boyle
- Re: [Megaco] descriptor order and error descripto… Christian Groves