IETF Logo Mail Archive

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

Lars Eggert <lars.eggert@nokia.com> Wed, 30 January 2008 15:30 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 1JKEtX-0000MM-7J; Wed, 30 Jan 2008 10:30:35 -0500
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1JKEtW-0000MH-Ob for tsvwg-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 10:30:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKEtW-0000M9-Et for tsvwg@ietf.org; Wed, 30 Jan 2008 10:30:34 -0500
Received: from smtp.nokia.com ([192.100.105.134] helo=mgw-mx09.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKEtW-0007I9-5c for tsvwg@ietf.org; Wed, 30 Jan 2008 10:30:34 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m0UFVR4D025146; Wed, 30 Jan 2008 09:31:30 -0600
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 Jan 2008 17:30:12 +0200
Received: from esdhcp035248.research.nokia.com ([172.21.35.248]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 Jan 2008 17:30:11 +0200
Message-Id: <C5FC511D-BC4A-42F0-BFB1-7230CAC79B6A@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Francois Le Faucheur IMAP <flefauch@cisco.com>
In-Reply-To: <D110EE81-74ED-407A-A781-E7A08C80EB51@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
Date: Wed, 30 Jan 2008 17:30:09 +0200
References: <47974BDB.70406@ericsson.com> <CD8D57B6-EB94-4DCE-A42A-02BC5F573A13@nokia.com> <7A1BB0E8-5EFB-4341-918A-F841DB1B57FF@cisco.com> <A268781D-F81A-48B3-8042-1892AC93B749@nokia.com> <E603EB77-B600-4A73-9217-EB797A5D7AAB@cisco.com> <E119D886-0838-4323-ABD7-0C8CCAE5C7A3@nokia.com> <668A8CDF-038D-490A-93A2-B5B71B186ADC@cisco.com> <EA366CF1-8D57-4DAC-8743-E9870F1E71F1@nokia.com> <D110EE81-74ED-407A-A781-E7A08C80EB51@cisco.com>
X-Mailer: Apple Mail (2.915)
X-OriginalArrivalTime: 30 Jan 2008 15:30:11.0906 (UTC) FILETIME=[00EE8220:01C86355]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ext Magnus Westerlund <magnus.westerlund@ericsson.com>, RJ Atkinson <rja@extremenetworks.com>, tsvwg list IETF <tsvwg@ietf.org>
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

On 2008-1-30, at 17:06, ext Francois Le Faucheur IMAP wrote:
> Why is it so important to ensure that the TSVWG does not send any  
> indication to MSEC that it would be useful to deploy a group keying  
> solution for RSVP?

A successful consensus call to adopt draft-behringer with the goal of  
publishing it as an Informational RFC simply does not have the side  
effect of indicating to MSEC or anyone else that TSVWG recommends  
draft-weis.

Lars

> Is this because you know of better solutions to achieve automated  
> key management for RSVP?
> If yes, can you share them so that we can discuss those?
> If not, what exactly would be so bad if TSVWG was to document the  
> fact that group keying would be useful for RSVP and if MSEC was to  
> interpret that as a cue to develop a solution for it?

v2.23.0 | Report a Bug | By Email