Re: My comments on the IP over X.25 MIB
Andy Malis <malis@bbn.com> Thu, 07 May 1992 18:47 UTC
Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa04158; 7 May 92 14:47 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa04950; 7 May 92 14:52 EDT
Received: from dg-rtp.rtp.dg.com by NRI.Reston.VA.US id aa04946; 7 May 92 14:52 EDT
Received: from OAKLAND.BBN.COM by dg-rtp.dg.com (5.4/dg-rtp-proto) id AA00858; Thu, 7 May 1992 14:11:07 -0400
Message-Id: <9205071811.AA00858@dg-rtp.dg.com>
To: "Dean D. Throop" <throop@dg-rtp.dg.com>
Cc: x25mib@dg-rtp.dg.com, malis@bbn.com
Subject: Re: My comments on the IP over X.25 MIB
In-Reply-To: Your message of Wed, 06 May 92 17:21:12 -0400. <9205062121.AA17325@walrus>
Date: Thu, 07 May 1992 13:17:48 -0400
From: Andy Malis <malis@bbn.com>
Dean, > Should we record the time of the last translation failure? Sounds good to me. > Should we record Q-bit failures on a Per PLE (interface) basis and > record the remote address rather than keep a per peer counter? Can we do both? If not, then you make a good case for doing it by interface. > Should we record the time of the last Q bit failure? Sure. > Should minimum open, idle, and hold down timers be kept on a per > PLE (interface) or per peer basis? Per Peer allows control of > different values for different remote peers but requires more > memory to hold all the different values. Not to mention more configuration work. However, if (for example) you know you're crossing an X.75 boundary to reach a particular destination, then different timers would be nice, if not necessary, in some cases. > Should we record failures on a per system basis rather than a per > interface table? Rather than having everthing per interface we > could make it global to the system; this might reduce the number of > objects required. I don't like this, unless you can give a more concrete proposal. Andy
- My comments on the IP over X.25 MIB Dean D. Throop
- Re: My comments on the IP over X.25 MIB Andy Malis