Re: Adjacency index

saperia@tcpjon.ogo.dec.com Sat, 29 August 1992 01:40 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa07742; 28 Aug 92 21:40 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa07738; 28 Aug 92 21:40 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa21303; 28 Aug 92 21:42 EDT
Received: by inet-gw-2.pa.dec.com; id AA05431; Fri, 28 Aug 92 18:39:10 -0700
Received: by nsl.pa.dec.com; id AA16411; Fri, 28 Aug 92 18:22:20 -0700
Received: by nsl.pa.dec.com; id AA16407; Fri, 28 Aug 92 18:22:18 -0700
Received: by inet-gw-2.pa.dec.com; id AA04724; Fri, 28 Aug 92 18:22:13 -0700
Received: by tcpjon.ogo.dec.com (5.57/ULTRIX-fma-071891); id AA11921; Fri, 28 Aug 92 21:24:47 -0400
Message-Id: <9208290124.AA11921@tcpjon.ogo.dec.com>
To: Art Berggreen <art@opal.acc.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 14:46:56 PDT." <9208282146.AA09641@opal.acc.com>
Date: Fri, 28 Aug 92 21:24:46 -0400
From: saperia@tcpjon.ogo.dec.com
X-Mts: smtp

>>Uh Jon,  did you miss renaming phivAdjAddr?

the reason it is not phivAdjNodeAddr is that that was the name in the old
table and I figured that people would understand what phivAdjAddr is?

If you feel strongly, give me an alternate suggestion.

/jon