From exim@www1.ietf.org Wed May 5 13:06:48 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26446 for ; Wed, 5 May 2004 13:06:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLPlb-0005ny-K4 for speechsc-archive@odin.ietf.org; Wed, 05 May 2004 13:01:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i45H17ZD022283 for speechsc-archive@odin.ietf.org; Wed, 5 May 2004 13:01:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLPXn-000157-JF for speechsc-web-archive@optimus.ietf.org; Wed, 05 May 2004 12:46:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25097 for ; Wed, 5 May 2004 12:46:48 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLPXl-0005dt-Sz for speechsc-web-archive@ietf.org; Wed, 05 May 2004 12:46:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLPWs-0005On-00 for speechsc-web-archive@ietf.org; Wed, 05 May 2004 12:45:55 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLPWM-000591-00 for speechsc-web-archive@ietf.org; Wed, 05 May 2004 12:45:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLPSA-0006vR-Uc; Wed, 05 May 2004 12:41:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLPEo-0001QU-4q for speechsc@optimus.ietf.org; Wed, 05 May 2004 12:27:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23646 for ; Wed, 5 May 2004 12:27:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLPEm-00002R-Og for speechsc@ietf.org; Wed, 05 May 2004 12:27:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLPDo-0007Xg-00 for speechsc@ietf.org; Wed, 05 May 2004 12:26:13 -0400 Received: from cerbrus.convedia.com ([216.129.93.50]) by ietf-mx with esmtp (Exim 4.12) id 1BLPD8-0007DS-00 for speechsc@ietf.org; Wed, 05 May 2004 12:25:30 -0400 Received: from ladon.convedia.com (ladon [192.168.208.15]) by cerbrus.convedia.com (8.12.9/8.12.9) with ESMTP id i45GDWEv019061 for ; Wed, 5 May 2004 09:13:32 -0700 (PDT) Received: from laptop33 ([192.168.209.3]) by ladon.convedia.com (8.12.9/8.12.9) with SMTP id i45GO5XU026818 for ; Wed, 5 May 2004 09:24:08 -0700 (PDT) From: "Garland Sharratt" To: Subject: RE: [Speechsc] RE: Scope of MRCPv2 Date: Wed, 5 May 2004 09:24:55 -0700 Keywords: .xbulk, .aa Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <4019679C.2020802@cisco.com> Importance: Normal Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I agree with Eric that we don't want MRCPv2 to expand too far in scope. There are many media server languages already available, and making MRCPv2 into another one would not be a good thing. -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Sarvi Shanmugham Sent: Thursday, January 29, 2004 12:06 To: Eric Burger Cc: SPEECHSC Subject: Re: [Speechsc] RE: Scope of MRCPv2 Though DTMF was not the primary goal, it is supported through DTMF only headers like Dtmf-Term-Char etc. that were added to support VXML documents with DTMF only grammars. I don't believe we have done anything special for audio play back, its just a synthesizer with limited capabilities. There is a need for recording as part of MRCP that has been voiced earlier and agreed on during the last meeting. The MRCPv1 extension proposes a Recording capability where the audio can be played back. A few reasons why recording functionality is being added is that in some cases, 1. we need functionality such as audio end-pointing(related to recognizers) to start and stop recording. 2. we may need to co-ordinate with DTMF recognition and play back for starting and stoping recordings. And again like you say, it was added mostly because there were some requirements related to recognizers and synthesizers. But I believe we should limit its use if some one wants to use it as plain recorder for recording voice mail or something. Fax and Transcoding I agree are not it scope. Sarvi Eric Burger wrote: >Detecting DTMF and playing audio works SO LONG as it is a side-effect, and not a goal. I would not want to see MRCPv2 start handling, for example, fax, transcoding, recording for playback purposes, etc. > >-----Original Message----- >From: Sarvi Shanmugham [mailto:sarvi@cisco.com] >Sent: Wednesday, January 28, 2004 12:53 PM >To: Eric Burger >Cc: SPEECHSC >Subject: Re: [Speechsc] RE: Scope of MRCPv2 > > >I would tend to disagree here. > >The speechrecog resource, in its simplest form can be a DTMF recognizer without any changes to the MRCPv2 protocol. Unless ofcourse the question was about reporting individual digits as opposed to matching DTMF grammars, in which case i agree with you. >The speechsynth resource in its simplest form is an audioplayer(or one that can do concatenated prompts at the next level), without any changes to the MRCPv2 protocol. >The MRCPv1 extension proposal already has recording support, which doesn't seem different from what is requested here. > >So I tend to think that the scenario being requested can be addressed with spec as is and should meet its needs. >The client may at various times choose to resources of varying levels of capabilities such as audioplayer, simplesynth(poor man's TTS) and advanced synth or DTMF only recog and speechrecog. The usage semantics are thre same and we shouldn't require the client to use different protocols for each. > >Sarvi > >Eric Burger wrote: > >I would call your example WAY out of scope. > >Existing device control choices are J.162 (somewhat documented in RFC3435) and H.248.1 (standardized in RFC3525). > >Existing application-level choices are VoiceXML (netann) and MSCML (documented in mscml). > >Do we really need more than that? :-) > > >-----Original Message----- >From: Cullen Jennings [mailto:fluffy@cisco.com] >Sent: Sunday, January 18, 2004 11:16 AM >To: SPEECHSC; Eric Burger; Dave Oran >Subject: Scope of MRCPv2 > > > >I'm trying to figure out the scope of what I should or should >not use MRCPv2 >for so that I can try and decide what might be missing from it. > >Consider the use case of an IVR build with a separated media >device and >controller. The media device plays audio prompts, reports >DTMF input up to >the controller, can stop audio playback when there is DTMF >input, and can >record audio it receives to files for later playback. It does >not do any >TTS, ASR, or speaker verification. > >Is this a use case we want to solve with MRCPv2 or should a different >protocol be used for this? > >Thanks, Cullen > > > > > > >_______________________________________________ >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 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 6 11:30:01 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20241 for ; Thu, 6 May 2004 11:30:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLkhx-0002RP-Dk for speechsc-archive@odin.ietf.org; Thu, 06 May 2004 11:22:45 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46FMjAo009365 for speechsc-archive@odin.ietf.org; Thu, 6 May 2004 11:22:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLkeF-000157-3i for speechsc-web-archive@optimus.ietf.org; Thu, 06 May 2004 11:18:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19545 for ; Thu, 6 May 2004 11:18:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLkeE-0005w9-9H for speechsc-web-archive@ietf.org; Thu, 06 May 2004 11:18:54 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLkdJ-0005Wh-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 11:17:58 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLkcS-00056w-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 11:17:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLkWb-0006wz-OP; Thu, 06 May 2004 11:11:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLkNu-0003g4-RN for speechsc@optimus.ietf.org; Thu, 06 May 2004 11:02:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18647 for ; Thu, 6 May 2004 11:01:58 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLkNs-0006XG-52 for speechsc@ietf.org; Thu, 06 May 2004 11:02:00 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLkNC-00066f-00 for speechsc@ietf.org; Thu, 06 May 2004 11:01:19 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BLkML-0005Zp-00 for speechsc@ietf.org; Thu, 06 May 2004 11:00:25 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Thu, 06 May 2004 11:02:51 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 May 2004 10:59:48 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Thu, 6 May 2004 10:57:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Speechsc] Hotword-Max-Seconds/Hotword-Min-Seconds Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Hi group, the definition of these header fields is inconsistent regarding the measuring unit. I think the value should be specified in milliseconds like all other timer in the spec. In this case Hotword-Max-Duration and Hotword-Min-Duration would be more appropriate header field names. Regards, Klaus _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 6 14:21:47 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08968 for ; Thu, 6 May 2004 14:21:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnHG-00032i-Rl for speechsc-archive@odin.ietf.org; Thu, 06 May 2004 14:07:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46I7MEl011697 for speechsc-archive@odin.ietf.org; Thu, 6 May 2004 14:07:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLn4e-00053G-4z for speechsc-web-archive@optimus.ietf.org; Thu, 06 May 2004 13:54:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07398 for ; Thu, 6 May 2004 13:54:17 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLn4b-0003F4-TS for speechsc-web-archive@ietf.org; Thu, 06 May 2004 13:54:18 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLn3Y-0002lE-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 13:53:12 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLn2R-0002G6-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 13:52:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLmlx-0003kQ-EF; Thu, 06 May 2004 13:35:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLmYv-0003FF-7D for speechsc@optimus.ietf.org; Thu, 06 May 2004 13:21:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03618 for ; Thu, 6 May 2004 13:21:31 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLmYt-0003nE-8I for speechsc@ietf.org; Thu, 06 May 2004 13:21:31 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLmXQ-00033P-00 for speechsc@ietf.org; Thu, 06 May 2004 13:20:01 -0400 Received: from mtl-mx1.nuance.com ([66.46.69.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLmVL-00029I-00 for speechsc@ietf.org; Thu, 06 May 2004 13:17:51 -0400 Received: from mpb1exbr01.nuance.com (mpb1exbr01.nuance.com [10.0.0.43]) by mtl-mx1.nuance.com (Postfix) with ESMTP id 4B6D1FD584; Thu, 6 May 2004 13:17:20 -0400 (EDT) Received: from mtb1exch01.nuance.com ([10.3.2.6]) by mpb1exbr01.nuance.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 6 May 2004 10:17:16 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] Hotword-Max-Seconds/Hotword-Min-Seconds Date: Thu, 6 May 2004 13:17:14 -0400 Message-ID: <7DE7C4EF3B7C8B4B82955191378290D801855EF6@mtb1exch01.nuance.com> Thread-Topic: [Speechsc] Hotword-Max-Seconds/Hotword-Min-Seconds Thread-Index: AcQzfSdeypKdgWQpTWmpiRPpOGZHVAAEMdQA From: "Pierre Forgues" To: "Reifenrath, Klaus" , X-OriginalArrivalTime: 06 May 2004 17:17:16.0783 (UTC) FILETIME=[FB01EFF0:01C4338D] Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Agreed! /Pierre -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org] On Behalf Of Reifenrath, Klaus Sent: 6 mai, 2004 10:58 To: 'speechsc@ietf.org' Subject: [Speechsc] Hotword-Max-Seconds/Hotword-Min-Seconds Hi group, the definition of these header fields is inconsistent regarding the measuring unit. I think the value should be specified in milliseconds like all other timer in the spec. In this case Hotword-Max-Duration and Hotword-Min-Duration would be more appropriate header field names. Regards, Klaus _______________________________________________ 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 exim@www1.ietf.org Thu May 6 15:17:01 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13064 for ; Thu, 6 May 2004 15:17:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLoHo-00033m-4x for speechsc-archive@odin.ietf.org; Thu, 06 May 2004 15:12:00 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46JC0J1011758 for speechsc-archive@odin.ietf.org; Thu, 6 May 2004 15:12:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLoBA-0004YY-Vf for speechsc-web-archive@optimus.ietf.org; Thu, 06 May 2004 15:05:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11431 for ; Thu, 6 May 2004 15:05:05 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLoB8-0001v0-2r for speechsc-web-archive@ietf.org; Thu, 06 May 2004 15:05:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLoAB-0001Uc-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 15:04:08 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLo9Q-00014s-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 15:03:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnyT-0004CP-AB; Thu, 06 May 2004 14:52:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnow-0007i7-Bf for speechsc@optimus.ietf.org; Thu, 06 May 2004 14:42:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10370 for ; Thu, 6 May 2004 14:42:07 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnot-0000DR-Iv for speechsc@ietf.org; Thu, 06 May 2004 14:42:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnoG-0007b8-00 for speechsc@ietf.org; Thu, 06 May 2004 14:41:29 -0400 Received: from mx2.scansoft.com ([198.71.64.82]) by ietf-mx with esmtp (Exim 4.12) id 1BLnnG-00075F-00 for speechsc@ietf.org; Thu, 06 May 2004 14:40:26 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx2 with trend_isnt_name_B; Thu, 06 May 2004 14:40:08 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 May 2004 14:39:55 -0400 Message-ID: <9E452E1028D9664E89CA1BBCF166805701C2B556@bn-exch1.speechworks.com> From: "Eberman, Brian" To: "'speechsc@ietf.org'" Cc: "Reifenrath, Klaus" Date: Thu, 6 May 2004 14:39:53 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43399.853F0850" Subject: [Speechsc] General SpeechSC draft feedback Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE autolearn=no version=2.60 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C43399.853F0850 Content-Type: text/plain I'm concerned about the SpeechSC specification along a complexity axis and portability axis. This is going to make the standard unnecessarily brittle and will slow adoption of what ScanSoft feels is a critical specification. In designing the originally specification we focused on some critical tests: 1) Platform not application portability -- is this piece of the specification required for platform communication portability or is it required for the application portability and is it attempting to standardize the application dev model. If its for the platform and is something the platform must know then it needs to be in the standard, otherwise its an extension point. The ASR section is getting very complex and difficult to understand and there are sections in there that I'm not convinced are required for anything except application portability. For example the timers for hot-word are not required in some of the hot-word implementations we do and why does the platform needs these variables. 2) Minimal messages --- we worked to make sure that the communication and messages were minimal. If a task could be accomplished within the standard even if the mechanism was not completely clear then it was sufficient, no syntactic sugar should be in the spec. For example now there is an entire section on voice enrollment. However the current v 1 specification is quite sufficient for voice enrollment. ScanSoft's solution can do voice enrollment already with the current specification. So why are we adding a significant amount of overhead to the specification to standardize a mechanism that isn't required. If extensions to return results are required to provide a more general mechanism then we are in favor of that. Second if something could be done with the current messages then it shouldn't be replicated by other means. For example now there is a parameter for the Recognize command that controls if it dequeues other recognizes that may have already been sent. A STOP already has this functionality. 3) Simplicity of the device -- we assumed that the device could perform actions very quickly and that it was as near stateless as possible. We wanted to make sure that if it failed a new device could come in and take over with minimal disruption to the service. Both the verification and voice enrollment specifications currently violate this approach. 4) Separation of services - Some significant progress has been made in this area and it needs to continue. This is the key problem of how you build a VXML device that doesn't have to see the audio. We are preparing a discussion on coordination of RTP playback that will be needed in the TTS section to help drive this. -Brian Eberman ------_=_NextPart_001_01C43399.853F0850 Content-Type: text/html Message
I'm concerned about the SpeechSC specification along a complexity axis and portability axis.  This is going to make the standard unnecessarily brittle and will slow adoption of what ScanSoft feels is a critical specification.
 
In designing the originally specification we focused on some critical tests:
 
1) Platform not application portability --  is this piece of the specification required for platform communication portability or is it required for the application portability and is it attempting to standardize the application dev model. If its for the platform and is something the platform must know then it needs to be in the standard, otherwise its an extension point.   The ASR section is getting very complex and difficult to understand and there are sections in there that I'm not convinced are required for anything except application portability.
 
For example the timers for hot-word are not required in some of the hot-word implementations we do and why does the platform needs these variables.
 
2) Minimal messages --- we worked to make sure that the communication and messages were minimal. If a task could be accomplished within the standard even if the mechanism was not completely clear then it was sufficient, no syntactic sugar should be in the spec.
 
For example now there is an entire section on voice enrollment. However the current v 1 specification is quite sufficient for voice enrollment. ScanSoft's solution can do voice enrollment already with the current specification. So why are we adding a significant amount of overhead to the specification to standardize a mechanism that isn't required.  If extensions to return results are required to provide a more general mechanism then we are in favor of that.
 
Second if something could be done with the current messages then it shouldn't be replicated by other means. For example now there is a parameter for the Recognize command that controls if it dequeues other recognizes that may have already been sent. A STOP already has this functionality.
 
3) Simplicity of the device -- we assumed that the device could perform actions very quickly and that it was as near stateless as possible. We wanted to make sure that if it failed a new device could come in and take over with minimal disruption to the service.  Both the verification and voice enrollment specifications currently violate this approach.
 
4) Separation of services -  Some significant progress has been made in this area and it needs to continue. This is the key problem of how you build a VXML device that doesn't have to see the audio.  We are preparing a discussion on coordination of RTP playback that will be needed in the TTS section to help drive this.
 
-Brian Eberman
 
------_=_NextPart_001_01C43399.853F0850-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 6 16:50:35 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18331 for ; Thu, 6 May 2004 16:50:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLpml-0008PH-8o for speechsc-archive@odin.ietf.org; Thu, 06 May 2004 16:48:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46Km3lf032311 for speechsc-archive@odin.ietf.org; Thu, 6 May 2004 16:48:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLpjP-000783-T9 for speechsc-web-archive@optimus.ietf.org; Thu, 06 May 2004 16:44:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18055 for ; Thu, 6 May 2004 16:44:32 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLpjN-0004q7-VR for speechsc-web-archive@ietf.org; Thu, 06 May 2004 16:44:34 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLpiI-0004OW-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 16:43:27 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLphU-0003vw-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 16:42:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLpYD-0001Cw-3A; Thu, 06 May 2004 16:33:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLpTT-00080A-AJ for speechsc@optimus.ietf.org; Thu, 06 May 2004 16:28:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17342 for ; Thu, 6 May 2004 16:28:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLpTR-0005yB-FX for speechsc@ietf.org; Thu, 06 May 2004 16:28:05 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLpSf-0005Yx-00 for speechsc@ietf.org; Thu, 06 May 2004 16:27:18 -0400 Received: from mtl-mx1.nuance.com ([66.46.69.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLpRw-000563-00 for speechsc@ietf.org; Thu, 06 May 2004 16:26:32 -0400 Received: from mpb1exbr01.nuance.com (mpb1exbr01.nuance.com [10.0.0.43]) by mtl-mx1.nuance.com (Postfix) with ESMTP id 2C9ABFDBCC; Thu, 6 May 2004 16:26:04 -0400 (EDT) Received: from MPB1EXCH02.nuance.com ([10.0.0.56]) by mpb1exbr01.nuance.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 6 May 2004 13:25:59 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C433A8.57D82784" Subject: RE: [Speechsc] General SpeechSC draft feedback Date: Thu, 6 May 2004 13:25:59 -0700 Message-ID: Thread-Topic: [Speechsc] General SpeechSC draft feedback Thread-Index: AcQznLhC6g+L/S/+QQGUFp5XX08iHgACfAYg From: "Daniel Burnett" To: "Eberman, Brian" , Cc: "Reifenrath, Klaus" X-OriginalArrivalTime: 06 May 2004 20:25:59.0798 (UTC) FILETIME=[580CE960:01C433A8] Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_20_30, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 This is a multi-part message in MIME format. ------_=_NextPart_001_01C433A8.57D82784 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I should point out that we have had virtually 100% Scansoft = participation and support for the features in the specification. They = have been worked out as compromises that permit the best of what vendors = have to offer within a standard framework. Not all features are needed = by all vendors, but every feature was accepted in the document by all = who have been participating. We have all accepted features that only = others needed, as is occasionally appropriate in any compromise-driven = body such as a standards organization. =20 In my mind the key question is, "Is there a new problem that didn't = exist in January when these extensions first appeared in the document?" = If the answer is no, then why don't we just finish up (since we're = almost done) so adoption of the specification can begin? =20 -- dan =20 -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf = Of Eberman, Brian Sent: Thursday, May 06, 2004 11:40 AM To: 'speechsc@ietf.org' Cc: Reifenrath, Klaus Subject: [Speechsc] General SpeechSC draft feedback I'm concerned about the SpeechSC specification along a complexity axis = and portability axis. This is going to make the standard unnecessarily = brittle and will slow adoption of what ScanSoft feels is a critical = specification.=20 =20 In designing the originally specification we focused on some critical = tests: =20 1) Platform not application portability -- is this piece of the = specification required for platform communication portability or is it = required for the application portability and is it attempting to = standardize the application dev model. If its for the platform and is = something the platform must know then it needs to be in the standard, = otherwise its an extension point. The ASR section is getting very = complex and difficult to understand and there are sections in there that = I'm not convinced are required for anything except application = portability.=20 =20 For example the timers for hot-word are not required in some of the = hot-word implementations we do and why does the platform needs these = variables. =20 2) Minimal messages --- we worked to make sure that the communication = and messages were minimal. If a task could be accomplished within the = standard even if the mechanism was not completely clear then it was = sufficient, no syntactic sugar should be in the spec. =20 For example now there is an entire section on voice enrollment. However = the current v 1 specification is quite sufficient for voice enrollment. = ScanSoft's solution can do voice enrollment already with the current = specification. So why are we adding a significant amount of overhead to = the specification to standardize a mechanism that isn't required. If = extensions to return results are required to provide a more general = mechanism then we are in favor of that. =20 Second if something could be done with the current messages then it = shouldn't be replicated by other means. For example now there is a = parameter for the Recognize command that controls if it dequeues other = recognizes that may have already been sent. A STOP already has this = functionality. =20 3) Simplicity of the device -- we assumed that the device could perform = actions very quickly and that it was as near stateless as possible. We = wanted to make sure that if it failed a new device could come in and = take over with minimal disruption to the service. Both the verification = and voice enrollment specifications currently violate this approach. =20 4) Separation of services - Some significant progress has been made in = this area and it needs to continue. This is the key problem of how you = build a VXML device that doesn't have to see the audio. We are = preparing a discussion on coordination of RTP playback that will be = needed in the TTS section to help drive this. =20 -Brian Eberman =20 ------_=_NextPart_001_01C433A8.57D82784 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
I=20 should point out that we have had virtually 100% Scansoft participation = and=20 support for the features in the specification.  They have been = worked out=20 as compromises that permit the best of what vendors have to offer within = a=20 standard framework.  Not all features are needed by all vendors, = but every=20 feature was accepted in the document by all who have been = participating. =20 We have all accepted features that only others needed, as is = occasionally=20 appropriate in any compromise-driven body such as a standards=20 organization.
 
In my=20 mind the key question is, "Is there a new problem that didn't exist in = January=20 when these extensions first appeared in the document?"  If the = answer is=20 no, then why don't we just finish up (since we're almost done) so = adoption of=20 the specification can begin?
 
--=20 dan
 
-----Original Message-----
From: = speechsc-admin@ietf.org=20 [mailto:speechsc-admin@ietf.org]On Behalf Of Eberman,=20 Brian
Sent: Thursday, May 06, 2004 11:40 AM
To:=20 'speechsc@ietf.org'
Cc: Reifenrath, Klaus
Subject:=20 [Speechsc] General SpeechSC draft feedback

I'm = concerned about=20 the SpeechSC specification along a complexity axis and portability = axis. =20 This is going to make the standard unnecessarily brittle and will slow = adoption=20 of what ScanSoft feels is a critical specification.
 
In = designing the=20 originally specification we focused on some critical = tests:
 
1) = Platform=20 not application portability --  is this piece of the = specification=20 required for platform communication portability or is it required for = the=20 application portability and is it attempting to standardize the = application dev=20 model. If its for the platform and is something the platform must know = then it=20 needs to be in the standard, otherwise its an extension point.  =  The=20 ASR section is getting very complex and difficult to understand and = there are=20 sections in there that I'm not convinced are required for anything = except=20 application portability.
 
For = example the=20 timers for hot-word are not required in some of the hot-word = implementations we=20 do and why does the platform needs these variables.
 
2) = Minimal=20 messages --- we worked to make sure that the communication and = messages=20 were minimal. If a task could be accomplished within the standard even = if the=20 mechanism was not completely clear then it was sufficient, no syntactic = sugar=20 should be in the spec.
 
For = example now=20 there is an entire section on voice enrollment. However the current v 1=20 specification is quite sufficient for voice enrollment. ScanSoft's = solution can=20 do voice enrollment already with the current specification. So why are = we adding=20 a significant amount of overhead to the specification to standardize a = mechanism=20 that isn't required.  If extensions to return results are required = to=20 provide a more general mechanism then we are in favor of=20 that.
 
Second = if something=20 could be done with the current messages then it shouldn't be replicated = by other=20 means. For example now there is a parameter for the Recognize command = that=20 controls if it dequeues other recognizes that may have already been = sent. A STOP=20 already has this functionality.
 
3)=20 Simplicity of the device -- we assumed that the device = could=20 perform actions very quickly and that it was as near stateless as = possible. We=20 wanted to make sure that if it failed a new device could come in and = take over=20 with minimal disruption to the service.  Both the verification and = voice=20 enrollment specifications currently violate this = approach.
 
4) Separation of services = -  Some=20 significant progress has been made in this area and it needs to = continue. This=20 is the key problem of how you build a VXML device that doesn't have to = see the=20 audio.  We are preparing a discussion on coordination of RTP = playback that=20 will be needed in the TTS section to help drive = this.
 
-Brian = Eberman
 
= ------_=_NextPart_001_01C433A8.57D82784-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 6 18:10:19 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23320 for ; Thu, 6 May 2004 18:10:19 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLr2N-00069b-SB for speechsc-archive@odin.ietf.org; Thu, 06 May 2004 18:08:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46M8FOl023650 for speechsc-archive@odin.ietf.org; Thu, 6 May 2004 18:08:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqwn-0002Ee-72 for speechsc-web-archive@optimus.ietf.org; Thu, 06 May 2004 18:02:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22308 for ; Thu, 6 May 2004 18:02:25 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLqwk-0006O3-KO for speechsc-web-archive@ietf.org; Thu, 06 May 2004 18:02:26 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLqvm-0005wy-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 18:01:27 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLqud-0005UG-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 18:00:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqoa-0006Xe-PI; Thu, 06 May 2004 17:54:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqju-0004jU-Aa for speechsc@optimus.ietf.org; Thu, 06 May 2004 17:49:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21624 for ; Thu, 6 May 2004 17:49:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLqjr-0000pG-PX for speechsc@ietf.org; Thu, 06 May 2004 17:49:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLqj0-0000QN-00 for speechsc@ietf.org; Thu, 06 May 2004 17:48:15 -0400 Received: from mtl-mx1.nuance.com ([66.46.69.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLqiQ-0007lg-00 for speechsc@ietf.org; Thu, 06 May 2004 17:47:38 -0400 Received: from mpb1exbr01.nuance.com (mpb1exbr01.nuance.com [10.0.0.43]) by mtl-mx1.nuance.com (Postfix) with ESMTP id 4DCC2FD827; Thu, 6 May 2004 17:47:11 -0400 (EDT) Received: from MPB1EXCH02.nuance.com ([10.0.0.56]) by mpb1exbr01.nuance.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 6 May 2004 14:47:07 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] Remarks on the verification result Date: Thu, 6 May 2004 14:47:07 -0700 Message-ID: Thread-Topic: [Speechsc] Remarks on the verification result Thread-Index: AcQbE0NtHGc8ZX7zR7CRYQPKykol1gYel5Sw From: "Daniel Burnett" To: "Reifenrath, Klaus" , X-OriginalArrivalTime: 06 May 2004 21:47:07.0422 (UTC) FILETIME=[AD6163E0:01C433B3] Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Responses embedded below. -- dan -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Reifenrath, Klaus Sent: Monday, April 05, 2004 6:35 AM To: 'speechsc@ietf.org' Subject: [Speechsc] Remarks on the verification result Verification result (see =A711.5): SV/SI is not the primary focus of NLSML or EMMA. Therefore the result = format needs to be defined in more detail. Especially the grammar attribute = (see example on page 101) needs some explanation, because in SV/SI no = grammars are involved. Also the incremental and cumulative elements need to be defined. DB>> Agreed. There needs to be an XML DTD and/or Schema to better = define the results. The current plan is to make these elements = available via a special MRCP namespace rather than changing NLSML/EMMA = itself. Num-frames seems to be very vendor specific. What if a vendor does not = have a 10ms frame rate? The intent of this parameter is not clear - i.e., if = it's intended to denote the amount of speech data (such as to make sure the utterance is not too short for reliable verification) - then, the result here should be a measurement in units of time (not frames). DB>> This is a tricky one. While a vender might not use 10ms frames, I = believe it is the most common value today. I think we actually = discussed this in a face-to-face meeting and decided at the time that a = 10ms frame size was fine. Maybe we should discuss this one? SV/SI engines that do not support gender or device detection cannot = return a meaningful value for 'matched'. Is this the reason why it is missing in = all examples? I suggest to remove it from the spec. DB>> Agreed. It should be removed from the spec. The spec should specify the range for verification-score and score: -1.0 = - 1.0 (negative scores are recommended for failing, positive scores are recommended for passing, size of number indicates confidence) DB>> It seems that only one confidence value is needed -- the confidence = that the person is who they claim to be. We could then just use a range = of 0 to 1. However, we should make it clear in the spec that although = the range is 0 to 1 it's not guaranteed to be a probability. Regards, Klaus _______________________________________________ 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 exim@www1.ietf.org Thu May 6 18:18:57 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24139 for ; Thu, 6 May 2004 18:18:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLr7I-0001Bs-Ht for speechsc-archive@odin.ietf.org; Thu, 06 May 2004 18:13:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46MDKLC004571 for speechsc-archive@odin.ietf.org; Thu, 6 May 2004 18:13:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLr3I-0006g4-JC for speechsc-web-archive@optimus.ietf.org; Thu, 06 May 2004 18:09:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23192 for ; Thu, 6 May 2004 18:09:08 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLr3F-0001UW-S2 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 18:09:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLr2F-00013x-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 18:08:07 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLr1A-0000c4-00 for speechsc-web-archive@ietf.org; Thu, 06 May 2004 18:07:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqvP-0000zH-6A; Thu, 06 May 2004 18:01:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqpj-0006qU-AU for speechsc@optimus.ietf.org; Thu, 06 May 2004 17:55:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21856 for ; Thu, 6 May 2004 17:55:07 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLqpg-0003K9-N0 for speechsc@ietf.org; Thu, 06 May 2004 17:55:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLqoh-0002un-00 for speechsc@ietf.org; Thu, 06 May 2004 17:54:08 -0400 Received: from e31.co.us.ibm.com ([32.97.110.129]) by ietf-mx with esmtp (Exim 4.12) id 1BLqnp-000260-00 for speechsc@ietf.org; Thu, 06 May 2004 17:53:14 -0400 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e31.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i46Lqgpj400790 for ; Thu, 6 May 2004 17:52:42 -0400 Received: from d03nm120.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i46Lqf8x375180 for ; Thu, 6 May 2004 15:52:42 -0600 In-Reply-To: To: speechsc@ietf.org MIME-Version: 1.0 Subject: [Speechsc] Recognition results X-Mailer: Lotus Notes Release 6.5 September 26, 2003 From: Jeff Kusnitz Message-ID: Date: Thu, 6 May 2004 14:53:13 -0700 X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 6.0.2CF2|July 23, 2003) at 05/06/2004 15:52:42, Serialize complete at 05/06/2004 15:52:42 Content-Type: text/plain; charset="US-ASCII" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no version=2.60 Example 1 at the bottom of page 65 has a small typo in it - the closing quotation mark is missing for the grammar URI (the same quotation mark is missing from the results in the example on page 71) But that's not why I'm posting :-) When a recognizer matches a grammar, it needs to process the semantic interpretation tags that are encoded in the grammar and return an NLSML document to the client. What happens if the SI is somehow malformed such that a recognition engine can not process it after recognition has completed? There doesn't seem to be an applicable return code - the recognition has completed successfully. It seems another cause-code/name is in order? And would the server return the incomplete NLSML results: S->C:MRCP/2.0 486 RECOGNITION-COMPLETE 543260 COMPLETE Channel-Identifier: 32AECB23433801@speechrecog Completion-Cause: 043 bad-semantic-tag Content-Type: applicationt/x-nlsml Content-Length: 276 may I speak to Andre Roy Thanks, Jeff _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri May 7 04:27:47 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08123 for ; Fri, 7 May 2004 04:27:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM0ag-0007HO-VK for speechsc-archive@odin.ietf.org; Fri, 07 May 2004 04:20:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i478KI9x027982 for speechsc-archive@odin.ietf.org; Fri, 7 May 2004 04:20:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM0QN-0002qw-T1 for speechsc-web-archive@optimus.ietf.org; Fri, 07 May 2004 04:09:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06700 for ; Fri, 7 May 2004 04:09:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM0QL-0000mV-9W for speechsc-web-archive@ietf.org; Fri, 07 May 2004 04:09:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM0PP-0000MH-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 04:08:39 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BM0Oe-0007iV-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 04:07:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM0I9-0007SU-Pf; Fri, 07 May 2004 04:01:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM00R-00028C-Ph for speechsc@optimus.ietf.org; Fri, 07 May 2004 03:42:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02753 for ; Fri, 7 May 2004 03:42:49 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM00P-0004j1-9Q for speechsc@ietf.org; Fri, 07 May 2004 03:42:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLzzb-0004Hk-00 for speechsc@ietf.org; Fri, 07 May 2004 03:41:59 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BLzyi-0003n8-00 for speechsc@ietf.org; Fri, 07 May 2004 03:41:04 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Fri, 07 May 2004 03:43:32 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 May 2004 03:40:30 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Fri, 7 May 2004 03:35:44 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Speechsc] =?iso-8859-1?Q?=A711=2E4_Adapt-Model?= Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 The description of this header field can be misunderstood in such a way that if adapt-model is true, the model necessarily gets adapted. I suggest to change "audio ... is used to ..." to "audio ... may be used to ...". Klaus _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri May 7 11:12:54 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29902 for ; Fri, 7 May 2004 11:12:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6cy-0006Ay-Hw for speechsc-archive@odin.ietf.org; Fri, 07 May 2004 10:47:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i47El49c023740 for speechsc-archive@odin.ietf.org; Fri, 7 May 2004 10:47:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6QW-0000XP-Pg for speechsc-web-archive@optimus.ietf.org; Fri, 07 May 2004 10:34:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26225 for ; Fri, 7 May 2004 10:34:08 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM6QU-00009W-FU for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:34:10 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM6PJ-0007R0-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:32:58 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BM6OM-0006wB-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:31:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM5vg-00010N-Lt; Fri, 07 May 2004 10:02:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM412-0001oG-9K for speechsc@optimus.ietf.org; Fri, 07 May 2004 07:59:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17156 for ; Fri, 7 May 2004 07:59:42 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM411-0002pH-CY for speechsc@ietf.org; Fri, 07 May 2004 07:59:43 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM405-0002QN-00 for speechsc@ietf.org; Fri, 07 May 2004 07:58:45 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BM3zl-000211-00 for speechsc@ietf.org; Fri, 07 May 2004 07:58:25 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Fri, 07 May 2004 08:00:53 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 May 2004 07:57:49 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Fri, 7 May 2004 07:56:22 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Speechsc] Status Codes Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 SIP distinguishes between 4xx and 5xx error codes: 4xx: Client Error -- the request contains bad syntax or cannot be fulfilled at this server; 5xx: Server Error -- the server failed to fulfil an apparently valid request; This seems to be useful also for MRCP. I think the following status codes should be added to the spec: 410 Unsupported Media Type The server is refusing to service the request because the message body of the request is in a format not supported by the requested resource for the requested method. Unfortunately there is currently no mechanism in place to find out which media types are supported by a resource. 411 Length Required The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message. 500 Server Internal Error (would replace 407) The server encountered an unexpected condition that prevented it from fulfilling the request. The client MAY display the specific error condition, and MAY retry the request. 501 Not Implemented The server does not support the functionality required to fulfil the request. This is the appropriate response when the resource does not recognize the request method and is not capable of supporting it. 502 Version Not Supported The server does not support, or refuses to support, the MRCP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, other than with this error message. What error code should be returned by a server if the client tries to set an unsupported vendor specific parameter? 403 (unsupported parameter) seems not to be right, because the MRCP parameter 'vendor-specific-parameter' is supported. 404 (illegal value for parameter) could be used, but is misleading Regards, Klaus _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri May 7 11:12:55 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29907 for ; Fri, 7 May 2004 11:12:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6d0-0006DF-DX for speechsc-archive@odin.ietf.org; Fri, 07 May 2004 10:47:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i47El6Dt023873 for speechsc-archive@odin.ietf.org; Fri, 7 May 2004 10:47:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6Qn-0000jh-Nw for speechsc-web-archive@optimus.ietf.org; Fri, 07 May 2004 10:34:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26290 for ; Fri, 7 May 2004 10:34:25 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM6Ql-0000Bz-9w for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:34:27 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM6Pi-0007UZ-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:33:23 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BM6On-00070N-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:32:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM5vk-00013m-Lc; Fri, 07 May 2004 10:02:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM46D-0004MB-AZ for speechsc@optimus.ietf.org; Fri, 07 May 2004 08:05:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17284 for ; Fri, 7 May 2004 08:05:03 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM46C-0004te-CD for speechsc@ietf.org; Fri, 07 May 2004 08:05:04 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM44t-0004Qw-00 for speechsc@ietf.org; Fri, 07 May 2004 08:03:44 -0400 Received: from mx2.scansoft.com ([198.71.64.82]) by ietf-mx with esmtp (Exim 4.12) id 1BM44b-000421-00 for speechsc@ietf.org; Fri, 07 May 2004 08:03:26 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx2 with trend_isnt_name_B; Fri, 07 May 2004 08:03:08 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 May 2004 08:02:54 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Fri, 7 May 2004 08:02:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Speechsc] generic-header Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Hi group! The header field 'vendor-specific' is defined for all resources, only exception currently is the recorder resource . I suggest to make it a generic-header. Regards, Klaus _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri May 7 11:16:33 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00256 for ; Fri, 7 May 2004 11:16:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6fN-0006nU-69 for speechsc-archive@odin.ietf.org; Fri, 07 May 2004 10:49:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i47EnXrW026124 for speechsc-archive@odin.ietf.org; Fri, 7 May 2004 10:49:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6YA-00046E-CA for speechsc-web-archive@optimus.ietf.org; Fri, 07 May 2004 10:42:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27063 for ; Fri, 7 May 2004 10:42:02 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM6Y8-0003bw-53 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:42:04 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM6WY-0002lR-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:40:27 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BM6V1-0001vO-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:38:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM5wI-0001nL-Id; Fri, 07 May 2004 10:02:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM4xO-0005rP-Jx for speechsc@optimus.ietf.org; Fri, 07 May 2004 09:00:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19594 for ; Fri, 7 May 2004 08:59:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM4xN-0004jG-2T for speechsc@ietf.org; Fri, 07 May 2004 09:00:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM4wI-0004FY-00 for speechsc@ietf.org; Fri, 07 May 2004 08:58:54 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BM4v8-0003Kb-00 for speechsc@ietf.org; Fri, 07 May 2004 08:57:42 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Fri, 07 May 2004 09:00:14 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 May 2004 08:57:10 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Fri, 7 May 2004 08:57:05 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Speechsc] changing verification servers Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 What about changing verification servers (say for load balancing reasons)? For consistency (see recognizer context block in 9.4 and 9.5), we should add a verifier-context-block header field to the verification resource (see below). Open issues: - What happens to the buffered data? - What happens to an open verification session? Can it be continued on the next server? With the current spec client side load-balancing and session failover becomes very difficult if not impossible! The same is true for enrollment sessions. Klaus Verifier Context Block When the client has to change verification servers within a call, this is a block of data that the client MAY collect from the first media server and provide to the second media server. Here the first verifier may have collected acoustic and other data during its verification. When we switch verification servers, communicating this data may allow the second verification server to provide better verification based on the acoustic data collected by the previous verifier. This block of data is vendor-specific and MUST be carried as MIME-type application/octets in the body of the message. This block of data is communicated in the SET-PARAMS and GET-PARAMS method/response messages. In the GET-PARAMS method, if an empty verifier-context-block header field is present, then the recognizer should return its vendor-specific context block in the message body as a MIME-entity with a specific content-id. The content-id value should also be specified in the verifier-context- block header field in the GET-PARAMS response. The SET-PARAMS request wishing to provide this vendor-specific data should send it in the message body as a MIME-entity with the same content-id that it received from the GET-PARAMS. The content-id should also be sent in the verifier-context-block header field of the SET-PARAMS message. Each vendor choosing to use this mechanism to handoff verifier context data among its servers should distinguish its vendor-specific block of data from other vendors by choosing a unique content-id that they should recognize. Klaus _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri May 7 11:17:35 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00331 for ; Fri, 7 May 2004 11:17:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6gT-0007BW-6b for speechsc-archive@odin.ietf.org; Fri, 07 May 2004 10:50:41 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i47Eofrw027613 for speechsc-archive@odin.ietf.org; Fri, 7 May 2004 10:50:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM6Zd-0004Np-JG for speechsc-web-archive@optimus.ietf.org; Fri, 07 May 2004 10:43:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27302 for ; Fri, 7 May 2004 10:43:33 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM6Zb-0004QK-5f for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:43:35 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM6Y4-0003Zz-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:42:00 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BM6WS-0002kZ-00 for speechsc-web-archive@ietf.org; Fri, 07 May 2004 10:40:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM5xK-0002l1-4w; Fri, 07 May 2004 10:04:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BM531-0007n1-5h for speechsc@optimus.ietf.org; Fri, 07 May 2004 09:05:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20313 for ; Fri, 7 May 2004 09:05:48 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BM52z-0007Xf-KE for speechsc@ietf.org; Fri, 07 May 2004 09:05:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BM51m-0006lx-00 for speechsc@ietf.org; Fri, 07 May 2004 09:04:34 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BM50F-0005h9-00 for speechsc@ietf.org; Fri, 07 May 2004 09:03:00 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Fri, 07 May 2004 09:05:32 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Fri, 7 May 2004 09:02:29 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Fri, 7 May 2004 09:02:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Speechsc] request-id Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Currently it is only required that the request-id is a unique identifier. In MRCPv1 client and server could make use of the command sequence number (CSeq header field) of the RTSP message. In MRCPv2 the request-id can take over this part, if it meets the following requirements: The initial value of the request-id is arbitrary, but MUST be less than 2**31. Consecutive requests within a MRCP session MUST contain strictly monotonically increasing and contiguous request-id's; request-id's do not wrap around. Klaus _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Tue May 11 09:28:52 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25296 for ; Tue, 11 May 2004 09:28:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNXH0-0003VV-CG for speechsc-archive@odin.ietf.org; Tue, 11 May 2004 09:26:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BDQIUk013477 for speechsc-archive@odin.ietf.org; Tue, 11 May 2004 09:26:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNXBq-0002ge-AI for speechsc-web-archive@optimus.ietf.org; Tue, 11 May 2004 09:20:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24826 for ; Tue, 11 May 2004 09:20:55 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNXBo-00018k-Nb for speechsc-web-archive@ietf.org; Tue, 11 May 2004 09:20:56 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNXAh-0000ij-00 for speechsc-web-archive@ietf.org; Tue, 11 May 2004 09:19:48 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNX9g-0000J6-00 for speechsc-web-archive@ietf.org; Tue, 11 May 2004 09:18:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNWxO-00088m-Md; Tue, 11 May 2004 09:06:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNWtI-0006sg-8T for speechsc@optimus.ietf.org; Tue, 11 May 2004 09:01:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24025 for ; Tue, 11 May 2004 09:01:45 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNWtG-0001Nu-Nm for speechsc@ietf.org; Tue, 11 May 2004 09:01:46 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNWsK-00011S-00 for speechsc@ietf.org; Tue, 11 May 2004 09:00:49 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BNWrd-0000IC-00 for speechsc@ietf.org; Tue, 11 May 2004 09:00:05 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Tue, 11 May 2004 09:02:43 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Tue, 11 May 2004 08:59:34 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Tue, 11 May 2004 08:56:17 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Speechsc] DTMF-Term-Timeout Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 The current definition of the DTMF-Term-Timeout header field does not explain the difference between DTMF-Term-Timeout and DTMF-Interdigit-Timeout. I suggest to add the following: The DTMF-Term-Timeout applies only when no additional input is allowed by the grammar; otherwise, the DTMF-Interdigit-Timeout applies. Why does MRCP specify a default value of 10 seconds while VoiceXML 2.0 uses the default value 0? The default value for DTMF-Interdigit-Timeout should be platform specific (as in VoiceXML 2.0). VoiceXML also defines a different default value for the DTMF-Term-Char. Klaus _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 13 17:38:40 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17846 for ; Thu, 13 May 2004 17:38:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BONm6-0004ro-BE for speechsc-archive@odin.ietf.org; Thu, 13 May 2004 17:29:54 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DLTs0U018700 for speechsc-archive@odin.ietf.org; Thu, 13 May 2004 17:29:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BONge-0001YE-0j for speechsc-web-archive@optimus.ietf.org; Thu, 13 May 2004 17:24:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15909 for ; Thu, 13 May 2004 17:24:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BONgb-0001Iu-NV for speechsc-web-archive@ietf.org; Thu, 13 May 2004 17:24:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BONdl-0007mH-00 for speechsc-web-archive@ietf.org; Thu, 13 May 2004 17:21:18 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BONcO-00076P-04 for speechsc-web-archive@ietf.org; Thu, 13 May 2004 17:19:52 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BONVb-0000w4-JA for speechsc-web-archive@ietf.org; Thu, 13 May 2004 17:12:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOMlR-0005Cj-2F; Thu, 13 May 2004 16:25:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOMNK-00082F-A0 for speechsc@optimus.ietf.org; Thu, 13 May 2004 16:00:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09891 for ; Thu, 13 May 2004 16:00:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOMNI-0001Jv-IB for speechsc@ietf.org; Thu, 13 May 2004 16:00:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOMMJ-0000mn-00 for speechsc@ietf.org; Thu, 13 May 2004 15:59:12 -0400 Received: from vtg-um-e2k1.cisco.com ([171.70.93.55] helo=vtg-um-e2k1.sj21ad.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BOMLA-0007XM-00 for speechsc@ietf.org; Thu, 13 May 2004 15:58:00 -0400 Received: from cisco.com ([10.32.130.132]) by vtg-um-e2k1.sj21ad.cisco.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 13 May 2004 12:57:30 -0700 Message-ID: <40A3D32A.6040003@cisco.com> Date: Thu, 13 May 2004 12:57:30 -0700 From: Sarvi Shanmugham Organization: Cisco Systems Inc. User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "IETF SPEECHSC (E-mail)" Content-Type: multipart/alternative; boundary="------------040702020305040900060705" X-OriginalArrivalTime: 13 May 2004 19:57:30.0394 (UTC) FILETIME=[860ECFA0:01C43924] Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_MESSAGE, HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. --------------040702020305040900060705 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit The MRCPv2 draft has been updated to version -03. Please find below the change logs for the new draft. Thanks, Sarvi 1. Updated Referce numbers to be acurate. 2. In the Introduction ......................... The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session. The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement. .................. 3. Added Security Considerations. 4. Updated with various types and corrections mentioned via email. 5. MRCP-Version description added the following text, per Klaus's request. Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0". 6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources. 7. Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke 8. Moved Vendor specific headers to be a generic header so that it applies to all resources. 9. Updated many places that use ALPHA to VCHAR as was suggested on the list. 10. Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure. 11. Added support for timestamp to Speech-Marker header 12. Changed name i. hotword-max-seconds ---> hotword-max-duration ii. hotword-min-seconds ---> hotword-min-duration 13. Change many headers from integer value o float 0.0 - 1.0 14. Recognition-Timeout description clarified. 15. DTMF-Term-Timeout clarified. 16. Recogintion-Mode support 17. DTMF and RFC2833 requirements clarified. 18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource 19. Added Speech-Complete-Timeout, New-audio-Channel and Abort-Verification header fields to the Verification resource. 20. Ver-Buffer-Utterance header field default value is set to "false" 21. Change the Value of "Score" and Verification-Score to 0.0 -1.0 22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods. 23. VER-STOP method updated to support stop Vs abort. --------------040702020305040900060705 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit The MRCPv2 draft has been updated to version -03.

