IETF Logo Mail Archive

Re: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement for configurationby SNMP

"Randy Presuhn" <randy_presuhn@mindspring.com> Mon, 06 November 2006 19:14 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gh9va-0004Gt-30; Mon, 06 Nov 2006 14:14:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gh9nX-0000HB-W5; Mon, 06 Nov 2006 14:06:20 -0500
Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gh9kK-0001Xw-I0; Mon, 06 Nov 2006 14:03:02 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=P4I1y21CnvR9p2NSJiDQGM2NRqGZunzbYGmQnM5o97YR0S9ZSLKH6YunLN7rhZTD; 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.165.3.236] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1Gh9kI-0006yG-Ca; Mon, 06 Nov 2006 14:02:59 -0500
Message-ID: <007701c701d6$2f956ee0$6601a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: 'MIB Doctors' <mib-doctors@ietf.org>, ops-nm@ietf.org
References: <036301c70109$0e9a5fc0$0600a8c0@china.huawei.com>
Subject: Re: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement for configurationby SNMP
Date: Mon, 06 Nov 2006 11:02:56 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888c29d63c4e37bdee6fe3ef371a368c0df6a0b7aeaa8661ca7350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.165.3.236
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 'Mark Townsley' <townsley@cisco.com>
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: "David B Harrington" <dbharrington@comcast.net>
> To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>; "'MIB Doctors'" <mib-doctors@ietf.org>; <ops-nm@ietf.org>
> Cc: "'Mark Townsley'" <townsley@cisco.com>
> Sent: Sunday, November 05, 2006 10:34 AM
> Subject: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement for configurationby SNMP 
...
> Since possible alternatives are on the horizon, and the IETF
> management framework has always permitted the support for alternative
> protocols for carrying MIB module data, I suggest that any long-lived
> requirements section RECOMMEND, but not REQUIRE, SNMP so that
> alternative protocols could be used in the future to meet these
> management functionality requirements.
> 
> However, I believe that MIB modules and support for SNMP should
> continue to be required as a condition of IETF standards-track
> advancement until suitable alternative solutions are completed and
> available.
...

I'm having trouble fitting these two paragraphs together.
The first is consistent with the changes suggested, but
the second is a strong argument against making those
changes.

Randy


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

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