From 888momo444@docomo.ne.jp Mon Jan 08 10:11:56 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H3wAG-0001Wz-0H for msec-archive@ietf.org; Mon, 08 Jan 2007 10:11:56 -0500 Received: from [220.194.46.198] (helo=kimu01.alpha.co.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H3wAD-0003ET-LD for msec-archive@ietf.org; Mon, 08 Jan 2007 10:11:55 -0500 Subject: =?ISO-2022-JP?B?grGC8YLJgr+CzYFBU05TgWmXoIFqiV6JY46WlrGLx4LFgreBQg==?= From: SNS（裏）運営事務局 To: msec-archive@ietf.org Message-ID: 20070109000901 Content-Type: text/plain; charset="SHIFT_JIS" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Tue, 9 Jan 2007 00:09:17 +0900 (JST) X-Spam-Score: 3.4 (+++) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 アカネ　さんがあなたを セックスフレンドネットワーキングサイト SNS（裏）へ招待しています。 メッセージ： 『いろんな人と気軽にセックスをしたいとおもって、SNSに入りました。 ちょっと気になったのでよかったら友達追加してもらえると嬉しいです☆ セックスの事色々知ってそうなので、色々おしえてほしいです! １月２０日あたりどうですかぁ？？』 下記のURLよりアカネさんの登録画面をご覧いただけます。 ↓こちらから招待者のsns（裏）トップページを見ることができます。 http://nuts.but.jp/89498849.htm ■□■　コミュニティ・エンターテイメント　　　　　　　　　　　　■□■ □■□　セックスフレンドネットワーキングサイト　SNS（裏）って何？　□■□ SNS（裏）は、メンバーより招待された方のみで構成されている、 日本初のセックスフレンドネットワーキングサイトです。 ■SNS（裏）ならこれまで以上にセフレ関係を活性化できる 信頼できる旧知の友人、お知り合いとのセックスライフの活性化を図るさまざまな ツールをご用意しています。 ■「友人の友人」と交流できる SNS（裏）を使えば友人同士のネットワークをたどって「友人の友人」との交流が 簡単にできます。そこにはあなたの友人から繋がる信頼できるネットワークが 形成されています。SNS（裏）はどこかで繋がっている人同士が集まるコミュニティ であり、これがソーシャルネットワーキングの特徴です。 ■SNS（裏）なら日記の読み書き、これまでご利用の日記の公開ができる みなさんは日記を公開することによって友人やSNS（裏）に登録している人々に多くの 情報を発信することが可能です。さらにこれまで使用されていた他の日記・ブログ を使うか、SNS（裏）の日記を使うかを選択することができます。 SNS（裏）へ参加↓ http://nuts.but.jp/89498849.htm それでは、参加を心よりお待ちしております。 ― SNS（裏） ――――――――――――――――――― コミュニティ・エンターテイメント SNS（裏） URL ：http://nuts.but.jp/ 運営会社 ： 株式会社SNS ――――――――――――――――――――――――― From msec-bounces@securemulticast.org Wed Jan 10 11:30:25 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4gLJ-0005Kt-RX for msec-archive@lists.ietf.org; Wed, 10 Jan 2007 11:30:25 -0500 Received: from six.pairlist.net ([209.68.2.254]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4gLG-000823-FW for msec-archive@lists.ietf.org; Wed, 10 Jan 2007 11:30:25 -0500 Received: from six.pairlist.net (localhost [127.0.0.1]) by six.pairlist.net (Postfix) with ESMTP id 862D42CED1; Wed, 10 Jan 2007 11:30:10 -0500 (EST) X-Original-To: msec@lists6.securemulticast.org Delivered-To: msec@six.pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by six.pairlist.net (Postfix) with SMTP id 800052CB0A for ; Wed, 10 Jan 2007 11:30:06 -0500 (EST) Received: (qmail 51300 invoked by uid 3269); 10 Jan 2007 16:30:06 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 51297 invoked from network); 10 Jan 2007 16:30:06 -0000 Received: from mailwash15.pair.com (66.39.2.15) by klesh.pair.com with SMTP; 10 Jan 2007 16:30:06 -0000 Received: from localhost (localhost [127.0.0.1]) by mailwash15.pair.com (Postfix) with SMTP id 84D68E9D7D for ; Wed, 10 Jan 2007 11:30:06 -0500 (EST) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mailwash15.pair.com (Postfix) with ESMTP id 7894DE9D7B for ; Wed, 10 Jan 2007 11:30:06 -0500 (EST) Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 10 Jan 2007 11:30:06 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.7.5a-GA) with ESMTP id MTL07908; Wed, 10 Jan 2007 11:30:01 -0500 (EST) Received: from 209-150-62-151.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com (HELO pascal.localnet) ([209.150.62.151]) by smtp01.lnh.mail.rcn.net with ESMTP; 10 Jan 2007 11:29:59 -0500 To: msec@securemulticast.org From: Ling Cheung Date: Wed, 10 Jan 2007 11:29:56 -0500 Message-ID: User-Agent: Gnus/5.090017 (Oort Gnus v0.17) XEmacs/21.4 (Reasonable Discussion, linux) MIME-Version: 1.0 X-Junkmail-Status: score=10/50, host=mr02.lnh.mail.rcn.net X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090204.45A512BC.0119,ss=1,fgs=0, ip=207.172.4.11, so=2006-05-09 23:27:51, dmn=5.2.125/2006-10-10 Subject: [MSEC] GSAKMP daemon X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "IETF Multicast Security \(MSEC\) WG list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: msec-bounces@securemulticast.org Errors-To: msec-bounces@securemulticast.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Hi all, We found the GSAKMP reference code on sourceforge and downloaded it. However, it doesn't compile. Configure fails when it tests gcc. We bypassed the two checks for gcc that were causing the problem. echo $ac_n "checking that we have auto_ptr""... $ac_c" 1>&6 ... echo $ac_n "checking that we have vector""... $ac_c" 1>&6 ... That allowed the configuration to finish, but, unsurprisingly, "make library" failed. Here is part of the error code. (We are running gcc 3.3.4 on Slackware 10.0.) ==================================================================== In file included from ../SecurityServices/SecurityServicesModule.h:32, from ../CRModule/CRProcessor.h:27, from ../CRModule/CRBuilder.cpp:20: ../SecurityServices/CertificateDataBase.h:21:20: hash_map: No such file or dir ectory In file included from ../SecurityServices/SecurityServicesModule.h:32, from ../CRModule/CRProcessor.h:27, from ../CRModule/CRBuilder.cpp:20: ../SecurityServices/CertificateDataBase.h: In member function `size_t dnhash::operator()(const DistinguishedName&) const': ../SecurityServices/CertificateDataBase.h:47: error: `hash' undeclared in namespace `std' ../SecurityServices/CertificateDataBase.h:47: error: parse error before `;' token ../SecurityServices/CertificateDataBase.h:48: error: `h' undeclared (first use this function) ==================================================================== Does anyone know how to get around this? Or is there a more recent version of the implementation? Thanks! -- Ling Cheung MIT CSAIL 32 Vassar St. (32-G628) Cambridge, MA 02139 U.S.A. _______________________________________________ msec mailing list msec@securemulticast.org http://six.pairlist.net/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 15 15:26:33 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6YPK-0001Ws-IG; Mon, 15 Jan 2007 15:26:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6YPJ-0001Wi-Pt for msec@ietf.org; Mon, 15 Jan 2007 15:26:17 -0500 Received: from lvs00-fl-n08.ftl.affinity.com ([216.219.253.156]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6YP0-0005Q7-7x for msec@ietf.org; Mon, 15 Jan 2007 15:26:17 -0500 Received: ("??"@ams008.ftl.affinity.com) by ams008.ftl.affinity.com id S609233AbXAOUZv for ; Mon, 15 Jan 2007 15:25:51 -0500 From: gmgietf@identaware.com To: msec@ietf.org Date: Mon, 15 Jan 2007 15:25:49 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: X-Spam-Score: 0.2 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Cc: Subject: [MSEC] Re: GSAKMP daemon X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hi Ling, Unfortunately, that GSAKMP source code is based on a fairly old Linux platform. For my GSAKMP implementation, I used that source code only as a design guidepost, so I can not advise you on how to build it. The best I could recommend is that you retrieve archival versions of the Linux that it is known to work with, then load up a PC running that build platform. After you get a proof of concept working, you could then port it to Slackware. Alternatively, you could try to directly contact the authors of that GSAKMP implementation. AFAIK, Hugh Harney and Uri Meth no longer monitor the MSEC list. Their contact info is in RFC4535. hth, George ===================================== Date: Wed, 10 Jan 2007 11:29:56 -0500 From: Ling Cheung To: msec@securemulticast.org Subject: [MSEC] GSAKMP daemon Hi all, We found the GSAKMP reference code on sourceforge and downloaded it. However, it doesn't compile. Configure fails when it tests gcc. We bypassed the two checks for gcc that were causing the problem. echo $ac_n "checking that we have auto_ptr""... $ac_c" 1>&6 ... echo $ac_n "checking that we have vector""... $ac_c" 1>&6 ... That allowed the configuration to finish, but, unsurprisingly, "make library" failed. Here is part of the error code. (We are running gcc 3.3.4 on Slackware 10.0.) ==================================================================== In file included from ../SecurityServices/SecurityServicesModule.h:32, from ../CRModule/CRProcessor.h:27, from ../CRModule/CRBuilder.cpp:20: ../SecurityServices/CertificateDataBase.h:21:20: hash_map: No such file or dir ectory In file included from ../SecurityServices/SecurityServicesModule.h:32, from ../CRModule/CRProcessor.h:27, from ../CRModule/CRBuilder.cpp:20: ../SecurityServices/CertificateDataBase.h: In member function `size_t dnhash::operator()(const DistinguishedName&) const': ../SecurityServices/CertificateDataBase.h:47: error: `hash' undeclared in namespace `std' ../SecurityServices/CertificateDataBase.h:47: error: parse error before `;' token ../SecurityServices/CertificateDataBase.h:48: error: `h' undeclared (first use this function) ==================================================================== Does anyone know how to get around this? Or is there a more recent version of the implementation? Thanks! -- Ling Cheung MIT CSAIL 32 Vassar St. (32-G628) Cambridge, MA 02139 U.S.A. _______________________________________________ msec mailing list msec@securemulticast.org http://six.pairlist.net/mailman/listinfo/msec _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 15 15:26:33 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6YPK-0001Ws-IG; Mon, 15 Jan 2007 15:26:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6YPJ-0001Wi-Pt for msec@ietf.org; Mon, 15 Jan 2007 15:26:17 -0500 Received: from lvs00-fl-n08.ftl.affinity.com ([216.219.253.156]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6YP0-0005Q7-7x for msec@ietf.org; Mon, 15 Jan 2007 15:26:17 -0500 Received: ("??"@ams008.ftl.affinity.com) by ams008.ftl.affinity.com id S609233AbXAOUZv for ; Mon, 15 Jan 2007 15:25:51 -0500 From: gmgietf@identaware.com To: msec@ietf.org Date: Mon, 15 Jan 2007 15:25:49 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: X-Spam-Score: 0.2 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Cc: Subject: [MSEC] Re: GSAKMP daemon X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hi Ling, Unfortunately, that GSAKMP source code is based on a fairly old Linux platform. For my GSAKMP implementation, I used that source code only as a design guidepost, so I can not advise you on how to build it. The best I could recommend is that you retrieve archival versions of the Linux that it is known to work with, then load up a PC running that build platform. After you get a proof of concept working, you could then port it to Slackware. Alternatively, you could try to directly contact the authors of that GSAKMP implementation. AFAIK, Hugh Harney and Uri Meth no longer monitor the MSEC list. Their contact info is in RFC4535. hth, George ===================================== Date: Wed, 10 Jan 2007 11:29:56 -0500 From: Ling Cheung To: msec@securemulticast.org Subject: [MSEC] GSAKMP daemon Hi all, We found the GSAKMP reference code on sourceforge and downloaded it. However, it doesn't compile. Configure fails when it tests gcc. We bypassed the two checks for gcc that were causing the problem. echo $ac_n "checking that we have auto_ptr""... $ac_c" 1>&6 ... echo $ac_n "checking that we have vector""... $ac_c" 1>&6 ... That allowed the configuration to finish, but, unsurprisingly, "make library" failed. Here is part of the error code. (We are running gcc 3.3.4 on Slackware 10.0.) ==================================================================== In file included from ../SecurityServices/SecurityServicesModule.h:32, from ../CRModule/CRProcessor.h:27, from ../CRModule/CRBuilder.cpp:20: ../SecurityServices/CertificateDataBase.h:21:20: hash_map: No such file or dir ectory In file included from ../SecurityServices/SecurityServicesModule.h:32, from ../CRModule/CRProcessor.h:27, from ../CRModule/CRBuilder.cpp:20: ../SecurityServices/CertificateDataBase.h: In member function `size_t dnhash::operator()(const DistinguishedName&) const': ../SecurityServices/CertificateDataBase.h:47: error: `hash' undeclared in namespace `std' ../SecurityServices/CertificateDataBase.h:47: error: parse error before `;' token ../SecurityServices/CertificateDataBase.h:48: error: `h' undeclared (first use this function) ==================================================================== Does anyone know how to get around this? Or is there a more recent version of the implementation? Thanks! -- Ling Cheung MIT CSAIL 32 Vassar St. (32-G628) Cambridge, MA 02139 U.S.A. _______________________________________________ msec mailing list msec@securemulticast.org http://six.pairlist.net/mailman/listinfo/msec _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@securemulticast.org Mon Jan 15 16:41:34 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6ZaA-0004Gf-6W for msec-archive@lists.ietf.org; Mon, 15 Jan 2007 16:41:34 -0500 Received: from six.pairlist.net ([209.68.2.254]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6Za5-0000WQ-LX for msec-archive@lists.ietf.org; Mon, 15 Jan 2007 16:41:34 -0500 Received: from six.pairlist.net (localhost [127.0.0.1]) by six.pairlist.net (Postfix) with ESMTP id 3EFFB2CDEF; Mon, 15 Jan 2007 16:41:23 -0500 (EST) X-Original-To: msec@lists6.securemulticast.org Delivered-To: msec@six.pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by six.pairlist.net (Postfix) with SMTP id 9A54F2BCBC for ; Mon, 15 Jan 2007 16:41:18 -0500 (EST) Received: (qmail 57388 invoked by uid 3269); 15 Jan 2007 21:41:18 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 57385 invoked from network); 15 Jan 2007 21:41:18 -0000 Received: from mailwash15.pair.com (66.39.2.15) by klesh.pair.com with SMTP; 15 Jan 2007 21:41:18 -0000 Received: from localhost (localhost [127.0.0.1]) by mailwash15.pair.com (Postfix) with SMTP id A6E25E9D9B for ; Mon, 15 Jan 2007 16:41:18 -0500 (EST) Received: from mx1.lan.ch (mx1.lan.ch [212.60.61.244]) by mailwash15.pair.com (Postfix) with ESMTP id 3C7FEE9D99 for ; Mon, 15 Jan 2007 16:41:18 -0500 (EST) Received: from localhost (av1.lan.ch [127.0.0.1]) by av1.lan.ch (Postfix) with SMTP id 1C3171B6C47 for ; Mon, 15 Jan 2007 22:41:15 +0100 (CET) autolearn=ham version=3.1.1 Received: from mail.hazienda.local (168-131-236-89-pool.cable.fcom.ch [89.236.131.168]) by mx1.lan.ch (Postfix) with ESMTP id 62FFF1B6C20 for ; Mon, 15 Jan 2007 22:41:11 +0100 (CET) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hazienda.local (Postfix) with ESMTP id 52683278DD for ; Mon, 15 Jan 2007 22:41:12 +0100 (CET) Received: from mail.hazienda.local ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16137-06 for ; Mon, 15 Jan 2007 22:40:55 +0100 (CET) Received: from [192.168.1.2] (212-41-104-149.adsl.solnet.ch [212.41.104.149]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.hazienda.local (Postfix) with ESMTP id 0BC5D276B9 for ; Mon, 15 Jan 2007 22:40:54 +0100 (CET) From: Reto Buerki To: msec@securemulticast.org In-Reply-To: References: Date: Mon, 15 Jan 2007 22:41:33 +0100 Message-Id: <1168897293.8350.12.camel@thunderbird> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Subject: Re: [MSEC] GSAKMP daemon X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "IETF Multicast Security \(MSEC\) WG list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: msec-bounces@securemulticast.org Errors-To: msec-bounces@securemulticast.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Hi Ling, I worked on this too for my diploma thesis last year. I was able to make the gsakmp implementation (version 0.8.1) compile successfully on an up-to-date linux system. Try applying the following patch on src/SecurityServices/CertificateDataBase.h: 21c21,22 < #include --- > #include > #include 23c24,25 < using namespace std; --- > //using namespace std; > using namespace __gnu_cxx; 47c49 < std::hash h; --- > hash h; Most of the problems compiling the source arise from different namespaces and locations of header files in newer compilers. I stopped working on this though because the daemon did not run very stable and GDOI was more promising for me. Hope it helped, - reto On Mon, 2007-01-15 at 15:25 -0500, gmgietf@identaware.com wrote: > Hi Ling, > > Unfortunately, that GSAKMP source code is based on a fairly old Linux > platform. For my GSAKMP implementation, I used that source code only as a > design guidepost, so I can not advise you on how to build it. The best I > could recommend is that you retrieve archival versions of the Linux that it > is known to work with, then load up a PC running that build platform. After > you get a proof of concept working, you could then port it to Slackware. > > Alternatively, you could try to directly contact the authors of that GSAKMP > implementation. AFAIK, Hugh Harney and Uri Meth no longer monitor the MSEC > list. Their contact info is in RFC4535. > > hth, > George > > ===================================== > Date: Wed, 10 Jan 2007 11:29:56 -0500 > From: Ling Cheung > To: msec@securemulticast.org > Subject: [MSEC] GSAKMP daemon > > Hi all, > > We found the GSAKMP reference code on sourceforge and downloaded it. > However, it doesn't compile. Configure fails when it tests gcc. > We bypassed the two checks for gcc that were causing the problem. > > echo $ac_n "checking that we have auto_ptr""... $ac_c" 1>&6 > ... > echo $ac_n "checking that we have vector""... $ac_c" 1>&6 > ... > > That allowed the configuration to finish, but, unsurprisingly, "make > library" failed. Here is part of the error code. (We are running gcc > 3.3.4 on Slackware 10.0.) > > ==================================================================== > In file included from ../SecurityServices/SecurityServicesModule.h:32, > from ../CRModule/CRProcessor.h:27, > from ../CRModule/CRBuilder.cpp:20: > ../SecurityServices/CertificateDataBase.h:21:20: hash_map: No such file or > dir > ectory > In file included from ../SecurityServices/SecurityServicesModule.h:32, > from ../CRModule/CRProcessor.h:27, > from ../CRModule/CRBuilder.cpp:20: > ../SecurityServices/CertificateDataBase.h: In member function `size_t > dnhash::operator()(const DistinguishedName&) const': > ../SecurityServices/CertificateDataBase.h:47: error: `hash' undeclared in > namespace `std' > ../SecurityServices/CertificateDataBase.h:47: error: parse error before `;' > token > ../SecurityServices/CertificateDataBase.h:48: error: `h' undeclared (first > use > > this function) > ==================================================================== > > Does anyone know how to get around this? Or is there a more recent > version of the implementation? > > Thanks! > _______________________________________________ msec mailing list msec@securemulticast.org http://six.pairlist.net/mailman/listinfo/msec From oracle@cluster2.smr.serenamail.com Tue Jan 23 16:36:52 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9TK0-0006kf-3i for msec-archive@ietf.org; Tue, 23 Jan 2007 16:36:52 -0500 Received: from [217.75.229.77] (helo=cluster2.smr.serenamail.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9TJx-0000YB-Iq for msec-archive@ietf.org; Tue, 23 Jan 2007 16:36:52 -0500 Received: by cluster2.smr.serenamail.com (Postfix, from userid 59) id 351A452C38F; Tue, 23 Jan 2007 21:32:52 +0100 (CET) To: msec-archive@ietf.org Subject: Wave of attacks in Baghdad leaves 24 dead Message-ID: <1169584372.33636.qmail@cnn.com> From: "CNN news" Content-type: text/html Date: Tue, 23 Jan 2007 21:32:52 +0100 (CET) X-Spam-Score: 3.1 (+++) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Untitled Document

Wave of attacks in Baghdad leaves 24 dead

POSTED: 1:21 p.m. EST, January 18, 2007

story.thurs.blast.ap.jpg  A U.S. soldier treats a man wounded by a truck bomb in Kirkuk.

• Three car bombings kill 10 at popular Baghdad market in Shiite Dora district
• Dora bomb kills 1; Baghdad police bombing kills 4, includes civilians
• Car bomb in city's Camp Sara area kills 3 civilians
• Bomb near police station kills 2; mortar attack in Sunni neighborhood kills 4

BAGHDAD, Iraq (CNN) -- More than half-a-dozen bombs and a mortar attack ripped through Baghdad on Thursday, leaving at least 24 people dead and 67 wounded, according to an Interior Ministry source.

In the day's deadliest attack, 10 died after three car bombs detonated nearly simultaneously at a popular vegetable market in southern Baghdad's Dora district. The blast wounded 30 people, according to an Interior Ministry official.

Lettuce and bloodstained clothes littered the ground among the debris left by buildings and vehicles, according to The Associated Press. The blast's impact caused a metal roof to blow off from a loading area, leaving a van burned out, with lettuce and onions still on top of it, the AP said.

Read more about this and other attacks in Iraq...

CNN's Sam Dagher and Jomana Karadsheh contributed to this report.

Copyright 2007 CNN. All rights reserved.This material may not be published, broadcast, rewritten, or redistributed. Associated Press contributed to this report.
From msec-bounces@securemulticast.org Mon Jan 29 10:00:32 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBXzk-000190-BW for msec-archive@lists.ietf.org; Mon, 29 Jan 2007 10:00:32 -0500 Received: from six.pairlist.net ([209.68.2.254]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBXzi-0007fB-Um for msec-archive@lists.ietf.org; Mon, 29 Jan 2007 10:00:32 -0500 Received: from six.pairlist.net (localhost [127.0.0.1]) by six.pairlist.net (Postfix) with ESMTP id 38C7C2C385; Mon, 29 Jan 2007 10:00:25 -0500 (EST) X-Original-To: msec@lists6.securemulticast.org Delivered-To: msec@six.pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by six.pairlist.net (Postfix) with SMTP id 13D5C2B914 for ; Mon, 29 Jan 2007 10:00:23 -0500 (EST) Received: (qmail 90988 invoked by uid 3269); 29 Jan 2007 15:00:22 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 90985 invoked from network); 29 Jan 2007 15:00:22 -0000 Received: from mailwash15.pair.com (66.39.2.15) by klesh.pair.com with SMTP; 29 Jan 2007 15:00:22 -0000 Received: from localhost (localhost [127.0.0.1]) by mailwash15.pair.com (Postfix) with SMTP id 1CB5FE9D44 for ; Mon, 29 Jan 2007 10:00:23 -0500 (EST) Received: from smtp.theory.csail.mit.edu (smtp.theory.csail.mit.edu [128.30.50.12]) by mailwash15.pair.com (Postfix) with ESMTP id 14A80E9D3D for ; Mon, 29 Jan 2007 10:00:23 -0500 (EST) Received: from theory.lcs.mit.edu ([128.30.51.92] helo=frege) by smtp.theory.csail.mit.edu with esmtpa (Exim 4.63) (envelope-from ) id 1HBXzZ-0006mS-3I for msec@securemulticast.org; Mon, 29 Jan 2007 10:00:22 -0500 To: msec@securemulticast.org Cc: From: Ling Cheung Date: Mon, 29 Jan 2007 10:00:40 -0500 Message-ID: <87r6tddgiv.fsf@theory.csail.mit.edu> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux) MIME-Version: 1.0 identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi Reto, Thanks a lot for your advice. With the patch you suggested and a few other tweaks, we managed to get the daemon running. Not the gui, though. Seems like some files are missing from the SourceForge CVS repository. [...] Content analysis details: (-104.4 points, 11.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -100 USER_IN_WHITELIST From: address is in the user's white-list -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.0 AWL AWL: From: address is in the auto white-list Subject: Re: [MSEC] GSAKMP daemon X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "IETF Multicast Security \(MSEC\) WG list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: msec-bounces@securemulticast.org Errors-To: msec-bounces@securemulticast.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Hi Reto, Thanks a lot for your advice. With the patch you suggested and a few other tweaks, we managed to get the daemon running. Not the gui, though. Seems like some files are missing from the SourceForge CVS repository. We are considering gsakmp for wireless networks where intermittent connectivity may be an issue. Do you think it is a reasonable choice? We plan to run some network simulations. Do you recall what types of stability issues you ran into with the sparta implementation? Thanks again for your help and best wishes. P.S. I sent this message earlier to but it bounced. -- Ling Cheung MIT CSAIL 32 Vassar St. (32-G628) Cambridge, MA 02139 U.S.A. _______________________________________________ msec mailing list msec@securemulticast.org http://six.pairlist.net/mailman/listinfo/msec From msec-bounces@securemulticast.org Mon Jan 29 12:46:41 2007 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBaaX-0008BC-BQ for msec-archive@lists.ietf.org; Mon, 29 Jan 2007 12:46:41 -0500 Received: from six.pairlist.net ([209.68.2.254]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBaaW-0005Ni-1v for msec-archive@lists.ietf.org; Mon, 29 Jan 2007 12:46:41 -0500 Received: from six.pairlist.net (localhost [127.0.0.1]) by six.pairlist.net (Postfix) with ESMTP id 8432C2BB31; Mon, 29 Jan 2007 12:46:31 -0500 (EST) X-Original-To: msec@lists6.securemulticast.org Delivered-To: msec@six.pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by six.pairlist.net (Postfix) with SMTP id 8AC4D2CB52 for ; Mon, 29 Jan 2007 12:45:13 -0500 (EST) Received: (qmail 38207 invoked by uid 3269); 29 Jan 2007 17:45:13 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 38204 invoked from network); 29 Jan 2007 17:45:13 -0000 Received: from mailwash15.pair.com (66.39.2.15) by klesh.pair.com with SMTP; 29 Jan 2007 17:45:13 -0000 Received: from localhost (localhost [127.0.0.1]) by mailwash15.pair.com (Postfix) with SMTP id C9D56E9D58 for ; Mon, 29 Jan 2007 12:45:13 -0500 (EST) Received: from mailx.swiss-it.ch (zux006-004-203.adsl.green.ch [81.6.4.203]) by mailwash15.pair.com (Postfix) with ESMTP id 9053CE9D51 for ; Mon, 29 Jan 2007 12:45:13 -0500 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailx.swiss-it.ch (Postfix) with ESMTP id 81D6D58909; Mon, 29 Jan 2007 18:45:11 +0100 (CET) Received: from mailx.swiss-it.ch ([127.0.0.1]) by localhost (mailx [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17127-02; Mon, 29 Jan 2007 18:44:45 +0100 (CET) Received: from [192.168.1.4] (212-41-116-84.adsl.solnet.ch [212.41.116.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailx.swiss-it.ch (Postfix) with ESMTP id E27DD58863; Mon, 29 Jan 2007 18:44:43 +0100 (CET) Message-ID: <45BE32A3.3010903@buerki.info> Date: Mon, 29 Jan 2007 18:45:07 +0100 From: Reto Buerki User-Agent: Icedove 1.5.0.9 (X11/20061220) MIME-Version: 1.0 To: Ling Cheung References: <87r6tddgiv.fsf@theory.csail.mit.edu> In-Reply-To: <87r6tddgiv.fsf@theory.csail.mit.edu> Cc: msec@securemulticast.org Subject: Re: [MSEC] GSAKMP daemon X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "IETF Multicast Security \(MSEC\) WG list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: msec-bounces@securemulticast.org Errors-To: msec-bounces@securemulticast.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Hi Ling Glad to hear that my little patch helped! I have no experience with the GUI sorry. The only thing I tried was to communicate with the daemon on the command line. I used the following commands: # create token: tokengen L 1 /usr/local/gsakmp \ /usr/local/gsakmp/certs/localcert.der \ /usr/local/gsakmp/private/localkey.der # activate group: apifeeder CrtGrp /usr/local/gsakmp/gsakmp.token # RTJ (request to join): apifeeder ReqTJL 239.1.1.1 12345 1 localhost # Key request: apifeeder ReqKey 239.1.1.1 12345 the daemon segfaulted at one command, I can't recall exactly which one it was and had no time to find out why. maybe you have more luck. > P.S. I sent this message earlier to > but it bounced. Thanks for this information! It's fixed now. - reto Ling Cheung wrote: > Hi Reto, > > Thanks a lot for your advice. With the patch you suggested and a few > other tweaks, we managed to get the daemon running. Not the gui, > though. Seems like some files are missing from the SourceForge CVS > repository. > > We are considering gsakmp for wireless networks where intermittent > connectivity may be an issue. Do you think it is a reasonable choice? > We plan to run some network simulations. Do you recall what types of > stability issues you ran into with the sparta implementation? > > Thanks again for your help and best wishes. > > P.S. I sent this message earlier to > but it bounced. > _______________________________________________ msec mailing list msec@securemulticast.org http://six.pairlist.net/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 20:49:28 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBi7G-0006yM-6a; Mon, 29 Jan 2007 20:48:58 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBi7E-0006yH-46 for msec@ietf.org; Mon, 29 Jan 2007 20:48:56 -0500 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBi7C-0005SC-Oh for msec@ietf.org; Mon, 29 Jan 2007 20:48:56 -0500 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U1mrId027244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Jan 2007 17:48:54 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U1mqud008222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 29 Jan 2007 17:48:53 -0800 Message-ID: <45BEA3BB.50001@qualcomm.com> Date: Mon, 29 Jan 2007 17:47:39 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Subject: [MSEC] MSEC status update X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, After a long hiatus, I am back on this with high priority. First of all, my sincere apologies for dropping this for so long. I was in India for about 4 weeks, after that catching up on things at work and generally postponing MSEC work until today. A few of you prompted me, and I have tried to get some work done before today, but it just did not work out. Anyway, that is behind us and let us get going with some energy so we can finish the work and close MSEC soon. We have a lot to do and I would like MSEC to stop meeting after Chicago, if all goes well. I have scheduled time for us in Prague, so please plan for it accordingly. That out of the way, we have the following drafts at the WG completion or near completion stage: I. MIKEY-applicability: Has finished last call and I will be forwarding it to Russ shortly. II. ECC: Are we ready to do a WG last call on this? MSEC-IPsec : Same question: Are we ready to do WGLC? GDOI-Update: Ditto Did I miss any from that category? III. We desperately need to finish the following drafts ASAP: GKDP: IV. TESLA-ALC-NORM: What is the status on this? draft-ietf-msec-ipsec-composite-group: Ditto! V. New work (to be adopted after asking for group's opinion): GDOI-SRTP: My opinion is that it is a good idea to have draft-baugher-msec-gdoi-srtp taken up as a WG item. I will ask group opinion on this today. TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an editor trying to finish the work; the original authors, except for Ran are not active in the group any longer. This is a gap filling exercise anyway, so I feel comfortable that there are no conflicts of interest here. I will ask the group of course). draft-weis-esp-group-counter-cipher-00: Ditto. Again, let me know if I missed anything? Thanks for your patience folks. Let's get some work done. best regards, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 20:49:28 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBi7G-0006yM-6a; Mon, 29 Jan 2007 20:48:58 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBi7E-0006yH-46 for msec@ietf.org; Mon, 29 Jan 2007 20:48:56 -0500 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBi7C-0005SC-Oh for msec@ietf.org; Mon, 29 Jan 2007 20:48:56 -0500 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U1mrId027244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Jan 2007 17:48:54 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U1mqud008222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 29 Jan 2007 17:48:53 -0800 Message-ID: <45BEA3BB.50001@qualcomm.com> Date: Mon, 29 Jan 2007 17:47:39 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Subject: [MSEC] MSEC status update X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, After a long hiatus, I am back on this with high priority. First of all, my sincere apologies for dropping this for so long. I was in India for about 4 weeks, after that catching up on things at work and generally postponing MSEC work until today. A few of you prompted me, and I have tried to get some work done before today, but it just did not work out. Anyway, that is behind us and let us get going with some energy so we can finish the work and close MSEC soon. We have a lot to do and I would like MSEC to stop meeting after Chicago, if all goes well. I have scheduled time for us in Prague, so please plan for it accordingly. That out of the way, we have the following drafts at the WG completion or near completion stage: I. MIKEY-applicability: Has finished last call and I will be forwarding it to Russ shortly. II. ECC: Are we ready to do a WG last call on this? MSEC-IPsec : Same question: Are we ready to do WGLC? GDOI-Update: Ditto Did I miss any from that category? III. We desperately need to finish the following drafts ASAP: GKDP: IV. TESLA-ALC-NORM: What is the status on this? draft-ietf-msec-ipsec-composite-group: Ditto! V. New work (to be adopted after asking for group's opinion): GDOI-SRTP: My opinion is that it is a good idea to have draft-baugher-msec-gdoi-srtp taken up as a WG item. I will ask group opinion on this today. TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an editor trying to finish the work; the original authors, except for Ran are not active in the group any longer. This is a gap filling exercise anyway, so I feel comfortable that there are no conflicts of interest here. I will ask the group of course). draft-weis-esp-group-counter-cipher-00: Ditto. Again, let me know if I missed anything? Thanks for your patience folks. Let's get some work done. best regards, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 20:52:10 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiAB-0000IK-TH; Mon, 29 Jan 2007 20:51:59 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiA9-0000EX-QI for msec@ietf.org; Mon, 29 Jan 2007 20:51:57 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBiA8-0006Nw-Dq for msec@ietf.org; Mon, 29 Jan 2007 20:51:57 -0500 Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U1ptrv030348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Jan 2007 17:51:55 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U1psfo017278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 29 Jan 2007 17:51:55 -0800 (PST) Message-ID: <45BEA471.9080101@qualcomm.com> Date: Mon, 29 Jan 2007 17:50:41 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [MSEC] Any objections to adopting TESLA-IPsec as a WG item X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, Please send any objections to adopting draft-dondeti-msec-ipsec-tesla-01 as a WG item (I know, I know, my name is on there, but this is not my pet topic or whatever. I am just advancing some leftover TESLA work done by other WG contributors through the process). Please see http://www3.ietf.org/proceedings/06nov/minutes/msec.txt for some more context. thanks, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 20:52:10 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiAB-0000IK-TH; Mon, 29 Jan 2007 20:51:59 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiA9-0000EX-QI for msec@ietf.org; Mon, 29 Jan 2007 20:51:57 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBiA8-0006Nw-Dq for msec@ietf.org; Mon, 29 Jan 2007 20:51:57 -0500 Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U1ptrv030348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Jan 2007 17:51:55 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U1psfo017278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 29 Jan 2007 17:51:55 -0800 (PST) Message-ID: <45BEA471.9080101@qualcomm.com> Date: Mon, 29 Jan 2007 17:50:41 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [MSEC] Any objections to adopting TESLA-IPsec as a WG item X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, Please send any objections to adopting draft-dondeti-msec-ipsec-tesla-01 as a WG item (I know, I know, my name is on there, but this is not my pet topic or whatever. I am just advancing some leftover TESLA work done by other WG contributors through the process). Please see http://www3.ietf.org/proceedings/06nov/minutes/msec.txt for some more context. thanks, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 21:00:11 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiHu-0003aq-T7; Mon, 29 Jan 2007 20:59:58 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiHu-0003aL-4X for msec@ietf.org; Mon, 29 Jan 2007 20:59:58 -0500 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBiHs-0000Ly-Q2 for msec@ietf.org; Mon, 29 Jan 2007 20:59:58 -0500 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U1xtHg028567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 29 Jan 2007 17:59:55 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U1xsQQ010311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Jan 2007 17:59:54 -0800 Message-ID: <45BEA651.3040206@qualcomm.com> Date: Mon, 29 Jan 2007 17:58:41 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org, Russ Housley Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: Subject: [MSEC] Any objections to adopting CTR mode draft as a WG item? X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, draft-weis-esp-group-counter-cipher-00 was presented at San Diego and was discussed at length. One could argue that this is out of scope for our charter, although the charter does not explicitly disallow multi-sender operation (here is the relevant line from the charter: "Initial efforts will focus on scalable solutions for groups with a single source and a very large number of recipients. " Ok, we have been at this for some 7 years and can no longer claim to be in initial stages, but you know what I mean.). At the meeting 6 people thought this should be a work item and no one objected. Any thoughts? Russ, could you tell us if we can do this without rechartering? thanks, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 21:00:11 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiHu-0003aq-T7; Mon, 29 Jan 2007 20:59:58 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiHu-0003aL-4X for msec@ietf.org; Mon, 29 Jan 2007 20:59:58 -0500 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBiHs-0000Ly-Q2 for msec@ietf.org; Mon, 29 Jan 2007 20:59:58 -0500 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U1xtHg028567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 29 Jan 2007 17:59:55 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U1xsQQ010311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Jan 2007 17:59:54 -0800 Message-ID: <45BEA651.3040206@qualcomm.com> Date: Mon, 29 Jan 2007 17:58:41 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org, Russ Housley Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: Subject: [MSEC] Any objections to adopting CTR mode draft as a WG item? X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, draft-weis-esp-group-counter-cipher-00 was presented at San Diego and was discussed at length. One could argue that this is out of scope for our charter, although the charter does not explicitly disallow multi-sender operation (here is the relevant line from the charter: "Initial efforts will focus on scalable solutions for groups with a single source and a very large number of recipients. " Ok, we have been at this for some 7 years and can no longer claim to be in initial stages, but you know what I mean.). At the meeting 6 people thought this should be a work item and no one objected. Any thoughts? Russ, could you tell us if we can do this without rechartering? thanks, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 21:07:31 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiP5-0007I7-Gv; Mon, 29 Jan 2007 21:07:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiP4-0007I2-Pz for msec@ietf.org; Mon, 29 Jan 2007 21:07:22 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBiP3-0002AM-EV for msec@ietf.org; Mon, 29 Jan 2007 21:07:22 -0500 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U27Kx1032384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Jan 2007 18:07:20 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U27JbE000721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 29 Jan 2007 18:07:20 -0800 (PST) Message-ID: <45BEA80E.8070800@qualcomm.com> Date: Mon, 29 Jan 2007 18:06:06 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [MSEC] Any objections to adopting GDOI-SRTP as a work item? X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, At the San Diego meeting, Mark presented GDOI-SRTP describing how to use GDOI to setup SRTP crypto context. There was some discussion and a couple of folks (Russ and me) volunteered to review the work. Please consider this a call for 1) gauging interest in this work and 2) adopting this work as a work item in MSEC. Please send your comments before next Monday (Feb 5, 2007). thanks, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 21:07:31 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiP5-0007I7-Gv; Mon, 29 Jan 2007 21:07:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiP4-0007I2-Pz for msec@ietf.org; Mon, 29 Jan 2007 21:07:22 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBiP3-0002AM-EV for msec@ietf.org; Mon, 29 Jan 2007 21:07:22 -0500 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U27Kx1032384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Jan 2007 18:07:20 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U27JbE000721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 29 Jan 2007 18:07:20 -0800 (PST) Message-ID: <45BEA80E.8070800@qualcomm.com> Date: Mon, 29 Jan 2007 18:06:06 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [MSEC] Any objections to adopting GDOI-SRTP as a work item? X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, At the San Diego meeting, Mark presented GDOI-SRTP describing how to use GDOI to setup SRTP crypto context. There was some discussion and a couple of folks (Russ and me) volunteered to review the work. Please consider this a call for 1) gauging interest in this work and 2) adopting this work as a work item in MSEC. Please send your comments before next Monday (Feb 5, 2007). thanks, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 21:09:39 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiR7-0007f0-EF; Mon, 29 Jan 2007 21:09:29 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiR5-0007eH-NH for msec@ietf.org; Mon, 29 Jan 2007 21:09:27 -0500 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBiR4-0002fF-Bc for msec@ietf.org; Mon, 29 Jan 2007 21:09:27 -0500 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U29PnZ030531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Jan 2007 18:09:25 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U29OS9001273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 29 Jan 2007 18:09:25 -0800 (PST) Message-ID: <45BEA88B.7040508@qualcomm.com> Date: Mon, 29 Jan 2007 18:08:11 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Subject: [MSEC] Please send comments and notes by Feb 5, 2007 X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, I have sent a call for comments on various pending drafts for consideration as WG items. Please send your comments by Feb 5, 2007 at the latest. thanks, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 21:09:39 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiR7-0007f0-EF; Mon, 29 Jan 2007 21:09:29 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBiR5-0007eH-NH for msec@ietf.org; Mon, 29 Jan 2007 21:09:27 -0500 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBiR4-0002fF-Bc for msec@ietf.org; Mon, 29 Jan 2007 21:09:27 -0500 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U29PnZ030531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Jan 2007 18:09:25 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U29OS9001273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 29 Jan 2007 18:09:25 -0800 (PST) Message-ID: <45BEA88B.7040508@qualcomm.com> Date: Mon, 29 Jan 2007 18:08:11 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Subject: [MSEC] Please send comments and notes by Feb 5, 2007 X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Folks, I have sent a call for comments on various pending drafts for consideration as WG items. Please send your comments by Feb 5, 2007 at the latest. thanks, Lakshminath _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 21:48:40 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBj2l-000831-VI; Mon, 29 Jan 2007 21:48:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBj2k-00082w-0J for msec@ietf.org; Mon, 29 Jan 2007 21:48:22 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBj2i-0003Bd-1Q for msec@ietf.org; Mon, 29 Jan 2007 21:48:21 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCN00F7WUEZ4V@szxga01-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 10:47:23 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCN00F3TUEZ7Z@szxga01-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 10:47:23 +0800 (CST) Received: from l52008 ([10.111.12.63]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JCN00GIEUEVY0@szxml04-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 10:47:22 +0800 (CST) Date: Tue, 30 Jan 2007 10:47:19 +0800 From: Liu Ya Subject: RE: [MSEC] MSEC status update In-reply-to: <45BEA3BB.50001@qualcomm.com> To: 'Lakshminath Dondeti' Message-id: <011501c74418$f5e99ba0$3f0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcdEEU9d6xhac3jLR/WT8pn2wB3xmwAA4iAQ X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Cc: msec@ietf.org X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hi, At the San Diego meeting, OSPF guys agreed to work on OSPFv3 automated group keying and write a requirement doc. The concluded requirements will be feedbacked to MSEC WG. New work items may come forth. In fact, we are preparing that doc. After an initial analysis, it is very possible that existing GKM protocols do not function well to meet all OSPFv3 requirements. This means there may be chance to extend GKM protocols to support OSPFv3 keying, and obviously it is difficult to finished this work before Chicago. This is my concern. Regards, Liu Ya Lakshminath Dondeti wrote: > > Folks, > > After a long hiatus, I am back on this with high priority. First of > all, my sincere apologies for dropping this for so long. I > was in India > for about 4 weeks, after that catching up on things at work and > generally postponing MSEC work until today. A few of you > prompted me, > and I have tried to get some work done before today, but it > just did not > work out. Anyway, that is behind us and let us get going with some > energy so we can finish the work and close MSEC soon. > > We have a lot to do and I would like MSEC to stop meeting > after Chicago, > if all goes well. I have scheduled time for us in Prague, so please > plan for it accordingly. > > That out of the way, we have the following drafts at the WG > completion > or near completion stage: > > I. > MIKEY-applicability: Has finished last call and I will be > forwarding it > to Russ shortly. > > II. > ECC: Are we ready to do a WG last call on this? > MSEC-IPsec : Same question: Are we ready to do WGLC? > GDOI-Update: Ditto > > Did I miss any from that category? > > III. > We desperately need to finish the following drafts ASAP: > GKDP: > > IV. > TESLA-ALC-NORM: What is the status on this? > draft-ietf-msec-ipsec-composite-group: Ditto! > > V. > New work (to be adopted after asking for group's opinion): > GDOI-SRTP: My opinion is that it is a good idea to have > draft-baugher-msec-gdoi-srtp taken up as a WG item. I will ask group > opinion on this today. > TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an > editor trying > to finish the work; the original authors, except for Ran are > not active > in the group any longer. This is a gap filling exercise anyway, so I > feel comfortable that there are no conflicts of interest > here. I will > ask the group of course). > draft-weis-esp-group-counter-cipher-00: Ditto. > > Again, let me know if I missed anything? > > > Thanks for your patience folks. Let's get some work done. > > best regards, > Lakshminath > > _______________________________________________ > MSEC mailing list > MSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/msec > _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 21:48:40 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBj2l-000831-VI; Mon, 29 Jan 2007 21:48:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBj2k-00082w-0J for msec@ietf.org; Mon, 29 Jan 2007 21:48:22 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBj2i-0003Bd-1Q for msec@ietf.org; Mon, 29 Jan 2007 21:48:21 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCN00F7WUEZ4V@szxga01-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 10:47:23 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCN00F3TUEZ7Z@szxga01-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 10:47:23 +0800 (CST) Received: from l52008 ([10.111.12.63]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JCN00GIEUEVY0@szxml04-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 10:47:22 +0800 (CST) Date: Tue, 30 Jan 2007 10:47:19 +0800 From: Liu Ya Subject: RE: [MSEC] MSEC status update In-reply-to: <45BEA3BB.50001@qualcomm.com> To: 'Lakshminath Dondeti' Message-id: <011501c74418$f5e99ba0$3f0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcdEEU9d6xhac3jLR/WT8pn2wB3xmwAA4iAQ X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Cc: msec@ietf.org X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hi, At the San Diego meeting, OSPF guys agreed to work on OSPFv3 automated group keying and write a requirement doc. The concluded requirements will be feedbacked to MSEC WG. New work items may come forth. In fact, we are preparing that doc. After an initial analysis, it is very possible that existing GKM protocols do not function well to meet all OSPFv3 requirements. This means there may be chance to extend GKM protocols to support OSPFv3 keying, and obviously it is difficult to finished this work before Chicago. This is my concern. Regards, Liu Ya Lakshminath Dondeti wrote: > > Folks, > > After a long hiatus, I am back on this with high priority. First of > all, my sincere apologies for dropping this for so long. I > was in India > for about 4 weeks, after that catching up on things at work and > generally postponing MSEC work until today. A few of you > prompted me, > and I have tried to get some work done before today, but it > just did not > work out. Anyway, that is behind us and let us get going with some > energy so we can finish the work and close MSEC soon. > > We have a lot to do and I would like MSEC to stop meeting > after Chicago, > if all goes well. I have scheduled time for us in Prague, so please > plan for it accordingly. > > That out of the way, we have the following drafts at the WG > completion > or near completion stage: > > I. > MIKEY-applicability: Has finished last call and I will be > forwarding it > to Russ shortly. > > II. > ECC: Are we ready to do a WG last call on this? > MSEC-IPsec : Same question: Are we ready to do WGLC? > GDOI-Update: Ditto > > Did I miss any from that category? > > III. > We desperately need to finish the following drafts ASAP: > GKDP: > > IV. > TESLA-ALC-NORM: What is the status on this? > draft-ietf-msec-ipsec-composite-group: Ditto! > > V. > New work (to be adopted after asking for group's opinion): > GDOI-SRTP: My opinion is that it is a good idea to have > draft-baugher-msec-gdoi-srtp taken up as a WG item. I will ask group > opinion on this today. > TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an > editor trying > to finish the work; the original authors, except for Ran are > not active > in the group any longer. This is a gap filling exercise anyway, so I > feel comfortable that there are no conflicts of interest > here. I will > ask the group of course). > draft-weis-esp-group-counter-cipher-00: Ditto. > > Again, let me know if I missed anything? > > > Thanks for your patience folks. Let's get some work done. > > best regards, > Lakshminath > > _______________________________________________ > MSEC mailing list > MSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/msec > _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 22:04:16 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBjHo-0005r1-2e; Mon, 29 Jan 2007 22:03:56 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBjHm-0005qt-PN for msec@ietf.org; Mon, 29 Jan 2007 22:03:54 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBjHl-0005gQ-Bt for msec@ietf.org; Mon, 29 Jan 2007 22:03:54 -0500 Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U33lmX006914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 29 Jan 2007 19:03:48 -0800 Received: from [10.50.72.175] (qconnect-10-50-72-175.qualcomm.com [10.50.72.175]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U33gXt007593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Jan 2007 19:03:47 -0800 (PST) Message-ID: <45BEB545.50106@qualcomm.com> Date: Mon, 29 Jan 2007 19:02:29 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: Liu Ya Subject: Re: [MSEC] MSEC status update References: <011501c74418$f5e99ba0$3f0c6f0a@china.huawei.com> In-Reply-To: <011501c74418$f5e99ba0$3f0c6f0a@china.huawei.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e Cc: msec@ietf.org X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hi, Thanks for the update. If you have an initial version of the requirements or threads of discussion on the OSPF list that MSEC should read to catch up on this, please do let us know. regards, Lakshminath Liu Ya wrote: > Hi, > > At the San Diego meeting, OSPF guys agreed to work on OSPFv3 automated > group keying and write a requirement doc. The concluded requirements > will be feedbacked to MSEC WG. New work items may come forth. > > In fact, we are preparing that doc. After an initial analysis, it is > very possible that existing GKM protocols do not function well to > meet all OSPFv3 requirements. This means there may be chance to extend > GKM protocols to support OSPFv3 keying, and obviously it is difficult > to finished this work before Chicago. This is my concern. > > Regards, > Liu Ya > > Lakshminath Dondeti wrote: >> Folks, >> >> After a long hiatus, I am back on this with high priority. First of > >> all, my sincere apologies for dropping this for so long. I >> was in India >> for about 4 weeks, after that catching up on things at work and >> generally postponing MSEC work until today. A few of you >> prompted me, >> and I have tried to get some work done before today, but it >> just did not >> work out. Anyway, that is behind us and let us get going with some >> energy so we can finish the work and close MSEC soon. >> >> We have a lot to do and I would like MSEC to stop meeting >> after Chicago, >> if all goes well. I have scheduled time for us in Prague, so please > >> plan for it accordingly. >> >> That out of the way, we have the following drafts at the WG >> completion >> or near completion stage: >> >> I. >> MIKEY-applicability: Has finished last call and I will be >> forwarding it >> to Russ shortly. >> >> II. >> ECC: Are we ready to do a WG last call on this? >> MSEC-IPsec : Same question: Are we ready to do WGLC? >> GDOI-Update: Ditto >> >> Did I miss any from that category? >> >> III. >> We desperately need to finish the following drafts ASAP: >> GKDP: >> >> IV. >> TESLA-ALC-NORM: What is the status on this? >> draft-ietf-msec-ipsec-composite-group: Ditto! >> >> V. >> New work (to be adopted after asking for group's opinion): >> GDOI-SRTP: My opinion is that it is a good idea to have >> draft-baugher-msec-gdoi-srtp taken up as a WG item. I will ask > group >> opinion on this today. >> TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an >> editor trying >> to finish the work; the original authors, except for Ran are >> not active >> in the group any longer. This is a gap filling exercise anyway, so > I >> feel comfortable that there are no conflicts of interest >> here. I will >> ask the group of course). >> draft-weis-esp-group-counter-cipher-00: Ditto. >> >> Again, let me know if I missed anything? >> >> >> Thanks for your patience folks. Let's get some work done. >> >> best regards, >> Lakshminath >> >> _______________________________________________ >> MSEC mailing list >> MSEC@ietf.org >> https://www1.ietf.org/mailman/listinfo/msec >> > > > _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 22:04:16 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBjHo-0005r1-2e; Mon, 29 Jan 2007 22:03:56 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBjHm-0005qt-PN for msec@ietf.org; Mon, 29 Jan 2007 22:03:54 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBjHl-0005gQ-Bt for msec@ietf.org; Mon, 29 Jan 2007 22:03:54 -0500 Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0U33lmX006914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 29 Jan 2007 19:03:48 -0800 Received: from [10.50.72.175] (qconnect-10-50-72-175.qualcomm.com [10.50.72.175]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0U33gXt007593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Jan 2007 19:03:47 -0800 (PST) Message-ID: <45BEB545.50106@qualcomm.com> Date: Mon, 29 Jan 2007 19:02:29 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: Liu Ya Subject: Re: [MSEC] MSEC status update References: <011501c74418$f5e99ba0$3f0c6f0a@china.huawei.com> In-Reply-To: <011501c74418$f5e99ba0$3f0c6f0a@china.huawei.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e Cc: msec@ietf.org X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hi, Thanks for the update. If you have an initial version of the requirements or threads of discussion on the OSPF list that MSEC should read to catch up on this, please do let us know. regards, Lakshminath Liu Ya wrote: > Hi, > > At the San Diego meeting, OSPF guys agreed to work on OSPFv3 automated > group keying and write a requirement doc. The concluded requirements > will be feedbacked to MSEC WG. New work items may come forth. > > In fact, we are preparing that doc. After an initial analysis, it is > very possible that existing GKM protocols do not function well to > meet all OSPFv3 requirements. This means there may be chance to extend > GKM protocols to support OSPFv3 keying, and obviously it is difficult > to finished this work before Chicago. This is my concern. > > Regards, > Liu Ya > > Lakshminath Dondeti wrote: >> Folks, >> >> After a long hiatus, I am back on this with high priority. First of > >> all, my sincere apologies for dropping this for so long. I >> was in India >> for about 4 weeks, after that catching up on things at work and >> generally postponing MSEC work until today. A few of you >> prompted me, >> and I have tried to get some work done before today, but it >> just did not >> work out. Anyway, that is behind us and let us get going with some >> energy so we can finish the work and close MSEC soon. >> >> We have a lot to do and I would like MSEC to stop meeting >> after Chicago, >> if all goes well. I have scheduled time for us in Prague, so please > >> plan for it accordingly. >> >> That out of the way, we have the following drafts at the WG >> completion >> or near completion stage: >> >> I. >> MIKEY-applicability: Has finished last call and I will be >> forwarding it >> to Russ shortly. >> >> II. >> ECC: Are we ready to do a WG last call on this? >> MSEC-IPsec : Same question: Are we ready to do WGLC? >> GDOI-Update: Ditto >> >> Did I miss any from that category? >> >> III. >> We desperately need to finish the following drafts ASAP: >> GKDP: >> >> IV. >> TESLA-ALC-NORM: What is the status on this? >> draft-ietf-msec-ipsec-composite-group: Ditto! >> >> V. >> New work (to be adopted after asking for group's opinion): >> GDOI-SRTP: My opinion is that it is a good idea to have >> draft-baugher-msec-gdoi-srtp taken up as a WG item. I will ask > group >> opinion on this today. >> TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an >> editor trying >> to finish the work; the original authors, except for Ran are >> not active >> in the group any longer. This is a gap filling exercise anyway, so > I >> feel comfortable that there are no conflicts of interest >> here. I will >> ask the group of course). >> draft-weis-esp-group-counter-cipher-00: Ditto. >> >> Again, let me know if I missed anything? >> >> >> Thanks for your patience folks. Let's get some work done. >> >> best regards, >> Lakshminath >> >> _______________________________________________ >> MSEC mailing list >> MSEC@ietf.org >> https://www1.ietf.org/mailman/listinfo/msec >> > > > _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 22:16:05 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBjTG-0001t2-Un; Mon, 29 Jan 2007 22:15:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBjTG-0001sx-4B for msec@ietf.org; Mon, 29 Jan 2007 22:15:46 -0500 Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBjTE-00070F-7R for msec@ietf.org; Mon, 29 Jan 2007 22:15:46 -0500 Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCN00AK9VNJ7V@szxga04-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 11:14:07 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCN00CU6VNIAP@szxga04-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 11:14:07 +0800 (CST) Received: from l52008 ([10.111.12.63]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JCN00GGEVNFY0@szxml04-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 11:14:06 +0800 (CST) Date: Tue, 30 Jan 2007 11:14:03 +0800 From: Liu Ya Subject: RE: [MSEC] MSEC status update In-reply-to: <45BEB545.50106@qualcomm.com> To: 'Lakshminath Dondeti' Message-id: <011701c7441c$b1c7c1a0$3f0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcdEG0Zx4APoWhumS0mfEjZTRllRIQAACYpw X-Spam-Score: 0.0 (/) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede Cc: msec@ietf.org X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Sure. I will post to MSEC mail list all the latest information about the requirements or discussions on OSPFv3 automated keying. Lakshminath Dondeti wrote: > > Hi, > > Thanks for the update. If you have an initial version of the > requirements or threads of discussion on the OSPF list that > MSEC should > read to catch up on this, please do let us know. > > regards, > Lakshminath > > Liu Ya wrote: > > Hi, > > > > At the San Diego meeting, OSPF guys agreed to work on > OSPFv3 automated > > group keying and write a requirement doc. The concluded requirements > > will be feedbacked to MSEC WG. New work items may come forth. > > > > In fact, we are preparing that doc. After an initial analysis, it is > > very possible that existing GKM protocols do not function well to > > meet all OSPFv3 requirements. This means there may be > chance to extend > > GKM protocols to support OSPFv3 keying, and obviously it is > difficult > > to finished this work before Chicago. This is my concern. > > > > Regards, > > Liu Ya > > > > Lakshminath Dondeti wrote: > >> Folks, > >> > >> After a long hiatus, I am back on this with high priority. > First of > > > >> all, my sincere apologies for dropping this for so long. I > >> was in India > >> for about 4 weeks, after that catching up on things at work and > >> generally postponing MSEC work until today. A few of you > >> prompted me, > >> and I have tried to get some work done before today, but it > >> just did not > >> work out. Anyway, that is behind us and let us get going > with some > >> energy so we can finish the work and close MSEC soon. > >> > >> We have a lot to do and I would like MSEC to stop meeting > >> after Chicago, > >> if all goes well. I have scheduled time for us in Prague, > so please > > > >> plan for it accordingly. > >> > >> That out of the way, we have the following drafts at the WG > >> completion > >> or near completion stage: > >> > >> I. > >> MIKEY-applicability: Has finished last call and I will be > >> forwarding it > >> to Russ shortly. > >> > >> II. > >> ECC: Are we ready to do a WG last call on this? > >> MSEC-IPsec : Same question: Are we ready to do WGLC? > >> GDOI-Update: Ditto > >> > >> Did I miss any from that category? > >> > >> III. > >> We desperately need to finish the following drafts ASAP: > >> GKDP: > >> > >> IV. > >> TESLA-ALC-NORM: What is the status on this? > >> draft-ietf-msec-ipsec-composite-group: Ditto! > >> > >> V. > >> New work (to be adopted after asking for group's opinion): > >> GDOI-SRTP: My opinion is that it is a good idea to have > >> draft-baugher-msec-gdoi-srtp taken up as a WG item. I will ask > > group > >> opinion on this today. > >> TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an > >> editor trying > >> to finish the work; the original authors, except for Ran are > >> not active > >> in the group any longer. This is a gap filling exercise anyway, so > > I > >> feel comfortable that there are no conflicts of interest > >> here. I will > >> ask the group of course). > >> draft-weis-esp-group-counter-cipher-00: Ditto. > >> > >> Again, let me know if I missed anything? > >> > >> > >> Thanks for your patience folks. Let's get some work done. > >> > >> best regards, > >> Lakshminath > >> > >> _______________________________________________ > >> MSEC mailing list > >> MSEC@ietf.org > >> https://www1.ietf.org/mailman/listinfo/msec > >> > > > > > > > _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Mon Jan 29 22:16:05 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBjTG-0001t2-Un; Mon, 29 Jan 2007 22:15:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBjTG-0001sx-4B for msec@ietf.org; Mon, 29 Jan 2007 22:15:46 -0500 Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBjTE-00070F-7R for msec@ietf.org; Mon, 29 Jan 2007 22:15:46 -0500 Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCN00AK9VNJ7V@szxga04-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 11:14:07 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCN00CU6VNIAP@szxga04-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 11:14:07 +0800 (CST) Received: from l52008 ([10.111.12.63]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JCN00GGEVNFY0@szxml04-in.huawei.com> for msec@ietf.org; Tue, 30 Jan 2007 11:14:06 +0800 (CST) Date: Tue, 30 Jan 2007 11:14:03 +0800 From: Liu Ya Subject: RE: [MSEC] MSEC status update In-reply-to: <45BEB545.50106@qualcomm.com> To: 'Lakshminath Dondeti' Message-id: <011701c7441c$b1c7c1a0$3f0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcdEG0Zx4APoWhumS0mfEjZTRllRIQAACYpw X-Spam-Score: 0.0 (/) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede Cc: msec@ietf.org X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Sure. I will post to MSEC mail list all the latest information about the requirements or discussions on OSPFv3 automated keying. Lakshminath Dondeti wrote: > > Hi, > > Thanks for the update. If you have an initial version of the > requirements or threads of discussion on the OSPF list that > MSEC should > read to catch up on this, please do let us know. > > regards, > Lakshminath > > Liu Ya wrote: > > Hi, > > > > At the San Diego meeting, OSPF guys agreed to work on > OSPFv3 automated > > group keying and write a requirement doc. The concluded requirements > > will be feedbacked to MSEC WG. New work items may come forth. > > > > In fact, we are preparing that doc. After an initial analysis, it is > > very possible that existing GKM protocols do not function well to > > meet all OSPFv3 requirements. This means there may be > chance to extend > > GKM protocols to support OSPFv3 keying, and obviously it is > difficult > > to finished this work before Chicago. This is my concern. > > > > Regards, > > Liu Ya > > > > Lakshminath Dondeti wrote: > >> Folks, > >> > >> After a long hiatus, I am back on this with high priority. > First of > > > >> all, my sincere apologies for dropping this for so long. I > >> was in India > >> for about 4 weeks, after that catching up on things at work and > >> generally postponing MSEC work until today. A few of you > >> prompted me, > >> and I have tried to get some work done before today, but it > >> just did not > >> work out. Anyway, that is behind us and let us get going > with some > >> energy so we can finish the work and close MSEC soon. > >> > >> We have a lot to do and I would like MSEC to stop meeting > >> after Chicago, > >> if all goes well. I have scheduled time for us in Prague, > so please > > > >> plan for it accordingly. > >> > >> That out of the way, we have the following drafts at the WG > >> completion > >> or near completion stage: > >> > >> I. > >> MIKEY-applicability: Has finished last call and I will be > >> forwarding it > >> to Russ shortly. > >> > >> II. > >> ECC: Are we ready to do a WG last call on this? > >> MSEC-IPsec : Same question: Are we ready to do WGLC? > >> GDOI-Update: Ditto > >> > >> Did I miss any from that category? > >> > >> III. > >> We desperately need to finish the following drafts ASAP: > >> GKDP: > >> > >> IV. > >> TESLA-ALC-NORM: What is the status on this? > >> draft-ietf-msec-ipsec-composite-group: Ditto! > >> > >> V. > >> New work (to be adopted after asking for group's opinion): > >> GDOI-SRTP: My opinion is that it is a good idea to have > >> draft-baugher-msec-gdoi-srtp taken up as a WG item. I will ask > > group > >> opinion on this today. > >> TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an > >> editor trying > >> to finish the work; the original authors, except for Ran are > >> not active > >> in the group any longer. This is a gap filling exercise anyway, so > > I > >> feel comfortable that there are no conflicts of interest > >> here. I will > >> ask the group of course). > >> draft-weis-esp-group-counter-cipher-00: Ditto. > >> > >> Again, let me know if I missed anything? > >> > >> > >> Thanks for your patience folks. Let's get some work done. > >> > >> best regards, > >> Lakshminath > >> > >> _______________________________________________ > >> MSEC mailing list > >> MSEC@ietf.org > >> https://www1.ietf.org/mailman/listinfo/msec > >> > > > > > > > _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Tue Jan 30 05:43:07 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBqRg-0003S9-Vm; Tue, 30 Jan 2007 05:42:36 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBqRf-0003Q6-P8 for msec@ietf.org; Tue, 30 Jan 2007 05:42:35 -0500 Received: from gecko.sbs.de ([194.138.37.40]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HBqRc-00060z-51 for msec@ietf.org; Tue, 30 Jan 2007 05:42:35 -0500 Received: from mail1.sbs.de (localhost [127.0.0.1]) by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id l0UAgRJ8014312; Tue, 30 Jan 2007 11:42:27 +0100 Received: from fthw9xoa.ww002.siemens.net (fthw9xoa.ww002.siemens.net [157.163.133.201]) by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id l0UAgRuc004982; Tue, 30 Jan 2007 11:42:27 +0100 Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by fthw9xoa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jan 2007 11:42:26 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [MSEC] MSEC status update Date: Tue, 30 Jan 2007 11:42:08 +0100 Message-ID: In-reply-to: <45BEA3BB.50001@qualcomm.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MSEC] MSEC status update Thread-Index: AcdEEU8e3yPE2VqgRnG6W4JvOpT3fgASdnzQ References: <45BEA3BB.50001@qualcomm.com> From: "Fries, Steffen" To: "Lakshminath Dondeti" , X-OriginalArrivalTime: 30 Jan 2007 10:42:26.0880 (UTC) FILETIME=[5565DC00:01C7445B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hi Lakshminath, seems fine from my point of view. Would you see the MIKEYv2 proposal in the scope of MSEC or in a different group. Ciao Steffen > -----Original Message----- > From: Lakshminath Dondeti [mailto:ldondeti@qualcomm.com]=20 > Sent: Tuesday, January 30, 2007 2:48 AM > To: msec@ietf.org > Subject: [MSEC] MSEC status update >=20 > Folks, >=20 > After a long hiatus, I am back on this with high priority. =20 > First of all, my sincere apologies for dropping this for so=20 > long. I was in India for about 4 weeks, after that catching=20 > up on things at work and generally postponing MSEC work until=20 > today. A few of you prompted me, and I have tried to get=20 > some work done before today, but it just did not work out. =20 > Anyway, that is behind us and let us get going with some=20 > energy so we can finish the work and close MSEC soon. >=20 > We have a lot to do and I would like MSEC to stop meeting=20 > after Chicago, if all goes well. I have scheduled time for=20 > us in Prague, so please plan for it accordingly. >=20 > That out of the way, we have the following drafts at the WG=20 > completion or near completion stage: >=20 > I. > MIKEY-applicability: Has finished last call and I will be=20 > forwarding it to Russ shortly. >=20 > II. > ECC: Are we ready to do a WG last call on this? > MSEC-IPsec : Same question: Are we ready to do WGLC? > GDOI-Update: Ditto >=20 > Did I miss any from that category? >=20 > III. > We desperately need to finish the following drafts ASAP: > GKDP: >=20 > IV. > TESLA-ALC-NORM: What is the status on this? > draft-ietf-msec-ipsec-composite-group: Ditto! >=20 > V. > New work (to be adopted after asking for group's opinion): > GDOI-SRTP: My opinion is that it is a good idea to have=20 > draft-baugher-msec-gdoi-srtp taken up as a WG item. I will=20 > ask group opinion on this today. > TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an=20 > editor trying to finish the work; the original authors,=20 > except for Ran are not active in the group any longer. This=20 > is a gap filling exercise anyway, so I feel comfortable that=20 > there are no conflicts of interest here. I will ask the=20 > group of course). > draft-weis-esp-group-counter-cipher-00: Ditto. >=20 > Again, let me know if I missed anything? >=20 >=20 > Thanks for your patience folks. Let's get some work done. >=20 > best regards, > Lakshminath >=20 > _______________________________________________ > MSEC mailing list > MSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/msec >=20 _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Tue Jan 30 05:43:07 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBqRg-0003S9-Vm; Tue, 30 Jan 2007 05:42:36 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBqRf-0003Q6-P8 for msec@ietf.org; Tue, 30 Jan 2007 05:42:35 -0500 Received: from gecko.sbs.de ([194.138.37.40]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HBqRc-00060z-51 for msec@ietf.org; Tue, 30 Jan 2007 05:42:35 -0500 Received: from mail1.sbs.de (localhost [127.0.0.1]) by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id l0UAgRJ8014312; Tue, 30 Jan 2007 11:42:27 +0100 Received: from fthw9xoa.ww002.siemens.net (fthw9xoa.ww002.siemens.net [157.163.133.201]) by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id l0UAgRuc004982; Tue, 30 Jan 2007 11:42:27 +0100 Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by fthw9xoa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jan 2007 11:42:26 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [MSEC] MSEC status update Date: Tue, 30 Jan 2007 11:42:08 +0100 Message-ID: In-reply-to: <45BEA3BB.50001@qualcomm.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MSEC] MSEC status update Thread-Index: AcdEEU8e3yPE2VqgRnG6W4JvOpT3fgASdnzQ References: <45BEA3BB.50001@qualcomm.com> From: "Fries, Steffen" To: "Lakshminath Dondeti" , X-OriginalArrivalTime: 30 Jan 2007 10:42:26.0880 (UTC) FILETIME=[5565DC00:01C7445B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hi Lakshminath, seems fine from my point of view. Would you see the MIKEYv2 proposal in the scope of MSEC or in a different group. Ciao Steffen > -----Original Message----- > From: Lakshminath Dondeti [mailto:ldondeti@qualcomm.com]=20 > Sent: Tuesday, January 30, 2007 2:48 AM > To: msec@ietf.org > Subject: [MSEC] MSEC status update >=20 > Folks, >=20 > After a long hiatus, I am back on this with high priority. =20 > First of all, my sincere apologies for dropping this for so=20 > long. I was in India for about 4 weeks, after that catching=20 > up on things at work and generally postponing MSEC work until=20 > today. A few of you prompted me, and I have tried to get=20 > some work done before today, but it just did not work out. =20 > Anyway, that is behind us and let us get going with some=20 > energy so we can finish the work and close MSEC soon. >=20 > We have a lot to do and I would like MSEC to stop meeting=20 > after Chicago, if all goes well. I have scheduled time for=20 > us in Prague, so please plan for it accordingly. >=20 > That out of the way, we have the following drafts at the WG=20 > completion or near completion stage: >=20 > I. > MIKEY-applicability: Has finished last call and I will be=20 > forwarding it to Russ shortly. >=20 > II. > ECC: Are we ready to do a WG last call on this? > MSEC-IPsec : Same question: Are we ready to do WGLC? > GDOI-Update: Ditto >=20 > Did I miss any from that category? >=20 > III. > We desperately need to finish the following drafts ASAP: > GKDP: >=20 > IV. > TESLA-ALC-NORM: What is the status on this? > draft-ietf-msec-ipsec-composite-group: Ditto! >=20 > V. > New work (to be adopted after asking for group's opinion): > GDOI-SRTP: My opinion is that it is a good idea to have=20 > draft-baugher-msec-gdoi-srtp taken up as a WG item. I will=20 > ask group opinion on this today. > TESLA-IPsec: Ditto (Note: I wrote it, but I am merely an=20 > editor trying to finish the work; the original authors,=20 > except for Ran are not active in the group any longer. This=20 > is a gap filling exercise anyway, so I feel comfortable that=20 > there are no conflicts of interest here. I will ask the=20 > group of course). > draft-weis-esp-group-counter-cipher-00: Ditto. >=20 > Again, let me know if I missed anything? >=20 >=20 > Thanks for your patience folks. Let's get some work done. >=20 > best regards, > Lakshminath >=20 > _______________________________________________ > MSEC mailing list > MSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/msec >=20 _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Tue Jan 30 09:09:54 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBtfl-00089i-LR; Tue, 30 Jan 2007 09:09:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBtfk-00088i-Og for msec@ietf.org; Tue, 30 Jan 2007 09:09:20 -0500 Received: from mx-serv.inrialpes.fr ([194.199.18.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBtcD-0001jv-1H for msec@ietf.org; Tue, 30 Jan 2007 09:05:42 -0500 Received: from vilnius.inrialpes.fr (vilnius.inrialpes.fr [194.199.18.81]) by mx-serv.inrialpes.fr (8.13.6/8.13.0) with ESMTP id l0UE5Hjw025504; Tue, 30 Jan 2007 15:05:18 +0100 (MET) Received: from [194.199.24.115] (ornon.inrialpes.fr [194.199.24.115]) by vilnius.inrialpes.fr (8.13.6/8.11.3/ImagV2) with ESMTP id l0UE5GNW012759; Tue, 30 Jan 2007 15:05:16 +0100 (MET) Message-ID: <45BF509D.2000305@inrialpes.fr> Date: Tue, 30 Jan 2007 15:05:17 +0100 From: Vincent Roca User-Agent: Thunderbird 1.5.0.9 (X11/20070103) MIME-Version: 1.0 To: Lakshminath Dondeti Subject: Re: [MSEC] MSEC status update References: <45BEA3BB.50001@qualcomm.com> In-Reply-To: <45BEA3BB.50001@qualcomm.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mx-serv.inrialpes.fr [194.199.18.100]); Tue, 30 Jan 2007 15:05:18 +0100 (MET) X-mx-serv-inrialpes-fr-MailScanner-Information: Please contact postmaster@inrialpes.fr for more information X-mx-serv-inrialpes-fr-MailScanner: Found to be clean X-mx-serv-inrialpes-fr-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=0, requis 5) X-mx-serv-inrialpes-fr-MailScanner-From: vincent.roca@inrialpes.fr X-Spam-Status: No X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: msec@ietf.org X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hello Lakshminath and al. > IV. > TESLA-ALC-NORM: What is the status on this? We are actively working on an update, that will hopefully be close to final. Cheers, Vincent _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Tue Jan 30 09:09:54 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBtfl-00089i-LR; Tue, 30 Jan 2007 09:09:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBtfk-00088i-Og for msec@ietf.org; Tue, 30 Jan 2007 09:09:20 -0500 Received: from mx-serv.inrialpes.fr ([194.199.18.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBtcD-0001jv-1H for msec@ietf.org; Tue, 30 Jan 2007 09:05:42 -0500 Received: from vilnius.inrialpes.fr (vilnius.inrialpes.fr [194.199.18.81]) by mx-serv.inrialpes.fr (8.13.6/8.13.0) with ESMTP id l0UE5Hjw025504; Tue, 30 Jan 2007 15:05:18 +0100 (MET) Received: from [194.199.24.115] (ornon.inrialpes.fr [194.199.24.115]) by vilnius.inrialpes.fr (8.13.6/8.11.3/ImagV2) with ESMTP id l0UE5GNW012759; Tue, 30 Jan 2007 15:05:16 +0100 (MET) Message-ID: <45BF509D.2000305@inrialpes.fr> Date: Tue, 30 Jan 2007 15:05:17 +0100 From: Vincent Roca User-Agent: Thunderbird 1.5.0.9 (X11/20070103) MIME-Version: 1.0 To: Lakshminath Dondeti Subject: Re: [MSEC] MSEC status update References: <45BEA3BB.50001@qualcomm.com> In-Reply-To: <45BEA3BB.50001@qualcomm.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mx-serv.inrialpes.fr [194.199.18.100]); Tue, 30 Jan 2007 15:05:18 +0100 (MET) X-mx-serv-inrialpes-fr-MailScanner-Information: Please contact postmaster@inrialpes.fr for more information X-mx-serv-inrialpes-fr-MailScanner: Found to be clean X-mx-serv-inrialpes-fr-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=0, requis 5) X-mx-serv-inrialpes-fr-MailScanner-From: vincent.roca@inrialpes.fr X-Spam-Status: No X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: msec@ietf.org X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org Hello Lakshminath and al. > IV. > TESLA-ALC-NORM: What is the status on this? We are actively working on an update, that will hopefully be close to final. Cheers, Vincent _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Tue Jan 30 20:51:05 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC4cI-0002zM-HG; Tue, 30 Jan 2007 20:50:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC4cH-0002z1-Hn for msec@ietf.org; Tue, 30 Jan 2007 20:50:29 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HC4c8-0005h8-7C for msec@ietf.org; Tue, 30 Jan 2007 20:50:29 -0500 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0V1oIZX032073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 30 Jan 2007 17:50:19 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0V1oH0A017911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 30 Jan 2007 17:50:18 -0800 (PST) Message-ID: <45BFF590.4060200@qualcomm.com> Date: Tue, 30 Jan 2007 17:49:04 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Subject: [MSEC] [Fwd: Re: Any objections to adopting CTR mode draft as a WG item?] X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org -------- Original Message -------- Subject: Re: Any objections to adopting CTR mode draft as a WG item? Date: Tue, 30 Jan 2007 20:30:04 -0500 From: Russ Housley To: Lakshminath Dondeti , msec@ietf.org References: <45BEA651.3040206@qualcomm.com> I do not think that a recharter is needed to work on this document of the MSEC WG chooses to do so. Russ At 08:58 PM 1/29/2007, Lakshminath Dondeti wrote: >Folks, > >draft-weis-esp-group-counter-cipher-00 was presented at San Diego >and was discussed at length. One could argue that this is out of >scope for our charter, although the charter does not explicitly >disallow multi-sender operation (here is the relevant line from the >charter: "Initial efforts will focus on scalable solutions for >groups with a single source and a very large number of recipients. >" Ok, we have been at this for some 7 years and can no longer claim >to be in initial stages, but you know what I mean.). > >At the meeting 6 people thought this should be a work item and no >one objected. Any thoughts? > >Russ, could you tell us if we can do this without rechartering? > >thanks, >Lakshminath > _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec From msec-bounces@ietf.org Tue Jan 30 20:51:05 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC4cI-0002zM-HG; Tue, 30 Jan 2007 20:50:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC4cH-0002z1-Hn for msec@ietf.org; Tue, 30 Jan 2007 20:50:29 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HC4c8-0005h8-7C for msec@ietf.org; Tue, 30 Jan 2007 20:50:29 -0500 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0V1oIZX032073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 30 Jan 2007 17:50:19 -0800 Received: from [129.46.173.183] (ldondeti.na.qualcomm.com [129.46.173.183]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0V1oH0A017911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 30 Jan 2007 17:50:18 -0800 (PST) Message-ID: <45BFF590.4060200@qualcomm.com> Date: Tue, 30 Jan 2007 17:49:04 -0800 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: msec@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Subject: [MSEC] [Fwd: Re: Any objections to adopting CTR mode draft as a WG item?] X-BeenThere: msec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast Security List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: msec-bounces@ietf.org -------- Original Message -------- Subject: Re: Any objections to adopting CTR mode draft as a WG item? Date: Tue, 30 Jan 2007 20:30:04 -0500 From: Russ Housley To: Lakshminath Dondeti , msec@ietf.org References: <45BEA651.3040206@qualcomm.com> I do not think that a recharter is needed to work on this document of the MSEC WG chooses to do so. Russ At 08:58 PM 1/29/2007, Lakshminath Dondeti wrote: >Folks, > >draft-weis-esp-group-counter-cipher-00 was presented at San Diego >and was discussed at length. One could argue that this is out of >scope for our charter, although the charter does not explicitly >disallow multi-sender operation (here is the relevant line from the >charter: "Initial efforts will focus on scalable solutions for >groups with a single source and a very large number of recipients. >" Ok, we have been at this for some 7 years and can no longer claim >to be in initial stages, but you know what I mean.). > >At the meeting 6 people thought this should be a work item and no >one objected. Any thoughts? > >Russ, could you tell us if we can do this without rechartering? > >thanks, >Lakshminath > _______________________________________________ MSEC mailing list MSEC@ietf.org https://www1.ietf.org/mailman/listinfo/msec