Please find below the change logs for the new draft.


Thanks,
Sarvi

1. Updated Referce numbers to be acurate.

2. In the Introduction   .........................

   The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session.  The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement.

..................

3. Added Security Considerations.

4. Updated with various types and corrections mentioned via email.

5. MRCP-Version  description added the following text, per Klaus's request.

Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0".

6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources.

7.  Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke

8.  Moved Vendor specific headers to be a generic header so that it applies to all resources.

9. Updated many places that use ALPHA to VCHAR as was suggested on the list.

10.  Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure.

11.  Added support for timestamp to Speech-Marker header

12. Changed name            
                            i. hotword-max-seconds ---> hotword-max-duration  
                            ii. hotword-min-seconds ---> hotword-min-duration

13.  Change many headers from integer value o float 0.0 - 1.0

14.  Recognition-Timeout description clarified.

15.  DTMF-Term-Timeout clarified.

16.  Recogintion-Mode support

17. DTMF and RFC2833 requirements clarified.

18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource

19.  Added Speech-Complete-Timeout,  New-audio-Channel and Abort-Verification header fields to the Verification resource.

20. Ver-Buffer-Utterance header field default value is set to "false"

21. Change the Value of  "Score" and Verification-Score to 0.0 -1.0

22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods.

23. VER-STOP method updated to support stop Vs abort.



 --------------040702020305040900060705-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 13 17:39:40 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18032 for ; Thu, 13 May 2004 17:39:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BONm8-0004ui-F8 for speechsc-archive@odin.ietf.org; Thu, 13 May 2004 17:29:56 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DLTu7o018883 for speechsc-archive@odin.ietf.org; Thu, 13 May 2004 17:29:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BONgx-0001np-Np for speechsc-web-archive@optimus.ietf.org; Thu, 13 May 2004 17:24:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15973 for ; Thu, 13 May 2004 17:24:32 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BONgv-0001L3-Gs for speechsc-web-archive@ietf.org; Thu, 13 May 2004 17:24:33 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BONe5-000041-00 for speechsc-web-archive@ietf.org; Thu, 13 May 2004 17:21:38 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BONcS-00076P-04 for speechsc-web-archive@ietf.org; Thu, 13 May 2004 17:19:56 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BONS4-0000qI-DE for speechsc-web-archive@ietf.org; Thu, 13 May 2004 17:09:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOMlH-0005Af-RA; Thu, 13 May 2004 16:24:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOMBp-0005GX-OA for speechsc@optimus.ietf.org; Thu, 13 May 2004 15:48:21 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09414; Thu, 13 May 2004 15:48:19 -0400 (EDT) Message-Id: <200405131948.PAA09414@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: speechsc@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 13 May 2004 15:48:19 -0400 Subject: [Speechsc] I-D ACTION:draft-ietf-speechsc-mrcpv2-03.txt Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --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 Filename : draft-ietf-speechsc-mrcpv2-03.txt Pages : 140 Date : 2004-5-13 This document describes a proposal for a Media Resource Control Protocol Version 2(MRCPv2) and aims to meet the requirements specified in the SPEECHSC working group requirements document. It is based on the Media Resource Control Protocol (MRCP), also called MRCPv1 developed jointly by Cisco Systems, Inc., Nuance Communications, and Speechworks Inc. The MRCPv2 protocol will control media service resources like speech synthesizers, recognizers, signal generators, signal detectors, fax servers etc. over a network. This protocol depends on a session management protocol such as the Session Initiation Protocol (SIP) to establish a separate MRCPv2 control session between the client and the media server. It also depends on SIP to establish the media pipe and associated parameters between the media source or sink and the media server. Once this is done, the MRCPv2 protocol exchange can happen over the control session established above allowing the client to command and control the media processing resources that may exist on the media server. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speechsc-mrcpv2-03.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-03.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-03.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: <2004-5-13160910.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-speechsc-mrcpv2-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-speechsc-mrcpv2-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-5-13160910.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Mon May 17 11:05:19 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27287 for ; Mon, 17 May 2004 11:05:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjdI-0000YI-GO for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:02:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HF2OqS002123 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:02:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjZ9-0008WP-CT for speechsc-web-archive@optimus.ietf.org; Mon, 17 May 2004 10:58:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26890 for ; Mon, 17 May 2004 10:58:03 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPjZ6-00069o-Ri for speechsc-web-archive@ietf.org; Mon, 17 May 2004 10:58:04 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPjYJ-0005lh-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 10:57:15 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPjWW-00059R-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 10:55:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjQQ-0007WV-Gp; Mon, 17 May 2004 10:49:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjOS-00077z-Dw for speechsc@optimus.ietf.org; Mon, 17 May 2004 10:47:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26285 for ; Mon, 17 May 2004 10:47:01 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPjOP-0002Nj-Vr for speechsc@ietf.org; Mon, 17 May 2004 10:47:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPjNa-00023m-00 for speechsc@ietf.org; Mon, 17 May 2004 10:46:10 -0400 Received: from salvelinus.brooktrout.com ([204.176.205.6]) by ietf-mx with esmtp (Exim 4.12) id 1BPjMm-0001jw-00 for speechsc@ietf.org; Mon, 17 May 2004 10:45:20 -0400 Received: from nhmail2.needham.brooktrout.com (nhmail2.eng.brooktrout.com [204.176.205.242]) by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id i4HEf4fB016641 for ; Mon, 17 May 2004 10:41:05 -0400 (EDT) Received: by nhmail2.eng.brooktrout.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 May 2004 10:39:47 -0400 Message-ID: From: Eric Burger To: "'speechsc@ietf.org'" Date: Mon, 17 May 2004 10:39:42 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Speechsc] Media Server or Media Resource Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 I have a form issue, not necessarily a substance issue. Throughout the MRCPv2 document, the "thing that is a server controlled by the MRCPv2 protocol" is called a "Media Server". A Media Server is a device that has a well-defined meaning, in the IETF, 3GPP (MRF), SIP Forum, IPCC, etc. That definition, IMHO, does not really match with "the thing that is a server controlled by the MRCPv2 protocol." In fact, the thing that embodies the accepted version of a Media Server is often a *client* to the MRCPv2 protocol. Would anyone be really put out if we did a 1,$:s/media server/media resource/g throughout the document? Rationale: The document describes the Media RESOURCE Control Protocol, not the Media SERVER Control Protocol. Thoughts? Comments? _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Mon May 17 11:17:16 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27781 for ; Mon, 17 May 2004 11:17:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjnU-00021V-S5 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:12:57 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HFCuwx007773 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:12:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjjs-0001Ww-6N for speechsc-web-archive@optimus.ietf.org; Mon, 17 May 2004 11:09:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27452 for ; Mon, 17 May 2004 11:09:08 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPjjp-00024r-Ih for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:09:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPjiw-0001lQ-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:08:14 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPjiB-0001R5-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:07:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjdt-0000dC-Fd; Mon, 17 May 2004 11:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjZC-0008WT-QO for speechsc@optimus.ietf.org; Mon, 17 May 2004 10:58:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26903 for ; Mon, 17 May 2004 10:58:07 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPjZ9-0006AA-Uu for speechsc@ietf.org; Mon, 17 May 2004 10:58:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPjYM-0005mH-00 for speechsc@ietf.org; Mon, 17 May 2004 10:57:19 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BPjX5-00059Q-00 for speechsc@ietf.org; Mon, 17 May 2004 10:55:59 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Mon, 17 May 2004 10:58:43 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 May 2004 10:55:22 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'speechsc@ietf.org'" Date: Mon, 17 May 2004 10:55:17 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Speechsc] RTP Info Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Hi! In version 03 an optional timestamp was added to the SPEECH-MARKER event. Unfortunately there was no guidance added how it has to be used and it does not address all issues about coordination of RTP playback. To overcome the various synchronisation problems between the client and the server with regard to the speech synthesizer resource, I suggest, to introduce a new header field: RTP-Info This field is used to set RTP-specific parameters. seq: Indicates the sequence number of a RTP packet. rtptime: Indicates the corresponding RTP timestamp. When a CONTROL to jump is issued the CONTROL response message MUST contain the RTP-info header to allow clients to gracefully deal with packets when jumping. In this case the sequence number indicates the last packet before the jump. The client uses this value to differentiate packets that originated before the jump from packets that originated after the jump. The RTP-info header MUST be part of the SPEECH-MARKER event. The sequence number indicates the last packet that was send before the synthesizer resource hit the tag in the speech markup. The RTP timestamp corresponds to the time when the synthesizer resource hit the tag in the speech markup. SPEAK-COMPLETE, STOP response and PAUSE response SHOULD set this header field to indicate the sequence number of the last packet that was initiated by the SPEAK request that was completed, stopped or paused. This enables the client to differentiate packets that belong to different SPEAK requests (if queuing is used). Making use of this header field the client can insert audio clips into the prompt without the need to send actual audio data with the SPEAK request to the server (saves bandwidth!). Syntax: RTP-Info = "RTP-Info" ":" seq ";" rtptime seq = "seq" "=" 1*DIGIT rtptime = "rtptime" "=" 1*DIGIT Klaus _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Mon May 17 11:40:54 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29035 for ; Mon, 17 May 2004 11:40:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkBv-0005Ka-Eu for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:38:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HFcBiC020484 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:38:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPk5z-00045S-KV for speechsc-web-archive@optimus.ietf.org; Mon, 17 May 2004 11:32:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28490 for ; Mon, 17 May 2004 11:32:01 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPk5y-0001qX-Mg for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:32:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPk4y-0001Vt-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:31:02 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPk3t-0000wK-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:29:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjzI-0003Kd-AB; Mon, 17 May 2004 11:25:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjuS-0002ke-6G for speechsc@optimus.ietf.org; Mon, 17 May 2004 11:20:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27983 for ; Mon, 17 May 2004 11:20:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPjuR-0005en-8X for speechsc@ietf.org; Mon, 17 May 2004 11:20:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPjtQ-0005JP-00 for speechsc@ietf.org; Mon, 17 May 2004 11:19:06 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BPjsR-0004fB-00 for speechsc@ietf.org; Mon, 17 May 2004 11:18:04 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Mon, 17 May 2004 11:20:39 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 May 2004 11:17:18 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'Sarvi Shanmugham'" Cc: "IETF SPEECHSC (E-mail)" Subject: RE: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs Date: Mon, 17 May 2004 11:17:17 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43C22.0A514770" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C43C22.0A514770 Content-Type: text/plain; charset="iso-8859-1" Hi Sarvi, many thanks for assembling the new version! There is a "copy-and-past" error: The description of the Completion Reason header field for the recognizer, recorder and verifier resource does not fit. Regards, Klaus -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Donnerstag, 13. Mai 2004 21:58 To: IETF SPEECHSC (E-mail) Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs The MRCPv2 draft has been updated to version -03. Please find below the change logs for the new draft. Thanks, Sarvi 1. Updated Referce numbers to be acurate. 2. In the Introduction ......................... The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session. The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement. .................. 3. Added Security Considerations. 4. Updated with various types and corrections mentioned via email. 5. MRCP-Version description added the following text, per Klaus's request. Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0". 6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources. 7. Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke 8. Moved Vendor specific headers to be a generic header so that it applies to all resources. 9. Updated many places that use ALPHA to VCHAR as was suggested on the list. 10. Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure. 11. Added support for timestamp to Speech-Marker header 12. Changed name i. hotword-max-seconds ---> hotword-max-duration ii. hotword-min-seconds ---> hotword-min-duration 13. Change many headers from integer value o float 0.0 - 1.0 14. Recognition-Timeout description clarified. 15. DTMF-Term-Timeout clarified. 16. Recogintion-Mode support 17. DTMF and RFC2833 requirements clarified. 18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource 19. Added Speech-Complete-Timeout, New-audio-Channel and Abort-Verification header fields to the Verification resource. 20. Ver-Buffer-Utterance header field default value is set to "false" 21. Change the Value of "Score" and Verification-Score to 0.0 -1.0 22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods. 23. VER-STOP method updated to support stop Vs abort. ------_=_NextPart_001_01C43C22.0A514770 Content-Type: text/html; charset="iso-8859-1"
Hi Sarvi,
 
many thanks for assembling the new version!
 
There is a "copy-and-past" error: The description of the Completion Reason header field for the recognizer, recorder and verifier resource does not fit.
 
Regards,
Klaus 
-----Original Message-----
From: Sarvi Shanmugham [mailto:sarvi@cisco.com]
Sent: Donnerstag, 13. Mai 2004 21:58
To: IETF SPEECHSC (E-mail)
Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs

The MRCPv2 draft has been updated to version -03.

Please find below the change logs for the new draft.


Thanks,
Sarvi

1. Updated Referce numbers to be acurate.

<!--[if !supportEmptyParas]-->2. In the Introduction   .........................<!--[endif]-->

   The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session.  The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement.

..................

3. Added Security Considerations.

4. Updated with various types and corrections mentioned via email.

5. MRCP-Version  description added the following text, per Klaus's request.

Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0".

6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources.

7.  Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke

8.  Moved Vendor specific headers to be a generic header so that it applies to all resources.

9. Updated many places that use ALPHA to VCHAR as was suggested on the list.

10.  Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure.

11.  Added support for timestamp to Speech-Marker header

12. Changed name            
                            i. hotword-max-seconds ---> hotword-max-duration  
                            ii. hotword-min-seconds ---> hotword-min-duration

13.  Change many headers from integer value o float 0.0 - 1.0

14.  Recognition-Timeout description clarified.

15.  DTMF-Term-Timeout clarified.

16.  Recogintion-Mode support

17. DTMF and RFC2833 requirements clarified.

18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource

19.  Added Speech-Complete-Timeout,  New-audio-Channel and Abort-Verification header fields to the Verification resource.

20. Ver-Buffer-Utterance header field default value is set to "false"

21. Change the Value of  "Score" and Verification-Score to 0.0 -1.0

22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods.

23. VER-STOP method updated to support stop Vs abort.



------_=_NextPart_001_01C43C22.0A514770-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Mon May 17 12:02:16 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01020 for ; Mon, 17 May 2004 12:02:15 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkTR-0007mK-5C for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:56:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HFuH2A029899 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:56:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkQN-0006yU-OY for speechsc-web-archive@optimus.ietf.org; Mon, 17 May 2004 11:53:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00237 for ; Mon, 17 May 2004 11:53:05 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPkQM-0001KM-JD for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:53:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPkPO-00010N-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:52:06 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPkOT-0000g6-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:51:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkCm-0005Tz-Ts; Mon, 17 May 2004 11:39:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPk47-0003tW-DK for speechsc@optimus.ietf.org; Mon, 17 May 2004 11:30:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28413 for ; Mon, 17 May 2004 11:30:05 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPk46-0001Bc-IC for speechsc@ietf.org; Mon, 17 May 2004 11:30:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPk34-0000pm-00 for speechsc@ietf.org; Mon, 17 May 2004 11:29:02 -0400 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BPk24-0000Cd-00 for speechsc@ietf.org; Mon, 17 May 2004 11:28:00 -0400 Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4HFRPC1014335; Mon, 17 May 2004 08:27:26 -0700 (PDT) Received: from [10.32.245.150] (stealth-10-32-245-150.cisco.com [10.32.245.150]) by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with SMTP id AOZ76980; Mon, 17 May 2004 08:27:25 -0700 (PDT) Date: Mon, 17 May 2004 11:27:19 -0400 From: "David R. Oran" To: "Reifenrath, Klaus" , "'speechsc@ietf.org'" Subject: Re: [Speechsc] RTP Info Message-ID: In-Reply-To: References: X-Mailer: Mulberry/3.1.3 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========EFACE4ACA6A6F6242D30==========" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 --==========EFACE4ACA6A6F6242D30========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I certainly see how one may want to control the RTP playout positioning by=20 synchronizing via an RTP timestamp, but I have grave misgivings about=20 letting sequence number information leak between the media plane and the=20 control plane. The reasons are multiple: a) RTP playout is controlled by the timestamp, not the sequence number b) sequence numbers will be complicated to handle if FEC is in use c) It's hard to position correctly if there are lost packets. As far as I know, it may be best to stay away entirely from direct usage of = RTP media state and instead synchronize only based on SSRC and NTP=20 realtime. That would also allow synchronization of audio even in the=20 presence of an associated video stream. Dave. --On Monday, May 17, 2004 10:55 AM -0400 "Reifenrath, Klaus"=20 wrote: > Hi! > > In version 03 an optional timestamp was added to the SPEECH-MARKER event. > Unfortunately there was no guidance added how it has to be used and it > does not address all issues about coordination of RTP playback. To > overcome the various synchronisation problems between the client and the > server with regard to the speech synthesizer resource, I suggest, to > introduce a new header field: > > RTP-Info > This field is used to set RTP-specific parameters. > seq: Indicates the sequence number of a RTP packet. > rtptime: Indicates the corresponding RTP timestamp. > > When a CONTROL to jump is issued the CONTROL response message MUST = contain > the RTP-info header to allow clients to gracefully deal with packets when > jumping. In this case the sequence number indicates the last packet = before > the jump. The client uses this value to differentiate packets that > originated before the jump from packets that originated after the jump. > > The RTP-info header MUST be part of the SPEECH-MARKER event. The sequence > number indicates the last packet that was send before the synthesizer > resource hit the tag in the speech markup. The RTP timestamp corresponds > to the time when the synthesizer resource hit the tag in the speech > markup. > > SPEAK-COMPLETE, STOP response and PAUSE response SHOULD set this header > field to indicate the sequence number of the last packet that was > initiated by the SPEAK request that was completed, stopped or paused. > This enables the client to differentiate packets that belong to different > SPEAK requests (if queuing is used). > > Making use of this header field the client can insert audio clips into = the > prompt without the need to send actual audio data with the SPEAK request > to the server (saves bandwidth!). > > Syntax: > > RTP-Info =3D "RTP-Info" ":" seq ";" rtptime > seq =3D "seq" "=3D" 1*DIGIT > rtptime =3D "rtptime" "=3D" 1*DIGIT > > > Klaus > > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www1.ietf.org/mailman/listinfo/speechsc --==========EFACE4ACA6A6F6242D30========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFAqNnYjWaEtlTdKuYRAlt8AJ46BJmAe1ftrnUW8D5waX+cRJW8+wCbBCpv lEBRXbERkB8eO3KgGp1j/3Q= =iyF0 -----END PGP SIGNATURE----- --==========EFACE4ACA6A6F6242D30==========-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Mon May 17 12:02:36 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01058 for ; Mon, 17 May 2004 12:02:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkTU-0007nm-FX for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:56:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HFuK4H029985 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 11:56:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkRO-00077B-Ee for speechsc-web-archive@optimus.ietf.org; Mon, 17 May 2004 11:54:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00304 for ; Mon, 17 May 2004 11:54:08 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPkRN-0001f9-9r for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:54:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPkQT-0001L6-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:53:15 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPkPc-00011N-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 11:52:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPkCn-0005U7-5b; Mon, 17 May 2004 11:39:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPk4D-0003tt-Dk for speechsc@optimus.ietf.org; Mon, 17 May 2004 11:30:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28424 for ; Mon, 17 May 2004 11:30:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPk4C-0001CL-IF for speechsc@ietf.org; Mon, 17 May 2004 11:30:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPk3B-0000qt-00 for speechsc@ietf.org; Mon, 17 May 2004 11:29:10 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BPk2N-0000Cj-00 for speechsc@ietf.org; Mon, 17 May 2004 11:28:19 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Mon, 17 May 2004 11:31:00 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 May 2004 11:27:39 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'Sarvi Shanmugham'" Cc: "IETF SPEECHSC (E-mail)" Subject: RE: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs Date: Mon, 17 May 2004 11:27:37 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43C23.7BBC5AC0" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_FONTCOLOR_BLUE, HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C43C23.7BBC5AC0 Content-Type: text/plain; charset="iso-8859-1" Hi Sarvi, regarding change 12): The description is still contradictory with regard to the dimension unit. Regards, Klaus -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Donnerstag, 13. Mai 2004 21:58 To: IETF SPEECHSC (E-mail) Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs The MRCPv2 draft has been updated to version -03. Please find below the change logs for the new draft. Thanks, Sarvi 1. Updated Referce numbers to be acurate. 2. In the Introduction ......................... The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session. The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement. .................. 3. Added Security Considerations. 4. Updated with various types and corrections mentioned via email. 5. MRCP-Version description added the following text, per Klaus's request. Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0". 6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources. 7. Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke 8. Moved Vendor specific headers to be a generic header so that it applies to all resources. 9. Updated many places that use ALPHA to VCHAR as was suggested on the list. 10. Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure. 11. Added support for timestamp to Speech-Marker header 12. Changed name i. hotword-max-seconds ---> hotword-max-duration ii. hotword-min-seconds ---> hotword-min-duration 13. Change many headers from integer value o float 0.0 - 1.0 14. Recognition-Timeout description clarified. 15. DTMF-Term-Timeout clarified. 16. Recogintion-Mode support 17. DTMF and RFC2833 requirements clarified. 18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource 19. Added Speech-Complete-Timeout, New-audio-Channel and Abort-Verification header fields to the Verification resource. 20. Ver-Buffer-Utterance header field default value is set to "false" 21. Change the Value of "Score" and Verification-Score to 0.0 -1.0 22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods. 23. VER-STOP method updated to support stop Vs abort. ------_=_NextPart_001_01C43C23.7BBC5AC0 Content-Type: text/html; charset="iso-8859-1"
Hi Sarvi,
 
regarding change 12): The description is still contradictory with regard to the dimension unit.
 
Regards,
Klaus
-----Original Message-----
From: Sarvi Shanmugham [mailto:sarvi@cisco.com]
Sent: Donnerstag, 13. Mai 2004 21:58
To: IETF SPEECHSC (E-mail)
Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs

The MRCPv2 draft has been updated to version -03.

Please find below the change logs for the new draft.


Thanks,
Sarvi

1. Updated Referce numbers to be acurate.

<!--[if !supportEmptyParas]-->2. In the Introduction   .........................<!--[endif]-->

   The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session.  The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement.

..................

3. Added Security Considerations.

4. Updated with various types and corrections mentioned via email.

5. MRCP-Version  description added the following text, per Klaus's request.

Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0".

6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources.

7.  Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke

8.  Moved Vendor specific headers to be a generic header so that it applies to all resources.

9. Updated many places that use ALPHA to VCHAR as was suggested on the list.

10.  Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure.

11.  Added support for timestamp to Speech-Marker header

12. Changed name            
                            i. hotword-max-seconds ---> hotword-max-duration  
                            ii. hotword-min-seconds ---> hotword-min-duration

13.  Change many headers from integer value o float 0.0 - 1.0

14.  Recognition-Timeout description clarified.

15.  DTMF-Term-Timeout clarified.

16.  Recogintion-Mode support

17. DTMF and RFC2833 requirements clarified.

18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource

19.  Added Speech-Complete-Timeout,  New-audio-Channel and Abort-Verification header fields to the Verification resource.

20. Ver-Buffer-Utterance header field default value is set to "false"

21. Change the Value of  "Score" and Verification-Score to 0.0 -1.0

22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods.

23. VER-STOP method updated to support stop Vs abort.



