[Id-event] John Scudder's No Objection on draft-ietf-secevent-subject-identifiers-15: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Tue, 14 February 2023 01:00 UTC

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-secevent-subject-identifiers@ietf.org, secevent-chairs@ietf.org, id-event@ietf.org, yaronf.ietf@gmail.com, yaronf.ietf@gmail.com
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <167633644399.43553.1011885148385794866@ietfa.amsl.com>
Date: Mon, 13 Feb 2023 17:00:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/b9l5QwujYFlJQeuxa0k35qiZkms>
Subject: [Id-event] John Scudder's No Objection on draft-ietf-secevent-subject-identifiers-15: (with COMMENT)

John Scudder has entered the following ballot position for
draft-ietf-secevent-subject-identifiers-15: 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-secevent-subject-identifiers/



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

Thanks for this very readable and thorough document. I have two minor comments.

- the BCP 14 boilerplate is supposed to (normatively) reference RFC 8174 as well as RFC 2119.
- “contain a uri members” -> “contain a uri member” (agreement in number)

[Id-event] John Scudder's No Objection on draft-i… John Scudder via Datatracker