Re: Adjacency index

saperia@tcpjon.ogo.dec.com Fri, 28 August 1992 18:08 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa05104; 28 Aug 92 14:08 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa05100; 28 Aug 92 14:08 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa12752; 28 Aug 92 14:10 EDT
Received: by inet-gw-2.pa.dec.com; id AA11695; Fri, 28 Aug 92 11:07:15 -0700
Received: by nsl.pa.dec.com; id AA11117; Fri, 28 Aug 92 10:55:38 -0700
Received: by nsl.pa.dec.com; id AA11113; Fri, 28 Aug 92 10:55:37 -0700
Received: by inet-gw-2.pa.dec.com; id AA11015; Fri, 28 Aug 92 10:55:35 -0700
Received: by tcpjon.ogo.dec.com (5.57/ULTRIX-fma-071891); id AA11058; Fri, 28 Aug 92 13:58:10 -0400
Message-Id: <9208281758.AA11058@tcpjon.ogo.dec.com>
To: Debasis Dalapati <deb@tci.bell-atl.com>
Cc: saperia@tcpjon.ogo.dec.com, phiv-mib@pa.dec.com
Subject: Re: Adjacency index
In-Reply-To: Your message of "Fri, 28 Aug 92 13:55:33 EDT." <9208281755.AA24147@tci.bell-atl.com>
Date: Fri, 28 Aug 92 13:58:09 -0400
From: saperia@tcpjon.ogo.dec.com
X-Mts: smtp

debasis,

There is now a thundering consensus for your request:


>>>>So, please use "phivCircuitIndex" with whatever name you prefer. 

This is how it is defined in the current draft - though clearly  the words are
not as good as they should have been.  The name of the object will be
phivAdjCircuitIndex.

See the rest of the notes for more details.

I believe we have at last put this issue to bed.

Thanks everyone for all the time on this.

/jon