------_=_NextPart_001_01C43C23.7BBC5AC0-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Mon May 17 13:08:30 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05798 for ; Mon, 17 May 2004 13:08:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPlVu-0003AF-O0 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 13:02:54 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HH2sX3012147 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 13:02:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPlGm-0001Ob-Eu for speechsc-web-archive@optimus.ietf.org; Mon, 17 May 2004 12:47:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04296 for ; Mon, 17 May 2004 12:47:13 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPlGk-00051c-Qb for speechsc-web-archive@ietf.org; Mon, 17 May 2004 12:47:14 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPlFs-0004gw-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 12:46:20 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPlFC-0004My-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 12:45:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPl13-0006cC-0e; Mon, 17 May 2004 12:31:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPksw-0004z2-Kf for speechsc@optimus.ietf.org; Mon, 17 May 2004 12:22:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02480 for ; Mon, 17 May 2004 12:22:35 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPksv-0003vK-6q for speechsc@ietf.org; Mon, 17 May 2004 12:22:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPkrW-0003S3-00 for speechsc@ietf.org; Mon, 17 May 2004 12:21:10 -0400 Received: from mx2.scansoft.com ([198.71.64.82]) by ietf-mx with esmtp (Exim 4.12) id 1BPkqO-0002ih-00 for speechsc@ietf.org; Mon, 17 May 2004 12:20:01 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx2 with trend_isnt_name_B; Mon, 17 May 2004 12:19:27 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Mon, 17 May 2004 12:19:07 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'David R. Oran'" Cc: "'speechsc@ietf.org'" Subject: RE: [Speechsc] RTP Info Date: Mon, 17 May 2004 12:19:06 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Hi Dave, I share your concerns, but as it is pointed out in RFC 2326 section 12.33 (RTP-Info header field of RTSP) RTCP is not sufficient to generate a mapping from RTP timestamps to NPT. Furthermore the mapping from RTP timestamps to NTP timestamps is only available after some time. Therefore I think we need the RTP timestamp. The sequence number might be superfluous. Regards, Klaus -----Original Message----- From: David R. Oran [mailto:oran@cisco.com] Sent: Montag, 17. Mai 2004 17:27 To: Reifenrath, Klaus; 'speechsc@ietf.org' Subject: Re: [Speechsc] RTP Info I certainly see how one may want to control the RTP playout positioning by synchronizing via an RTP timestamp, but I have grave misgivings about letting sequence number information leak between the media plane and the control plane. The reasons are multiple: a) RTP playout is controlled by the timestamp, not the sequence number b) sequence numbers will be complicated to handle if FEC is in use c) It's hard to position correctly if there are lost packets. As far as I know, it may be best to stay away entirely from direct usage of RTP media state and instead synchronize only based on SSRC and NTP realtime. That would also allow synchronization of audio even in the presence of an associated video stream. Dave. --On Monday, May 17, 2004 10:55 AM -0400 "Reifenrath, Klaus" wrote: > Hi! > > In version 03 an optional timestamp was added to the SPEECH-MARKER event. > Unfortunately there was no guidance added how it has to be used and it > does not address all issues about coordination of RTP playback. To > overcome the various synchronisation problems between the client and the > server with regard to the speech synthesizer resource, I suggest, to > introduce a new header field: > > RTP-Info > This field is used to set RTP-specific parameters. > seq: Indicates the sequence number of a RTP packet. > rtptime: Indicates the corresponding RTP timestamp. > > When a CONTROL to jump is issued the CONTROL response message MUST contain > the RTP-info header to allow clients to gracefully deal with packets when > jumping. In this case the sequence number indicates the last packet before > the jump. The client uses this value to differentiate packets that > originated before the jump from packets that originated after the jump. > > The RTP-info header MUST be part of the SPEECH-MARKER event. The sequence > number indicates the last packet that was send before the synthesizer > resource hit the tag in the speech markup. The RTP timestamp corresponds > to the time when the synthesizer resource hit the tag in the speech > markup. > > SPEAK-COMPLETE, STOP response and PAUSE response SHOULD set this header > field to indicate the sequence number of the last packet that was > initiated by the SPEAK request that was completed, stopped or paused. > This enables the client to differentiate packets that belong to different > SPEAK requests (if queuing is used). > > Making use of this header field the client can insert audio clips into the > prompt without the need to send actual audio data with the SPEAK request > to the server (saves bandwidth!). > > Syntax: > > RTP-Info = "RTP-Info" ":" seq ";" rtptime > seq = "seq" "=" 1*DIGIT > rtptime = "rtptime" "=" 1*DIGIT > > > Klaus > > _______________________________________________ > 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 exim@www1.ietf.org Mon May 17 19:01:22 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11570 for ; Mon, 17 May 2004 19:01:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPr4k-00051R-Mh for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 18:59:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HMxEDX019306 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 18:59:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPqfo-0006RL-Ih for speechsc-web-archive@optimus.ietf.org; Mon, 17 May 2004 18:33:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09864 for ; Mon, 17 May 2004 18:33:23 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPqfk-0000XI-Vo for speechsc-web-archive@ietf.org; Mon, 17 May 2004 18:33:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPqei-00006y-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 18:32:21 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPqde-0007NQ-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 18:31:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPqQr-0005ZB-AQ; Mon, 17 May 2004 18:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPjmc-0001oK-KL for speechsc@optimus.ietf.org; Mon, 17 May 2004 11:12:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27554 for ; Mon, 17 May 2004 11:12:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPjmb-000327-Pg for speechsc@ietf.org; Mon, 17 May 2004 11:12:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPjlp-0002jI-00 for speechsc@ietf.org; Mon, 17 May 2004 11:11:13 -0400 Received: from [216.248.178.195] (helo=www.vocalocity.net) by ietf-mx with esmtp (Exim 4.12) id 1BPjl2-0002Q8-00 for Speechsc@ietf.org; Mon, 17 May 2004 11:10:24 -0400 Received: from vocalocity.net (unknown [10.0.100.104]) by www.vocalocity.net (Postfix) with ESMTP id 72785A441; Mon, 17 May 2004 11:10:24 -0400 (EDT) Message-ID: <40A8D5DE.9040100@vocalocity.net> Date: Mon, 17 May 2004 11:10:22 -0400 From: Jeff Haynie User-Agent: Mozilla Thunderbird 0.5+ (Windows/20040326) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit That's funny - I myself have struggled with the same term and would be much more in favor of "media resource". Jeff Eric Burger wrote: > >I have a form issue, not necessarily a substance issue. > >Throughout the MRCPv2 document, the "thing that is a server controlled by >the MRCPv2 protocol" is called a "Media Server". > >A Media Server is a device that has a well-defined meaning, in the IETF, >3GPP (MRF), SIP Forum, IPCC, etc. > >That definition, IMHO, does not really match with "the thing that is a >server controlled by the MRCPv2 protocol." In fact, the thing that embodies >the accepted version of a Media Server is often a *client* to the MRCPv2 >protocol. > >Would anyone be really put out if we did a 1,$:s/media server/media >resource/g throughout the document? > >Rationale: The document describes the Media RESOURCE Control Protocol, not >the Media SERVER Control Protocol. > > > >Thoughts? Comments? > >_______________________________________________ >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 exim@www1.ietf.org Mon May 17 19:51:16 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14135 for ; Mon, 17 May 2004 19:51:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPrjZ-0004AY-WC for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 19:41:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HNfP1g016010 for speechsc-archive@odin.ietf.org; Mon, 17 May 2004 19:41:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPrgx-0002vz-0U for speechsc-web-archive@optimus.ietf.org; Mon, 17 May 2004 19:38:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13529 for ; Mon, 17 May 2004 19:38:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPrgv-00004R-A4 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 19:38:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPrg6-0007V0-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 19:37:51 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPrf7-00077L-00 for speechsc-web-archive@ietf.org; Mon, 17 May 2004 19:36:49 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPrVe-0006pQ-Ul; Mon, 17 May 2004 19:27:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPrQG-0004rL-0h for speechsc@optimus.ietf.org; Mon, 17 May 2004 19:21:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12416 for ; Mon, 17 May 2004 19:21:27 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPrQE-0001fc-DM for speechsc@ietf.org; Mon, 17 May 2004 19:21:26 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPrPD-0001Je-00 for speechsc@ietf.org; Mon, 17 May 2004 19:20:23 -0400 Received: from cerbrus.convedia.com ([216.129.93.50]) by ietf-mx with esmtp (Exim 4.12) id 1BPrOL-0000fR-00 for Speechsc@ietf.org; Mon, 17 May 2004 19:19:29 -0400 Received: from mailhost.convedia.com (ladon [192.168.208.15]) by cerbrus.convedia.com (8.12.9/8.12.9) with ESMTP id i4HN75Ev005905; Mon, 17 May 2004 16:07:05 -0700 (PDT) Received: from laptop33 ([192.168.209.5]) by mailhost.convedia.com (8.12.9/8.12.9) with SMTP id i4HNIpfc020311; Mon, 17 May 2004 16:18:52 -0700 (PDT) From: "Garland Sharratt" To: "Eric Burger" Cc: Subject: RE: [Speechsc] Media Server or Media Resource Date: Mon, 17 May 2004 16:18:52 -0700 Keywords: .xbulk, .aa Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <40A8D5DE.9040100@vocalocity.net> x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Eric, I concur. Using the term "media server" for MRCPv2 muddies the waters, I think, and implies the two things are the same whereas they are not. Garland -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Jeff Haynie Sent: Monday, May 17, 2004 08:10 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource That's funny - I myself have struggled with the same term and would be much more in favor of "media resource". Jeff Eric Burger wrote: > >I have a form issue, not necessarily a substance issue. > >Throughout the MRCPv2 document, the "thing that is a server controlled by >the MRCPv2 protocol" is called a "Media Server". > >A Media Server is a device that has a well-defined meaning, in the IETF, >3GPP (MRF), SIP Forum, IPCC, etc. > >That definition, IMHO, does not really match with "the thing that is a >server controlled by the MRCPv2 protocol." In fact, the thing that embodies >the accepted version of a Media Server is often a *client* to the MRCPv2 >protocol. > >Would anyone be really put out if we did a 1,$:s/media server/media >resource/g throughout the document? > >Rationale: The document describes the Media RESOURCE Control Protocol, not >the Media SERVER Control Protocol. > > > >Thoughts? Comments? > >_______________________________________________ >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 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Tue May 18 06:05:44 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00066 for ; Tue, 18 May 2004 06:05:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ1QV-00084c-HJ for speechsc-archive@odin.ietf.org; Tue, 18 May 2004 06:02:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IA2NVd031035 for speechsc-archive@odin.ietf.org; Tue, 18 May 2004 06:02:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ1MR-0006zY-8X for speechsc-web-archive@optimus.ietf.org; Tue, 18 May 2004 05:58:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29625 for ; Tue, 18 May 2004 05:58:07 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQ1MN-0003Il-LS for speechsc-web-archive@ietf.org; Tue, 18 May 2004 05:58:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQ1LQ-0002sZ-00 for speechsc-web-archive@ietf.org; Tue, 18 May 2004 05:57:09 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQ1Kg-0002TP-00 for speechsc-web-archive@ietf.org; Tue, 18 May 2004 05:56:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ1Be-00054Y-09; Tue, 18 May 2004 05:47:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ17t-0004Di-PX for speechsc@optimus.ietf.org; Tue, 18 May 2004 05:43:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28658 for ; Tue, 18 May 2004 05:43:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQ17q-0004iY-Bz for speechsc@ietf.org; Tue, 18 May 2004 05:43:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQ16u-0004J9-00 for speechsc@ietf.org; Tue, 18 May 2004 05:42:08 -0400 Received: from eagle.ericsson.se ([193.180.251.53]) by ietf-mx with esmtp (Exim 4.12) id 1BQ15w-0003tS-00 for speechsc@ietf.org; Tue, 18 May 2004 05:41:08 -0400 Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118]) by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i4I9f9Ah022910 for ; Tue, 18 May 2004 11:41:09 +0200 Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Tue, 18 May 2004 11:41:09 +0200 Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.60]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id KM9QH91Z; Tue, 18 May 2004 11:41:09 +0200 Message-ID: <40A9DA35.5080600@ericsson.com> Date: Tue, 18 May 2004 11:41:09 +0200 X-Sybari-Trust: 63a1fa3b 08d63d2e 4c643c65 00000138 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: sv, en-us, en MIME-Version: 1.0 To: "Reifenrath, Klaus" CC: "'speechsc@ietf.org'" Subject: Re: [Speechsc] RTP Info References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 May 2004 09:41:09.0509 (UTC) FILETIME=[3FCC5350:01C43CBC] Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Independently of how you decided the if this is needed or not. The RTP-Info syntax in RTSP is erroneous and missing an important part to be complete. It does need to contain a SSRC. If you are going to adopt this header I would recommend that you redefine it in the following way: Syntax: RTP-Info = "RTP-Info" ":" rtp-sync-point *("," rtp-sync-point) rtp-sync-point = source-id ";" rtptime [";" seq] source-id = "ssrc" "=" 8*8HEX seq = "seq" "=" 1*DIGIT rtptime = "rtptime" "=" 1*DIGIT The only thing one might need to consider if the SSRC is always easily available. If not then the source-id field could be defined as optional. However it is probably important to ensure that sync info from multiple sources in the same RTP session can be properly handled. Cheers Magnus > Reifenrath, Klaus wrote: > Hi! > > In version 03 an optional timestamp was added to the SPEECH-MARKER > event. > Unfortunately there was no guidance added how it has to be used and it > does > not address all issues about coordination of RTP playback. To overcome > the > various synchronisation problems between the client and the server with > regard to the speech synthesizer resource, I suggest, to introduce a new > header field: > > RTP-Info > This field is used to set RTP-specific parameters. > seq: Indicates the sequence number of a RTP packet. > rtptime: Indicates the corresponding RTP timestamp. > > When a CONTROL to jump is issued the CONTROL response message MUST > contain > the RTP-info header to allow clients to gracefully deal with packets > when > jumping. In this case the sequence number indicates the last packet > before > the jump. The client uses this value to differentiate packets that > originated before the jump from packets that originated after the jump. > > The RTP-info header MUST be part of the SPEECH-MARKER event. The > sequence > number indicates the last packet that was send before the synthesizer > resource hit the tag in the speech markup. The RTP timestamp corresponds > to > the time when the synthesizer resource hit the tag in the speech markup. > > SPEAK-COMPLETE, STOP response and PAUSE response SHOULD set this header > field to indicate the sequence number of the last packet that was > initiated > by the SPEAK request that was completed, stopped or paused. This enables > the > client to differentiate packets that belong to different SPEAK requests > (if > queuing is used). > > Making use of this header field the client can insert audio clips into > the > prompt without the need to send actual audio data with the SPEAK request > to > the server (saves bandwidth!). > > Syntax: > > RTP-Info = "RTP-Info" ":" seq ";" rtptime > seq = "seq" "=" 1*DIGIT > rtptime = "rtptime" "=" 1*DIGIT > > > Klaus > > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www1.ietf.org/mailman/listinfo/speechsc > -- Magnus Westerlund Multimedia Technologies, Ericsson Research EAB/TVA/A ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Tue May 18 20:28:06 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00572 for ; Tue, 18 May 2004 20:28:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQEuu-0008HI-HI for speechsc-archive@odin.ietf.org; Tue, 18 May 2004 20:26:40 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J0QeUQ031813 for speechsc-archive@odin.ietf.org; Tue, 18 May 2004 20:26:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQEdE-0005XP-Pq for speechsc-web-archive@optimus.ietf.org; Tue, 18 May 2004 20:08:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29743 for ; Tue, 18 May 2004 20:08:23 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQEdC-00029J-Rg for speechsc-web-archive@ietf.org; Tue, 18 May 2004 20:08:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQEcM-00025c-00 for speechsc-web-archive@ietf.org; Tue, 18 May 2004 20:07:31 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BQEbq-00021G-00 for speechsc-web-archive@ietf.org; Tue, 18 May 2004 20:06:58 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BQEbr-0005Xt-Vp for speechsc-web-archive@ietf.org; Tue, 18 May 2004 20:07:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQEVE-0003a0-Fs; Tue, 18 May 2004 20:00:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQEMn-0002cZ-LQ for speechsc@optimus.ietf.org; Tue, 18 May 2004 19:51:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28862 for ; Tue, 18 May 2004 19:51:24 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQEMl-0000pH-Pr for speechsc@ietf.org; Tue, 18 May 2004 19:51:23 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQEMF-0000kb-00 for speechsc@ietf.org; Tue, 18 May 2004 19:50:52 -0400 Received: from vtg-um-e2k1.cisco.com ([171.70.93.55] helo=vtg-um-e2k1.sj21ad.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BQELF-0000ZP-00 for Speechsc@ietf.org; Tue, 18 May 2004 19:49:49 -0400 Received: from cisco.com ([10.32.130.132]) by vtg-um-e2k1.sj21ad.cisco.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 18 May 2004 16:49:19 -0700 Message-ID: <40AAA0FE.2010804@cisco.com> Date: Tue, 18 May 2004 16:49:18 -0700 From: Sarvi Shanmugham Organization: Cisco Systems Inc. User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garland Sharratt CC: Eric Burger , Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------040408040206020006080002" X-OriginalArrivalTime: 18 May 2004 23:49:19.0490 (UTC) FILETIME=[BC972E20:01C43D32] Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE, HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. --------------040408040206020006080002 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit This is fine by me. And I haven't heard any opposition so far. I will make the necessary edits. Sarvi Garland Sharratt wrote: >Eric, I concur. Using the term "media server" for MRCPv2 muddies the >waters, I think, and implies the two things are the same whereas they are >not. > >Garland > >-----Original Message----- >From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >Of Jeff Haynie >Sent: Monday, May 17, 2004 08:10 >To: Eric Burger >Cc: Speechsc@ietf.org >Subject: Re: [Speechsc] Media Server or Media Resource > > >That's funny - I myself have struggled with the same term and would be >much more in favor of "media resource". > >Jeff > >Eric Burger wrote: > > > >> >>I have a form issue, not necessarily a substance issue. >> >>Throughout the MRCPv2 document, the "thing that is a server controlled by >>the MRCPv2 protocol" is called a "Media Server". >> >>A Media Server is a device that has a well-defined meaning, in the IETF, >>3GPP (MRF), SIP Forum, IPCC, etc. >> >>That definition, IMHO, does not really match with "the thing that is a >>server controlled by the MRCPv2 protocol." In fact, the thing that >> >> >embodies > > >>the accepted version of a Media Server is often a *client* to the MRCPv2 >>protocol. >> >>Would anyone be really put out if we did a 1,$:s/media server/media >>resource/g throughout the document? >> >>Rationale: The document describes the Media RESOURCE Control Protocol, not >>the Media SERVER Control Protocol. >> >> >> >>Thoughts? Comments? >> >>_______________________________________________ >>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 > > >_______________________________________________ >Speechsc mailing list >Speechsc@ietf.org >https://www1.ietf.org/mailman/listinfo/speechsc > > > --------------040408040206020006080002 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit This is fine by me. And I haven't heard any opposition so far.
 I will make the necessary edits.

Sarvi
Garland Sharratt wrote: 
Eric, I concur.  Using the term "media server" for MRCPv2 muddies the
waters, I think, and implies the two things are the same whereas they are
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would be
much more in favor of "media resource".

Jeff

Eric Burger wrote:

  
<ChairHat state="off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server controlled by
the MRCPv2 protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the IETF,
3GPP (MRF), SIP Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that is a
server controlled by the MRCPv2 protocol."  In fact, the thing that
    
embodies
  
the accepted version of a Media Server is often a *client* to the MRCPv2
protocol.

Would anyone be really put out if we did a 1,$:s/media server/media
resource/g throughout the document?

Rationale: The document describes the Media RESOURCE Control Protocol, not
the Media SERVER Control Protocol.

</ChairHat>

Thoughts?  Comments?

_______________________________________________
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


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

--------------040408040206020006080002-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed May 19 06:06:50 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27203 for ; Wed, 19 May 2004 06:06:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQNtj-0002e9-7n for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 06:02:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JA23Yf010174 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 06:02:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQNje-0008MY-Ky for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 05:51:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25917 for ; Wed, 19 May 2004 05:51:35 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQNjb-0006xA-1D for speechsc-web-archive@ietf.org; Wed, 19 May 2004 05:51:35 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQNib-0006mq-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 05:50:35 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQNhg-0006ci-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 05:49:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQNLq-0001dh-2o; Wed, 19 May 2004 05:27:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQN52-0007Qs-NR for speechsc@optimus.ietf.org; Wed, 19 May 2004 05:09:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22785 for ; Wed, 19 May 2004 05:09:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQN4z-0007AE-Bu for speechsc@ietf.org; Wed, 19 May 2004 05:09:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQN46-00071m-00 for speechsc@ietf.org; Wed, 19 May 2004 05:08:44 -0400 Received: from mx2.scansoft.com ([198.71.64.82]) by ietf-mx with esmtp (Exim 4.12) id 1BQN3P-0006lJ-00 for Speechsc@ietf.org; Wed, 19 May 2004 05:07:59 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx2 with trend_isnt_name_B; Wed, 19 May 2004 05:07:36 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Wed, 19 May 2004 05:07:15 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'Sarvi Shanmugham'" , Eric Burger Cc: Speechsc@ietf.org Subject: RE: [Speechsc] Media Server or Media Resource Date: Wed, 19 May 2004 05:07:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43D80.AAFDE250" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C43D80.AAFDE250 Content-Type: text/plain; charset="iso-8859-1" Hi Eric and Sarvi, after some internal discussions I prefer to stay with the term "media server"! In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that was referenced in the speechsc requirements document) the following definition of a media server can be found (section 3 on page 3): "Media servers are devices that perform media processing on real-time packet media." According to this definition the MRCP server is a media server (and not the platform that uses MRCP servers for media processing, which becomes a media proxy). In a network architecture that includes MRCP servers there might be other media servers. Could someone point me to the documents of the IETF, 3GPP, ... where I can find their definition of a media server. The term "media server" is used fairly often (especially in product brochures), but it seems to be difficult to find precise definitions. Thanks, Klaus -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Mittwoch, 19. Mai 2004 01:49 To: Garland Sharratt Cc: Eric Burger; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource This is fine by me. And I haven't heard any opposition so far. I will make the necessary edits. Sarvi Garland Sharratt wrote: Eric, I concur. Using the term "media server" for MRCPv2 muddies the waters, I think, and implies the two things are the same whereas they are not. Garland -----Original Message----- From: speechsc-admin@ietf.org [ mailto:speechsc-admin@ietf.org ]On Behalf Of Jeff Haynie Sent: Monday, May 17, 2004 08:10 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource That's funny - I myself have struggled with the same term and would be much more in favor of "media resource". Jeff Eric Burger wrote: I have a form issue, not necessarily a substance issue. Throughout the MRCPv2 document, the "thing that is a server controlled by the MRCPv2 protocol" is called a "Media Server". A Media Server is a device that has a well-defined meaning, in the IETF, 3GPP (MRF), SIP Forum, IPCC, etc. That definition, IMHO, does not really match with "the thing that is a server controlled by the MRCPv2 protocol." In fact, the thing that embodies the accepted version of a Media Server is often a *client* to the MRCPv2 protocol. Would anyone be really put out if we did a 1,$:s/media server/media resource/g throughout the document? Rationale: The document describes the Media RESOURCE Control Protocol, not the Media SERVER Control Protocol. Thoughts? Comments? _______________________________________________ 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 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc ------_=_NextPart_001_01C43D80.AAFDE250 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi = Eric and=20 Sarvi,
 
after = some internal=20 discussions I prefer to stay with the term "media = server"!
 
In=20 draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that = was=20 referenced in the speechsc requirements document) the following = definition of a=20 media server can be found (section 3 on page = 3):
"Media servers are=20 devices that perform media processing on real-time packet=20 media."
According to this=20 definition the MRCP server is a media server (and not the = platform=20 that uses MRCP servers for media processing, which becomes a media = proxy). 
In a = network=20 architecture that includes MRCP servers there might be other media=20 servers.
 
Could = someone point=20 me to the documents of the IETF, 3GPP, ... where I can find their = definition of=20 a media server. The term "media server" is used fairly often = (especially in=20 product brochures), but it seems to be difficult to find precise=20 definitions.
 
Thanks,
Klaus
 
 
-----Original Message-----
From: Sarvi Shanmugham=20 [mailto:sarvi@cisco.com]
Sent: Mittwoch, 19. Mai 2004=20 01:49
To: Garland Sharratt
Cc: Eric Burger;=20 Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or = Media=20 Resource

This is fine by me. And I haven't heard = any=20 opposition so far.
 I will make the necessary=20 edits.

Sarvi
Garland Sharratt wrote:=20 
Eric, I concur.  Using the term "media =
server" for MRCPv2 muddies the
waters, I think, and implies the two things are the same whereas they =
are
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would be
much more in favor of "media resource".

Jeff

Eric Burger wrote:

  
<ChairHat =
state=3D"off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server controlled =
by
the MRCPv2 protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the =
IETF,
3GPP (MRF), SIP Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that is a
server controlled by the MRCPv2 protocol."  In fact, the thing that
    
embodies
  
the accepted version of a =
Media Server is often a *client* to the MRCPv2
protocol.

Would anyone be really put out if we did a 1,$:s/media server/media
resource/g throughout the document?

Rationale: The document describes the Media RESOURCE Control Protocol, =
not
the Media SERVER Control Protocol.

</ChairHat>

Thoughts?  Comments?

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


    


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


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

------_=_NextPart_001_01C43D80.AAFDE250-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed May 19 15:39:57 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06745 for ; Wed, 19 May 2004 15:39:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQWkj-0007RF-Kf for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 15:29:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JJTLsB028593 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 15:29:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQVxx-0000JE-Mu for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 14:38:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29406 for ; Wed, 19 May 2004 14:38:54 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQVxu-0006va-VA for speechsc-web-archive@ietf.org; Wed, 19 May 2004 14:38:55 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQVx8-0006pR-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 14:38:11 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQVv5-0006fG-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 14:35:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQVlc-0005wa-Lm; Wed, 19 May 2004 14:26:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQRvr-0000OY-31 for speechsc@optimus.ietf.org; Wed, 19 May 2004 10:20:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14251 for ; Wed, 19 May 2004 10:20:27 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQRvo-0000A1-J2 for speechsc@ietf.org; Wed, 19 May 2004 10:20:28 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQRuX-00001R-00 for speechsc@ietf.org; Wed, 19 May 2004 10:19:11 -0400 Received: from almso1.att.com ([192.128.167.69] helo=almso1.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 1BQRte-0007gt-00 for Speechsc@ietf.org; Wed, 19 May 2004 10:18:14 -0400 Received: from attrh0i.attrh.att.com ([135.37.94.54]) by almso1.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id i4JEETCg019794 for ; Wed, 19 May 2004 10:17:44 -0400 Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.9) by attrh0i.attrh.att.com (6.5.032) id 40951C4D001ED703; Wed, 19 May 2004 10:17:31 -0400 x-mimeole: Produced By Microsoft Exchange V6.0.6561.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43DAC.0D2330BC" Subject: RE: [Speechsc] Media Server or Media Resource Date: Wed, 19 May 2004 10:17:43 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A071EF4C0@ACCLUST02EVS1.ugd.att.com> Thread-Topic: [Speechsc] Media Server or Media Resource Thread-Index: AcQ9hqK2Dj2Sa715SZaUtiJhFZK1CgAJHe0Q From: "Roy, Radhika R, ALABS" To: "Reifenrath, Klaus" , "Sarvi Shanmugham" , "Eric Burger" Cc: Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. ------_=_NextPart_001_01C43DAC.0D2330BC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Eric, Klaus, and Sarvi: =20 Let me try to provide the definition of media servers: =20 "Media servers (MSs) typically operate with application servers (ASs) to = handle and terminate media streams, and provide services such as = announcement, media bridging, media transcoding, interactive voice = response (IVR) messages (with or without VocieXML), speech-to-text (STT) = conversion, text-to-speech (TTS) conversion, and others." =20 Cheers! =20 Radhika R. Roy AT&T 732 420 1580 -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf = Of Reifenrath, Klaus Sent: Wednesday, May 19, 2004 5:07 AM To: 'Sarvi Shanmugham'; Eric Burger Cc: Speechsc@ietf.org Subject: RE: [Speechsc] Media Server or Media Resource Hi Eric and Sarvi, =20 after some internal discussions I prefer to stay with the term "media = server"! =20 In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that = was referenced in the speechsc requirements document) the following = definition of a media server can be found (section 3 on page 3): "Media servers are devices that perform media processing on real-time = packet media." According to this definition the MRCP server is a media server (and not = the platform that uses MRCP servers for media processing, which becomes = a media proxy). =20 In a network architecture that includes MRCP servers there might be = other media servers. =20 Could someone point me to the documents of the IETF, 3GPP, ... where I = can find their definition of a media server. The term "media server" is = used fairly often (especially in product brochures), but it seems to be = difficult to find precise definitions. =20 Thanks, Klaus =20 =20 -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Mittwoch, 19. Mai 2004 01:49 To: Garland Sharratt Cc: Eric Burger; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource This is fine by me. And I haven't heard any opposition so far.=20 I will make the necessary edits. Sarvi Garland Sharratt wrote:=20 Eric, I concur. Using the term "media server" for MRCPv2 muddies the waters, I think, and implies the two things are the same whereas they = are not. Garland -----Original Message----- From: speechsc-admin@ietf.org [ mailto:speechsc-admin@ietf.org]On = Behalf Of Jeff Haynie Sent: Monday, May 17, 2004 08:10 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource That's funny - I myself have struggled with the same term and would be much more in favor of "media resource". Jeff Eric Burger wrote: =20 I have a form issue, not necessarily a substance issue. Throughout the MRCPv2 document, the "thing that is a server controlled = by the MRCPv2 protocol" is called a "Media Server". A Media Server is a device that has a well-defined meaning, in the IETF, 3GPP (MRF), SIP Forum, IPCC, etc. That definition, IMHO, does not really match with "the thing that is a server controlled by the MRCPv2 protocol." In fact, the thing that =20 embodies =20 the accepted version of a Media Server is often a *client* to the MRCPv2 protocol. Would anyone be really put out if we did a 1,$:s/media server/media resource/g throughout the document? Rationale: The document describes the Media RESOURCE Control Protocol, = not the Media SERVER Control Protocol. Thoughts? Comments? _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 ------_=_NextPart_001_01C43DAC.0D2330BC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Eric,=20 Klaus, and Sarvi:
 
Let me=20 try to provide the definition of media servers:
 
"Media=20 servers (MSs) typically operate with application servers (ASs) to handle = and=20 terminate media streams, and provide services such as announcement, = media=20 bridging, media transcoding, interactive voice response (IVR) messages = (with or=20 without VocieXML), speech-to-text (STT) conversion, text-to-speech (TTS) = conversion, and others."
 
Cheers!
 
Radhika R. Roy
AT&T
732=20 420 1580
-----Original Message-----
From: = speechsc-admin@ietf.org=20 [mailto:speechsc-admin@ietf.org]On Behalf Of Reifenrath,=20 Klaus
Sent: Wednesday, May 19, 2004 5:07 AM
To: = 'Sarvi=20 Shanmugham'; Eric Burger
Cc: = Speechsc@ietf.org
Subject:=20 RE: [Speechsc] Media Server or Media Resource

Hi = Eric and=20 Sarvi,
 
after some=20 internal discussions I prefer to stay with the term "media=20 server"!
 
In=20 draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that = was=20 referenced in the speechsc requirements document) the following = definition of=20 a media server can be found (section 3 on page = 3):
"Media servers are=20 devices that perform media processing on real-time packet=20 media."
According to this=20 definition the MRCP server is a media server (and not the = platform=20 that uses MRCP servers for media processing, which becomes a media=20 proxy). =20
In a = network=20 architecture that includes MRCP servers there might be other media=20 servers.
 
Could someone=20 point me to the documents of the IETF, 3GPP, ... where I can find = their=20 definition of a media server. The term "media server" is used fairly = often=20 (especially in product brochures), but it seems to be difficult to = find=20 precise definitions.
 
Thanks,
Klaus
 
 
-----Original Message-----
From: Sarvi Shanmugham = [mailto:sarvi@cisco.com]
Sent: Mittwoch, 19. Mai 2004=20 01:49
To: Garland Sharratt
Cc: Eric Burger;=20 Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or = Media=20 Resource

This is fine by me. And I haven't heard = any=20 opposition so far.
 I will make the necessary=20 edits.

Sarvi
Garland Sharratt wrote:=20 
Eric, I concur.  Using the term "media =
server" for MRCPv2 muddies the
waters, I think, and implies the two things are the same whereas they =
are
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would be
much more in favor of "media resource".

Jeff

Eric Burger wrote:

  
<ChairHat =
state=3D"off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server controlled =
by
the MRCPv2 protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the IETF,
3GPP (MRF), SIP Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that is a
server controlled by the MRCPv2 protocol."  In fact, the thing that
    
embodies
  
the accepted version of a =
Media Server is often a *client* to the MRCPv2
protocol.

Would anyone be really put out if we did a 1,$:s/media server/media
resource/g throughout the document?

Rationale: The document describes the Media RESOURCE Control Protocol, =
not
the Media SERVER Control Protocol.

</ChairHat>

Thoughts?  Comments?

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


    


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


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

------_=_NextPart_001_01C43DAC.0D2330BC-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed May 19 15:58:48 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09446 for ; Wed, 19 May 2004 15:58:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQWrM-0000s8-Ff for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 15:36:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JJaBHq003344 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 15:36:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQWMY-0002GU-Ll for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 15:04:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01780 for ; Wed, 19 May 2004 15:04:13 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQWMQ-0002as-Cc for speechsc-web-archive@ietf.org; Wed, 19 May 2004 15:04:14 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQWLK-0002Ne-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 15:03:08 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQWKF-0002CB-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 15:01:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQVoM-0006fd-Dm; Wed, 19 May 2004 14:29:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQTWv-00026a-Az for speechsc@optimus.ietf.org; Wed, 19 May 2004 12:02:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20254 for ; Wed, 19 May 2004 12:02:50 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQTWt-0000L8-VT for speechsc@ietf.org; Wed, 19 May 2004 12:02:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQTW4-0000Hv-00 for speechsc@ietf.org; Wed, 19 May 2004 12:02:01 -0400 Received: from mx1.scansoft.com ([198.71.64.81]) by ietf-mx with esmtp (Exim 4.12) id 1BQTVM-0000BS-00 for speechsc@ietf.org; Wed, 19 May 2004 12:01:16 -0400 Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx1 with trend_isnt_name_B; Wed, 19 May 2004 12:03:16 -0400 Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service (5.5.2653.19) id ; Wed, 19 May 2004 11:59:52 -0400 Message-ID: From: "Reifenrath, Klaus" To: "'Sarvi Shanmugham'" Cc: "IETF SPEECHSC (E-mail)" Subject: RE: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs Date: Wed, 19 May 2004 11:58:47 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43DBA.2BA74390" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C43DBA.2BA74390 Content-Type: text/plain; charset="iso-8859-1" Hi Sarvi, with your change 17) DTMF tone recognition became a SHOULD for the recognizer resource. DTMF tone recognition is not a natural feature of SPEECH recognition engines. Furthermore host based DTMF recognition seems not to be very common. Therefore I suggest, to replace the SHOULD with a MAY. Regards, Klaus -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Donnerstag, 13. Mai 2004 21:58 To: IETF SPEECHSC (E-mail) Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs The MRCPv2 draft has been updated to version -03. Please find below the change logs for the new draft. Thanks, Sarvi 1. Updated Referce numbers to be acurate. 2. In the Introduction ......................... The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session. The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement. .................. 3. Added Security Considerations. 4. Updated with various types and corrections mentioned via email. 5. MRCP-Version description added the following text, per Klaus's request. Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0". 6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources. 7. Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke 8. Moved Vendor specific headers to be a generic header so that it applies to all resources. 9. Updated many places that use ALPHA to VCHAR as was suggested on the list. 10. Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure. 11. Added support for timestamp to Speech-Marker header 12. Changed name i. hotword-max-seconds ---> hotword-max-duration ii. hotword-min-seconds ---> hotword-min-duration 13. Change many headers from integer value o float 0.0 - 1.0 14. Recognition-Timeout description clarified. 15. DTMF-Term-Timeout clarified. 16. Recogintion-Mode support 17. DTMF and RFC2833 requirements clarified. 18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource 19. Added Speech-Complete-Timeout, New-audio-Channel and Abort-Verification header fields to the Verification resource. 20. Ver-Buffer-Utterance header field default value is set to "false" 21. Change the Value of "Score" and Verification-Score to 0.0 -1.0 22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods. 23. VER-STOP method updated to support stop Vs abort. ------_=_NextPart_001_01C43DBA.2BA74390 Content-Type: text/html; charset="iso-8859-1"
Hi Sarvi,
 
with your change 17) DTMF tone recognition became a SHOULD for the recognizer resource.
DTMF tone recognition is not a natural feature of SPEECH recognition engines. Furthermore host based DTMF recognition seems not to be very common.
Therefore I suggest, to replace the SHOULD with a MAY.
 
Regards,
Klaus
-----Original Message-----
From: Sarvi Shanmugham [mailto:sarvi@cisco.com]
Sent: Donnerstag, 13. Mai 2004 21:58
To: IETF SPEECHSC (E-mail)
Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs

The MRCPv2 draft has been updated to version -03.

Please find below the change logs for the new draft.


Thanks,
Sarvi

1. Updated Referce numbers to be acurate.

<!--[if !supportEmptyParas]-->2. In the Introduction   .........................<!--[endif]-->

   The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session.  The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement.

..................

3. Added Security Considerations.

4. Updated with various types and corrections mentioned via email.

5. MRCP-Version  description added the following text, per Klaus's request.

Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0".

6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources.

7.  Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke

8.  Moved Vendor specific headers to be a generic header so that it applies to all resources.

9. Updated many places that use ALPHA to VCHAR as was suggested on the list.

10.  Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure.

11.  Added support for timestamp to Speech-Marker header

12. Changed name            
                            i. hotword-max-seconds ---> hotword-max-duration  
                            ii. hotword-min-seconds ---> hotword-min-duration

13.  Change many headers from integer value o float 0.0 - 1.0

14.  Recognition-Timeout description clarified.

15.  DTMF-Term-Timeout clarified.

16.  Recogintion-Mode support

17. DTMF and RFC2833 requirements clarified.

18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource

19.  Added Speech-Complete-Timeout,  New-audio-Channel and Abort-Verification header fields to the Verification resource.

20. Ver-Buffer-Utterance header field default value is set to "false"

21. Change the Value of  "Score" and Verification-Score to 0.0 -1.0

22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods.

23. VER-STOP method updated to support stop Vs abort.



------_=_NextPart_001_01C43DBA.2BA74390-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed May 19 17:46:12 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21463 for ; Wed, 19 May 2004 17:46:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQYfK-0002Q1-Nn for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 17:31:55 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JLVsju009298 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 17:31:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQYRH-0002xu-0K for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 17:17:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18047 for ; Wed, 19 May 2004 17:17:19 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQYRE-0001GV-PQ for speechsc-web-archive@ietf.org; Wed, 19 May 2004 17:17:20 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQYQI-00018N-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 17:16:23 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQYPf-00010g-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 17:15:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQXU5-00067M-Iv; Wed, 19 May 2004 16:16:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQXGN-0000R2-1Y for speechsc@optimus.ietf.org; Wed, 19 May 2004 16:02:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10010 for ; Wed, 19 May 2004 16:02:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQXGL-0003zK-8v for speechsc@ietf.org; Wed, 19 May 2004 16:02:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQXFL-0003s3-00 for speechsc@ietf.org; Wed, 19 May 2004 16:01:00 -0400 Received: from [212.17.54.82] (helo=mail.voxpilot.com) by ietf-mx with esmtp (Exim 4.12) id 1BQXEP-0003kT-00 for Speechsc@ietf.org; Wed, 19 May 2004 16:00:01 -0400 Received: from daburkew2k (dsl-34-34.dsl.netsource.ie [213.79.34.34]) by mail.voxpilot.com (Postfix) with ESMTP id 6562F21403D; Wed, 19 May 2004 21:05:00 +0100 (IST) Message-ID: <016d01c43de4$3aeaca00$0a01a8c0@db01.voxpilot.com> From: "Dave Burke" To: "Reifenrath, Klaus" , "'Sarvi Shanmugham'" , "Eric Burger" Cc: References: Subject: Re: [Speechsc] Media Server or Media Resource Date: Wed, 19 May 2004 21:59:51 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_016A_01C43DEC.9C37DF20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_016A_01C43DEC.9C37DF20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I prefer calling a "Media Server" a "Media B2BUA".=20 Only kidding. I favour Eric's suggestion for "media resource" in the MRCPv2 = specification.=20 - Dave ----- Original Message -----=20 From: Reifenrath, Klaus=20 To: 'Sarvi Shanmugham' ; Eric Burger=20 Cc: Speechsc@ietf.org=20 Sent: Wednesday, May 19, 2004 10:07 AM Subject: RE: [Speechsc] Media Server or Media Resource Hi Eric and Sarvi, after some internal discussions I prefer to stay with the term "media = server"! In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, = that was referenced in the speechsc requirements document) the following = definition of a media server can be found (section 3 on page 3): "Media servers are devices that perform media processing on real-time = packet media." According to this definition the MRCP server is a media server (and = not the platform that uses MRCP servers for media processing, which = becomes a media proxy). =20 In a network architecture that includes MRCP servers there might be = other media servers. Could someone point me to the documents of the IETF, 3GPP, ... where I = can find their definition of a media server. The term "media server" is = used fairly often (especially in product brochures), but it seems to be = difficult to find precise definitions. Thanks, Klaus -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Mittwoch, 19. Mai 2004 01:49 To: Garland Sharratt Cc: Eric Burger; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource This is fine by me. And I haven't heard any opposition so far.=20 I will make the necessary edits. Sarvi Garland Sharratt wrote:=20 Eric, I concur. Using the term "media server" for MRCPv2 muddies the waters, I think, and implies the two things are the same whereas they = are not. Garland -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Jeff Haynie Sent: Monday, May 17, 2004 08:10 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource That's funny - I myself have struggled with the same term and would be much more in favor of "media resource". Jeff Eric Burger wrote: =20 I have a form issue, not necessarily a substance issue. Throughout the MRCPv2 document, the "thing that is a server controlled = by the MRCPv2 protocol" is called a "Media Server". A Media Server is a device that has a well-defined meaning, in the IETF, 3GPP (MRF), SIP Forum, IPCC, etc. That definition, IMHO, does not really match with "the thing that is a server controlled by the MRCPv2 protocol." In fact, the thing that =20 embodies =20 the accepted version of a Media Server is often a *client* to the MRCPv2 protocol. Would anyone be really put out if we did a 1,$:s/media server/media resource/g throughout the document? Rationale: The document describes the Media RESOURCE Control Protocol, = not the Media SERVER Control Protocol. Thoughts? Comments? _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 ------=_NextPart_000_016A_01C43DEC.9C37DF20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I prefer calling a "Media Server" a = "Media B2BUA".=20
 
Only kidding.
 
I favour = Eric's suggestion for=20 "media resource" in the MRCPv2 specification.
 
- Dave
----- Original Message -----
From:=20 Reifenrath, Klaus =
To: 'Sarvi Shanmugham' ; Eric=20 Burger
Sent: Wednesday, May 19, 2004 = 10:07=20 AM
Subject: RE: [Speechsc] Media = Server or=20 Media Resource

Hi = Eric and=20 Sarvi,
 
after some=20 internal discussions I prefer to stay with the term "media=20 server"!
 
In=20 draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that = was=20 referenced in the speechsc requirements document) the following = definition of=20 a media server can be found (section 3 on page = 3):
"Media servers are=20 devices that perform media processing on real-time packet=20 media."
According to this=20 definition the MRCP server is a media server (and not the = platform=20 that uses MRCP servers for media processing, which becomes a media=20 proxy). =20
In a = network=20 architecture that includes MRCP servers there might be other media=20 servers.
 
Could someone=20 point me to the documents of the IETF, 3GPP, ... where I can find = their=20 definition of a media server. The term "media server" is used fairly = often=20 (especially in product brochures), but it seems to be difficult to = find=20 precise definitions.
 
Thanks,
Klaus
 
 
-----Original Message-----
From: Sarvi Shanmugham = [mailto:sarvi@cisco.com]
Sent: Mittwoch, 19. Mai 2004=20 01:49
To: Garland Sharratt
Cc: Eric Burger;=20 Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or = Media=20 Resource

This is fine by me. And I haven't heard = any=20 opposition so far.
 I will make the necessary=20 edits.

Sarvi
Garland Sharratt wrote:=20 
Eric, I concur.  Using the term "media =
server" for MRCPv2 muddies the
waters, I think, and implies the two things are the same whereas they =
are
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would be
much more in favor of "media resource".

Jeff

Eric Burger wrote:

  
<ChairHat =
state=3D"off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server controlled =
by
the MRCPv2 protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the IETF,
3GPP (MRF), SIP Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that is a
server controlled by the MRCPv2 protocol."  In fact, the thing that
    
embodies
  
the accepted version of a =
Media Server is often a *client* to the MRCPv2
protocol.

Would anyone be really put out if we did a 1,$:s/media server/media
resource/g throughout the document?

Rationale: The document describes the Media RESOURCE Control Protocol, =
not
the Media SERVER Control Protocol.

</ChairHat>

Thoughts?  Comments?

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


    


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


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

