Re: [MSEC] MSEC status update

Lakshminath Dondeti <ldondeti@qualcomm.com> Tue, 30 January 2007 03:03 UTC

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 <ldondeti@qualcomm.com>
User-Agent: Thunderbird 2.0b2 (Windows/20070116)
MIME-Version: 1.0
To: Liu Ya <liuya@huawei.com>
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 <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,

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