Skip to content
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.

Sign up for GitHub

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

Changes resulting from John Scudder's IESG review #63

Merged
merged 2 commits into from
Oct 19, 2023
Merged

Changes resulting from John Scudder's IESG review #63

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
58fa5d0
Make BCP178-related requirement a lower-case "must"
cabo Oct 19, 2023
88e6650
Explain the meaning of critical/elective in Fig 1/2 examples
cabo Oct 19, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions draft-ietf-sedate-datetime-extended.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}

Expand Down Expand Up @@ -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]
Expand All @@ -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]
Expand Down
Loading