------=_NextPart_000_016A_01C43DEC.9C37DF20-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed May 19 20:25:08 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00898 for ; Wed, 19 May 2004 20:25:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQbJH-0006MJ-Vb for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 20:21:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K0LJUZ024444 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 20:21:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQbCU-0004sM-Je for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 20:14:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00529 for ; Wed, 19 May 2004 20:14:16 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQbCS-0000Vo-Ek for speechsc-web-archive@ietf.org; Wed, 19 May 2004 20:14:16 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQbBO-0000PD-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 20:13:12 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQbAf-0000Id-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 20:12:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQb4V-0003Ag-Nb; Wed, 19 May 2004 20:06:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQb2d-0002fL-8R for speechsc@optimus.ietf.org; Wed, 19 May 2004 20:04:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00248 for ; Wed, 19 May 2004 20:04:05 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQb2b-0007CX-54 for speechsc@ietf.org; Wed, 19 May 2004 20:04:05 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQb1i-00076O-00 for speechsc@ietf.org; Wed, 19 May 2004 20:03:12 -0400 Received: from cerbrus.convedia.com ([216.129.93.50]) by ietf-mx with esmtp (Exim 4.12) id 1BQb1N-0006z8-00 for Speechsc@ietf.org; Wed, 19 May 2004 20:02:49 -0400 Received: from mailhost.convedia.com (ladon [192.168.208.15]) by cerbrus.convedia.com (8.12.9/8.12.9) with ESMTP id i4JNoLEv010402 for ; Wed, 19 May 2004 16:50:21 -0700 (PDT) Received: from laptop33 ([192.168.209.2]) by mailhost.convedia.com (8.12.9/8.12.9) with SMTP id i4K02DjU013091 for ; Wed, 19 May 2004 17:02:13 -0700 (PDT) From: "Garland Sharratt" To: Subject: RE: [Speechsc] Media Server or Media Resource Date: Wed, 19 May 2004 17:02:19 -0700 Keywords: .xbulk, .aa Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01C43DC3.0B453AE0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal In-Reply-To: <34DA635B184A644DA4588E260EC0A25A071EF4C0@ACCLUST02EVS1.ugd.att.com> Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_0017_01C43DC3.0B453AE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit To Radhika's list I would also add recording and playback, as well as video announcements, video recording and playback, and video bridging. "Media server" is a generic term in NGN for a multi-purpose slave media processing engine controlled by a call agent or application server. All NGN architectures have a media server component, often by another name; in 3GPP, for instance, it's called an Media Resource Function Processor (MRFP). Media server control interfaces in NGN architectures are MGCP, H.248, and SIP. Garland -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Roy, Radhika R, ALABS Sent: Wednesday, May 19, 2004 07:18 To: Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger Cc: Speechsc@ietf.org Subject: RE: [Speechsc] Media Server or Media Resource Eric, Klaus, and Sarvi: Let me try to provide the definition of media servers: "Media servers (MSs) typically operate with application servers (ASs) to handle and terminate media streams, and provide services such as announcement, media bridging, media transcoding, interactive voice response (IVR) messages (with or without VocieXML), speech-to-text (STT) conversion, text-to-speech (TTS) conversion, and others." Cheers! Radhika R. Roy AT&T 732 420 1580 -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Reifenrath, Klaus Sent: Wednesday, May 19, 2004 5:07 AM To: 'Sarvi Shanmugham'; Eric Burger Cc: Speechsc@ietf.org Subject: RE: [Speechsc] Media Server or Media Resource Hi Eric and Sarvi, after some internal discussions I prefer to stay with the term "media server"! In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that was referenced in the speechsc requirements document) the following definition of a media server can be found (section 3 on page 3): "Media servers are devices that perform media processing on real-time packet media." According to this definition the MRCP server is a media server (and not the platform that uses MRCP servers for media processing, which becomes a media proxy). In a network architecture that includes MRCP servers there might be other media servers. Could someone point me to the documents of the IETF, 3GPP, ... where I can find their definition of a media server. The term "media server" is used fairly often (especially in product brochures), but it seems to be difficult to find precise definitions. Thanks, Klaus -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Mittwoch, 19. Mai 2004 01:49 To: Garland Sharratt Cc: Eric Burger; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource This is fine by me. And I haven't heard any opposition so far. I will make the necessary edits. Sarvi Garland Sharratt wrote: Eric, I concur. Using the term "media server" for MRCPv2 muddies the waters, I think, and implies the two things are the same whereas they are not. Garland -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Jeff Haynie Sent: Monday, May 17, 2004 08:10 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource That's funny - I myself have struggled with the same term and would be much more in favor of "media resource". Jeff Eric Burger wrote: I have a form issue, not necessarily a substance issue. Throughout the MRCPv2 document, the "thing that is a server controlled by the MRCPv2 protocol" is called a "Media Server". A Media Server is a device that has a well-defined meaning, in the IETF, 3GPP (MRF), SIP Forum, IPCC, etc. That definition, IMHO, does not really match with "the thing that is a server controlled by the MRCPv2 protocol." In fact, the thing that embodies the accepted version of a Media Server is often a *client* to the MRCPv2 protocol. Would anyone be really put out if we did a 1,$:s/media server/media resource/g throughout the document? Rationale: The document describes the Media RESOURCE Control Protocol, not the Media SERVER Control Protocol. Thoughts? Comments? _______________________________________________ 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 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc ------=_NextPart_000_0017_01C43DC3.0B453AE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
To=20 Radhika's list I would also add recording and playback, as well as video = announcements, video recording and playback, and video=20 bridging.
 
"Media=20 server" is a generic term in NGN for a multi-purpose slave media = processing=20 engine controlled by a call agent or application server.  All NGN=20 architectures have a media server component, often by another name; in = 3GPP, for=20 instance, it's called an Media Resource Function Processor (MRFP).  = Media=20 server control interfaces in NGN architectures are MGCP, H.248, and=20 SIP.
 
Garland
 
-----Original Message-----
From: = speechsc-admin@ietf.org=20 [mailto:speechsc-admin@ietf.org]On Behalf Of Roy, Radhika R,=20 ALABS
Sent: Wednesday, May 19, 2004 07:18
To: = Reifenrath,=20 Klaus; Sarvi Shanmugham; Eric Burger
Cc:=20 Speechsc@ietf.org
Subject: RE: [Speechsc] Media Server or = Media=20 Resource

Eric,=20 Klaus, and Sarvi:
 
Let me=20 try to provide the definition of media servers:
 
"Media=20 servers (MSs) typically operate with application servers (ASs) to handle = and=20 terminate media streams, and provide services such as announcement, = media=20 bridging, media transcoding, interactive voice response (IVR) messages = (with or=20 without VocieXML), speech-to-text (STT) conversion, text-to-speech (TTS) = conversion, and others."
 
Cheers!
 
Radhika R. Roy
AT&T
732=20 420 1580
-----Original Message-----
From: = speechsc-admin@ietf.org=20 [mailto:speechsc-admin@ietf.org]On Behalf Of Reifenrath,=20 Klaus
Sent: Wednesday, May 19, 2004 5:07 AM
To: = 'Sarvi=20 Shanmugham'; Eric Burger
Cc: = Speechsc@ietf.org
Subject:=20 RE: [Speechsc] Media Server or Media Resource

Hi = Eric and=20 Sarvi,
 
after some=20 internal discussions I prefer to stay with the term "media=20 server"!
 
In=20 draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that = was=20 referenced in the speechsc requirements document) the following = definition of=20 a media server can be found (section 3 on page = 3):
"Media servers are=20 devices that perform media processing on real-time packet=20 media."
According to this=20 definition the MRCP server is a media server (and not the = platform=20 that uses MRCP servers for media processing, which becomes a media=20 proxy). =20
In a = network=20 architecture that includes MRCP servers there might be other media=20 servers.
 
Could someone=20 point me to the documents of the IETF, 3GPP, ... where I can find = their=20 definition of a media server. The term "media server" is used fairly = often=20 (especially in product brochures), but it seems to be difficult to = find=20 precise definitions.
 
Thanks,
Klaus
 
 
-----Original Message-----
From: Sarvi Shanmugham = [mailto:sarvi@cisco.com]
Sent: Mittwoch, 19. Mai 2004=20 01:49
To: Garland Sharratt
Cc: Eric Burger;=20 Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or = Media=20 Resource

This is fine by me. And I haven't heard = any=20 opposition so far.
 I will make the necessary=20 edits.

Sarvi
Garland Sharratt wrote:=20 
Eric, I concur.  Using the term "media =
server" for MRCPv2 muddies the
waters, I think, and implies the two things are the same whereas they =
are
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would be
much more in favor of "media resource".

Jeff

Eric Burger wrote:

  
<ChairHat =
state=3D"off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server controlled =
by
the MRCPv2 protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the IETF,
3GPP (MRF), SIP Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that is a
server controlled by the MRCPv2 protocol."  In fact, the thing that
    
embodies
  
the accepted version of a =
Media Server is often a *client* to the MRCPv2
protocol.

Would anyone be really put out if we did a 1,$:s/media server/media
resource/g throughout the document?

Rationale: The document describes the Media RESOURCE Control Protocol, =
not
the Media SERVER Control Protocol.

</ChairHat>

Thoughts?  Comments?

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


    


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


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

------=_NextPart_000_0017_01C43DC3.0B453AE0-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed May 19 21:25:25 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03708 for ; Wed, 19 May 2004 21:25:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQc9u-0002ZF-0H for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 21:15:42 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K1FfrU009865 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 21:15:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQc4c-0001Sq-9Y for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 21:10:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03118 for ; Wed, 19 May 2004 21:10:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQc4Z-0007da-Ko for speechsc-web-archive@ietf.org; Wed, 19 May 2004 21:10:11 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQc3i-0007Wa-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 21:09:19 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQc34-0007PE-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 21:08:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQbzZ-0008BH-9I; Wed, 19 May 2004 21:05:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQbt4-0006pY-QI for speechsc@optimus.ietf.org; Wed, 19 May 2004 20:58:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02564 for ; Wed, 19 May 2004 20:58:16 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQbt2-0005zP-6f for speechsc@ietf.org; Wed, 19 May 2004 20:58:16 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQbs9-0005s4-00 for speechsc@ietf.org; Wed, 19 May 2004 20:57:22 -0400 Received: from [216.248.178.195] (helo=www.vocalocity.net) by ietf-mx with esmtp (Exim 4.12) id 1BQbrn-0005kO-00 for Speechsc@ietf.org; Wed, 19 May 2004 20:56:59 -0400 Received: from vocalocity.net (unknown [216.233.3.85]) by www.vocalocity.net (Postfix) with ESMTP id DCC88A441; Wed, 19 May 2004 20:56:54 -0400 (EDT) Message-ID: <40AC0255.2010106@vocalocity.net> Date: Wed, 19 May 2004 20:56:53 -0400 From: Jeff Haynie User-Agent: Mozilla Thunderbird 0.5+ (Windows/20040326) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garland Sharratt Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Both you and Radhika seem to highlight exactly what MRCP is NOT and re-enforce Eric's original request, no? Of course, I'm not implying that media servers can't also support the MRCP protocol as a fact of implementation - that's something that's completely within reason. Jeff Garland Sharratt wrote: > To Radhika's list I would also add recording and playback, as well as > video announcements, video recording and playback, and video bridging. > > "Media server" is a generic term in NGN for a multi-purpose slave > media processing engine controlled by a call agent or application > server. All NGN architectures have a media server component, often by > another name; in 3GPP, for instance, it's called an Media Resource > Function Processor (MRFP). Media server control interfaces in NGN > architectures are MGCP, H.248, and SIP. > > Garland > > -----Original Message----- > *From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On > Behalf Of *Roy, Radhika R, ALABS > *Sent:* Wednesday, May 19, 2004 07:18 > *To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger > *Cc:* Speechsc@ietf.org > *Subject:* RE: [Speechsc] Media Server or Media Resource > > Eric, Klaus, and Sarvi: > > Let me try to provide the definition of media servers: > > "Media servers (MSs) typically operate with application servers (ASs) > to handle and terminate media streams, and provide services such as > announcement, media bridging, media transcoding, interactive voice > response (IVR) messages (with or without VocieXML), speech-to-text > (STT) conversion, text-to-speech (TTS) conversion, and others." > > Cheers! > > Radhika R. Roy > AT&T > 732 420 1580 > > -----Original Message----- > *From:* speechsc-admin@ietf.org > [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus > *Sent:* Wednesday, May 19, 2004 5:07 AM > *To:* 'Sarvi Shanmugham'; Eric Burger > *Cc:* Speechsc@ietf.org > *Subject:* RE: [Speechsc] Media Server or Media Resource > > Hi Eric and Sarvi, > > after some internal discussions I prefer to stay with the term > "media server"! > > In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, > that was referenced in the speechsc requirements document) the > following definition of a media server can be found (section 3 on > page 3): > "Media servers are devices that perform media processing on > real-time packet media." > According to this definition the MRCP server is a media server > (and not the platform that uses MRCP servers for media processing, > which becomes a media proxy). > In a network architecture that includes MRCP servers there might > be other media servers. > > Could someone point me to the documents of the IETF, 3GPP, ... > where I can find their definition of a media server. The term > "media server" is used fairly often (especially in product > brochures), but it seems to be difficult to find precise definitions. > > Thanks, > Klaus > > > > -----Original Message----- > *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] > *Sent:* Mittwoch, 19. Mai 2004 01:49 > *To:* Garland Sharratt > *Cc:* Eric Burger; Speechsc@ietf.org > *Subject:* Re: [Speechsc] Media Server or Media Resource > > This is fine by me. And I haven't heard any opposition so far. > I will make the necessary edits. > > Sarvi > Garland Sharratt wrote: > >>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>waters, I think, and implies the two things are the same whereas they are >>not. >> >>Garland >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>Of Jeff Haynie >>Sent: Monday, May 17, 2004 08:10 >>To: Eric Burger >>Cc: Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>That's funny - I myself have struggled with the same term and would be >>much more in favor of "media resource". >> >>Jeff >> >>Eric Burger wrote: >> >> >> >>> >>>I have a form issue, not necessarily a substance issue. >>> >>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>the MRCPv2 protocol" is called a "Media Server". >>> >>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>3GPP (MRF), SIP Forum, IPCC, etc. >>> >>>That definition, IMHO, does not really match with "the thing that is a >>>server controlled by the MRCPv2 protocol." In fact, the thing that >>> >>> >>embodies >> >> >>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>protocol. >>> >>>Would anyone be really put out if we did a 1,$:s/media server/media >>>resource/g throughout the document? >>> >>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>the Media SERVER Control Protocol. >>> >>> >>> >>>Thoughts? Comments? >>> >>>_______________________________________________ >>>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 >> >> >>_______________________________________________ >>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 exim@www1.ietf.org Wed May 19 22:22:26 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06208 for ; Wed, 19 May 2004 22:22:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQdAY-0008Nf-EV for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 22:20:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K2KQqB032214 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 22:20:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQct0-0004G0-Vf for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 22:02:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05365 for ; Wed, 19 May 2004 22:02:15 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQcsx-0006y4-U5 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:02:16 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQcs6-0006qG-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:01:23 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQcrN-0006hh-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:00:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQcj5-00027C-8R; Wed, 19 May 2004 21:52:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQcdQ-0008H0-Jp for speechsc@optimus.ietf.org; Wed, 19 May 2004 21:46:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04669 for ; Wed, 19 May 2004 21:46:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQcdN-0004iq-F4 for speechsc@ietf.org; Wed, 19 May 2004 21:46:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQccV-0004bA-00 for speechsc@ietf.org; Wed, 19 May 2004 21:45:16 -0400 Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 1BQcc2-0004T9-00 for Speechsc@ietf.org; Wed, 19 May 2004 21:44:46 -0400 Received: from attrh0i.attrh.att.com ([135.37.94.54]) by almso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id i4K1h66c022577 for ; Wed, 19 May 2004 21:44:17 -0400 Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.9) by attrh0i.attrh.att.com (6.5.032) id 40951C4D002062EB; Wed, 19 May 2004 21:44:04 -0400 x-mimeole: Produced By Microsoft Exchange V6.0.6561.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] Media Server or Media Resource Date: Wed, 19 May 2004 21:44:16 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A0721736E@ACCLUST02EVS1.ugd.att.com> Thread-Topic: [Speechsc] Media Server or Media Resource Thread-Index: AcQ+BulL7nO/Y19sS221L0e7QbTHXQABGnTQ From: "Roy, Radhika R, ALABS" To: "Jeff Haynie" , "Garland Sharratt" Cc: Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Jeff: Garland and I have been saying exactly what a media server is. A media = server will be using many protocols, and MRCP is only of them. In this sense, MRCP is one of the protocols that is used for its media = resources control.=20 Who knows MRCP may NOT enough to control all the media resources of a = Media Server. Let us see the big picture of a media server. Radhika -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Jeff Haynie Sent: Wednesday, May 19, 2004 8:57 PM To: Garland Sharratt Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource Both you and Radhika seem to highlight exactly what MRCP is NOT and=20 re-enforce Eric's original request, no? Of course, I'm not implying=20 that media servers can't also support the MRCP protocol as a fact of=20 implementation - that's something that's completely within reason. Jeff Garland Sharratt wrote: > To Radhika's list I would also add recording and playback, as well as=20 > video announcements, video recording and playback, and video bridging. > =20 > "Media server" is a generic term in NGN for a multi-purpose slave=20 > media processing engine controlled by a call agent or application=20 > server. All NGN architectures have a media server component, often by = > another name; in 3GPP, for instance, it's called an Media Resource=20 > Function Processor (MRFP). Media server control interfaces in NGN=20 > architectures are MGCP, H.248, and SIP. > =20 > Garland > =20 > -----Original Message----- > *From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On=20 > Behalf Of *Roy, Radhika R, ALABS > *Sent:* Wednesday, May 19, 2004 07:18 > *To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger > *Cc:* Speechsc@ietf.org > *Subject:* RE: [Speechsc] Media Server or Media Resource > > Eric, Klaus, and Sarvi: > =20 > Let me try to provide the definition of media servers: > =20 > "Media servers (MSs) typically operate with application servers (ASs)=20 > to handle and terminate media streams, and provide services such as=20 > announcement, media bridging, media transcoding, interactive voice=20 > response (IVR) messages (with or without VocieXML), speech-to-text=20 > (STT) conversion, text-to-speech (TTS) conversion, and others." > =20 > Cheers! > =20 > Radhika R. Roy > AT&T > 732 420 1580 > > -----Original Message----- > *From:* speechsc-admin@ietf.org > [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus > *Sent:* Wednesday, May 19, 2004 5:07 AM > *To:* 'Sarvi Shanmugham'; Eric Burger > *Cc:* Speechsc@ietf.org > *Subject:* RE: [Speechsc] Media Server or Media Resource > > Hi Eric and Sarvi, > =20 > after some internal discussions I prefer to stay with the term > "media server"! > =20 > In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, > that was referenced in the speechsc requirements document) the > following definition of a media server can be found (section 3 on > page 3): > "Media servers are devices that perform media processing on > real-time packet media." > According to this definition the MRCP server is a media server > (and not the platform that uses MRCP servers for media processing, > which becomes a media proxy).=20 > In a network architecture that includes MRCP servers there might > be other media servers. > =20 > Could someone point me to the documents of the IETF, 3GPP, ... > where I can find their definition of a media server. The term > "media server" is used fairly often (especially in product > brochures), but it seems to be difficult to find precise = definitions. > =20 > Thanks, > Klaus > =20 > =20 > > -----Original Message----- > *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] > *Sent:* Mittwoch, 19. Mai 2004 01:49 > *To:* Garland Sharratt > *Cc:* Eric Burger; Speechsc@ietf.org > *Subject:* Re: [Speechsc] Media Server or Media Resource > > This is fine by me. And I haven't heard any opposition so far. > I will make the necessary edits. > > Sarvi > Garland Sharratt wrote: > >>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>waters, I think, and implies the two things are the same whereas they = are >>not. >> >>Garland >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On = Behalf >>Of Jeff Haynie >>Sent: Monday, May 17, 2004 08:10 >>To: Eric Burger >>Cc: Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>That's funny - I myself have struggled with the same term and would be >>much more in favor of "media resource". >> >>Jeff >> >>Eric Burger wrote: >> >> =20 >> >>> >>>I have a form issue, not necessarily a substance issue. >>> >>>Throughout the MRCPv2 document, the "thing that is a server = controlled by >>>the MRCPv2 protocol" is called a "Media Server". >>> >>>A Media Server is a device that has a well-defined meaning, in the = IETF, >>>3GPP (MRF), SIP Forum, IPCC, etc. >>> >>>That definition, IMHO, does not really match with "the thing that is = a >>>server controlled by the MRCPv2 protocol." In fact, the thing that >>> =20 >>> >>embodies >> =20 >> >>>the accepted version of a Media Server is often a *client* to the = MRCPv2 >>>protocol. >>> >>>Would anyone be really put out if we did a 1,$:s/media server/media >>>resource/g throughout the document? >>> >>>Rationale: The document describes the Media RESOURCE Control = Protocol, not >>>the Media SERVER Control Protocol. >>> >>> >>> >>>Thoughts? Comments? >>> >>>_______________________________________________ >>>Speechsc mailing list >>>Speechsc@ietf.org >>>https://www1.ietf.org/mailman/listinfo/speechsc >>> >>> >>> =20 >>> >> >> >>_______________________________________________ >>Speechsc mailing list >>Speechsc@ietf.org >>https://www1.ietf.org/mailman/listinfo/speechsc >> >> >>_______________________________________________ >>Speechsc mailing list >>Speechsc@ietf.org >>https://www1.ietf.org/mailman/listinfo/speechsc >> >> =20 >> > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed May 19 22:23:07 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06277 for ; Wed, 19 May 2004 22:23:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQdBq-0000PF-Ie for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 22:21:47 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K2Lk0d001557 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 22:21:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQctu-0004S8-JU for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 22:03:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05415 for ; Wed, 19 May 2004 22:03:11 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQctr-00075c-Gu for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:03:11 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQcsw-0006xu-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:02:15 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQcs6-0006qA-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:01:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQcmw-0002WU-16; Wed, 19 May 2004 21:56:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQchR-0001TZ-H9 for speechsc@optimus.ietf.org; Wed, 19 May 2004 21:50:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04799 for ; Wed, 19 May 2004 21:50:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQchO-0005Fb-6k for speechsc@ietf.org; Wed, 19 May 2004 21:50:18 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQcgU-00056s-00 for speechsc@ietf.org; Wed, 19 May 2004 21:49:23 -0400 Received: from [216.248.178.195] (helo=www.vocalocity.net) by ietf-mx with esmtp (Exim 4.12) id 1BQcfc-0004z0-00 for Speechsc@ietf.org; Wed, 19 May 2004 21:48:28 -0400 Received: from vocalocity.net (unknown [216.233.3.85]) by www.vocalocity.net (Postfix) with ESMTP id 1AB63A441; Wed, 19 May 2004 21:48:29 -0400 (EDT) Message-ID: <40AC0E69.9030205@vocalocity.net> Date: Wed, 19 May 2004 21:48:25 -0400 From: Jeff Haynie User-Agent: Mozilla Thunderbird 0.5+ (Windows/20040326) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Roy, Radhika R, ALABS" Cc: Garland Sharratt , Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource References: <34DA635B184A644DA4588E260EC0A25A0721736E@ACCLUST02EVS1.ugd.att.com> In-Reply-To: <34DA635B184A644DA4588E260EC0A25A0721736E@ACCLUST02EVS1.ugd.att.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit OK, sorry, I'm confused. Do you support using the term "media server" or "media resource"? I can't tell from your response. Garland suggested in the original post that he favored the term "media resource" too. Jeff Roy, Radhika R, ALABS wrote: >Jeff: > >Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. > >In this sense, MRCP is one of the protocols that is used for its media resources control. > >Who knows MRCP may NOT enough to control all the media resources of a Media Server. > >Let us see the big picture of a media server. > >Radhika > >-----Original Message----- >From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >Of Jeff Haynie >Sent: Wednesday, May 19, 2004 8:57 PM >To: Garland Sharratt >Cc: Speechsc@ietf.org >Subject: Re: [Speechsc] Media Server or Media Resource > > >Both you and Radhika seem to highlight exactly what MRCP is NOT and >re-enforce Eric's original request, no? Of course, I'm not implying >that media servers can't also support the MRCP protocol as a fact of >implementation - that's something that's completely within reason. > >Jeff > >Garland Sharratt wrote: > > > >>To Radhika's list I would also add recording and playback, as well as >>video announcements, video recording and playback, and video bridging. >> >>"Media server" is a generic term in NGN for a multi-purpose slave >>media processing engine controlled by a call agent or application >>server. All NGN architectures have a media server component, often by >>another name; in 3GPP, for instance, it's called an Media Resource >>Function Processor (MRFP). Media server control interfaces in NGN >>architectures are MGCP, H.248, and SIP. >> >>Garland >> >>-----Original Message----- >>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On >>Behalf Of *Roy, Radhika R, ALABS >>*Sent:* Wednesday, May 19, 2004 07:18 >>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>*Cc:* Speechsc@ietf.org >>*Subject:* RE: [Speechsc] Media Server or Media Resource >> >>Eric, Klaus, and Sarvi: >> >>Let me try to provide the definition of media servers: >> >>"Media servers (MSs) typically operate with application servers (ASs) >>to handle and terminate media streams, and provide services such as >>announcement, media bridging, media transcoding, interactive voice >>response (IVR) messages (with or without VocieXML), speech-to-text >>(STT) conversion, text-to-speech (TTS) conversion, and others." >> >>Cheers! >> >>Radhika R. Roy >>AT&T >>732 420 1580 >> >> -----Original Message----- >> *From:* speechsc-admin@ietf.org >> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >> *Sent:* Wednesday, May 19, 2004 5:07 AM >> *To:* 'Sarvi Shanmugham'; Eric Burger >> *Cc:* Speechsc@ietf.org >> *Subject:* RE: [Speechsc] Media Server or Media Resource >> >> Hi Eric and Sarvi, >> >> after some internal discussions I prefer to stay with the term >> "media server"! >> >> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >> that was referenced in the speechsc requirements document) the >> following definition of a media server can be found (section 3 on >> page 3): >> "Media servers are devices that perform media processing on >> real-time packet media." >> According to this definition the MRCP server is a media server >> (and not the platform that uses MRCP servers for media processing, >> which becomes a media proxy). >> In a network architecture that includes MRCP servers there might >> be other media servers. >> >> Could someone point me to the documents of the IETF, 3GPP, ... >> where I can find their definition of a media server. The term >> "media server" is used fairly often (especially in product >> brochures), but it seems to be difficult to find precise definitions. >> >> Thanks, >> Klaus >> >> >> >> -----Original Message----- >> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >> *Sent:* Mittwoch, 19. Mai 2004 01:49 >> *To:* Garland Sharratt >> *Cc:* Eric Burger; Speechsc@ietf.org >> *Subject:* Re: [Speechsc] Media Server or Media Resource >> >> This is fine by me. And I haven't heard any opposition so far. >> I will make the necessary edits. >> >> Sarvi >> Garland Sharratt wrote: >> >> >> >>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>waters, I think, and implies the two things are the same whereas they are >>>not. >>> >>>Garland >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>Of Jeff Haynie >>>Sent: Monday, May 17, 2004 08:10 >>>To: Eric Burger >>>Cc: Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>That's funny - I myself have struggled with the same term and would be >>>much more in favor of "media resource". >>> >>>Jeff >>> >>>Eric Burger wrote: >>> >>> >>> >>> >>> >>>> >>>>I have a form issue, not necessarily a substance issue. >>>> >>>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>>the MRCPv2 protocol" is called a "Media Server". >>>> >>>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>> >>>>That definition, IMHO, does not really match with "the thing that is a >>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>> >>>> >>>> >>>> >>>embodies >>> >>> >>> >>> >>>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>>protocol. >>>> >>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>resource/g throughout the document? >>>> >>>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>>the Media SERVER Control Protocol. >>>> >>>> >>>> >>>>Thoughts? Comments? >>>> >>>>_______________________________________________ >>>>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 >>> >>> >>>_______________________________________________ >>>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 > > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Wed May 19 22:38:40 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07098 for ; Wed, 19 May 2004 22:38:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQdQo-0003aU-VG for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 22:37:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K2bEMi013767 for speechsc-archive@odin.ietf.org; Wed, 19 May 2004 22:37:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQdGW-0001OH-IV for speechsc-web-archive@optimus.ietf.org; Wed, 19 May 2004 22:26:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06484 for ; Wed, 19 May 2004 22:26:32 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQdGT-0002ZM-Be for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:26:33 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQdFY-0002Oi-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:25:37 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQdEg-0002El-00 for speechsc-web-archive@ietf.org; Wed, 19 May 2004 22:24:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQdCA-0000Yv-LE; Wed, 19 May 2004 22:22:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQd4h-0006hc-9L for speechsc@optimus.ietf.org; Wed, 19 May 2004 22:14:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05805 for ; Wed, 19 May 2004 22:14:19 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQd4e-0000jv-1b for speechsc@ietf.org; Wed, 19 May 2004 22:14:20 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQd3i-0000bt-00 for speechsc@ietf.org; Wed, 19 May 2004 22:13:24 -0400 Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 1BQd3Q-0000TQ-00 for Speechsc@ietf.org; Wed, 19 May 2004 22:13:04 -0400 Received: from attrh0i.attrh.att.com ([135.37.94.54]) by almso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id i4K2CV6W027035 for ; Wed, 19 May 2004 22:12:35 -0400 Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.9) by attrh0i.attrh.att.com (6.5.032) id 40951C4D00206707; Wed, 19 May 2004 22:12:21 -0400 x-mimeole: Produced By Microsoft Exchange V6.0.6561.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] Media Server or Media Resource Date: Wed, 19 May 2004 22:12:34 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A07217383@ACCLUST02EVS1.ugd.att.com> Thread-Topic: [Speechsc] Media Server or Media Resource Thread-Index: AcQ+DlmN9iZb1sksT5u5sgn8bHD78QAAYlkw From: "Roy, Radhika R, ALABS" To: "Jeff Haynie" Cc: "Garland Sharratt" , Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Jeff: OK, let us go back to analyze these terms: Media Resources and Media = Server. That is, MRCP is used to control (many, if not all) "media resources" of = a media server. Radhika -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Jeff Haynie Sent: Wednesday, May 19, 2004 9:48 PM To: Roy, Radhika R, ALABS Cc: Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource OK, sorry, I'm confused. Do you support using the term "media server"=20 or "media resource"? I can't tell from your response. Garland=20 suggested in the original post that he favored the term "media resource" = too. Jeff Roy, Radhika R, ALABS wrote: >Jeff: > >Garland and I have been saying exactly what a media server is. A media = server will be using many protocols, and MRCP is only of them. > >In this sense, MRCP is one of the protocols that is used for its media = resources control.=20 > >Who knows MRCP may NOT enough to control all the media resources of a = Media Server. > >Let us see the big picture of a media server. > >Radhika > >-----Original Message----- >From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >Of Jeff Haynie >Sent: Wednesday, May 19, 2004 8:57 PM >To: Garland Sharratt >Cc: Speechsc@ietf.org >Subject: Re: [Speechsc] Media Server or Media Resource > > >Both you and Radhika seem to highlight exactly what MRCP is NOT and=20 >re-enforce Eric's original request, no? Of course, I'm not implying=20 >that media servers can't also support the MRCP protocol as a fact of=20 >implementation - that's something that's completely within reason. > >Jeff > >Garland Sharratt wrote: > > =20 > >>To Radhika's list I would also add recording and playback, as well as=20 >>video announcements, video recording and playback, and video bridging. >>=20 >>"Media server" is a generic term in NGN for a multi-purpose slave=20 >>media processing engine controlled by a call agent or application=20 >>server. All NGN architectures have a media server component, often by = >>another name; in 3GPP, for instance, it's called an Media Resource=20 >>Function Processor (MRFP). Media server control interfaces in NGN=20 >>architectures are MGCP, H.248, and SIP. >>=20 >>Garland >>=20 >>-----Original Message----- >>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On=20 >>Behalf Of *Roy, Radhika R, ALABS >>*Sent:* Wednesday, May 19, 2004 07:18 >>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>*Cc:* Speechsc@ietf.org >>*Subject:* RE: [Speechsc] Media Server or Media Resource >> >>Eric, Klaus, and Sarvi: >>=20 >>Let me try to provide the definition of media servers: >>=20 >>"Media servers (MSs) typically operate with application servers (ASs)=20 >>to handle and terminate media streams, and provide services such as=20 >>announcement, media bridging, media transcoding, interactive voice=20 >>response (IVR) messages (with or without VocieXML), speech-to-text=20 >>(STT) conversion, text-to-speech (TTS) conversion, and others." >>=20 >>Cheers! >>=20 >>Radhika R. Roy >>AT&T >>732 420 1580 >> >> -----Original Message----- >> *From:* speechsc-admin@ietf.org >> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >> *Sent:* Wednesday, May 19, 2004 5:07 AM >> *To:* 'Sarvi Shanmugham'; Eric Burger >> *Cc:* Speechsc@ietf.org >> *Subject:* RE: [Speechsc] Media Server or Media Resource >> >> Hi Eric and Sarvi, >> =20 >> after some internal discussions I prefer to stay with the term >> "media server"! >> =20 >> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >> that was referenced in the speechsc requirements document) the >> following definition of a media server can be found (section 3 on >> page 3): >> "Media servers are devices that perform media processing on >> real-time packet media." >> According to this definition the MRCP server is a media server >> (and not the platform that uses MRCP servers for media processing, >> which becomes a media proxy).=20 >> In a network architecture that includes MRCP servers there might >> be other media servers. >> =20 >> Could someone point me to the documents of the IETF, 3GPP, ... >> where I can find their definition of a media server. The term >> "media server" is used fairly often (especially in product >> brochures), but it seems to be difficult to find precise = definitions. >> =20 >> Thanks, >> Klaus >> =20 >> =20 >> >> -----Original Message----- >> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >> *Sent:* Mittwoch, 19. Mai 2004 01:49 >> *To:* Garland Sharratt >> *Cc:* Eric Burger; Speechsc@ietf.org >> *Subject:* Re: [Speechsc] Media Server or Media Resource >> >> This is fine by me. And I haven't heard any opposition so far. >> I will make the necessary edits. >> >> Sarvi >> Garland Sharratt wrote: >> >> =20 >> >>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>waters, I think, and implies the two things are the same whereas they = are >>>not. >>> >>>Garland >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On = Behalf >>>Of Jeff Haynie >>>Sent: Monday, May 17, 2004 08:10 >>>To: Eric Burger >>>Cc: Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>That's funny - I myself have struggled with the same term and would = be >>>much more in favor of "media resource". >>> >>>Jeff >>> >>>Eric Burger wrote: >>> >>>=20 >>> >>> =20 >>> >>>> >>>>I have a form issue, not necessarily a substance issue. >>>> >>>>Throughout the MRCPv2 document, the "thing that is a server = controlled by >>>>the MRCPv2 protocol" is called a "Media Server". >>>> >>>>A Media Server is a device that has a well-defined meaning, in the = IETF, >>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>> >>>>That definition, IMHO, does not really match with "the thing that is = a >>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>> =20 >>>> >>>> =20 >>>> >>>embodies >>>=20 >>> >>> =20 >>> >>>>the accepted version of a Media Server is often a *client* to the = MRCPv2 >>>>protocol. >>>> >>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>resource/g throughout the document? >>>> >>>>Rationale: The document describes the Media RESOURCE Control = Protocol, not >>>>the Media SERVER Control Protocol. >>>> >>>> >>>> >>>>Thoughts? Comments? >>>> >>>>_______________________________________________ >>>>Speechsc mailing list >>>>Speechsc@ietf.org >>>>https://www1.ietf.org/mailman/listinfo/speechsc >>>> >>>> >>>> =20 >>>> >>>> =20 >>>> >>>_______________________________________________ >>>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 >>> >>>=20 >>> >>> =20 >>> > > >_______________________________________________ >Speechsc mailing list >Speechsc@ietf.org >https://www1.ietf.org/mailman/listinfo/speechsc > =20 > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 20 17:52:02 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28804 for ; Thu, 20 May 2004 17:52:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvKP-0003mA-So for speechsc-archive@odin.ietf.org; Thu, 20 May 2004 17:43:50 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KLhn35014509 for speechsc-archive@odin.ietf.org; Thu, 20 May 2004 17:43:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQv92-0007DI-8T for speechsc-web-archive@optimus.ietf.org; Thu, 20 May 2004 17:32:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27319 for ; Thu, 20 May 2004 17:32:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQv8z-0001iH-QQ for speechsc-web-archive@ietf.org; Thu, 20 May 2004 17:32:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQv71-0001Mf-00 for speechsc-web-archive@ietf.org; Thu, 20 May 2004 17:30:04 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQv3Q-0000q5-00 for speechsc-web-archive@ietf.org; Thu, 20 May 2004 17:26:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQumk-00077w-B5; Thu, 20 May 2004 17:09:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQu1B-0000oD-1H for speechsc@optimus.ietf.org; Thu, 20 May 2004 16:19:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18472 for ; Thu, 20 May 2004 16:19:50 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQu19-0007H3-82 for speechsc@ietf.org; Thu, 20 May 2004 16:19:51 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQu0B-0007BX-00 for speechsc@ietf.org; Thu, 20 May 2004 16:18:53 -0400 Received: from vtg-um-e2k1.cisco.com ([171.70.93.55] helo=vtg-um-e2k1.sj21ad.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BQtzD-00075n-00 for Speechsc@ietf.org; Thu, 20 May 2004 16:17:51 -0400 Received: from cisco.com ([10.32.130.132]) by vtg-um-e2k1.sj21ad.cisco.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 20 May 2004 13:17:21 -0700 Message-ID: <40AD1271.5020306@cisco.com> Date: Thu, 20 May 2004 13:17:53 -0700 From: Sarvi Shanmugham Organization: Cisco Systems Inc. User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Roy, Radhika R, ALABS" CC: Jeff Haynie , Garland Sharratt , Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource References: <34DA635B184A644DA4588E260EC0A25A07217383@ACCLUST02EVS1.ugd.att.com> In-Reply-To: <34DA635B184A644DA4588E260EC0A25A07217383@ACCLUST02EVS1.ugd.att.com> Content-Type: multipart/alternative; boundary="------------010907080608060503090900" X-OriginalArrivalTime: 20 May 2004 20:17:21.0594 (UTC) FILETIME=[74F5C1A0:01C43EA7] Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_MESSAGE, HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. --------------010907080608060503090900 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Well from what I am hearing so far, a Media server is an entity that may support multiple media resources on it. But, the resources may not all be controlled by single protocol. So it would be a misnomer to call the whole box an "MRCP server" or "MRCP media server". But from the definitions flying around, it looks like people do agree that the box as a whole can be called/classified as a "Media server" without any protocol implications. So here is a suggestion, I propose we change all occurances of "MRCP server" or "MRCP Media server". I will instead use one of the following terms/phrases depending on the context. To refer to individual resources I will use "MRCP resource" or "MRCP media resource". To refer to the whole box that may have multiple media resources(MRCP or otherwise) I will use the phrase "Media Server" or "MRCP resources on the Media Server" as appropriate. Any thoughts. Sarvi Roy, Radhika R, ALABS wrote: >Jeff: > >OK, let us go back to analyze these terms: Media Resources and Media Server. > >That is, MRCP is used to control (many, if not all) "media resources" of a media server. > >Radhika > >-----Original Message----- >From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >Of Jeff Haynie >Sent: Wednesday, May 19, 2004 9:48 PM >To: Roy, Radhika R, ALABS >Cc: Garland Sharratt; Speechsc@ietf.org >Subject: Re: [Speechsc] Media Server or Media Resource > > >OK, sorry, I'm confused. Do you support using the term "media server" >or "media resource"? I can't tell from your response. Garland >suggested in the original post that he favored the term "media resource" >too. > >Jeff > >Roy, Radhika R, ALABS wrote: > > > >>Jeff: >> >>Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. >> >>In this sense, MRCP is one of the protocols that is used for its media resources control. >> >>Who knows MRCP may NOT enough to control all the media resources of a Media Server. >> >>Let us see the big picture of a media server. >> >>Radhika >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>Of Jeff Haynie >>Sent: Wednesday, May 19, 2004 8:57 PM >>To: Garland Sharratt >>Cc: Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>Both you and Radhika seem to highlight exactly what MRCP is NOT and >>re-enforce Eric's original request, no? Of course, I'm not implying >>that media servers can't also support the MRCP protocol as a fact of >>implementation - that's something that's completely within reason. >> >>Jeff >> >>Garland Sharratt wrote: >> >> >> >> >> >>>To Radhika's list I would also add recording and playback, as well as >>>video announcements, video recording and playback, and video bridging. >>> >>>"Media server" is a generic term in NGN for a multi-purpose slave >>>media processing engine controlled by a call agent or application >>>server. All NGN architectures have a media server component, often by >>>another name; in 3GPP, for instance, it's called an Media Resource >>>Function Processor (MRFP). Media server control interfaces in NGN >>>architectures are MGCP, H.248, and SIP. >>> >>>Garland >>> >>>-----Original Message----- >>>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On >>>Behalf Of *Roy, Radhika R, ALABS >>>*Sent:* Wednesday, May 19, 2004 07:18 >>>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>>*Cc:* Speechsc@ietf.org >>>*Subject:* RE: [Speechsc] Media Server or Media Resource >>> >>>Eric, Klaus, and Sarvi: >>> >>>Let me try to provide the definition of media servers: >>> >>>"Media servers (MSs) typically operate with application servers (ASs) >>>to handle and terminate media streams, and provide services such as >>>announcement, media bridging, media transcoding, interactive voice >>>response (IVR) messages (with or without VocieXML), speech-to-text >>>(STT) conversion, text-to-speech (TTS) conversion, and others." >>> >>>Cheers! >>> >>>Radhika R. Roy >>>AT&T >>>732 420 1580 >>> >>> -----Original Message----- >>> *From:* speechsc-admin@ietf.org >>> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >>> *Sent:* Wednesday, May 19, 2004 5:07 AM >>> *To:* 'Sarvi Shanmugham'; Eric Burger >>> *Cc:* Speechsc@ietf.org >>> *Subject:* RE: [Speechsc] Media Server or Media Resource >>> >>> Hi Eric and Sarvi, >>> >>> after some internal discussions I prefer to stay with the term >>> "media server"! >>> >>> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >>> that was referenced in the speechsc requirements document) the >>> following definition of a media server can be found (section 3 on >>> page 3): >>> "Media servers are devices that perform media processing on >>> real-time packet media." >>> According to this definition the MRCP server is a media server >>> (and not the platform that uses MRCP servers for media processing, >>> which becomes a media proxy). >>> In a network architecture that includes MRCP servers there might >>> be other media servers. >>> >>> Could someone point me to the documents of the IETF, 3GPP, ... >>> where I can find their definition of a media server. The term >>> "media server" is used fairly often (especially in product >>> brochures), but it seems to be difficult to find precise definitions. >>> >>> Thanks, >>> Klaus >>> >>> >>> >>> -----Original Message----- >>> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >>> *Sent:* Mittwoch, 19. Mai 2004 01:49 >>> *To:* Garland Sharratt >>> *Cc:* Eric Burger; Speechsc@ietf.org >>> *Subject:* Re: [Speechsc] Media Server or Media Resource >>> >>> This is fine by me. And I haven't heard any opposition so far. >>> I will make the necessary edits. >>> >>> Sarvi >>> Garland Sharratt wrote: >>> >>> >>> >>> >>> >>>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>>waters, I think, and implies the two things are the same whereas they are >>>>not. >>>> >>>>Garland >>>> >>>>-----Original Message----- >>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>>Of Jeff Haynie >>>>Sent: Monday, May 17, 2004 08:10 >>>>To: Eric Burger >>>>Cc: Speechsc@ietf.org >>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>> >>>> >>>>That's funny - I myself have struggled with the same term and would be >>>>much more in favor of "media resource". >>>> >>>>Jeff >>>> >>>>Eric Burger wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>> >>>>>I have a form issue, not necessarily a substance issue. >>>>> >>>>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>>>the MRCPv2 protocol" is called a "Media Server". >>>>> >>>>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>>> >>>>>That definition, IMHO, does not really match with "the thing that is a >>>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>embodies >>>> >>>> >>>> >>>> >>>> >>>> >>>>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>>>protocol. >>>>> >>>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>>resource/g throughout the document? >>>>> >>>>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>>>the Media SERVER Control Protocol. >>>>> >>>>> >>>>> >>>>>Thoughts? Comments? >>>>> >>>>>_______________________________________________ >>>>>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 >>>> >>>> >>>>_______________________________________________ >>>>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 >> >> >> >> > > >_______________________________________________ >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 > > > --------------010907080608060503090900 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Well from what I am hearing so far, a Media server is an entity that may support multiple media resources on it.  But, the resources may not all be controlled by single protocol.

