From speechsc-bounces@ietf.org Mon Dec 04 05:56:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrBU8-0002CA-L9; Mon, 04 Dec 2006 05:55:44 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrBU7-0002BY-7v
	for speechsc@ietf.org; Mon, 04 Dec 2006 05:55:43 -0500
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GrBTu-0000HD-4o
	for speechsc@ietf.org; Mon, 04 Dec 2006 05:55:43 -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 <0J9Q00DL9SSGII@szxga03-in.huawei.com> for
	speechsc@ietf.org; Mon, 04 Dec 2006 17:24:16 +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 <0J9Q00FA7SS9S2@szxga03-in.huawei.com> for
	speechsc@ietf.org; Mon, 04 Dec 2006 17:24:16 +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 <0J9Q00AC8SS6WL@szxml03-in.huawei.com> for
	speechsc@ietf.org; Mon, 04 Dec 2006 17:24:08 +0800 (CST)
Date: Mon, 04 Dec 2006 14:54:05 +0530
From: sreekanth <sreekanthm@huawei.com>
Subject: Re: [Speechsc] Query in the general message header ABNF
To: Pete Cordell <pete@tech-know-ware.com>
Message-id: <000a01c71785$f29579c0$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: <C6A1C20DB743364EB446E923B2229FEF02C09BE9@xmb-sjc-229.amer.cisco.com>
	<002601c70e03$648cfa80$a504120a@china.huawei.com>
	<00a601c70ef2$de567130$1c00a8c0@Codalogic>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17cf8eab1d6bbd2874a56f9e3554d91d
Cc: speechsc@ietf.org, "Saravanan Shanmugham \(sarvi\)" <sarvi@cisco.com>
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sreekanth <sreekanthm@huawei.com>
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="===============0060020843=="
Errors-To: speechsc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0060020843==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_9RCmFMNGOxeeR7rPpmf+kA)"

This is a multi-part message in MIME format.

--Boundary_(ID_9RCmFMNGOxeeR7rPpmf+kA)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hi Pete,

Thanks for replying.. 

1) I still have one more query on the section 6.2 defning the header grammar..

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 field value syntax, we can msg hdrs like

header:                                      // CRLF and WSP CRLF -> LWS
                                                  // WSP CRLF -> LWS
 foo                                            // WSP CRLF -> LWS
  bar                                            // WSP CRLF -> LWS
  =                                               // WSP CRLF -> LWS
  18CRLF

Since the LWS([*WSP CRLF] 1*WSP) can again have WSP followed by CRLF.. There can be 2 lines after the header: in the above example..


2) The draft does not explain the ABNF grammar for Extension header.

3) The ABNF grammar for voiceprint-identifier has some ambiguity .

    "Voiceprint-Identifier" ":" 1*VCHAR "." 1*VCHAR *[";" 1*VCHAR "." 1*VCHAR] CRLF

    The seperator '.'  is again part of VCHAR.. So there is a overlap between the Header Value and the seperator..



Pls clarify on this.


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!


----- Original Message ----- 
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "sreekanth" <sreekanthm@huawei.com>
Cc: <speechsc@ietf.org>
Sent: Thursday, November 23, 2006 5:01 PM
Subject: Re: [Speechsc] Query in the general message header ABNF


> 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" <sreekanthm@huawei.com>
> To: "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>; "Dan Burnett" 
> <dan_burnett2000@yahoo.com>
> Cc: <speechsc@ietf.org>
> 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 = <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
>>
>>
>>
>>
>>
>>
>>
> 
> 
> --------------------------------------------------------------------------------
> 
> 
>> _______________________________________________
>> Speechsc mailing list
>> Speechsc@ietf.org
>> https://www1.ietf.org/mailman/listinfo/speechsc
>> 
> 
> 
>

