[Bridge-mib] Re: FW: 802.1x and TimeTicks

"Les Bell" <Les_Bell@eur.3com.com> Mon, 25 March 2002 08:59 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05690 for <bridge-archive@odin.ietf.org>; Mon, 25 Mar 2002 03:59:10 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id DAA24038 for bridge-archive@odin.ietf.org; Mon, 25 Mar 2002 03:59:13 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA23886; Mon, 25 Mar 2002 03:58:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA23844 for <bridge-mib@optimus.ietf.org>; Mon, 25 Mar 2002 03:58:33 -0500 (EST)
Received: from columba.www.eur.3com.com (ip-161-71-171-238.corp-eur.3com.com [161.71.171.238]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05683 for <bridge-mib@ietf.org>; Mon, 25 Mar 2002 03:58:29 -0500 (EST)
Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50]) by columba.www.eur.3com.com with ESMTP id g2P90Ex11811; Mon, 25 Mar 2002 09:00:14 GMT
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id g2P8wSc25893; Mon, 25 Mar 2002 08:58:28 GMT
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256B87.00316C0C ; Mon, 25 Mar 2002 08:59:49 +0000
X-Lotus-FromDomain: 3COM
From: Les Bell <Les_Bell@eur.3com.com>
To: "Pape, Bruno" <bpape@enterasys.com>
cc: "'stds-802-1@ieee.org'" <stds-802-1@ieee.org>, bridge-mib@ietf.org
Message-ID: <80256B87.00316ABD.00@notesmta.eur.3com.com>
Date: Mon, 25 Mar 2002 08:53:25 +0000
Mime-Version: 1.0
Content-type: multipart/mixed; Boundary="0__=I5dk6uZXhttP0Kuv1ymWLLHZJsnDfrQbJy8jqtD4rnKfkvjXfFr4q0Xf"
Content-Disposition: inline
Subject: [Bridge-mib] Re: FW: 802.1x and TimeTicks
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org


Bruno,

The intention for dot1xAuthSessionTime was to report it in hundredths of
seconds, as the TimeTicks TC says.  The description is wrong.

The question we have to ask now is:
How do people think we should fix this bug?

Option 1:
    Fix the description to say "hundredths of seconds".

Option 2:
    Fix the syntax as Integer32 (I think IETF rules do not permit this).

Option 3:
    Deprecate dot1xAuthSessionTime and
        a) define a new item using TimeTicks, or
        b) define a new item using Integer32.

This bug highlights one of the problems of developing MIBs in IEEE 802 groups:
lack of peer review.  The MIB experts are all at the IETF, so we need to get
IETF involvement in the MIB development at an early stage, so the MIB is
released at the same time as the IEEE 802 standard it addresses.  I think the
current approach with the hubmib WG development of the Power Over Ethernet MIB
is a good example of this.

Les...





"Pape, Bruno" <bpape@enterasys.com> on 22/03/2002 19:21:02

Sent by:  "Pape, Bruno" <bpape@enterasys.com>


To:   "'stds-802-1 @ieee.org'" <stds-802-1@ieee.org>
cc:    (Les Bell/GB/3Com)
Subject:  FW: 802.1x and TimeTicks






-----Original Message-----
From: Laurence, Francis (Joe)
Sent: Friday, March 22, 2002 2:21 PM
To: Pape, Bruno
Subject: RE: 802.1x and TimeTicks

Bruno,
   You might want to forward your message to the standards mailer for the
IEEE802.1
   group that created the standard. They are pretty good at answering
questions regarding
   the standards that they create.

The address is :
            stds-802-1@ieee.org <mailto:stds-802-1@ieee.org>

Joe L.

-----Original Message-----
From: Pape, Bruno
Sent: Friday, March 22, 2002 1:48 PM
To: mibcommittee
Subject: 802.1x and TimeTicks

It looks like the IEEE8021-PAE-MIB attempts to redefine TimeTicks in
its definition of dot1xAuthSessionTime.  The Net-SNMP code interprets
TimeTicks as per SNMPv2-SMI.  I would propose that we resolve the
conflict in favor of the SNMPv2-SMI definition of TimeTicks.  This would
apply to etsysDot1xAuthSessionTime in enterasys-8021x-extensions-mib.txt
as well.

Anyone feel like taking this up with the IEEE?

Thanks,

Bruno


From http://cvsmibs/cgi-bin/cvsweb.cgi/standards/ieee/IEEE8021-PAE-MIB
<http://cvsmibs/cgi-bin/cvsweb.cgi/standards/ieee/IEEE8021-PAE-MIB>

dot1xAuthSessionTime OBJECT-TYPE
    SYNTAX TimeTicks
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
               "The duration of the session in seconds."
    REFERENCE  "9.4.4, Session Time"
    ::= { dot1xAuthSessionStatsEntry 7 }

And from http://cvsmibs/cgi-bin/cvsweb.cgi/standards/ietf/SNMPv2-SMI
<http://cvsmibs/cgi-bin/cvsweb.cgi/standards/ietf/SNMPv2-SMI>

-- hundredths of seconds since an epoch
TimeTicks ::=
    [APPLICATION 3]
        IMPLICIT INTEGER (0..4294967295)