[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

snmpconf Re: TE-MIB readonly or read/write

Forwarding bounced message.

------- Forwarded Message

Message-ID: <3A37A982.805318E2@mailhost.avici.com>
Date: Wed, 13 Dec 2000 11:53:22 -0500
From: Joseph Dube <jdube@mailhost.avici.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Rob Frye <rfrye@longsys.com>
CC: TE Working Group <te-wg@UU.NET>,
        SNMPv3 Working Group <snmpv3@lists.tislabs.com>,
        SNMPconf Working Group <snmpconf@snmp.com>
Subject: Re: TE-MIB readonly or read/write
References: <3A36D5D5.B12D252F@longsys.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Please note that there is another mib containing a superset of the contents
of draft-ietf-tewg-mib-00.txt (Kireeti's mib).  This other mib is called
draft-ietf-mpls-te-mib-05.txt and it allows management and configuration via


Rob Frye wrote:

> In today's TEWG session, Kireeti stated that SNMP is used only for
> monitoring and shouldn't (according to various ISP's) be used for
> management/configuration.  I recommend that the TE MIB be usable for
> configuration for those things that can't be configured via LSP setup
> [whether by RSVP or LDP/CR-LDP].  SNMPv3 is gaining ground in some
> areas, and it's a positive cause-and-effect spiral: the more ISPs & IT
> depts are able to use SNMPv3 for device management, the more they want
> to be able to do so uniformly, and thus drive the availability & support
> for SNMPv3 elsewhere.
> I would like the MIB to be read/write.
> --
> // Rob.
> Rob Frye
> Director, Software Development
> Longitude Systems, Inc.
> 15000 Conference Center Drive
> Chantilly, VA  20151
> www.longsys.com
> voice:  +1-703-818-5426
> fax:    +1-703-961-8751
> mobile: +1-703-725-1130
> email:  rfrye@longsys.com

------- End of Forwarded Message