RE: [Dmsp] Missing statement ?

"Engelsma Jonathan-QA2678" <Jonathan.Engelsma@motorola.com> Mon, 05 June 2006 14:38 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnGDo-0007Jw-FQ; Mon, 05 Jun 2006 10:38:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnGDn-0007IZ-4d for dmsp@ietf.org; Mon, 05 Jun 2006 10:38:23 -0400
Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnGDh-0005We-Fs for dmsp@ietf.org; Mon, 05 Jun 2006 10:38:23 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id k55EcGGl023773 for <dmsp@ietf.org>; Mon, 5 Jun 2006 07:38:16 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25]) by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k55EcFFH026334 for <dmsp@ietf.org>; Mon, 5 Jun 2006 09:38:16 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Dmsp] Missing statement ?
Date: Mon, 5 Jun 2006 10:37:39 -0400
Message-ID: <6806C66D71ED9241BAECC0478173B71F97049D@de01exm69.ds.mot.com>
In-Reply-To: <BAF83494CE653943A97B9F755016A0660338FF05@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Dmsp] Missing statement ?
Thread-Index: AcaGGeSxyFcEIZkZSsqWupP13nkHKQCkkIQA
From: "Engelsma Jonathan-QA2678" <Jonathan.Engelsma@motorola.com>
To: "zze-BODIN Fabien RD-SIRP-LAN" <fabien.bodin@orange-ft.com>, <dmsp@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: GUILLOU Aurelien RD-SIRP-LAN <aurelien.guillou@orange-ft.com>
X-BeenThere: dmsp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Multimodal Synchronization Protocol <dmsp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dmsp>
List-Post: <mailto:dmsp@ietf.org>
List-Help: <mailto:dmsp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=subscribe>
Errors-To: dmsp-bounces@ietf.org

Fabien,

Yes, you are correct.  The Rx(SIG_VXML_START) event needs to be added to the VUA state machine in section 4.4.2.1 as you have specified in your mail.  I have updated in the next version of the specification.

Good find!

Thanks,
-jre

________________________________

From: zze-BODIN Fabien RD-SIRP-LAN [mailto:fabien.bodin@orange-ft.com] 
Sent: Friday, June 02, 2006 3:55 AM
To: dmsp@ietf.org
Cc: GUILLOU Aurelien RD-SIRP-LAN
Subject: [Dmsp] Missing statement ?



Hi, 
I am a trainee, working on an implementation of the DMSP with Aurélien Guillou from France Telecom. 
Trying to clarify the specification (draft-engelsma-dmsp-01.txt) with a schema, it seems that something is missing... 
Concerning the VUA state machine, CONN_CLOSED state is supposed to be the start point, right ? 
In this case, there should be a transition from CONN_CLOSED to VXML_START_RCVD.
Something like that:
+--------------------+-----------------+---------------+
| Event              | Next State      | Action        |
+--------------------+-----------------+---------------+
| Rx(SIG_VXML_START) | VXML_START_RCVD | N(VXML_START) |
+--------------------+-----------------+---------------+
should be add to the point 4.4.2.1. of the draft where the CONN_CLOSED state of the VUA state machine is outlined. 
Do you agree ? 
Thanks for answering 
Best regards 
Fabien Bodin 
P.S: I apologize for my english :) 


_______________________________________________
Dmsp mailing list
Dmsp@ietf.org
https://www1.ietf.org/mailman/listinfo/dmsp