From 58fa5d068d261a07652b280afcda270ace117eb7 Mon Sep 17 00:00:00 2001 From: Carsten Bormann Date: Thu, 19 Oct 2023 11:14:33 +0200 Subject: [PATCH 1/2] Make BCP178-related requirement a lower-case "must" --- 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 ab3d6ed..4379fa0 100644 --- a/draft-ietf-sedate-datetime-extended.md +++ b/draft-ietf-sedate-datetime-extended.md @@ -476,7 +476,7 @@ in controlled environments and cannot be registered; such keys MUST NOT be used for interchange and MUST be rejected by implementations not specifically configured to take part in such an experiment. See {{BCP178}} for a discussion about the danger of experimental keys -leaking out to general production and why that MUST be prevented. +leaking out to general production and why that must be prevented. ## Optional Generation, Elective vs. Critical Consumption {#optionally-critical} From 88e6650f8131b918c63a42da30fcbaad82512f0b Mon Sep 17 00:00:00 2001 From: Carsten Bormann Date: Thu, 19 Oct 2023 11:28:38 +0200 Subject: [PATCH 2/2] Explain the meaning of critical/elective in Fig 1/2 examples --- draft-ietf-sedate-datetime-extended.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/draft-ietf-sedate-datetime-extended.md b/draft-ietf-sedate-datetime-extended.md index 4379fa0..fb8dc68 100644 --- a/draft-ietf-sedate-datetime-extended.md +++ b/draft-ietf-sedate-datetime-extended.md @@ -590,7 +590,10 @@ and/or programmed behavior. For example, the IXDTF timestamps in {{example-inconsistent}} represent 00:14:07 UTC, indicating a local time with a `time-offset` of +00:00. However, because Europe/London used offset +01:00 in July 2022, the -timestamps are inconsistent: +timestamps are inconsistent in {{example-inconsistent}}, where the first +case is one where the application MUST act on the inconsistency (the +time zone suffix is marked critical), and the second case is one where +it MAY act on it (time zone suffix is elective). 2022-07-08T00:14:07+00:00[!Europe/London] 2022-07-08T00:14:07+00:00[Europe/London] @@ -605,7 +608,11 @@ inconsistent because they do not assert any particular local time nor local offset in their {{RFC3339}} part. Instead, applications that receive these strings can calculate the local offset and local time using the rules of the time zone suffix, -such as Europe/London in the example below. +such as Europe/London in the example in {{example-consistent}}, which +like {{example-inconsistent}} has a case with a time zone suffix marked +critical, i.e., the intention is that the application must understand +the time zone information, and one marked elective, which then only is +provided as additional information. 2022-07-08T00:14:07Z[!Europe/London] 2022-07-08T00:14:07Z[Europe/London]