Re: [AVT] SRTP and related
"Dan Wing" <dwing@cisco.com> Tue, 22 April 2008 01:53 UTC
Return-Path: <avt-bounces@ietf.org>
X-Original-To: avt-archive@optimus.ietf.org
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D45133A6CB2; Mon, 21 Apr 2008 18:53:38 -0700 (PDT)
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C551528C236 for <avt@core3.amsl.com>; Mon, 21 Apr 2008 18:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 hlABey4t9ICP for <avt@core3.amsl.com>; Mon, 21 Apr 2008 18:53:31 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 060D93A6FA7 for <avt@ietf.org>; Mon, 21 Apr 2008 18:53:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,691,1199692800"; d="scan'208";a="22835656"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-5.cisco.com with ESMTP; 21 Apr 2008 18:53:10 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m3M1rAWZ012095; Mon, 21 Apr 2008 18:53:10 -0700
Received: from dwingwxp01 ([10.32.240.194]) by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m3M1r99A012064; Tue, 22 Apr 2008 01:53:10 GMT
From: Dan Wing <dwing@cisco.com>
To: 'rossi kamal' <rossikamal@gmail.com>
References: <87277b870804202224o678d59c1yaf3c0261ead211b4@mail.gmail.com>
Date: Mon, 21 Apr 2008 18:53:09 -0700
Message-ID: <05b401c8a41b$9df96a60$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <87277b870804202224o678d59c1yaf3c0261ead211b4@mail.gmail.com>
Thread-Index: AcijqVH28I7n603FRPu740tG4xj+vwAcOE4g
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1826; t=1208829190; x=1209693190; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[AVT]=20SRTP=20and=20related |Sender:=20; bh=EIkBXs+EARy48c3GeaDOXK18nrpxmWRNn2funcSIU20=; b=opSuV3hF/JETfi9Oae0qsorkYeItUTLBhK7BsjoSGXamz451SyM7fmYhWQ 4iPkgusHwL066qnwR9lFIkY8CQrv/A4NJuiKxH+DYzNKywE7gf4/V18oyt7a DRpUEV78W0;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Cc: avt@ietf.org
Subject: Re: [AVT] SRTP and related
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
> -----Original Message----- > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On > Behalf Of rossi kamal > Sent: Sunday, April 20, 2008 10:24 PM > To: avt@ietf.org > Subject: [AVT] SRTP and related > > Hello > > I want to know the facts about the implementation of > SRTP-MIKEY,SRTP-ZRTP,SIP over TLS & their implementation in > detail.. In 2004, Karl Norrman (karl.norrman@ericsson.com) sent a pointer for a reference implementation of MIKEY, <http://www.ietf.org/mail-archive/web/avt/current/msg03659.html> but the URI he referenced is not working gor me right now. I'm not sure which MIKEY 'mode' it implemented (MIKEY-RSA, MIKEY-PSK, MIKEY-RSA-R, MIKEY-NULL, etc.; see <http://tools.ietf.org/html/draft-ietf-msec-mikey-applicability-09> and <http://tools.ietf.org/html/draft-ietf-sip-media-security-requirements-04#appe ndix-A>). I am aware of two implementations of the ZRTP key management system, one is available under license from <http://zfoneproject.com>, the other is by Werner Dittmann for MiniSIP <http://www.minisip.org>, <http://www.imc.org/ietf-rtpsec/mail-archive/msg00504.html>. The SRTP library that most folks use is <http://srtp.sourceforge.net/srtp.html>. For TLS and DTLS, many use OpenSSL <http://www.openssl.org>. > The java libraries that can be efficient to implement > those.. Java can call C, which may be your best bet. (by the way, of your original question the AVT working group only standardizes SRTP. MIKEY belongs to MSEC, SIP-over-TLS belongs to SIP, and ZRTP is an individual draft.) -d > Can anyone suggest the interroperability isseue > and the way to solve those > _______________________________________________ > Audio/Video Transport Working Group > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www.ietf.org/mailman/listinfo/avt
- [AVT] SRTP and related rossi kamal
- Re: [AVT] SRTP and related Dan Wing