RFC 3339: The Internet’s Clock

If you’ve ever looked at a JSON API or a log file, you’ve likely seen a timestamp like `2024-04-05T15:30:00Z`. This format is defined by RFC 3339, a refined "profile" of the broader ISO 8601 standard specifically designed for use on the internet.

ISO 8601 vs. RFC 3339

While ISO 8601 is extremely flexible (allowing for week numbers, ordinal dates, and even "truncated" dates), the internet needed something stricter. RFC 3339 was created in 2002 to ensure that all internet-connected systems could parse timestamps unambiguously.

Key Stricter Rules

• Four-Digit Years: RFC 3339 requires the full four-digit year (YYYY).
• Complete Time: It requires the time to be included, down to at least the second.
• Time Offsets: It requires a timezone offset (like `+05:30`) or the letter `Z` for UTC.
• The 'T' Separator: While ISO 8601 allows the 'T' to be omitted in some cases, RFC 3339 strongly encourages its use as a separator.

Why It Matters

RFC 3339 is the default format for almost all modern web technologies, including:

• Webhooks: GitHub, Stripe, and Discord use RFC 3339 for their event timestamps.
• RSS/Atom Feeds: The `updated` and `published` tags in news feeds rely on this format.
• Certificates: The validity period of SSL/TLS certificates is defined using RFC 3339-compliant strings.

Conclusion

RFC 3339 is the "contract" between different software systems. It ensures that when one computer says "now," every other computer knows exactly which millisecond it means. On the Epoch Clock, we deal in integers, but RFC 3339 is how we talk about those integers in human-readable terms.