[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: DateAndTimeOrNull
> -----Original Message-----
> From: owner-mreview@ops.ietf.org
> [mailto:owner-mreview@ops.ietf.org]On Behalf Of
> j.schoenwaelder@iu-bremen.de
> Sent: 01 March, 2005 7:55 PM
> To: Romascanu, Dan (Dan)
> Cc: Mreview (E-mail); Lior khermosh
> Subject: Re: DateAndTimeOrNull
>
>
> On Tue, Mar 01, 2005 at 07:23:45PM +0200, Romascanu, Dan (Dan) wrote:
>
> > One of the MIB modules in the Ethernet Interfaces and Hub MIB WG
> > needs to use a TC that extends DateAndTime TC to DateAndTimeOrNull.
> > Beyond the RFC 2579 functionality, null would be filled in whenever
> > a clock is not available to the agent to provide
> DateAndTime information.
> >
> > We believe that there may be a broader usage for such a TC
> beyond other WG.
> >
> > I found some traces of a previous discussion - did it ever
> result in
> > defining such a TC some place?
>
> DateAndTime just works fine. It has been used quite a bit in MIBs to
> represent a NULL value and a clarification on this has been posted
> after quite some discussion as an errata to RFC 2579 which legalizes
> the usage of a value which entirely consists of zeros as a NULL value.
Can you point us to this errata? Thanks, Dan
>
> /js
>
> --
> Juergen Schoenwaelder International University Bremen
> <http://www.eecs.iu-bremen.de/> P.O. Box 750 561,
> 28725 Bremen, Germany
>
>
- Follow-Ups:
- Re: DateAndTimeOrNull
- From: =?unknown-8bit?b?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@iu-bremen.de>