--Boundary_(ID_9RCmFMNGOxeeR7rPpmf+kA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2995" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=Arial size=2>Hi Pete,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thanks for replying.. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>1) I still have one more query on the section 6.2 
defning the header grammar..</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>message-header = field-name ":" [ field-value 
]</FONT></DIV>
<DIV><FONT face=Arial size=2>field-name = token</FONT></DIV>
<DIV><FONT face=Arial size=2><STRONG>field-value = *LWS field-content *( CRLF 
1*LWS field-content)</STRONG><BR>field-content = &lt;the OCTETs making up the 
field-value<BR>&nbsp; and consisting of either *TEXT or combinations of token, 
separators, and quoted-string&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>As per the field value syntax, we can msg hdrs 
like</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><STRONG>header:&nbsp;</STRONG></FONT><FONT 
face=Arial 
size=2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// CRLF and </STRONG>WSP CRLF -&gt; LWS</FONT></DIV>
<DIV><FONT face=Arial 
size=2><STRONG>&nbsp;</STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;// 
WSP CRLF -&gt; LWS</FONT></DIV>
<DIV><FONT face=Arial 
size=2><STRONG>&nbsp;foo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// </STRONG>WSP CRLF -&gt; LWS</FONT></DIV>
<DIV><FONT face=Arial size=2><STRONG>&nbsp; 
bar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// </STRONG>WSP CRLF -&gt; LWS</FONT></DIV>
<DIV><FONT face=Arial size=2><STRONG>&nbsp; 
=&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// </STRONG>WSP CRLF -&gt; LWS</FONT></DIV>
<DIV><FONT face=Arial size=2><STRONG>&nbsp; 18CRLF</STRONG></FONT></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Since the LWS([*WSP CRLF] 1*WSP) can again have WSP 
followed by CRLF.. There can be 2 lines after the header: in the above 
example..</FONT></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2>2) The draft does not explain the ABNF 
grammar for Extension header.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2>3) The ABNF grammar for&nbsp;<FONT 
size=2>voiceprint-identifier&nbsp;has some 
ambiguity&nbsp;.</FONT></FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2><FONT 
size=2></FONT></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><FONT size=2><STRONG>&nbsp;&nbsp;&nbsp; 
</STRONG>"Voiceprint-Identifier" ":" 1*VCHAR "." 1*VCHAR *[";" 1*VCHAR "." 
1*VCHAR] CRLF</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; The seperator '.'&nbsp; is again 
part of VCHAR.. So there is a overlap between the Header Value and the 
seperator..</FONT></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Pls clarify on this.</FONT></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2>Regards,</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>Sreekanth</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><STRONG></STRONG>&nbsp;</DIV></FONT>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>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!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>----- Original Message ----- </FONT>
<DIV><FONT face=Arial size=2>From: "Pete Cordell" &lt;</FONT><A 
href="mailto:pete@tech-know-ware.com"><FONT face=Arial 
size=2>pete@tech-know-ware.com</FONT></A><FONT face=Arial 
size=2>&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>To: "sreekanth" &lt;</FONT><A 
href="mailto:sreekanthm@huawei.com"><FONT face=Arial 
size=2>sreekanthm@huawei.com</FONT></A><FONT face=Arial size=2>&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>Cc: &lt;</FONT><A 
href="mailto:speechsc@ietf.org"><FONT face=Arial 
size=2>speechsc@ietf.org</FONT></A><FONT face=Arial size=2>&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>Sent: Thursday, November 23, 2006 5:01 
PM</FONT></DIV>
<DIV><FONT face=Arial size=2>Subject: Re: [Speechsc] Query in the general 
message header ABNF</FONT></DIV></DIV>
<DIV><FONT face=Arial><BR><FONT size=2></FONT></FONT></DIV><FONT face=Arial 
size=2>&gt; Hi Sreekanth,<BR>&gt; <BR>&gt; This is the general format of all 
headers, and the concept is consistent <BR>&gt; across many protocols including 
SMTP, HTTP and SIP.&nbsp; This general rule <BR>&gt; allows you to readily find 
the beginning of headers without having to do <BR>&gt; detailed parsing of each 
header (e.g. just look for non-white space after CR <BR>&gt; LF).&nbsp; It also 
allows you to skip over, possibly ignorable, headers that may <BR>&gt; not be 
defined yet.<BR>&gt; <BR>&gt; BTW - this isn't just for list type headers.&nbsp; 
It can be used for any header <BR>&gt; that benefits from being spread across 
multiple lines. e.g.:<BR>&gt; <BR>&gt; MyHeader: foo<BR>&gt;&nbsp;&nbsp;&nbsp; 
bar<BR>&gt;&nbsp;&nbsp;&nbsp; do<BR>&gt;&nbsp;&nbsp;&nbsp; 
da<BR>&gt;&nbsp;&nbsp;&nbsp; =<BR>&gt;&nbsp;&nbsp;&nbsp; 18<BR>&gt; <BR>&gt; 
<BR>&gt; To the doc authors:<BR>&gt; --------------------<BR>&gt; I note that 
section 6.2 says: "The value MAY be preceded by any amount of <BR>&gt; LWS, 
though a single SP is preferred."&nbsp; However, most of the examples don't 
<BR>&gt; include a space.&nbsp; Maybe no space is preferred for MRCP?<BR>&gt; 
<BR>&gt; Also, I can't find anywhere that says whether the EBNF grammar is 
explicit <BR>&gt; about where white space can be included or not.&nbsp; Some 
rules suggest that it <BR>&gt; is and some rules imply that it is not (i.e. no 
mention of optional WS). <BR>&gt; Sorry if this has been raised before.<BR>&gt; 
<BR>&gt; And, just in case it's not been raised before, should the EBNF for the 
<BR>&gt; method name and message-header be made extensible? e.g. something 
like:<BR>&gt; <BR>&gt; method-name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
=&nbsp;&nbsp;&nbsp; 
generic-method<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; 
synthesizer-method<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; 
recorder-method<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; 
recognizer-method<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; 
verifier-method<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; token&nbsp;&nbsp; ; &lt;------<BR>&gt; <BR>&gt; 
message-header&nbsp;&nbsp; =&nbsp;&nbsp;&nbsp; 1*(generic-header / 
resource-header / <BR>&gt; extension-header)<BR>&gt; <BR>&gt; extension-header = 
field-name ":" [ field-value ]<BR>&gt; <BR>&gt; If appropriate, perhaps these 
issues can be discussed at the start of the <BR>&gt; EBNF section (15).<BR>&gt; 
<BR>&gt; <BR>&gt; HTH,<BR>&gt; <BR>&gt; Pete.<BR>&gt; --<BR>&gt; 
=============================================<BR>&gt; Pete Cordell<BR>&gt; 
Tech-Know-Ware Ltd<BR>&gt; for XML to C++ data binding visit<BR>&gt; </FONT><A 
href="http://www.tech-know-ware.com/lmx"><FONT face=Arial 
size=2>http://www.tech-know-ware.com/lmx</FONT></A><BR><FONT face=Arial 
size=2>&gt; (or </FONT><A href="http://www.xml2cpp.com"><FONT face=Arial 
size=2>http://www.xml2cpp.com</FONT></A><FONT face=Arial size=2>)<BR>&gt; 
=============================================<BR>&gt; <BR>&gt; ----- Original 
Message ----- <BR>&gt; From: "sreekanth" &lt;</FONT><A 
href="mailto:sreekanthm@huawei.com"><FONT face=Arial 
size=2>sreekanthm@huawei.com</FONT></A><FONT face=Arial size=2>&gt;<BR>&gt; To: 
"Saravanan Shanmugham (sarvi)" &lt;</FONT><A href="mailto:sarvi@cisco.com"><FONT 
face=Arial size=2>sarvi@cisco.com</FONT></A><FONT face=Arial size=2>&gt;; "Dan 
Burnett" <BR>&gt; &lt;</FONT><A href="mailto:dan_burnett2000@yahoo.com"><FONT 
face=Arial size=2>dan_burnett2000@yahoo.com</FONT></A><FONT face=Arial 
size=2>&gt;<BR>&gt; Cc: &lt;</FONT><A href="mailto:speechsc@ietf.org"><FONT 
face=Arial size=2>speechsc@ietf.org</FONT></A><FONT face=Arial 
size=2>&gt;<BR>&gt; Sent: Wednesday, November 22, 2006 6:56 AM<BR>&gt; Subject: 
[Speechsc] Query in the general message header ABNF<BR>&gt; <BR>&gt; 
<BR>&gt;&gt; This is a quote from the section 6.2 of 
mrcpv2-draft-11<BR>&gt;&gt;<BR>&gt;&gt; message-header = field-name ":" [ 
field-value ]<BR>&gt;&gt;<BR>&gt;&gt; field-name = token<BR>&gt;&gt;<BR>&gt;&gt; 
field-value = *LWS field-content *( CRLF 1*LWS 
field-content)<BR>&gt;&gt;<BR>&gt;&gt; field-content = &lt;the OCTETs making up 
the field-value<BR>&gt;&gt;<BR>&gt;&gt; and consisting of either *TEXT or 
combinations<BR>&gt;&gt;<BR>&gt;&gt; of token, separators, and 
quoted-string&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; As per the 
above rule if the header if of list type,&nbsp; is it&nbsp; mandatory 
<BR>&gt;&gt; that the multiple header values MUST have atleast one 
LWS???<BR>&gt;&gt;<BR>&gt;&gt; In the header ABNF already seperator for the 
multiple values is defined.. <BR>&gt;&gt; So Why do we need this 
LWS??<BR>&gt;&gt;<BR>&gt;&gt; Pls clarify on this.<BR>&gt;&gt;<BR>&gt;&gt; 
Sreekanth<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt; 
<BR>&gt; <BR>&gt; 
--------------------------------------------------------------------------------<BR>&gt; 
<BR>&gt; <BR>&gt;&gt; 
_______________________________________________<BR>&gt;&gt; Speechsc mailing 
list<BR>&gt;&gt; </FONT><A href="mailto:Speechsc@ietf.org"><FONT face=Arial 
size=2>Speechsc@ietf.org</FONT></A><BR><FONT face=Arial size=2>&gt;&gt; 
</FONT><A href="https://www1.ietf.org/mailman/listinfo/speechsc"><FONT 
face=Arial 
size=2>https://www1.ietf.org/mailman/listinfo/speechsc</FONT></A><BR><FONT 
face=Arial size=2>&gt;&gt; <BR>&gt; <BR>&gt; <BR>&gt;</FONT></BODY></HTML>

--Boundary_(ID_9RCmFMNGOxeeR7rPpmf+kA)--


--===============0060020843==
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

--===============0060020843==--




From speechsc-bounces@ietf.org Wed Dec 06 01:28:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrqFv-0004QD-2e; Wed, 06 Dec 2006 01:27:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrqFu-0004Q8-9E
	for speechsc@ietf.org; Wed, 06 Dec 2006 01:27:46 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrqFp-0002hs-UV
	for speechsc@ietf.org; Wed, 06 Dec 2006 01:27:46 -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 <0J9U00M8Z9OTHH@szxga01-in.huawei.com> for
	speechsc@ietf.org; Wed, 06 Dec 2006 14:22:05 +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 <0J9U001B19OS7H@szxga01-in.huawei.com> for
	speechsc@ietf.org; Wed, 06 Dec 2006 14:22:05 +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 <0J9U00FCP9OP7T@szxml03-in.huawei.com> for
	speechsc@ietf.org; Wed, 06 Dec 2006 14:22:04 +0800 (CST)
Date: Wed, 06 Dec 2006 11:52:01 +0530
From: sreekanth <sreekanthm@huawei.com>
Subject: Re: [Speechsc] (no subject)
To: "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>,
	Dan Burnett <dan_burnett2000@yahoo.com>
Message-id: <002c01c718fe$d802cb10$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: <C6A1C20DB743364EB446E923B2229FEF02AEFF71@xmb-sjc-229.amer.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 926f893f9bbbfa169f045f85f0cdb955
Cc: speechsc@ietf.org
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sreekanth <sreekanthm@huawei.com>
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="===============1180751839=="
Errors-To: speechsc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1180751839==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_53xXAikq9MlUp3kkhv86MA)"

