-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ISO8601 or RFC3339 for creation/expiration dates? #2
Comments
I've used RFC 3339 in all of my stuff. For binary formats I use TAI64N. |
I'd rather not have something which requires understanding timezones and DST in order to compare dates, as that's a good way to have different components of a system interpreting a given timestamp differently (for instance, even with the same implementation of biscuit, you could disagreements between systems using a different version of TAI64 (and TAI64N) have the advantage of simplicity: it is nigh-impossible to fuck up the timestamp comparison, as it is pretty-much just integer comparison. |
TAI64N seems sensible indeed (as long as the biscuit libraries give an ergonomic way to specify durations). |
RFC 3339 might be simpler
The text was updated successfully, but these errors were encountered: