From speechsc-bounces@ietf.org Thu Dec 13 04:36:16 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2kUJ-0000Q5-AR; Thu, 13 Dec 2007 04:36:15 -0500 Received: from speechsc by megatron.ietf.org with local (Exim 4.43) id 1J2kUH-0000Py-1z for speechsc-confirm+ok@megatron.ietf.org; Thu, 13 Dec 2007 04:36:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2kUG-0000Pq-OG for speechsc@ietf.org; Thu, 13 Dec 2007 04:36:12 -0500 Received: from szxga04-in.huawei.com ([61.144.161.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J2kU9-0004MR-Vm for speechsc@ietf.org; Thu, 13 Dec 2007 04:36:12 -0500 Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JSZ003V3EMSIX@szxga04-in.huawei.com> for speechsc@ietf.org; Thu, 13 Dec 2007 17:35:16 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JSZ006ZGEMQ86@szxga04-in.huawei.com> for speechsc@ietf.org; Thu, 13 Dec 2007 17:35:16 +0800 (CST) Received: from htiplr71752 ([10.18.24.82]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JSZ00IF8EMJHZ@szxml03-in.huawei.com> for speechsc@ietf.org; Thu, 13 Dec 2007 17:35:14 +0800 (CST) Date: Thu, 13 Dec 2007 15:05:07 +0530 From: Rajanish To: speechsc@ietf.org Message-id: <001e01c83d6b$737ce8a0$5218120a@china.huawei.com> Organization: Huawei MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Mailer: Microsoft Office Outlook 11 Thread-index: Acg9a3KMK+UyhnqhTW6YuTphbp5Z+g== X-Spam-Score: 0.0 (/) X-Scan-Signature: fca741f5016e6ff607eaed2fd431d10d Subject: [Speechsc] Query on Channel-identifier header in Draft 12 X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rajanish@huawei.com List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1815321334==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============1815321334== Content-type: multipart/alternative; boundary="Boundary_(ID_yqq6MyIIvCpHCgyRK6zVTQ)" This is a multi-part message in MIME format. --Boundary_(ID_yqq6MyIIvCpHCgyRK6zVTQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi, I was trying to understand the ABNF for the channel identifier header, As per the draft-ietf-speechsc-mrcpv2-12 Channel identifier is explained as below 6.2.1. Channel-Identifier All MRCPv2 requests, responses and events MUST contain the Channel- Identifier header. The value is allocated by the server when a control channel is added to the session and communicated to the client by the "a=channel" attribute in the SDP answer from the server. The header value consists of 2 parts separated by the '@' symbol. The first part is an unambiguous string identifying the MRCPv2 session. The second part is a string token which specifies one of the media processing resource types listed in Section 3.1. The unambiguous string (first part) MUST BE unique among the resource instances managed by the server and is common to all resource channels with that server established through a single SIP dialog. channel-identifier = "Channel-Identifier" ":" channel-id CRLF channel-id = 1*VCHAR "@" 1*VCHAR The header value consists of two parts separated by "@" , the First part is a VCHAR and Second part is also a VCHAR. The problem here is '@' also falls in the range of VCHAR set of characters. VCHAR = %x21-7E (33-126) @ = %x40 (64) So we can have any number of "@" characters in the first part as well as in second part. due to this we will not be able to distinguish the first part from second part. Kindly help me regarding this issue. Thanks and Regards Rajanish S D --Boundary_(ID_yqq6MyIIvCpHCgyRK6zVTQ) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT

Hi,

 

I was trying to understand the ABNF for the channel identifier header, As per the draft-ietf-speechsc-mrcpv2-12

Channel identifier is explained as below

 

6.2.1.  Channel-Identifier

 

 

   All MRCPv2 requests, responses and events MUST contain the Channel-

   Identifier header.  The value is allocated by the server when a

   control channel is added to the session and communicated to the

   client by the "a=channel" attribute in the SDP answer from the

   server.  The header value consists of 2 parts separated by the '@'

   symbol.  The first part is an unambiguous string identifying the

   MRCPv2 session.  The second part is a string token which specifies

   one of the media processing resource types listed in Section 3.1.

   The unambiguous string (first part) MUST BE unique among the resource

   instances managed by the server and is common to all resource

   channels with that server established through a single SIP dialog.

 

 

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

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

 

 

The header value consists of two parts separated by “@” , the First part is a VCHAR and Second part is also a VCHAR. The problem here is

‘@’ also falls  in the range of  VCHAR set of characters.

 

VCHAR            =    %x21-7E  (33-126)

@                 =   %x40    (64)

 

So we can have any number of “@” characters in the first part as well as in second part. due to this we will not be able to distinguish the first part from second part.

 

Kindly help me regarding this issue.

 

Thanks and Regards

Rajanish S D

 

 

 

 

 

 

 

 

--Boundary_(ID_yqq6MyIIvCpHCgyRK6zVTQ)-- --===============1815321334== 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 Supplemental web site: <http://www.standardstrack.com/ietf/speechsc> --===============1815321334==-- From speechsc-bounces@ietf.org Mon Dec 17 07:46:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4FMV-00017D-O6; Mon, 17 Dec 2007 07:46:23 -0500 Received: from speechsc by megatron.ietf.org with local (Exim 4.43) id 1J4FMT-00016T-Uf for speechsc-confirm+ok@megatron.ietf.org; Mon, 17 Dec 2007 07:46:21 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4FMT-00016L-IN for speechsc@ietf.org; Mon, 17 Dec 2007 07:46:21 -0500 Received: from web52712.mail.re2.yahoo.com ([206.190.48.235]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1J4FMS-0005Tv-Li for speechsc@ietf.org; Mon, 17 Dec 2007 07:46:21 -0500 Received: (qmail 27304 invoked by uid 60001); 17 Dec 2007 12:46:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=Al75lhO/FAd0ONw7xxQs45ZZ6d6sNE8Eoj0ewG5xN/5glnSkKzruN/yiwcofSt+tUi38FgLF315YLV35vfzb0UlJlNpWsKOuCf/kAqmTbsSuplI4Q4MFg3ED7uU45vv+S4irROrJ+VAdI6o9raNTeH2G361kWohGofwSVHc0RVk=; X-YMail-OSG: Rp0e8EEVM1kI2ZrCAXi4zw_DetVjBTtdSBa6cuYwoSLAL0PxNJqlVc92YrBHRJ.iG5t78JXP_g-- Received: from [195.69.162.137] by web52712.mail.re2.yahoo.com via HTTP; Mon, 17 Dec 2007 04:46:19 PST X-Mailer: YahooMailRC/818.31 YahooMailWebService/0.7.158.1 Date: Mon, 17 Dec 2007 04:46:19 -0800 (PST) From: Arsen Chaloyan Subject: Re: [Speechsc] Query on Channel-identifier header in Draft 12 To: speechsc@ietf.org MIME-Version: 1.0 Message-ID: <727391.26675.qm@web52712.mail.re2.yahoo.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: a743e34ab8eb08259de9a7307caed594 Cc: rajanish@huawei.com X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1697275058==" Errors-To: speechsc-bounces@ietf.org --===============1697275058== Content-Type: multipart/alternative; boundary="0-578650507-1197895579=:26675" --0-578650507-1197895579=:26675 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable In my understanding,=0Aan unambiguous string=0Aidentifying the MRCPv2 sessi= on MUST be ALPHA/DIGIT, but not VCHAR=0A channel-identifier =3D=0A"Chann= el-Identifier" ":" channel-id CRLF=0A =0A=0A =0Achannel-id =3D 1*= ALPHA/DIGIT=0A"@" 1*VCHAR=0A=0A=0A =0A=0Aprobably with some extent to allow= extra symbols like =0A =0A"$"=0A/ "-"=0A/ "_"=0A/ "."=0A/ "+"=0A=0AHope th= is helps,=0AArsen.=0A=0A----- Original Message ----=0AFrom: Rajanish =0ATo: speechsc@ietf.org=0ASent: Thursday, December 13, 2007= 1:35:07 PM=0ASubject: [Speechsc] Query on Channel-identifier header in Dra= ft 12=0A=0A=0A=0A=0A=0A =0A =0A=0A=0A=0A=0A=0A=0A=0A=0AHi,=0A =0A=0A = =0A =0A=0AI was trying to understand the ABNF for the channel=0Aidentifier = header, As per the draft-ietf-speechsc-mrcpv2-12=0A =0A=0AChannel=0Aidentif= ier is explained as below=0A =0A=0A =0A =0A=0A6.2.1. Channel-Identifier= =0A =0A=0A =0A =0A=0A =0A =0A=0A All MRCPv2 requests, responses and eve= nts MUST=0Acontain the Channel-=0A =0A=0A Identifier header. The value i= s allocated by=0Athe server when a=0A =0A=0A control channel is added to = the session and communicated=0Ato the=0A =0A=0A client by the "a=3Dchanne= l" attribute in the=0ASDP answer from the=0A =0A=0A server. The header v= alue consists of 2=0Aparts separated by the '@'=0A =0A=0A symbol. The fi= rst part is an unambiguous string=0Aidentifying the=0A =0A=0A MRCPv2 sess= ion. The second part is a string=0Atoken which specifies=0A =0A=0A one o= f the media processing resource types listed in=0ASection 3.1.=0A =0A=0A = The unambiguous string (first part) MUST BE unique=0Aamong the resource=0A = =0A=0A instances managed by the server and is common to all=0Aresource=0A= =0A=0A channels with that server established through a=0Asingle SIP dial= og.=0A =0A=0A =0A =0A=0A =0A =0A=0A channel-identifier =3D=0A"Channel-= Identifier" ":" channel-id CRLF=0A =0A=0A =0Achannel-id =3D 1*VCH= AR=0A"@" 1*VCHAR=0A =0A=0A =0A =0A=0A =0A =0A=0AThe header value consists = of two parts separated by =93@=94=0A, the First part is a VCHAR and Second = part is also a VCHAR. The problem here=0Ais =0A =0A=0A=91@=92 also falls i= n the range of VCHAR=0Aset of characters.=0A =0A=0A =0A =0A=0AVCHAR = =0A=3D %x21-7E (33-126)=0A =0A=0A@ =3D =0A%x40 = (64)=0A =0A=0A =0A =0A=0ASo we can have any number of=0A=93@=94 character= s in the first part as well as in second part. due to=0Athis we will not be= able to distinguish the first part from second part.=0A =0A=0A =0A =0A=0A= Kindly help me regarding this issue.=0A =0A=0A =0A =0A=0AThanks and Regard= s=0A =0A=0ARajanish S D=0A =0A=0A=0A=0A=0A=0A=0A --0-578650507-1197895579=:26675 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
In my understanding,
an unambiguous string=0Aidentifying t= he MRCPv2 session MUST be ALPHA/DIGIT, but not VCHAR
   channel-identifier  =3D=0A"Channel-I= dentifier" ":" channel-id CRLF

=0A=0A

  =0Achannel-id        = ;  =3D 1*ALPHA/DIGIT=0A"@" 1*VCHAR


=0A=0Aprobably with som= e extent to allow extra symbols like =0A =0A"$"=0A/ "-"=0A/ "_"=0A/ "."=0A/ "= +"

Hope this helps,
Arsen.

----- Original M= essage ----
From: Rajanish <rajanish@huawei.com>
To: speechsc@i= etf.org
Sent: Thursday, December 13, 2007 1:35:07 PM
Subject: [Speech= sc] Query on Channel-identifier header in Draft 12

=0A=0A=0A=0A =0A = =0A=0A=0A=0A=0A
=0A=0A

Hi,

=0A=0A

 

=0A=0A

draft-ietf-speechsc-mrcpv2-12

=0A=0A

Channel=0Aidentifier is explained = as below

=0A=0A

= 6.2.1.  Channel-Identifier

=0A= =0A

 

=0A=0A

 

=0A=0A

   A= ll MRCPv2 requests, responses and events MUST=0Acontain the Channel-=

=0A=0A

   Identifier header.&nb= sp; The value is allocated by=0Athe server when a

=0A=0A<= p class=3D"MsoNormal" style=3D"">   control channel is added to the session = and communicated=0Ato the

=0A=0A

&= nbsp;  client by the "a=3Dchannel" attribute in the=0ASDP answer from = the

=0A=0A

&n= bsp;  server.  The header value cons= ists of 2=0Aparts separated by the '@'

=0A=0A

   symbol.=   The = first part is an unambiguous string=0Aidentifying the

=0A= =0A

   MRCPv2 session.  The second par= t is a string=0Atoken which specifies

=0A=0A

=    one of the media processing resource types listed in= =0ASection 3.1.

=0A=0A

<= font color=3D"black" face=3D"Courier New" size=3D"2">  = The unambiguous string (first part) MUST BE unique=0Aamong the resource

=0A=0A

   instances managed= by the server and is common to all=0Aresource

=0A=0A

   channels with that server established throu= gh a=0Asingle SIP dialog.

=0A=0A

=  

=0A=0A

 =

=0A=0A

   channel-identifier  =3D= =0A"Channel-Identifier" ":" channel-id CRLF

=0A=0A

  =0Achannel-id     &nb= sp;    =3D 1*VCHAR=0A"@" 1*VCHAR

=0A=0A

 

=0A=0A

 

=0A=0A

<= font face=3D"Arial" size=3D"2">The header value consists of two parts separated by =93@=94=0A, th= e First part is a VCHAR and Second part is also a VCHAR. The problem here= =0Ais

=0A=0A

=91@=92 als= o falls  in the range of  VCHAR=0Aset of characters.

=0A=0A

 

=0A=0A

VCHAR         = ;  =0A=3D    %x21-7E  (33-126)<= /p> =0A=0A

@       = ;          =3D  =0A%= x40    (64)

=0A=0A

<= font face=3D"Arial" size=3D"2">  

=0A=0A

= So we can have any number of=0A=93@=94 characters in the first pa= rt as well as in second part. due to=0Athis we will not be able to distingu= ish the first part from second part.

=0A=0A

 

=0A=0A

Kindly help me regarding this issue.<= /font>

=0A=0A

 =

=0A=0A

Thanks and Re= gards

=0A=0A

= Rajanish S D

=0A=0A
=0A=0A
<= /html> --0-578650507-1197895579=:26675-- --===============1697275058== 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 Supplemental web site: <http://www.standardstrack.com/ietf/speechsc> --===============1697275058==-- From speechsc-bounces@ietf.org Mon Dec 17 15:34:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4Mft-0007hW-O0; Mon, 17 Dec 2007 15:34:53 -0500 Received: from speechsc by megatron.ietf.org with local (Exim 4.43) id 1J4Mfs-0007hR-Hb for speechsc-confirm+ok@megatron.ietf.org; Mon, 17 Dec 2007 15:34:52 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4Mfs-0007hI-7Q for speechsc@ietf.org; Mon, 17 Dec 2007 15:34:52 -0500 Received: from rnextsmtp.bea.com ([66.248.192.39] helo=repmmg02.bea.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4Mfr-0008FQ-M6 for speechsc@ietf.org; Mon, 17 Dec 2007 15:34:52 -0500 Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id lBHKYiHP011708; Mon, 17 Dec 2007 12:34:44 -0800 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id lBHKYhi5014840; Mon, 17 Dec 2007 12:34:43 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: RE: [Speechsc] Query on Channel-identifier header in Draft 12 Date: Mon, 17 Dec 2007 12:34:36 -0800 Message-ID: In-Reply-To: <727391.26675.qm@web52712.mail.re2.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speechsc] Query on Channel-identifier header in Draft 12 Thread-Index: AchAqvL7DMqNGGB8SS+D88/VXpWHJQAQNbTg References: <727391.26675.qm@web52712.mail.re2.yahoo.com> From: "Eric Burger" To: "Arsen Chaloyan" , "Dan Burnett" x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Cc: speechsc@ietf.org, rajanish@huawei.com X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org The correct production would be either dot-atom "@" dot-atom or, more likely addr-spec Both productions coming from RFC 2822. ________________________________ From: Arsen Chaloyan [mailto:achaloyan@yahoo.com] Sent: Monday, December 17, 2007 7:46 AM To: speechsc@ietf.org Cc: rajanish@huawei.com Subject: Re: [Speechsc] Query on Channel-identifier header in Draft 12 In my understanding, an unambiguous string identifying the MRCPv2 session MUST be ALPHA/DIGIT, but not VCHAR channel-identifier = "Channel-Identifier" ":" channel-id CRLF channel-id = 1*ALPHA/DIGIT "@" 1*VCHAR probably with some extent to allow extra symbols like "$" / "-" / "_" / "." / "+" Hope this helps, Arsen. ----- Original Message ---- From: Rajanish To: speechsc@ietf.org Sent: Thursday, December 13, 2007 1:35:07 PM Subject: [Speechsc] Query on Channel-identifier header in Draft 12 Hi, I was trying to understand the ABNF for the channel identifier header, As per the draft-ietf-speechsc-mrcpv2-12 Channel identifier is explained as below 6.2.1. Channel-Identifier All MRCPv2 requests, responses and events MUST contain the Channel- Identifier header. The value is allocated by the server when a control channel is added to the session and communicated to the client by the "a=channel" attribute in the SDP answer from the server. The header value consists of 2 parts separated by the '@' symbol. The first part is an unambiguous string identifying the MRCPv2 session. The second part is a string token which specifies one of the media processing resource types listed in Section 3.1. The unambiguous string (first part) MUST BE unique among the resource instances managed by the server and is common to all resource channels with that server established through a single SIP dialog. channel-identifier = "Channel-Identifier" ":" channel-id CRLF channel-id = 1*VCHAR "@" 1*VCHAR The header value consists of two parts separated by "@" , the First part is a VCHAR and Second part is also a VCHAR. The problem here is '@' also falls in the range of VCHAR set of characters. VCHAR = %x21-7E (33-126) @ = %x40 (64) So we can have any number of "@" characters in the first part as well as in second part. due to this we will not be able to distinguish the first part from second part. Kindly help me regarding this issue. Thanks and Regards Rajanish S D Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc Supplemental web site: <http://www.standardstrack.com/ietf/speechsc> From speechsc-bounces@ietf.org Thu Dec 20 17:41:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5U4y-0006tk-RZ; Thu, 20 Dec 2007 17:41:24 -0500 Received: from speechsc by megatron.ietf.org with local (Exim 4.43) id 1J5U4w-0006YY-VC for speechsc-confirm+ok@megatron.ietf.org; Thu, 20 Dec 2007 17:41:23 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5U4w-0006Ry-EP for speechsc@ietf.org; Thu, 20 Dec 2007 17:41:22 -0500 Received: from mmail.voxeo.com ([66.193.54.208] helo=voxeo.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J5U4v-0005Sn-SB for speechsc@ietf.org; Thu, 20 Dec 2007 17:41:22 -0500 Received: from [72.126.192.234] (account dburnett [72.126.192.234] verified) by voxeo.com (CommuniGate Pro SMTP 5.1.12) with ESMTPSA id 25749347; Thu, 20 Dec 2007 22:41:20 +0000 In-Reply-To: References: <727391.26675.qm@web52712.mail.re2.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3CE87D3D-E1FB-4CF4-B95E-8EC4D5728FE4@voxeo.com> Content-Transfer-Encoding: 7bit From: Dan Burnett Subject: Re: [Speechsc] Query on Channel-identifier header in Draft 12 Date: Thu, 20 Dec 2007 17:40:57 -0500 To: Eric Burger X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac Cc: speechsc@ietf.org, rajanish@huawei.com X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org I think Arsen's suggestion is close. The production that matches the examples (along with obvious extensions to the list of resources) is 1*alphanum "@" 1*alphanum. Remember, the goal of the first part is to provide an id, while the second part needs to be a resource type. -- dan On Dec 17, 2007, at 3:34 PM, Eric Burger wrote: > The correct production would be either > dot-atom "@" dot-atom > or, more likely > addr-spec > > Both productions coming from RFC 2822. > > ________________________________ > > From: Arsen Chaloyan [mailto:achaloyan@yahoo.com] > Sent: Monday, December 17, 2007 7:46 AM > To: speechsc@ietf.org > Cc: rajanish@huawei.com > Subject: Re: [Speechsc] Query on Channel-identifier header in Draft 12 > > > In my understanding, > an unambiguous string identifying the MRCPv2 session MUST be > ALPHA/DIGIT, but not VCHAR > > > channel-identifier = "Channel-Identifier" ":" channel-id CRLF > > channel-id = 1*ALPHA/DIGIT "@" 1*VCHAR > > > > > probably with some extent to allow extra symbols like "$" / "-" / > "_" / > "." / "+" > > Hope this helps, > Arsen. > > > ----- Original Message ---- > From: Rajanish > To: speechsc@ietf.org > Sent: Thursday, December 13, 2007 1:35:07 PM > Subject: [Speechsc] Query on Channel-identifier header in Draft 12 > > > > Hi, > > > > I was trying to understand the ABNF for the channel identifier header, > As per the draft-ietf-speechsc-mrcpv2-12 > > Channel identifier is explained as below > > > > 6.2.1. Channel-Identifier > > > > > > All MRCPv2 requests, responses and events MUST contain the Channel- > > Identifier header. The value is allocated by the server when a > > control channel is added to the session and communicated to the > > client by the "a=channel" attribute in the SDP answer from the > > server. The header value consists of 2 parts separated by the '@' > > symbol. The first part is an unambiguous string identifying the > > MRCPv2 session. The second part is a string token which specifies > > one of the media processing resource types listed in Section 3.1. > > The unambiguous string (first part) MUST BE unique among the > resource > > instances managed by the server and is common to all resource > > channels with that server established through a single SIP dialog. > > > > > > channel-identifier = "Channel-Identifier" ":" channel-id CRLF > > channel-id = 1*VCHAR "@" 1*VCHAR > > > > > > The header value consists of two parts separated by "@" , the First > part > is a VCHAR and Second part is also a VCHAR. The problem here is > > '@' also falls in the range of VCHAR set of characters. > > > > VCHAR = %x21-7E (33-126) > > @ = %x40 (64) > > > > So we can have any number of "@" characters in the first part as > well as > in second part. due to this we will not be able to distinguish the > first > part from second part. > > > > Kindly help me regarding this issue. > > > > Thanks and Regards > > Rajanish S D > > > Notice: This email message, together with any attachments, may > contain information of BEA Systems, Inc., its subsidiaries > and affiliated entities, that may be confidential, proprietary, > copyrighted and/or legally privileged, and is intended solely for > the use of the individual or entity named in this message. If you > are not the intended recipient, and have received this message in > error, please immediately return this by email and then delete it. _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc Supplemental web site: <http://www.standardstrack.com/ietf/speechsc> From speechsc-bounces@ietf.org Thu Dec 20 17:48:10 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5UBW-0004go-3U; Thu, 20 Dec 2007 17:48:10 -0500 Received: from speechsc by megatron.ietf.org with local (Exim 4.43) id 1J5UBV-0004YP-2T for speechsc-confirm+ok@megatron.ietf.org; Thu, 20 Dec 2007 17:48:09 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5UBU-0004Uh-MD for speechsc@ietf.org; Thu, 20 Dec 2007 17:48:08 -0500 Received: from rnextsmtp.bea.com ([66.248.192.39] helo=repmmg02.bea.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5UBS-0005v5-B1 for speechsc@ietf.org; Thu, 20 Dec 2007 17:48:08 -0500 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id lBKMm3pA003320; Thu, 20 Dec 2007 14:48:03 -0800 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id lBKMlx3A028793; Thu, 20 Dec 2007 14:48:01 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: RE: [Speechsc] Query on Channel-identifier header in Draft 12 Date: Thu, 20 Dec 2007 14:46:58 -0800 Message-ID: In-Reply-To: <3CE87D3D-E1FB-4CF4-B95E-8EC4D5728FE4@voxeo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speechsc] Query on Channel-identifier header in Draft 12 Thread-Index: AchDWXkQjQ8hNicmRT+SRFJhzjLSfQAALz7A References: <727391.26675.qm@web52712.mail.re2.yahoo.com> <3CE87D3D-E1FB-4CF4-B95E-8EC4D5728FE4@voxeo.com> From: "Eric Burger" To: "Dan Burnett" x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Cc: speechsc@ietf.org, rajanish@huawei.com X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Absolutely right, IMHO. thanks. -----Original Message----- From: Dan Burnett [mailto:dburnett@voxeo.com] Sent: Thursday, December 20, 2007 5:41 PM To: Eric Burger Cc: Arsen Chaloyan; rajanish@huawei.com; speechsc@ietf.org Subject: Re: [Speechsc] Query on Channel-identifier header in Draft 12 I think Arsen's suggestion is close. The production that matches the examples (along with obvious extensions to the list of resources) is 1*alphanum "@" 1*alphanum. Remember, the goal of the first part is to provide an id, while the second part needs to be a resource type. -- dan On Dec 17, 2007, at 3:34 PM, Eric Burger wrote: > The correct production would be either > dot-atom "@" dot-atom > or, more likely > addr-spec > > Both productions coming from RFC 2822. > > ________________________________ > > From: Arsen Chaloyan [mailto:achaloyan@yahoo.com] > Sent: Monday, December 17, 2007 7:46 AM > To: speechsc@ietf.org > Cc: rajanish@huawei.com > Subject: Re: [Speechsc] Query on Channel-identifier header in Draft 12 > > > In my understanding, > an unambiguous string identifying the MRCPv2 session MUST be > ALPHA/DIGIT, but not VCHAR > > > channel-identifier = "Channel-Identifier" ":" channel-id CRLF > > channel-id = 1*ALPHA/DIGIT "@" 1*VCHAR > > > > > probably with some extent to allow extra symbols like "$" / "-" / "_" > / "." / "+" > > Hope this helps, > Arsen. > > > ----- Original Message ---- > From: Rajanish > To: speechsc@ietf.org > Sent: Thursday, December 13, 2007 1:35:07 PM > Subject: [Speechsc] Query on Channel-identifier header in Draft 12 > > > > Hi, > > > > I was trying to understand the ABNF for the channel identifier header, > As per the draft-ietf-speechsc-mrcpv2-12 > > Channel identifier is explained as below > > > > 6.2.1. Channel-Identifier > > > > > > All MRCPv2 requests, responses and events MUST contain the Channel- > > Identifier header. The value is allocated by the server when a > > control channel is added to the session and communicated to the > > client by the "a=channel" attribute in the SDP answer from the > > server. The header value consists of 2 parts separated by the '@' > > symbol. The first part is an unambiguous string identifying the > > MRCPv2 session. The second part is a string token which specifies > > one of the media processing resource types listed in Section 3.1. > > The unambiguous string (first part) MUST BE unique among the > resource > > instances managed by the server and is common to all resource > > channels with that server established through a single SIP dialog. > > > > > > channel-identifier = "Channel-Identifier" ":" channel-id CRLF > > channel-id = 1*VCHAR "@" 1*VCHAR > > > > > > The header value consists of two parts separated by "@" , the First > part is a VCHAR and Second part is also a VCHAR. The problem here is > > '@' also falls in the range of VCHAR set of characters. > > > > VCHAR = %x21-7E (33-126) > > @ = %x40 (64) > > > > So we can have any number of "@" characters in the first part as well > as in second part. due to this we will not be able to distinguish the > first part from second part. > > > > Kindly help me regarding this issue. > > > > Thanks and Regards > > Rajanish S D > > > Notice: This email message, together with any attachments, may > contain information of BEA Systems, Inc., its subsidiaries > and affiliated entities, that may be confidential, proprietary, > copyrighted and/or legally privileged, and is intended solely for the > use of the individual or entity named in this message. If you are not > the intended recipient, and have received this message in error, > please immediately return this by email and then delete it. Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc Supplemental web site: <http://www.standardstrack.com/ietf/speechsc> From speechsc-bounces@ietf.org Fri Dec 21 12:30:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5lhG-0001zx-Ga; Fri, 21 Dec 2007 12:30:06 -0500 Received: from speechsc by megatron.ietf.org with local (Exim 4.43) id 1J5lhC-0001zd-V9 for speechsc-confirm+ok@megatron.ietf.org; Fri, 21 Dec 2007 12:30:02 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5lhC-0001zS-IZ; Fri, 21 Dec 2007 12:30:02 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J5lhC-0007s1-4z; Fri, 21 Dec 2007 12:30:02 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 15D642AC9B; Fri, 21 Dec 2007 17:30:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1J5lhB-0005vp-Qn; Fri, 21 Dec 2007 12:30:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 21 Dec 2007 12:30:01 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: speechsc@ietf.org Subject: [Speechsc] I-D Action:draft-ietf-speechsc-mrcpv2-15.txt X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Speech Services Control Working Group of the IETF. Title : Media Resource Control Protocol Version 2 (MRCPv2) Author(s) : S. Shanmugham, D. Burnett Filename : draft-ietf-speechsc-mrcpv2-15.txt Pages : 210 Date : 2007-12-21 The MRCPv2 protocol allows client hosts to control media service resources such as speech synthesizers, recognizers, verifiers and identifiers residing in servers on the network. MRCPv2 is not a "stand-alone" protocol - it relies on a session management protocol such as the Session Initiation Protocol (SIP) to establish the MRCPv2 control session between the client and the server, and for rendezvous and capability discovery. It also depends on SIP and SDP to establish the media sessions and associated parameters between the media source or sink and the media server. Once this is done, the MRCPv2 protocol exchange operates over the control session established above, allowing the client to control the media processing resources on the speech resource server. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speechsc-mrcpv2-15.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-speechsc-mrcpv2-15.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-speechsc-mrcpv2-15.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-12-21122214.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-speechsc-mrcpv2-15.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-speechsc-mrcpv2-15.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-12-21122214.I-D\@ietf.org> --OtherAccess-- --NextPart 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 Supplemental web site: <http://www.standardstrack.com/ietf/speechsc> --NextPart-- From speechsc-bounces@ietf.org Fri Dec 21 12:40:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5lr4-0005LK-MZ; Fri, 21 Dec 2007 12:40:14 -0500 Received: from speechsc by megatron.ietf.org with local (Exim 4.43) id 1J5lr3-0005Ha-N9 for speechsc-confirm+ok@megatron.ietf.org; Fri, 21 Dec 2007 12:40:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5lr3-0005GG-BO for speechsc@ietf.org; Fri, 21 Dec 2007 12:40:13 -0500 Received: from mmail.voxeo.com ([66.193.54.208] helo=voxeo.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5lr2-0004s1-Tz for speechsc@ietf.org; Fri, 21 Dec 2007 12:40:13 -0500 Received: from [76.111.49.153] (account dburnett HELO [192.168.15.162]) by voxeo.com (CommuniGate Pro SMTP 5.1.12) with ESMTPSA id 25887808 for speechsc@ietf.org; Fri, 21 Dec 2007 17:40:12 +0000 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <31E8CC44-898A-4F3E-BE99-092BBB4CB335@voxeo.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: speechsc@ietf.org From: Dan Burnett Date: Fri, 21 Dec 2007 12:40:11 -0500 X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Subject: [Speechsc] changes in draft -15 X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Group, Here is the list of changes for the most recent draft. -- dan - Changed header name "voice-parameters" to be "voice-parameter" everywhere in document to match ABNF. - In 5.1, added text explaining that headers are disallowed on all methods except those specifically mentioned in the relevant sections. - In 6.2.1 and the ABNF appendix, changed channel-id to be 1*alphanum "@" 1*alphanum to better match examples and intended use. - In 9.4.30, to make the text and examples consistent, changed the text to "The value is either a URI or text. If the value is a URI, it MUST be a Content-ID that refers to an entity of type plain/text in the body of the message. Otherwise, the server MUST treat the value as the text to be interpreted." - In 9.4.38 (Enroll-utterance), noted that the way in which the utterance is added is engine-specific. - In 11.13, removed Verification-Mode line from the example. - In 11.4.4, reworded the text and converted the MAY to a SHOULD in a way that still permits implementation leeway. - In 11.4.5, reworded the text. - In 11.4.6 and 11.4.7, clarified that the header can only appear in SET-PARAMS, GET-PARAMS, or START-SESSION methods. - In 11.4.8, noted that the default value is implementation-specific. - In 11.4.10, reworded the last sentence to make it clearer that the only place this header is permitted is on the VERIFY method. - In 11.4.18, clarified that the header can appear in VERIFY, SET- PARAMS, or GET-PARAMS. - In 11.4.19, clarified that the header can appear in VERIFY. - In 8.4.5, 9.4.12, 10.4.4, and 11.4.17, changed "Clients MAY interpret ..." to be "Clients MUST NOT interpret ...". - In 9.4.8 and 11.4.12, changed "The URI value of the header MUST be NULL ..." to "The value of the header MUST be empty ..." and changed all ABNF accordingly. Also updated related statements throughout the document (9.4.22, 9.4.42, 11.4.10). - In 14.2.4, reworded the text. - In 14.2.5, removed the reference to future work in the W3C Speech Interface Framework. - In 14.2.6, noted that the client controls both the grammar and the semantics to be returned upon grammar matches, so the user of the MRCP protocol is fully empowered to cause results to be returned in NLSML in such a way that the interpretation is clear to that user. - In 14.2.7, reworded the text. - Updated EMMA reference to newest specification. _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc Supplemental web site: <http://www.standardstrack.com/ietf/speechsc>