RFC 8794, "Extensible Binary Meta Language", July 2020

Note: This RFC has been updated by RFC 9559

Errata ID: 7192
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Steve Lhomme
Date Reported: 2022-10-30

Section 7.6. says:

   The Date Element stores an integer in the same format as the Signed
   Integer Element that expresses a point in time referenced in
   nanoseconds from the precise beginning of the third millennium of the
   Gregorian Calendar in Coordinated Universal Time (also known as
   2001-01-01T00:00:00.000000000 UTC).  This provides a possible
   expression of time from 1708-09-11T00:12:44.854775808 UTC to
   2293-04-11T11:47:16.854775807 UTC.

It should say:

   The Date Element stores an integer in the same format as the Signed
   Integer Element that expresses a point in time referenced in
   nanoseconds from the precise beginning of the third millennium of the
   Gregorian Calendar in Coordinated Universal Time (also known as
   2001-01-01T00:00:00.000000000 UTC).  This provides a possible
   expression of time from September 1708 to April 2293.

   The integer stored represents the number of nanoseconds between the
   date to express and 2001-01-01T00:00:00.000000000 UTC, not counting
   leap seconds.  That is 86,400,000,000,000 nanoseconds for each day.
   Conversions from other date systems should ensure leap seconds are
   not counted in EBML values.

   The 2001-01-01T00:00:00.000000000 UTC date also corresponds to
   978307200 seconds in Unix time [POSIX].

Notes:

Add some notice about leap seconds not being counted as in POSIX. Remove bogus nanosecond values.

See https://github.com/ietf-wg-cellar/ebml-specification/pull/415

Report New Errata