This is a multi-part message in MIME format.

--Boundary_(ID_53xXAikq9MlUp3kkhv86MA)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hi sarvi,

1) In section, 11.11. VERIFY-FROM-BUFFER of the draft says...

For VERIFY-FROM-BUFFER method, the server MAY optionally return an "IN-PROGRESS" response before the "VERIFICATION-COMPLETE" event.

As per the above statement , Can MRCP server send VERIFICATION-COMPLETE without sending any 2xx response ?..

MRCP Client                            MRCP server

          -------------VERIFY-FROM-BUFFER------------------------->

          <-------VERIFICATION-COMPLETE-----------------


2) Can server send  INTERPRETATION-COMPLETE without any 2xx response for INTERPRET method ??

Pls clarify on this..

Thanking you in Advance.

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!


  ----- 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_53xXAikq9MlUp3kkhv86MA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2995" name=GENERATOR>
<STYLE></STYLE>
</HEAD>

<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi sarvi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>1) In section, <FONT color=#000032 size=2>11.11. 
VERIFY-FROM-BUFFER of the draft says...</FONT></FONT></DIV>
<DIV><FONT face=Arial color=#000032 size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>
<P><STRONG>For VERIFY-FROM-BUFFER method, the server MAY optionally return an 
"IN-PROGRESS" response before the "VERIFICATION-COMPLETE" event.</STRONG></P>
<P>As per the above statement , Can MRCP server send VERIFICATION-COMPLETE 
without sending any 2xx response ?..</P><FONT face=Arial>
<DIV><FONT face=Arial size=2>MRCP 
Client&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MRCP 
server</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial 
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-------------<STRONG>VERIFY-FROM-BUFFER</STRONG>-------------------------&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial 
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;-------<STRONG>VERIFICATION-COMPLETE</STRONG>-----------------</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV></FONT><FONT face="Times New Roman">2) Can server send&nbsp; <FONT 
color=#000032 size=2>INTERPRETATION-COMPLETE without any 2xx response for <FONT 
color=#000000>INTERPRET method </FONT>??</FONT></FONT></DIV>
<DIV><FONT color=#000032></FONT>&nbsp;</DIV>
<DIV><FONT color=#000032>Pls clarify on this..</FONT></DIV>
<DIV><FONT color=#000032></FONT>&nbsp;</DIV>
<DIV><FONT color=#000032>Thanking you in Advance.</FONT></DIV>
<DIV><FONT color=#000032></FONT>&nbsp;</DIV>
<DIV><FONT color=#000032>Sreekanth</FONT></DIV>
<DIV><FONT color=#000032></FONT>&nbsp;</DIV></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV>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!</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=sarvi@cisco.com href="mailto:sarvi@cisco.com">Saravanan Shanmugham 
  (sarvi)</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=sreekanthm@huawei.com 
  href="mailto:sreekanthm@huawei.com">sreekanth</A> ; <A 
  title=dan_burnett2000@yahoo.com href="mailto:dan_burnett2000@yahoo.com">Dan 
  Burnett</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=speechsc@ietf.org 
  href="mailto:speechsc@ietf.org">speechsc@ietf.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Saturday, October 28, 2006 6:40 
  AM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Speechsc] (no 
subject)</DIV>
  <DIV><BR></DIV>
  <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN 
  class=353500801-28102006>No. </SPAN></FONT></DIV>
  <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN 
  class=353500801-28102006>SPEAK-COMPLETE makes sense only if there was a 200 
  response meaning that the request was initiated 
  successfully.</SPAN></FONT></DIV>
  <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN 
  class=353500801-28102006>i.e. SPEAK-COMPLETE makes sense if the resource was 
  in a IN-PROGRESS/PENDING state.</SPAN></FONT></DIV>
  <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN 
  class=353500801-28102006></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN 
  class=353500801-28102006>Sarvi</SPAN></FONT></DIV><BR>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
    <HR tabIndex=-1>
    <FONT face=Tahoma size=2><B>From:</B> sreekanth 
    [mailto:sreekanthm@huawei.com] <BR><B>Sent:</B> Thursday, October 26, 2006 
    11:04 PM<BR><B>To:</B> Dan Burnett; Saravanan Shanmugham 
    (sarvi)<BR><B>Cc:</B> <A 
    href="mailto:speechsc@ietf.org">speechsc@ietf.org</A><BR><B>Subject:</B> 
    [Speechsc] (no subject)<BR><B>Importance:</B> High<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>Can the MRCP server send SPEAK-COMPLETE without 
    sending 200 responses (IN-PROGRESS or PENDING state)...</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>MRCP 
    Client&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MRCP 
    server</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    -------------SPEAK-------------------------&gt;</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &lt;-------SPEAK-COMPLETE-----------</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>Can this happen in any error sceneriao(any 
    server side failure)????<BR></FONT></DIV>
    <DIV><FONT face=Arial size=2>Pls clarify on this....</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
    <DIV><FONT face=Arial size=2>Sreekanth</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    </FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_53xXAikq9MlUp3kkhv86MA)--


--===============1180751839==
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

--===============1180751839==--




From speechsc-bounces@ietf.org Wed Dec 06 04:29:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Grt5K-0001ru-AN; Wed, 06 Dec 2006 04:29:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Grt5J-0001ro-Q1
	for speechsc@ietf.org; Wed, 06 Dec 2006 04:29:01 -0500
