RE: MIB Counters discontinuity

["Nagi Reddy Jonnala \(njonnala\)" <njonnala@cisco.com>]

Sounds good and thanks to all of you. We'll address this issue in the
next revision.

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org]
On Behalf Of Nelson, David
Sent: Tuesday, March 21, 2006 1:08 AM
To: radiusext@ops.ietf.org
Subject: RE: MIB Counters discontinuity

Bert Wijnen writes...

> From your story, it seems to me that
> you need your own Discontinuity Timer.

I was discussing this issue with Dave Harrington, over lunch.  Dave
concurred with the suggestion that these MIBs contain their own
discontinuity timestamp, rather than relying on the sysUpTime object or
using sysORUpTime.

It should be sufficient for each RADIUS client entity or server entity
to maintain a single up time.


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>