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

Lars Eggert <lars.eggert@nokia.com> Wed, 30 January 2008 13:58 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 1JKDSR-0004p5-TC; Wed, 30 Jan 2008 08:58:31 -0500
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1JKDSQ-0004d4-5L for tsvwg-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 08:58:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKDSP-0004cb-RJ for tsvwg@ietf.org; Wed, 30 Jan 2008 08:58:29 -0500
Received: from smtp.nokia.com ([192.100.122.230] helo=mgw-mx03.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKDSP-0002ws-AH for tsvwg@ietf.org; Wed, 30 Jan 2008 08:58:29 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m0UDw4Vh008202; Wed, 30 Jan 2008 15:58:15 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 Jan 2008 15:57:43 +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 15:57:43 +0200
Message-Id: <86426C1B-2A34-4FC0-B5B0-96B30B430AEA@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <6BE1423F-7F69-4948-BD55-D103C07E7153@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)
Subject: Re: [Tsvwg] Adopting draft-behringer-tsvwg-rsvp-security-groupkeying as WG item?
Date: Wed, 30 Jan 2008 15:57:41 +0200
References: <47974BDB.70406@ericsson.com> <CD8D57B6-EB94-4DCE-A42A-02BC5F573A13@nokia.com> <7A1BB0E8-5EFB-4341-918A-F841DB1B57FF@cisco.com> <6BE1423F-7F69-4948-BD55-D103C07E7153@extremenetworks.com>
X-Mailer: Apple Mail (2.915)
X-OriginalArrivalTime: 30 Jan 2008 13:57:43.0305 (UTC) FILETIME=[15B52F90:01C86348]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 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

On 2008-1-28, at 15:47, ext RJ Atkinson wrote:
> On  28 Jan 2008, at 04:59, Francois Le Faucheur wrote:
>> On 24 Jan 2008, at 18:04, Lars Eggert wrote:
>>
>>> (individual hat on)
>>>
>>> I'm not convinced that this document needs to be a TSVWG document.  
>>> It's an Informational document that surveys group keying options  
>>> for RSVP, and as such could be published directly through the RFC  
>>> Editor.
>
> Lars,
>    Are you *objecting* to the document becoming a TSV WG
> informational document xor merely observing that multiple
> options on handling the draft exist in theory ?

The latter - I'm not convinced it needs to become a TSVWG document,  
but I also don't see a reason for it not to, *if* we're clear that  
this adoption does not motivate or request and solutions work elsewhere.

Lars