Received: from smtp1.wanadoo.co.uk ([193.252.22.158] helo=smtp1.freeserve.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Grt5G-0001Tj-4a
	for speechsc@ietf.org; Wed, 06 Dec 2006 04:29:01 -0500
Received: from me-wanadoo.net (localhost [127.0.0.1])
	by mwinf3013.me.freeserve.com (SMTP Server) with ESMTP id 7C433B400089; 
	Wed,  6 Dec 2006 10:28:55 +0100 (CET)
Received: from Codalogic (user-5445210e.lns4-c11.dsl.pol.co.uk [84.69.33.14])
	by mwinf3013.me.freeserve.com (SMTP Server) with SMTP id
	1A4B4B400084; Wed,  6 Dec 2006 10:28:55 +0100 (CET)
X-ME-UUID: 20061206092855107.1A4B4B400084@mwinf3013.me.freeserve.com
Message-ID: <007401c71918$f1bea0a0$1c00a8c0@Codalogic>
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "sreekanth" <sreekanthm@huawei.com>
References: <C6A1C20DB743364EB446E923B2229FEF02C09BE9@xmb-sjc-229.amer.cisco.com>
	<002601c70e03$648cfa80$a504120a@china.huawei.com>
	<00a601c70ef2$de567130$1c00a8c0@Codalogic>
	<000a01c71785$f29579c0$a504120a@china.huawei.com>
Subject: Re: [Speechsc] Query in the general message header ABNF
Date: Wed, 6 Dec 2006 09:28:22 -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: 0.1 (/)
X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae
Cc: speechsc@ietf.org
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>
Errors-To: speechsc-bounces@ietf.org

It's *LMS and 1*LWS.  Therefore, the following is also legal (although not 
recommended):

header:                                      // CRLF and WSP CRLF -> LWS
                                                  // WSP CRLF -> LWS
                                                  // WSP CRLF -> LWS
  foo                                            // WSP CRLF -> LWS
                                                  // WSP CRLF -> LWS
                                                  // WSP CRLF -> LWS
  bar                                            // WSP CRLF -> LWS
  =                                               // WSP CRLF -> LWS
  18


I will have to let others address the other issues you raised.

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" <sreekanthm@huawei.com>
To: "Pete Cordell" <pete@tech-know-ware.com>
Cc: <speechsc@ietf.org>; "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>; 
"Dan Burnett" <dan_burnett2000@yahoo.com>
Sent: Monday, December 04, 2006 9:24 AM
Subject: Re: [Speechsc] Query in the general message header ABNF


> Hi Pete,
>
> Thanks for replying..
>
> 1) I still have one more query on the section 6.2 defning the header 
> grammar..
>
> 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 field value syntax, we can msg hdrs like
>
> header:                                      // CRLF and WSP CRLF -> LWS
>                                                  // WSP CRLF -> LWS
> foo                                            // WSP CRLF -> LWS
>  bar                                            // WSP CRLF -> LWS
>  =                                               // WSP CRLF -> LWS
>  18CRLF
>
> Since the LWS([*WSP CRLF] 1*WSP) can again have WSP followed by CRLF.. 
> There can be 2 lines after the header: in the above example..
>
>
> 2) The draft does not explain the ABNF grammar for Extension header.
>
> 3) The ABNF grammar for voiceprint-identifier has some ambiguity .
>
>    "Voiceprint-Identifier" ":" 1*VCHAR "." 1*VCHAR *[";" 1*VCHAR "." 
> 1*VCHAR] CRLF
>
>    The seperator '.'  is again part of VCHAR.. So there is a overlap 
> between the Header Value and the seperator..
>
>
>
> Pls clarify on this.
>
>
> 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!
>
>
> ----- Original Message ----- 
> From: "Pete Cordell" <pete@tech-know-ware.com>
> To: "sreekanth" <sreekanthm@huawei.com>
> Cc: <speechsc@ietf.org>
> Sent: Thursday, November 23, 2006 5:01 PM
> Subject: Re: [Speechsc] Query in the general message header ABNF
>
>
>> 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" <sreekanthm@huawei.com>
>> To: "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>; "Dan Burnett"
>> <dan_burnett2000@yahoo.com>
>> Cc: <speechsc@ietf.org>
>> 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 = <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
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>> _______________________________________________
>>> 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



From speechsc-bounces@ietf.org Sun Dec 17 00:51:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gvovi-0000QG-4E; Sun, 17 Dec 2006 00:51:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gvovh-0000QB-1B
	for speechsc@ietf.org; Sun, 17 Dec 2006 00:51:21 -0500
Received: from web31307.mail.mud.yahoo.com ([68.142.198.102])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gvove-0006kk-O9
	for speechsc@ietf.org; Sun, 17 Dec 2006 00:51:21 -0500
Received: (qmail 57350 invoked by uid 60001); 17 Dec 2006 05:51:03 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=ooDU8kOCtMmJPr9uSyfaaRzmMT1JF/II0Hd7r8yMr5d/0jWl0geXkYNwhXlOzkrZE06RiswNx50ddpCpf+fUwXxRiazYfhjM4waw9WbF0ZqszBquy22SUkXqECwXgQ0zVhObBB1QlknbFFY6WTiE7y291VYsNgAbdwZksigKhq4=;
X-YMail-OSG: vYaRWGMVM1kdF5zPTSXsS8zWvvA9eqeobIpmM.SLzUTj1sxuJTunXMKYpN.PvypVw3GrQ2nRKA_WyVybLmttnE2YEc5rk9.iSCRc6h1aKmcPe13Af.oyQPHuAgYI12PzgE9uwEytlrfGr2GLUEsIAIMX7i0wDrtXbwjQ59Y251vKUYn2gbjedmpz
Received: from [82.99.229.121] by web31307.mail.mud.yahoo.com via HTTP;
	Sat, 16 Dec 2006 21:51:02 PST
Date: Sat, 16 Dec 2006 21:51:02 -0800 (PST)
From: jafar ahmadian <jafar_ahmadian@yahoo.com>
To: speechsc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <7426.54145.qm@web31307.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: jafar_ahmadian@yahoo.com
Subject: [Speechsc] Media Resource Management
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>
Errors-To: speechsc-bounces@ietf.org

Hi 
  I see in "Figure 1: Architectural Diagram" of
 "draft-ietf-speechsc-mrcpv2-11.txt" 
 this Phrase "Media Resource Management ".
  How  "Media Resource Management" is Working?
  Do you have any Information or papers or links for
it?
Thanks .

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

_______________________________________________
Speechsc mailing list
Speechsc@ietf.org
https://www1.ietf.org/mailman/listinfo/speechsc



From speechsc-bounces@ietf.org Tue Dec 19 16:16:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwmJy-0004Oc-J1; Tue, 19 Dec 2006 16:16:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwmJx-0004OR-8Q
	for speechsc@ietf.org; Tue, 19 Dec 2006 16:16:21 -0500
