Re: Adjacency index

Art Berggreen <art@opal.acc.com> Fri, 28 August 1992 16:05 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa03886; 28 Aug 92 12:05 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa03882; 28 Aug 92 12:05 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa10000; 28 Aug 92 12:07 EDT
Received: by inet-gw-2.pa.dec.com; id AA04808; Fri, 28 Aug 92 09:07:20 -0700
Received: by nsl.pa.dec.com; id AA09844; Fri, 28 Aug 92 08:49:48 -0700
Received: by nsl.pa.dec.com; id AA09840; Fri, 28 Aug 92 08:49:27 -0700
Received: by inet-gw-1.pa.dec.com; id AA09550; Fri, 28 Aug 92 08:48:48 -0700
Received: by opal.acc.com (4.1/SMI-4.0)id AA09465; Fri, 28 Aug 92 08:50:23 PDT
Date: Fri, 28 Aug 92 08:50:23 PDT
From: Art Berggreen <art@opal.acc.com>
Message-Id: <9208281550.AA09465@opal.acc.com>
To: phiv-mib@pa.dec.com
Subject: Re: Adjacency index

>       phivAdjEntry OBJECT-TYPE
>           SYNTAX PhivAdjEntry
>           ACCESS not-accessible
>           STATUS mandatory
>           DESCRIPTION
>               "There is one entry in the table for each adjacency."
>           INDEX  { phivAdjCircuitName, phivAdjNodeAddr }
>           ::= { phivAdjTable 1 }

If you were to use phivAdjCircuitNmae, it would have to be the last component
of the instance (being variable length).

But please, let's use phivAdjCircuitIndex, it's much simpler to deal with.

Art