From speechsc-bounces@ietf.org Mon Nov 06 21:19:14 2006 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 ; 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 ; 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, 6 Nov 2006 18:15:53 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: VoiceXML Input-modes problem - A proposal Thread-Index: AccCEqccYJ0QepUSSSaC4bl83kcyCA== From: "Saravanan Shanmugham \(sarvi\)" To: 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 |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 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0336851291==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============0336851291== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C70212.A76C96B9" This is a multi-part message in MIME format. ------_=_NextPart_001_01C70212.A76C96B9 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable =20 Hi, The topic of meeting VoiceXML input-modes property requirements through MRCP has come up a few times before. =20 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. =20 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.=20 =20 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. =20 Thanks, Sarvi =20 ------_=_NextPart_001_01C70212.A76C96B9 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
 
Hi,
The = topic of meeting=20 VoiceXML input-modes property requirements through MRCP has come = up a few=20 times before.
 
One = part of the=20 problem(relating to barge-in support) was addressed by = the=20 following
   =20 1. change START-OF-SPEECH to START-OF-INPUt
   =20 2. Add support for Input-Type header into the START-OF-INPUT event, = which=20 specifies what type of input was detected.
 
The = second piece=20 relating to controlling the recognition engine to limit recognition = to=20 dtmf-only or speech-only was not addressed.
I = would like=20 to address this problem by proposing a new header "Input-Mode" = header.=20 This will tell the recognition engine whether it should recognize = speech=20 only, dtmf only or both. The possible values for this header=20 are "speech-only", "dtmf-only" and "speech-dtmf". = This header MUST = be supported=20 by a recognition engine and MAY be carried in the RECOGNIZE,=20 SET-PARAMS and GET-PARAMS methods and their responses. =
 
Note: = This is a=20 proposal for resolving this issue. It does not in anyway mean that this=20 header/solution will or will not get into the next draft. That would = depend=20 purely on the time and resource constraints of the editors in releasing = the next=20 draft and the fact that the document is already in last call and the = change=20 limitations it might impose. If it does not get into the = next draft, which=20 is likey, this and a few other resolved but pending proposals will=20 be published as a follow-on draft/RFC.
 
