Re: [Isms] ISMS solution seslection procedure

Kaushik Narayan <kaushik@cisco.com> Thu, 23 September 2004 19:10 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 PAA12164; Thu, 23 Sep 2004 15:10:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAZ66-0007NN-CI; Thu, 23 Sep 2004 15:17:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAYoz-0006bC-0c; Thu, 23 Sep 2004 15:00:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAYcZ-0003FE-J3 for isms@megatron.ietf.org; Thu, 23 Sep 2004 14:47:11 -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 OAA09317 for <isms@ietf.org>; Thu, 23 Sep 2004 14:47:09 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAYjO-0006kG-D2 for isms@ietf.org; Thu, 23 Sep 2004 14:54:15 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 23 Sep 2004 11:57:48 +0000
X-BrightmailFiltered: true
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i8NIjHwr011453; Thu, 23 Sep 2004 11:45:21 -0700 (PDT)
Received: from kaushik-w2k02.cisco.com (dhcp-171-71-255-89.cisco.com [171.71.255.89]) by mira-sjc5-a.cisco.com (MOS 3.4.5-GR) with ESMTP id AUD91232; Thu, 23 Sep 2004 11:44:45 -0700 (PDT)
Message-Id: <6.0.0.22.0.20040923113759.06008310@mira-sjc5-a.cisco.com>
X-Sender: kaushik@mira-sjc5-a.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Thu, 23 Sep 2004 11:45:17 -0700
To: Juergen Quittek <quittek@netlab.nec.de>
From: Kaushik Narayan <kaushik@cisco.com>
Subject: Re: [Isms] ISMS solution seslection procedure
In-Reply-To: <1171138004.1095960180@[10.1.1.171]>
References: <1171138004.1095960180@[10.1.1.171]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: isms@ietf.org
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: d8ae4fd88fcaf47c1a71c804d04f413d

I prefer an evaluation team.


At 08:23 AM 9/23/2004, Juergen Quittek wrote:
>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


_______________________________________________
Isms mailing list
Isms@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/isms