Re: [Speechsc] [RAI] RAI review of draft-ietf-speechsc-mrcpv2-19

Eric Burger <eburger@standardstrack.com> Sun, 12 July 2009 01:09 UTC

Return-Path: <eburger@standardstrack.com>
X-Original-To: speechsc@core3.amsl.com
Delivered-To: speechsc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C79023A6812; Sat, 11 Jul 2009 18:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHl+FvyKw-Qa; Sat, 11 Jul 2009 18:09:26 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.252.251]) by core3.amsl.com (Postfix) with ESMTP id 0B1D93A6811; Sat, 11 Jul 2009 18:09:26 -0700 (PDT)
Received: from c-75-68-112-157.hsd1.nh.comcast.net ([75.68.112.157] helo=[192.168.45.100]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1MPnZ4-0004Ve-3X; Sat, 11 Jul 2009 18:09:14 -0700
Message-Id: <1C686439-B153-4C31-86CC-1F9D9FD1914E@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Francois Audet <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1EE8AAC1@zrc2hxm0.corp.nortel.com>
Content-Type: multipart/signed; boundary="Apple-Mail-25-618329138"; micalg="sha1"; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sat, 11 Jul 2009 21:09:44 -0400
References: <033101c9ff3a$cbe33160$63a99420$%roni@huawei.com> <EE02487B-63DE-4CC6-81A9-7A4FAAD4A76D@standardstrack.com> <1ECE0EB50388174790F9694F77522CCF1EE8AAC1@zrc2hxm0.corp.nortel.com>
X-Mailer: Apple Mail (2.935.3)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: speechsc@ietf.org, rai@ietf.org
Subject: Re: [Speechsc] [RAI] RAI review of draft-ietf-speechsc-mrcpv2-19
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Speech Services Control Working Group <speechsc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speechsc>
List-Post: <mailto:speechsc@ietf.org>
List-Help: <mailto:speechsc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jul 2009 01:09:26 -0000

Correct: no one doing MRCPv2, not no one at all.

On Jul 9, 2009, at 4:48 PM, Francois Audet wrote:

> Eric,
>
> I think you need to clarify the context of the following statement you
> made: "The reality is that NO ONE has implemented any security to
> date."
>
> Certainly, SRTP is widely implemented and deployed in many  
> environements
> (e.g., Enteprise telephony for example).
>
> I am assuming that your comment was specific to MRCPv2?
>
>> -----Original Message-----
>> From: rai-bounces@ietf.org [mailto:rai-bounces@ietf.org] On
>> Behalf Of Eric Burger
>> Sent: Thursday, July 09, 2009 13:28
>> To: Roni Even
>> Cc: Daniel Burnett; speechsc@ietf.org; Saravanan Shanmugham;
>> rai@ietf.org
>> Subject: Re: [RAI] RAI review of draft-ietf-speechsc-mrcpv2-19
>>
>> The reality is that NO ONE has implemented any security to
>> date. The GENART reviewer raised the same issue, and so far
>> the work group has the same response: MRCPv2 (the speechsc
>> work group) is not planning on figuring out which of the
>> seven key exchange mechanisms to use in SIP.  We are counting
>> on the community publishing something, and people using it.
>> After all, we are the "using SIP for media resource control"
>> work group, not the "media resource control work group using
>> something like SIP for control."
>>
>> Does this work for you?
>>
>> On Jul 7, 2009, at 3:40 PM, Roni Even wrote:
>>
>>> [snip]
>>>
>>>
>>> 18.   In section 12.3 the suggestion is to use SRTP as the
>> mandatory
>>> interoperability mode. If the reason for mandating SRTP is for a
>>> common mode you should also decide on a key exchange mechanism. I
>>> suggest you look
>>> athttp://tools.ietf.org/html/draft-ietf-avt-srtp-not-mandatory-02
>>> for discussion on media security.
>>
>>