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

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Mon, 28 January 2008 12:31 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 1JJT8q-0007uh-L7; Mon, 28 Jan 2008 07:31:12 -0500
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1JJT8o-0007uc-Vc for tsvwg-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 07:31:10 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJT8o-0007uU-LG for tsvwg@ietf.org; Mon, 28 Jan 2008 07:31:10 -0500
Received: from mail.gmx.net ([213.165.64.20]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JJT8n-0002B5-U6 for tsvwg@ietf.org; Mon, 28 Jan 2008 07:31:10 -0500
Received: (qmail invoked by alias); 28 Jan 2008 12:31:08 -0000
Received: from proxy3-nsn.nsn-inter.net (EHLO [217.115.75.231]) [217.115.75.231] by mail.gmx.net (mp008) with SMTP; 28 Jan 2008 13:31:08 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+NR1UVW4eNT2niuFoqVkRszc2/dcTZTxYFwol3AF 5VJO5MOntFAZtk
Message-ID: <479DCB0F.4060408@gmx.net>
Date: Mon, 28 Jan 2008 14:31:11 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Melinda Shore <mshore@cisco.com>
Subject: Re: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
References: <C3C3336F.31EF0%mshore@cisco.com>
In-Reply-To: <C3C3336F.31EF0%mshore@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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

Hi Melinda,

Melinda Shore wrote:
> On 1/28/08 4:59 AM, "Francois Le Faucheur IMAP" <flefauch@cisco.com> wrote:
>   
>> This could, for example, be easily achieved with small extensions to
>> GDOI (draft-weis-gdoi-for-rsvp), but a solution will only be defined
>> in IETF (e.g. by MSEC) if the corresponding need is established by
>> the TSVWG.
>>     
>
> I'd like to add that there's some pent-up pool of
> GDOI profiles, at least one member of which is waiting
> to see what happens with the RSVP profile and what MSEC
> decides to do.
>
> I do think that this is an enormously useful approach
> for when peers cannot be known in advance and PKI is
> unavailable or otherwise not attractive.
>
>   
How many other alternatives have you considered?

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

Ciao
Hannes

> Melinda
>
>
>