[DNSOP] Orie Steele's No Objection on draft-ietf-dnsop-rfc8624-bis-09: (with COMMENT)

Orie Steele via Datatracker <noreply@ietf.org> Mon, 19 May 2025 20:25 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from [10.244.8.226] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id BE5F82A666FC; Mon, 19 May 2025 13:25:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Orie Steele via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.40.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174768631165.485945.17542801112153835514@dt-datatracker-59b84fc74f-84jsl>
Date: Mon, 19 May 2025 13:25:11 -0700
Message-ID-Hash: RIEVDDBBPDAMOIRPB5BSWCD3AACCMGP6
X-Message-ID-Hash: RIEVDDBBPDAMOIRPB5BSWCD3AACCMGP6
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-dnsop-rfc8624-bis@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Orie Steele <orie@or13.io>
Subject: [DNSOP] Orie Steele's No Objection on draft-ietf-dnsop-rfc8624-bis-09: (with COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/h9lwziZXy2cYCIq7cX65afTplAA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

Orie Steele has entered the following ballot position for
draft-ietf-dnsop-rfc8624-bis-09: 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-dnsop-rfc8624-bis/



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

# Orie Steele, ART AD, comments for draft-ietf-dnsop-rfc8624-bis-09
CC @OR13

* line numbers:
  -
  https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-dnsop-rfc8624-bis-09.txt&submitcheck=True

* comment syntax:
  - https://github.com/mnot/ietf-comments/blob/main/format.md

* "Handling Ballot Positions":
  - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/

## Comments

Thanks to Barry Leiba for the ARTART review.

### Guidance to DEs for divergence?

```
268        and "use".  We note that the values for "Implement for" and "Use for"
269        may diverge in the future
```

The divergence that is expected here is probably that there will be more
implementation than use, right?

Some additional guidance to DEs might be helpful here.

## Nits

### KSK expand on first use.

```
391        Upgrading algorithm at the same time as rolling the new KSK key will
```