IETF Logo Mail Archive

Re: [OPS-NM] RE: [MIB-DOCTORS] RE: SNMP MIBs and IETF standards trackwork

"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 08 November 2006 05:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ghfb7-0001IU-7o; Wed, 08 Nov 2006 00:03:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ghfb5-0001Gj-0i; Wed, 08 Nov 2006 00:03:35 -0500
Received: from elasmtp-junco.atl.sa.earthlink.net ([209.86.89.63]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ghfb2-0008Qm-M2; Wed, 08 Nov 2006 00:03:34 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=mq2Ka7qC62I5c06EaAYfsja0yEEwbklXzxLNiH9O8g8lRmHj3dYJzM5QwUbmPxlI; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.166.38.206] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1Ghfb0-00083D-G1; Wed, 08 Nov 2006 00:03:30 -0500
Message-ID: <009b01c702f3$4061acc0$6601a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ops-nm@ietf.org
References: <AAB4B3D3CF0F454F98272CBE187FDE2F0BB1A132@is0004avexu1.global.avaya.com>
Subject: Re: [OPS-NM] RE: [MIB-DOCTORS] RE: SNMP MIBs and IETF standards trackwork
Date: Tue, 07 Nov 2006 21:01:42 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888c29d63c4e37bdee6a7dfcdb59f90d5d90d5cfb0bedb10990350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.166.38.206
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: MIB Doctors <mib-doctors@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Hi -

> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: "David B Harrington" <dbharrington@comcast.net>; "Natale, Bob" <RNATALE@mitre.org>
> Cc: "MIB Doctors" <mib-doctors@ietf.org>; <ops-nm@ietf.org>
> Sent: Tuesday, November 07, 2006 11:13 AM
> Subject: [OPS-NM] RE: [MIB-DOCTORS] RE: SNMP MIBs and IETF standards trackwork
...
>  Some WGs consider that SNMP does not fit their requirements,
> especially for configuration operations. Mandating a MIB module and
> support for SNMP is not applicable in some cases and in other prevents a
> real discussion about manageability requirements. 
...

What protocol(s) and management information model(s) are these
WGs using?  Or are they just arguing that since SNMP and MIBs
aren't perfect, it's better to do nothing?

Randy


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm

v2.40.4 | Report a Bug | By Email | System Status