Adjacency index

saperia@tcpjon.ogo.dec.com Tue, 25 August 1992 20:59 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa06916; 25 Aug 92 16:59 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa06912; 25 Aug 92 16:59 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa18041; 25 Aug 92 17:01 EDT
Received: by inet-gw-2.pa.dec.com; id AA23786; Tue, 25 Aug 92 14:00:33 -0700
Received: by nsl.pa.dec.com; id AA17431; Tue, 25 Aug 92 13:38:31 -0700
Received: by nsl.pa.dec.com; id AA17427; Tue, 25 Aug 92 13:38:30 -0700
Received: by inet-gw-2.pa.dec.com; id AA22709; Tue, 25 Aug 92 13:38:29 -0700
Received: by tcpjon.ogo.dec.com (5.57/ULTRIX-fma-071891); id AA04122; Tue, 25 Aug 92 16:41:14 -0400
Message-Id: <9208252041.AA04122@tcpjon.ogo.dec.com>
To: phiv-mib@pa.dec.com
Cc: phil@shiva.com, saperia@tcpjon.ogo.dec.com, dperkins@synoptics.com
Subject: Adjacency index
Date: Tue, 25 Aug 92 16:41:13 -0400
From: saperia@tcpjon.ogo.dec.com
X-Mts: smtp

Well I stand corrected.  Given that, that leaves us with two choices, either
depricate the old table which would work (as in MIBII).  I think it is messy
though.  The other choice is to do what we had planned last week.  Just change
the description which was unclear - the semantics really do not change  The
index was the index value of the circuit (taken from the circuit table) over 
which the adjacency is realized.

/jon


------- Forwarded Message

Return-Path: dperkins@synoptics.com
Received: by tcpjon.ogo.dec.com (5.57/ULTRIX-fma-071891);
	id AA03885; Tue, 25 Aug 92 13:00:47 -0400
Received: by inet-gw-2.pa.dec.com; id AA11599; Tue, 25 Aug 92 09:57:56 -0700
Received: from immer.synoptics.com by synoptics.com (4.1/SMI-4.1)id AA05039; Tue, 25 Aug 92 09:56:20 PDT
Received: by immer.synoptics.com (4.1/2.0N)   id AA29590; Tue, 25 Aug 92 09:56:21 PDT
Message-Id: <9208251656.AA29590@immer.synoptics.com>
Date: Tue, 25 Aug 92 09:56:21 PDT
From: David Perkins <dperkins@synoptics.com>
To: phil@Shiva.COM, saperia
Subject: Re: DECnet MIB question (3) -- adjacency
Cc: art@opal.acc.com, phiv-mib@Pa.dec.com

Jon,

There are only a few characteristics about MIB
items that can be changed once the MIB is published.
You can change the DESCRIPTION text as long as the semantics
are not changed. You can change the REFERENCE text to fix
typo's, bugs, etc. But you can not change the indexing,
or syntax. So, the question from Phil was a good one.

	Phil asks:

	>>Can you change the index on a table without deprecating
	>>the old one and creating a new and different one
	>>(particularly if an RFC has been published)?

        Jon's response....

	>>>The answer in this case is yes.  My interpretation of this
	>>>is that the documnet is currently at proposed standard status.
	>>>Before it could be moved forward as a draft, people have
	>>>to work on implementations.  The change to the index is 
	>>>a result of people looking at the problem a bit more closely.
	>>>So I see this as a normal part of the evolution.

	>>>I also do not think it is a major change.  If others on
	>>>the list really wanted to keep the other and deprecate
	>>>it I suppose we could. I do not feel very strongly about
	>>>this - so if there is a big press to deprecate the old and
	>>>essentially copy it with a couple of very minor changes
	>>>(not from a coding perspective as John would point out)
	>>>I will do it. 

This response is not correct. The proper way to "fix" the
problem is to obsolete/deprecate the old table (and all the "columns")
and to create a new table (and "columns").  This is why writing MIBs
is such a difficult task, since it it not valid to correct certain
classes of bugs by simply republishing the document with the
change once the document has been published. These types of fixes
are hopefully caught before the MIB starts on the standards track.

Sorry,
/dave perkins, synoptics, 408-764-1516

------- End of Forwarded Message