Thanks,
Sarvi  
------_=_NextPart_001_01C70212.A76C96B9-- --===============0336851291== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc --===============0336851291==-- From speechsc-bounces@ietf.org Mon Nov 06 22:18:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhHTv-00036K-M2; Mon, 06 Nov 2006 22:18:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhHTv-00036C-14 for speechsc@ietf.org; Mon, 06 Nov 2006 22:18:35 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhHTt-0008He-LA for speechsc@ietf.org; Mon, 06 Nov 2006 22:18:35 -0500 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 06 Nov 2006 19:18:31 -0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAH2JT0WrR7PDh2dsb2JhbACMSgEBAQgOKg X-IronPort-AV: i="4.09,393,1157353200"; d="scan'208"; a="350442232:sNHT27336228" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA73IUTD000695 for ; Mon, 6 Nov 2006 19:18:30 -0800 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kA73IUAo004467 for ; Mon, 6 Nov 2006 19:18:30 -0800 (PST) Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 6 Nov 2006 19:18:30 -0800 Received: from [130.129.71.49] ([10.21.82.238]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 6 Nov 2006 19:18:30 -0800 Message-ID: <454FFB05.7070700@cisco.com> Date: Mon, 06 Nov 2006 22:18:29 -0500 From: Jonathan Rosenberg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: speechsc@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Nov 2006 03:18:30.0176 (UTC) FILETIME=[65FC6200:01C7021B] DKIM-Signature: a=rsa-sha1; q=dns; l=1898; t=1162869510; x=1163733510; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20 |Subject:ICE=20tutorial=3A=20Lunch=20logistics=20update=20[DO=20NOT=20REPLY]; X=v=3Dcisco.com=3B=20h=3Dwvzj+J9U4bGAuwmnCCs9T7HKQa8=3D; b=DW6xk1+K83jGOuzeXqLt7q0x7CbYRZwLzVvznC5VqKEnWAQAC7AZA02nfRYHwHoEz+s+N7tG K+Hsj2C8o1x1NjQNG8S0S4s5CEqDc9ZuyIPlwMiWrsBE2aFEb+VTqp7b; Authentication-Results: sj-dkim-3.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Subject: [Speechsc] ICE tutorial: Lunch logistics update [DO NOT REPLY] X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Apologies to multiple recipients) (DO NOT REPLY) WHAT: Tutorial on Interactive Connectivity Establishment (ICE) (http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-12.txt) WHEN: Tuesday, November 7 1130-1300 Lunch will be provided at a nominal fee of $10 Sandwiches, salad and chips Bring-your-own beverage Please get me your $10 prior to the end of the IETF meeting. Only 90 lunches have been ordered, its first-come-first-served I am covering this out of my own pocket, so please do get me your $10 if you partake of the food. I'm not tracking who eats or pays - we're on the honor system here! WHERE: Grande Ballroom A WHO: Anyone with an interest in RAI work that would like to learn more about ICE. WHY: ICE is one of the 'core' SIP specifications (according to the SIP hitchhikers guide) and seeing some good adoption. It's the IETF tool for NAT traversal for SIP-based media. However, it's a complex specification. The tutorial will assume only basic familiarity with SIP, SDP and NAT, and explain the rest. Participants will emerge with a high level understanding of the operation of ICE. The tutorial will be based on the pending -12 version. RSVP: Please send a note to me with the Subject line "ice-is-nice" (mailto:jdrosen@cisco.com?Subject=ice-is-nice). !DO NOT REPLY TO THIS NOTE! -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Wed Nov 08 02:09:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhhYq-0002Uo-DG; Wed, 08 Nov 2006 02:09:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhhYn-0002Tq-GH for speechsc@ietf.org; Wed, 08 Nov 2006 02:09:21 -0500 Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhhYl-00053R-EH for speechsc@ietf.org; Wed, 08 Nov 2006 02:09:21 -0500 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8E00CBOHLCBJ@szxga03-in.huawei.com> for speechsc@ietf.org; Wed, 08 Nov 2006 15:17:36 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8E00MZVHLCJD@szxga03-in.huawei.com> for speechsc@ietf.org; Wed, 08 Nov 2006 15:17:36 +0800 (CST) Received: from [127.0.0.1] ([10.18.4.172]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J8E00DA4HD0K8@szxml03-in.huawei.com> for speechsc@ietf.org; Wed, 08 Nov 2006 15:12:38 +0800 (CST) Date: Wed, 08 Nov 2006 12:35:39 +0530 From: Srinivas R Thota To: speechsc@ietf.org Message-id: <455181C3.7040104@huawei.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5 (Windows/20051201) X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Subject: [Speechsc] query Simultaneous RECOGNIZE and RECORD MRCP media requests on the same media X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Hi , Can RECOGNIZE and RECORD MRCP media requests on the same media ? (for example for a use-case wherein user utterances have to be record while attempting recognition. ) I know that the same can be archived using save-waveform header in RECOGNIZE, but is it possible to do media-forking between Recognizer and Recorder which are different resources and archive this, does it have any specific problem. Can this work even if Recognizer and Recorder on different systems. ? Thanks & Regards, Srinivas R Thota -- -- *************************************************************************************** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Wed Nov 08 13:49:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhsUN-0001CE-B4; Wed, 08 Nov 2006 13:49:31 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhsUL-0001C9-SB for speechsc@ietf.org; Wed, 08 Nov 2006 13:49:29 -0500 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhsUK-0000Bm-GJ for speechsc@ietf.org; Wed, 08 Nov 2006 13:49:29 -0500 Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 08 Nov 2006 10:49:28 -0800 X-IronPort-AV: i="4.09,401,1157353200"; d="scan'208"; a="87363884:sNHT51389505" Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA8InRIn007302; Wed, 8 Nov 2006 10:49:27 -0800 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kA8InRin001187; Wed, 8 Nov 2006 10:49:27 -0800 (PST) Received: from xmb-sjc-229.amer.cisco.com ([128.107.191.122]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Nov 2006 10:49:27 -0800 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 Subject: RE: [Speechsc] query Simultaneous RECOGNIZE and RECORD MRCP media requests on the same media Date: Wed, 8 Nov 2006 10:49:25 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speechsc] query Simultaneous RECOGNIZE and RECORD MRCP media requests on the same media Thread-Index: AccDBXMdnKsOqptFTGybj6CBu3W2zAAX+JYg From: "Saravanan Shanmugham \(sarvi\)" To: "Srinivas R Thota" , X-OriginalArrivalTime: 08 Nov 2006 18:49:27.0732 (UTC) FILETIME=[9E18C740:01C70366] DKIM-Signature: a=rsa-sha1; q=dns; l=2823; t=1163011767; x=1163875767; c=relaxed/simple; s=sjdkim1002; 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 |Subject:RE=3A=20[Speechsc]=20query=20Simultaneous=20RECOGNIZE=20and=20RECORD=20M RCP=20media=20requests=20on=20the=20same=20media; X=v=3Dcisco.com=3B=20h=3DHFwGfo64g4fn3jRVB6YZ/pNWD0U=3D; b=PuJwfeiti43aL50WJr/Y4CTDxh7ovZa9nihVbysyJCOyV4Ppu5DL45+0ZXY+PCmgVT6WYk5k 35BTtN6mX9TGoAV/Cziuj5HM3ofSs05R2uXDRIWKtSIivcAeeKmuxNQ+; Authentication-Results: sj-dkim-1.cisco.com; header.From=sarvi@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org When you setup your media and control channels, you associate the control channels(resource) to the media channel. Within a single MRCP session A single media channel can be associated with more that one control channel i.e resource. So the resources can share and process that single channel. In the server this may be implemented through forking to the 2 resources or whatever other means is appropriate for the server implementation.=20 So, Yes, you can issue a RECORD on the recorder resource while at the same time issuing a RECOGNIZE on the recognizer resource. The protocol allows this. The question is whether a particular MRCP server implementation supports this. Now, if the recorder and recognizer are on different servers, they are separate MRCP sessions. Here the control channels(resources), will not be able to share a media pipe. But this is not say the client may not fork its media source 2-ways and send them to the recognizer and recorder resources separately. Thx, Sarvi -----Original Message----- From: Srinivas R Thota [mailto:srinivas_thota@huawei.com]=20 Sent: Tuesday, November 07, 2006 11:06 PM To: speechsc@ietf.org Subject: [Speechsc] query Simultaneous RECOGNIZE and=20 RECORD MRCP media requests on the same media =20 Hi , =20 Can RECOGNIZE and RECORD MRCP media requests on the same media ? (for example for a use-case wherein user utterances have=20 to be record while attempting recognition. ) I know that=20 the same can be archived using save-waveform header in=20 RECOGNIZE, but is it possible to do media-forking between=20 Recognizer and Recorder which are different resources and=20 archive this, does it have any specific problem. Can this work even if Recognizer and Recorder on=20 different systems. ? =20 Thanks & Regards, Srinivas R Thota =20 --=20 =20 -- *********************************************************** **************************** This e-mail and attachments contain confidential=20 information from HUAWEI, which is intended only for the=20 person or entity whose address is listed above. Any use of=20 the information contained herein in any way (including,=20 but not limited to, total or partial disclosure,=20 reproduction, or dissemination) by persons other than the=20 intended recipient's) is prohibited. If you receive this=20 e-mail in error, please notify the sender by phone or=20 email immediately and delete it! =20 =20 =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Sat Nov 11 14:35:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiycS-00048s-DC; Sat, 11 Nov 2006 14:34:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiycR-00047s-3O for speechsc@ietf.org; Sat, 11 Nov 2006 14:34:23 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiycO-0002Bu-Lc for speechsc@ietf.org; Sat, 11 Nov 2006 14:34:23 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8K00ARUZNTGS@szxga01-in.huawei.com> for speechsc@ietf.org; Sun, 12 Nov 2006 03:33:29 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8K00A73ZNSMT@szxga01-in.huawei.com> for speechsc@ietf.org; Sun, 12 Nov 2006 03:33:29 +0800 (CST) Received: from HTIPL20760 ([10.18.4.165]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J8K008B1ZNQVU@szxml04-in.huawei.com> for speechsc@ietf.org; Sun, 12 Nov 2006 03:33:28 +0800 (CST) Date: Sun, 12 Nov 2006 01:03:26 +0530 From: sreekanth To: Dan Burnett , "Saravanan Shanmugham (sarvi)" Message-id: <002c01c705c8$42ad4c00$a504120a@china.huawei.com> Organization: huawei MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 1.6 (+) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: speechsc@ietf.org Subject: [Speechsc] (no subject) X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sreekanth List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1298958428==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============1298958428== Content-type: multipart/alternative; boundary="Boundary_(ID_hO7msR/wOTRmXn5lOGoU9g)" This is a multi-part message in MIME format. --Boundary_(ID_hO7msR/wOTRmXn5lOGoU9g) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Hi, Accept grammar as per the rfc 2616 is Accept = "Accept" ":" #( media-range [ accept-params ] )CRLF The following is from rfc 733.. "Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is, "(element),,(element)" is permitted, but counts as only two elements." Is there is any use case of using this '#' which unnecessarily makes parsing complex.. Can we change it to construct * Accept = "Accept" ":" *( media-range [ accept-params ] )CRLF Regards, Sreekanth This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! --Boundary_(ID_hO7msR/wOTRmXn5lOGoU9g) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
Hi,
 
Accept grammar as per the rfc 2616 is
 
Accept           =    "Accept" ":" #( media-range [ accept-params ] )CRLF
 
The following is from rfc 733..
 
"Wherever this construct is used, null elements are allowed, but do not  contribute  to  the  count  of  elements
present.   That  is,  "(element),,(element)"  is  permitted,  but counts as only two  elements."
 
Is there is any use case of using this '#' which unnecessarily makes parsing complex..
 
Can we change it to construct  * 
 
Accept           =    "Accept" ":"  *( media-range [ accept-params ] )CRLF
 
 
Regards,
Sreekanth
 
 
This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
 
 
--Boundary_(ID_hO7msR/wOTRmXn5lOGoU9g)-- --===============1298958428== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc --===============1298958428==-- From speechsc-bounces@ietf.org Sun Nov 12 09:16:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjG7s-0007Ey-Vm; Sun, 12 Nov 2006 09:16:01 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjG7r-0007DY-MC for speechsc@ietf.org; Sun, 12 Nov 2006 09:15:59 -0500 Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GjG7p-00061x-OK for speechsc@ietf.org; Sun, 12 Nov 2006 09:15:59 -0500 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8M00FTEFL22L@szxga03-in.huawei.com> for speechsc@ietf.org; Sun, 12 Nov 2006 22:15:02 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8M00MVDFL1MK@szxga03-in.huawei.com> for speechsc@ietf.org; Sun, 12 Nov 2006 22:15:02 +0800 (CST) Received: from [127.0.0.1] ([10.18.4.172]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J8M00DQHFL01V@szxml04-in.huawei.com> for speechsc@ietf.org; Sun, 12 Nov 2006 22:15:01 +0800 (CST) Date: Sun, 12 Nov 2006 19:45:01 +0530 From: Srinivas R Thota To: speechsc@ietf.org Message-id: <45572C65.7050400@huawei.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5 (Windows/20051201) X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Subject: [Speechsc] query on grammar precedence and recognized results X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Hi, referring to section 9.9. RECOGNIZE of draft-ietf-speechsc-mrcpv2-11.txt "The order of these grammars specifies the precedence of the grammars which is used when more than one grammar in the list matches the speech; in this case, the grammar with the higher precedence is returned as a match. This precedence capability is useful in applications like VoiceXML browsers to order grammars specified at the dialog, document and root level of a VoiceXML application." [1] Is there any way to turn off the precedence.? [2] Does this mean only one result with highest precedence will be present in RECOGNIZE-COMPLETE event ? [3] If we need to get more results can we use GET-RESULT. ? [4] Can we get a result which has more confidence but low on precedence ? Please clarify Thanks, Srinivas R Thota -- *************************************************************************************** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Wed Nov 15 07:38:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkK1P-0006CA-Vp; Wed, 15 Nov 2006 07:37:43 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkK1O-0006At-Tf for speechsc@ietf.org; Wed, 15 Nov 2006 07:37:42 -0500 Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkK1L-0004AQ-Vc for speechsc@ietf.org; Wed, 15 Nov 2006 07:37:42 -0500 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8R00JBJUZTWK@szxga03-in.huawei.com> for speechsc@ietf.org; Wed, 15 Nov 2006 20:35:53 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8R00BSVUZSG5@szxga03-in.huawei.com> for speechsc@ietf.org; Wed, 15 Nov 2006 20:35:53 +0800 (CST) Received: from HTIPL20760 ([10.18.4.165]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J8R00MVCUZRB9@szxml04-in.huawei.com> for speechsc@ietf.org; Wed, 15 Nov 2006 20:35:52 +0800 (CST) Date: Wed, 15 Nov 2006 18:05:51 +0530 From: sreekanth To: "Saravanan Shanmugham (sarvi)" Message-id: <003801c708b2$960bb8e0$a504120a@china.huawei.com> Organization: huawei MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-Priority: 3 X-MSMail-priority: Normal References: X-Spam-Score: 0.0 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Cc: speechsc@ietf.org Subject: [Speechsc] Precision of Float-value in MRCP X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sreekanth List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1270946336==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============1270946336== Content-type: multipart/alternative; boundary="Boundary_(ID_O23VukkAAg81DRiyJrGTRA)" This is a multi-part message in MIME format. --Boundary_(ID_O23VukkAAg81DRiyJrGTRA) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Hi, The draft-11 does not specfiy the ABNF grammar for the float-value used in Min-Verification-Score header. min-verification-score = "Min-Verification-Score" ":" [-] Float-value CRLF Pls clarify on this Sreekanth ----- Original Message ----- From: Saravanan Shanmugham (sarvi) To: sreekanth ; Dan Burnett Cc: speechsc@ietf.org Sent: Saturday, October 28, 2006 6:40 AM Subject: RE: [Speechsc] (no subject) No. SPEAK-COMPLETE makes sense only if there was a 200 response meaning that the request was initiated successfully. i.e. SPEAK-COMPLETE makes sense if the resource was in a IN-PROGRESS/PENDING state. Sarvi ---------------------------------------------------------------------------- From: sreekanth [mailto:sreekanthm@huawei.com] Sent: Thursday, October 26, 2006 11:04 PM To: Dan Burnett; Saravanan Shanmugham (sarvi) Cc: speechsc@ietf.org Subject: [Speechsc] (no subject) Importance: High Hi, Can the MRCP server send SPEAK-COMPLETE without sending 200 responses (IN-PROGRESS or PENDING state)... MRCP Client MRCP server -------------SPEAK-------------------------> <-------SPEAK-COMPLETE----------- Can this happen in any error sceneriao(any server side failure)???? Pls clarify on this.... Regards, Sreekanth --Boundary_(ID_O23VukkAAg81DRiyJrGTRA) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
Hi,
 
The draft-11 does not specfiy the ABNF grammar for the float-value used in Min-Verification-Score header.

min-verification-score = "Min-Verification-Score" ":" [-] Float-value CRLF

Pls clarify on this

Sreekanth

 

 

 

 
----- Original Message -----
Sent: Saturday, October 28, 2006 6:40 AM
Subject: RE: [Speechsc] (no subject)

No.
SPEAK-COMPLETE makes sense only if there was a 200 response meaning that the request was initiated successfully.
i.e. SPEAK-COMPLETE makes sense if the resource was in a IN-PROGRESS/PENDING state.
 
Sarvi

From: sreekanth [mailto:sreekanthm@huawei.com]
Sent: Thursday, October 26, 2006 11:04 PM
To: Dan Burnett; Saravanan Shanmugham (sarvi)
Cc: speechsc@ietf.org
Subject: [Speechsc] (no subject)
Importance: High

Hi,
 
 
Can the MRCP server send SPEAK-COMPLETE without sending 200 responses (IN-PROGRESS or PENDING state)...
 
 
MRCP Client                            MRCP server
 
           -------------SPEAK------------------------->
 
           <-------SPEAK-COMPLETE-----------
 
Can this happen in any error sceneriao(any server side failure)????
Pls clarify on this....
 
 
Regards,
Sreekanth
 
 
 
              
--Boundary_(ID_O23VukkAAg81DRiyJrGTRA)-- --===============1270946336== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc --===============1270946336==-- From speechsc-bounces@ietf.org Fri Nov 17 09:49:55 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gl51f-0000ZL-1p; Fri, 17 Nov 2006 09:49:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gl51c-0000Xx-Tj for speechsc@ietf.org; Fri, 17 Nov 2006 09:49:05 -0500 Received: from g2.genesyslab.com ([198.49.180.210]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gl51b-0005uj-J1 for speechsc@ietf.org; Fri, 17 Nov 2006 09:49:04 -0500 Received: from NAHALD.us.int.genesyslab.com ([192.168.20.92]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 17 Nov 2006 06:49:02 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: [speechsc] Inputmodes Proposal Date: Fri, 17 Nov 2006 06:48:58 -0800 Message-ID: <059AF07365DC474393A19A3AF187DF74165E27@NAHALD.us.int.genesyslab.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [speechsc] Inputmodes Proposal Thread-Index: AccKV4NlNy07gg0/QwObTg4W9XE7mg== From: "Andrew Wahbe" To: "IETF SPEECHSC" X-OriginalArrivalTime: 17 Nov 2006 14:49:02.0254 (UTC) FILETIME=[858F44E0:01C70A57] X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0260493956==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============0260493956== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C70A57.859BF66E" This is a multi-part message in MIME format. ------_=_NextPart_001_01C70A57.859BF66E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The VoiceXML Forum MRCP Liaison Committee has discussed the proposed feature for specifying the input-modes enabled in a recognition (see http://www.ietf.org/mail-archive/web/speechsc/current/msg02007.html ). The goal of this discussion was to determine if the omission of this feature would prevent MRCP v2 from being used to implement a compliant VoiceXML 2.x platform. The Committee was unable to reach agreement on this issue. We encourage the contribution of individual opinions on this issue to the SpeechSC list so that a resolution can be reached. It should be noted that this discussion was not meant to address the merits of the proposal itself. The outcome should not be used to infer Committee members' opinions on whether the proposed feature should be included in MRCP v2 or any subsequent RFC. =20 =20 Andrew Wahbe VoiceXML Forum MRCP Liaison Committee ------_=_NextPart_001_01C70A57.859BF66E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
The = VoiceXML Forum=20 MRCP Liaison Committee has discussed the proposed feature for specifying = the=20 input-modes enabled in a recognition (see http://www.ietf.org/mail-archive/web/speechsc/current/msg02007.h= tml). The goal of this=20 discussion was to determine if the omission of this feature would = prevent=20 MRCP v2 from being used to implement a compliant VoiceXML 2.x platform.=20 The Committee was unable=20 to reach agreement on this issue. We encourage the=20 contribution of individual opinions on this issue to the SpeechSC = list so that a resolution can be reached.=20 It=20 should be noted that this discussion was not meant to = address the=20 merits of the proposal itself. = The outcome should not be used to infer = Committee=20 members' opinions on whether the proposed feature should = be included=20 in MRCP v2 or any subsequent RFC.
 
 
Andrew=20 Wahbe
VoiceXML = Forum MRCP=20 Liaison Committee
------_=_NextPart_001_01C70A57.859BF66E-- --===============0260493956== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc --===============0260493956==-- From speechsc-bounces@ietf.org Wed Nov 22 02:04:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gmm9N-000883-Lp; Wed, 22 Nov 2006 02:04:05 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gmm9L-00087r-IP for speechsc@ietf.org; Wed, 22 Nov 2006 02:04:03 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gmm9J-0000Iu-Mz for speechsc@ietf.org; Wed, 22 Nov 2006 02:04:03 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J9400IERDYWLQ@szxga01-in.huawei.com> for speechsc@ietf.org; Wed, 22 Nov 2006 14:56:56 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J94009Y2DYWCH@szxga01-in.huawei.com> for speechsc@ietf.org; Wed, 22 Nov 2006 14:56:56 +0800 (CST) Received: from HTIPL20760 ([10.18.4.165]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J94004CVDYUQA@szxml03-in.huawei.com> for speechsc@ietf.org; Wed, 22 Nov 2006 14:56:56 +0800 (CST) Date: Wed, 22 Nov 2006 12:26:52 +0530 From: sreekanth To: "Saravanan Shanmugham (sarvi)" , Dan Burnett Message-id: <002601c70e03$648cfa80$a504120a@china.huawei.com> Organization: huawei MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-Priority: 3 X-MSMail-priority: Normal References: X-Spam-Score: 0.0 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Cc: speechsc@ietf.org Subject: [Speechsc] Query in the general message header ABNF X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sreekanth List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1422310622==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============1422310622== Content-type: multipart/alternative; boundary="Boundary_(ID_AtSaIMOuRRwdXfBYSKuXdA)" This is a multi-part message in MIME format. --Boundary_(ID_AtSaIMOuRRwdXfBYSKuXdA) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT This is a quote from the section 6.2 of mrcpv2-draft-11 message-header = field-name ":" [ field-value ] field-name = token field-value = *LWS field-content *( CRLF 1*LWS field-content) field-content = As per the above rule if the header if of list type, is it mandatory that the multiple header values MUST have atleast one LWS??? In the header ABNF already seperator for the multiple values is defined.. So Why do we need this LWS?? Pls clarify on this. Sreekanth --Boundary_(ID_AtSaIMOuRRwdXfBYSKuXdA) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT

This is a quote from the section 6.2 of mrcpv2-draft-11

message-header = field-name ":" [ field-value ]

field-name = token

field-value = *LWS field-content *( CRLF 1*LWS field-content)

field-content = <the OCTETs making up the field-value

and consisting of either *TEXT or combinations

of token, separators, and quoted-string>

 

As per the above rule if the header if of list type,  is it  mandatory that the multiple header values MUST have atleast one LWS???

In the header ABNF already seperator for the multiple values is defined.. So Why do we need this LWS??

Pls clarify on this.

Sreekanth

 

 

 

--Boundary_(ID_AtSaIMOuRRwdXfBYSKuXdA)-- --===============1422310622== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc --===============1422310622==-- From speechsc-bounces@ietf.org Thu Nov 23 06:31:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnCnV-0007Zt-9a; Thu, 23 Nov 2006 06:31:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnCnT-0007YO-M7 for speechsc@ietf.org; Thu, 23 Nov 2006 06:31:15 -0500 Received: from smtp2.wanadoo.co.uk ([193.252.22.157] helo=smtp2.freeserve.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GnCnO-0007vC-64 for speechsc@ietf.org; Thu, 23 Nov 2006 06:31:15 -0500 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3111.me.freeserve.com (SMTP Server) with ESMTP id 9A8A6200008D; Thu, 23 Nov 2006 12:31:09 +0100 (CET) Received: from Codalogic (user-5445210e.lns4-c11.dsl.pol.co.uk [84.69.33.14]) by mwinf3111.me.freeserve.com (SMTP Server) with SMTP id 5132C200008A; Thu, 23 Nov 2006 12:31:09 +0100 (CET) X-ME-UUID: 20061123113109332.5132C200008A@mwinf3111.me.freeserve.com Message-ID: <00a601c70ef2$de567130$1c00a8c0@Codalogic> From: "Pete Cordell" To: "sreekanth" References: <002601c70e03$648cfa80$a504120a@china.huawei.com> Subject: Re: [Speechsc] Query in the general message header ABNF Date: Thu, 23 Nov 2006 11:31:03 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Spam-Score: 1.9 (+) X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196 Cc: speechsc@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Hi Sreekanth, This is the general format of all headers, and the concept is consistent across many protocols including SMTP, HTTP and SIP. This general rule allows you to readily find the beginning of headers without having to do detailed parsing of each header (e.g. just look for non-white space after CR LF). It also allows you to skip over, possibly ignorable, headers that may not be defined yet. BTW - this isn't just for list type headers. It can be used for any header that benefits from being spread across multiple lines. e.g.: MyHeader: foo bar do da = 18 To the doc authors: -------------------- I note that section 6.2 says: "The value MAY be preceded by any amount of LWS, though a single SP is preferred." However, most of the examples don't include a space. Maybe no space is preferred for MRCP? Also, I can't find anywhere that says whether the EBNF grammar is explicit about where white space can be included or not. Some rules suggest that it is and some rules imply that it is not (i.e. no mention of optional WS). Sorry if this has been raised before. And, just in case it's not been raised before, should the EBNF for the method name and message-header be made extensible? e.g. something like: method-name = generic-method / synthesizer-method / recorder-method / recognizer-method / verifier-method / token ; <------ message-header = 1*(generic-header / resource-header / extension-header) extension-header = field-name ":" [ field-value ] If appropriate, perhaps these issues can be discussed at the start of the EBNF section (15). HTH, Pete. -- ============================================= Pete Cordell Tech-Know-Ware Ltd for XML to C++ data binding visit http://www.tech-know-ware.com/lmx (or http://www.xml2cpp.com) ============================================= ----- Original Message ----- From: "sreekanth" To: "Saravanan Shanmugham (sarvi)" ; "Dan Burnett" Cc: Sent: Wednesday, November 22, 2006 6:56 AM Subject: [Speechsc] Query in the general message header ABNF > This is a quote from the section 6.2 of mrcpv2-draft-11 > > message-header = field-name ":" [ field-value ] > > field-name = token > > field-value = *LWS field-content *( CRLF 1*LWS field-content) > > field-content = > and consisting of either *TEXT or combinations > > of token, separators, and quoted-string> > > > > As per the above rule if the header if of list type, is it mandatory > that the multiple header values MUST have atleast one LWS??? > > In the header ABNF already seperator for the multiple values is defined.. > So Why do we need this LWS?? > > Pls clarify on this. > > Sreekanth > > > > > > > -------------------------------------------------------------------------------- > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www1.ietf.org/mailman/listinfo/speechsc > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc