Re: [MSEC] RSVP keying ... any updates?

Brian Weis <bew@cisco.com> Tue, 19 February 2008 01:18 UTC

Return-Path: <msec-bounces@ietf.org>
X-Original-To: ietfarch-msec-archive@core3.amsl.com
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 55FAC28C47F; Mon, 18 Feb 2008 17:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.28
X-Spam-Level:
X-Spam-Status: No, score=-1.28 tagged_above=-999 required=5 tests=[AWL=-2.237, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, SARE_MULT_VIA_CITIZNET=1.394]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHZwup8wEEYk; Mon, 18 Feb 2008 17:18:55 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10B943A6DAC; Mon, 18 Feb 2008 17:18:52 -0800 (PST)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F6BD3A6DAA for <msec@core3.amsl.com>; Mon, 18 Feb 2008 17:18:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hZ9HqhfDs+BM for <msec@core3.amsl.com>; Mon, 18 Feb 2008 17:18:50 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 761E13A6DAC for <msec@ietf.org>; Mon, 18 Feb 2008 17:18:50 -0800 (PST)
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 18 Feb 2008 17:18:48 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m1J1Il3P024671; Mon, 18 Feb 2008 17:18:47 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1J1IJK0017298; Tue, 19 Feb 2008 01:18:46 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Feb 2008 17:18:35 -0800
Received: from [128.107.112.225] ([128.107.112.225]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Feb 2008 17:18:35 -0800
In-Reply-To: <47A76B9B.5020106@qualcomm.com>
References: <47A76B9B.5020106@qualcomm.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <34FC58CC-D41D-40D2-9245-0A840EEDCDD4@cisco.com>
From: Brian Weis <bew@cisco.com>
Date: Mon, 18 Feb 2008 17:19:01 -0800
To: Lakshminath Dondeti <ldondeti@qualcomm.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 19 Feb 2008 01:18:35.0134 (UTC) FILETIME=[5924D9E0:01C87295]
Authentication-Results: sj-dkim-4; header.From=bew@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: msec@ietf.org
Subject: Re: [MSEC] RSVP keying ... any updates?
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

Hi Lakshminath,

On Feb 4, 2008, at 11:46 AM, Lakshminath Dondeti wrote:

> Hi all,
>
> I have asked for a slot for MSEC in Philly.  One of the topics I  
> want us
> to figure out the next steps on is the RSVP keying.  But, I would like
> to have that discussion happen before we get to Philly.  Let us use  
> the
> face-to-face time to resolve any snags and not for tutorials (I would
> need one, but I can do that offline with the authors :) ).
>
> I have been told that there was a discussion on the TSV list.  I am
> going to try and read up on that soon.

The conclusion of the TSV discussion is here:
	<http://www.ietf.org/mail-archive/web/tsvwg/current/msg08172.html>
The short of it is that draft-behringer-tsvwg-rsvp-security- 
groupkeying is authorized to become a TSVWG WG draft (targeted as an  
Informational RFC). I believe this is the action you were gating any  
MSEC WG work on keying for RSVP. Would you agree to go forward with  
the GDOI work described in draft-weis-gdoi-for-rsvp?

If so, the suggestion was made in Vancouver to transmogrify weis-gdoi- 
for-rsvp into a more general document for distributing integrity keys  
used for routing and signaling protocols such as RSVP. I think this  
would be reasonably straightforward, and would like to consider such  
a document as an MSEC WG document. If the WG agrees, I would be happy  
to present it at the Philadelphia MSEC meeting.

Thanks,
Brian

> While we are on topic, any other items?
>
> thanks,
> Lakshminath
> _______________________________________________
> MSEC mailing list
> MSEC@ietf.org
> http://www.ietf.org/mailman/listinfo/msec

-- 
Brian Weis
Advanced Security Development, Security Technology Group, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com

_______________________________________________
MSEC mailing list
MSEC@ietf.org
http://www.ietf.org/mailman/listinfo/msec