So it would be a misnomer to call the whole box an "MRCP server" or "MRCP media server". 
But  from the definitions flying around, it looks like people do agree that the box as a whole can be called/classified as a "Media server" without any protocol implications.

So here is a suggestion, I propose we change all occurances of "MRCP server" or "MRCP Media server".
I will instead use one of the following terms/phrases depending on the context.
    To refer to individual resources I will use "MRCP resource" or  "MRCP media resource".
    To refer to the whole box that may have multiple media resources(MRCP or otherwise) I will use the phrase  "Media Server" or "MRCP resources on the Media Server" as appropriate.

Any thoughts.

Sarvi

Roy, Radhika R, ALABS wrote: 
Jeff:

OK, let us go back to analyze these terms: Media Resources and Media Server.

That is, MRCP is used to control (many, if not all) "media resources" of a media server.

Radhika

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Wednesday, May 19, 2004 9:48 PM
To: Roy, Radhika R, ALABS
Cc: Garland Sharratt; Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


OK, sorry, I'm confused.  Do you support using the term "media server" 
or "media resource"?  I can't tell from your response.  Garland 
suggested in the original post that he favored the term "media resource" 
too.

Jeff

Roy, Radhika R, ALABS wrote:

  
Jeff:

Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them.

In this sense, MRCP is one of the protocols that is used for its media resources control. 

Who knows MRCP may NOT enough to control all the media resources of a Media Server.

Let us see the big picture of a media server.

Radhika

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Wednesday, May 19, 2004 8:57 PM
To: Garland Sharratt
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


Both you and Radhika seem to highlight exactly what MRCP is NOT and 
re-enforce Eric's original request, no?  Of course, I'm not implying 
that media servers can't also support the MRCP protocol as a fact of 
implementation - that's something that's completely within reason.

Jeff

Garland Sharratt wrote:

 

    
To Radhika's list I would also add recording and playback, as well as 
video announcements, video recording and playback, and video bridging.

"Media server" is a generic term in NGN for a multi-purpose slave 
media processing engine controlled by a call agent or application 
server.  All NGN architectures have a media server component, often by 
another name; in 3GPP, for instance, it's called an Media Resource 
Function Processor (MRFP).  Media server control interfaces in NGN 
architectures are MGCP, H.248, and SIP.

Garland

-----Original Message-----
*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On 
Behalf Of *Roy, Radhika R, ALABS
*Sent:* Wednesday, May 19, 2004 07:18
*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger
*Cc:* Speechsc@ietf.org
*Subject:* RE: [Speechsc] Media Server or Media Resource

Eric, Klaus, and Sarvi:

Let me try to provide the definition of media servers:

"Media servers (MSs) typically operate with application servers (ASs) 
to handle and terminate media streams, and provide services such as 
announcement, media bridging, media transcoding, interactive voice 
response (IVR) messages (with or without VocieXML), speech-to-text 
(STT) conversion, text-to-speech (TTS) conversion, and others."

Cheers!

Radhika R. Roy
AT&T
732 420 1580

   -----Original Message-----
   *From:* speechsc-admin@ietf.org
   [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus
   *Sent:* Wednesday, May 19, 2004 5:07 AM
   *To:* 'Sarvi Shanmugham'; Eric Burger
   *Cc:* Speechsc@ietf.org
   *Subject:* RE: [Speechsc] Media Server or Media Resource

   Hi Eric and Sarvi,
    
   after some internal discussions I prefer to stay with the term
   "media server"!
    
   In draft-burger-sipping-msuri-01.txt (expired IETF internet draft,
   that was referenced in the speechsc requirements document) the
   following definition of a media server can be found (section 3 on
   page 3):
   "Media servers are devices that perform media processing on
   real-time packet media."
   According to this definition the MRCP server is a media server
   (and not the platform that uses MRCP servers for media processing,
   which becomes a media proxy). 
   In a network architecture that includes MRCP servers there might
   be other media servers.
    
   Could someone point me to the documents of the IETF, 3GPP, ...
   where I can find their definition of a media server. The term
   "media server" is used fairly often (especially in product
   brochures), but it seems to be difficult to find precise definitions.
    
   Thanks,
   Klaus
    
    

       -----Original Message-----
       *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com]
       *Sent:* Mittwoch, 19. Mai 2004 01:49
       *To:* Garland Sharratt
       *Cc:* Eric Burger; Speechsc@ietf.org
       *Subject:* Re: [Speechsc] Media Server or Media Resource

       This is fine by me. And I haven't heard any opposition so far.
        I will make the necessary edits.

       Sarvi
       Garland Sharratt wrote:

   

      
Eric, I concur.  Using the term "media server" for MRCPv2 muddies the
waters, I think, and implies the two things are the same whereas they are
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would be
much more in favor of "media resource".

Jeff

Eric Burger wrote:



     

        
<ChairHat state="off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server controlled by
the MRCPv2 protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the IETF,
3GPP (MRF), SIP Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that is a
server controlled by the MRCPv2 protocol."  In fact, the thing that
  

       

          
embodies


     

        
the accepted version of a Media Server is often a *client* to the MRCPv2
protocol.

Would anyone be really put out if we did a 1,$:s/media server/media
resource/g throughout the document?

Rationale: The document describes the Media RESOURCE Control Protocol, not
the Media SERVER Control Protocol.

</ChairHat>

Thoughts?  Comments?

_______________________________________________
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


_______________________________________________
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
 

    


_______________________________________________
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

--------------010907080608060503090900-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 20 18:00:39 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29354 for ; Thu, 20 May 2004 18:00:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvPI-0006aX-80 for speechsc-archive@odin.ietf.org; Thu, 20 May 2004 17:48:52 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KLmqJt025326 for speechsc-archive@odin.ietf.org; Thu, 20 May 2004 17:48:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvGe-0002CZ-JH for speechsc-web-archive@optimus.ietf.org; Thu, 20 May 2004 17:39:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27861 for ; Thu, 20 May 2004 17:39:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQvGc-0002S1-74 for speechsc-web-archive@ietf.org; Thu, 20 May 2004 17:39:54 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQvFg-0002M9-00 for speechsc-web-archive@ietf.org; Thu, 20 May 2004 17:38:58 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQvEl-0002Gy-00 for speechsc-web-archive@ietf.org; Thu, 20 May 2004 17:37:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQv0O-0003K9-7G; Thu, 20 May 2004 17:23:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQuaa-00025f-Tr for speechsc@optimus.ietf.org; Thu, 20 May 2004 16:56:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22434 for ; Thu, 20 May 2004 16:56:25 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQuaY-0004PW-P3 for speechsc@ietf.org; Thu, 20 May 2004 16:56:26 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQuWq-0003l5-00 for speechsc@ietf.org; Thu, 20 May 2004 16:52:42 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BQuUr-0003MJ-02 for Speechsc@ietf.org; Thu, 20 May 2004 16:50:33 -0400 Received: from cerbrus.convedia.com ([216.129.93.50]) by mx2.foretec.com with esmtp (Exim 4.24) id 1BQuKK-0000qH-MI for Speechsc@ietf.org; Thu, 20 May 2004 16:39:40 -0400 Received: from mailhost.convedia.com (ladon [192.168.208.15]) by cerbrus.convedia.com (8.12.9/8.12.9) with ESMTP id i4KKKoEv012073; Thu, 20 May 2004 13:20:50 -0700 (PDT) Received: from laptop33 ([192.168.209.4]) by mailhost.convedia.com (8.12.9/8.12.9) with SMTP id i4KKWhjU026232; Thu, 20 May 2004 13:32:43 -0700 (PDT) From: "Garland Sharratt" To: "Sarvi Shanmugham" Cc: Subject: RE: [Speechsc] Media Server or Media Resource Date: Thu, 20 May 2004 13:32:44 -0700 Keywords: .aa Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004D_01C43E6E.EE83B470" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <40AD1271.5020306@cisco.com> Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_FONTCOLOR_BLUE, HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_004D_01C43E6E.EE83B470 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sarvi, I view a "media server" as a general-purpose media processing entity, whereas an MRCP server is special purpose, for speech only. Similarly I don't regard MRCP as a media server control interface (they are SIP, MGCP, and H.248) because it's not general purpose, rather it's a speech server control language. I think the whole idea of a media server is in fact its general-purpose nature and its applicability to a wide range of applications and services, all controlled through a single general-purpose control interface. So I'd suggest that something like "speech server" would be a better name for the MRCP server. Garland -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Thursday, May 20, 2004 13:18 To: Roy, Radhika R, ALABS Cc: Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource Well from what I am hearing so far, a Media server is an entity that may support multiple media resources on it. But, the resources may not all be controlled by single protocol. So it would be a misnomer to call the whole box an "MRCP server" or "MRCP media server". But from the definitions flying around, it looks like people do agree that the box as a whole can be called/classified as a "Media server" without any protocol implications. So here is a suggestion, I propose we change all occurances of "MRCP server" or "MRCP Media server". I will instead use one of the following terms/phrases depending on the context. To refer to individual resources I will use "MRCP resource" or "MRCP media resource". To refer to the whole box that may have multiple media resources(MRCP or otherwise) I will use the phrase "Media Server" or "MRCP resources on the Media Server" as appropriate. Any thoughts. Sarvi Roy, Radhika R, ALABS wrote: Jeff: OK, let us go back to analyze these terms: Media Resources and Media Server. That is, MRCP is used to control (many, if not all) "media resources" of a media server. Radhika -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Jeff Haynie Sent: Wednesday, May 19, 2004 9:48 PM To: Roy, Radhika R, ALABS Cc: Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource OK, sorry, I'm confused. Do you support using the term "media server" or "media resource"? I can't tell from your response. Garland suggested in the original post that he favored the term "media resource" too. Jeff Roy, Radhika R, ALABS wrote: Jeff: Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. In this sense, MRCP is one of the protocols that is used for its media resources control. Who knows MRCP may NOT enough to control all the media resources of a Media Server. Let us see the big picture of a media server. Radhika -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Jeff Haynie Sent: Wednesday, May 19, 2004 8:57 PM To: Garland Sharratt Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource Both you and Radhika seem to highlight exactly what MRCP is NOT and re-enforce Eric's original request, no? Of course, I'm not implying that media servers can't also support the MRCP protocol as a fact of implementation - that's something that's completely within reason. Jeff Garland Sharratt wrote: To Radhika's list I would also add recording and playback, as well as video announcements, video recording and playback, and video bridging. "Media server" is a generic term in NGN for a multi-purpose slave media processing engine controlled by a call agent or application server. All NGN architectures have a media server component, often by another name; in 3GPP, for instance, it's called an Media Resource Function Processor (MRFP). Media server control interfaces in NGN architectures are MGCP, H.248, and SIP. Garland -----Original Message----- *From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On Behalf Of *Roy, Radhika R, ALABS *Sent:* Wednesday, May 19, 2004 07:18 *To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger *Cc:* Speechsc@ietf.org *Subject:* RE: [Speechsc] Media Server or Media Resource Eric, Klaus, and Sarvi: Let me try to provide the definition of media servers: "Media servers (MSs) typically operate with application servers (ASs) to handle and terminate media streams, and provide services such as announcement, media bridging, media transcoding, interactive voice response (IVR) messages (with or without VocieXML), speech-to-text (STT) conversion, text-to-speech (TTS) conversion, and others." Cheers! Radhika R. Roy AT&T 732 420 1580 -----Original Message----- *From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus *Sent:* Wednesday, May 19, 2004 5:07 AM *To:* 'Sarvi Shanmugham'; Eric Burger *Cc:* Speechsc@ietf.org *Subject:* RE: [Speechsc] Media Server or Media Resource Hi Eric and Sarvi, after some internal discussions I prefer to stay with the term "media server"! In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that was referenced in the speechsc requirements document) the following definition of a media server can be found (section 3 on page 3): "Media servers are devices that perform media processing on real-time packet media." According to this definition the MRCP server is a media server (and not the platform that uses MRCP servers for media processing, which becomes a media proxy). In a network architecture that includes MRCP servers there might be other media servers. Could someone point me to the documents of the IETF, 3GPP, ... where I can find their definition of a media server. The term "media server" is used fairly often (especially in product brochures), but it seems to be difficult to find precise definitions. Thanks, Klaus -----Original Message----- *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] *Sent:* Mittwoch, 19. Mai 2004 01:49 *To:* Garland Sharratt *Cc:* Eric Burger; Speechsc@ietf.org *Subject:* Re: [Speechsc] Media Server or Media Resource This is fine by me. And I haven't heard any opposition so far. I will make the necessary edits. Sarvi Garland Sharratt wrote: Eric, I concur. Using the term "media server" for MRCPv2 muddies the waters, I think, and implies the two things are the same whereas they are not. Garland -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Jeff Haynie Sent: Monday, May 17, 2004 08:10 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource That's funny - I myself have struggled with the same term and would be much more in favor of "media resource". Jeff Eric Burger wrote: I have a form issue, not necessarily a substance issue. Throughout the MRCPv2 document, the "thing that is a server controlled by the MRCPv2 protocol" is called a "Media Server". A Media Server is a device that has a well-defined meaning, in the IETF, 3GPP (MRF), SIP Forum, IPCC, etc. That definition, IMHO, does not really match with "the thing that is a server controlled by the MRCPv2 protocol." In fact, the thing that embodies the accepted version of a Media Server is often a *client* to the MRCPv2 protocol. Would anyone be really put out if we did a 1,$:s/media server/media resource/g throughout the document? Rationale: The document describes the Media RESOURCE Control Protocol, not the Media SERVER Control Protocol. Thoughts? Comments? _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 ------=_NextPart_000_004D_01C43E6E.EE83B470 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
Sarvi,=20 I view a "media server" as a general-purpose media processing entity, = whereas an=20 MRCP server is special purpose, for speech only.  Similarly I don't = regard=20 MRCP as a media server control interface (they are SIP, MGCP, and H.248) = because=20 it's not general purpose, rather it's a speech server control = language. =20
 
I=20 think the whole idea of a media server is in fact its general-purpose = nature and=20 its applicability to a wide range of applications and services, all = controlled=20 through a single general-purpose control interface.
 
So I'd=20 suggest that something like "speech server" would be a better name for = the MRCP=20 server.
 
Garland
 
-----Original Message-----
From: Sarvi Shanmugham=20 [mailto:sarvi@cisco.com]
Sent: Thursday, May 20, 2004=20 13:18
To: Roy, Radhika R, ALABS
Cc: Jeff Haynie; = Garland=20 Sharratt; Speechsc@ietf.org
Subject: Re: [Speechsc] Media = Server or=20 Media Resource

Well from what I am hearing so far, a = Media=20 server is an entity that may support multiple media resources on = it.  But,=20 the resources may not all be controlled by single protocol.

So = it would=20 be a misnomer to call the whole box an "MRCP server" or "MRCP media=20 server". 
But  from the definitions flying around, it = looks like=20 people do agree that the box as a whole can be called/classified as a = "Media=20 server" without any protocol implications.

So here is a = suggestion, I=20 propose we change all occurances of "MRCP server" or "MRCP Media = server".
I=20 will instead use one of the following terms/phrases depending on the=20 context.
    To refer to individual resources I will use = "MRCP=20 resource" or  "MRCP media resource".
    To refer = to the=20 whole box that may have multiple media resources(MRCP or otherwise) I = will use=20 the phrase  "Media Server" or "MRCP resources on the Media Server" = as=20 appropriate.

Any thoughts.

Sarvi

Roy, Radhika R, = ALABS=20 wrote:=20 
Jeff:

OK, let us go back to analyze these terms: Media Resources and Media =
Server.

That is, MRCP is used to control (many, if not all) "media resources" of =
a media server.

Radhika

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Wednesday, May 19, 2004 9:48 PM
To: Roy, Radhika R, ALABS
Cc: Garland Sharratt; Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


OK, sorry, I'm confused.  Do you support using the term "media server"=20
or "media resource"?  I can't tell from your response.  Garland=20
suggested in the original post that he favored the term "media resource" =

too.

Jeff

Roy, Radhika R, ALABS wrote:

  
Jeff:

Garland and I have been saying exactly what a media server is. A media =
server will be using many protocols, and MRCP is only of them.

In this sense, MRCP is one of the protocols that is used for its media =
resources control.=20

Who knows MRCP may NOT enough to control all the media resources of a =
Media Server.

Let us see the big picture of a media server.

Radhika

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Wednesday, May 19, 2004 8:57 PM
To: Garland Sharratt
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


Both you and Radhika seem to highlight exactly what MRCP is NOT and=20
re-enforce Eric's original request, no?  Of course, I'm not implying=20
that media servers can't also support the MRCP protocol as a fact of=20
implementation - that's something that's completely within reason.

Jeff

Garland Sharratt wrote:

=20

    
To Radhika's list I would =
also add recording and playback, as well as=20
video announcements, video recording and playback, and video bridging.

"Media server" is a generic term in NGN for a multi-purpose slave=20
media processing engine controlled by a call agent or application=20
server.  All NGN architectures have a media server component, often by=20
another name; in 3GPP, for instance, it's called an Media Resource=20
Function Processor (MRFP).  Media server control interfaces in NGN=20
architectures are MGCP, H.248, and SIP.

Garland

-----Original Message-----
*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On=20
Behalf Of *Roy, Radhika R, ALABS
*Sent:* Wednesday, May 19, 2004 07:18
*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger
*Cc:* Speechsc@ietf.org
*Subject:* RE: [Speechsc] Media Server or Media Resource

Eric, Klaus, and Sarvi:

Let me try to provide the definition of media servers:

"Media servers (MSs) typically operate with application servers (ASs)=20
to handle and terminate media streams, and provide services such as=20
announcement, media bridging, media transcoding, interactive voice=20
response (IVR) messages (with or without VocieXML), speech-to-text=20
(STT) conversion, text-to-speech (TTS) conversion, and others."

Cheers!

Radhika R. Roy
AT&T
732 420 1580

   -----Original Message-----
   *From:* speechsc-admin@ietf.org
   [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus
   *Sent:* Wednesday, May 19, 2004 5:07 AM
   *To:* 'Sarvi Shanmugham'; Eric Burger
   *Cc:* Speechsc@ietf.org
   *Subject:* RE: [Speechsc] Media Server or Media Resource

   Hi Eric and Sarvi,
   =20
   after some internal discussions I prefer to stay with the term
   "media server"!
   =20
   In draft-burger-sipping-msuri-01.txt (expired IETF internet draft,
   that was referenced in the speechsc requirements document) the
   following definition of a media server can be found (section 3 on
   page 3):
   "Media servers are devices that perform media processing on
   real-time packet media."
   According to this definition the MRCP server is a media server
   (and not the platform that uses MRCP servers for media processing,
   which becomes a media proxy).=20
   In a network architecture that includes MRCP servers there might
   be other media servers.
   =20
   Could someone point me to the documents of the IETF, 3GPP, ...
   where I can find their definition of a media server. The term
   "media server" is used fairly often (especially in product
   brochures), but it seems to be difficult to find precise definitions.
   =20
   Thanks,
   Klaus
   =20
   =20

       -----Original Message-----
       *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com]
       *Sent:* Mittwoch, 19. Mai 2004 01:49
       *To:* Garland Sharratt
       *Cc:* Eric Burger; Speechsc@ietf.org
       *Subject:* Re: [Speechsc] Media Server or Media Resource

       This is fine by me. And I haven't heard any opposition so far.
        I will make the necessary edits.

       Sarvi
       Garland Sharratt wrote:

  =20

      
Eric, I concur.  Using =
the term "media server" for MRCPv2 muddies the
waters, I think, and implies the two things are the same whereas they =
are
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would be
much more in favor of "media resource".

Jeff

Eric Burger wrote:



    =20

        
<ChairHat =
state=3D"off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server controlled =
by
the MRCPv2 protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the IETF,
3GPP (MRF), SIP Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that is a
server controlled by the MRCPv2 protocol."  In fact, the thing that
 =20

      =20

          
embodies


    =20

        
the accepted version of =
a Media Server is often a *client* to the MRCPv2
protocol.

Would anyone be really put out if we did a 1,$:s/media server/media
resource/g throughout the document?

Rationale: The document describes the Media RESOURCE Control Protocol, =
not
the Media SERVER Control Protocol.

</ChairHat>

Thoughts?  Comments?

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


 =20

      =20

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


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



    =20

        
_______________________________________________
Speechsc mailing list
Speechsc@ietf.org
https://www1.iet=
f.org/mailman/listinfo/speechsc
=20

    


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

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

