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

snmpconf Re: TE-MIB readonly or read/write

Forwarded bounced message

------- Forwarded Message

Date: Wed, 13 Dec 2000 12:36:11 -0500 (EST)
From: Tony Tauber <ttauber@genuity.net>
X-Sender:  <ttauber@mesa.bbnplanet.com>
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
In-Reply-To: <3A36D5D5.B12D252F@longsys.com>
Message-ID: <Pine.GSO.4.30.0012131232060.1427-100000@mesa.bbnplanet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

> I would like the MIB to be read/write.

I'm inclined to agree.

I don't do SNMP sets and believe that's the common practice
among operators today (as Randy mentioned), but can't see
a good architectural reason to deny this possiblity right
out of the gate and box ourselves in.

If people choose not to use this capability or to administratively
prohibit it, that's fine; just like is done with SNMP sets today.


------- End of Forwarded Message