[Isms] ISMS solution seslection procedure
Juergen Quittek <quittek@netlab.nec.de> Thu, 23 September 2004 15:49 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24725; Thu, 23 Sep 2004 11:49:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAVxc-0002XI-HR; Thu, 23 Sep 2004 11:56:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAVmT-0002Y1-E0; Thu, 23 Sep 2004 11:45:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAVRZ-0007ad-Vb for isms@megatron.ietf.org; Thu, 23 Sep 2004 11:23:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22612 for <isms@ietf.org>; Thu, 23 Sep 2004 11:23:35 -0400 (EDT)
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAVYM-0001x6-7Z for isms@ietf.org; Thu, 23 Sep 2004 11:30:40 -0400
Received: from [10.1.1.171] (dummy.netlab.nec.de [195.37.70.40]) by kyoto.netlab.nec.de (Postfix) with ESMTP id A5E861BAC4D; Thu, 23 Sep 2004 17:23:00 +0200 (CEST)
Date: Thu, 23 Sep 2004 17:23:00 +0200
From: Juergen Quittek <quittek@netlab.nec.de>
To: isms@ietf.org
Message-ID: <1171138004.1095960180@[10.1.1.171]>
X-Mailer: Mulberry/3.0.3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Subject: [Isms] ISMS solution seslection procedure
X-BeenThere: isms@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/isms>
List-Post: <mailto:isms@lists.ietf.org>
List-Help: <mailto:isms-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@lists.ietf.org?subject=subscribe>
Sender: isms-bounces@ietf.org
Errors-To: isms-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Dear all, Welcome to the ISMS working group! We have a very ambitious schedule and need to start discussing how we want to achieve our goal in time. Our major objective is selecting a solution for integrating SNMP with a security infrastructure as described in the charter. The charter also defines a submission deadline for solutions, but it does not specify the selection process. This message is a first step towards an agreement on the selection process. Basically, we have to evaluate all submitted solutions and then select one. For the evaluation we need a list of evaluation criteria and evaluators. Wes already spent a lot of time on identifying criteria/requirements. We should start with his list and discuss it on a separate email thread. Concerning the evaluators it can be useful to have a look at other WGs. Similar selections were made in the SEAMOBY, IPFIX and MIDCOM WGs. In the SEAMOBY WG the chairs evaluated proposed solutions, in the IPFIX and MIDCOM WGs an evaluations team performed this task. Since SEAMOBY decision ended up in a disaster (shutting down the entire work item at the IETF) it might be a good idea to go the way of IPFIX and MIDCOM where the decisions went reasonably well. Of course we are free to go our own way and our experiences may be completely different from the ones made in SEAMOBY, IPFIX and MIDCOM. So, please give us your opinion on the evaluators. Do you prefer - the WG chairs - an evaluation team - others ??? The evaluators should prepare a written evaluation and give a recommendation. Preferably the evaluation and recommendation should be available as an Internet draft, see for example <http://www.watersprings.org/pub/id/draft-ietf-seamoby-paging-protocol-assessment-01.txt> <http://www.ietf.org/internet-drafts/draft-leinen-ipfix-eval-contrib-03.txt> <http://www.ietf.org/internet-drafts/draft-ietf-midcom-protocol-eval-06.txt>. Ideally, a first version of this draft (containing the final list of evaluation criteria, but probably not yet any evaluation) would already be posted by the deadline for submitting solutions. Then we need to hurry to get to a recommendation in November. Please send any comment, suggestion, opinion on the selection procedure. And since little time is left, please send it rather soon than late. Thanks, Ken and Juergen _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms
- Re: [Isms] ISMS solution seslection procedure Kaushik Narayan
- [Isms] ISMS solution seslection procedure Juergen Quittek
- RE: [Isms] ISMS solution seslection procedure Nelson, David
- RE: [Isms] ISMS solution seslection procedure David B Harrington
- RE: [Isms] ISMS solution seslection procedure Chris Elliott
- Re: [Isms] ISMS solution seslection procedure Wes Hardaker
- RE: [Isms] ISMS solution seslection procedure David B Harrington
- Re: [Isms] ISMS solution seslection procedure Wes Hardaker
- Re: [Isms] ISMS solution seslection procedure Ken Hornstein
- Re: [Isms] ISMS solution selection procedure David T. Perkins