IETF Logo Mail Archive

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

Eric Burger <eburger@standardstrack.com> Thu, 09 July 2009 20:27 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 B99EA28C274; Thu, 9 Jul 2009 13:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level:
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=0.079, 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 rs+bFDJ7LUBa; Thu, 9 Jul 2009 13:27:41 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.252.251]) by core3.amsl.com (Postfix) with ESMTP id A06E828C14F; Thu, 9 Jul 2009 13:27:41 -0700 (PDT)
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=[10.31.32.174]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1MP0Dm-0007xt-V2; Thu, 09 Jul 2009 13:27:59 -0700
Message-Id: <EE02487B-63DE-4CC6-81A9-7A4FAAD4A76D@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Roni Even <Even.roni@huawei.com>
In-Reply-To: <033101c9ff3a$cbe33160$63a99420$%roni@huawei.com>
Content-Type: multipart/signed; boundary="Apple-Mail-7-428628199"; micalg="sha1"; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 09 Jul 2009 16:28:04 -0400
References: <033101c9ff3a$cbe33160$63a99420$%roni@huawei.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, Saravanan Shanmugham <sarvi@cisco.com>, rai@ietf.org
Subject: Re: [Speechsc] 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: Thu, 09 Jul 2009 20:27:42 -0000

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.

v2.38.3 | Report a Bug | By Email | System Status