Re: DECnet MIB question (3) -- adjacency

saperia@tcpjon.ogo.dec.com Tue, 25 August 1992 15:05 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa02541; 25 Aug 92 11:05 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa02537; 25 Aug 92 11:05 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa07829; 25 Aug 92 11:07 EDT
Received: by inet-gw-2.pa.dec.com; id AA04652; Tue, 25 Aug 92 08:00:33 -0700
Received: by nsl.pa.dec.com; id AA12467; Tue, 25 Aug 92 07:16:59 -0700
Received: by nsl.pa.dec.com; id AA12463; Tue, 25 Aug 92 07:16:58 -0700
Received: by inet-gw-2.pa.dec.com; id AA01506; Tue, 25 Aug 92 07:16:56 -0700
Received: by tcpjon.ogo.dec.com (5.57/ULTRIX-fma-071891); id AA03503; Tue, 25 Aug 92 10:19:29 -0400
Message-Id: <9208251419.AA03503@tcpjon.ogo.dec.com>
To: Art Berggreen <art@opal.acc.com>
Cc: saperia@tcpjon.ogo.dec.com, phiv-mib@pa.dec.com
Subject: Re: DECnet MIB question (3) -- adjacency
In-Reply-To: Your message of "Fri, 21 Aug 92 16:54:26 PDT." <9208212354.AA17632@opal.acc.com>
Date: Tue, 25 Aug 92 10:19:29 -0400
From: saperia@tcpjon.ogo.dec.com
X-Mts: smtp

Art,

I am just catching up on mail and saw your comment:


>>If we go this route, I'd just ask to swap the order to:
>>    { phivAdjCircuitIndex, phivAdjNodeAddr }
It makes sense and I will make the change when we redo the draft.

/jon