[stir] Benjamin Kaduk's No Objection on draft-ietf-stir-enhance-rfc8226-04: (with COMMENT)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Sat, 03 July 2021 17:50 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: stir@ietf.org
Delivered-To: stir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A5CAF3A1E45; Sat, 3 Jul 2021 10:50:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-stir-enhance-rfc8226@ietf.org, stir-chairs@ietf.org, stir@ietf.org, rjsparks@nostrum.com, ben@nostrum.com, ben@nostrum.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.34.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <162533462765.18440.5054449553859461793@ietfa.amsl.com>
Date: Sat, 03 Jul 2021 10:50:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/o6Nc9peIWwrOt5SRPKVTha2wcmg>
Subject: [stir] Benjamin Kaduk's No Objection on draft-ietf-stir-enhance-rfc8226-04: (with COMMENT)
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jul 2021 17:50:28 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-stir-enhance-rfc8226-04: 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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


Thanks for the updates in the -04; they address all my comments well.

Just one editorial note on the new Section 6:

   On the other hand, if the situation does not call for mustExclude
   constraints, then either the EnhancedJWTClaimConstraints extension or
   the JWTClaimConstraints extension can express the constraints.  Until
   such time as the EnhancedJWTClaimConstraints become widely

For singular/plural match, I think "becomes" is better.
I'd also consuder "such time as support for the EnhancedJWTClaimConstraints
extension becomes widely implemented".

   implemented, the use of the JWTClaimConstraints extension may be more
   likely to be implemented.  This guess is based on the presumption

"use of ... may be more likely to be implemented" is an unusual construction.
I think "use of ... may be more likely to succeed" or "the [extension] may
be more likely to be implemented" would be more typical.

   that the first specified extension will be implemented more widely in
   the next few years.