FddiTime, and update to Path config table

Anil Rijsinghani <anil@levers.enet.dec.com> Tue, 21 July 1992 19:04 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa06550; 21 Jul 92 15:04 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa06546; 21 Jul 92 15:04 EDT
Received: from CS.UTK.EDU by NRI.Reston.VA.US id aa22440; 21 Jul 92 15:07 EDT
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA14497; Tue, 21 Jul 92 14:24:19 -0400
Received: from inet-gw-2.pa.dec.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA14493; Tue, 21 Jul 92 14:24:15 -0400
Received: by inet-gw-2.pa.dec.com; id AA02635; Tue, 21 Jul 92 11:24:12 -0700
Received: by us1rmc.bb.dec.com; id AA29210; Tue, 21 Jul 92 14:22:27 -0400
Message-Id: <9207211822.AA29210@us1rmc.bb.dec.com>
Received: from levers.enet; by us1rmc.enet; Tue, 21 Jul 92 14:22:41 EDT
Date: Tue, 21 Jul 1992 14:22:41 -0400
From: Anil Rijsinghani <anil@levers.enet.dec.com>
To: fddi-mib@cs.utk.edu
Cc: anil@levers.enet.dec.com
Apparently-To: fddi-mib@cs.utk.edu
Subject: FddiTime, and update to Path config table

    A small update on the Path Config Table I sent out last week:
    the PATHConfResourceCurPath is an enumerated type now,
    and should be one of: isolated(1), local(2), secondary(3), primary(4),
    concatenated(5), thru(6).

    On a different topic: at the meeting last week, we spoke about
    possibly going to a more usable time unit than 80 nsec units.
    After speaking with some people here, it appears that 1 microsecond
    units would be both more readable and sufficiently granular for all
    objects that use this syntax.  Unless there are objections, I
    propose that FddiTime be changed to 1 usec units.

    thanks,
    Anil