From d3da316deeb4ae2508054d7349511095047f6ae3 Mon Sep 17 00:00:00 2001 From: cabo Date: Mon, 16 Oct 2023 17:41:42 +0200 Subject: [PATCH] =?UTF-8?q?held=20back=20=E2=9E=94=20compromised?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- draft-ietf-sedate-datetime-extended.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-sedate-datetime-extended.md b/draft-ietf-sedate-datetime-extended.md index 43b0bb7..9f2d99a 100644 --- a/draft-ietf-sedate-datetime-extended.md +++ b/draft-ietf-sedate-datetime-extended.md @@ -369,7 +369,7 @@ in email headers, described in {{Section 3.3 of RFC5322}} and introduced earlier in {{Section 3.3 of RFC2822}}. This email header convention is in actual use, while its adaptation into {{RFC3339}} always was -held back by the fact that {{ISO8601-2000}} and later versions do not actually allow `-00:00`. +compromised by the fact that {{ISO8601-2000}} and later versions do not actually allow `-00:00`. Implementations that needed to express the semantics of `-00:00` therefore tended to use `Z` instead.