Internet Draft - Power Ethernet MIB

"MAINS,SCOTT (HP-Roseville,ex1)" <[email protected]>
Newsgroups gmane.ietf.hubmib
Message-ID <[email protected]>
Hi Everyone--

I was reviewing this draft and found the following inconsistencies:

       ::= { pethPsePortEntry 8 }

        pethPsePortPowerMaintenanceStatus  OBJECT-TYPE
       SYNTAX INTEGER   {
                  ok(1),
                  underCurrent(2),
                  mPSAbsent(3)
        }
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
           "The value ok(1) indicates the Power Maintenance
            Signature is present and the overcurrent condition has not been
            detected.
            The value overCurrent (2) indicates an overcurrent condition
            has been detected.
            The value mPSAbsent(3) indicates that the Power Maintenance
            Signature is absent."


       REFERENCE   "[IEEE Draft P802.3af/D3.3, October, 2002, 30.9.1.1.8
                   aPSEPowerMaintenanceStatus]"

The 802.3af/D4.0, November 14, 2002 has values of ok, MPSAbsent, and
overCurrent. Shouldn't this match? 

       ::= { pethPsePortEntry 11 }

        pethPsePortOverCurrentCounter OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
                "Counts the number of times that the aPSEPowerCurrentStatus
                 attribute changes from any value to the value
overCurrent(2)."
       REFERENCE   "[IEEE Draft P802.3af/D3.3, October, 2002, object
30.9.1.1.10
                     aPSEOverCurrentCounter]"

I believe the description should read pethPsePortPowerMaintenanceStatus and
not aPSEPowerCurrentStatus and the Reference should change to
aPSEPowerMaintenanceStatus to match 802.3af.

Thanks,
Scott

Scott Mains
Hewlett-Packard Company
Procurve Networking Business
8000 Foothills Blvd. M/S 5557
Roseville, CA 95747
Ph: 916 785-3505
Fax: 916 785-1199
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.