Re: ITC copped out on UTC again

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi -

> From: "Michael Richardson" <mcr@xxxxxxxxxxxx>
> To: "Phillip Hallam-Baker" <hallam@xxxxxxxxx>
> Cc: "IETF Discussion Mailing List" <ietf@xxxxxxxx>
> Sent: Friday, January 20, 2012 10:13 AM
> Subject: Re: ITC copped out on UTC again
...
> Can you tell me which protocols use future timestamps in an moving form
> (not stored at rest in a certificate in a DANE RR, for instance), which
> care about discrepancies of less than 1 minute?

The disman Scheduling MIB (RFC 3231) has future timestamps. They
are defined as dates / times, with provision for how discontinuities
in civil time (whether due to "summer time", time zone changes, or leap
seconds) are to be handled.  This definition makes it unlikely that
a sane developer would internally represent them as computed
intervals.  Leap second handling is a big non-issue in SNMP-land,
as far as I know.

Randy

_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]