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

ken carlberg <carlberg@g11.org.uk> Tue, 29 January 2008 18:15 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 1JJuzk-0003s3-Jt; Tue, 29 Jan 2008 13:15:40 -0500
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1JJuzj-0003ry-VI for tsvwg-confirm+ok@megatron.ietf.org; Tue, 29 Jan 2008 13:15:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJuzj-0003rq-LI for tsvwg@ietf.org; Tue, 29 Jan 2008 13:15:39 -0500
Received: from qmta06.emeryville.ca.mail.comcast.net ([76.96.30.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJuzi-0007JG-5h for tsvwg@ietf.org; Tue, 29 Jan 2008 13:15:39 -0500
Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by QMTA06.emeryville.ca.mail.comcast.net with comcast id j1oo1Y00M0mlR8U0A0NH00; Tue, 29 Jan 2008 18:15:37 +0000
Received: from [192.168.1.120] ([68.33.242.22]) by OMTA11.emeryville.ca.mail.comcast.net with comcast id j6Fb1Y00N0ViFGL8X00000; Tue, 29 Jan 2008 18:15:37 +0000
X-Authority-Analysis: v=1.0 c=1 a=5wdjpoFPGtcA:10 a=tuv82GU5MHP1ZoOJEZ4A:9 a=qRghtZ7AtsFBUYAh_WJkp1e6hCMA:4 a=WuK_CZDBSqoA:10
Message-Id: <192D8F15-2860-4F90-A042-58EEE917ACA5@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
To: Brian Weis <bew@cisco.com>
In-Reply-To: <D2813B59-D4EA-474C-AC31-FF6B86BF8294@cisco.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: Tue, 29 Jan 2008 13:15:35 -0500
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> <D2813B59-D4EA-474C-AC31-FF6B86BF8294@cisco.com>
X-Mailer: Apple Mail (2.915)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: ext Magnus Westerlund <magnus.westerlund@ericsson.com>, RJ Atkinson <rja@extremenetworks.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 Jan 29, 2008, at 12:25 PM, Brian Weis wrote:

> On the other hand, rejecting it sends a message to MSEC that the use  
> of group security isn't particularly valuable for RSVP and so there  
> isn't much point in doing addition protocol work to make the group  
> security model more secure.

i think that's reading to much into the original question of whether  
the document should be a working group item or an individual submission.

my feeling is that part of the on-line discussion has drifted away  
from a more fundamental question of whether or not the draft document  
is one that requires _group_ consensus.  Put another way, do the  
authors feel the perspectives/issues brought up on this thread foster  
a need to add or change existing text?  Or, do the authors (chairs, or  
others) feel that the document speaks for itself and can be sidelined  
and weakened by issues raised by others?  if the former, then it  
should be a wg item.  if the latter, then it should stay as an  
individual submission.  And keep in mind, an individual submission is  
still constructive and reference point for the community.

My personal opinion is that the document would benefit from consensus  
input given the points raised by others on this thread.  But if the  
authors feel changes will dilute the current points made in the  
document, then it should stay an individual submission.

-ken