RE: [MSEC] MSEC status update

Liu Ya <liuya@huawei.com> Tue, 30 January 2007 02:48 UTC

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 <liuya@huawei.com>
Subject: RE: [MSEC] MSEC status update
In-reply-to: <45BEA3BB.50001@qualcomm.com>
To: 'Lakshminath Dondeti' <ldondeti@qualcomm.com>
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 <msec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=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