Received: from [87.198.5.178] (helo=mail.voxpilot.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwmJt-0005en-UV
	for speechsc@ietf.org; Tue, 19 Dec 2006 16:16:21 -0500
Received: by mail.voxpilot.com (Postfix, from userid 552)
	id E0E4E2140FD; Tue, 19 Dec 2006 21:16:10 +0000 (GMT)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on db01ms01
X-Spam-Status: No, score=-3.6 required=5.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	HTML_MESSAGE autolearn=ham version=3.1.0
X-Spam-Level: 
Received: from daburkewxp (dsl-34-34.dsl.netsource.ie [213.79.34.34])
	by mail.voxpilot.com (Postfix) with ESMTP id 56B2C2140FA
	for <speechsc@ietf.org>; Tue, 19 Dec 2006 21:16:04 +0000 (GMT)
Message-ID: <060f01c723b2$db792910$6700000a@db01.voxpilot.com>
From: "Dave Burke" <david.burke@voxpilot.com>
To: <speechsc@ietf.org>
Subject: [speechsc] Minor editorial - don't use discard port in OPTIONS
	response
Date: Tue, 19 Dec 2006 21:15:48 -0000
MIME-Version: 1.0
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: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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="===============1153331206=="
Errors-To: speechsc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1153331206==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_060C_01C723B2.DB0B2500"

This is a multi-part message in MIME format.

------=_NextPart_000_060C_01C723B2.DB0B2500
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

In the example in Section 7, the port number for the control channel =
m-line ought to be 0 not 9 (the server port reported should not be =
enabled).

Dave


------=_NextPart_000_060C_01C723B2.DB0B2500
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>In the example in Section 7, the port =
number for=20
the control channel m-line ought to be 0 not 9 (the server port reported =
should=20
not be enabled).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Dave</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_060C_01C723B2.DB0B2500--



--===============1153331206==
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

--===============1153331206==--





From speechsc-bounces@ietf.org Thu Dec 28 23:07:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H091Y-00089W-OD; Thu, 28 Dec 2006 23:07:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H091X-00089R-AI
	for speechsc@ietf.org; Thu, 28 Dec 2006 23:07:15 -0500
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H08r4-0000NK-Pq
	for speechsc@ietf.org; Thu, 28 Dec 2006 23:07:15 -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 <0JB000ETGNP2I5@szxga01-in.huawei.com> for
	speechsc@ietf.org; Fri, 29 Dec 2006 11:43:50 +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 <0JB000BOMNOZ55@szxga01-in.huawei.com> for
	speechsc@ietf.org; Fri, 29 Dec 2006 11:43:50 +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 <0JB000MXNNOV1I@szxml03-in.huawei.com> for
	speechsc@ietf.org; Fri, 29 Dec 2006 11:43:47 +0800 (CST)
Date: Fri, 29 Dec 2006 09:13:42 +0530
From: sreekanth <sreekanthm@huawei.com>
Subject: Re: [Speechsc] Query in the general message header ABNF
To: speechsc@ietf.org
Message-id: <003e01c72afb$8a65be30$a504120a@china.huawei.com>
Organization: huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-Priority: 3
X-MSMail-priority: Normal
References: <C6A1C20DB743364EB446E923B2229FEF02C09BE9@xmb-sjc-229.amer.cisco.com>
	<002601c70e03$648cfa80$a504120a@china.huawei.com>
	<00a601c70ef2$de567130$1c00a8c0@Codalogic>
	<000a01c71785$f29579c0$a504120a@china.huawei.com>
	<007401c71918$f1bea0a0$1c00a8c0@Codalogic>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 539f8b288ab42db633e5c7cf1c34fca1
Cc: David R Oran <oran@cisco.com>,
	"Saravanan Shanmugham \(sarvi\)" <sarvi@cisco.com>
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sreekanth <sreekanthm@huawei.com>
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="===============1238835220=="
Errors-To: speechsc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1238835220==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_KK3PLZ0wmAxLhNJrEtB7yw)"

This is a multi-part message in MIME format.

--Boundary_(ID_KK3PLZ0wmAxLhNJrEtB7yw)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hi ,

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>

We have missed one point in the above grammar for generic headers.There can be an empty line in the field value..

Pls consider the example for the Active-Request-Id-List header...

Active-Request-Id-List: 123, CRLF LWS 125 CRLF

The definition of LWS is  LWS    =    [*WSP CRLF] 1*WSP ; linear whitespace

Now if the LWS again contains CRLF followed by WSP, then it becomes

Active-Request-Id-List: 123, CRLF CRLF WSP 125 CRLF

which as per the ABNF is the beginning of the message body..


I suggest to change the generic grammar to 


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

since any parser implemention MUST be robust enough to receive messages with or without the LWS..

Pls clarify on this..


Regards,
Sreekanth




----- Original Message ----- 
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "sreekanth" <sreekanthm@huawei.com>
Cc: <speechsc@ietf.org>
Sent: Wednesday, December 06, 2006 2:58 PM
Subject: Re: [Speechsc] Query in the general message header ABNF


> It's *LMS and 1*LWS.  Therefore, the following is also legal (although not 
> recommended):
> 
> header:                                      // CRLF and WSP CRLF -> LWS
>                                                  // WSP CRLF -> LWS
>                                                  // WSP CRLF -> LWS
>  foo                                            // WSP CRLF -> LWS
>                                                  // WSP CRLF -> LWS
>                                                  // WSP CRLF -> LWS
>  bar                                            // WSP CRLF -> LWS
>  =                                               // WSP CRLF -> LWS
>  18
> 
> 
> I will have to let others address the other issues you raised.
> 
> 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" <sreekanthm@huawei.com>
> To: "Pete Cordell" <pete@tech-know-ware.com>
> Cc: <speechsc@ietf.org>; "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>; 
> "Dan Burnett" <dan_burnett2000@yahoo.com>
> Sent: Monday, December 04, 2006 9:24 AM
> Subject: Re: [Speechsc] Query in the general message header ABNF
> 
> 
>> Hi Pete,
>>
>> Thanks for replying..
>>
>> 1) I still have one more query on the section 6.2 defning the header 
>> grammar..
>>
>> 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 field value syntax, we can msg hdrs like
>>
>> header:                                      // CRLF and WSP CRLF -> LWS
>>                                                  // WSP CRLF -> LWS
>> foo                                            // WSP CRLF -> LWS
>>  bar                                            // WSP CRLF -> LWS
>>  =                                               // WSP CRLF -> LWS
>>  18CRLF
>>
>> Since the LWS([*WSP CRLF] 1*WSP) can again have WSP followed by CRLF.. 
>> There can be 2 lines after the header: in the above example..
>>
>>
>> 2) The draft does not explain the ABNF grammar for Extension header.
>>
>> 3) The ABNF grammar for voiceprint-identifier has some ambiguity .
>>
>>    "Voiceprint-Identifier" ":" 1*VCHAR "." 1*VCHAR *[";" 1*VCHAR "." 
>> 1*VCHAR] CRLF
>>
>>    The seperator '.'  is again part of VCHAR.. So there is a overlap 
>> between the Header Value and the seperator..
>>
>>
>>
>> Pls clarify on this.
>>
>>
>> Regards,
>> Sreekanth
>>

>>
>>
>> ----- Original Message ----- 
>> From: "Pete Cordell" <pete@tech-know-ware.com>
>> To: "sreekanth" <sreekanthm@huawei.com>
>> Cc: <speechsc@ietf.org>
>> Sent: Thursday, November 23, 2006 5:01 PM
>> Subject: Re: [Speechsc] Query in the general message header ABNF
>>
>>
>>> 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" <sreekanthm@huawei.com>
>>> To: "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>; "Dan Burnett"
>>> <dan_burnett2000@yahoo.com>
>>> Cc: <speechsc@ietf.org>
>>> 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 = <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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>> _______________________________________________
>>>> Speechsc mailing list
>>>> Speechsc@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/speechsc
>>>>
>>>
>>>
>>>
>> 
> 
> 
>

