On 2023-04-24, at 14:20, Michal Vasko <[email protected]> wrote: > > canonical
Hi Michal, I don’t know what exactly “canonical” means here. As a general rule, timestamps used by machines should not use timezones, so you should use 2023-02-22T22:00:00Z If there is a use for indicating the timezone offset a particular system was in when the timestamp actually occurred, then you might indicate that with a timezone offset: 2023-02-23T11:00:00+13:00 The point in time at which you formatted this datetime is never relevant. I’m having a hard time imagining when you want to supply this hint at an individual timestamp level — I would believe these all should be without timezone offsets, i.e., Z. Your system information might usefully have timezone information (see also below), if timezone is at all relevant to your system. Note that if you have additional information (“hints”) that you want to send with the actual timestamp, you probably want to know about SEDATE’s IXDTF: https://www.ietf.org/archive/id/draft-ietf-sedate-datetime-extended-07.html I don’t know when YANG will pick this up; I don’t know how important these hints are in management information (and that my uncertainty applies to using the timezone offset defined by RFC 3339 in YANG as well). Grüße, Carsten _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
