Re: Adjacency index

Debasis Dalapati <deb@tci.bell-atl.com> Fri, 28 August 1992 22:06 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa07035; 28 Aug 92 18:06 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa07031; 28 Aug 92 18:06 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa18225; 28 Aug 92 18:08 EDT
Received: by inet-gw-2.pa.dec.com; id AA26185; Fri, 28 Aug 92 15:08:10 -0700
Received: by nsl.pa.dec.com; id AA13736; Fri, 28 Aug 92 14:44:44 -0700
Received: by nsl.pa.dec.com; id AA13732; Fri, 28 Aug 92 14:44:41 -0700
Received: by inet-gw-2.pa.dec.com; id AA25095; Fri, 28 Aug 92 14:44:38 -0700
Received: by bagate.BELL-ATL.COM (/\==/\ Smail3.1.25.1 #25.29)id <m0mOE8x-0000bxC@bagate.BELL-ATL.COM>; Fri, 28 Aug 92 17:46 EDT
Received: by tci.bell-atl.com (4.1/SMI-4.1)id AA24524; Fri, 28 Aug 92 17:55:15 EDT
Date: Fri, 28 Aug 92 17:55:15 EDT
From: Debasis Dalapati <deb@tci.bell-atl.com>
Message-Id: <9208282155.AA24524@tci.bell-atl.com>
To: saperia@tcpjon.ogo.dec.com
Subject: Re: Adjacency index
Cc: phiv-mib@pa.dec.com

>
>From: saperia@tcpjon.ogo.dec.com
>
>Debasis,
>
>>>Could you repeat once more what the "INDEX" specification would look like for
>>>phivAdjEntry object ?
>
>Sure here is the entire table:
>
>Here is how the new table would look with new names etc.  Rather than
>tacking an N on at the end of each name, I just added node to the name
>in most cases which makes the meaning of the objects clear (I hope).
>
>       phivAdjNodeTable OBJECT-TYPE
>           SYNTAX SEQUENCE OF PhivAdjNodeEntry
>           ACCESS not-accessible
>           STATUS mandatory
>           DESCRIPTION
>               "The Adjacent Node Table."
>           ::= { adjacency 1 }
>
>       phivAdjNodeEntry OBJECT-TYPE
>           SYNTAX PhivAdjNodeEntry
>           ACCESS not-accessible
>           STATUS mandatory
>           DESCRIPTION
>               "There is one entry in the table for each adjacency."
>           INDEX  { phivAdjNodeCircuitIndex, phivAdjAddr }
>           ::= { phivAdjNodeTable 1 }
>
>       PhivAdjNodeEntry ::=
>           SEQUENCE {
>               phivAdjNodeCircuitIndex
>                   INTEGER,
>               phivAdjAddr
>                   PhivAddr,
>               phivAdjNodeBlockSize
>                   INTEGER,
>               phivAdjNodeListenTimer
>                   INTEGER (1..65535),
>               phivAdjNodeCircuitEtherServPhysAddr
>                   OCTET STRING,
>               phivAdjNodeType
>                   INTEGER,
>               phivAdjNodeState
>                   INTEGER,
>               phivAdjNodePriority
>                   INTEGER,
>               phivAdjNodeExecListenTimer
>                   INTEGER (1..65535)
>            }
>
>[ stuffs deleted ]
>
>

Jon,

Perfect! Well done with the names. 

Now as we are creating the new table, would it be appropriate to get rid
of the object phivAdjNodeExecListenTimer at this time?

Some time back, I asked a question about phivAdjListenTimer and 
phivAdjExecListenTimer and my understanding was that phivAdjExecListenTimer
could be dropped from the table. Well, there is no harm in keeping it, except
myself (and others) could avoid explaning it. :) Just reminding. 

debasis