Re: DECIV-MIB - Objects routeing 14 and 24

Jon Saperia <saperia@tcpjon.tay.dec.com> Thu, 17 June 1993 13:50 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03110; 17 Jun 93 9:50 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03106; 17 Jun 93 9:50 EDT
Received: from inet-gw-2.pa.dec.com by CNRI.Reston.VA.US id aa10098; 17 Jun 93 9:50 EDT
Received: by inet-gw-2.pa.dec.com; id AA04811; Thu, 17 Jun 93 06:50:49 -0700
Received: by nsl.pa.dec.com; id AA17263; Thu, 17 Jun 93 06:09:52 -0700
Received: by nsl.pa.dec.com; id AA17259; Thu, 17 Jun 93 06:09:50 -0700
Received: by pobox1.pa.dec.com; id AA06982; Thu, 17 Jun 93 06:09:47 -0700
Received: by tcpjon.tay.dec.com (5.57/ULTRIX-fma-071891); id AA07282; Thu, 17 Jun 93 09:13:35 -0400
Message-Id: <9306171313.AA07282@tcpjon.tay.dec.com>
To: Sven Olav Lund <sol@sony.craycom.dk>
Cc: saperia@tcpjon.tay.dec.com, phiv-mib@pa.dec.com
Subject: Re: DECIV-MIB - Objects routeing 14 and 24
In-Reply-To: Your message of "Wed, 16 Jun 93 09:34:57 BST." <9306160835.AA04630@sony.craycom.dk>
Date: Thu, 17 Jun 93 09:13:34 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jon Saperia <saperia@tcpjon.tay.dec.com>
X-Mts: smtp

Hi,

>  I wonder why 'phivRouteType' and 'phivRouteSystemAddr' are read-only
> parameters? According to the 'Network Management Functional Specification'
> they are not restricted to read-only. Our implementation allows changing
>  of the Routing Type and Executor Address. It would be nice if the MIB
>  supports this too.

I asked that you post this to the list since this is one of the groups that
everone who responded to the survey implemented.  I would be happy to
obsolete these two objects and remake them as read-write if the other
people do not object.  

Lets see what people say.  If there are not objections, I will redo the objects
as read-write.
/jon