------=_NextPart_000_004D_01C43E6E.EE83B470-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Thu May 20 18:23:37 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02075 for ; Thu, 20 May 2004 18:23:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvjp-00005D-4x for speechsc-archive@odin.ietf.org; Thu, 20 May 2004 18:10:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KMA5jw000313 for speechsc-archive@odin.ietf.org; Thu, 20 May 2004 18:10:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvez-0005gQ-DA for speechsc-web-archive@optimus.ietf.org; Thu, 20 May 2004 18:05:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29870 for ; Thu, 20 May 2004 18:05:01 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQvew-0004LV-Ky for speechsc-web-archive@ietf.org; Thu, 20 May 2004 18:05:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQve4-0004Ic-00 for speechsc-web-archive@ietf.org; Thu, 20 May 2004 18:04:10 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQvdk-0004FE-00 for speechsc-web-archive@ietf.org; Thu, 20 May 2004 18:03:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvb8-0002XC-Kh; Thu, 20 May 2004 18:01:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvSH-0007fE-Ju for speechsc@optimus.ietf.org; Thu, 20 May 2004 17:51:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28793 for ; Thu, 20 May 2004 17:51:53 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQvSF-0003Qs-03 for speechsc@ietf.org; Thu, 20 May 2004 17:51:55 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQvRL-0003ML-00 for speechsc@ietf.org; Thu, 20 May 2004 17:51:00 -0400 Received: from cerbrus.convedia.com ([216.129.93.50]) by ietf-mx with esmtp (Exim 4.12) id 1BQvQV-0003Cz-00 for Speechsc@ietf.org; Thu, 20 May 2004 17:50:07 -0400 Received: from mailhost.convedia.com (ladon [192.168.208.15]) by cerbrus.convedia.com (8.12.9/8.12.9) with ESMTP id i4KLbZEv012267; Thu, 20 May 2004 14:37:35 -0700 (PDT) Received: from convedia.com (dhcp-198 [192.168.208.198]) by mailhost.convedia.com (8.12.9/8.12.9) with ESMTP id i4KLnTjU004258; Thu, 20 May 2004 14:49:29 -0700 (PDT) Message-ID: <40AD27E8.70605@convedia.com> Date: Thu, 20 May 2004 14:49:28 -0700 From: Tim Melanchuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sarvi Shanmugham CC: "Roy, Radhika R, ALABS" , Jeff Haynie , Garland Sharratt , Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource References: <34DA635B184A644DA4588E260EC0A25A07217383@ACCLUST02EVS1.ugd.att.com> <40AD1271.5020306@cisco.com> In-Reply-To: <40AD1271.5020306@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit this approach sounds reasonable. "media server" is somewhat of generic term that is used for slightly different things in different contexts. for example, rtsp uses the term media server extensively and defines it as: Media server: The server providing playback services for one or more media streams. Different media streams within a presentation may originate from different media servers. A media server may reside on the same or a different host as the web server the presentation is invoked from. Sarvi Shanmugham wrote: > Well from what I am hearing so far, a Media server is an entity that may > support multiple media resources on it. But, the resources may not all > be controlled by single protocol. > > So it would be a misnomer to call the whole box an "MRCP server" or > "MRCP media server". > But from the definitions flying around, it looks like people do agree > that the box as a whole can be called/classified as a "Media server" > without any protocol implications. > > So here is a suggestion, I propose we change all occurances of "MRCP > server" or "MRCP Media server". > I will instead use one of the following terms/phrases depending on the > context. > To refer to individual resources I will use "MRCP resource" or > "MRCP media resource". > To refer to the whole box that may have multiple media > resources(MRCP or otherwise) I will use the phrase "Media Server" or > "MRCP resources on the Media Server" as appropriate. > > Any thoughts. > > Sarvi > > Roy, Radhika R, ALABS wrote: > >>Jeff: >> >>OK, let us go back to analyze these terms: Media Resources and Media Server. >> >>That is, MRCP is used to control (many, if not all) "media resources" of a media server. >> >>Radhika >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>Of Jeff Haynie >>Sent: Wednesday, May 19, 2004 9:48 PM >>To: Roy, Radhika R, ALABS >>Cc: Garland Sharratt; Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>OK, sorry, I'm confused. Do you support using the term "media server" >>or "media resource"? I can't tell from your response. Garland >>suggested in the original post that he favored the term "media resource" >>too. >> >>Jeff >> >>Roy, Radhika R, ALABS wrote: >> >> >> >>>Jeff: >>> >>>Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. >>> >>>In this sense, MRCP is one of the protocols that is used for its media resources control. >>> >>>Who knows MRCP may NOT enough to control all the media resources of a Media Server. >>> >>>Let us see the big picture of a media server. >>> >>>Radhika >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>Of Jeff Haynie >>>Sent: Wednesday, May 19, 2004 8:57 PM >>>To: Garland Sharratt >>>Cc: Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>Both you and Radhika seem to highlight exactly what MRCP is NOT and >>>re-enforce Eric's original request, no? Of course, I'm not implying >>>that media servers can't also support the MRCP protocol as a fact of >>>implementation - that's something that's completely within reason. >>> >>>Jeff >>> >>>Garland Sharratt wrote: >>> >>> >>> >>> >>> >>>>To Radhika's list I would also add recording and playback, as well as >>>>video announcements, video recording and playback, and video bridging. >>>> >>>>"Media server" is a generic term in NGN for a multi-purpose slave >>>>media processing engine controlled by a call agent or application >>>>server. All NGN architectures have a media server component, often by >>>>another name; in 3GPP, for instance, it's called an Media Resource >>>>Function Processor (MRFP). Media server control interfaces in NGN >>>>architectures are MGCP, H.248, and SIP. >>>> >>>>Garland >>>> >>>>-----Original Message----- >>>>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On >>>>Behalf Of *Roy, Radhika R, ALABS >>>>*Sent:* Wednesday, May 19, 2004 07:18 >>>>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>>>*Cc:* Speechsc@ietf.org >>>>*Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>>Eric, Klaus, and Sarvi: >>>> >>>>Let me try to provide the definition of media servers: >>>> >>>>"Media servers (MSs) typically operate with application servers (ASs) >>>>to handle and terminate media streams, and provide services such as >>>>announcement, media bridging, media transcoding, interactive voice >>>>response (IVR) messages (with or without VocieXML), speech-to-text >>>>(STT) conversion, text-to-speech (TTS) conversion, and others." >>>> >>>>Cheers! >>>> >>>>Radhika R. Roy >>>>AT&T >>>>732 420 1580 >>>> >>>> -----Original Message----- >>>> *From:* speechsc-admin@ietf.org >>>> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >>>> *Sent:* Wednesday, May 19, 2004 5:07 AM >>>> *To:* 'Sarvi Shanmugham'; Eric Burger >>>> *Cc:* Speechsc@ietf.org >>>> *Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>> Hi Eric and Sarvi, >>>> >>>> after some internal discussions I prefer to stay with the term >>>> "media server"! >>>> >>>> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >>>> that was referenced in the speechsc requirements document) the >>>> following definition of a media server can be found (section 3 on >>>> page 3): >>>> "Media servers are devices that perform media processing on >>>> real-time packet media." >>>> According to this definition the MRCP server is a media server >>>> (and not the platform that uses MRCP servers for media processing, >>>> which becomes a media proxy). >>>> In a network architecture that includes MRCP servers there might >>>> be other media servers. >>>> >>>> Could someone point me to the documents of the IETF, 3GPP, ... >>>> where I can find their definition of a media server. The term >>>> "media server" is used fairly often (especially in product >>>> brochures), but it seems to be difficult to find precise definitions. >>>> >>>> Thanks, >>>> Klaus >>>> >>>> >>>> >>>> -----Original Message----- >>>> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >>>> *Sent:* Mittwoch, 19. Mai 2004 01:49 >>>> *To:* Garland Sharratt >>>> *Cc:* Eric Burger; Speechsc@ietf.org >>>> *Subject:* Re: [Speechsc] Media Server or Media Resource >>>> >>>> This is fine by me. And I haven't heard any opposition so far. >>>> I will make the necessary edits. >>>> >>>> Sarvi >>>> Garland Sharratt wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>>>waters, I think, and implies the two things are the same whereas they are >>>>>not. >>>>> >>>>>Garland >>>>> >>>>>-----Original Message----- >>>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>>>Of Jeff Haynie >>>>>Sent: Monday, May 17, 2004 08:10 >>>>>To: Eric Burger >>>>>Cc: Speechsc@ietf.org >>>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>>> >>>>> >>>>>That's funny - I myself have struggled with the same term and would be >>>>>much more in favor of "media resource". >>>>> >>>>>Jeff >>>>> >>>>>Eric Burger wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>>I have a form issue, not necessarily a substance issue. >>>>>> >>>>>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>>>>the MRCPv2 protocol" is called a "Media Server". >>>>>> >>>>>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>>>> >>>>>>That definition, IMHO, does not really match with "the thing that is a >>>>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>embodies >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>>>>protocol. >>>>>> >>>>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>>>resource/g throughout the document? >>>>>> >>>>>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>>>>the Media SERVER Control Protocol. >>>>>> >>>>>> >>>>>> >>>>>>Thoughts? Comments? >>>>>> >>>>>>_______________________________________________ >>>>>>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 >>>>> >>>>> >>>>>_______________________________________________ >>>>>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 >>> >>> >>> >>> >> >> >>_______________________________________________ >>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 >> >> >> > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri May 21 00:26:59 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19414 for ; Fri, 21 May 2004 00:26:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR1aP-0004O0-MO for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 00:24:46 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4L4OjMw016860 for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 00:24:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR1WJ-0003X0-OA for speechsc-web-archive@optimus.ietf.org; Fri, 21 May 2004 00:20:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19063 for ; Fri, 21 May 2004 00:20:28 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR1WH-0004ns-Al for speechsc-web-archive@ietf.org; Fri, 21 May 2004 00:20:29 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR1Vh-0004fg-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 00:19:54 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BR1Uc-0004VT-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 00:18:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR1O4-0001GH-Rs; Fri, 21 May 2004 00:12:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR1MQ-0000a1-DG for speechsc@optimus.ietf.org; Fri, 21 May 2004 00:10:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18465 for ; Fri, 21 May 2004 00:10:14 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR1MN-0003hU-VB for speechsc@ietf.org; Fri, 21 May 2004 00:10:16 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR1Lb-0003bt-00 for speechsc@ietf.org; Fri, 21 May 2004 00:09:28 -0400 Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 1BR1KW-0003Pj-00 for Speechsc@ietf.org; Fri, 21 May 2004 00:08:20 -0400 Received: from attrh0i.attrh.att.com ([135.37.94.54]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id i4L47owl004867 for ; Thu, 20 May 2004 23:07:50 -0500 Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.9) by attrh0i.attrh.att.com (6.5.032) id 40951C4D0022D822; Fri, 21 May 2004 00:07:36 -0400 x-mimeole: Produced By Microsoft Exchange V6.0.6561.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] Media Server or Media Resource Date: Fri, 21 May 2004 00:07:49 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A0725E6AF@ACCLUST02EVS1.ugd.att.com> Thread-Topic: [Speechsc] Media Server or Media Resource Thread-Index: AcQ+tHz/h3XosY0uRgCFEl5y8Isl7QAMq2Tw From: "Roy, Radhika R, ALABS" To: "Tim Melanchuk" , "Sarvi Shanmugham" Cc: "Jeff Haynie" , "Garland Sharratt" , Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable All: Seeing all definitions, it appears that we can safely conclude what Sarvi has proposed: 1. "MRCP server" or "MRCP Media server" - (a media server that contains only MRCP media resources) 2. "MRCP resource" or "MRCP media resource" - (self explanatory) 3. "MRCP resources on the Media Server" - (a media server that contains MRCP resources in addition to other media resources) 4. "Media Server" - (a media server that contains MRCP plus other media resources in the context of our works) Items 3 and 4 are the same in the context of our works. Radhika -----Original Message----- From: Tim Melanchuk [mailto:timm@convedia.com] Sent: Thursday, May 20, 2004 5:49 PM To: Sarvi Shanmugham Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource this approach sounds reasonable. "media server" is somewhat of generic term that is used for slightly different things in different contexts. for example, rtsp uses the term media server extensively and defines it as: Media server: The server providing playback services for one or more media streams. Different media streams within a presentation may originate from different media servers. A media server may reside on the same or a different host as the web server the presentation is invoked from. Sarvi Shanmugham wrote: > Well from what I am hearing so far, a Media server is an entity that may=20 > support multiple media resources on it. But, the resources may not all=20 > be controlled by single protocol. >=20 > So it would be a misnomer to call the whole box an "MRCP server" or=20 > "MRCP media server".=20 > But from the definitions flying around, it looks like people do agree > that the box as a whole can be called/classified as a "Media server"=20 > without any protocol implications. >=20 > So here is a suggestion, I propose we change all occurances of "MRCP=20 > server" or "MRCP Media server". > I will instead use one of the following terms/phrases depending on the > context. > To refer to individual resources I will use "MRCP resource" or =20 > "MRCP media resource". > To refer to the whole box that may have multiple media=20 > resources(MRCP or otherwise) I will use the phrase "Media Server" or=20 > "MRCP resources on the Media Server" as appropriate. >=20 > Any thoughts. >=20 > Sarvi >=20 > Roy, Radhika R, ALABS wrote: >=20 >>Jeff: >> >>OK, let us go back to analyze these terms: Media Resources and Media Server. >> >>That is, MRCP is used to control (many, if not all) "media resources" of a media server. >> >>Radhika >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>Of Jeff Haynie >>Sent: Wednesday, May 19, 2004 9:48 PM >>To: Roy, Radhika R, ALABS >>Cc: Garland Sharratt; Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>OK, sorry, I'm confused. Do you support using the term "media server" >>or "media resource"? I can't tell from your response. Garland=20 >>suggested in the original post that he favored the term "media resource"=20 >>too. >> >>Jeff >> >>Roy, Radhika R, ALABS wrote: >> >> =20 >> >>>Jeff: >>> >>>Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. >>> >>>In this sense, MRCP is one of the protocols that is used for its media resources control.=20 >>> >>>Who knows MRCP may NOT enough to control all the media resources of a Media Server. >>> >>>Let us see the big picture of a media server. >>> >>>Radhika >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>Of Jeff Haynie >>>Sent: Wednesday, May 19, 2004 8:57 PM >>>To: Garland Sharratt >>>Cc: Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>Both you and Radhika seem to highlight exactly what MRCP is NOT and=20 >>>re-enforce Eric's original request, no? Of course, I'm not implying=20 >>>that media servers can't also support the MRCP protocol as a fact of=20 >>>implementation - that's something that's completely within reason. >>> >>>Jeff >>> >>>Garland Sharratt wrote: >>> >>>=20 >>> >>> =20 >>> >>>>To Radhika's list I would also add recording and playback, as well as=20 >>>>video announcements, video recording and playback, and video bridging. >>>> >>>>"Media server" is a generic term in NGN for a multi-purpose slave=20 >>>>media processing engine controlled by a call agent or application=20 >>>>server. All NGN architectures have a media server component, often by=20 >>>>another name; in 3GPP, for instance, it's called an Media Resource=20 >>>>Function Processor (MRFP). Media server control interfaces in NGN=20 >>>>architectures are MGCP, H.248, and SIP. >>>> >>>>Garland >>>> >>>>-----Original Message----- >>>>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On=20 >>>>Behalf Of *Roy, Radhika R, ALABS >>>>*Sent:* Wednesday, May 19, 2004 07:18 >>>>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>>>*Cc:* Speechsc@ietf.org >>>>*Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>>Eric, Klaus, and Sarvi: >>>> >>>>Let me try to provide the definition of media servers: >>>> >>>>"Media servers (MSs) typically operate with application servers (ASs)=20 >>>>to handle and terminate media streams, and provide services such as=20 >>>>announcement, media bridging, media transcoding, interactive voice=20 >>>>response (IVR) messages (with or without VocieXML), speech-to-text=20 >>>>(STT) conversion, text-to-speech (TTS) conversion, and others." >>>> >>>>Cheers! >>>> >>>>Radhika R. Roy >>>>AT&T >>>>732 420 1580 >>>> >>>> -----Original Message----- >>>> *From:* speechsc-admin@ietf.org >>>> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >>>> *Sent:* Wednesday, May 19, 2004 5:07 AM >>>> *To:* 'Sarvi Shanmugham'; Eric Burger >>>> *Cc:* Speechsc@ietf.org >>>> *Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>> Hi Eric and Sarvi, >>>> =20 >>>> after some internal discussions I prefer to stay with the term >>>> "media server"! >>>> =20 >>>> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >>>> that was referenced in the speechsc requirements document) the >>>> following definition of a media server can be found (section 3 on >>>> page 3): >>>> "Media servers are devices that perform media processing on >>>> real-time packet media." >>>> According to this definition the MRCP server is a media server >>>> (and not the platform that uses MRCP servers for media processing, >>>> which becomes a media proxy).=20 >>>> In a network architecture that includes MRCP servers there might >>>> be other media servers. >>>> =20 >>>> Could someone point me to the documents of the IETF, 3GPP, ... >>>> where I can find their definition of a media server. The term >>>> "media server" is used fairly often (especially in product >>>> brochures), but it seems to be difficult to find precise definitions. >>>> =20 >>>> Thanks, >>>> Klaus >>>> =20 >>>> =20 >>>> >>>> -----Original Message----- >>>> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >>>> *Sent:* Mittwoch, 19. Mai 2004 01:49 >>>> *To:* Garland Sharratt >>>> *Cc:* Eric Burger; Speechsc@ietf.org >>>> *Subject:* Re: [Speechsc] Media Server or Media Resource >>>> >>>> This is fine by me. And I haven't heard any opposition so far. >>>> I will make the necessary edits. >>>> >>>> Sarvi >>>> Garland Sharratt wrote: >>>> >>>> =20 >>>> >>>> =20 >>>> >>>>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>>>waters, I think, and implies the two things are the same whereas they are >>>>>not. >>>>> >>>>>Garland >>>>> >>>>>-----Original Message----- >>>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>>>Of Jeff Haynie >>>>>Sent: Monday, May 17, 2004 08:10 >>>>>To: Eric Burger >>>>>Cc: Speechsc@ietf.org >>>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>>> >>>>> >>>>>That's funny - I myself have struggled with the same term and would be >>>>>much more in favor of "media resource". >>>>> >>>>>Jeff >>>>> >>>>>Eric Burger wrote: >>>>> >>>>> >>>>> >>>>> =20 >>>>> >>>>> =20 >>>>> >>>>>> >>>>>>I have a form issue, not necessarily a substance issue. >>>>>> >>>>>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>>>>the MRCPv2 protocol" is called a "Media Server". >>>>>> >>>>>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>>>> >>>>>>That definition, IMHO, does not really match with "the thing that is a >>>>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>>>> =20 >>>>>> >>>>>> =20 >>>>>> >>>>>> =20 >>>>>> >>>>>embodies >>>>> >>>>> >>>>> =20 >>>>> >>>>> =20 >>>>> >>>>>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>>>>protocol. >>>>>> >>>>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>>>resource/g throughout the document? >>>>>> >>>>>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>>>>the Media SERVER Control Protocol. >>>>>> >>>>>> >>>>>> >>>>>>Thoughts? Comments? >>>>>> >>>>>>_______________________________________________ >>>>>>Speechsc mailing list >>>>>>Speechsc@ietf.org >>>>>>https://www1.ietf.org/mailman/listinfo/speechsc >>>>>> >>>>>> >>>>>> =20 >>>>>> >>>>>> =20 >>>>>> >>>>>> =20 >>>>>> >>>>>_______________________________________________ >>>>>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 >>>>> >>>>> >>>>> >>>>> =20 >>>>> >>>>> =20 >>>>> >>>_______________________________________________ >>>Speechsc mailing list >>>Speechsc@ietf.org >>>https://www1.ietf.org/mailman/listinfo/speechsc >>>=20 >>> >>> =20 >>> >> >> >>_______________________________________________ >>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 >> >> =20 >> >=20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri May 21 05:39:18 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18961 for ; Fri, 21 May 2004 05:39:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR6SM-0000Pt-KE for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 05:36:47 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4L9akfm001601 for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 05:36:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR6P8-0007bq-Su for speechsc-web-archive@optimus.ietf.org; Fri, 21 May 2004 05:33:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18509 for ; Fri, 21 May 2004 05:33:23 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR6P5-0007Ue-I5 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 05:33:23 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR6OB-0007LZ-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 05:32:29 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BR6NT-0007DS-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 05:31:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR67Z-00033t-LN; Fri, 21 May 2004 05:15:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR5x0-0008Ht-Hc for speechsc@optimus.ietf.org; Fri, 21 May 2004 05:04:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16980 for ; Fri, 21 May 2004 05:04:19 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR5wx-0003BT-8d for speechsc@ietf.org; Fri, 21 May 2004 05:04:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR5vy-00032R-00 for speechsc@ietf.org; Fri, 21 May 2004 05:03:19 -0400 Received: from [212.17.54.82] (helo=mail.voxpilot.com) by ietf-mx with esmtp (Exim 4.12) id 1BR5vA-0002rf-00 for Speechsc@ietf.org; Fri, 21 May 2004 05:02:28 -0400 Received: from daburkew2k (unknown [10.0.0.202]) by mail.voxpilot.com (Postfix) with ESMTP id 6E70821403D; Fri, 21 May 2004 10:07:47 +0100 (IST) Message-ID: <001501c43f12$574e5890$ca00000a@db01.voxpilot.com> From: "Dave Burke" To: "Roy, Radhika R, ALABS" , "Tim Melanchuk" , "Sarvi Shanmugham" Cc: "Jeff Haynie" , "Garland Sharratt" , References: <34DA635B184A644DA4588E260EC0A25A0725E6AF@ACCLUST02EVS1.ugd.att.com> Subject: Re: [Speechsc] Media Server or Media Resource Date: Fri, 21 May 2004 10:02:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I like simplicity and I think the readers of the MRCPv2 specification will appreciate this also. We are seeking some sort of general term for discussing entities controlled by MRCPv2. At first glance "Media Server" appears to be an appropriate general term but unfortunately it carries with it definition out of scope of MRCPv2. What I like about Eric's original suggestion is that the phrase "Media Server" does not appear at all in the MRCPv2 specification. Building on this, why not just: "Media Resource": An entity to be controlled by MRCPv2 "MRCPv2 Server": Aggregate of one or more "Media Resource", exposed by MRCPv2. ("Server" for short) "MRCPv2 Client": The entity controlling one or more "Media Resource" via MRCPv2. ("Client" for short). This avoids confusion and leaves the media server vendors to decide if they want their product to be an MRCPv2 Client (probably the usual case), or an MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 Client and Server (ref my facetious remark earlier about a "Media B2BUA"). - Dave ----- Original Message ----- From: "Roy, Radhika R, ALABS" To: "Tim Melanchuk" ; "Sarvi Shanmugham" Cc: "Jeff Haynie" ; "Garland Sharratt" ; Sent: Friday, May 21, 2004 5:07 AM Subject: RE: [Speechsc] Media Server or Media Resource All: Seeing all definitions, it appears that we can safely conclude what Sarvi has proposed: 1. "MRCP server" or "MRCP Media server" - (a media server that contains only MRCP media resources) 2. "MRCP resource" or "MRCP media resource" - (self explanatory) 3. "MRCP resources on the Media Server" - (a media server that contains MRCP resources in addition to other media resources) 4. "Media Server" - (a media server that contains MRCP plus other media resources in the context of our works) Items 3 and 4 are the same in the context of our works. Radhika -----Original Message----- From: Tim Melanchuk [mailto:timm@convedia.com] Sent: Thursday, May 20, 2004 5:49 PM To: Sarvi Shanmugham Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource this approach sounds reasonable. "media server" is somewhat of generic term that is used for slightly different things in different contexts. for example, rtsp uses the term media server extensively and defines it as: Media server: The server providing playback services for one or more media streams. Different media streams within a presentation may originate from different media servers. A media server may reside on the same or a different host as the web server the presentation is invoked from. Sarvi Shanmugham wrote: > Well from what I am hearing so far, a Media server is an entity that may > support multiple media resources on it. But, the resources may not all > be controlled by single protocol. > > So it would be a misnomer to call the whole box an "MRCP server" or > "MRCP media server". > But from the definitions flying around, it looks like people do agree > that the box as a whole can be called/classified as a "Media server" > without any protocol implications. > > So here is a suggestion, I propose we change all occurances of "MRCP > server" or "MRCP Media server". > I will instead use one of the following terms/phrases depending on the > context. > To refer to individual resources I will use "MRCP resource" or > "MRCP media resource". > To refer to the whole box that may have multiple media > resources(MRCP or otherwise) I will use the phrase "Media Server" or > "MRCP resources on the Media Server" as appropriate. > > Any thoughts. > > Sarvi > > Roy, Radhika R, ALABS wrote: > >>Jeff: >> >>OK, let us go back to analyze these terms: Media Resources and Media Server. >> >>That is, MRCP is used to control (many, if not all) "media resources" of a media server. >> >>Radhika >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>Of Jeff Haynie >>Sent: Wednesday, May 19, 2004 9:48 PM >>To: Roy, Radhika R, ALABS >>Cc: Garland Sharratt; Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>OK, sorry, I'm confused. Do you support using the term "media server" >>or "media resource"? I can't tell from your response. Garland >>suggested in the original post that he favored the term "media resource" >>too. >> >>Jeff >> >>Roy, Radhika R, ALABS wrote: >> >> >> >>>Jeff: >>> >>>Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. >>> >>>In this sense, MRCP is one of the protocols that is used for its media resources control. >>> >>>Who knows MRCP may NOT enough to control all the media resources of a Media Server. >>> >>>Let us see the big picture of a media server. >>> >>>Radhika >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>Of Jeff Haynie >>>Sent: Wednesday, May 19, 2004 8:57 PM >>>To: Garland Sharratt >>>Cc: Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>Both you and Radhika seem to highlight exactly what MRCP is NOT and >>>re-enforce Eric's original request, no? Of course, I'm not implying >>>that media servers can't also support the MRCP protocol as a fact of >>>implementation - that's something that's completely within reason. >>> >>>Jeff >>> >>>Garland Sharratt wrote: >>> >>> >>> >>> >>> >>>>To Radhika's list I would also add recording and playback, as well as >>>>video announcements, video recording and playback, and video bridging. >>>> >>>>"Media server" is a generic term in NGN for a multi-purpose slave >>>>media processing engine controlled by a call agent or application >>>>server. All NGN architectures have a media server component, often by >>>>another name; in 3GPP, for instance, it's called an Media Resource >>>>Function Processor (MRFP). Media server control interfaces in NGN >>>>architectures are MGCP, H.248, and SIP. >>>> >>>>Garland >>>> >>>>-----Original Message----- >>>>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On >>>>Behalf Of *Roy, Radhika R, ALABS >>>>*Sent:* Wednesday, May 19, 2004 07:18 >>>>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>>>*Cc:* Speechsc@ietf.org >>>>*Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>>Eric, Klaus, and Sarvi: >>>> >>>>Let me try to provide the definition of media servers: >>>> >>>>"Media servers (MSs) typically operate with application servers (ASs) >>>>to handle and terminate media streams, and provide services such as >>>>announcement, media bridging, media transcoding, interactive voice >>>>response (IVR) messages (with or without VocieXML), speech-to-text >>>>(STT) conversion, text-to-speech (TTS) conversion, and others." >>>> >>>>Cheers! >>>> >>>>Radhika R. Roy >>>>AT&T >>>>732 420 1580 >>>> >>>> -----Original Message----- >>>> *From:* speechsc-admin@ietf.org >>>> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >>>> *Sent:* Wednesday, May 19, 2004 5:07 AM >>>> *To:* 'Sarvi Shanmugham'; Eric Burger >>>> *Cc:* Speechsc@ietf.org >>>> *Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>> Hi Eric and Sarvi, >>>> >>>> after some internal discussions I prefer to stay with the term >>>> "media server"! >>>> >>>> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >>>> that was referenced in the speechsc requirements document) the >>>> following definition of a media server can be found (section 3 on >>>> page 3): >>>> "Media servers are devices that perform media processing on >>>> real-time packet media." >>>> According to this definition the MRCP server is a media server >>>> (and not the platform that uses MRCP servers for media processing, >>>> which becomes a media proxy). >>>> In a network architecture that includes MRCP servers there might >>>> be other media servers. >>>> >>>> Could someone point me to the documents of the IETF, 3GPP, ... >>>> where I can find their definition of a media server. The term >>>> "media server" is used fairly often (especially in product >>>> brochures), but it seems to be difficult to find precise definitions. >>>> >>>> Thanks, >>>> Klaus >>>> >>>> >>>> >>>> -----Original Message----- >>>> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >>>> *Sent:* Mittwoch, 19. Mai 2004 01:49 >>>> *To:* Garland Sharratt >>>> *Cc:* Eric Burger; Speechsc@ietf.org >>>> *Subject:* Re: [Speechsc] Media Server or Media Resource >>>> >>>> This is fine by me. And I haven't heard any opposition so far. >>>> I will make the necessary edits. >>>> >>>> Sarvi >>>> Garland Sharratt wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>>>waters, I think, and implies the two things are the same whereas they are >>>>>not. >>>>> >>>>>Garland >>>>> >>>>>-----Original Message----- >>>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>>>Of Jeff Haynie >>>>>Sent: Monday, May 17, 2004 08:10 >>>>>To: Eric Burger >>>>>Cc: Speechsc@ietf.org >>>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>>> >>>>> >>>>>That's funny - I myself have struggled with the same term and would be >>>>>much more in favor of "media resource". >>>>> >>>>>Jeff >>>>> >>>>>Eric Burger wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>>I have a form issue, not necessarily a substance issue. >>>>>> >>>>>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>>>>the MRCPv2 protocol" is called a "Media Server". >>>>>> >>>>>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>>>> >>>>>>That definition, IMHO, does not really match with "the thing that is a >>>>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>embodies >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>>>>protocol. >>>>>> >>>>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>>>resource/g throughout the document? >>>>>> >>>>>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>>>>the Media SERVER Control Protocol. >>>>>> >>>>>> >>>>>> >>>>>>Thoughts? Comments? >>>>>> >>>>>>_______________________________________________ >>>>>>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 >>>>> >>>>> >>>>>_______________________________________________ >>>>>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 >>> >>> >>> >>> >> >> >>_______________________________________________ >>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 >> >> >> > _______________________________________________ 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 exim@www1.ietf.org Fri May 21 09:09:59 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29403 for ; Fri, 21 May 2004 09:09:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR9kc-0001q3-7i for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 09:07:52 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LD7opN007060 for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 09:07:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR9Xh-0006oQ-Qs for speechsc-web-archive@optimus.ietf.org; Fri, 21 May 2004 08:54:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28658 for ; Fri, 21 May 2004 08:54:27 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR9Xg-0004tF-Hq for speechsc-web-archive@ietf.org; Fri, 21 May 2004 08:54:28 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR9Wi-0004fy-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 08:53:30 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BR9Vn-0004SI-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 08:52:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR9PX-0004eu-AY; Fri, 21 May 2004 08:46:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR99b-0000Hb-4O for speechsc@optimus.ietf.org; Fri, 21 May 2004 08:29:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27060 for ; Fri, 21 May 2004 08:29:32 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR99Z-0007JU-Ru for speechsc@ietf.org; Fri, 21 May 2004 08:29:33 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR98Z-00077s-00 for speechsc@ietf.org; Fri, 21 May 2004 08:28:32 -0400 Received: from ckmso2.att.com ([209.219.209.75] helo=ckmso2.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 1BR98H-0006xW-00 for Speechsc@ietf.org; Fri, 21 May 2004 08:28:13 -0400 Received: from attrh0i.attrh.att.com ([135.37.94.54]) by ckmso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id i4LCQg45028423 for ; Fri, 21 May 2004 08:27:43 -0400 Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.9) by attrh0i.attrh.att.com (6.5.032) id 40951C4D0023368D; Fri, 21 May 2004 08:27:28 -0400 x-mimeole: Produced By Microsoft Exchange V6.0.6561.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] Media Server or Media Resource Date: Fri, 21 May 2004 08:27:42 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A0725E79F@ACCLUST02EVS1.ugd.att.com> Thread-Topic: [Speechsc] Media Server or Media Resource Thread-Index: AcQ/EmNrEHVbHNiLTKGgXyobzbF0IwAHFHXg From: "Roy, Radhika R, ALABS" To: "Dave Burke" , "Tim Melanchuk" , "Sarvi Shanmugham" Cc: "Jeff Haynie" , "Garland Sharratt" , Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Burk's proposal is also a viable solution, but the word "MCRCv2" itself = seems to be very "odd." What is the opinion of others? -----Original Message----- From: Dave Burke [mailto:david.burke@voxpilot.com] Sent: Friday, May 21, 2004 5:02 AM To: Roy, Radhika R, ALABS; Tim Melanchuk; Sarvi Shanmugham Cc: Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource I like simplicity and I think the readers of the MRCPv2 specification = will appreciate this also. We are seeking some sort of general term for discussing entities = controlled by MRCPv2. At first glance "Media Server" appears to be an appropriate general term but unfortunately it carries with it definition out of = scope of MRCPv2. What I like about Eric's original suggestion is that the phrase "Media Server" does not appear at all in the MRCPv2 specification. Building on this, why not just: "Media Resource": An entity to be controlled by MRCPv2 "MRCPv2 Server": Aggregate of one or more "Media Resource", exposed by MRCPv2. = ("Server" for short) "MRCPv2 Client": The entity controlling one or more "Media Resource" via MRCPv2. ("Client" for short). This avoids confusion and leaves the media server vendors to decide if = they want their product to be an MRCPv2 Client (probably the usual case), or = an MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 = Client and Server (ref my facetious remark earlier about a "Media B2BUA"). - Dave ----- Original Message ----- From: "Roy, Radhika R, ALABS" To: "Tim Melanchuk" ; "Sarvi Shanmugham" Cc: "Jeff Haynie" ; "Garland Sharratt" ; Sent: Friday, May 21, 2004 5:07 AM Subject: RE: [Speechsc] Media Server or Media Resource All: Seeing all definitions, it appears that we can safely conclude what Sarvi has proposed: 1. "MRCP server" or "MRCP Media server" - (a media server that contains only MRCP media resources) 2. "MRCP resource" or "MRCP media resource" - (self explanatory) 3. "MRCP resources on the Media Server" - (a media server that contains MRCP resources in addition to other media resources) 4. "Media Server" - (a media server that contains MRCP plus other media resources in the context of our works) Items 3 and 4 are the same in the context of our works. Radhika -----Original Message----- From: Tim Melanchuk [mailto:timm@convedia.com] Sent: Thursday, May 20, 2004 5:49 PM To: Sarvi Shanmugham Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource this approach sounds reasonable. "media server" is somewhat of generic term that is used for slightly different things in different contexts. for example, rtsp uses the term media server extensively and defines it as: Media server: The server providing playback services for one or more media streams. Different media streams within a presentation may originate from different media servers. A media server may reside on the same or a different host as the web server the presentation is invoked from. Sarvi Shanmugham wrote: > Well from what I am hearing so far, a Media server is an entity that may > support multiple media resources on it. But, the resources may not all > be controlled by single protocol. > > So it would be a misnomer to call the whole box an "MRCP server" or > "MRCP media server". > But from the definitions flying around, it looks like people do agree > that the box as a whole can be called/classified as a "Media server" > without any protocol implications. > > So here is a suggestion, I propose we change all occurances of "MRCP > server" or "MRCP Media server". > I will instead use one of the following terms/phrases depending on the > context. > To refer to individual resources I will use "MRCP resource" or > "MRCP media resource". > To refer to the whole box that may have multiple media > resources(MRCP or otherwise) I will use the phrase "Media Server" or > "MRCP resources on the Media Server" as appropriate. > > Any thoughts. > > Sarvi > > Roy, Radhika R, ALABS wrote: > >>Jeff: >> >>OK, let us go back to analyze these terms: Media Resources and Media Server. >> >>That is, MRCP is used to control (many, if not all) "media resources" of a media server. >> >>Radhika >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>Of Jeff Haynie >>Sent: Wednesday, May 19, 2004 9:48 PM >>To: Roy, Radhika R, ALABS >>Cc: Garland Sharratt; Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>OK, sorry, I'm confused. Do you support using the term "media server" >>or "media resource"? I can't tell from your response. Garland >>suggested in the original post that he favored the term "media resource" >>too. >> >>Jeff >> >>Roy, Radhika R, ALABS wrote: >> >> >> >>>Jeff: >>> >>>Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. >>> >>>In this sense, MRCP is one of the protocols that is used for its media resources control. >>> >>>Who knows MRCP may NOT enough to control all the media resources of a Media Server. >>> >>>Let us see the big picture of a media server. >>> >>>Radhika >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>Of Jeff Haynie >>>Sent: Wednesday, May 19, 2004 8:57 PM >>>To: Garland Sharratt >>>Cc: Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>Both you and Radhika seem to highlight exactly what MRCP is NOT and >>>re-enforce Eric's original request, no? Of course, I'm not implying >>>that media servers can't also support the MRCP protocol as a fact of >>>implementation - that's something that's completely within reason. >>> >>>Jeff >>> >>>Garland Sharratt wrote: >>> >>> >>> >>> >>> >>>>To Radhika's list I would also add recording and playback, as well as >>>>video announcements, video recording and playback, and video bridging. >>>> >>>>"Media server" is a generic term in NGN for a multi-purpose slave >>>>media processing engine controlled by a call agent or application >>>>server. All NGN architectures have a media server component, often by >>>>another name; in 3GPP, for instance, it's called an Media Resource >>>>Function Processor (MRFP). Media server control interfaces in NGN >>>>architectures are MGCP, H.248, and SIP. >>>> >>>>Garland >>>> >>>>-----Original Message----- >>>>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On >>>>Behalf Of *Roy, Radhika R, ALABS >>>>*Sent:* Wednesday, May 19, 2004 07:18 >>>>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>>>*Cc:* Speechsc@ietf.org >>>>*Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>>Eric, Klaus, and Sarvi: >>>> >>>>Let me try to provide the definition of media servers: >>>> >>>>"Media servers (MSs) typically operate with application servers (ASs) >>>>to handle and terminate media streams, and provide services such as >>>>announcement, media bridging, media transcoding, interactive voice >>>>response (IVR) messages (with or without VocieXML), speech-to-text >>>>(STT) conversion, text-to-speech (TTS) conversion, and others." >>>> >>>>Cheers! >>>> >>>>Radhika R. Roy >>>>AT&T >>>>732 420 1580 >>>> >>>> -----Original Message----- >>>> *From:* speechsc-admin@ietf.org >>>> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >>>> *Sent:* Wednesday, May 19, 2004 5:07 AM >>>> *To:* 'Sarvi Shanmugham'; Eric Burger >>>> *Cc:* Speechsc@ietf.org >>>> *Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>> Hi Eric and Sarvi, >>>> >>>> after some internal discussions I prefer to stay with the term >>>> "media server"! >>>> >>>> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >>>> that was referenced in the speechsc requirements document) the >>>> following definition of a media server can be found (section 3 on >>>> page 3): >>>> "Media servers are devices that perform media processing on >>>> real-time packet media." >>>> According to this definition the MRCP server is a media server >>>> (and not the platform that uses MRCP servers for media processing, >>>> which becomes a media proxy). >>>> In a network architecture that includes MRCP servers there might >>>> be other media servers. >>>> >>>> Could someone point me to the documents of the IETF, 3GPP, ... >>>> where I can find their definition of a media server. The term >>>> "media server" is used fairly often (especially in product >>>> brochures), but it seems to be difficult to find precise definitions. >>>> >>>> Thanks, >>>> Klaus >>>> >>>> >>>> >>>> -----Original Message----- >>>> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >>>> *Sent:* Mittwoch, 19. Mai 2004 01:49 >>>> *To:* Garland Sharratt >>>> *Cc:* Eric Burger; Speechsc@ietf.org >>>> *Subject:* Re: [Speechsc] Media Server or Media Resource >>>> >>>> This is fine by me. And I haven't heard any opposition so far. >>>> I will make the necessary edits. >>>> >>>> Sarvi >>>> Garland Sharratt wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>>>waters, I think, and implies the two things are the same whereas they are >>>>>not. >>>>> >>>>>Garland >>>>> >>>>>-----Original Message----- >>>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>>>Of Jeff Haynie >>>>>Sent: Monday, May 17, 2004 08:10 >>>>>To: Eric Burger >>>>>Cc: Speechsc@ietf.org >>>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>>> >>>>> >>>>>That's funny - I myself have struggled with the same term and would be >>>>>much more in favor of "media resource". >>>>> >>>>>Jeff >>>>> >>>>>Eric Burger wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>>I have a form issue, not necessarily a substance issue. >>>>>> >>>>>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>>>>the MRCPv2 protocol" is called a "Media Server". >>>>>> >>>>>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>>>> >>>>>>That definition, IMHO, does not really match with "the thing that is a >>>>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>embodies >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>>>>protocol. >>>>>> >>>>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>>>resource/g throughout the document? >>>>>> >>>>>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>>>>the Media SERVER Control Protocol. >>>>>> >>>>>> >>>>>> >>>>>>Thoughts? Comments? >>>>>> >>>>>>_______________________________________________ >>>>>>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 >>>>> >>>>> >>>>>_______________________________________________ >>>>>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 >>> >>> >>> >>> >> >> >>_______________________________________________ >>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 >> >> >> > _______________________________________________ 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 exim@www1.ietf.org Fri May 21 10:59:37 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07195 for ; Fri, 21 May 2004 10:59:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRBOJ-0001pw-D4 for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 10:52:55 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LEqtuJ007057 for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 10:52:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRBHH-0000Yh-A8 for speechsc-web-archive@optimus.ietf.org; Fri, 21 May 2004 10:45:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06434 for ; Fri, 21 May 2004 10:45:35 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRBHE-0005Kd-N2 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 10:45:36 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRBGI-00056s-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 10:44:40 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRBFN-0004tG-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 10:43:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRB47-0003n6-8E; Fri, 21 May 2004 10:32:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRAsA-0007Ar-NK for speechsc@optimus.ietf.org; Fri, 21 May 2004 10:19:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03626 for ; Fri, 21 May 2004 10:19:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRAs8-0006wu-2k for speechsc@ietf.org; Fri, 21 May 2004 10:19:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRArB-0006j0-00 for speechsc@ietf.org; Fri, 21 May 2004 10:18:42 -0400 Received: from cerbrus.convedia.com ([216.129.93.50]) by ietf-mx with esmtp (Exim 4.12) id 1BRAq1-0006Ht-00 for Speechsc@ietf.org; Fri, 21 May 2004 10:17:29 -0400 Received: from mailhost.convedia.com (ladon [192.168.208.15]) by cerbrus.convedia.com (8.12.9/8.12.9) with ESMTP id i4LE53Ev013449 for ; Fri, 21 May 2004 07:05:03 -0700 (PDT) Received: from laptop33 ([192.168.209.4]) by mailhost.convedia.com (8.12.9/8.12.9) with SMTP id i4LEGtjU027779 for ; Fri, 21 May 2004 07:16:56 -0700 (PDT) From: "Garland Sharratt" To: Subject: RE: [Speechsc] Media Server or Media Resource Date: Fri, 21 May 2004 07:16:55 -0700 Keywords: .aa Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <34DA635B184A644DA4588E260EC0A25A0725E79F@ACCLUST02EVS1.ugd.att.com> x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Content-Transfer-Encoding: 7bit Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit How about: "Media Resource" "MRCP Server" "MRCP Client" with Dave's meanings. -----Original Message----- From: Roy, Radhika R, ALABS [mailto:rrroy@att.com] Sent: Friday, May 21, 2004 05:28 To: Dave Burke; Tim Melanchuk; Sarvi Shanmugham Cc: Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: RE: [Speechsc] Media Server or Media Resource Burk's proposal is also a viable solution, but the word "MCRCv2" itself seems to be very "odd." What is the opinion of others? -----Original Message----- From: Dave Burke [mailto:david.burke@voxpilot.com] Sent: Friday, May 21, 2004 5:02 AM To: Roy, Radhika R, ALABS; Tim Melanchuk; Sarvi Shanmugham Cc: Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource I like simplicity and I think the readers of the MRCPv2 specification will appreciate this also. We are seeking some sort of general term for discussing entities controlled by MRCPv2. At first glance "Media Server" appears to be an appropriate general term but unfortunately it carries with it definition out of scope of MRCPv2. What I like about Eric's original suggestion is that the phrase "Media Server" does not appear at all in the MRCPv2 specification. Building on this, why not just: "Media Resource": An entity to be controlled by MRCPv2 "MRCPv2 Server": Aggregate of one or more "Media Resource", exposed by MRCPv2. ("Server" for short) "MRCPv2 Client": The entity controlling one or more "Media Resource" via MRCPv2. ("Client" for short). This avoids confusion and leaves the media server vendors to decide if they want their product to be an MRCPv2 Client (probably the usual case), or an MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 Client and Server (ref my facetious remark earlier about a "Media B2BUA"). - Dave ----- Original Message ----- From: "Roy, Radhika R, ALABS" To: "Tim Melanchuk" ; "Sarvi Shanmugham" Cc: "Jeff Haynie" ; "Garland Sharratt" ; Sent: Friday, May 21, 2004 5:07 AM Subject: RE: [Speechsc] Media Server or Media Resource All: Seeing all definitions, it appears that we can safely conclude what Sarvi has proposed: 1. "MRCP server" or "MRCP Media server" - (a media server that contains only MRCP media resources) 2. "MRCP resource" or "MRCP media resource" - (self explanatory) 3. "MRCP resources on the Media Server" - (a media server that contains MRCP resources in addition to other media resources) 4. "Media Server" - (a media server that contains MRCP plus other media resources in the context of our works) Items 3 and 4 are the same in the context of our works. Radhika -----Original Message----- From: Tim Melanchuk [mailto:timm@convedia.com] Sent: Thursday, May 20, 2004 5:49 PM To: Sarvi Shanmugham Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource this approach sounds reasonable. "media server" is somewhat of generic term that is used for slightly different things in different contexts. for example, rtsp uses the term media server extensively and defines it as: Media server: The server providing playback services for one or more media streams. Different media streams within a presentation may originate from different media servers. A media server may reside on the same or a different host as the web server the presentation is invoked from. Sarvi Shanmugham wrote: > Well from what I am hearing so far, a Media server is an entity that may > support multiple media resources on it. But, the resources may not all > be controlled by single protocol. > > So it would be a misnomer to call the whole box an "MRCP server" or > "MRCP media server". > But from the definitions flying around, it looks like people do agree > that the box as a whole can be called/classified as a "Media server" > without any protocol implications. > > So here is a suggestion, I propose we change all occurances of "MRCP > server" or "MRCP Media server". > I will instead use one of the following terms/phrases depending on the > context. > To refer to individual resources I will use "MRCP resource" or > "MRCP media resource". > To refer to the whole box that may have multiple media > resources(MRCP or otherwise) I will use the phrase "Media Server" or > "MRCP resources on the Media Server" as appropriate. > > Any thoughts. > > Sarvi > > Roy, Radhika R, ALABS wrote: > >>Jeff: >> >>OK, let us go back to analyze these terms: Media Resources and Media Server. >> >>That is, MRCP is used to control (many, if not all) "media resources" of a media server. >> >>Radhika >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>Of Jeff Haynie >>Sent: Wednesday, May 19, 2004 9:48 PM >>To: Roy, Radhika R, ALABS >>Cc: Garland Sharratt; Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>OK, sorry, I'm confused. Do you support using the term "media server" >>or "media resource"? I can't tell from your response. Garland >>suggested in the original post that he favored the term "media resource" >>too. >> >>Jeff >> >>Roy, Radhika R, ALABS wrote: >> >> >> >>>Jeff: >>> >>>Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. >>> >>>In this sense, MRCP is one of the protocols that is used for its media resources control. >>> >>>Who knows MRCP may NOT enough to control all the media resources of a Media Server. >>> >>>Let us see the big picture of a media server. >>> >>>Radhika >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>Of Jeff Haynie >>>Sent: Wednesday, May 19, 2004 8:57 PM >>>To: Garland Sharratt >>>Cc: Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>Both you and Radhika seem to highlight exactly what MRCP is NOT and >>>re-enforce Eric's original request, no? Of course, I'm not implying >>>that media servers can't also support the MRCP protocol as a fact of >>>implementation - that's something that's completely within reason. >>> >>>Jeff >>> >>>Garland Sharratt wrote: >>> >>> >>> >>> >>> >>>>To Radhika's list I would also add recording and playback, as well as >>>>video announcements, video recording and playback, and video bridging. >>>> >>>>"Media server" is a generic term in NGN for a multi-purpose slave >>>>media processing engine controlled by a call agent or application >>>>server. All NGN architectures have a media server component, often by >>>>another name; in 3GPP, for instance, it's called an Media Resource >>>>Function Processor (MRFP). Media server control interfaces in NGN >>>>architectures are MGCP, H.248, and SIP. >>>> >>>>Garland >>>> >>>>-----Original Message----- >>>>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On >>>>Behalf Of *Roy, Radhika R, ALABS >>>>*Sent:* Wednesday, May 19, 2004 07:18 >>>>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>>>*Cc:* Speechsc@ietf.org >>>>*Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>>Eric, Klaus, and Sarvi: >>>> >>>>Let me try to provide the definition of media servers: >>>> >>>>"Media servers (MSs) typically operate with application servers (ASs) >>>>to handle and terminate media streams, and provide services such as >>>>announcement, media bridging, media transcoding, interactive voice >>>>response (IVR) messages (with or without VocieXML), speech-to-text >>>>(STT) conversion, text-to-speech (TTS) conversion, and others." >>>> >>>>Cheers! >>>> >>>>Radhika R. Roy >>>>AT&T >>>>732 420 1580 >>>> >>>> -----Original Message----- >>>> *From:* speechsc-admin@ietf.org >>>> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >>>> *Sent:* Wednesday, May 19, 2004 5:07 AM >>>> *To:* 'Sarvi Shanmugham'; Eric Burger >>>> *Cc:* Speechsc@ietf.org >>>> *Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>> Hi Eric and Sarvi, >>>> >>>> after some internal discussions I prefer to stay with the term >>>> "media server"! >>>> >>>> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >>>> that was referenced in the speechsc requirements document) the >>>> following definition of a media server can be found (section 3 on >>>> page 3): >>>> "Media servers are devices that perform media processing on >>>> real-time packet media." >>>> According to this definition the MRCP server is a media server >>>> (and not the platform that uses MRCP servers for media processing, >>>> which becomes a media proxy). >>>> In a network architecture that includes MRCP servers there might >>>> be other media servers. >>>> >>>> Could someone point me to the documents of the IETF, 3GPP, ... >>>> where I can find their definition of a media server. The term >>>> "media server" is used fairly often (especially in product >>>> brochures), but it seems to be difficult to find precise definitions. >>>> >>>> Thanks, >>>> Klaus >>>> >>>> >>>> >>>> -----Original Message----- >>>> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >>>> *Sent:* Mittwoch, 19. Mai 2004 01:49 >>>> *To:* Garland Sharratt >>>> *Cc:* Eric Burger; Speechsc@ietf.org >>>> *Subject:* Re: [Speechsc] Media Server or Media Resource >>>> >>>> This is fine by me. And I haven't heard any opposition so far. >>>> I will make the necessary edits. >>>> >>>> Sarvi >>>> Garland Sharratt wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>>>waters, I think, and implies the two things are the same whereas they are >>>>>not. >>>>> >>>>>Garland >>>>> >>>>>-----Original Message----- >>>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>>>Of Jeff Haynie >>>>>Sent: Monday, May 17, 2004 08:10 >>>>>To: Eric Burger >>>>>Cc: Speechsc@ietf.org >>>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>>> >>>>> >>>>>That's funny - I myself have struggled with the same term and would be >>>>>much more in favor of "media resource". >>>>> >>>>>Jeff >>>>> >>>>>Eric Burger wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>>I have a form issue, not necessarily a substance issue. >>>>>> >>>>>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>>>>the MRCPv2 protocol" is called a "Media Server". >>>>>> >>>>>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>>>> >>>>>>That definition, IMHO, does not really match with "the thing that is a >>>>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>embodies >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>>>>protocol. >>>>>> >>>>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>>>resource/g throughout the document? >>>>>> >>>>>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>>>>the Media SERVER Control Protocol. >>>>>> >>>>>> >>>>>> >>>>>>Thoughts? Comments? >>>>>> >>>>>>_______________________________________________ >>>>>>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 >>>>> >>>>> >>>>>_______________________________________________ >>>>>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 >>> >>> >>> >>> >> >> >>_______________________________________________ >>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 >> >> >> > _______________________________________________ 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 exim@www1.ietf.org Fri May 21 11:41:45 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09686 for ; Fri, 21 May 2004 11:41:45 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRBu2-0000z7-0A for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 11:25:42 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LFPfVL003785 for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 11:25:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRBmb-0007xc-8d for speechsc-web-archive@optimus.ietf.org; Fri, 21 May 2004 11:18:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08294 for ; Fri, 21 May 2004 11:17:58 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRBma-0004pa-Cs for speechsc-web-archive@ietf.org; Fri, 21 May 2004 11:18:00 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRBle-0004aE-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 11:17:04 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRBku-0004K4-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 11:16:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRBZ7-0004eh-BF; Fri, 21 May 2004 11:04:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRBTu-00034v-JE for speechsc@optimus.ietf.org; Fri, 21 May 2004 10:58:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07118 for ; Fri, 21 May 2004 10:58:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRBTr-0000Sf-Pv for speechsc@ietf.org; Fri, 21 May 2004 10:58:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRBTB-0000FE-00 for speechsc@ietf.org; Fri, 21 May 2004 10:57:59 -0400 Received: from almso1.att.com ([192.128.167.69] helo=almso1.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 1BRBSU-00000g-00 for Speechsc@ietf.org; Fri, 21 May 2004 10:57:14 -0400 Received: from attrh0i.attrh.att.com ([135.37.94.54]) by almso1.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id i4LErqCd009746 for ; Fri, 21 May 2004 10:56:43 -0400 Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.9) by attrh0i.attrh.att.com (6.5.032) id 40951C4D0023966F; Fri, 21 May 2004 10:56:29 -0400 x-mimeole: Produced By Microsoft Exchange V6.0.6561.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speechsc] Media Server or Media Resource Date: Fri, 21 May 2004 10:56:43 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A0725EB9B@ACCLUST02EVS1.ugd.att.com> Thread-Topic: [Speechsc] Media Server or Media Resource Thread-Index: AcQ/QgO903IHjog3TXSHDSubXrDUtAAAaXeA From: "Roy, Radhika R, ALABS" To: "Garland Sharratt" , Content-Transfer-Encoding: quoted-printable Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable I agree with this set as long as we do not need to "v2." Radhika -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf Of Garland Sharratt Sent: Friday, May 21, 2004 10:17 AM To: Speechsc@ietf.org Subject: RE: [Speechsc] Media Server or Media Resource How about: "Media Resource" "MRCP Server" "MRCP Client" with Dave's meanings. -----Original Message----- From: Roy, Radhika R, ALABS [mailto:rrroy@att.com] Sent: Friday, May 21, 2004 05:28 To: Dave Burke; Tim Melanchuk; Sarvi Shanmugham Cc: Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: RE: [Speechsc] Media Server or Media Resource Burk's proposal is also a viable solution, but the word "MCRCv2" itself seems to be very "odd." What is the opinion of others? -----Original Message----- From: Dave Burke [mailto:david.burke@voxpilot.com] Sent: Friday, May 21, 2004 5:02 AM To: Roy, Radhika R, ALABS; Tim Melanchuk; Sarvi Shanmugham Cc: Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource I like simplicity and I think the readers of the MRCPv2 specification = will appreciate this also. We are seeking some sort of general term for discussing entities = controlled by MRCPv2. At first glance "Media Server" appears to be an appropriate general term but unfortunately it carries with it definition out of = scope of MRCPv2. What I like about Eric's original suggestion is that the phrase "Media Server" does not appear at all in the MRCPv2 specification. Building on this, why not just: "Media Resource": An entity to be controlled by MRCPv2 "MRCPv2 Server": Aggregate of one or more "Media Resource", exposed by MRCPv2. = ("Server" for short) "MRCPv2 Client": The entity controlling one or more "Media Resource" via MRCPv2. ("Client" for short). This avoids confusion and leaves the media server vendors to decide if = they want their product to be an MRCPv2 Client (probably the usual case), or = an MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 = Client and Server (ref my facetious remark earlier about a "Media B2BUA"). - Dave ----- Original Message ----- From: "Roy, Radhika R, ALABS" To: "Tim Melanchuk" ; "Sarvi Shanmugham" Cc: "Jeff Haynie" ; "Garland Sharratt" ; Sent: Friday, May 21, 2004 5:07 AM Subject: RE: [Speechsc] Media Server or Media Resource All: Seeing all definitions, it appears that we can safely conclude what Sarvi has proposed: 1. "MRCP server" or "MRCP Media server" - (a media server that contains only MRCP media resources) 2. "MRCP resource" or "MRCP media resource" - (self explanatory) 3. "MRCP resources on the Media Server" - (a media server that contains MRCP resources in addition to other media resources) 4. "Media Server" - (a media server that contains MRCP plus other media resources in the context of our works) Items 3 and 4 are the same in the context of our works. Radhika -----Original Message----- From: Tim Melanchuk [mailto:timm@convedia.com] Sent: Thursday, May 20, 2004 5:49 PM To: Sarvi Shanmugham Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource this approach sounds reasonable. "media server" is somewhat of generic term that is used for slightly different things in different contexts. for example, rtsp uses the term media server extensively and defines it as: Media server: The server providing playback services for one or more media streams. Different media streams within a presentation may originate from different media servers. A media server may reside on the same or a different host as the web server the presentation is invoked from. Sarvi Shanmugham wrote: > Well from what I am hearing so far, a Media server is an entity that may > support multiple media resources on it. But, the resources may not all > be controlled by single protocol. > > So it would be a misnomer to call the whole box an "MRCP server" or > "MRCP media server". > But from the definitions flying around, it looks like people do agree > that the box as a whole can be called/classified as a "Media server" > without any protocol implications. > > So here is a suggestion, I propose we change all occurances of "MRCP > server" or "MRCP Media server". > I will instead use one of the following terms/phrases depending on the > context. > To refer to individual resources I will use "MRCP resource" or > "MRCP media resource". > To refer to the whole box that may have multiple media > resources(MRCP or otherwise) I will use the phrase "Media Server" or > "MRCP resources on the Media Server" as appropriate. > > Any thoughts. > > Sarvi > > Roy, Radhika R, ALABS wrote: > >>Jeff: >> >>OK, let us go back to analyze these terms: Media Resources and Media Server. >> >>That is, MRCP is used to control (many, if not all) "media resources" of a media server. >> >>Radhika >> >>-----Original Message----- >>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>Of Jeff Haynie >>Sent: Wednesday, May 19, 2004 9:48 PM >>To: Roy, Radhika R, ALABS >>Cc: Garland Sharratt; Speechsc@ietf.org >>Subject: Re: [Speechsc] Media Server or Media Resource >> >> >>OK, sorry, I'm confused. Do you support using the term "media server" >>or "media resource"? I can't tell from your response. Garland >>suggested in the original post that he favored the term "media resource" >>too. >> >>Jeff >> >>Roy, Radhika R, ALABS wrote: >> >> >> >>>Jeff: >>> >>>Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. >>> >>>In this sense, MRCP is one of the protocols that is used for its media resources control. >>> >>>Who knows MRCP may NOT enough to control all the media resources of a Media Server. >>> >>>Let us see the big picture of a media server. >>> >>>Radhika >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>Of Jeff Haynie >>>Sent: Wednesday, May 19, 2004 8:57 PM >>>To: Garland Sharratt >>>Cc: Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>Both you and Radhika seem to highlight exactly what MRCP is NOT and >>>re-enforce Eric's original request, no? Of course, I'm not implying >>>that media servers can't also support the MRCP protocol as a fact of >>>implementation - that's something that's completely within reason. >>> >>>Jeff >>> >>>Garland Sharratt wrote: >>> >>> >>> >>> >>> >>>>To Radhika's list I would also add recording and playback, as well as >>>>video announcements, video recording and playback, and video bridging. >>>> >>>>"Media server" is a generic term in NGN for a multi-purpose slave >>>>media processing engine controlled by a call agent or application >>>>server. All NGN architectures have a media server component, often by >>>>another name; in 3GPP, for instance, it's called an Media Resource >>>>Function Processor (MRFP). Media server control interfaces in NGN >>>>architectures are MGCP, H.248, and SIP. >>>> >>>>Garland >>>> >>>>-----Original Message----- >>>>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On >>>>Behalf Of *Roy, Radhika R, ALABS >>>>*Sent:* Wednesday, May 19, 2004 07:18 >>>>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>>>*Cc:* Speechsc@ietf.org >>>>*Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>>Eric, Klaus, and Sarvi: >>>> >>>>Let me try to provide the definition of media servers: >>>> >>>>"Media servers (MSs) typically operate with application servers (ASs) >>>>to handle and terminate media streams, and provide services such as >>>>announcement, media bridging, media transcoding, interactive voice >>>>response (IVR) messages (with or without VocieXML), speech-to-text >>>>(STT) conversion, text-to-speech (TTS) conversion, and others." >>>> >>>>Cheers! >>>> >>>>Radhika R. Roy >>>>AT&T >>>>732 420 1580 >>>> >>>> -----Original Message----- >>>> *From:* speechsc-admin@ietf.org >>>> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >>>> *Sent:* Wednesday, May 19, 2004 5:07 AM >>>> *To:* 'Sarvi Shanmugham'; Eric Burger >>>> *Cc:* Speechsc@ietf.org >>>> *Subject:* RE: [Speechsc] Media Server or Media Resource >>>> >>>> Hi Eric and Sarvi, >>>> >>>> after some internal discussions I prefer to stay with the term >>>> "media server"! >>>> >>>> In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, >>>> that was referenced in the speechsc requirements document) the >>>> following definition of a media server can be found (section 3 on >>>> page 3): >>>> "Media servers are devices that perform media processing on >>>> real-time packet media." >>>> According to this definition the MRCP server is a media server >>>> (and not the platform that uses MRCP servers for media processing, >>>> which becomes a media proxy). >>>> In a network architecture that includes MRCP servers there might >>>> be other media servers. >>>> >>>> Could someone point me to the documents of the IETF, 3GPP, ... >>>> where I can find their definition of a media server. The term >>>> "media server" is used fairly often (especially in product >>>> brochures), but it seems to be difficult to find precise definitions. >>>> >>>> Thanks, >>>> Klaus >>>> >>>> >>>> >>>> -----Original Message----- >>>> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >>>> *Sent:* Mittwoch, 19. Mai 2004 01:49 >>>> *To:* Garland Sharratt >>>> *Cc:* Eric Burger; Speechsc@ietf.org >>>> *Subject:* Re: [Speechsc] Media Server or Media Resource >>>> >>>> This is fine by me. And I haven't heard any opposition so far. >>>> I will make the necessary edits. >>>> >>>> Sarvi >>>> Garland Sharratt wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Eric, I concur. Using the term "media server" for MRCPv2 muddies the >>>>>waters, I think, and implies the two things are the same whereas they are >>>>>not. >>>>> >>>>>Garland >>>>> >>>>>-----Original Message----- >>>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On Behalf >>>>>Of Jeff Haynie >>>>>Sent: Monday, May 17, 2004 08:10 >>>>>To: Eric Burger >>>>>Cc: Speechsc@ietf.org >>>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>>> >>>>> >>>>>That's funny - I myself have struggled with the same term and would be >>>>>much more in favor of "media resource". >>>>> >>>>>Jeff >>>>> >>>>>Eric Burger wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>>I have a form issue, not necessarily a substance issue. >>>>>> >>>>>>Throughout the MRCPv2 document, the "thing that is a server controlled by >>>>>>the MRCPv2 protocol" is called a "Media Server". >>>>>> >>>>>>A Media Server is a device that has a well-defined meaning, in the IETF, >>>>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>>>> >>>>>>That definition, IMHO, does not really match with "the thing that is a >>>>>>server controlled by the MRCPv2 protocol." In fact, the thing that >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>embodies >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>the accepted version of a Media Server is often a *client* to the MRCPv2 >>>>>>protocol. >>>>>> >>>>>>Would anyone be really put out if we did a 1,$:s/media server/media >>>>>>resource/g throughout the document? >>>>>> >>>>>>Rationale: The document describes the Media RESOURCE Control Protocol, not >>>>>>the Media SERVER Control Protocol. >>>>>> >>>>>> >>>>>> >>>>>>Thoughts? Comments? >>>>>> >>>>>>_______________________________________________ >>>>>>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 >>>>> >>>>> >>>>>_______________________________________________ >>>>>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 >>> >>> >>> >>> >> >> >>_______________________________________________ >>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 >> >> >> > _______________________________________________ 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 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Fri May 21 17:24:22 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04996 for ; Fri, 21 May 2004 17:24:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRHRU-00066f-Hl for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 17:20:36 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LLKacl023473 for speechsc-archive@odin.ietf.org; Fri, 21 May 2004 17:20:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRHGC-0002fx-LT for speechsc-web-archive@optimus.ietf.org; Fri, 21 May 2004 17:08:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03669 for ; Fri, 21 May 2004 17:08:52 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRHG9-0004yQ-VH for speechsc-web-archive@ietf.org; Fri, 21 May 2004 17:08:53 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRHFM-0004oZ-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 17:08:12 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRHDW-0004bJ-00 for speechsc-web-archive@ietf.org; Fri, 21 May 2004 17:06:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRH2y-0004Tp-Cu; Fri, 21 May 2004 16:55:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRGiV-0004Jv-QD for speechsc@optimus.ietf.org; Fri, 21 May 2004 16:34:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29251 for ; Fri, 21 May 2004 16:34:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRGiT-0006rJ-Q5 for speechsc@ietf.org; Fri, 21 May 2004 16:34:05 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRGgX-0006aW-00 for speechsc@ietf.org; Fri, 21 May 2004 16:32:08 -0400 Received: from vtg-um-e2k1.cisco.com ([171.70.93.55] helo=vtg-um-e2k1.sj21ad.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BRGfS-0006H1-00 for Speechsc@ietf.org; Fri, 21 May 2004 16:30:58 -0400 Received: from cisco.com ([10.32.130.132]) by vtg-um-e2k1.sj21ad.cisco.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 21 May 2004 13:30:27 -0700 Message-ID: <40AE6704.1010805@cisco.com> Date: Fri, 21 May 2004 13:31:00 -0700 From: Sarvi Shanmugham Organization: Cisco Systems Inc. User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dave Burke CC: "Roy, Radhika R, ALABS" , Tim Melanchuk , Jeff Haynie , Garland Sharratt , Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource References: <34DA635B184A644DA4588E260EC0A25A0725E6AF@ACCLUST02EVS1.ugd.att.com> <001501c43f12$574e5890$ca00000a@db01.voxpilot.com> In-Reply-To: <001501c43f12$574e5890$ca00000a@db01.voxpilot.com> Content-Type: multipart/alternative; boundary="------------030709070305060907050600" X-OriginalArrivalTime: 21 May 2004 20:30:27.0873 (UTC) FILETIME=[74082910:01C43F72] Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE, HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. --------------030709070305060907050600 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I can go with this proposal. I would suggest that we loose the v2 portion in the naming, as many of these servers are bound to support v1 for backward compatibility. Sarvi Dave Burke wrote: >I like simplicity and I think the readers of the MRCPv2 specification will >appreciate this also. > >We are seeking some sort of general term for discussing entities controlled >by MRCPv2. At first glance "Media Server" appears to be an appropriate >general term but unfortunately it carries with it definition out of scope of >MRCPv2. > >What I like about Eric's original suggestion is that the phrase "Media >Server" does not appear at all in the MRCPv2 specification. Building on >this, why not just: > >"Media Resource": > An entity to be controlled by MRCPv2 > >"MRCPv2 Server": > Aggregate of one or more "Media Resource", exposed by MRCPv2. ("Server" >for short) > >"MRCPv2 Client": > The entity controlling one or more "Media Resource" via MRCPv2. >("Client" for short). > >This avoids confusion and leaves the media server vendors to decide if they >want their product to be an MRCPv2 Client (probably the usual case), or an >MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 Client >and Server (ref my facetious remark earlier about a "Media B2BUA"). > >- Dave > >----- Original Message ----- >From: "Roy, Radhika R, ALABS" >To: "Tim Melanchuk" ; "Sarvi Shanmugham" > >Cc: "Jeff Haynie" ; "Garland Sharratt" >; >Sent: Friday, May 21, 2004 5:07 AM >Subject: RE: [Speechsc] Media Server or Media Resource > > >All: > >Seeing all definitions, it appears that we can safely conclude what >Sarvi has proposed: > >1. "MRCP server" or "MRCP Media server" - (a media server that contains >only MRCP media resources) > >2. "MRCP resource" or "MRCP media resource" - (self explanatory) > >3. "MRCP resources on the Media Server" - (a media server that contains >MRCP resources in addition to other media resources) > >4. "Media Server" - (a media server that contains MRCP plus other media >resources in the context of our works) > >Items 3 and 4 are the same in the context of our works. > >Radhika > >-----Original Message----- >From: Tim Melanchuk [mailto:timm@convedia.com] >Sent: Thursday, May 20, 2004 5:49 PM >To: Sarvi Shanmugham >Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt; >Speechsc@ietf.org >Subject: Re: [Speechsc] Media Server or Media Resource > > >this approach sounds reasonable. "media server" is somewhat of >generic term that is used for slightly different things in different >contexts. for example, rtsp uses the term media server extensively >and defines it as: > > Media server: The server providing playback services for one or > more media streams. Different media streams within a > presentation may originate from different media servers. A > media server may reside on the same or a different host as > the web server the presentation is invoked from. > > > >Sarvi Shanmugham wrote: > > > >>Well from what I am hearing so far, a Media server is an entity that >> >> >may > > >>support multiple media resources on it. But, the resources may not >> >> >all > > >>be controlled by single protocol. >> >>So it would be a misnomer to call the whole box an "MRCP server" or >>"MRCP media server". >>But from the definitions flying around, it looks like people do agree >> >> > > > >>that the box as a whole can be called/classified as a "Media server" >>without any protocol implications. >> >>So here is a suggestion, I propose we change all occurances of "MRCP >>server" or "MRCP Media server". >>I will instead use one of the following terms/phrases depending on the >> >> > > > >>context. >> To refer to individual resources I will use "MRCP resource" or >>"MRCP media resource". >> To refer to the whole box that may have multiple media >>resources(MRCP or otherwise) I will use the phrase "Media Server" or >>"MRCP resources on the Media Server" as appropriate. >> >>Any thoughts. >> >>Sarvi >> >>Roy, Radhika R, ALABS wrote: >> >> >> >>>Jeff: >>> >>>OK, let us go back to analyze these terms: Media Resources and Media >>> >>> >Server. > > >>>That is, MRCP is used to control (many, if not all) "media resources" >>> >>> >of a media server. > > >>>Radhika >>> >>>-----Original Message----- >>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On >>> >>> >Behalf > > >>>Of Jeff Haynie >>>Sent: Wednesday, May 19, 2004 9:48 PM >>>To: Roy, Radhika R, ALABS >>>Cc: Garland Sharratt; Speechsc@ietf.org >>>Subject: Re: [Speechsc] Media Server or Media Resource >>> >>> >>>OK, sorry, I'm confused. Do you support using the term "media server" >>> >>> > > > >>>or "media resource"? I can't tell from your response. Garland >>>suggested in the original post that he favored the term "media >>> >>> >resource" > > >>>too. >>> >>>Jeff >>> >>>Roy, Radhika R, ALABS wrote: >>> >>> >>> >>> >>> >>>>Jeff: >>>> >>>>Garland and I have been saying exactly what a media server is. A >>>> >>>> >media server will be using many protocols, and MRCP is only of them. > > >>>>In this sense, MRCP is one of the protocols that is used for its >>>> >>>> >media resources control. > > >>>>Who knows MRCP may NOT enough to control all the media resources of a >>>> >>>> >Media Server. > > >>>>Let us see the big picture of a media server. >>>> >>>>Radhika >>>> >>>>-----Original Message----- >>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On >>>> >>>> >Behalf > > >>>>Of Jeff Haynie >>>>Sent: Wednesday, May 19, 2004 8:57 PM >>>>To: Garland Sharratt >>>>Cc: Speechsc@ietf.org >>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>> >>>> >>>>Both you and Radhika seem to highlight exactly what MRCP is NOT and >>>>re-enforce Eric's original request, no? Of course, I'm not implying >>>>that media servers can't also support the MRCP protocol as a fact of >>>>implementation - that's something that's completely within reason. >>>> >>>>Jeff >>>> >>>>Garland Sharratt wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>>To Radhika's list I would also add recording and playback, as well >>>>> >>>>> >as > > >>>>>video announcements, video recording and playback, and video >>>>> >>>>> >bridging. > > >>>>>"Media server" is a generic term in NGN for a multi-purpose slave >>>>>media processing engine controlled by a call agent or application >>>>>server. All NGN architectures have a media server component, often >>>>> >>>>> >by > > >>>>>another name; in 3GPP, for instance, it's called an Media Resource >>>>>Function Processor (MRFP). Media server control interfaces in NGN >>>>>architectures are MGCP, H.248, and SIP. >>>>> >>>>>Garland >>>>> >>>>>-----Original Message----- >>>>>*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On >>>>>Behalf Of *Roy, Radhika R, ALABS >>>>>*Sent:* Wednesday, May 19, 2004 07:18 >>>>>*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger >>>>>*Cc:* Speechsc@ietf.org >>>>>*Subject:* RE: [Speechsc] Media Server or Media Resource >>>>> >>>>>Eric, Klaus, and Sarvi: >>>>> >>>>>Let me try to provide the definition of media servers: >>>>> >>>>>"Media servers (MSs) typically operate with application servers >>>>> >>>>> >(ASs) > > >>>>>to handle and terminate media streams, and provide services such as >>>>>announcement, media bridging, media transcoding, interactive voice >>>>>response (IVR) messages (with or without VocieXML), speech-to-text >>>>>(STT) conversion, text-to-speech (TTS) conversion, and others." >>>>> >>>>>Cheers! >>>>> >>>>>Radhika R. Roy >>>>>AT&T >>>>>732 420 1580 >>>>> >>>>> -----Original Message----- >>>>> *From:* speechsc-admin@ietf.org >>>>> [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus >>>>> *Sent:* Wednesday, May 19, 2004 5:07 AM >>>>> *To:* 'Sarvi Shanmugham'; Eric Burger >>>>> *Cc:* Speechsc@ietf.org >>>>> *Subject:* RE: [Speechsc] Media Server or Media Resource >>>>> >>>>> Hi Eric and Sarvi, >>>>> >>>>> after some internal discussions I prefer to stay with the term >>>>> "media server"! >>>>> >>>>> In draft-burger-sipping-msuri-01.txt (expired IETF internet >>>>> >>>>> >draft, > > >>>>> that was referenced in the speechsc requirements document) the >>>>> following definition of a media server can be found (section 3 on >>>>> page 3): >>>>> "Media servers are devices that perform media processing on >>>>> real-time packet media." >>>>> According to this definition the MRCP server is a media server >>>>> (and not the platform that uses MRCP servers for media >>>>> >>>>> >processing, > > >>>>> which becomes a media proxy). >>>>> In a network architecture that includes MRCP servers there might >>>>> be other media servers. >>>>> >>>>> Could someone point me to the documents of the IETF, 3GPP, ... >>>>> where I can find their definition of a media server. The term >>>>> "media server" is used fairly often (especially in product >>>>> brochures), but it seems to be difficult to find precise >>>>> >>>>> >definitions. > > >>>>> Thanks, >>>>> Klaus >>>>> >>>>> >>>>> >>>>> -----Original Message----- >>>>> *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] >>>>> *Sent:* Mittwoch, 19. Mai 2004 01:49 >>>>> *To:* Garland Sharratt >>>>> *Cc:* Eric Burger; Speechsc@ietf.org >>>>> *Subject:* Re: [Speechsc] Media Server or Media Resource >>>>> >>>>> This is fine by me. And I haven't heard any opposition so >>>>> >>>>> >far. > > >>>>> I will make the necessary edits. >>>>> >>>>> Sarvi >>>>> Garland Sharratt wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>Eric, I concur. Using the term "media server" for MRCPv2 muddies >>>>>> >>>>>> >the > > >>>>>>waters, I think, and implies the two things are the same whereas >>>>>> >>>>>> >they are > > >>>>>>not. >>>>>> >>>>>>Garland >>>>>> >>>>>>-----Original Message----- >>>>>>From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On >>>>>> >>>>>> >Behalf > > >>>>>>Of Jeff Haynie >>>>>>Sent: Monday, May 17, 2004 08:10 >>>>>>To: Eric Burger >>>>>>Cc: Speechsc@ietf.org >>>>>>Subject: Re: [Speechsc] Media Server or Media Resource >>>>>> >>>>>> >>>>>>That's funny - I myself have struggled with the same term and would >>>>>> >>>>>> >be > > >>>>>>much more in favor of "media resource". >>>>>> >>>>>>Jeff >>>>>> >>>>>>Eric Burger wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>>I have a form issue, not necessarily a substance issue. >>>>>>> >>>>>>>Throughout the MRCPv2 document, the "thing that is a server >>>>>>> >>>>>>> >controlled by > > >>>>>>>the MRCPv2 protocol" is called a "Media Server". >>>>>>> >>>>>>>A Media Server is a device that has a well-defined meaning, in the >>>>>>> >>>>>>> >IETF, > > >>>>>>>3GPP (MRF), SIP Forum, IPCC, etc. >>>>>>> >>>>>>>That definition, IMHO, does not really match with "the thing that >>>>>>> >>>>>>> >is a > > >>>>>>>server controlled by the MRCPv2 protocol." In fact, the thing >>>>>>> >>>>>>> >that > > >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>embodies >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>>the accepted version of a Media Server is often a *client* to the >>>>>>> >>>>>>> >MRCPv2 > > >>>>>>>protocol. >>>>>>> >>>>>>>Would anyone be really put out if we did a 1,$:s/media >>>>>>> >>>>>>> >server/media > > >>>>>>>resource/g throughout the document? >>>>>>> >>>>>>>Rationale: The document describes the Media RESOURCE Control >>>>>>> >>>>>>> >Protocol, not > > >>>>>>>the Media SERVER Control Protocol. >>>>>>> >>>>>>> >>>>>>> >>>>>>>Thoughts? Comments? >>>>>>> >>>>>>>_______________________________________________ >>>>>>>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 >>>>>> >>>>>> >>>>>>_______________________________________________ >>>>>>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 >>>> >>>> >>>> >>>> >>>> >>>> >>>_______________________________________________ >>>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 >>> >>> >>> >>> >>> > > >_______________________________________________ >Speechsc mailing list >Speechsc@ietf.org >https://www1.ietf.org/mailman/listinfo/speechsc > > > > > --------------030709070305060907050600 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I can go with this proposal. I would suggest that we loose the v2 portion in the naming, as many of these servers are bound to support v1 for backward compatibility.

