X.25 MIB Questions

"Glenn C. Aikens (919-254-4588)" <AIKENS@ralvma.vnet.ibm.com> Wed, 15 September 1993 20:45 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12637; 15 Sep 93 16:45 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12633; 15 Sep 93 16:45 EDT
Received: from dg-rtp.rtp.dg.com by CNRI.Reston.VA.US id aa02053; 15 Sep 93 16:45 EDT
Received: from dg-webo.us.dg.com by dg-rtp.dg.com (5.4R2.01/dg-rtp-v02) id AA15517; Wed, 15 Sep 1993 16:15:52 -0400
Received: from vnet.ibm.com by dg-webo.webo.dg.com (5.4.1/dg-webo-v1) id AA12526; Wed, 15 Sep 1993 16:14:04 -0400
Message-Id: <9309152014.AA12526@dg-webo.webo.dg.com>
Received: from RALVMA by vnet.IBM.COM (IBM VM SMTP V2R2) with BSMTP id 2707; Wed, 15 Sep 93 16:09:07 EDT
Date: Wed, 15 Sep 93 16:08:19 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Glenn C. Aikens (919-254-4588)" <AIKENS@ralvma.vnet.ibm.com>
To: x25mib@dg-rtp.dg.com
Subject: X.25 MIB Questions

   I have a couple of questions about the X.25 MIBs that I am hoping
the working group can help with.

1)  Want to make sure I understand the description for the x25Restart TRAP
    (X.25 Packet Layer MIB RFC1382).  This is how I understand it:

    - When an X.25 link is brought up, a linkUp TRAP is sent, but a x25Restart
      TRAP is NOT sent.
    - When an X.25 link receives a restart packet, an x25Restart TRAP is
      sent, but linkUp and linkDown TRAPS are NOT sent.
    - When an X.25 link sends/receives a frame reject packet, a linkDown TRAP
      is sent, but an x25Restart TRAP is NOT sent

    Is this correct?  Am I missing anything?

2)  Couple of questions on the Call Parm Table (X.25 Packet Layer MIB RFC1382):

    - What is the intent of the Call Parm Table?  Default, intended, current, or
      past Call Parms?  All of them?  Implementer's choice?

    - Maintaining a huge Call Parm Table (with past Call Parms) could require
      a tremendous amount of memory/processing cycles.  Because of timing and
      memory constraints, an implementation may only want to keep a subset
      (maybe just current) of the total Call Parms.
      What is the recommended use of the Call Parm Table for
      implementations that may have storage/memory/processing constraints?

3)  The Multiprotocol Interconnect over X.25 MIB is an Internet draft, not an
    RFC.  Should someone who is implementing RFC1356 support the
    Multiprotocol Interconnect MIB, or wait until the MIB is a standard?
    Implement the draft now and the standard later?  How close is the
    Multiprotocol Interconnect MIB to becoming a standard?

4)  What is the value of having mioxPleMaxCircuits=0 (Multiprotocol Interconnect
    MIB) in the mioxPleTable?  The time interval when an interface is going down
    is probably split-second and so it is probably not a great help to the
    user since he will almost always never see it.