[Speechsc] VoiceXML Input-modes problem - A proposal

"Saravanan Shanmugham \(sarvi\)" <sarvi@cisco.com> Tue, 07 November 2006 02:18 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhGXx-0005Nq-QI; Mon, 06 Nov 2006 21:18:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhGXv-0005Lz-JZ for speechsc@ietf.org; Mon, 06 Nov 2006 21:18:39 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhGXA-00075Z-Q4 for speechsc@ietf.org; Mon, 06 Nov 2006 21:17:54 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88]) by sj-iport-4.cisco.com with ESMTP; 06 Nov 2006 18:15:58 -0800
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAMR6T0WrRApY/2dsb2JhbACCcg
X-IronPort-AV: i="4.09,393,1157353200"; d="scan'208,217"; a="1862432976:sNHT134984972"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-7.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA72FwZO017227 for <speechsc@ietf.org>; Mon, 6 Nov 2006 18:15:58 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kA72FqWA009084 for <speechsc@ietf.org>; Mon, 6 Nov 2006 18:15:57 -0800 (PST)
Received: from xmb-sjc-229.amer.cisco.com ([128.107.191.122]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 6 Nov 2006 18:15:54 -0800
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 06 Nov 2006 18:15:53 -0800
Message-ID: <C6A1C20DB743364EB446E923B2229FEF02C09507@xmb-sjc-229.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: VoiceXML Input-modes problem - A proposal
Thread-Index: AccCEqccYJ0QepUSSSaC4bl83kcyCA==
From: "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>
To: speechsc@ietf.org
X-OriginalArrivalTime: 07 Nov 2006 02:15:54.0741 (UTC) FILETIME=[A7927A50:01C70212]
DKIM-Signature: a=rsa-sha1; q=dns; l=5155; t=1162865758; x=1163729758; c=relaxed/simple; s=sjdkim7002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sarvi@cisco.com; z=From:=22Saravanan=20Shanmugham=20\(sarvi\)=22=20<sarvi@cisco.com> |Subject:VoiceXML=20Input-modes=20problem=20-=20A=20proposal; X=v=3Dcisco.com=3B=20h=3D6grvQdRPrxVDuB8TKdIvGE8VdqI=3D; b=NTN79lrHVM6EM/c2xkhrwmN7G5ehFf79fOK1PtJcivfbMoHCJcrNQi0gSAgDy8TJfgE51l6C yvAc4uaRXsLVcOjPbXhto2GvPh1DIvUiKARcZiT6JVOda3bOrmZQIvcu;
Authentication-Results: sj-dkim-7.cisco.com; header.From=sarvi@cisco.com; dkim=pass ( 59 extraneous bytes; sig from cisco.com verified; );
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Subject: [Speechsc] VoiceXML Input-modes problem - A proposal
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Speech Services Control Working Group <speechsc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:speechsc@ietf.org>
List-Help: <mailto:speechsc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0336851291=="
Errors-To: speechsc-bounces@ietf.org

 
Hi,
The topic of meeting VoiceXML input-modes property requirements through
MRCP has come up a few times before.
 
One part of the problem(relating to barge-in support) was addressed by
the following
    1. change START-OF-SPEECH to START-OF-INPUt
    2. Add support for Input-Type header into the START-OF-INPUT event,
which specifies what type of input was detected.
 
The second piece relating to controlling the recognition engine to limit
recognition to dtmf-only or speech-only was not addressed.

I would like to address this problem by proposing a new header
"Input-Mode" header. This will tell the recognition engine whether it
should recognize speech only, dtmf only or both. The possible values for
this header are "speech-only", "dtmf-only" and "speech-dtmf". This
header MUST be supported by a recognition engine and MAY be carried in
the RECOGNIZE, SET-PARAMS and GET-PARAMS methods and their responses. 
 
Note: This is a proposal for resolving this issue. It does not in anyway
mean that this header/solution will or will not get into the next draft.
That would depend purely on the time and resource constraints of the
editors in releasing the next draft and the fact that the document is
already in last call and the change limitations it might impose. If it
does not get into the next draft, which is likey, this and a few other
resolved but pending proposals will be published as a follow-on
draft/RFC.
 
Thanks,
Sarvi  
_______________________________________________
Speechsc mailing list
Speechsc@ietf.org
https://www1.ietf.org/mailman/listinfo/speechsc