Sarvi
Dave Burke wrote: 
I like simplicity and I think the readers of the MRCPv2 specification will
appreciate this also.

We are seeking some sort of general term for discussing entities controlled
by MRCPv2. At first glance "Media Server" appears to be an appropriate
general term but unfortunately it carries with it definition out of scope of
MRCPv2.

What I like about Eric's original suggestion is that the phrase "Media
Server" does not appear at all in the MRCPv2 specification. Building on
this, why not just:

"Media Resource":
    An entity to be controlled by MRCPv2

"MRCPv2 Server":
    Aggregate of one or more "Media Resource", exposed by MRCPv2. ("Server"
for short)

"MRCPv2 Client":
    The entity controlling one or more "Media Resource" via MRCPv2.
("Client" for short).

This avoids confusion and leaves the media server vendors to decide if they
want their product to be an MRCPv2 Client (probably the usual case), or an
MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 Client
and Server (ref my facetious remark earlier about a "Media B2BUA").

- Dave

----- Original Message -----
From: "Roy, Radhika R, ALABS" <rrroy@att.com>
To: "Tim Melanchuk" <timm@convedia.com>; "Sarvi Shanmugham"
<sarvi@cisco.com>
Cc: "Jeff Haynie" <jhaynie@vocalocity.net>; "Garland Sharratt"
<gsharratt@convedia.com>; <Speechsc@ietf.org>
Sent: Friday, May 21, 2004 5:07 AM
Subject: RE: [Speechsc] Media Server or Media Resource


All:

Seeing all definitions, it appears that we can safely conclude what
Sarvi has proposed:

1. "MRCP server" or "MRCP Media server" - (a media server that contains
only MRCP media resources)

2. "MRCP resource" or  "MRCP media resource" - (self explanatory)

3. "MRCP resources on the Media Server" - (a media server that contains
MRCP resources in addition to other media resources)

4. "Media Server" - (a media server that contains MRCP plus other media
resources in the context of our works)

Items 3 and 4 are the same in the context of our works.

Radhika

-----Original Message-----
From: Tim Melanchuk [mailto:timm@convedia.com]
Sent: Thursday, May 20, 2004 5:49 PM
To: Sarvi Shanmugham
Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt;
Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


this approach sounds reasonable. "media server" is somewhat of
generic term that is used for slightly different things in different
contexts. for example, rtsp uses the term media server extensively
and defines it as:

         Media server: The server providing playback services for one or
              more media streams. Different media streams within a
              presentation may originate from different media servers. A
              media server may reside on the same or a different host as
              the web server the presentation is invoked from.



Sarvi Shanmugham wrote:

  
Well from what I am hearing so far, a Media server is an entity that
    
may
  
support multiple media resources on it.  But, the resources may not
    
all
  
be controlled by single protocol.

So it would be a misnomer to call the whole box an "MRCP server" or
"MRCP media server".
But  from the definitions flying around, it looks like people do agree
    

  
that the box as a whole can be called/classified as a "Media server"
without any protocol implications.

So here is a suggestion, I propose we change all occurances of "MRCP
server" or "MRCP Media server".
I will instead use one of the following terms/phrases depending on the
    

  
context.
    To refer to individual resources I will use "MRCP resource" or
"MRCP media resource".
    To refer to the whole box that may have multiple media
resources(MRCP or otherwise) I will use the phrase  "Media Server" or
"MRCP resources on the Media Server" as appropriate.

Any thoughts.

Sarvi

Roy, Radhika R, ALABS wrote:

    
Jeff:

OK, let us go back to analyze these terms: Media Resources and Media
      
Server.
  
That is, MRCP is used to control (many, if not all) "media resources"
      
of a media server.
  
Radhika

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On
      
Behalf
  
Of Jeff Haynie
Sent: Wednesday, May 19, 2004 9:48 PM
To: Roy, Radhika R, ALABS
Cc: Garland Sharratt; Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


OK, sorry, I'm confused.  Do you support using the term "media server"
      

  
or "media resource"?  I can't tell from your response.  Garland
suggested in the original post that he favored the term "media
      
resource"
  
too.

Jeff

Roy, Radhika R, ALABS wrote:



      
Jeff:

Garland and I have been saying exactly what a media server is. A
        
media server will be using many protocols, and MRCP is only of them.
  
In this sense, MRCP is one of the protocols that is used for its
        
media resources control.
  
Who knows MRCP may NOT enough to control all the media resources of a
        
Media Server.
  
Let us see the big picture of a media server.

Radhika

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On
        
Behalf
  
Of Jeff Haynie
Sent: Wednesday, May 19, 2004 8:57 PM
To: Garland Sharratt
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


Both you and Radhika seem to highlight exactly what MRCP is NOT and
re-enforce Eric's original request, no?  Of course, I'm not implying
that media servers can't also support the MRCP protocol as a fact of
implementation - that's something that's completely within reason.

Jeff

Garland Sharratt wrote:





        
To Radhika's list I would also add recording and playback, as well
          
as
  
video announcements, video recording and playback, and video
          
bridging.
  
"Media server" is a generic term in NGN for a multi-purpose slave
media processing engine controlled by a call agent or application
server.  All NGN architectures have a media server component, often
          
by
  
another name; in 3GPP, for instance, it's called an Media Resource
Function Processor (MRFP).  Media server control interfaces in NGN
architectures are MGCP, H.248, and SIP.

Garland

-----Original Message-----
*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On
Behalf Of *Roy, Radhika R, ALABS
*Sent:* Wednesday, May 19, 2004 07:18
*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger
*Cc:* Speechsc@ietf.org
*Subject:* RE: [Speechsc] Media Server or Media Resource

Eric, Klaus, and Sarvi:

Let me try to provide the definition of media servers:

"Media servers (MSs) typically operate with application servers
          
(ASs)
  
to handle and terminate media streams, and provide services such as
announcement, media bridging, media transcoding, interactive voice
response (IVR) messages (with or without VocieXML), speech-to-text
(STT) conversion, text-to-speech (TTS) conversion, and others."

Cheers!

Radhika R. Roy
AT&T
732 420 1580

  -----Original Message-----
  *From:* speechsc-admin@ietf.org
  [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus
  *Sent:* Wednesday, May 19, 2004 5:07 AM
  *To:* 'Sarvi Shanmugham'; Eric Burger
  *Cc:* Speechsc@ietf.org
  *Subject:* RE: [Speechsc] Media Server or Media Resource

  Hi Eric and Sarvi,

  after some internal discussions I prefer to stay with the term
  "media server"!

  In draft-burger-sipping-msuri-01.txt (expired IETF internet
          
draft,
  
  that was referenced in the speechsc requirements document) the
  following definition of a media server can be found (section 3 on
  page 3):
  "Media servers are devices that perform media processing on
  real-time packet media."
  According to this definition the MRCP server is a media server
  (and not the platform that uses MRCP servers for media
          
processing,
  
  which becomes a media proxy).
  In a network architecture that includes MRCP servers there might
  be other media servers.

  Could someone point me to the documents of the IETF, 3GPP, ...
  where I can find their definition of a media server. The term
  "media server" is used fairly often (especially in product
  brochures), but it seems to be difficult to find precise
          
definitions.
  
  Thanks,
  Klaus



      -----Original Message-----
      *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com]
      *Sent:* Mittwoch, 19. Mai 2004 01:49
      *To:* Garland Sharratt
      *Cc:* Eric Burger; Speechsc@ietf.org
      *Subject:* Re: [Speechsc] Media Server or Media Resource

      This is fine by me. And I haven't heard any opposition so
          
far.
  
       I will make the necessary edits.

      Sarvi
      Garland Sharratt wrote:





          
Eric, I concur.  Using the term "media server" for MRCPv2 muddies
            
the
  
waters, I think, and implies the two things are the same whereas
            
they are
  
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On
            
Behalf
  
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would
            
be
  
much more in favor of "media resource".

Jeff

Eric Burger wrote:







            
<ChairHat state="off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server
              
controlled by
  
the MRCPv2 protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the
              
IETF,
  
3GPP (MRF), SIP Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that
              
is a
  
server controlled by the MRCPv2 protocol."  In fact, the thing
              
that
  




              
embodies






            
the accepted version of a Media Server is often a *client* to the
              
MRCPv2
  
protocol.

Would anyone be really put out if we did a 1,$:s/media
              
server/media
  
resource/g throughout the document?

Rationale: The document describes the Media RESOURCE Control
              
Protocol, not
  
the Media SERVER Control Protocol.

</ChairHat>

Thoughts?  Comments?

_______________________________________________
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


_______________________________________________
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




        
_______________________________________________
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



      


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

--------------030709070305060907050600-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Sat May 22 06:26:17 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26516 for ; Sat, 22 May 2004 06:26:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRTdA-0004fS-Pj for speechsc-archive@odin.ietf.org; Sat, 22 May 2004 06:21:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MALSAa017943 for speechsc-archive@odin.ietf.org; Sat, 22 May 2004 06:21:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRTbR-0004FN-Nr for speechsc-web-archive@optimus.ietf.org; Sat, 22 May 2004 06:19:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26121 for ; Sat, 22 May 2004 06:19:36 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRTbN-0004bX-C9 for speechsc-web-archive@ietf.org; Sat, 22 May 2004 06:19:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRTaB-0004LQ-00 for speechsc-web-archive@ietf.org; Sat, 22 May 2004 06:18:26 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRTZ7-00043u-00 for speechsc-web-archive@ietf.org; Sat, 22 May 2004 06:17:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRTUz-0002xV-4r; Sat, 22 May 2004 06:13:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRTQM-0001HL-Di for speechsc@optimus.ietf.org; Sat, 22 May 2004 06:08:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24893 for ; Sat, 22 May 2004 06:08:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRTQI-0002GW-FN for speechsc@ietf.org; Sat, 22 May 2004 06:08:10 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRTPM-00028r-00 for speechsc@ietf.org; Sat, 22 May 2004 06:07:15 -0400 Received: from [212.17.54.82] (helo=mail.voxpilot.com) by ietf-mx with esmtp (Exim 4.12) id 1BRTP9-00021K-00 for Speechsc@ietf.org; Sat, 22 May 2004 06:06:59 -0400 Received: from daburkew2k (dsl-34-34.dsl.netsource.ie [213.79.34.34]) by mail.voxpilot.com (Postfix) with ESMTP id C7FFB21403D; Sat, 22 May 2004 11:12:19 +0100 (IST) Message-ID: <004501c43fe4$7e6e0790$0a01a8c0@db01.voxpilot.com> From: "Dave Burke" To: "Sarvi Shanmugham" Cc: "Roy, Radhika R, ALABS" , "Tim Melanchuk" , "Jeff Haynie" , "Garland Sharratt" , References: <34DA635B184A644DA4588E260EC0A25A0725E6AF@ACCLUST02EVS1.ugd.att.com> <001501c43f12$574e5890$ca00000a@db01.voxpilot.com> <40AE6704.1010805@cisco.com> Subject: Re: [Speechsc] Media Server or Media Resource Date: Sat, 22 May 2004 11:06:32 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003C_01C43FEC.D7029940" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE, HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_003C_01C43FEC.D7029940 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Agreed. - Dave ----- Original Message -----=20 From: Sarvi Shanmugham=20 To: Dave Burke=20 Cc: Roy, Radhika R, ALABS ; Tim Melanchuk ; Jeff Haynie ; Garland = Sharratt ; Speechsc@ietf.org=20 Sent: Friday, May 21, 2004 9:31 PM Subject: Re: [Speechsc] Media Server or Media Resource I can go with this proposal. I would suggest that we loose the v2 = portion in the naming, as many of these servers are bound to support v1 = for backward compatibility. Sarvi Dave Burke wrote:=20 I like simplicity and I think the readers of the MRCPv2 specification = will appreciate this also. We are seeking some sort of general term for discussing entities = controlled by MRCPv2. At first glance "Media Server" appears to be an appropriate general term but unfortunately it carries with it definition out of = scope of MRCPv2. What I like about Eric's original suggestion is that the phrase "Media Server" does not appear at all in the MRCPv2 specification. Building on this, why not just: "Media Resource": An entity to be controlled by MRCPv2 "MRCPv2 Server": Aggregate of one or more "Media Resource", exposed by MRCPv2. = ("Server" for short) "MRCPv2 Client": The entity controlling one or more "Media Resource" via MRCPv2. ("Client" for short). This avoids confusion and leaves the media server vendors to decide if = they want their product to be an MRCPv2 Client (probably the usual case), or = an MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 = Client and Server (ref my facetious remark earlier about a "Media B2BUA"). - Dave ----- Original Message ----- From: "Roy, Radhika R, ALABS" To: "Tim Melanchuk" ; "Sarvi Shanmugham" Cc: "Jeff Haynie" ; "Garland Sharratt" ; Sent: Friday, May 21, 2004 5:07 AM Subject: RE: [Speechsc] Media Server or Media Resource All: Seeing all definitions, it appears that we can safely conclude what Sarvi has proposed: 1. "MRCP server" or "MRCP Media server" - (a media server that contains only MRCP media resources) 2. "MRCP resource" or "MRCP media resource" - (self explanatory) 3. "MRCP resources on the Media Server" - (a media server that contains MRCP resources in addition to other media resources) 4. "Media Server" - (a media server that contains MRCP plus other media resources in the context of our works) Items 3 and 4 are the same in the context of our works. Radhika -----Original Message----- From: Tim Melanchuk [mailto:timm@convedia.com] Sent: Thursday, May 20, 2004 5:49 PM To: Sarvi Shanmugham Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource this approach sounds reasonable. "media server" is somewhat of generic term that is used for slightly different things in different contexts. for example, rtsp uses the term media server extensively and defines it as: Media server: The server providing playback services for one or more media streams. Different media streams within a presentation may originate from different media servers. A media server may reside on the same or a different host as the web server the presentation is invoked from. Sarvi Shanmugham wrote: =20 Well from what I am hearing so far, a Media server is an entity that =20 may =20 support multiple media resources on it. But, the resources may not =20 all =20 be controlled by single protocol. So it would be a misnomer to call the whole box an "MRCP server" or "MRCP media server". But from the definitions flying around, it looks like people do agree =20 =20 that the box as a whole can be called/classified as a "Media server" without any protocol implications. So here is a suggestion, I propose we change all occurances of "MRCP server" or "MRCP Media server". I will instead use one of the following terms/phrases depending on the =20 =20 context. To refer to individual resources I will use "MRCP resource" or "MRCP media resource". To refer to the whole box that may have multiple media resources(MRCP or otherwise) I will use the phrase "Media Server" or "MRCP resources on the Media Server" as appropriate. Any thoughts. Sarvi Roy, Radhika R, ALABS wrote: =20 Jeff: OK, let us go back to analyze these terms: Media Resources and Media =20 Server. =20 That is, MRCP is used to control (many, if not all) "media resources" =20 of a media server. =20 Radhika -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On =20 Behalf =20 Of Jeff Haynie Sent: Wednesday, May 19, 2004 9:48 PM To: Roy, Radhika R, ALABS Cc: Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource OK, sorry, I'm confused. Do you support using the term "media server" =20 =20 or "media resource"? I can't tell from your response. Garland suggested in the original post that he favored the term "media =20 resource" =20 too. Jeff Roy, Radhika R, ALABS wrote: =20 Jeff: Garland and I have been saying exactly what a media server is. A =20 media server will be using many protocols, and MRCP is only of them. =20 In this sense, MRCP is one of the protocols that is used for its =20 media resources control. =20 Who knows MRCP may NOT enough to control all the media resources of a =20 Media Server. =20 Let us see the big picture of a media server. Radhika -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On =20 Behalf =20 Of Jeff Haynie Sent: Wednesday, May 19, 2004 8:57 PM To: Garland Sharratt Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource Both you and Radhika seem to highlight exactly what MRCP is NOT and re-enforce Eric's original request, no? Of course, I'm not implying that media servers can't also support the MRCP protocol as a fact of implementation - that's something that's completely within reason. Jeff Garland Sharratt wrote: =20 To Radhika's list I would also add recording and playback, as well =20 as =20 video announcements, video recording and playback, and video =20 bridging. =20 "Media server" is a generic term in NGN for a multi-purpose slave media processing engine controlled by a call agent or application server. All NGN architectures have a media server component, often =20 by =20 another name; in 3GPP, for instance, it's called an Media Resource Function Processor (MRFP). Media server control interfaces in NGN architectures are MGCP, H.248, and SIP. Garland -----Original Message----- *From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On Behalf Of *Roy, Radhika R, ALABS *Sent:* Wednesday, May 19, 2004 07:18 *To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger *Cc:* Speechsc@ietf.org *Subject:* RE: [Speechsc] Media Server or Media Resource Eric, Klaus, and Sarvi: Let me try to provide the definition of media servers: "Media servers (MSs) typically operate with application servers =20 (ASs) =20 to handle and terminate media streams, and provide services such as announcement, media bridging, media transcoding, interactive voice response (IVR) messages (with or without VocieXML), speech-to-text (STT) conversion, text-to-speech (TTS) conversion, and others." Cheers! Radhika R. Roy AT&T 732 420 1580 -----Original Message----- *From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus *Sent:* Wednesday, May 19, 2004 5:07 AM *To:* 'Sarvi Shanmugham'; Eric Burger *Cc:* Speechsc@ietf.org *Subject:* RE: [Speechsc] Media Server or Media Resource Hi Eric and Sarvi, after some internal discussions I prefer to stay with the term "media server"! In draft-burger-sipping-msuri-01.txt (expired IETF internet =20 draft, =20 that was referenced in the speechsc requirements document) the following definition of a media server can be found (section 3 on page 3): "Media servers are devices that perform media processing on real-time packet media." According to this definition the MRCP server is a media server (and not the platform that uses MRCP servers for media =20 processing, =20 which becomes a media proxy). In a network architecture that includes MRCP servers there might be other media servers. Could someone point me to the documents of the IETF, 3GPP, ... where I can find their definition of a media server. The term "media server" is used fairly often (especially in product brochures), but it seems to be difficult to find precise =20 definitions. =20 Thanks, Klaus -----Original Message----- *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com] *Sent:* Mittwoch, 19. Mai 2004 01:49 *To:* Garland Sharratt *Cc:* Eric Burger; Speechsc@ietf.org *Subject:* Re: [Speechsc] Media Server or Media Resource This is fine by me. And I haven't heard any opposition so =20 far. =20 I will make the necessary edits. Sarvi Garland Sharratt wrote: =20 Eric, I concur. Using the term "media server" for MRCPv2 muddies =20 the =20 waters, I think, and implies the two things are the same whereas =20 they are =20 not. Garland -----Original Message----- From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On =20 Behalf =20 Of Jeff Haynie Sent: Monday, May 17, 2004 08:10 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource That's funny - I myself have struggled with the same term and would =20 be =20 much more in favor of "media resource". Jeff Eric Burger wrote: =20 I have a form issue, not necessarily a substance issue. Throughout the MRCPv2 document, the "thing that is a server =20 controlled by =20 the MRCPv2 protocol" is called a "Media Server". A Media Server is a device that has a well-defined meaning, in the =20 IETF, =20 3GPP (MRF), SIP Forum, IPCC, etc. That definition, IMHO, does not really match with "the thing that =20 is a =20 server controlled by the MRCPv2 protocol." In fact, the thing =20 that =20 =20 embodies =20 the accepted version of a Media Server is often a *client* to the =20 MRCPv2 =20 protocol. Would anyone be really put out if we did a 1,$:s/media =20 server/media =20 resource/g throughout the document? Rationale: The document describes the Media RESOURCE Control =20 Protocol, not =20 the Media SERVER Control Protocol. Thoughts? Comments? _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 _______________________________________________ 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 =20 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc =20 ------=_NextPart_000_003C_01C43FEC.D7029940 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Agreed.
 
