Re: Various DECnet MIB questions & Adjacency index

EMA - we manage almost anything! <sylor@blumon.enet.dec.com> Fri, 28 August 1992 19:38 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa05830; 28 Aug 92 15:38 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa05826; 28 Aug 92 15:38 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa14798; 28 Aug 92 15:40 EDT
Received: by inet-gw-2.pa.dec.com; id AA17359; Fri, 28 Aug 92 12:37:16 -0700
Received: by nsl.pa.dec.com; id AA12026; Fri, 28 Aug 92 12:09:59 -0700
Received: by nsl.pa.dec.com; id AA11359; Fri, 28 Aug 92 11:17:38 -0700
Message-Id: <9208281817.AA11359@nsl.pa.dec.com>
Received: from blumon.enet; by nsl.enet; Fri, 28 Aug 92 12:09:53 PDT
Date: Fri, 28 Aug 92 12:09:53 PDT
From: EMA - we manage almost anything! <sylor@blumon.enet.dec.com>
To: phiv-mib@pa.dec.com
Cc: sylor@blumon.enet.dec.com
Apparently-To: phiv-mib@Pa.dec.com
Subject: Re: Various DECnet MIB questions & Adjacency index

    Yes, by all means, use circuit index. That's consistent with "common
    practice" in all the mibs.

    But... Using a variable length string does work in SNMP, the necessary
    pieces are there. And it does not have to be the last index in the list
    (there's a count up front that tells you where the string ends). Bob
    pointed out the "problem", Lexigraphic ordering orders variable length
    strings first by length and then alphabetically. That's not intuitive.

    						Mark

    PS: (-: Just to put those complaints about how hard it is to code for
            string indices in perspective; The NICE protocol uses variable
            length strings as "indices" for circuits, and it works quite nicely
            (sic).  There was an agent for RT-11 that ran on a 64Kbyte machine.
            :-)