Re: Table idices

Bob Stewart <bstewart@cisco.com> Thu, 27 March 1997 19:33 UTC

Received: from cnri by ietf.org id aa04050; 27 Mar 97 14:33 EST
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa18685; 27 Mar 97 14:33 EST
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id OAA00480 for snmpv2-outgoing; Thu, 27 Mar 1997 14:24:15 -0500 (EST)
X-Sender: bstewart@puli.cisco.com
Message-Id: <v03101743af607a0f86c4@[171.69.128.42]>
In-Reply-To: <19970327175904927.AAA169@jleonard.wireless.tellabs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 27 Mar 1997 14:26:28 -0500
To: John Leonard <jleonard@mail1.wireless.tellabs.com>
From: Bob Stewart <bstewart@cisco.com>
Subject: Re: Table idices
Cc: SNMPv2 List <snmpv2@tis.com>, SNMP List <snmp@lists.psi.com>
Sender: owner-snmpv2@ex.tis.com
Precedence: bulk

Circa 1:01 PM -0500 3/27/97, John Leonard bitwhacked:
>Is there any SNMP or SNMPv2 RFC that comes out and states that INTEGER
>table indices can't take the value 0? I know that there is a *very* strong
>convention that they not use 0, but is this actually forbidden?

Zero is a legitimate table index.  It is typically avoided for the
"arbitrary integer index" so it can be used for other purposes, such as in
a reference to indicate no index is set or applies.

	Bob