Re: [Cbor] Roman Danyliw's No Objection on draft-ietf-cbor-time-tag-11: (with COMMENT)

[Carsten Bormann <[e-mail]>]

Hi Roman,

thank you for this review.
Changes that should address these COMMENTS are in
https://github.com/cbor-wg/time-tag/pull/26

Details please see below.

Grüße, Carsten


> On Oct 23, 2023, at 17:13, Roman Danyliw via Datatracker <[e-mail]> wrote:
> 
> Roman Danyliw has entered the following ballot position for
> draft-ietf-cbor-time-tag-11: No Objection
> ]
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-cbor-time-tag/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> ** Section 2.
>   For example, map keys could be registered for direct representations
>   of natural platform time formats.
> 
> What are “natural platform time formats”?

Something like the POSIX-Epoch-(1970-)based tv_sec/tv_nsec pair that UNIX uses (well, we cover that with keys 1/-9), or Windows’s 100-nanosecond intervals since January 1, 1601, which were in turn derived from VMS quadword time (100ns "ticks” since "Smithsonian Base Time”, i.e., 17-Nov-1858 00:00:00).  Java’s milliseconds from the POSIX Epoch has also been mentioned (which can already be covered employing key 4).

> ** Section 3.
>   The map must contain exactly one unsigned integer key that specifies
>   the "base time", and may also contain one or more negative integer or
>   text-string keys, which may encode supplementary information.
> 
> Should a normative MUST and MAY be used here?

Yes.

Now
3ad3548

> ** Section 8.
>   Time, of course, has significant security considerations; these
>   include the exploitation of ambiguities where time is security
>   relevant (e.g., for freshness or in a validity span) or the
>   disclosure of characteristics of the emitting system (e.g., time
>   zone, or clock resolution and wall clock offset).
> 
> Recommend citing the Security Considerations of
> draft-ietf-sedate-datetime-extended.  The text there covers a number of the
> topics mentioned above.

Yes.

Now
ab7edc7