From msec-admin@securemulticast.org Mon Feb 2 04:48:13 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29567 for ; Mon, 2 Feb 2004 04:48:12 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 1473B53811; Mon, 2 Feb 2004 04:44:06 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 344355377E for ; Mon, 2 Feb 2004 04:42:31 -0500 (EST) Received: (qmail 91611 invoked by uid 3269); 2 Feb 2004 09:42:31 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 91608 invoked from network); 2 Feb 2004 09:42:31 -0000 Received: from thoth.sbs.de (192.35.17.2) by klesh.pair.com with SMTP; 2 Feb 2004 09:42:31 -0000 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id i129g0B04803; Mon, 2 Feb 2004 10:42:12 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id i129fsV10442; Mon, 2 Feb 2004 10:41:54 +0100 (MET) Received: from mail-k.mchp.siemens.de (mail-k.mchp.siemens.de [139.23.202.237]) by mars.cert.siemens.de (8.12.11/8.12.11/$SiemensCERT: mail/cert.mc.pre,v 1.56 2003/11/06 20:07:28 ust Exp $) with ESMTP id i129fsi1065861; Mon, 2 Feb 2004 10:41:54 +0100 (CET) Received: from mhpaba5c (mhpaba5c [139.23.204.46]) by mail-k.mchp.siemens.de with ESMTP id i129frXG029942; Mon, 2 Feb 2004 10:41:53 +0100 (MET) From: "Steffen Fries" Organization: Siemens AG To: "Elisabetta Carrara (KI/EAB)" MIME-Version: 1.0 Reply-To: steffen.fries@siemens.com Cc: msec@securemulticast.org Message-ID: <401E2972.9348.E945F1E@localhost> Priority: normal In-reply-to: <400BDC6D.21218.EE610BF@localhost> References: <4E85E49D1F0CBF4F96EA08E335750D7D062EFF2A@Esealnt877.al.sw.ericsson.se> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: [MSEC] MIKEY Question Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Mon, 02 Feb 2004 10:41:54 +0100 Content-Transfer-Encoding: 7BIT Hi Elisabetta, I've got some questions to MIKEY especdially regarding the length of used keys: - MIKEY allows to transmit either the TGK or the TEK. If the TEK is transmitted directly, the length is provided. If the TGK is transmitted, the length of the TGK is transmitted. How is the length of the TEK determined on both sides, when a PRF is used to derive the TEK from the transmitted TGK? There are different length of the TEK mention in MIKEY (128, 192, 256) - MIKEY allows either to transmit a salting key or to derive the salting key from the TGK. In the latter case, how is it signaled that the salt is derived and which length of the salt is to be used? Regards Steffen ----------------------------------------------------------- Steffen Fries, Siemens AG, CT IC 3 Otto-Hahn-Ring 6, D-81730 Munich, Germany Phone: (+49) 89 / 636-53403, Fax : (+49) 89 / 636-48000 Email: Steffen.Fries@siemens.com ----------------------------------------------------------- _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Mon Feb 2 14:15:12 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03448 for ; Mon, 2 Feb 2004 14:15:11 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 468F1539A3; Mon, 2 Feb 2004 14:14:41 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 1ACD45356C for ; Mon, 2 Feb 2004 13:36:33 -0500 (EST) Received: (qmail 64638 invoked by uid 3269); 2 Feb 2004 18:36:33 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 64633 invoked from network); 2 Feb 2004 18:36:32 -0000 Received: from eagle.ericsson.se (193.180.251.53) by klesh.pair.com with SMTP; 2 Feb 2004 18:36:32 -0000 Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120]) by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i12IaVAh011204 for ; Mon, 2 Feb 2004 19:36:31 +0100 Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Mon, 2 Feb 2004 19:36:39 +0100 Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id <1AZ5AH4Q>; Mon, 2 Feb 2004 19:36:54 +0100 Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D062F0244@Esealnt877.al.sw.ericsson.se> From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Cc: "'msec@securemulticast.org'" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 02 Feb 2004 18:36:39.0107 (UTC) FILETIME=[7EBE6930:01C3E9BB] Subject: [MSEC] RE: MIKEY Question Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Mon, 2 Feb 2004 19:30:49 +0100 Hi Steffen, the signalling you are looking for should be in the security protocol policy definition. The draft corrently specifies the policy for SRTP, and indeed explicit signalling is missing. We have assumed that the default values should be used, as specified in the SRTP draft. However, as you noted, we were not clear; explicit signalling (the two lenght parameters) should be added within the SRTP policy parameter section. Many thanks for pointing it out, cheers /Elisabetta > -----Original Message----- > From: Steffen Fries [mailto:steffen.fries@siemens.com] > Sent: den 2 februari 2004 10:42 > To: Elisabetta Carrara (KI/EAB) > Cc: msec@securemulticast.org > Subject: MIKEY Question > > > Hi Elisabetta, > > I've got some questions to MIKEY especdially regarding the > length of used keys: > > - MIKEY allows to transmit either the TGK or the TEK. If the > TEK is transmitted directly, the length is provided. If the > TGK is transmitted, the length of the TGK is transmitted. How > is the length of the TEK determined on both sides, when a PRF > is used to derive the TEK from the transmitted TGK? There are > different length of the TEK mention in MIKEY (128, 192, 256) > > - MIKEY allows either to transmit a salting key or to derive > the salting key from the TGK. In the latter case, how is it > signaled that the salt is derived and which length of the > salt is to be used? > > Regards > Steffen > ----------------------------------------------------------- > Steffen Fries, Siemens AG, CT IC 3 > Otto-Hahn-Ring 6, D-81730 Munich, Germany > Phone: (+49) 89 / 636-53403, > Fax : (+49) 89 / 636-48000 > Email: Steffen.Fries@siemens.com > ----------------------------------------------------------- > > This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Tue Feb 3 02:48:59 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26251 for ; Tue, 3 Feb 2004 02:48:58 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 844FD53A2D; Tue, 3 Feb 2004 02:48:28 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id C6BBF539D7 for ; Tue, 3 Feb 2004 02:47:32 -0500 (EST) Received: (qmail 33122 invoked by uid 3269); 3 Feb 2004 07:47:32 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 33119 invoked from network); 3 Feb 2004 07:47:32 -0000 Received: from thoth.sbs.de (192.35.17.2) by klesh.pair.com with SMTP; 3 Feb 2004 07:47:32 -0000 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id i137lUB21854; Tue, 3 Feb 2004 08:47:30 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i137lS313665; Tue, 3 Feb 2004 08:47:28 +0100 (MET) Received: from mail-k.mchp.siemens.de (mail-k.mchp.siemens.de [139.23.202.237]) by mars.cert.siemens.de (8.12.11/8.12.11/$SiemensCERT: mail/cert.mc.pre,v 1.56 2003/11/06 20:07:28 ust Exp $) with ESMTP id i137lRqA073637; Tue, 3 Feb 2004 08:47:28 +0100 (CET) Received: from mhpaba5c (mhpaba5c [139.23.204.46]) by mail-k.mchp.siemens.de with ESMTP id i137lRXG012305; Tue, 3 Feb 2004 08:47:27 +0100 (MET) From: "Steffen Fries" Organization: Siemens AG To: "Elisabetta Carrara (KI/EAB)" MIME-Version: 1.0 Reply-To: steffen.fries@siemens.com Cc: msec@securemulticast.org Message-ID: <401F601D.23127.1351E827@localhost> Priority: normal In-reply-to: <4E85E49D1F0CBF4F96EA08E335750D7D062F0244@Esealnt877.al.sw.ericsson.se> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: [MSEC] RE: MIKEY Question Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Tue, 03 Feb 2004 08:47:25 +0100 Content-Transfer-Encoding: 7BIT Hi Elisabetta, so, solving the problem is just adding the two parameters to the SRTP policy section, thats good. Will you compile an updated version of the MIKEY draft? Regards Steffen From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Copies to: "'msec@securemulticast.org'" Subject: RE: MIKEY Question Date sent: Mon, 2 Feb 2004 19:30:49 +0100 > Hi Steffen, > the signalling you are looking for should be in the security > protocol policy definition. The draft corrently specifies the > policy for SRTP, and indeed explicit signalling is missing. > > We have assumed that the default values should be used, as > specified in the SRTP draft. However, as you noted, we were > not clear; explicit signalling (the two lenght parameters) > should be added within the SRTP policy parameter section. > > Many thanks for pointing it out, > cheers > /Elisabetta > > > > > > -----Original Message----- > > From: Steffen Fries [mailto:steffen.fries@siemens.com] > > Sent: den 2 februari 2004 10:42 > > To: Elisabetta Carrara (KI/EAB) > > Cc: msec@securemulticast.org > > Subject: MIKEY Question > > > > > > Hi Elisabetta, > > > > I've got some questions to MIKEY especdially regarding the > > length of used keys: > > > > - MIKEY allows to transmit either the TGK or the TEK. If the > > TEK is transmitted directly, the length is provided. If the > > TGK is transmitted, the length of the TGK is transmitted. How is > > the length of the TEK determined on both sides, when a PRF is used > > to derive the TEK from the transmitted TGK? There are different > > length of the TEK mention in MIKEY (128, 192, 256) > > > > - MIKEY allows either to transmit a salting key or to derive > > the salting key from the TGK. In the latter case, how is it > > signaled that the salt is derived and which length of the > > salt is to be used? > > > > Regards > > Steffen > > ----------------------------------------------------------- > > Steffen Fries, Siemens AG, CT IC 3 > > Otto-Hahn-Ring 6, D-81730 Munich, Germany > > Phone: (+49) 89 / 636-53403, > > Fax : (+49) 89 / 636-48000 > > Email: Steffen.Fries@siemens.com > > ----------------------------------------------------------- > > > > > > This communication is confidential and intended solely for the > addressee(s). Any unauthorized review, use, disclosure or distribution > is prohibited. If you believe this message has been sent to you in > error, please notify the sender by replying to this transmission and > delete the message without disclosing it. Thank you. > > E-mail including attachments is susceptible to data corruption, > interruption, unauthorized amendment, tampering and viruses, and we > only send and receive e-mails on the basis that we are not liable for > any such corruption, interception, amendment, tampering or viruses or > any consequences thereof. > > _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Tue Feb 3 04:48:33 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29930 for ; Tue, 3 Feb 2004 04:48:32 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 99B1853A44; Tue, 3 Feb 2004 04:48:03 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 0D680536D7 for ; Tue, 3 Feb 2004 04:46:16 -0500 (EST) Received: (qmail 68278 invoked by uid 3269); 3 Feb 2004 09:46:16 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 68275 invoked from network); 3 Feb 2004 09:46:15 -0000 Received: from albatross-ext.wise.edt.ericsson.se (193.180.251.49) by klesh.pair.com with SMTP; 3 Feb 2004 09:46:15 -0000 Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118]) by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i139kEqY025570 for ; Tue, 3 Feb 2004 10:46:14 +0100 (MET) Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Tue, 3 Feb 2004 10:46:11 +0100 Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id <1AZ5HRTL>; Tue, 3 Feb 2004 10:46:36 +0100 Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D062F0248@Esealnt877.al.sw.ericsson.se> From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Cc: msec@securemulticast.org MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 03 Feb 2004 09:46:11.0360 (UTC) FILETIME=[8E576200:01C3EA3A] Subject: [MSEC] RE: MIKEY Question Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Tue, 3 Feb 2004 10:40:23 +0100 Steffen, MIKEY is in the Editor queue. I hope that the addition can be fixed during the Authors' 48 Hours. Can Ran or Thomas confirm? cheers /Elisabetta > -----Original Message----- > From: Steffen Fries [mailto:steffen.fries@siemens.com] > Sent: den 3 februari 2004 08:47 > To: Elisabetta Carrara (KI/EAB) > Cc: msec@securemulticast.org > Subject: RE: MIKEY Question > > > Hi Elisabetta, > > so, solving the problem is just adding the two parameters to > the SRTP policy section, thats good. Will you compile an > updated version of the MIKEY draft? > > Regards > Steffen > > > From: "Elisabetta Carrara (KI/EAB)" > > To: "'steffen.fries@siemens.com'" > > Copies to: "'msec@securemulticast.org'" > > Subject: RE: MIKEY Question > Date sent: Mon, 2 Feb 2004 19:30:49 +0100 > > > Hi Steffen, > > the signalling you are looking for should be in the security > > protocol policy definition. The draft corrently specifies the > > policy for SRTP, and indeed explicit signalling is missing. > > > > We have assumed that the default values should be used, as > > specified in the SRTP draft. However, as you noted, we were > > not clear; explicit signalling (the two lenght parameters) > > should be added within the SRTP policy parameter section. > > > > Many thanks for pointing it out, > > cheers > > /Elisabetta > > > > > > > > > > > -----Original Message----- > > > From: Steffen Fries [mailto:steffen.fries@siemens.com] > > > Sent: den 2 februari 2004 10:42 > > > To: Elisabetta Carrara (KI/EAB) > > > Cc: msec@securemulticast.org > > > Subject: MIKEY Question > > > > > > > > > Hi Elisabetta, > > > > > > I've got some questions to MIKEY especdially regarding the > > > length of used keys: > > > > > > - MIKEY allows to transmit either the TGK or the TEK. If the > > > TEK is transmitted directly, the length is provided. If the > > > TGK is transmitted, the length of the TGK is transmitted. How is > > > the length of the TEK determined on both sides, when a > PRF is used > > > to derive the TEK from the transmitted TGK? There are different > > > length of the TEK mention in MIKEY (128, 192, 256) > > > > > > - MIKEY allows either to transmit a salting key or to derive > > > the salting key from the TGK. In the latter case, how is it > > > signaled that the salt is derived and which length of the > > > salt is to be used? > > > > > > Regards > > > Steffen > > > ----------------------------------------------------------- > > > Steffen Fries, Siemens AG, CT IC 3 > > > Otto-Hahn-Ring 6, D-81730 Munich, Germany > > > Phone: (+49) 89 / 636-53403, > > > Fax : (+49) 89 / 636-48000 > > > Email: Steffen.Fries@siemens.com > > > ----------------------------------------------------------- > > > > > > This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Wed Feb 4 00:41:14 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23544 for ; Wed, 4 Feb 2004 00:41:13 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 9026353AC3; Wed, 4 Feb 2004 00:40:25 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 1AE0A535C4 for ; Wed, 4 Feb 2004 00:39:20 -0500 (EST) Received: (qmail 69467 invoked by uid 3269); 4 Feb 2004 05:39:20 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 69464 invoked from network); 4 Feb 2004 05:39:20 -0000 Received: from igw2.watson.ibm.com (129.34.20.6) by klesh.pair.com with SMTP; 4 Feb 2004 05:39:20 -0000 Received: from sp1n293en1.watson.ibm.com (sp1n293en1.watson.ibm.com [129.34.20.41]) by igw2.watson.ibm.com (8.11.7-20030924/8.11.4) with ESMTP id i145dId24398; Wed, 4 Feb 2004 00:39:19 -0500 Received: from ornavella.watson.ibm.com (localhost [127.0.0.1]) by sp1n293en1.watson.ibm.com (8.11.7-20030924/8.11.7/8.11.7-01-14-2004) with ESMTP id i145dI704088; Wed, 4 Feb 2004 00:39:18 -0500 Received: from localhost (canetti@localhost) by ornavella.watson.ibm.com (AIX5.1/8.11.6p2/8.11.0/03-06-2002) with ESMTP id i145dHJ26692; Wed, 4 Feb 2004 00:39:17 -0500 From: canetti To: msec@securemulticast.org Cc: housley@vigilsec.com, smb@research.att.com Subject: Re: [MSEC] Msec meeting in Seoul In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Wed, 4 Feb 2004 00:39:16 -0500 (EST) To date, Thomas and I learnded of only a single person that is planning to go to Seoul. In light of this, it seems that there is no constituency for a meeting. If you would still like MSEC to meet in Seoul please let Thomas and me know within the next two days. Ran and Thomas PS. I hope that those who are working on writing/revising I-Ds will not be discouraged by the cancellation, and will still try to get the documents in before the Seoul cutoff dates. On Fri, 23 Jan 2004, canetti wrote: > > Folks, > > We would like to get a sense of how many people are planning on attending an > MSEC meeting in Seoul. There will be several business items, including (but > not limited to): > > -An updated GKMARCH document (after last call, on its way to IESG review) > -ESP with digital signatures draft > -Updated informational TESLA document > -TESLA on ESP document > -TESLA on SRTP document > -Potentially MSEC requirements document > > > So if you plan on attending then please drop one of us a note (especially if > you're one of the active contributors to msec). > > Thanks, > Ran and Thomas > - > > > > > _______________________________________________ > msec mailing list > msec@securemulticast.org > http://www.pairlist.net/mailman/listinfo/msec > _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Wed Feb 4 05:03:44 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28374 for ; Wed, 4 Feb 2004 05:03:43 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 768405399B; Wed, 4 Feb 2004 05:03:00 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 14CB053678 for ; Wed, 4 Feb 2004 05:01:39 -0500 (EST) Received: (qmail 44909 invoked by uid 3269); 4 Feb 2004 10:01:39 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 44905 invoked from network); 4 Feb 2004 10:01:39 -0000 Received: from thoth.sbs.de (192.35.17.2) by klesh.pair.com with SMTP; 4 Feb 2004 10:01:39 -0000 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id i14A1ao02318; Wed, 4 Feb 2004 11:01:37 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i14A1W322978; Wed, 4 Feb 2004 11:01:32 +0100 (MET) Received: from mail-k.mchp.siemens.de (mail-k.mchp.siemens.de [139.23.202.237]) by mars.cert.siemens.de (8.12.11/8.12.11/$SiemensCERT: mail/cert.mc.pre,v 1.56 2003/11/06 20:07:28 ust Exp $) with ESMTP id i14A1UCt092567; Wed, 4 Feb 2004 11:01:31 +0100 (CET) Received: from mhpaba5c (mhpaba5c [139.23.204.46]) by mail-k.mchp.siemens.de with ESMTP id i14A1UXG026329; Wed, 4 Feb 2004 11:01:30 +0100 (MET) From: "Steffen Fries" Organization: Siemens AG To: "Elisabetta Carrara (KI/EAB)" MIME-Version: 1.0 Reply-To: steffen.fries@siemens.com Cc: msec@securemulticast.org Message-ID: <4020D10A.18635.8F0FFD@localhost> Priority: normal In-reply-to: <4E85E49D1F0CBF4F96EA08E335750D7D062F0248@Esealnt877.al.sw.ericsson.se> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: [MSEC] Another MIKEY Question Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Wed, 04 Feb 2004 11:01:30 +0100 Content-Transfer-Encoding: 7BIT Hi Elisabetta, I've got another question, just for clarification. In section 4.4 of the MIKEY draft the following is stated: "However, the SSRC is not sufficient. For the retrieval of the Data SA from MIKEY, it is RECOMMENDED that the MIKEY implementation support a lookup using destination network address and port together with SSRC." What would be a scenario, where the network address and the port is not suffcient and the SSRC is actually needed? Regards Steffen ----------------------------------------------------------- Steffen Fries, Siemens AG, CT IC 3 Otto-Hahn-Ring 6, D-81730 Munich, Germany Phone: (+49) 89 / 636-53403, Fax : (+49) 89 / 636-48000 Email: Steffen.Fries@siemens.com ----------------------------------------------------------- _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Thu Feb 5 07:50:51 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13763 for ; Thu, 5 Feb 2004 07:50:51 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 100E953B17; Thu, 5 Feb 2004 07:44:08 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 6DCA65386A for ; Thu, 5 Feb 2004 07:42:41 -0500 (EST) Received: (qmail 88678 invoked by uid 3269); 5 Feb 2004 12:42:41 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 88675 invoked from network); 5 Feb 2004 12:42:41 -0000 Received: from eagle.ericsson.se (193.180.251.53) by klesh.pair.com with SMTP; 5 Feb 2004 12:42:41 -0000 Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120]) by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i15CgeAh024063 for ; Thu, 5 Feb 2004 13:42:40 +0100 Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Thu, 5 Feb 2004 13:42:40 +0100 Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id <1AZ6CF8V>; Thu, 5 Feb 2004 13:43:13 +0100 Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D062F0295@Esealnt877.al.sw.ericsson.se> From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Cc: msec@securemulticast.org MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 05 Feb 2004 12:42:40.0068 (UTC) FILETIME=[8A878040:01C3EBE5] Subject: [MSEC] RE: Another MIKEY Question Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Thu, 5 Feb 2004 13:36:50 +0100 Hi Steffen, the RTP spec says that participants in an RTP session may share the same destination transport address, but they would use the (unique) SSRC to demultiplex. In particular, the SSRC is needed in sessions with more than one participant/data source/listener. Each listener and data source uses its own SSRC, and the SA may be different for each. Cheers /Elisabetta > -----Original Message----- > From: Steffen Fries [mailto:steffen.fries@siemens.com] > Sent: den 4 februari 2004 11:02 > To: Elisabetta Carrara (KI/EAB) > Cc: msec@securemulticast.org > Subject: Another MIKEY Question > > > Hi Elisabetta, > > I've got another question, just for clarification. In section > 4.4 of the MIKEY draft the following is stated: > "However, the SSRC is not sufficient. For the retrieval of the > Data SA from MIKEY, it is RECOMMENDED that the MIKEY > implementation support a lookup using destination network > address and port together with SSRC." > > What would be a scenario, where the network address and the > port is not suffcient and the SSRC is actually needed? > > Regards > Steffen > > ----------------------------------------------------------- > Steffen Fries, Siemens AG, CT IC 3 > Otto-Hahn-Ring 6, D-81730 Munich, Germany > Phone: (+49) 89 / 636-53403, > Fax : (+49) 89 / 636-48000 > Email: Steffen.Fries@siemens.com > ----------------------------------------------------------- > > This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Thu Feb 5 08:04:38 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14229 for ; Thu, 5 Feb 2004 08:04:38 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 0811E536A9; Thu, 5 Feb 2004 08:04:07 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id D4153536A9 for ; Thu, 5 Feb 2004 08:02:54 -0500 (EST) Received: (qmail 92750 invoked by uid 3269); 5 Feb 2004 13:02:54 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 92747 invoked from network); 5 Feb 2004 13:02:54 -0000 Received: from thoth.sbs.de (192.35.17.2) by klesh.pair.com with SMTP; 5 Feb 2004 13:02:54 -0000 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id i15D2ro06644; Thu, 5 Feb 2004 14:02:53 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i15D2m316451; Thu, 5 Feb 2004 14:02:48 +0100 (MET) Received: from mail-k.mchp.siemens.de (mail-k.mchp.siemens.de [139.23.202.237]) by mars.cert.siemens.de (8.12.11/8.12.11/$SiemensCERT: mail/cert.mc.pre,v 1.56 2003/11/06 20:07:28 ust Exp $) with ESMTP id i15D2mmm002000; Thu, 5 Feb 2004 14:02:48 +0100 (CET) Received: from mhpaba5c (mhpaba5c [139.23.204.46]) by mail-k.mchp.siemens.de with ESMTP id i15D2mXG015192; Thu, 5 Feb 2004 14:02:48 +0100 (MET) From: "Steffen Fries" Organization: Siemens AG To: "Elisabetta Carrara (KI/EAB)" MIME-Version: 1.0 Reply-To: steffen.fries@siemens.com Cc: msec@securemulticast.org Message-ID: <40224D03.26990.65B5302@localhost> Priority: normal In-reply-to: <4E85E49D1F0CBF4F96EA08E335750D7D062F0295@Esealnt877.al.sw.ericsson.se> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: [MSEC] RE: Another MIKEY Question Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Thu, 05 Feb 2004 14:02:43 +0100 Content-Transfer-Encoding: 7BIT Hi Elisabetta, hm, okay, I did not though on a multicast case. Just for my curiousity, how do you get the SSRC in your implementation for the RTP connection? Using the common RTP stacks, there is no option to get the SSRC before actually opening an RTP channel nor is there an interface to set the SSRC from outside. Did you adapt the RTP stack to do this? Regards Steffen From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Copies to: msec@securemulticast.org Subject: RE: Another MIKEY Question Date sent: Thu, 5 Feb 2004 13:36:50 +0100 > > Hi Steffen, > the RTP spec says that participants in an RTP session > may share the same destination transport address, but > they would use the (unique) SSRC to demultiplex. > In particular, the SSRC is needed in sessions with more > than one participant/data source/listener. Each listener > and data source uses its own SSRC, and the SA may be > different for each. > > Cheers > /Elisabetta > > > > > > -----Original Message----- > > From: Steffen Fries [mailto:steffen.fries@siemens.com] > > Sent: den 4 februari 2004 11:02 > > To: Elisabetta Carrara (KI/EAB) > > Cc: msec@securemulticast.org > > Subject: Another MIKEY Question > > > > > > Hi Elisabetta, > > > > I've got another question, just for clarification. In section > > 4.4 of the MIKEY draft the following is stated: > > "However, the SSRC is not sufficient. For the retrieval of the Data > > SA from MIKEY, it is RECOMMENDED that the MIKEY implementation > > support a lookup using destination network address and port > > together with SSRC." > > > > What would be a scenario, where the network address and the > > port is not suffcient and the SSRC is actually needed? > > > > Regards > > Steffen > > _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Thu Feb 5 14:18:50 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29850 for ; Thu, 5 Feb 2004 14:18:49 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id A18815393C; Thu, 5 Feb 2004 14:18:19 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 01E0F5363E for ; Thu, 5 Feb 2004 14:16:44 -0500 (EST) Received: (qmail 4983 invoked by uid 3269); 5 Feb 2004 19:16:44 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 4980 invoked from network); 5 Feb 2004 19:16:43 -0000 Received: from zrc2s0jx.nortelnetworks.com (47.103.122.112) by klesh.pair.com with SMTP; 5 Feb 2004 19:16:43 -0000 Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i15JGcS29811; Thu, 5 Feb 2004 13:16:39 -0600 (CST) Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com [132.245.205.52]) by zsc3c028.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 1F3VZ7AV; Thu, 5 Feb 2004 11:16:39 -0800 Received: from nortelnetworks.com (LDONDETI-2 [47.17.22.109]) by zbl6c002.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id D826H9DF; Thu, 5 Feb 2004 14:16:37 -0500 Message-ID: <40229695.6010005@nortelnetworks.com> X-Sybari-Space: 00000000 00000000 00000000 00000000 From: "Dondeti, Lakshminath" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: canetti Cc: msec@securemulticast.org, Thomas Hardjono Subject: Re: [MSEC] Msec meeting in Seoul References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Thu, 05 Feb 2004 14:16:37 -0500 Content-Transfer-Encoding: 7bit canetti wrote: >To date, Thomas and I learnded of only a single person that is planning to >go to Seoul. In light of this, it seems that there is no constituency for >a meeting. If you would still like MSEC to meet in Seoul please let Thomas >and me know within the next two days. > >Ran and Thomas > >PS. I hope that those who are working on writing/revising I-Ds will not >be discouraged by the cancellation, and will still try to get the >documents in before the Seoul cutoff dates. > > Unfortunately, for me MSEC not meeting in Seoul does make the I-Ds somewhat of a lower priority :-( ! I think that will be the case with other MSEC contributors as well. Lakshminath >On Fri, 23 Jan 2004, canetti wrote: > > > >>Folks, >> >>We would like to get a sense of how many people are planning on attending an >>MSEC meeting in Seoul. There will be several business items, including (but >>not limited to): >> >>-An updated GKMARCH document (after last call, on its way to IESG review) >>-ESP with digital signatures draft >>-Updated informational TESLA document >>-TESLA on ESP document >>-TESLA on SRTP document >>-Potentially MSEC requirements document >> >> >>So if you plan on attending then please drop one of us a note (especially if >>you're one of the active contributors to msec). >> >>Thanks, >>Ran and Thomas >>- >> >> >> >> >>_______________________________________________ >>msec mailing list >>msec@securemulticast.org >>http://www.pairlist.net/mailman/listinfo/msec >> >> >> > > >_______________________________________________ >msec mailing list >msec@securemulticast.org >http://www.pairlist.net/mailman/listinfo/msec > > > _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Thu Feb 5 14:25:29 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00306 for ; Thu, 5 Feb 2004 14:25:28 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 85C4F53B68; Thu, 5 Feb 2004 14:24:20 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 9B17553758 for ; Thu, 5 Feb 2004 14:23:41 -0500 (EST) Received: (qmail 6386 invoked by uid 3269); 5 Feb 2004 19:23:41 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 6381 invoked from network); 5 Feb 2004 19:23:41 -0000 Received: from m4.sparta.com (157.185.61.2) by klesh.pair.com with SMTP; 5 Feb 2004 19:23:41 -0000 Received: from ambrosius.sparta.com (beta5.sparta.com [157.185.63.21]) by m4.sparta.com (8.12.8/8.12.8) with ESMTP id i15JNZwo014147; Thu, 5 Feb 2004 13:23:35 -0600 Received: from columbia.sparta.com (lilo.columbia.SPARTA.COM [157.185.80.32]) by ambrosius.sparta.com (8.12.8/8.12.8) with ESMTP id i15JNY3L031996; Thu, 5 Feb 2004 13:23:35 -0600 Received: from sparta.com (dhcp-12.columbia.sparta.com [157.185.80.12]) by columbia.sparta.com (8.12.10+Sun/8.12.10) with ESMTP id i15JNXw0027234; Thu, 5 Feb 2004 14:23:33 -0500 (EST) Subject: Re: [MSEC] Msec meeting in Seoul Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v553) Cc: canetti , msec@securemulticast.org, Thomas Hardjono To: canetti From: Hugh Harney In-Reply-To: <40229695.6010005@nortelnetworks.com> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.553) Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Thu, 5 Feb 2004 14:23:33 -0500 Content-Transfer-Encoding: 7bit Ran, We plan on updating the GSAKMP draft as if we were going to Seoul. So stay tuned for v5. Hugh On Thursday, February 5, 2004, at 02:16 PM, Dondeti, Lakshminath wrote: > canetti wrote: > >> To date, Thomas and I learnded of only a single person that is >> planning to >> go to Seoul. In light of this, it seems that there is no >> constituency for >> a meeting. If you would still like MSEC to meet in Seoul please let >> Thomas >> and me know within the next two days. >> >> Ran and Thomas >> >> PS. I hope that those who are working on writing/revising I-Ds will >> not >> be discouraged by the cancellation, and will still try to get the >> documents in before the Seoul cutoff dates. > _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Fri Feb 6 10:17:32 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00253 for ; Fri, 6 Feb 2004 10:17:31 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id B429653E37; Fri, 6 Feb 2004 10:14:32 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id DD7E053E2B for ; Fri, 6 Feb 2004 10:13:55 -0500 (EST) Received: (qmail 77029 invoked by uid 3269); 6 Feb 2004 15:13:56 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 77026 invoked from network); 6 Feb 2004 15:13:55 -0000 Received: from penguin-ext.wise.edt.ericsson.se (193.180.251.47) by klesh.pair.com with SMTP; 6 Feb 2004 15:13:55 -0000 Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120]) by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i16FDsYG009998 for ; Fri, 6 Feb 2004 16:13:54 +0100 (MET) Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Fri, 6 Feb 2004 16:13:54 +0100 Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id <1LJFC2J4>; Fri, 6 Feb 2004 16:14:31 +0100 Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D062F02A8@Esealnt877.al.sw.ericsson.se> From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Cc: msec@securemulticast.org MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 06 Feb 2004 15:13:54.0272 (UTC) FILETIME=[D596E600:01C3ECC3] Subject: [MSEC] RE: Another MIKEY Question Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Fri, 6 Feb 2004 16:08:00 +0100 Hi, as SRTP specifies, that information needs to be conveyed to RTP. How this is done is an implementation issue, which of course may require changes to existing APIs (depending on which RTP implementation you use). cheers /E > -----Original Message----- > From: Steffen Fries [mailto:steffen.fries@siemens.com] > Sent: den 5 februari 2004 14:03 > To: Elisabetta Carrara (KI/EAB) > Cc: msec@securemulticast.org > Subject: RE: Another MIKEY Question > > > Hi Elisabetta, > > hm, okay, I did not though on a multicast case. > > Just for my curiousity, how do you get the SSRC in your > implementation for the RTP connection? Using the common RTP > stacks, there is no option to get the SSRC before actually > opening an RTP channel nor is there an interface to set the > SSRC from outside. Did you adapt the RTP stack to do this? > > Regards > Steffen > > From: "Elisabetta Carrara (KI/EAB)" > > To: "'steffen.fries@siemens.com'" > > Copies to: msec@securemulticast.org > Subject: RE: Another MIKEY Question > Date sent: Thu, 5 Feb 2004 13:36:50 +0100 > > > > > Hi Steffen, > > the RTP spec says that participants in an RTP session > > may share the same destination transport address, but > > they would use the (unique) SSRC to demultiplex. > > In particular, the SSRC is needed in sessions with more > > than one participant/data source/listener. Each listener > > and data source uses its own SSRC, and the SA may be > > different for each. > > > > Cheers > > /Elisabetta > > > > > > > > > > > -----Original Message----- > > > From: Steffen Fries [mailto:steffen.fries@siemens.com] > > > Sent: den 4 februari 2004 11:02 > > > To: Elisabetta Carrara (KI/EAB) > > > Cc: msec@securemulticast.org > > > Subject: Another MIKEY Question > > > > > > > > > Hi Elisabetta, > > > > > > I've got another question, just for clarification. In section > > > 4.4 of the MIKEY draft the following is stated: > > > "However, the SSRC is not sufficient. For the retrieval > of the Data > > > SA from MIKEY, it is RECOMMENDED that the MIKEY implementation > > > support a lookup using destination network address and port > > > together with SSRC." > > > > > > What would be a scenario, where the network address and the > > > port is not suffcient and the SSRC is actually needed? > > > > > > Regards > > > Steffen > > > > This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Fri Feb 6 19:48:11 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01851 for ; Fri, 6 Feb 2004 19:48:11 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 5892D535F9; Fri, 6 Feb 2004 19:46:06 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 722D8535EE for ; Fri, 6 Feb 2004 19:42:22 -0500 (EST) Received: (qmail 24247 invoked by uid 3269); 7 Feb 2004 00:42:22 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 24244 invoked from network); 7 Feb 2004 00:42:22 -0000 Received: from sj-iport-4.cisco.com (171.68.10.86) by klesh.pair.com with SMTP; 7 Feb 2004 00:42:22 -0000 Received: from mbaugher-w2k07.cisco.com (sjc-vpn3-424.cisco.com [10.21.65.168]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i170gIpq025071; Fri, 6 Feb 2004 16:42:18 -0800 (PST) Message-Id: <6.0.0.22.2.20040206164008.038c5ad8@mira-sjc5-6.cisco.com> X-Sender: mbaugher@mira-sjc5-6.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 To: internet-drafts@ietf.org From: Mark Baugher Cc: canetti@watson.ibm.com, thardjono@verisign.com, msec@securemulticast.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [MSEC] draft-ietf-msec-srtp-tesla-00.txt Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Fri, 06 Feb 2004 16:42:15 -0800 Dear Internet Drafts Editor: Please post the version 0 draft of the following draft http://www.rdrop.com/users/mbaugher/I-D/draft-ietf-msec-srtp-tesla-00.txt This is an official msec working group I-D. Please notify msec@securemulticast.org. thanks, Mark _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Mon Feb 9 04:46:33 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09026 for ; Mon, 9 Feb 2004 04:46:32 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 9E89A53AD2; Mon, 9 Feb 2004 04:46:03 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id B28235393F for ; Mon, 9 Feb 2004 04:44:19 -0500 (EST) Received: (qmail 69670 invoked by uid 3269); 9 Feb 2004 09:44:19 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 69667 invoked from network); 9 Feb 2004 09:44:19 -0000 Received: from david.siemens.de (192.35.17.14) by klesh.pair.com with SMTP; 9 Feb 2004 09:44:19 -0000 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.11.7/8.11.7) with ESMTP id i199iIb05213; Mon, 9 Feb 2004 10:44:18 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i199iB311998; Mon, 9 Feb 2004 10:44:11 +0100 (MET) Received: from mail-k.mchp.siemens.de (mail-k.mchp.siemens.de [139.23.202.237]) by mars.cert.siemens.de (8.12.11/8.12.11/$SiemensCERT: mail/cert.mc.pre,v 1.56 2003/11/06 20:07:28 ust Exp $) with ESMTP id i199iB3u073058; Mon, 9 Feb 2004 10:44:11 +0100 (CET) Received: from mhpaba5c (mhpaba5c [139.23.204.46]) by mail-k.mchp.siemens.de with ESMTP id i199iAXG015760; Mon, 9 Feb 2004 10:44:10 +0100 (MET) From: "Steffen Fries" Organization: Siemens AG To: "Elisabetta Carrara (KI/EAB)" MIME-Version: 1.0 Subject: Re: [MSEC] RE: Another MIKEY Question Reply-To: steffen.fries@siemens.com Cc: msec@securemulticast.org Message-ID: <4027647C.23636.138A3683@localhost> Priority: normal In-reply-to: <40224D03.26990.65B5302@localhost> References: <4E85E49D1F0CBF4F96EA08E335750D7D062F0295@Esealnt877.al.sw.ericsson.se> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Mon, 09 Feb 2004 10:44:12 +0100 Content-Transfer-Encoding: 7BIT Hi Elisabetta, hope I don't bother you ... here is yet another question. In the 08 version of MIKEY, it is recommended in section 4.2.5 to support also RSA OAEP. How is this signaled in the Envelope Key payload (section 6.3)? Is there a new payload header to be defined. Tight to this would be an error message signaling an error, that a dedicated key encryption method is not supported. Regards Steffen _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Mon Feb 9 08:50:54 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18656 for ; Mon, 9 Feb 2004 08:50:53 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 5508653D0B; Mon, 9 Feb 2004 08:46:22 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id CFE5B53CB1 for ; Mon, 9 Feb 2004 08:44:56 -0500 (EST) Received: (qmail 22708 invoked by uid 3269); 9 Feb 2004 13:44:56 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 22705 invoked from network); 9 Feb 2004 13:44:56 -0000 Received: from penguin-ext.wise.edt.ericsson.se (193.180.251.47) by klesh.pair.com with SMTP; 9 Feb 2004 13:44:56 -0000 Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120]) by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i19DitYG008799 for ; Mon, 9 Feb 2004 14:44:55 +0100 (MET) Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Mon, 9 Feb 2004 14:44:55 +0100 Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id <1LJFXRN8>; Mon, 9 Feb 2004 14:45:43 +0100 Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D062F02B8@Esealnt877.al.sw.ericsson.se> From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Cc: msec@securemulticast.org Subject: RE: [MSEC] RE: Another MIKEY Question MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 09 Feb 2004 13:44:55.0201 (UTC) FILETIME=[E67E9110:01C3EF12] Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Mon, 9 Feb 2004 14:39:02 +0100 Hi Steffen, the information is signaled in the certificate. Check for ex. appendix A of ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-1/pkcs-1v2-1.pdf cheers /E > -----Original Message----- > From: Steffen Fries [mailto:steffen.fries@siemens.com] > Sent: den 9 februari 2004 10:44 > To: Elisabetta Carrara (KI/EAB) > Cc: msec@securemulticast.org > Subject: Re: [MSEC] RE: Another MIKEY Question > > > Hi Elisabetta, > > hope I don't bother you ... here is yet another question. > > In the 08 version of MIKEY, it is recommended in section 4.2.5 > to support also RSA OAEP. How is this signaled in the Envelope > Key payload (section 6.3)? Is there a new payload header to be > defined. Tight to this would be an error message signaling an > error, that a dedicated key encryption method is not supported. > > Regards > Steffen > This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Mon Feb 9 14:08:17 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04783 for ; Mon, 9 Feb 2004 14:08:17 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 2C3F553605; Mon, 9 Feb 2004 14:06:15 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id A462B537AE for ; Mon, 9 Feb 2004 14:04:02 -0500 (EST) Received: (qmail 2404 invoked by uid 3269); 9 Feb 2004 19:04:02 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 2401 invoked from network); 9 Feb 2004 19:04:02 -0000 Received: from pigeon.verisign.com (65.205.251.71) by klesh.pair.com with SMTP; 9 Feb 2004 19:04:02 -0000 Received: from mou1wnexc01.vcorp.ad.vrsn.com (verisign.com [65.205.251.53]) by pigeon.verisign.com (8.12.10/) with ESMTP id i19J3sn8027592; Mon, 9 Feb 2004 11:03:55 -0800 (PST) Received: by mou1wnexc01.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2653.19) id <1TZHL26D>; Mon, 9 Feb 2004 11:03:54 -0800 Message-ID: From: "Hardjono, Thomas" To: "'Dinara Suleymanova'" , Mark Baugher Cc: canetti@watson.ibm.com, "Hardjono, Thomas" , msec@securemulticast.org Subject: RE: [MSEC] draft-ietf-msec-srtp-tesla-00.txt MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_002C_01C3EEFC.A91AC8E0" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Mon, 9 Feb 2004 11:03:48 -0800 This is a multi-part message in MIME format. ------=_NextPart_000_002C_01C3EEFC.A91AC8E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dinara, Yes, this has been approved. Apologies for the delay on my part. thomas ------ MSEC co-chair -----Original Message----- From: Dinara Suleymanova [mailto:dinaras@ietf.org] Sent: Monday, February 09, 2004 10:57 AM To: Mark Baugher Cc: canetti@watson.ibm.com; thardjono@verisign.com; msec@securemulticast.org Subject: Re: [MSEC] draft-ietf-msec-srtp-tesla-00.txt Was it approved by the wg chairs ? At 04:42 PM 2/6/04 -0800, Mark Baugher wrote: >Dear Internet Drafts Editor: >Please post the version 0 draft of the following draft >http://www.rdrop.com/users/mbaugher/I-D/draft-ietf-msec-srtp-tesla-00.t >xt > >This is an official msec working group I-D. Please notify >msec@securemulticast.org. > >thanks, Mark > > >_______________________________________________ >msec mailing list >msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec ------=_NextPart_000_002C_01C3EEFC.A91AC8E0 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOkzCCAwMw ggJsAhEAuS9gzIifoXpGCbhbcGyKrzANBgkqhkiG9w0BAQUFADCBwTELMAkGA1UEBhMCVVMxFzAV BgNVBAoTDlZlcmlTaWduLCBJbmMuMTwwOgYDVQQLEzNDbGFzcyAyIFB1YmxpYyBQcmltYXJ5IENl cnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzIxOjA4BgNVBAsTMShjKSAxOTk4IFZlcmlTaWduLCBJ bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l dHdvcmswHhcNOTgwNTE4MDAwMDAwWhcNMjgwODAxMjM1OTU5WjCBwTELMAkGA1UEBhMCVVMxFzAV BgNVBAoTDlZlcmlTaWduLCBJbmMuMTwwOgYDVQQLEzNDbGFzcyAyIFB1YmxpYyBQcmltYXJ5IENl cnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzIxOjA4BgNVBAsTMShjKSAxOTk4IFZlcmlTaWduLCBJ bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l dHdvcmswgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKeIASF0LOcaA/CY4Zc8DyEI8Zzbl+ma /MIEBhO+X1LIzB4sElYsuAFpLMyZH62wlq55BPITOcF7mLoILOjChBMsqmnpCfTHqQKkQsIjT0rY 8A6i+zFsyeZvmScH9eb0THiebetGhvq5hslU8rLEr9RGHFrJFTD/DWz1LQ5tzn93AgMBAAEwDQYJ KoZIhvcNAQEFBQADgYEAci75f9HxcfvEnvbFXlGKQJi4aPibHIPY4p29/+2h5mbqLwn0ytfqpSuV 9iRghk1ELoOlxC2g0654aW9y2myuCPBjkjfmu8QwF613zEk1qs/Yj9G+txiWR3NqVCI0ZC22FptZ W7RRWTqzCxT0Et9noPStMmResUZyJ4wSe8VEtK4wggOmMIIDD6ADAgECAhB1jYKLFwIGqnrNp5q9 I7AoMA0GCSqGSIb3DQEBBQUAMIHBMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIElu Yy4xPDA6BgNVBAsTM0NsYXNzIDIgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3Jp dHkgLSBHMjE6MDgGA1UECxMxKGMpIDE5OTggVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0aG9yaXpl ZCB1c2Ugb25seTEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazAeFw05OTAyMjUwMDAw MDBaFw0wOTAyMjQyMzU5NTlaMIGtMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1YmplY3QgdG8gdGVybXMg YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTEmMCQGA1UEAxMdVmVyaVNp Z24gQ2xhc3MgMiBQZXJzb25uZWwgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKcEbA+i crdKBi741yksNJ2CvEiRSses+en8uVl4sVXAU1ixz28WO8FJ1cv0bszhzMu1xy5OiKo06bbQW3w+ FVc04Ri8/931r2dZIArlPeqIikDSmokTKam21dunfuHnNyST/ZR0TXrkMm1M6FwWl6/dktlmihRm 5OpaA6g9X/sLAgMBAAGjgbAwga0wEQYJYIZIAYb4QgEBBAQDAgEGMA8GA1UdEwQIMAYBAf8CAQEw CwYDVR0PBAQDAgEGMEQGA1UdIAQ9MDswOQYLYIZIAYb4RQEHFwIwKjAoBggrBgEFBQcCARYcaHR0 cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl cmlzaWduLmNvbS9wY2EyLWcyLmNybDANBgkqhkiG9w0BAQUFAAOBgQBSXraV2298pn4F9lSFO9ka ikVZX3zCZe75QN5UbseQEoAkPECjY+yFH/UeG4nKPY7jSy7fnBvujudUuVaT/tvRxET4y5xAnZKs xc4E8RFG7Ii8mMiMIX03nMxrvTSlk4y9nDkd6qecGs31R20scxNjaiEuWn2HfbxMvvLHA8KMtjCC A8AwggMpoAMCAQICEErIAANjYdQVAxbxhjabt80wDQYJKoZIhvcNAQEFBQAwga0xFzAVBgNVBAoT DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQL E0BVc2UgaXMgc3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBh LWtyIChjKTk5MSYwJAYDVQQDEx1WZXJpU2lnbiBDbGFzcyAyIFBlcnNvbm5lbCBDQTAeFw05OTAy MjUwMDAwMDBaFw0wOTAyMjMyMzU5NTlaMIGsMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1YmplY3QgdG8g dGVybXMgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTElMCMGA1UEAxMc VmVyaVNpZ24gQ2xhc3MgMiBFbXBsb3llZSBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA wIrRh2Gi6jADVWsINvCX+hpUNSQf6H2dyMNz09hG9ZEt2TjtlNewJnMq3pdQTf8iHL1wAJgMWCqx pHKPpbn3LXxg47Xf6X1OISFh1fw7VMmkCZy7IvmiunBhT4ZGov0FZOwKP6ZYdle7FnNEfPClDZfA bKbxYwglsQQXlaCN/n8CAwEAAaOB3zCB3DApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0 ZUxhYmVsMS0xMTgwEQYJYIZIAYb4QgEBBAQDAgEGMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQD AgEGMEQGA1UdIAQ9MDswOQYLYIZIAYb4RQEHFwIwKjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cu dmVyaXNpZ24uY29tL3JwYTA4BgNVHR8EMTAvMC2gK6AphidodHRwOi8vY3JsLnZlcmlzaWduLmNv bS9WU0NsYXNzMkludC5jcmwwDQYJKoZIhvcNAQEFBQADgYEANhj9M2DWF9MEtdhUX1Ia5ZIIKPSi QNrDW4wahpfvrqIV/mzEzi/IAcozvvJ5WDOXl5JFcFpOKB3d98GIThuHVwI9kyXZfk5yNYlJF7O5 dy9tDvmkiCXBznZzZWkFk3fn/ZOWGDhNWGx6nejSm+jQ24n9ScJ1BAOXpdSWgdgjQfAwggQaMIID g6ADAgECAhAYSRf8kLabofH3SxzVEHCAMA0GCSqGSIb3DQEBBAUAMIGsMRcwFQYDVQQKEw5WZXJp U2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFJMEcGA1UECxNAVXNl IGlzIHN1YmplY3QgdG8gdGVybXMgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rciAo Yyk5OTElMCMGA1UEAxMcVmVyaVNpZ24gQ2xhc3MgMiBFbXBsb3llZSBDQTAeFw0wMzAzMjEwMDAw MDBaFw0wNDAzMjAyMzU5NTlaMGsxETAPBgNVBAoTCFZFUklTSUdOMQswCQYDVQQLEwJIUTETMBEG A1UEAxMKUmVjaXBpZW50czE0MDIGA1UEAxMrdGhhcmRqb25vIChIYXJkam9ubyBUaG9tYXMsIFZl cmlTaWduLCBJbmMuKTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAzgtbsbrMRafXb2WkJ+ny zp/kvtzxbas4Qro/3ooVMxeMylH8rM31BUFVMrlBEEe/DtwXhILPVh/4kpPDUUYpFVhbg3I6NVhK 4F7eb4+8Mc+K7A7gzU9bGehWlh5XmEIritXgWm5KKR8ReLvRb8YWPQLLikS0yfQF0KhuoLnid48C AwEAAaOCAXswggF3MAkGA1UdEwQCMAAwWQYDVR0fBFIwUDBOoEygSoZIaHR0cDovL29uc2l0ZWNy bC52ZXJpc2lnbi5jb20vVmVyaVNpZ25JbmNFeGNoYW5nZUVtcGxveWVlcy9MYXRlc3RDUkwuY3Js MAsGA1UdDwQEAwIFoDAhBgNVHREEGjAYgRZ0aGFyZGpvbm9AdmVyaXNpZ24uY29tMIGsBgNVHSAE gaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2ln bi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24n cyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglg hkgBhvhCAQEEBAMCB4AwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMA0GCSqGSIb3DQEB BAUAA4GBADkxDDPN7RzNkf5R7No0l92Xb+tt1+6X0TwkfL7iHQ95S19gSWctuoLHVKqdb0+4S+Lq KKfHATKLUSLJezw7kxkiFZLpWGI91ru1UlpH1v6l34VO9iyINrbFSuCt5N53n1leczRQVBSOvPxg 5FReDiG6axLGZJYPAv2d6cpi1HBCMYID3jCCA9oCAQEwgcEwgawxFzAVBgNVBAoTDlZlcmlTaWdu LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQLE0BVc2UgaXMg c3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyIChjKTk5 MSUwIwYDVQQDExxWZXJpU2lnbiBDbGFzcyAyIEVtcGxveWVlIENBAhAYSRf8kLabofH3SxzVEHCA MAkGBSsOAwIaBQCgggJyMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X DTA0MDIwOTE5MDU0M1owIwYJKoZIhvcNAQkEMRYEFMpLofm4hEZWNMX3O/ThDXqxyt3iMGcGCSqG SIb3DQEJDzFaMFgwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcG BSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3DQIFMIHSBgkrBgEEAYI3EAQx gcQwgcEwgawxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVz dCBOZXR3b3JrMUkwRwYDVQQLE0BVc2UgaXMgc3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3 dy52ZXJpc2lnbi5jb20vcnBhLWtyIChjKTk5MSUwIwYDVQQDExxWZXJpU2lnbiBDbGFzcyAyIEVt cGxveWVlIENBAhAYSRf8kLabofH3SxzVEHCAMIHUBgsqhkiG9w0BCRACCzGBxKCBwTCBrDEXMBUG A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxSTBH BgNVBAsTQFVzZSBpcyBzdWJqZWN0IHRvIHRlcm1zIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNv bS9ycGEta3IgKGMpOTkxJTAjBgNVBAMTHFZlcmlTaWduIENsYXNzIDIgRW1wbG95ZWUgQ0ECEBhJ F/yQtpuh8fdLHNUQcIAwDQYJKoZIhvcNAQEBBQAEgYC91e5r0fRYg7UNdk52OFWXNQ8OVJfKTJAy b/IJIDennV7SQMN4gYhMDRnmNaH51bPn7biiTCEGBp2JW1YKgfG1nfidFHosZcnqFGP+o8IQSn50 V9vyXHU/8BLUSdVn/X+cmPCzUDZtrXR1nJnECtYS/TuqH+K3M9kXw7oS/JtI6AAAAAAAAA== ------=_NextPart_000_002C_01C3EEFC.A91AC8E0-- _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Wed Feb 11 16:13:46 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24765 for ; Wed, 11 Feb 2004 16:13:44 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id D078753D6A; Wed, 11 Feb 2004 16:08:34 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 390F55382E for ; Wed, 11 Feb 2004 15:51:43 -0500 (EST) Received: (qmail 64186 invoked by uid 3269); 11 Feb 2004 20:51:42 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 64148 invoked from network); 11 Feb 2004 20:51:42 -0000 Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176) by klesh.pair.com with SMTP; 11 Feb 2004 20:51:42 -0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22603; Wed, 11 Feb 2004 15:51:35 -0500 (EST) Message-Id: <200402112051.PAA22603@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: msec@securemulticast.org From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: [MSEC] I-D ACTION:draft-ietf-msec-srtp-tesla-00.txt Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Wed, 11 Feb 2004 15:51:34 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast Security Working Group of the IETF. Title : The Use of TESLA in SRTP Author(s) : M. Baugher Filename : draft-ietf-msec-srtp-tesla-00.txt Pages : 17 Date : 2004-2-11 This memo describes the use of the Timed Efficient Stream loss- tolerant Authentication (TESLA) transform within the Secure Real- time Transport Protocol (SRTP), to provide data origin authentication for multicast and broadcast data streams. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-msec-srtp-tesla-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-msec-srtp-tesla-00.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-msec-srtp-tesla-00.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-2-11160535.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-msec-srtp-tesla-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-msec-srtp-tesla-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-2-11160535.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Thu Feb 12 05:44:43 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18446 for ; Thu, 12 Feb 2004 05:44:43 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 5E71353659; Thu, 12 Feb 2004 05:44:04 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 4E2BA535D7 for ; Thu, 12 Feb 2004 05:42:53 -0500 (EST) Received: (qmail 84562 invoked by uid 3269); 12 Feb 2004 10:42:53 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 84558 invoked from network); 12 Feb 2004 10:42:52 -0000 Received: from goliath.siemens.de (192.35.17.28) by klesh.pair.com with SMTP; 12 Feb 2004 10:42:52 -0000 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.11.7/8.11.7) with ESMTP id i1CAgos21677; Thu, 12 Feb 2004 11:42:51 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i1CAgnm25923; Thu, 12 Feb 2004 11:42:49 +0100 (MET) Received: from mail-k.mchp.siemens.de (mail-k.mchp.siemens.de [139.23.202.237]) by mars.cert.siemens.de (8.12.11/8.12.11/$SiemensCERT: mail/cert.mc.pre,v 1.56 2003/11/06 20:07:28 ust Exp $) with ESMTP id i1CAgn9h068113; Thu, 12 Feb 2004 11:42:49 +0100 (CET) Received: from mhpaba5c (mhpaba5c [139.23.204.46]) by mail-k.mchp.siemens.de with ESMTP id i1CAgnXG016745; Thu, 12 Feb 2004 11:42:49 +0100 (MET) From: "Steffen Fries" Organization: Siemens AG To: "Elisabetta Carrara (KI/EAB)" MIME-Version: 1.0 Subject: RE: [MSEC] RE: Another MIKEY Question Reply-To: steffen.fries@siemens.com Cc: msec@securemulticast.org Message-ID: <402B66B5.10414.4413F40@localhost> Priority: normal In-reply-to: <4E85E49D1F0CBF4F96EA08E335750D7D062F02B8@Esealnt877.al.sw.ericsson.se> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Thu, 12 Feb 2004 11:42:45 +0100 Content-Transfer-Encoding: 7BIT Hi Elisabetta, thanks for the response. I'm not quit sure if this answers the question completely. Within PKCS#1 there is a list of possible supported encryption mechanisms. This is not a choice. This means, if a peer supports both methods, how does the remote peer know which to chose? In contrast, the certificate also describes several possible algorithms for signatures, which is also not a choice. But here, MIKEY signals the chosen signature algorithm as part of the Signature payload (SIGN) in the S type. Regards Steffen From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Copies to: msec@securemulticast.org Subject: RE: [MSEC] RE: Another MIKEY Question Date sent: Mon, 9 Feb 2004 14:39:02 +0100 > Hi Steffen, > the information is signaled in the certificate. > Check for ex. appendix A of > ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-1/pkcs-1v2-1.pdf > > cheers > /E > > > > > -----Original Message----- > > From: Steffen Fries [mailto:steffen.fries@siemens.com] > > Sent: den 9 februari 2004 10:44 > > To: Elisabetta Carrara (KI/EAB) > > Cc: msec@securemulticast.org > > Subject: Re: [MSEC] RE: Another MIKEY Question > > > > > > Hi Elisabetta, > > > > hope I don't bother you ... here is yet another question. > > > > In the 08 version of MIKEY, it is recommended in section 4.2.5 to > > support also RSA OAEP. How is this signaled in the Envelope Key > > payload (section 6.3)? Is there a new payload header to be defined. > > Tight to this would be an error message signaling an error, that a > > dedicated key encryption method is not supported. > > > > Regards > > Steffen > > > > This communication is confidential and intended solely for the > addressee(s). Any unauthorized review, use, disclosure or distribution > is prohibited. If you believe this message has been sent to you in > error, please notify the sender by replying to this transmission and > delete the message without disclosing it. Thank you. > > E-mail including attachments is susceptible to data corruption, > interruption, unauthorized amendment, tampering and viruses, and we > only send and receive e-mails on the basis that we are not liable for > any such corruption, interception, amendment, tampering or viruses or > any consequences thereof. > > > _______________________________________________ > msec mailing list > msec@securemulticast.org > http://www.pairlist.net/mailman/listinfo/msec > _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Thu Feb 12 11:05:30 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29962 for ; Thu, 12 Feb 2004 11:05:29 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 545BC53C4F; Thu, 12 Feb 2004 11:00:05 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 63E1E536D5 for ; Thu, 12 Feb 2004 10:58:24 -0500 (EST) Received: (qmail 62860 invoked by uid 3269); 12 Feb 2004 15:58:24 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 62857 invoked from network); 12 Feb 2004 15:58:24 -0000 Received: from eagle.ericsson.se (193.180.251.53) by klesh.pair.com with SMTP; 12 Feb 2004 15:58:24 -0000 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 i1CFwNAh016704 for ; Thu, 12 Feb 2004 16:58:23 +0100 Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Thu, 12 Feb 2004 16:58:23 +0100 Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id <1LJHAVB9>; Thu, 12 Feb 2004 16:59:22 +0100 Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D0A0095DD@Esealnt877.al.sw.ericsson.se> From: "Elisabetta Carrara (KI/EAB)" To: "'steffen.fries@siemens.com'" Cc: msec@securemulticast.org Subject: RE: [MSEC] RE: Another MIKEY Question MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 12 Feb 2004 15:58:23.0046 (UTC) FILETIME=[0AC7FE60:01C3F181] Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Thu, 12 Feb 2004 16:52:18 +0100 Hi Steffen, we haven't seen the need for that, mainly because ASFAWK it is discouraged to use the same key pair for both v1.5 and OAEP, therefore both options together should hopefully not appear. If they do, we would assume that the mandatory and default one is used (i.e. v1.5). Cheers /Elisabetta > -----Original Message----- > From: msec-admin@securemulticast.org > [mailto:msec-admin@securemulticast.org]On Behalf Of Steffen Fries > Sent: den 12 februari 2004 11:43 > To: Elisabetta Carrara (KI/EAB) > Cc: msec@securemulticast.org > Subject: RE: [MSEC] RE: Another MIKEY Question > > > Hi Elisabetta, > > thanks for the response. I'm not quit sure if this answers the > question completely. Within PKCS#1 there is a list of possible > supported encryption mechanisms. This is not a choice. This > means, if a peer supports both methods, how does the remote > peer know which to chose? > > In contrast, the certificate also describes several possible > algorithms for signatures, which is also not a choice. But > here, MIKEY signals the chosen signature algorithm as part of > the Signature payload (SIGN) in the S type. > > Regards > Steffen > > From: "Elisabetta Carrara (KI/EAB)" > > To: "'steffen.fries@siemens.com'" > > Copies to: msec@securemulticast.org > Subject: RE: [MSEC] RE: Another MIKEY Question > Date sent: Mon, 9 Feb 2004 14:39:02 +0100 > > > Hi Steffen, > > the information is signaled in the certificate. > > Check for ex. appendix A of > > ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-1/pkcs-1v2-1.pdf > > > > cheers > > /E > > > > > > > > > -----Original Message----- > > > From: Steffen Fries [mailto:steffen.fries@siemens.com] > > > Sent: den 9 februari 2004 10:44 > > > To: Elisabetta Carrara (KI/EAB) > > > Cc: msec@securemulticast.org > > > Subject: Re: [MSEC] RE: Another MIKEY Question > > > > > > > > > Hi Elisabetta, > > > > > > hope I don't bother you ... here is yet another question. > > > > > > In the 08 version of MIKEY, it is recommended in section 4.2.5 to > > > support also RSA OAEP. How is this signaled in the Envelope Key > > > payload (section 6.3)? Is there a new payload header to > be defined. > > > Tight to this would be an error message signaling an error, that a > > > dedicated key encryption method is not supported. > > > > > > Regards > > > Steffen > > > > > > > This communication is confidential and intended solely for the > > addressee(s). Any unauthorized review, use, disclosure or > distribution > > is prohibited. If you believe this message has been sent to you in > > error, please notify the sender by replying to this transmission and > > delete the message without disclosing it. Thank you. > > > > E-mail including attachments is susceptible to data corruption, > > interruption, unauthorized amendment, tampering and viruses, and we > > only send and receive e-mails on the basis that we are not > liable for > > any such corruption, interception, amendment, tampering or > viruses or > > any consequences thereof. > > > > > > _______________________________________________ > > msec mailing list > > msec@securemulticast.org > > http://www.pairlist.net/mailman/listinfo/msec > > > > > > _______________________________________________ > msec mailing list > msec@securemulticast.org > http://www.pairlist.net/mailman/listinfo/msec > This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Mon Feb 16 10:35:28 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25626 for ; Mon, 16 Feb 2004 10:35:28 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id DF5AB53608; Mon, 16 Feb 2004 10:34:55 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 922AE53708 for ; Mon, 16 Feb 2004 10:33:06 -0500 (EST) Received: (qmail 13155 invoked by uid 3269); 16 Feb 2004 15:33:06 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 13152 invoked from network); 16 Feb 2004 15:33:06 -0000 Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176) by klesh.pair.com with SMTP; 16 Feb 2004 15:33:06 -0000 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25109; Mon, 16 Feb 2004 10:33:02 -0500 (EST) Message-Id: <200402161533.KAA25109@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: msec@securemulticast.org From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: [MSEC] I-D ACTION:draft-ietf-msec-gsakmp-sec-05.txt Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Mon, 16 Feb 2004 10:33:01 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast Security Working Group of the IETF. Title : GSAKMP Author(s) : H. Harney Filename : draft-ietf-msec-gsakmp-sec-05.txt Pages : 113 Date : 2004-2-13 This document specifies the Group Secure Association Key Management Protocol (GSAKMP). The GSAKMP provides a security framework for creating and managing cryptographic groups on a network. It provides mechanisms to disseminate group policy and authenticate users, rules to perform access control decisions during group establishment and recovery, capabilities to recover from the compromise of group members, delegation of group security functions, and capabilities to destroy the group. It also generates group keys. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-msec-gsakmp-sec-05.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-msec-gsakmp-sec-05.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-msec-gsakmp-sec-05.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-2-16104551.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-msec-gsakmp-sec-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-msec-gsakmp-sec-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-2-16104551.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Tue Feb 17 03:30:53 2004 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16482 for ; Tue, 17 Feb 2004 03:30:52 -0500 (EST) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 6AB3153AAF; Tue, 17 Feb 2004 03:30:23 -0500 (EST) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 1659653A93 for ; Tue, 17 Feb 2004 03:29:47 -0500 (EST) Received: (qmail 60966 invoked by uid 3269); 17 Feb 2004 08:29:47 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 60963 invoked from network); 17 Feb 2004 08:29:46 -0000 Received: from cosmos.kaist.ac.kr (192.249.24.2) by klesh.pair.com with SMTP; 17 Feb 2004 08:29:46 -0000 Received: from cosmos.kaist.ac.kr (localhost.kaist.ac.kr [127.0.0.1]) by cosmos.kaist.ac.kr (8.12.2/8.9.3) with ESMTP id i1H8F9SD002948; Tue, 17 Feb 2004 17:15:09 +0900 (KST) Received: (from hkpark@localhost) by cosmos.kaist.ac.kr (8.12.2/8.12.2/Submit) id i1H8F8P5002946; Tue, 17 Feb 2004 17:15:08 +0900 (KST) (envelope-from hkpark) Message-ID: <20040217171508.D2599@cosmos.kaist.ac.kr> From: Heonkyu Park To: msec@securemulticast.org Cc: Heonkyu Park Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Subject: [MSEC] unscribe this maillist Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Tue, 17 Feb 2004 17:15:08 +0900 unscribe this maillist, thank you. _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec