[Sedate] John Scudder's No Objection on draft-ietf-sedate-datetime-extended-10: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Wed, 18 October 2023 19:18 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sedate@ietf.org
Delivered-To: sedate@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DACAC14CE27; Wed, 18 Oct 2023 12:18:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sedate-datetime-extended@ietf.org, sedate-chairs@ietf.org, sedate@ietf.org, Mark@internetpolicyadvisors.com, Mark@internetpolicyadvisors.com
X-Test-IDTracker: no
X-IETF-IDTracker: 11.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <169765673756.38475.7646435180794176727@ietfa.amsl.com>
Date: Wed, 18 Oct 2023 12:18:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sedate/8ru2Ee94lt4aMzqkk_GxRcVcFIY>
Subject: [Sedate] John Scudder's No Objection on draft-ietf-sedate-datetime-extended-10: (with COMMENT)
X-BeenThere: sedate@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Serialising Extended Data About Times and Events <sedate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sedate>, <mailto:sedate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sedate/>
List-Post: <mailto:sedate@ietf.org>
List-Help: <mailto:sedate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sedate>, <mailto:sedate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Oct 2023 19:18:57 -0000

John Scudder has entered the following ballot position for
draft-ietf-sedate-datetime-extended-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sedate-datetime-extended/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for this easy-to-read document.

## COMMENTS

### Section 3.2, misused 2119 keyword

                                                    See
   [BCP178] for a discussion about the danger of experimental keys
   leaking out to general production and why that MUST be prevented.

That MUST is far afield from what RFC 2119 thinks it should be used for. Seems
like it should be "must".

### Section 3.4 examples are silent on handling the "critical" mark

Section 3.4 has two sets of examples. Each set is a pair, with the same
timestamp, but in one the tag is marked critical and in the other, it isn't.
The text doesn't say anything about the difference in handling the critical vs.
non-critical versions. I can see why you'd want the two versions -- IF you were
going to use them in the explanatory text, to illuminate the use of the
critical mark. But you don't. Seems like you should either talk about the
difference in how they're handled or just supply one version.

## LESS-THAN-NITS

Note that AFAICT every instance of “note that” in this document could be
deleted without loss of clarity, but this is purely a personal style matter.
(OK the one in §3.4 does serve the purpose of letting the sentence not begin
with "-00:00" which would be a little jarring.)