Suggested corrections to FDDI MIB Version 2.1

Change is different 16-Nov-1992 1406 <stefani@quiver.enet.dec.com> Mon, 16 November 1992 20:33 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12936; 16 Nov 92 15:33 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12932; 16 Nov 92 15:33 EST
Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa03100; 16 Nov 92 15:35 EST
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA29055; Mon, 16 Nov 92 14:10:52 -0500
Received: from inet-gw-2.pa.dec.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA29051; Mon, 16 Nov 92 14:10:48 -0500
Received: by inet-gw-2.pa.dec.com; id AA21333; Mon, 16 Nov 92 11:10:43 -0800
Received: by us1rmc.bb.dec.com; id AA27796; Mon, 16 Nov 92 14:08:14 -0500
Message-Id: <9211161908.AA27796@us1rmc.bb.dec.com>
Received: from quiver.enet; by us1rmc.enet; Mon, 16 Nov 92 14:08:14 EST
Date: Mon, 16 Nov 92 14:08:14 EST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Change is different 16-Nov-1992 1406 <stefani@quiver.enet.dec.com>
To: fddi-mib@cs.utk.edu
Cc: luc@quiver.enet.dec.com, shawn@quiver.enet.dec.com, anil@quiver.enet.dec.com, stefani@quiver.enet.dec.com
Apparently-To: fddi-mib@cs.utk.edu
Subject: Suggested corrections to FDDI MIB Version 2.1

After reviewing the FDDI MIB Draft Version 2.1, we have the following
suggested corrections:

Regards,
   Larry

+---------------------------------------------------------------------------+
|   Lawrence Stefani                        Digital Equipment Corporation   |
|   Network Systems Engineering             stefani@quiver.enet.dec.com     |
+---------------------------------------------------------------------------+



The SMT Group
-------------

(pgs. 13, 21, 22)
    The SMTHoldState object is optional in SMT 7.2 and should be removed from
    the SNMP MIB.

(pgs. 14, 23)
    The SMTSetCount object is optional in SMT 7.2 and not particularly useful
    for SNMP management and should be removed from the SNMP MIB.

(pg. 14)
    The snmpFddiSMTOpVersionId object should have read-only access.

(pg. 16)
    The SMTNonMasterCt object has a syntax constraint of (0..2).  The
    snmpFddiSMTNonMasterCts object syntax may be updated accordingly.

(pg. 17)
    The snmpFddiSMTConfigPolicy object should have a syntax of INTEGER (0..1).

(pg. 18)
    The snmpFddiSMTConnectionPolicy object should have a syntax of
    INTEGER (32768..65535).

(pg. 24)
    The snmpFddiSMTStationAction object is missing the new actions from SMT
    7.2:

	disable-a(6)
        disable-b(7)
        disable-m(8)

    The syntax and descriptions should be updated accordingly.


The MAC Group
-------------

(pgs. 26, 28)
    The MACBridgeFunctions object is optional in SMT 7.2 and should be
    removed from the SNMP MIB.

(pgs. 27, 39, 40)
    The MACAction object was deleted in SMT 7.1 and should be removed from
    the SNMP MIB.

(pg. 31)
    The snmpFddiMACRequestedPaths object should have a syntax of
    INTEGER (0..255).

(pg. 33)
    The snmpFddiMACTReq object should have read-only access.

(pgs. 35, 36)
    The snmpFddiMACFrameErrorThreshold object should have read-write access.

(pg. 38)
    The snmpFddiMACMAUnitdataEnable object should have read-write access.


The PATH Group
--------------

(pg. 47)
    The snmpFddiPATHMaxTReq object should have read-write access.


The PORT Group
--------------

(pgs. 50, 53)
    The PORTRequestedPaths object has a syntax of three bytes representing
    "none", "tree", and "peer", respectively.  Each byte is a bit-string
    of permitted paths and has a range of (0..255).

    The snmpFddiPORTRequestedPaths object should have its SYNTAX updated
    to reflect the SMT definition as appropriate for SNMP MIB SYNTAX
    definitions.

