IETF Logo Mail Archive

RE: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?

"Kantawala, Anshul" <anshul.kantawala@lmco.com> Thu, 24 January 2008 15:33 UTC

Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI45D-0000lk-IK; Thu, 24 Jan 2008 10:33:39 -0500
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1JI45C-0000fy-L6 for tsvwg-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 10:33:38 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI45C-0000fg-9m for tsvwg@ietf.org; Thu, 24 Jan 2008 10:33:38 -0500
Received: from mailgw1a.lmco.com ([192.31.106.7]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JI45B-0008Bb-SR for tsvwg@ietf.org; Thu, 24 Jan 2008 10:33:38 -0500
Received: from emss02g01.ems.lmco.com (relay2.ems.lmco.com [166.29.2.54])by mailgw1a.lmco.com (LM-6) with ESMTP id m0OFWBnb018001for <tsvwg@ietf.org>; Thu, 24 Jan 2008 08:32:31 -0700 (MST)
Received: from CONVERSION2-DAEMON.lmco.com by lmco.com (PMDF V6.3-x14 #31428) id <0JV500A01MPSFO@lmco.com> for tsvwg@ietf.org; Thu, 24 Jan 2008 08:22:40 -0700 (MST)
Received: from EMSS09I00.us.lmco.com ([158.183.26.31]) by lmco.com (PMDF V6.3-x14 #31428) with ESMTP id <0JV5006IRMPIMH@lmco.com> for tsvwg@ietf.org; Thu, 24 Jan 2008 08:22:30 -0700 (MST)
Received: from EMSS09M03.us.lmco.com ([158.183.26.17]) by EMSS09I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 24 Jan 2008 10:21:47 -0500
Date: Thu, 24 Jan 2008 10:21:48 -0500
From: "Kantawala, Anshul" <anshul.kantawala@lmco.com>
Subject: RE: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
In-reply-to: <47974BDB.70406@ericsson.com>
To: tsvwg <tsvwg@ietf.org>
Message-id: <A55DB203FF9BCF478586DB2350863864158F1ED5@emss09m03.us.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-Topic: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
Thread-Index: AchdympHWgUnRBrUT7qfy5PTKHB6WwA0kLhw
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <47974BDB.70406@ericsson.com>
X-OriginalArrivalTime: 24 Jan 2008 15:21:47.0569 (UTC) FILETIME=[D5D84A10:01C85E9C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi,
I support making this draft a WG document.

Anshul Kantawala

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com] 
Sent: Wednesday, January 23, 2008 9:15 AM
To: tsvwg
Subject: [Tsvwg] Adopting
draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?

Hi,

At the meeting "Applicability of Keying Methods for RSVP Security"
(draft-behringer-tsvwg-rsvp-security-groupkeying-01) was presented. It 
seemed to be quite a lot of support for having TSVWG develop an 
Informative document on RSVP Group keying. Thus the question to the WG 
is; Should TSVWG adopt 
draft-behringer-tsvwg-rsvp-security-groupkeying-01 as an basis for a WG 
item?

Best Regards

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email