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

Francois Le Faucheur IMAP <flefauch@cisco.com> Wed, 30 January 2008 15:06 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 1JKEW6-0002bO-U4; Wed, 30 Jan 2008 10:06:22 -0500
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1JKEW5-0002bF-Ml for tsvwg-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 10:06:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKEW5-0002b6-CG for tsvwg@ietf.org; Wed, 30 Jan 2008 10:06:21 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKEW4-0005LT-MP for tsvwg@ietf.org; Wed, 30 Jan 2008 10:06:21 -0500
X-IronPort-AV: E=Sophos;i="4.25,277,1199660400"; d="scan'208";a="4401825"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 30 Jan 2008 16:06:12 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m0UF6B09030672; Wed, 30 Jan 2008 16:06:11 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m0UF5tlR017614; Wed, 30 Jan 2008 15:06:11 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 Jan 2008 16:06:07 +0100
Received: from [144.254.53.198] ([144.254.53.198]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 Jan 2008 16:06:06 +0100
In-Reply-To: <EA366CF1-8D57-4DAC-8743-E9870F1E71F1@nokia.com>
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>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <D110EE81-74ED-407A-A781-E7A08C80EB51@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
Date: Wed, 30 Jan 2008 16:06:02 +0100
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 30 Jan 2008 15:06:06.0747 (UTC) FILETIME=[A38CBEB0:01C86351]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2121; t=1201705571; x=1202569571; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco. com> |Subject:=20Re=3A=20[Tsvwg]=20Adopting=20draft-behringer-ts vwg-rsvp-security-groupkeying=20as=20WG=20item? |Sender:=20; bh=4+GQpoUXBvQX1h2YZBPN7El4f9nnF92IIKyrA80SgEA=; b=BPiPZdc5toxLxg2PKqe3OVsnRdPbrF7pXVUHdzSX35+hcChBA5/pNTtFFz Vxd7F2uAFrQe7jyST+OkAqXy54uwRjvNOOxmvFIUXy6/h5Zt8CkgGCmCEKeC re7aUUtirY;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: RJ Atkinson <rja@extremenetworks.com>, ext Magnus Westerlund <magnus.westerlund@ericsson.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

Hi Lars,

On 30 Jan 2008, at 15:08, Lars Eggert wrote:
>
>> Second, draft-behringer is not proposing to dictate what MSEC  
>> should or should not do. It is about documenting group keying  
>> applicability to RSVP and its benefits in some scenarios. The  
>> expectation is indeed that MSEC will find its own motivation to  
>> develop a solution based on the benefits it would bring to RSVP.  
>> That's all.
>
> Great. Because recalling the discussion in SAAG, I came away with a  
> different impression. The SAAG minutes say:
>
> "There was progress on four [MSEC - ed.] work items, including  
> crypto suites for
> GDOI, and extensions to GDOI for hash agility, GDOI for SRTP, and
> TESLA extensions.  There are also several current work items that
> are not making progress and may need to be dropped.  Some new work
> has been proposed to support keying for transport and routing
> protocols, but this work will not go forward unless it is clear that
> the appropriate WGs in transport and routing have consensus.
> If clear direction is provided, msec will consider a charter update  
> for
> new work.  Otherwise, msec will stay on course to complete its  
> active documents and shut down."
>
> The "support keying for transport" bit was about RSVP group keying  
> (draft-weis), and the half-sentence following it makes it pretty  
> clear that MSEC won't take it on unless TSVWG would indicate some  
> sort of consensus about this work. I'm merely attempting to clarify  
> that any adoption of draft-behringer isn't such an indication.
>


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?
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?

Thanks

Francois