Re: Adjacency index

Bob Stewart <rlstewart@eng.xyplex.com> Fri, 28 August 1992 15:36 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa03436; 28 Aug 92 11:36 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa03432; 28 Aug 92 11:36 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa09354; 28 Aug 92 11:38 EDT
Received: by inet-gw-2.pa.dec.com; id AA03103; Fri, 28 Aug 92 08:37:13 -0700
Received: by nsl.pa.dec.com; id AA09537; Fri, 28 Aug 92 08:08:33 -0700
Received: by nsl.pa.dec.com; id AA09533; Fri, 28 Aug 92 08:08:32 -0700
Received: by inet-gw-2.pa.dec.com; id AA01572; Fri, 28 Aug 92 08:08:30 -0700
Received: by xap.xyplex.com id <AA12928@xap.xyplex.com>; Fri, 28 Aug 92 11:07:56 -0500
Date: Fri, 28 Aug 92 11:07:56 -0500
Message-Id: <9208281607.AA12928@xap.xyplex.com>
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: phiv-mib@pa.dec.com
In-Reply-To: saperia@tcpjon.ogo.dec.com's message of Fri, 28 Aug 92 09:55:32 -0400 <9208281355.AA10320@tcpjon.ogo.dec.com>
Subject: Re: Adjacency index

I didn't mean to come on so strong about "decidedly broken."  No offense
intended, Jon.  Sometimes I get over enthusiastic.

I believe you are required to leave the old table's object identifiers unused,
perhaps forever.  As a MIB grows, its original, logical flow usually becomes
somewhat disrupted by additions.

You can use DisplayString for circuit name as an index.  The ASN.1 binary
encoding of that and OCTET STRING are identical.  You're right about it being
a bit painful.  It's weird, too, as get-next will return the names by length
first, then alphabetically.  That's a recognized oddity in the encoding.

	Bob