--Boundary_(ID_KK3PLZ0wmAxLhNJrEtB7yw)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=Arial size=2>Hi ,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>This is a quote from the section 6.2 of 
mrcpv2-draft-11<BR><BR>&nbsp;message-header = field-name ":" [ field-value 
]<BR><BR>&nbsp;field-name = token<BR><BR><STRONG>&nbsp;field-value = *LWS 
field-content *( CRLF 1*LWS field-content)</STRONG><BR><BR>&nbsp;field-content = 
&lt;the OCTETs making up the field-value<BR>&nbsp;and consisting of either *TEXT 
or combinations<BR>&nbsp;of token, separators, and 
quoted-string&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>We have missed one point in the above grammar for 
generic headers.There can be an empty line in the field value..</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Pls consider the example for the 
Active-Request-Id-List header...</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Active-Request-Id-List: 123, <STRONG>CRLF 
LWS</STRONG> 125 CRLF</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>The definition of LWS is&nbsp; 
LWS&nbsp;&nbsp;&nbsp; =&nbsp;&nbsp;&nbsp; [*WSP CRLF] 1*WSP ; linear 
whitespace</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Now if the LWS again contains CRLF followed by WSP, 
then it becomes</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Active-Request-Id-List: 123, <STRONG>CRLF CRLF WSP 
</STRONG>125 CRLF</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>which as per the ABNF is the beginning of the 
message body..</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I suggest to change the generic grammar to 
</FONT></DIV><FONT face=Arial size=2>
<DIV><BR><BR><STRONG>&nbsp;field-value = *LWS field-content *( *LWS 
field-content)</STRONG></DIV>
<DIV><STRONG></STRONG>&nbsp;</DIV>
<DIV>since any parser implemention MUST be robust enough to receive messages 
with or without the LWS..</DIV>
<DIV>&nbsp;</DIV>
<DIV>Pls clarify on this..</DIV>
<DIV><STRONG></STRONG>&nbsp;</DIV>
<DIV></FONT><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV><FONT face=Arial size=2>Sreekanth</DIV>
<DIV><BR></DIV></FONT>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>----- Original Message ----- </FONT>
<DIV><FONT face=Arial size=2>From: "Pete Cordell" &lt;</FONT><A 
href="mailto:pete@tech-know-ware.com"><FONT face=Arial 
size=2>pete@tech-know-ware.com</FONT></A><FONT face=Arial 
size=2>&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>To: "sreekanth" &lt;</FONT><A 
href="mailto:sreekanthm@huawei.com"><FONT face=Arial 
size=2>sreekanthm@huawei.com</FONT></A><FONT face=Arial size=2>&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>Cc: &lt;</FONT><A 
href="mailto:speechsc@ietf.org"><FONT face=Arial 
size=2>speechsc@ietf.org</FONT></A><FONT face=Arial size=2>&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>Sent: Wednesday, December 06, 2006 2:58 
PM</FONT></DIV>
<DIV><FONT face=Arial size=2>Subject: Re: [Speechsc] Query in the general 
message header ABNF</FONT></DIV></DIV>
<DIV><FONT face=Arial><BR><FONT size=2></FONT></FONT></DIV><FONT face=Arial 
size=2>&gt; It's *LMS and 1*LWS.&nbsp; Therefore, the following is also legal 
(although not <BR>&gt; recommended):<BR>&gt; <BR>&gt; 
header:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// CRLF and WSP CRLF -&gt; 
LWS<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; 
LWS<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; LWS<BR>&gt;&nbsp; 
foo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; 
LWS<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; 
LWS<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; LWS<BR>&gt;&nbsp; 
bar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; LWS<BR>&gt;&nbsp; 
=&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; LWS<BR>&gt;&nbsp; 18<BR>&gt; <BR>&gt; <BR>&gt; I will have to 
let others address the other issues you raised.<BR>&gt; <BR>&gt; Pete.<BR>&gt; 
--<BR>&gt; =============================================<BR>&gt; Pete 
Cordell<BR>&gt; Tech-Know-Ware Ltd<BR>&gt; for XML to C++ data binding 
visit<BR>&gt; </FONT><A href="http://www.tech-know-ware.com/lmx"><FONT 
face=Arial size=2>http://www.tech-know-ware.com/lmx</FONT></A><BR><FONT 
face=Arial size=2>&gt; (or </FONT><A href="http://www.xml2cpp.com"><FONT 
face=Arial size=2>http://www.xml2cpp.com</FONT></A><FONT face=Arial 
size=2>)<BR>&gt; =============================================<BR>&gt; <BR>&gt; 
----- Original Message ----- <BR>&gt; From: "sreekanth" &lt;</FONT><A 
href="mailto:sreekanthm@huawei.com"><FONT face=Arial 
size=2>sreekanthm@huawei.com</FONT></A><FONT face=Arial size=2>&gt;<BR>&gt; To: 
"Pete Cordell" &lt;</FONT><A href="mailto:pete@tech-know-ware.com"><FONT 
face=Arial size=2>pete@tech-know-ware.com</FONT></A><FONT face=Arial 
size=2>&gt;<BR>&gt; Cc: &lt;</FONT><A href="mailto:speechsc@ietf.org"><FONT 
face=Arial size=2>speechsc@ietf.org</FONT></A><FONT face=Arial size=2>&gt;; 
"Saravanan Shanmugham (sarvi)" &lt;</FONT><A href="mailto:sarvi@cisco.com"><FONT 
face=Arial size=2>sarvi@cisco.com</FONT></A><FONT face=Arial size=2>&gt;; 
<BR>&gt; "Dan Burnett" &lt;</FONT><A 
href="mailto:dan_burnett2000@yahoo.com"><FONT face=Arial 
size=2>dan_burnett2000@yahoo.com</FONT></A><FONT face=Arial size=2>&gt;<BR>&gt; 
Sent: Monday, December 04, 2006 9:24 AM<BR>&gt; Subject: Re: [Speechsc] Query in 
the general message header ABNF<BR>&gt; <BR>&gt; <BR>&gt;&gt; Hi 
Pete,<BR>&gt;&gt;<BR>&gt;&gt; Thanks for replying..<BR>&gt;&gt;<BR>&gt;&gt; 1) I 
still have one more query on the section 6.2 defning the header <BR>&gt;&gt; 
grammar..<BR>&gt;&gt;<BR>&gt;&gt; message-header = field-name ":" [ field-value 
]<BR>&gt;&gt; field-name = token<BR>&gt;&gt; field-value = *LWS field-content *( 
CRLF 1*LWS field-content)<BR>&gt;&gt; field-content = &lt;the OCTETs making up 
the field-value<BR>&gt;&gt;&nbsp; and consisting of either *TEXT or combinations 
of token, separators, and <BR>&gt;&gt; quoted-string&gt;<BR>&gt;&gt;<BR>&gt;&gt; 
As per the field value syntax, we can msg hdrs like<BR>&gt;&gt;<BR>&gt;&gt; 
header:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// CRLF and WSP CRLF -&gt; 
LWS<BR>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; LWS<BR>&gt;&gt; 
foo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; LWS<BR>&gt;&gt;&nbsp; 
bar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; LWS<BR>&gt;&gt;&nbsp; 
=&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
// WSP CRLF -&gt; LWS<BR>&gt;&gt;&nbsp; 18CRLF<BR>&gt;&gt;<BR>&gt;&gt; Since the 
LWS([*WSP CRLF] 1*WSP) can again have WSP followed by CRLF.. <BR>&gt;&gt; There 
can be 2 lines after the header: in the above 
example..<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; 2) The draft does not explain the 
ABNF grammar for Extension header.<BR>&gt;&gt;<BR>&gt;&gt; 3) The ABNF grammar 
for voiceprint-identifier has some ambiguity 
.<BR>&gt;&gt;<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; "Voiceprint-Identifier" ":" 1*VCHAR 
"." 1*VCHAR *[";" 1*VCHAR "." <BR>&gt;&gt; 1*VCHAR] 
CRLF<BR>&gt;&gt;<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; The seperator '.'&nbsp; is again 
part of VCHAR.. So there is a overlap <BR>&gt;&gt; between the Header Value and 
the seperator..<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; Pls clarify on 
this.<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; Regards,<BR>&gt;&gt; 
Sreekanth<BR>&gt;&gt;<BR><BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; ----- Original 
Message ----- <BR>&gt;&gt; From: "Pete Cordell" &lt;</FONT><A 
href="mailto:pete@tech-know-ware.com"><FONT face=Arial 
size=2>pete@tech-know-ware.com</FONT></A><FONT face=Arial 
size=2>&gt;<BR>&gt;&gt; To: "sreekanth" &lt;</FONT><A 
href="mailto:sreekanthm@huawei.com"><FONT face=Arial 
size=2>sreekanthm@huawei.com</FONT></A><FONT face=Arial size=2>&gt;<BR>&gt;&gt; 
Cc: &lt;</FONT><A href="mailto:speechsc@ietf.org"><FONT face=Arial 
size=2>speechsc@ietf.org</FONT></A><FONT face=Arial size=2>&gt;<BR>&gt;&gt; 
Sent: Thursday, November 23, 2006 5:01 PM<BR>&gt;&gt; Subject: Re: [Speechsc] 
Query in the general message header ABNF<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;&gt; 
Hi Sreekanth,<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; This is the general format of all 
headers, and the concept is consistent<BR>&gt;&gt;&gt; across many protocols 
including SMTP, HTTP and SIP.&nbsp; This general rule<BR>&gt;&gt;&gt; allows you 
to readily find the beginning of headers without having to do<BR>&gt;&gt;&gt; 
detailed parsing of each header (e.g. just look for non-white space after 
<BR>&gt;&gt;&gt; CR<BR>&gt;&gt;&gt; LF).&nbsp; It also allows you to skip over, 
possibly ignorable, headers that <BR>&gt;&gt;&gt; may<BR>&gt;&gt;&gt; not be 
defined yet.<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; BTW - this isn't just for list type 
headers.&nbsp; It can be used for any <BR>&gt;&gt;&gt; header<BR>&gt;&gt;&gt; 
that benefits from being spread across multiple lines. 
e.g.:<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; MyHeader: 
foo<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; bar<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; 
do<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; da<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; 
=<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; 
18<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; To the doc 
authors:<BR>&gt;&gt;&gt; --------------------<BR>&gt;&gt;&gt; I note that 
section 6.2 says: "The value MAY be preceded by any amount of<BR>&gt;&gt;&gt; 
LWS, though a single SP is preferred."&nbsp; However, most of the examples 
<BR>&gt;&gt;&gt; don't<BR>&gt;&gt;&gt; include a space.&nbsp; Maybe no space is 
preferred for MRCP?<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; Also, I can't find anywhere 
that says whether the EBNF grammar is <BR>&gt;&gt;&gt; explicit<BR>&gt;&gt;&gt; 
about where white space can be included or not.&nbsp; Some rules suggest that 
<BR>&gt;&gt;&gt; it<BR>&gt;&gt;&gt; is and some rules imply that it is not (i.e. 
no mention of optional WS).<BR>&gt;&gt;&gt; Sorry if this has been raised 
before.<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; And, just in case it's not been raised 
before, should the EBNF for the<BR>&gt;&gt;&gt; method name and message-header 
be made extensible? e.g. something like:<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; 
method-name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =&nbsp;&nbsp;&nbsp; 
generic-method<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; 
synthesizer-method<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; 
recorder-method<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; 
recognizer-method<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; 
verifier-method<BR>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
/&nbsp;&nbsp;&nbsp; token&nbsp;&nbsp; ; 
&lt;------<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; message-header&nbsp;&nbsp; 
=&nbsp;&nbsp;&nbsp; 1*(generic-header / resource-header /<BR>&gt;&gt;&gt; 
extension-header)<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; extension-header = field-name 
":" [ field-value ]<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; If appropriate, perhaps 
these issues can be discussed at the start of the<BR>&gt;&gt;&gt; EBNF section 
(15).<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; 
HTH,<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; Pete.<BR>&gt;&gt;&gt; --<BR>&gt;&gt;&gt; 
=============================================<BR>&gt;&gt;&gt; Pete 
Cordell<BR>&gt;&gt;&gt; Tech-Know-Ware Ltd<BR>&gt;&gt;&gt; for XML to C++ data 
binding visit<BR>&gt;&gt;&gt; </FONT><A 
href="http://www.tech-know-ware.com/lmx"><FONT face=Arial 
size=2>http://www.tech-know-ware.com/lmx</FONT></A><BR><FONT face=Arial 
size=2>&gt;&gt;&gt; (or </FONT><A href="http://www.xml2cpp.com"><FONT face=Arial 
size=2>http://www.xml2cpp.com</FONT></A><FONT face=Arial 
size=2>)<BR>&gt;&gt;&gt; 
=============================================<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; 
----- Original Message ----- <BR>&gt;&gt;&gt; From: "sreekanth" &lt;</FONT><A 
href="mailto:sreekanthm@huawei.com"><FONT face=Arial 
size=2>sreekanthm@huawei.com</FONT></A><FONT face=Arial 
size=2>&gt;<BR>&gt;&gt;&gt; To: "Saravanan Shanmugham (sarvi)" &lt;</FONT><A 
href="mailto:sarvi@cisco.com"><FONT face=Arial 
size=2>sarvi@cisco.com</FONT></A><FONT face=Arial size=2>&gt;; "Dan 
Burnett"<BR>&gt;&gt;&gt; &lt;</FONT><A 
href="mailto:dan_burnett2000@yahoo.com"><FONT face=Arial 
size=2>dan_burnett2000@yahoo.com</FONT></A><FONT face=Arial 
size=2>&gt;<BR>&gt;&gt;&gt; Cc: &lt;</FONT><A 
href="mailto:speechsc@ietf.org"><FONT face=Arial 
size=2>speechsc@ietf.org</FONT></A><FONT face=Arial size=2>&gt;<BR>&gt;&gt;&gt; 
Sent: Wednesday, November 22, 2006 6:56 AM<BR>&gt;&gt;&gt; Subject: [Speechsc] 
Query in the general message header 
ABNF<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; This is a quote from 
the section 6.2 of mrcpv2-draft-11<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; 
message-header = field-name ":" [ field-value 
]<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; field-name = 
token<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; field-value = *LWS field-content 
*( CRLF 1*LWS field-content)<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; 
field-content = &lt;the OCTETs making up the 
field-value<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; and consisting of either 
*TEXT or combinations<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; of token, 
separators, and 
quoted-string&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; 
As per the above rule if the header if of list type,&nbsp; is it&nbsp; 
mandatory<BR>&gt;&gt;&gt;&gt; that the multiple header values MUST have atleast 
one LWS???<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; In the header ABNF already 
seperator for the multiple values is <BR>&gt;&gt;&gt;&gt; 
defined..<BR>&gt;&gt;&gt;&gt; So Why do we need this 
LWS??<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; Pls clarify on 
this.<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; 
Sreekanth<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; 
--------------------------------------------------------------------------------<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;&gt; 
_______________________________________________<BR>&gt;&gt;&gt;&gt; Speechsc 
mailing list<BR>&gt;&gt;&gt;&gt; </FONT><A href="mailto:Speechsc@ietf.org"><FONT 
face=Arial size=2>Speechsc@ietf.org</FONT></A><BR><FONT face=Arial 
size=2>&gt;&gt;&gt;&gt; </FONT><A 
href="https://www1.ietf.org/mailman/listinfo/speechsc"><FONT face=Arial 
size=2>https://www1.ietf.org/mailman/listinfo/speechsc</FONT></A><BR><FONT 
face=Arial 
size=2>&gt;&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt;<BR>&gt;&gt; 
<BR>&gt; <BR>&gt; <BR>&gt;</FONT></BODY></HTML>

