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

Melinda Shore <mshore@cisco.com> Mon, 28 January 2008 12:42 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 1JJTJr-0007Il-3T; Mon, 28 Jan 2008 07:42:35 -0500
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1JJTJq-0007Ig-68 for tsvwg-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 07:42:34 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJTJp-0007IY-RR for tsvwg@ietf.org; Mon, 28 Jan 2008 07:42:33 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJTJp-0002gp-HJ for tsvwg@ietf.org; Mon, 28 Jan 2008 07:42:33 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 28 Jan 2008 07:42:33 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m0SCgXTa004173; Mon, 28 Jan 2008 07:42:33 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m0SCgNJ1027448; Mon, 28 Jan 2008 12:42:32 GMT
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 Jan 2008 07:42:26 -0500
Received: from 10.86.115.68 ([10.86.115.68]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) with Microsoft Exchange Server HTTP-DAV ; Mon, 28 Jan 2008 12:42:26 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 28 Jan 2008 07:42:27 -0500
Subject: Re: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
From: Melinda Shore <mshore@cisco.com>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Message-ID: <C3C337E3.31EF5%mshore@cisco.com>
Thread-Topic: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
Thread-Index: Achhqzz0e17zf82eEdyrYwAKleNSdA==
In-Reply-To: <479DCB0F.4060408@gmx.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Jan 2008 12:42:26.0967 (UTC) FILETIME=[3CEF3270:01C861AB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1005; t=1201524153; x=1202388153; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mshore@cisco.com; z=From:=20Melinda=20Shore=20<mshore@cisco.com> |Subject:=20Re=3A=20[Tsvwg]=20Adopting=0A=20draft-behringer -tsvwg-rsvp-security-groupkeying=20as=20WG=20item? |Sender:=20 |To:=20Hannes=20Tschofenig=20<Hannes.Tschofenig@gmx.net>; bh=0Vx+uWTwljL9kWbGG8DDFWvrIaL5IyGzyqGkkuhfTV4=; b=VqcpY9uMQDIHj4jByuNrzKKt3kLffI4m8byOnraN90yRqK5D2Cu4UaCIWP TLOKpM7btN1y3pk8j1ej4c01B4BGudc1FVILDA3jb4b5f+poAT41L1MpuwYq warUsQa62C;
Authentication-Results: rtp-dkim-2; header.From=mshore@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ext Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg list IETF <tsvwg@ietf.org>, RJ Atkinson <rja@extremenetworks.com>, Brian Weis <bew@cisco.com>
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 1/28/08 7:31 AM, "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> wrote:
> How many other alternatives have you considered?

There weren't a lot of reasonable alternatives available.  For
us, a primary attraction is that group keys provide an
implicit authorization, which might not be as fine-grained
as we might like in an ideal world but goes beyond what's
available with other tools while doing it simply (no manual
keying, no Kerberos).  This is particularly useful for
keying a protocol which can carry multiple application-
types or to multiple communities inside the same administrative
domain.

> Btw, since a IKE DOI builds on IKE there might well be a PKI underneath.

Sure, but it's not the 'I' we're trying to avoid.

At any rate, I think it would be good if someone from TSVWG and
someone from MSEC sat down and hashed out how they'd like the
work to go forward, then brought the proposal to both groups.
It feels like this has been stalled out for awhile.

Melinda