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

RJ Atkinson <rja@extremenetworks.com> Mon, 28 January 2008 13:54 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 1JJURs-0006b2-BU; Mon, 28 Jan 2008 08:54:56 -0500
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1JJURr-0006ax-7M for tsvwg-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 08:54:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJURq-0006ap-TK for tsvwg@ietf.org; Mon, 28 Jan 2008 08:54:54 -0500
Received: from eastrmmtao107.cox.net ([68.230.240.59]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJURq-0004Na-H9 for tsvwg@ietf.org; Mon, 28 Jan 2008 08:54:54 -0500
Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmmtao107.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20080128135452.SCSJ8815.eastrmmtao107.cox.net@eastrmimpo02.cox.net>; Mon, 28 Jan 2008 08:54:52 -0500
Received: from [10.30.20.71] ([68.10.117.240]) by eastrmimpo02.cox.net with bizsmtp id idu51Y00B5BGrj00000000; Mon, 28 Jan 2008 08:54:06 -0500
From: RJ Atkinson <rja@extremenetworks.com>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
In-Reply-To: <479DCB0F.4060408@gmx.net>
Subject: Re: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
References: <C3C3336F.31EF0%mshore@cisco.com> <479DCB0F.4060408@gmx.net>
Message-Id: <7BE377EF-6FD1-4F95-81AB-CC22B8E71A75@extremenetworks.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Date: Mon, 28 Jan 2008 08:54:52 -0500
X-Mailer: Apple Mail (2.915)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ext Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg list IETF <tsvwg@ietf.org>, Melinda Shore <mshore@cisco.com>, Randall 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  28 Jan 2008, at 07:31, Hannes Tschofenig wrote:
> How many other alternatives have you considered?

I am not aware of any alternatives that would enable
scalable automated key management for RSVP.  At present,
there are zero standardised mechanisms for that purpose.

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

ISAKMP/IKE do not require a PKI.  In fact, many deployments
of ISAKMP/IKE with IPsec today do not use any sort of PKI.
(I use one quite regularly myself.)

So nothing on the table here would require a PKI or prohibit
use of a PKI.  In short, PKIs are not germane to the thread
at hand in any way obvious to me.

Yours,

Ran
rja@extremenetworks.com