--Boundary_(ID_KK3PLZ0wmAxLhNJrEtB7yw)--


--===============1238835220==
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

--===============1238835220==--




From speechsc-bounces@ietf.org Sat Dec 30 09:56:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H0fdA-0004SD-Vj; Sat, 30 Dec 2006 09:56:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H0fd9-0004S6-La
	for speechsc@ietf.org; Sat, 30 Dec 2006 09:56:15 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H0fcQ-0001Gz-QL
	for speechsc@ietf.org; Sat, 30 Dec 2006 09:56:15 -0500
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JB300LMSC7FP4@szxga02-in.huawei.com> for
	speechsc@ietf.org; Sat, 30 Dec 2006 22:28:27 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JB300JVTC7EPI@szxga02-in.huawei.com> for
	speechsc@ietf.org; Sat, 30 Dec 2006 22:28:27 +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 <0JB300CNTC7A8A@szxml03-in.huawei.com> for
	speechsc@ietf.org; Sat, 30 Dec 2006 22:28:26 +0800 (CST)
Date: Sat, 30 Dec 2006 19:58:20 +0530
From: sreekanth <sreekanthm@huawei.com>
To: "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>,
	Dan Burnett <dan_burnett2000@yahoo.com>,
	Pete Cordell <pete@tech-know-ware.com>
