Subject: TE-RSVP MIB?

From: K Arvind <[email-masked]>
Date: Wed, 4 Aug 1999 18:33:51 -0400

Hi,

RFC2206 specifies a MIB for RSVP. However,

(1) It appears to be tightly intertwined with the Integrated Services 
model. Many of the objects are not relevant to TE-RSVP (see below):
	rsvpSessionProtocol
	rsvpSenderProtocol
	rsvpSenderDestPort
	rsvpSenderPort
	rsvpSenderFlowId
	rsvpResvProtocol
	rsvpResvDestPort
	rsvpResvPort
	rsvpResvFwdProtocol
	rsvpResvFwdDestPort
	rsvpResvFwdPort

(2) A large number of other objects (TSpec, RSpec, AdSpec-related objects) 
will be relevant only if tunnels are used to realize IntServ classes of 
service. (of course, the TE-RSVP spec does not rule out this use)

(3) Also, the MIB allows RSVP path and reservation state to be established 
on any node directly via SNMP. Would such a capability be useful or 
relevant to TE-RSVP? Wouldn't it be safer to allow RSVP state to be 
established only through the traffic engineering service interface?

(4) The MIB, for obvious reasons, does not cover many of the objects 
defined in the TE-RSVP draft (ERO, session attribute, etc.)

Given these disconnects between RFC2206 and TE-RSVP, would it be useful to 
define a new MIB for TE-RSVP? Has such a MIB been proposed already?

Thank you.

Regards,
Arvind.

K. Arvind, Ph.D.
TENOR Networks, Inc.
50, Nagog Park, Acton, MA 01720
W: 978-264-4900 x124
F: 978-264-0671
E: mailto:[email-masked]
U: http://www.tenornetworks.com