[Sip] RE: SRTP and MIKEY usage in SIP
"Elisabetta Carrara (EAB)" <Elisabetta.Carrara@era.ericsson.se> Mon, 20 January 2003 13:55 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20282 for <sip-archive@odin.ietf.org>; Mon, 20 Jan 2003 08:55:49 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0KECtZ21758 for sip-archive@odin.ietf.org; Mon, 20 Jan 2003 09:12:55 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0KECaJ21750; Mon, 20 Jan 2003 09:12:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HFrUJ09025 for <sip@optimus.ietf.org>; Fri, 17 Jan 2003 10:53:30 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26265 for <sip@ietf.org>; Fri, 17 Jan 2003 10:37:18 -0500 (EST)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69]) by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h0HFeeAv003549; Fri, 17 Jan 2003 16:40:40 +0100 (MET)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55) id <ZGNBWQW2>; Fri, 17 Jan 2003 16:40:40 +0100
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D02838A59@Esealnt877.al.sw.ericsson.se>
From: "Elisabetta Carrara (EAB)" <Elisabetta.Carrara@era.ericsson.se>
To: 'Steffen Fries' <steffen.fries@siemens.com>, sip@ietf.org
Cc: "Fredrik Lindholm (EAB)" <Fredrik.Lindholm@era.ericsson.se>
Date: Fri, 17 Jan 2003 16:41:03 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [Sip] RE: SRTP and MIKEY usage in SIP
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Hi Steffen the public-key based methods are most suitable for client-to-client communications. The pre-shared could be for ex a good choice for client(s)-to-server communications. So, for SIP the public-key based may be more suitable, generally speaking. Cheers, /E > -----Original Message----- > From: Steffen Fries [mailto:steffen.fries@siemens.com] > Sent: den 17 januari 2003 16:20 > To: sip@ietf.org > Cc: Elisabetta.Carrara@era.ericsson.se > Subject: SRTP and MIKEY usage in SIP > > > Hi, > > I'm not quite sure, which working group fits best for this > question, thus I'm starting with the SIP WG ;-) > > When SIP and SRTP are used in conjunction, an appropriate > key management is necessary for SRTP. Within the MSEC WG > MIKEY has been defined, which is thought to be used (also) > for SRTP. > > MIKEY and an related draft (draft-ietf-msec-MIKEY-DHHMAC- > 01.txt) offer 4 different key management methods based on: > - pre-shared secrets > - public key encryption > - Diffie Hellman protected with signatures > - Diffie Hellman protected with pre-shared secrets > > When MIKEY and SRTP are to be used in a SIP environment, > what would be a suitable choice out of the four options? > > I'm not sure if the pre-shared secret pased methods are > suitable, since this would assume, that all users who want to > communicate need to exchange a shared secret before. Well, this > could be done by puting a shared secret in the SIP message and > securing this by S/MIME, but then MIKEY would be protected by > symmetric methods, although asymmetric technology was used to > secure the shared secret transport, namely S/MIME. One could > also use the certificates and private keys to secure MIKEY > right from the beginning. > > There might be scenarios where the symmetric case is > appropriate, but I'm not sure if this is a rather general case. > > Is MIKEY generally considered for key management in SIP or will > this rather be done using draft-baugher-mmusic-sdpmediasec- > 00.txt secured by S/MIME? > > The usage of MIKEY and SRTP is especially interesting in > conjunction with other multimedia protocols like H.323. Voice > encryption and associated key management could be performed > across the different signaling protocols. > > Was there already a discussion related to this question, which > I may be missed? > > Regards > Steffen > _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] RE: SRTP and MIKEY usage in SIP Elisabetta Carrara (EAB)
- [Sip] SRTP and MIKEY usage in SIP Steffen Fries