[midcom] RE: SNMPv3 as MIDCOM protocol: Opinions?

"Harrington, David" <dbh@enterasys.com> Thu, 05 December 2002 17:07 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19966 for <midcom-archive@odin.ietf.org>; Thu, 5 Dec 2002 12:07:10 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB5H9Yn07031 for midcom-archive@odin.ietf.org; Thu, 5 Dec 2002 12:09:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB5H95v06995; Thu, 5 Dec 2002 12:09:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB5GtOv05310 for <midcom@optimus.ietf.org>; Thu, 5 Dec 2002 11:55:24 -0500
Received: from ctron-dnm.enterasys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19263 for <midcom@ietf.org>; Thu, 5 Dec 2002 11:52:29 -0500 (EST)
Received: (from uucp@localhost) by ctron-dnm.enterasys.com (8.8.7/8.8.7) id MAA16328 for <midcom@ietf.org>; Thu, 5 Dec 2002 12:07:28 -0500 (EST)
Received: from unknown(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1) id xma016267; Thu, 5 Dec 02 12:06:29 -0500
Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2.ets.enterasys.com with InterScan Messaging Security Suite for SMTP; Thu, 05 Dec 2002 11:54:25 -0500
Received: from nhrocmbx1.enterasys.com ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.4905); Thu, 5 Dec 2002 11:54:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Thu, 05 Dec 2002 11:54:24 -0500
Message-ID: <6D745637A7E0F94DA070743C55CDA9BA075902@NHROCMBX1.ets.enterasys.com>
Thread-Topic: SNMPv3 as MIDCOM protocol: Opinions?
Thread-Index: AcKcd3gasIwE3Qb4ShKmRbUmu45JugABdorg
From: "Harrington, David" <dbh@enterasys.com>
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>, Martin.Stiemerling@ccrle.nec.de
Cc: snmpv3@lists.tislabs.com, midcom@ietf.org
X-OriginalArrivalTime: 05 Dec 2002 16:54:25.0077 (UTC) FILETIME=[F76DB650:01C29C7E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gB5GtOv05311
Subject: [midcom] RE: SNMPv3 as MIDCOM protocol: Opinions?
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi,

Message #1: As SNMPv3 co-chair.

Let me inform the SNMPv3 working about the fact that SNMP has been proposed as a candidate for the Middlebox Communications protocol. This has been mentioned on the mailing list in the past.

RFC3303 and 3304 describe the MIDCOM architecture and requirements.

The evaluation is being done against a checklist of requirements specified in RFC3304.
An evaluation of SNMPv3 versus MIDCOM requirements, done by Juergen Quittek and I, can be found in draft-ietf-midcom-protocol-eval-06.txt.

Juergen did an earlier evaluation of SNMP (all versions) in draft-quittek-midcom-snmp-eval-00.txt

It would be helpful if the people in the WG reviewed the requirements and analyses and contributed any comments to the process.

---
David Harrington            
dbh@enterasys.com           
co-chair, IETF SNMPv3 WG


> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
> Sent: Thursday, December 05, 2002 10:18 AM
> To: Martin.Stiemerling@ccrle.nec.de
> Cc: snmpv3@lists.tislabs.com; midcom@ietf.org
> Subject: Re: SNMPv3 as MIDCOM protocol: Opinions?
> 
> 
> 
> >>>>> Martin Stiemerling writes:
> 
> Martin> as you may have heard: the MIDCOM WG is currently doing a
> Martin> protocol evaluation which protocol to use as the MIDCOM
> Martin> protocol. SNMPv3 is amongst these candidates (diameter,
> Martin> cops(-pr), megaco).  Would you strongly recommend to use
> Martin> SNMPv3 as the MIDCOM protocol without having a bad feeling?
> 
> Feeling is one dimension in a multi-dimensional space. And we all know
> that SNMP has a reputation which is kind of special.
> 
> Anyway, it usually makes sense to also look at the functional
> requirements and the features offered by a protocol if you are not
> completely driven by feelings. Are the MIDCOM requirements spelled out
> somewhere?
> 
> /js
> 
> -- 
> Juergen Schoenwaelder    
> <http://www.informatik.uni-osnabrueck.de/schoenw/>
> 
> 
> 
_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom