Subject: snmpconf TE-MIB readonly or read/write

From: Steve Moulton <[email-masked]>
Date: Wed, 13 Dec 2000 12:59:19 -0500

The following message is being forwarded to snmpconf after being
bounced due to an address change.

------- Forwarded Message

Received: by seymour39.SNMP.COM (8.9.3/m.000221) id LAA15362;
	Wed, 13 Dec 2000 11:31:06 -0500 (EST)
Date: Wed, 13 Dec 2000 11:31:06 -0500 (EST)
From: [email-masked]
Message-Id: <[email-masked]>
To: [email-masked]
Subject: BOUNCE [email-masked]:    Non-member submission from [Rob Frye <[email-masked]>]   

>From [email-masked]  Wed Dec 13 11:31:03 2000
Date: Tue, 12 Dec 2000 17:50:14 -0800
From: Rob Frye <[email-masked]>
Organization: Longitude Systems, Inc.
To: TE Working Group <[email-masked]>
CC: SNMPv3 Working Group <[email-masked]>,
        SNMPconf Working Group <[email-masked]>
Subject: TE-MIB readonly or read/write

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:  [email-masked]

------- End of Forwarded Message