Subject: [Bridge-mib] Q: dot1dTpAgingTime in RFC1493 ?

From: [email-masked] (Alex Ruzin)
Date: Tue, 25 Dec 2001 12:43:38 +0200

Hi,

In RFC1493 there is no option to disable aging process at all.

In our products we have to use one of two *bad* methods:
1. *Edit* the standard MIB to avoid interval "range validity" of
dot1dTpAgingTime:
          dot1dTpAgingTime OBJECT-TYPE
              SYNTAX   INTEGER -- (10..1000000) [the range is commented out]

              ACCESS   read-write
              STATUS   mandatory
              DESCRIPTION
                      "The timeout period in seconds for aging out
                      dynamically learned forwarding information.
                      802.1D-1990 recommends a default of 300 seconds.
                      The value 0 means mode 'aging out is disabled'."
              REFERENCE
                      "IEEE 802.1D-1990: Section 6.7.1.1.3"
              ::= { dot1dTp 2 }

The value '0' of the object means the mode "aging is disabled"

2. Use our *private* MIB for this purpose.

Question: Is WG going to solve this problem in the standard MIB ?
Or: is there another method (may in another MIB) ?
Or: does WG think, that aging process has not to be disabled ?

As example, we propose to add a new special object, something like this:

          dot1dTpAgingEnabled OBJECT-TYPE
              SYNTAX   TruthValue
              ACCESS   read-write
              STATUS   mandatory
              DESCRIPTION
                      "The value true(1) means 'aging mode is enabled'.
                       The value false(2) means 'aging mode is disabled'"
              REFERENCE
                      "IEEE 802.1D-1990: Section 6.7.1.1.3"
              ::= { dot1dTp 5 }

Best regards, Alex

_______________________________________________
Bridge-mib mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/bridge-mib