DECnet MIB question (3) -- adjacency

"John A. Shriver" <jas@proteon.com> Fri, 21 August 1992 22:15 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa08471; 21 Aug 92 18:15 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa08467; 21 Aug 92 18:15 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa18390; 21 Aug 92 18:17 EDT
Received: by inet-gw-2.pa.dec.com; id AA08111; Fri, 21 Aug 92 15:13:54 -0700
Received: by nsl.pa.dec.com; id AA00800; Fri, 21 Aug 92 14:22:05 -0700
Received: by nsl.pa.dec.com; id AA00796; Fri, 21 Aug 92 14:22:04 -0700
Received: by inet-gw-2.pa.dec.com; id AA03095; Fri, 21 Aug 92 13:50:11 -0700
Received: from sonny.proteon.com by monk.proteon.com (5.65/1.8)id AA19328; Fri, 21 Aug 92 16:50:06 -0400
Received: by sonny.proteon.com (3.2/SMI-3.2)id AA19502; Fri, 21 Aug 92 16:49:57 EDT
Date: Fri, 21 Aug 92 16:49:57 EDT
From: "John A. Shriver" <jas@proteon.com>
Message-Id: <9208212049.AA19502@sonny.proteon.com>
To: phiv-mib@pa.dec.com
In-Reply-To: Debasis Dalapati's message of Fri, 21 Aug 92 15:33:04 EDT <9208211933.AA11141@tci.bell-atl.com>
Subject: DECnet MIB question (3) -- adjacency

Hmm, as I look at it harder, I start to agree (much as I don't want to
be the person implenting it) that the INDEX should be
{phivAdjNodeAddr, phivAdjCircuitIndex}.  It won't be the first table
to have node addresses as indices.

As for get next, it always returns the next higher value of the index,
whatever it is...