- Dave
----- Original Message -----
From:=20 Sarvi = Shanmugham=20
Cc: Roy, Radhika R, ALABS ; Tim = Melanchuk ; Jeff=20 Haynie ; Garland Sharratt ; Speechsc@ietf.org=20
Sent: Friday, May 21, 2004 9:31 = PM
Subject: Re: [Speechsc] Media = Server or=20 Media Resource

I can go with this proposal. I would suggest that we = loose the=20 v2 portion in the naming, as many of these servers are bound to = support v1 for=20 backward compatibility.

Sarvi
Dave Burke wrote:=20 
I like simplicity and I think the readers =
of the MRCPv2 specification will
appreciate this also.

We are seeking some sort of general term for discussing entities =
controlled
by MRCPv2. At first glance "Media Server" appears to be an appropriate
general term but unfortunately it carries with it definition out of =
scope of
MRCPv2.

What I like about Eric's original suggestion is that the phrase "Media
Server" does not appear at all in the MRCPv2 specification. Building on
this, why not just:

"Media Resource":
    An entity to be controlled by MRCPv2

"MRCPv2 Server":
    Aggregate of one or more "Media Resource", exposed by MRCPv2. =
("Server"
for short)

"MRCPv2 Client":
    The entity controlling one or more "Media Resource" via MRCPv2.
("Client" for short).

This avoids confusion and leaves the media server vendors to decide if =
they
want their product to be an MRCPv2 Client (probably the usual case), or =
an
MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 =
Client
and Server (ref my facetious remark earlier about a "Media B2BUA").

- Dave

----- Original Message -----
From: "Roy, Radhika R, ALABS" <rrroy@att.com>
To: "Tim Melanchuk" <timm@convedia.com>; "Sarvi =
Shanmugham"
<sarvi@cisco.com>
Cc: "Jeff Haynie" <jhaynie@vocalocity.net>=
; "Garland Sharratt"
<gsharratt@convedia.com>=
; <Speechsc@ietf.org>
Sent: Friday, May 21, 2004 5:07 AM
Subject: RE: [Speechsc] Media Server or Media Resource


All:

Seeing all definitions, it appears that we can safely conclude what
Sarvi has proposed:

1. "MRCP server" or "MRCP Media server" - (a media server that contains
only MRCP media resources)

2. "MRCP resource" or  "MRCP media resource" - (self explanatory)

3. "MRCP resources on the Media Server" - (a media server that contains
MRCP resources in addition to other media resources)

4. "Media Server" - (a media server that contains MRCP plus other media
resources in the context of our works)

Items 3 and 4 are the same in the context of our works.

Radhika

-----Original Message-----
From: Tim Melanchuk [mailto:timm@convedia.com]
Sent: Thursday, May 20, 2004 5:49 PM
To: Sarvi Shanmugham
Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt;
Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


this approach sounds reasonable. "media server" is somewhat of
generic term that is used for slightly different things in different
contexts. for example, rtsp uses the term media server extensively
and defines it as:

         Media server: The server providing playback services for one or
              more media streams. Different media streams within a
              presentation may originate from different media servers. A
              media server may reside on the same or a different host as
              the web server the presentation is invoked from.



Sarvi Shanmugham wrote:

  
Well from what I am hearing =
so far, a Media server is an entity that
    
may
  
support multiple media =
resources on it.  But, the resources may not
    
all
  
be controlled by single =
protocol.

So it would be a misnomer to call the whole box an "MRCP server" or
"MRCP media server".
But  from the definitions flying around, it looks like people do agree
    

  
that the box as a whole can =
be called/classified as a "Media server"
without any protocol implications.

So here is a suggestion, I propose we change all occurances of "MRCP
server" or "MRCP Media server".
I will instead use one of the following terms/phrases depending on the
    

  
context.
    To refer to individual resources I will use "MRCP resource" or
"MRCP media resource".
    To refer to the whole box that may have multiple media
resources(MRCP or otherwise) I will use the phrase  "Media Server" or
"MRCP resources on the Media Server" as appropriate.

Any thoughts.

Sarvi

Roy, Radhika R, ALABS wrote:

    
Jeff:

OK, let us go back to analyze these terms: Media Resources and Media
      
Server.
  
That is, MRCP is used to =
control (many, if not all) "media resources"
      
of a media =
server.
  
Radhika

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On
      
Behalf
  
Of Jeff Haynie
Sent: Wednesday, May 19, 2004 9:48 PM
To: Roy, Radhika R, ALABS
Cc: Garland Sharratt; Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


OK, sorry, I'm confused.  Do you support using the term "media server"
      

  
or "media resource"?  I =
can't tell from your response.  Garland
suggested in the original post that he favored the term "media
      
resource"
  
too.

Jeff

Roy, Radhika R, ALABS wrote:



      
Jeff:

Garland and I have been saying exactly what a media server is. A
        
media server will be using many protocols, and MRCP is =
only of them.
  
In this sense, MRCP is =
one of the protocols that is used for its
        
media resources control.
  
Who knows MRCP may NOT =
enough to control all the media resources of a
        
Media Server.
  
Let us see the big =
picture of a media server.

Radhika

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On
        
Behalf
  
Of Jeff Haynie
Sent: Wednesday, May 19, 2004 8:57 PM
To: Garland Sharratt
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


Both you and Radhika seem to highlight exactly what MRCP is NOT and
re-enforce Eric's original request, no?  Of course, I'm not implying
that media servers can't also support the MRCP protocol as a fact of
implementation - that's something that's completely within reason.

Jeff

Garland Sharratt wrote:





        
To Radhika's list I =
would also add recording and playback, as well
          
as
  
video announcements, =
video recording and playback, and video
          
bridging.
  
"Media server" is a =
generic term in NGN for a multi-purpose slave
media processing engine controlled by a call agent or application
server.  All NGN architectures have a media server component, often
          
by
  
another name; in =
3GPP, for instance, it's called an Media Resource
Function Processor (MRFP).  Media server control interfaces in NGN
architectures are MGCP, H.248, and SIP.

Garland

-----Original Message-----
*From:* speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]*On
Behalf Of *Roy, Radhika R, ALABS
*Sent:* Wednesday, May 19, 2004 07:18
*To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger
*Cc:* Speechsc@ietf.org
*Subject:* RE: [Speechsc] Media Server or Media Resource

Eric, Klaus, and Sarvi:

Let me try to provide the definition of media servers:

"Media servers (MSs) typically operate with application servers
          
(ASs)
  
to handle and =
terminate media streams, and provide services such as
announcement, media bridging, media transcoding, interactive voice
response (IVR) messages (with or without VocieXML), speech-to-text
(STT) conversion, text-to-speech (TTS) conversion, and others."

Cheers!

Radhika R. Roy
AT&T
732 420 1580

  -----Original Message-----
  *From:* speechsc-admin@ietf.org
  [mailto:speechsc-admin@ietf.org]*On Behalf Of *Reifenrath, Klaus
  *Sent:* Wednesday, May 19, 2004 5:07 AM
  *To:* 'Sarvi Shanmugham'; Eric Burger
  *Cc:* Speechsc@ietf.org
  *Subject:* RE: [Speechsc] Media Server or Media Resource

  Hi Eric and Sarvi,

  after some internal discussions I prefer to stay with the term
  "media server"!

  In draft-burger-sipping-msuri-01.txt (expired IETF internet
          
draft,
  
  that was referenced =
in the speechsc requirements document) the
  following definition of a media server can be found (section 3 on
  page 3):
  "Media servers are devices that perform media processing on
  real-time packet media."
  According to this definition the MRCP server is a media server
  (and not the platform that uses MRCP servers for media
          
processing,
  
  which becomes a =
media proxy).
  In a network architecture that includes MRCP servers there might
  be other media servers.

  Could someone point me to the documents of the IETF, 3GPP, ...
  where I can find their definition of a media server. The term
  "media server" is used fairly often (especially in product
  brochures), but it seems to be difficult to find precise
          
definitions.
  
  Thanks,
  Klaus



      -----Original Message-----
      *From:* Sarvi Shanmugham [mailto:sarvi@cisco.com]
      *Sent:* Mittwoch, 19. Mai 2004 01:49
      *To:* Garland Sharratt
      *Cc:* Eric Burger; Speechsc@ietf.org
      *Subject:* Re: [Speechsc] Media Server or Media Resource

      This is fine by me. And I haven't heard any opposition so
          
far.
  
       I will make =
the necessary edits.

      Sarvi
      Garland Sharratt wrote:





          
Eric, I concur.  =
Using the term "media server" for MRCPv2 muddies
            =
the 
waters, I think, =
and implies the two things are the same whereas
            =
they are 
not.

Garland

-----Original Message-----
From: speechsc-admin@ietf.org [mailto:speechsc-admin@ietf.org]On
            =
Behalf 
Of Jeff Haynie
Sent: Monday, May 17, 2004 08:10
To: Eric Burger
Cc: Speechsc@ietf.org
Subject: Re: [Speechsc] Media Server or Media Resource


That's funny - I myself have struggled with the same term and would
            =
be 
much more in favor =
of "media resource".

Jeff

Eric Burger wrote:







            
<ChairHat =
state=3D"off">
I have a form issue, not necessarily a substance issue.

Throughout the MRCPv2 document, the "thing that is a server
              =

controlled by
  
the MRCPv2 =
protocol" is called a "Media Server".

A Media Server is a device that has a well-defined meaning, in the
              =

IETF,
  
3GPP (MRF), SIP =
Forum, IPCC, etc.

That definition, IMHO, does not really match with "the thing that
              =

is a
  
server controlled =
by the MRCPv2 protocol."  In fact, the thing
              =

that
  



              
embodies






            
the accepted =
version of a Media Server is often a *client* to the
              =

MRCPv2
  
protocol.

Would anyone be really put out if we did a 1,$:s/media
              =

server/media
  
resource/g =
throughout the document?

Rationale: The document describes the Media RESOURCE Control
              =

Protocol, not
  
the Media SERVER =
Control Protocol.

</ChairHat>

Thoughts?  Comments?

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








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


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







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




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

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



      


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

------=_NextPart_000_003C_01C43FEC.D7029940-- _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Sun May 23 15:36:53 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02391 for ; Sun, 23 May 2004 15:36:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRykt-0007yx-C8 for speechsc-archive@odin.ietf.org; Sun, 23 May 2004 15:35:31 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4NJZVBS030683 for speechsc-archive@odin.ietf.org; Sun, 23 May 2004 15:35:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRyhD-0007Yv-F1 for speechsc-web-archive@optimus.ietf.org; Sun, 23 May 2004 15:31:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02140 for ; Sun, 23 May 2004 15:31:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRyhB-0004Zf-Ri for speechsc-web-archive@ietf.org; Sun, 23 May 2004 15:31:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRygF-0004K1-00 for speechsc-web-archive@ietf.org; Sun, 23 May 2004 15:30:44 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRyfY-00044K-00 for speechsc-web-archive@ietf.org; Sun, 23 May 2004 15:30:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRycf-0006pt-R0; Sun, 23 May 2004 15:27:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRyTp-0005n8-4K for speechsc@optimus.ietf.org; Sun, 23 May 2004 15:17:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01762 for ; Sun, 23 May 2004 15:17:51 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRyTn-00014f-Qq for speechsc@ietf.org; Sun, 23 May 2004 15:17:51 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRySr-0000oZ-00 for speechsc@ietf.org; Sun, 23 May 2004 15:16:54 -0400 Received: from [195.222.227.10] (helo=gromit.ibp.de) by ietf-mx with esmtp (Exim 4.12) id 1BRySF-0007jE-00 for speechsc@ietf.org; Sun, 23 May 2004 15:16:16 -0400 Received: from moody.ibp.de ([195.222.227.22] helo=ibp.de) by gromit.ibp.de with esmtp (Exim 4.33) id 1BRyNm-0008V6-KC for speechsc@ietf.org; Sun, 23 May 2004 21:11:38 +0200 Message-ID: <40B0F7E7.4080605@ibp.de> Date: Sun, 23 May 2004 21:13:43 +0200 From: Claudia Daboul User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925 X-Accept-Language: en-us, en MIME-Version: 1.0 To: speechsc@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Speechsc] Speaker Verification Comments Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, I have some comments and some questions on the Speaker Verification section of the MRCPv2 spec. By the way of introduction: I took part on some integrations of speaker verification functionality in the ECTF S.100 framework and also in other vendor specific frameworks. Some intergrations were based on Nuance's Verifier/Recognizer but we also integrated a "standalone" verifier running in parallel with an independent recognizer. My questions/comments: 1 a) It seems impossible to create a new speaker identification group with the protocol, since according to the examples for VER-SET-VOICEPRINT, it will fail if the group doesn't exist. It should be possible to specify a new group in a training session, but not in an identification session. The problem seems to be that the session type can only be specified after the voiceprint is set. This leads me to the next question, which is a bit more general. 1 b) Why should the speaker model be changeable in a training or verification session? In the frameworks I've worked in so far, a training or verification session has always been associated with only one speaker model/group record. This also means that the commands SET-VOICEPRINT and SET-PARAMS(verification-mode) are included in the START-SESSION command. Furthermore the parameters "security-level", "num-min-verification-phrases" and "num-max-verification-phrases" are usually specified for a session and not for a single utterance (in the VERIFY command). 1 c) The headerfields voiceprint-uri and adapt-model can't be fixed through the SET-PARAMS function, although they will usually not change in an application. 1 d) The protocol doesn't specify an interval for verification and training scores. 1 e) Shouldn't it be possible for the client to set thresholds for acceptance or rejection and for adaptation based on verification/training scores? 2 a) A question concerning buffering in a file (using VERIFY with the "save-waveform" headerfield): It is not clear to me what happens when VERIFIY is called for the second time with the header-field "save-waveform = true". Should the second utterance be appended to the first one in the already existing file or will a new file be created for each utterance? 2 b) For verification from a file the VERIFY function is used, although the action is similar to the VERIFY-FROM-BUFFER function. 3 a) Why can a digit sequence be specified as a required phrase, but not a text phrase? In any case a recognizer is needed to check the required phrase or digit sequence, but then it depends on the grammar used by the recognizer which phrases can be used as the required phrases. 3 b) For checking the required phrase or digit sequence a standalone verifier would have to communicate with a recognizer running at the same time. This would only make sense, when verifier and recognizer are on the same host. When they are on different hosts, I suppose that the communication would have to include the client, but then it would be easier, if the client checks the required phrase itself and deletes the utterance from the verification process if necessary. 3 c) I did not quite understand how the "verification-type" parameter should influence the verifiers behaviour. 4) Some database operations are missing in the spec, which I think are necessary: 4 a) It should be possible to make copies of speaker models and of group records. 4 b) As a voiceprint can be part of several groups it should be possible to delete a group record without deleting all the voiceprints it contains. 4 c) There should be a function allowing to subscribe existing voiceprints to a group which may already exist or otherwise be created. 5) When verifier and recognizer are colocated (in one session), the VERIFY and RECOGNIZE commands usually specify the same action twice. 6) There is no parameter for the verifier specifying the maximum length of an utterance. For the recognizer it was called recognition-timeout. Suggestions: 1a)&1b) The START-SESSION command should have the following optional header fields: - adapt-model, - voiceprint-uri, - voiceprint-identifier, - voiceprint-group, - verification-mode, - security-level, - num-min-verification-phrases, - num-max-verification-phrases. The SET-VOICEPRINT command should be ommited. 1 c) The headerfields voiceprint-uri and adapt-model should be settable also through the SET-PARAMS function. 1 d) Set the interval for verification and training scores to [-100, 100]. 1 e) Allow setting thresholds for acceptance or rejection and for adaptation based on verification/training scores. 2 a) Make file buffering similar to internal buffering. Thus utterances should be concatenated and there should be a mechanism to delete the buffering file. Alternative: By default create a new file for each utterance, but if the client wishes to append an utterance to an existing file, it should set the header-field "waveform-url = existing waveform-url" together with "save-waveform=true" in the VERIFY function. 2 b) Use the VER-FROM-BUFFER (with the headerfield input-waveform-url) function rather than VERIFY to process the utterances stored in the file. 3 a) Allow also text phrases as required phrases. 3 b) There should be a communication mechanism between verifier and recognizer similar to the communtication between player and recognizer when the prompt is finished. When verifier and recognizer are on different hosts, the required phrase should not be settable. 4 a) Extend the DELETE-operation to allow deleting a group record without deleting all the voiceprints it contains. 4 b) Define a COPY-RECORD function for speaker models and groups. 4 c) Define a SUBSCRIBE-GROUP function. Alternative: Make subscription a special case of the COPY-RECORD function. 5) Allow sending the VERIFY and RECOGNIZE commands in one message, when verifier and recognizer are in the same session. 6) Rename the headerfield recognition-timeout to max-speech-duration and make it an optional headerfield of the VERIFY command. With best regards, Claudia Daboul -- Dr. Claudia Daboul Luetkensallee 19 22041 Hamburg Tel.: +49 (40) 3172541 Fax.: +49 (40) 3172547 E-mail: claudia@ibp.de _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Sun May 23 22:23:43 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20657 for ; Sun, 23 May 2004 22:23:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BS52s-0007FJ-U8 for speechsc-archive@odin.ietf.org; Sun, 23 May 2004 22:18:31 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4O2IUPJ027848 for speechsc-archive@odin.ietf.org; Sun, 23 May 2004 22:18:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BS4ue-0005bF-8y for speechsc-web-archive@optimus.ietf.org; Sun, 23 May 2004 22:10:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20198 for ; Sun, 23 May 2004 22:09:56 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BS4ub-0001YN-0K for speechsc-web-archive@ietf.org; Sun, 23 May 2004 22:09:57 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BS4th-0001IT-00 for speechsc-web-archive@ietf.org; Sun, 23 May 2004 22:09:02 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BS4tH-00012j-00 for speechsc-web-archive@ietf.org; Sun, 23 May 2004 22:08:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BS4mv-0004AA-J1; Sun, 23 May 2004 22:02:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BS4i9-0003fD-Dk for speechsc@optimus.ietf.org; Sun, 23 May 2004 21:57:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19822 for ; Sun, 23 May 2004 21:57:02 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BS4i6-0005tX-Hl for speechsc@ietf.org; Sun, 23 May 2004 21:57:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BS4hE-0005dl-00 for speechsc@ietf.org; Sun, 23 May 2004 21:56:09 -0400 Received: from salvelinus.brooktrout.com ([204.176.205.6]) by ietf-mx with esmtp (Exim 4.12) id 1BS4gN-0005NB-00 for speechsc@ietf.org; Sun, 23 May 2004 21:55:15 -0400 Received: from nhmail2.needham.brooktrout.com (nhmail2.eng.brooktrout.com [204.176.205.242]) by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id i4O1qZ4W011520; Sun, 23 May 2004 21:52:37 -0400 (EDT) Received: by nhmail2.eng.brooktrout.com with Internet Mail Service (5.5.2653.19) id ; Sun, 23 May 2004 21:51:17 -0400 Message-ID: From: Eric Burger To: "''Sarvi Shanmugham' '" Cc: "'IETF SPEECHSC (E-mail) '" Subject: RE: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs Date: Sun, 23 May 2004 21:51:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 [chair hat off] agreed [chair hat on] -----Original Message----- From: Reifenrath, Klaus To: 'Sarvi Shanmugham' Cc: IETF SPEECHSC (E-mail) Sent: 5/19/04 11:58 AM Subject: RE: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs Hi Sarvi, with your change 17) DTMF tone recognition became a SHOULD for the recognizer resource. DTMF tone recognition is not a natural feature of SPEECH recognition engines. Furthermore host based DTMF recognition seems not to be very common. Therefore I suggest, to replace the SHOULD with a MAY. Regards, Klaus -----Original Message----- From: Sarvi Shanmugham [mailto:sarvi@cisco.com] Sent: Donnerstag, 13. Mai 2004 21:58 To: IETF SPEECHSC (E-mail) Subject: [Speechsc] draft-ietf-speechsc-mrcpv2-03.txt change logs The MRCPv2 draft has been updated to version -03. Please find below the change logs for the new draft. Thanks, Sarvi 1. Updated Referce numbers to be acurate. 2. In the Introduction ......................... The protocol requirements of SPEECHSC require that protocol is capable of reaching a media server and setting up communication channels to it, for communicating control message and media streams to/from the server. The Session Initiation Protocol (SIP) protocol described in [4] meets these requirements and is used to setup and tear down media and control pipes to the server. In addition, the SIP re-INVITE can be used to change the characteristics of these media and control pipes mid-session. The MRCPv2 protocol hence is designed to leverage and build upon a session management protocols such as Session Initiation Protocol (SIP) and Session Description Protocol (SDP). SDP is used to describe the parameters of the media pipe associated with that session. It is mandatory to support SIP as the session level protocol to ensure interoperability. Other protocols can be used at the session level by prior agreement. .................. 3. Added Security Considerations. 4. Updated with various types and corrections mentioned via email. 5. MRCP-Version description added the following text, per Klaus's request. Request, response and event messages include the version of MRCP in use, and follow [H3.1] (with HTTP replaced by MRCP, and HTTP/1.1 replaced by MRCP/2.0) regarding version ordering, compliance requirements, and upgrading of version numbers. To be compliant with this specification, applications sending MRCP messages MUST include a mrcp-version of "MRCP/2.0". 6. Moved GET-PARAMS and SET-PARAMS to generic methods common for all resources. 7. Added support for Cokkie headers intot he generic headers section. Text provided by Dave Burke 8. Moved Vendor specific headers to be a generic header so that it applies to all resources. 9. Updated many places that use ALPHA to VCHAR as was suggested on the list. 10. Added Completion-Reason header to all resources to allow the server to return Test error messages describing the reason for failure. 11. Added support for timestamp to Speech-Marker header 12. Changed name i. hotword-max-seconds ---> hotword-max-duration ii. hotword-min-seconds ---> hotword-min-duration 13. Change many headers from integer value o float 0.0 - 1.0 14. Recognition-Timeout description clarified. 15. DTMF-Term-Timeout clarified. 16. Recogintion-Mode support 17. DTMF and RFC2833 requirements clarified. 18. Added new methods GET-INTERMEDIATE-RESULTS and VER-CLEAR-BUFFER to the verififcation resource 19. Added Speech-Complete-Timeout, New-audio-Channel and Abort-Verification header fields to the Verification resource. 20. Ver-Buffer-Utterance header field default value is set to "false" 21. Change the Value of "Score" and Verification-Score to 0.0 -1.0 22. Calrified the VERIFY text with respect to existing voice-print adapt Vs retrain and wtih respect to VER-DELETE-VOICEPRINT methods. 23. VER-STOP method updated to support stop Vs abort. _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From exim@www1.ietf.org Sun May 23 22:35:47 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21072 for ; Sun, 23 May 2004 22:35:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BS5Hh-0000m6-4F for speechsc-archive@odin.ietf.org; Sun, 23 May 2004 22:33:49 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4O2Xnpv002973 for speechsc-archive@odin.ietf.org; Sun, 23 May 2004 22:33:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BS5Cz-0008Mj-MM for speechsc-web-archive@optimus.ietf.org; Sun, 23 May 2004 22:28:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20831 for ; Sun, 23 May 2004 22:28:53 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BS5Cw-0006VH-3u for speechsc-web-archive@ietf.org; Sun, 23 May 2004 22:28:54 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BS5Bw-0006DC-00 for speechsc-web-archive@ietf.org; Sun, 23 May 2004 22:27:54 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BS5Aq-0005ih-00 for speechsc-web-archive@ietf.org; Sun, 23 May 2004 22:26:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BS53N-0007Gd-IY; Sun, 23 May 2004 22:19:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BS4ta-0005TX-DW for speechsc@optimus.ietf.org; Sun, 23 May 2004 22:08:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20137 for ; Sun, 23 May 2004 22:08:50 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BS4tX-0001HD-9A for speechsc@ietf.org; Sun, 23 May 2004 22:08:51 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BS4sY-00011F-00 for speechsc@ietf.org; Sun, 23 May 2004 22:07:52 -0400 Received: from salvelinus.brooktrout.com ([204.176.205.6]) by ietf-mx with esmtp (Exim 4.12) id 1BS4rW-0000bT-00 for Speechsc@ietf.org; Sun, 23 May 2004 22:06:46 -0400 Received: from nhmail2.needham.brooktrout.com (nhmail2.eng.brooktrout.com [204.176.205.242]) by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id i4O1wE4W013032; Sun, 23 May 2004 21:58:15 -0400 (EDT) Received: by nhmail2.eng.brooktrout.com with Internet Mail Service (5.5.2653.19) id ; Sun, 23 May 2004 21:56:55 -0400 Message-ID: From: Eric Burger To: "'Dave Burke '" , "'Sarvi Shanmugham '" Cc: "'Roy, Radhika R, ALABS '" , "'Tim Melanchuk '" , "'Jeff Haynie '" , "'Garland Sharratt '" , "'Speechsc@ietf.org '" Subject: RE: [Speechsc] Media Server or Media Resource Date: Sun, 23 May 2004 21:56:54 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: speechsc-admin@ietf.org Errors-To: speechsc-admin@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Speech Services Control Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 I concur, as well. Going a bit further, I would offer that the only time the words "media" and "server" are found next to each other in the document is in the phrase "A media server can be a MRCP client to a MRCP server." -----Original Message----- From: Dave Burke To: Sarvi Shanmugham Cc: Roy, Radhika R, ALABS; Tim Melanchuk; Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Sent: 5/22/04 6:06 AM Subject: Re: [Speechsc] Media Server or Media Resource Agreed. - Dave ----- Original Message ----- From: Sarvi Shanmugham To: Dave Burke Cc: Roy, Radhika R, ALABS ; Tim Melanchuk ; Jeff Haynie ; Garland Sharratt ; Speechsc@ietf.org Sent: Friday, May 21, 2004 9:31 PM Subject: Re: [Speechsc] Media Server or Media Resource I can go with this proposal. I would suggest that we loose the v2 portion in the naming, as many of these servers are bound to support v1 for backward compatibility. Sarvi Dave Burke wrote: I like simplicity and I think the readers of the MRCPv2 specification will appreciate this also. We are seeking some sort of general term for discussing entities controlled by MRCPv2. At first glance "Media Server" appears to be an appropriate general term but unfortunately it carries with it definition out of scope of MRCPv2. What I like about Eric's original suggestion is that the phrase "Media Server" does not appear at all in the MRCPv2 specification. Building on this, why not just: "Media Resource": An entity to be controlled by MRCPv2 "MRCPv2 Server": Aggregate of one or more "Media Resource", exposed by MRCPv2. ("Server" for short) "MRCPv2 Client": The entity controlling one or more "Media Resource" via MRCPv2. ("Client" for short). This avoids confusion and leaves the media server vendors to decide if they want their product to be an MRCPv2 Client (probably the usual case), or an MRCPv2 Server (possible but perhaps not so common), or even an MRCPv2 Client and Server (ref my facetious remark earlier about a "Media B2BUA"). - Dave ----- Original Message ----- From: "Roy, Radhika R, ALABS" To: "Tim Melanchuk" ; "Sarvi Shanmugham" Cc: "Jeff Haynie" ; "Garland Sharratt" ; Sent: Friday, May 21, 2004 5:07 AM Subject: RE: [Speechsc] Media Server or Media Resource All: Seeing all definitions, it appears that we can safely conclude what Sarvi has proposed: 1. "MRCP server" or "MRCP Media server" - (a media server that contains only MRCP media resources) 2. "MRCP resource" or "MRCP media resource" - (self explanatory) 3. "MRCP resources on the Media Server" - (a media server that contains MRCP resources in addition to other media resources) 4. "Media Server" - (a media server that contains MRCP plus other media resources in the context of our works) Items 3 and 4 are the same in the context of our works. Radhika -----Original Message----- From: Tim Melanchuk [ mailto:timm@convedia.com ] Sent: Thursday, May 20, 2004 5:49 PM To: Sarvi Shanmugham Cc: Roy, Radhika R, ALABS; Jeff Haynie; Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource this approach sounds reasonable. "media server" is somewhat of generic term that is used for slightly different things in different contexts. for example, rtsp uses the term media server extensively and defines it as: Media server: The server providing playback services for one or more media streams. Different media streams within a presentation may originate from different media servers. A media server may reside on the same or a different host as the web server the presentation is invoked from. Sarvi Shanmugham wrote: Well from what I am hearing so far, a Media server is an entity that may support multiple media resources on it. But, the resources may not all be controlled by single protocol. So it would be a misnomer to call the whole box an "MRCP server" or "MRCP media server". But from the definitions flying around, it looks like people do agree that the box as a whole can be called/classified as a "Media server" without any protocol implications. So here is a suggestion, I propose we change all occurances of "MRCP server" or "MRCP Media server". I will instead use one of the following terms/phrases depending on the context. To refer to individual resources I will use "MRCP resource" or "MRCP media resource". To refer to the whole box that may have multiple media resources(MRCP or otherwise) I will use the phrase "Media Server" or "MRCP resources on the Media Server" as appropriate. Any thoughts. Sarvi Roy, Radhika R, ALABS wrote: Jeff: OK, let us go back to analyze these terms: Media Resources and Media Server. That is, MRCP is used to control (many, if not all) "media resources" of a media server. Radhika -----Original Message----- From: speechsc-admin@ietf.org [ mailto:speechsc-admin@ietf.org ]On Behalf Of Jeff Haynie Sent: Wednesday, May 19, 2004 9:48 PM To: Roy, Radhika R, ALABS Cc: Garland Sharratt; Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource OK, sorry, I'm confused. Do you support using the term "media server" or "media resource"? I can't tell from your response. Garland suggested in the original post that he favored the term "media resource" too. Jeff Roy, Radhika R, ALABS wrote: Jeff: Garland and I have been saying exactly what a media server is. A media server will be using many protocols, and MRCP is only of them. In this sense, MRCP is one of the protocols that is used for its media resources control. Who knows MRCP may NOT enough to control all the media resources of a Media Server. Let us see the big picture of a media server. Radhika -----Original Message----- From: speechsc-admin@ietf.org [ mailto:speechsc-admin@ietf.org ]On Behalf Of Jeff Haynie Sent: Wednesday, May 19, 2004 8:57 PM To: Garland Sharratt Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource Both you and Radhika seem to highlight exactly what MRCP is NOT and re-enforce Eric's original request, no? Of course, I'm not implying that media servers can't also support the MRCP protocol as a fact of implementation - that's something that's completely within reason. Jeff Garland Sharratt wrote: To Radhika's list I would also add recording and playback, as well as video announcements, video recording and playback, and video bridging. "Media server" is a generic term in NGN for a multi-purpose slave media processing engine controlled by a call agent or application server. All NGN architectures have a media server component, often by another name; in 3GPP, for instance, it's called an Media Resource Function Processor (MRFP). Media server control interfaces in NGN architectures are MGCP, H.248, and SIP. Garland -----Original Message----- *From:* speechsc-admin@ietf.org [ mailto:speechsc-admin@ietf.org ]*On Behalf Of *Roy, Radhika R, ALABS *Sent:* Wednesday, May 19, 2004 07:18 *To:* Reifenrath, Klaus; Sarvi Shanmugham; Eric Burger *Cc:* Speechsc@ietf.org *Subject:* RE: [Speechsc] Media Server or Media Resource Eric, Klaus, and Sarvi: Let me try to provide the definition of media servers: "Media servers (MSs) typically operate with application servers (ASs) to handle and terminate media streams, and provide services such as announcement, media bridging, media transcoding, interactive voice response (IVR) messages (with or without VocieXML), speech-to-text (STT) conversion, text-to-speech (TTS) conversion, and others." Cheers! Radhika R. Roy AT&T 732 420 1580 -----Original Message----- *From:* speechsc-admin@ietf.org [ mailto:speechsc-admin@ietf.org ]*On Behalf Of *Reifenrath, Klaus *Sent:* Wednesday, May 19, 2004 5:07 AM *To:* 'Sarvi Shanmugham'; Eric Burger *Cc:* Speechsc@ietf.org *Subject:* RE: [Speechsc] Media Server or Media Resource Hi Eric and Sarvi, after some internal discussions I prefer to stay with the term "media server"! In draft-burger-sipping-msuri-01.txt (expired IETF internet draft, that was referenced in the speechsc requirements document) the following definition of a media server can be found (section 3 on page 3): "Media servers are devices that perform media processing on real-time packet media." According to this definition the MRCP server is a media server (and not the platform that uses MRCP servers for media processing, which becomes a media proxy). In a network architecture that includes MRCP servers there might be other media servers. Could someone point me to the documents of the IETF, 3GPP, ... where I can find their definition of a media server. The term "media server" is used fairly often (especially in product brochures), but it seems to be difficult to find precise definitions. Thanks, Klaus -----Original Message----- *From:* Sarvi Shanmugham [ mailto:sarvi@cisco.com ] *Sent:* Mittwoch, 19. Mai 2004 01:49 *To:* Garland Sharratt *Cc:* Eric Burger; Speechsc@ietf.org *Subject:* Re: [Speechsc] Media Server or Media Resource This is fine by me. And I haven't heard any opposition so far. I will make the necessary edits. Sarvi Garland Sharratt wrote: Eric, I concur. Using the term "media server" for MRCPv2 muddies the waters, I think, and implies the two things are the same whereas they are not. Garland -----Original Message----- From: speechsc-admin@ietf.org [ mailto:speechsc-admin@ietf.org ]On Behalf Of Jeff Haynie Sent: Monday, May 17, 2004 08:10 To: Eric Burger Cc: Speechsc@ietf.org Subject: Re: [Speechsc] Media Server or Media Resource That's funny - I myself have struggled with the same term and would be much more in favor of "media resource". Jeff Eric Burger wrote: I have a form issue, not necessarily a substance issue. Throughout the MRCPv2 document, the "thing that is a server controlled by the MRCPv2 protocol" is called a "Media Server". A Media Server is a device that has a well-defined meaning, in the IETF, 3GPP (MRF), SIP Forum, IPCC, etc. That definition, IMHO, does not really match with "the thing that is a server controlled by the MRCPv2 protocol." In fact, the thing that embodies the accepted version of a Media Server is often a *client* to the MRCPv2 protocol. Would anyone be really put out if we did a 1,$:s/media server/media resource/g throughout the document? Rationale: The document describes the Media RESOURCE Control Protocol, not the Media SERVER Control Protocol. Thoughts? Comments? _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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