(pgs. 56, 57, 58)
    The snmpFddiPORTLerEstimate, snmpFddiPORTLerCutoff, and
    snmpFddiPORTLerAlarm objects should all have a syntax of INTEGER (4..15).

(pg. 60)
    The SYNTAX for the snmpFddiPORTAction object contains values from the
    SMTStationAction object.  Since SMT 7.2 hasn't modified PORTAction,
    the snmpFddiPORTAction text can be replaced with the one from RFC1285.


Editorial Comments
------------------

(pg. 5)
    The word "contains" is duplicated in the first sentence of section 4.1.

(pg.9)
    The comments for FddiResourceId can be updated with the removal of
    the ATTACHMENT group from SMT 7.2.

To be consistent with the ANSI SMT naming convention, I recommend that

         - (pgs. 13, 16)  snmpFddiSMTPathsAvailable be renamed to
                          snmpFddiSMTAvailablePaths.

         - (pgs. 26, 28)  snmpFddiMACFrameStatusFunction be renamed to
                          snmpFddiMACFrameStatusFunctions.

         - (pgs. 26, 31)  snmpFddiMACDupAddrTest be renamed to
                          snmpFddiMACDupAddressTest.

         - (pgs. 27, 37)  snmpFddiMACFrameCondition be renamed to
                          snmpFddiMACFrameErrorFlag.

         - (pgs. 50, 51)  snmpFddiPORTPCType be renamed to snmpFddiPORTMyType.

         - (pgs. 50, 51)  snmpFddiPORTPCNeighbor be renamed to
                          snmpFddiPORTNeighborType.

         - (pgs. 50, 53)  snmpFddiPORTCEState be renamed to
                          snmpFddiPORTCurrentPath.

         - (pgs. 50, 59)  snmpFddiPORTLerCondition be renamed to
                          snmpFddiPORTLerFlag.

(pg. 18)
    The description for snmpFddiSMTConfigPolicy should be updated to reflect
    the changes in that object's syntax.

    The description for snmpFddiSMTConnectionPolicy should be updated to
    replace "32767" with "32768" in the second sentence of the second
    paragraph.

(pg. 28)
    The description for snmpFddiMACFrameStatusFunction should be updated to
    replace "copying" with "fs-clearing" in the function table.

(pg. 34)
    The reference for the snmpFddiMACTvxValue object should be updated from
    "ANSI { fddiMAC 53 }" to "ANSI { fddiMAC 54 }".

(pg. 38)
    The description for snmpFddiMACMAUnitdataEnable contains the description
    for the MACVendorAttrib.  The description should be replaced.

(pg. 46)
    The description for snmpFddiPATHTVXLowerBound should be updated starting
    from "Changes to this variable..."

   	Changes to this variable shall either satisfy the time value
        relationship:

		fddiPATHTVXLowerBound <= fddiMACTVXCapability

        of each of the MACs currently on the path, or be considered
        out of range.  The initial value of fddiPATHTVXLowerBound
        shall be 2.500 msec."

(pg. 47)
    The description for snmpFddiPATHTMaxLowerBound should be updated starting
    from "This variable has the time..."

   	This variable has the time value range of:

		fddiPATHMaxTReq <= fddiPATHTMaxLowerBound

        and an absolute time value range of:

                10 msec. <= fddiPATHTMaxLowerBound.

        Changes to this variable shall either satisfy the time value
        relationship:

		fddiPATHTMaxLowerBound <= fddiMACTMaxCapability

        of each of the MACs currently on the path, or be considered
        out of range.  The initial value of fddiPATHTMaxLowerBound
        shall be 165 msec."

(pgs. 47, 48)
    The description for snmpFddiPATHTMaxLowerBound should be updated starting
    from "This variable has the time..."

   	This variable has the time value range of:

		fddiPATHTVXLowerBound < fddiPATHMaxTReq <=
                fddiPATHTMaxLowerBound.

        The default value of fddiPATHMaxTReq is 165 msec."