Message-id: <001201c72c1e$c2061cd0$a504120a@china.huawei.com>
Organization: huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: speechsc@ietf.org
Subject: [Speechsc] Query in the ABNF grammar of Channel-Identifier header
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sreekanth <sreekanthm@huawei.com>
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="===============1616318627=="
Errors-To: speechsc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1616318627==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_mBKChWbBoRDrJ/usGGjTYA)"

This is a multi-part message in MIME format.

--Boundary_(ID_mBKChWbBoRDrJ/usGGjTYA)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hi,

As per the ABNf grammar for generic headers(Section 6.2. Generic Message Headers),

 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>


Do we need to consider LWS on or before the seperator '@' for channel-Identifier header???

channel-identifier = "Channel-Identifier" ":" channel-id CRLF

channel-id = 1*HEXDIG "@" 1*VCHAR



Pls clarify on this..


Regards,
Sreekanth



--Boundary_(ID_mBKChWbBoRDrJ/usGGjTYA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>As per the ABNf grammar for generic headers(Section 
<B><FONT color=#000032 size=2>6.2. Generic Message 
Headers</B></FONT>),</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV>
<DIV><FONT face=Arial size=2>&nbsp;message-header = field-name ":" [ field-value 
]<BR><BR>&nbsp;field-name = token<BR><BR>&nbsp;field-value = *LWS field-content 
*( CRLF 1*LWS field-content)<BR><BR>&nbsp;field-content = &lt;<STRONG>the OCTETs 
making up the field-value<BR>&nbsp;and consisting of either *TEXT or 
combinations<BR>&nbsp;of token, separators, and 
quoted-string&gt;</STRONG></FONT></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2>Do we need to consider LWS on or before the 
seperator <A href="mailto:'@'">'@'</A> for channel-Identifier 
header???</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT size=2>
<P>channel-identifier = "Channel-Identifier" ":" channel-id CRLF</P>
<P>channel-id = 1*HEXDIG "<STRONG><U><FONT face=Arial 
color=#0000ff>@</FONT></U></STRONG>" 1*VCHAR</P></FONT></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Pls clarify on this..</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV><FONT face=Arial size=2>Sreekanth</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial 
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</FONT></DIV></BODY></HTML>

--Boundary_(ID_mBKChWbBoRDrJ/usGGjTYA)--


--===============1616318627==
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

--===============1616318627==--




From speechsc-bounces@ietf.org Sun Dec 31 09:58:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H128W-0008By-C4; Sun, 31 Dec 2006 09:58:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H128T-0008Bp-Ve
	for speechsc@ietf.org; Sun, 31 Dec 2006 09:58:06 -0500
Received: from romy.inter.net.il ([192.114.186.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H128S-0006gH-Cw
	for speechsc@ietf.org; Sun, 31 Dec 2006 09:58:05 -0500
Received: from Elya (natanya.inter.net.il [212.68.144.1] (may be forged))
	by romy.inter.net.il (MOS 3.7.3-GA)
	with ESMTP id GRK08031 (AUTH nsc-57);
	Sun, 31 Dec 2006 16:57:53 +0200 (IST)
From: "Ilya Knyazhansky" <ilyak@nscspeech.com>
To: <speechsc@ietf.org>
Date: Sun, 31 Dec 2006 16:58:41 +0200
Organization: nsc
Message-ID: <001401c72cec$2983b570$ae00a8c0@nsc.co.il>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Subject: [Speechsc] Resource Discovery
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ilyak@nscspeech.com
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="===============1492511885=="
Errors-To: speechsc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1492511885==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0015_01C72CFC.ED0C8570"

This is a multi-part message in MIME format.

------=_NextPart_000_0015_01C72CFC.ED0C8570
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi All
 
As I understand from reading section 7 of the draft, the capabilities
negotiation can be done using SIP OPTIONS method - but the range of
capabilities that can be negotiated this way is rather limited, how for
example the client can learn what languages are supported by the media
processing resource? Or how can the client discover some performance
related characteristics of the resource (i.e. how much simultaneous
calls can be processed by specific resource).
 
In SIP, mechanisms like the one defined in RFC3840 exist that allow more
flexible capabilities negotiation but they are not mentioned in MRCP
spec.
 
Could you please give more practical, real-life examples on how can one
chose MRCP server based on supported recognition language, number of
supported channels etc
 
Thanks,
Ilya
 

------=_NextPart_000_0015_01C72CFC.ED0C8570
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C72CFC.ECA11970">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:ApplyBreakingRules/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi All<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>As I understand from reading section 7 of the draft, =
the capabilities
negotiation can be done using SIP OPTIONS method &#8211; but the range =
of
capabilities that can be negotiated this way is rather limited, how for =
example
the client can learn what languages are supported by the media =
processing
resource? Or how can the client discover some performance related
characteristics of the resource (i.e. how much simultaneous calls can be
processed by specific resource).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In SIP, mechanisms like the one defined in RFC3840 =
exist
that allow more flexible capabilities negotiation but they are not =
mentioned in
MRCP spec.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Could you please give more practical, real-life =
examples on
how <span class=3DGramE>can</span> one chose MRCP server based on =
supported recognition
language, number of supported channels etc<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'>Thanks,</span></font><span
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'>Ilya</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0015_01C72CFC.ED0C8570--



--===============1492511885==
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

--===============1492511885==--