Sorry: RFC6019, not 6013. Poul-Henning
In message <[email protected]>, "Poul-Henning Kamp" writes: > >Btw, forgot to mention here that RFC6013 > BinaryTime: > An Alternate Format for Representing Date and Time in ASN.1 > >Adopts/gold-plates the POSIX timestamp: > > The syntax for BinaryTime is: > > BinaryTime ::= INTEGER (0..MAX) > > The integer value is the number of seconds, excluding leap seconds, > after midnight UTC, January 1, 1970. This representation of time is > sometimes called "UNIX time" [POSIX]. This time format cannot > represent time values prior to January 1, 1970. The latest UTC time > value that can be represented by a four-octet integer value is > 03:14:07 on January 19, 2038, which is represented by the hexadecimal > value 7FFFFFFF. Time values beyond 03:14:07 on January 19, 2038, are > represented by integer values that are longer than four octets, and a > five-octet integer value is sufficient to represent dates covering > the next seventeen millennia. > > >-- >Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >[email protected] | TCP/IP since RFC 956 >FreeBSD committer | BSD since 4.3-tahoe >Never attribute to malice what can adequately be explained by incompetence. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ LEAPSECS mailing list [email protected] http://six.pairlist.net/mailman/listinfo/leapsecs
