BinaryTime: An Alternate Format for Representing Date and Time in ASN.1
RFC 4049
Yes
No Objection
Recuse
Note: This ballot was opened for revision 02 and is now closed.
(Alexey Melnikov; former steering group member) Yes
(Jari Arkko; former steering group member) Yes
A reference to POSIX spec or the term "UNIX time" would be useful for clarity -- I had to look up whether the definitions are the same here and there. (Both DO skip leap seconds but I didn't remember if that was indeed the case.) This could be added as an RFC Editor note.
(Sean Turner; former steering group member) Yes
(Tim Polk; former steering group member) Yes
(Adrian Farrel; former steering group member) No Objection
Section 5 says
However, if both of these attributes are
present, they MUST provide the same date and time.
Wouldn't it be helpful to say what should be done if they do not provide the same date and time?
---
Let is be a lesson to all writers and reviewers of I-Ds. The Abstract says:
This document specifies a new ASN.1 type
This is no longer true; the novelty has worn off.
(Dan Romascanu; former steering group member) No Objection
(David Harrington; former steering group member) No Objection
(Gonzalo Camarillo; former steering group member) No Objection
(Peter Saint-Andre; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Stewart Bryant; former steering group member) No Objection
(Russ Housley; former steering group member) Recuse