[Sidrops] Deb Cooley's No Objection on draft-ietf-sidrops-rpki-crl-numbers-04: (with COMMENT)

Deb Cooley via Datatracker <noreply@ietf.org> Tue, 20 May 2025 13:08 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@mail2.ietf.org
Received: from [10.244.8.226] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 9117B2AAC83C; Tue, 20 May 2025 06:08:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Deb Cooley 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: <174774652148.480395.8429074922360546375@dt-datatracker-59b84fc74f-84jsl>
Date: Tue, 20 May 2025 06:08:41 -0700
Message-ID-Hash: 2LRG3LLGSBF3DTJRUFMMRYKOZNHF7S2W
X-Message-ID-Hash: 2LRG3LLGSBF3DTJRUFMMRYKOZNHF7S2W
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-sidrops-rpki-crl-numbers@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org, housley@vigilsec.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Deb Cooley <debcooley1@gmail.com>
Subject: [Sidrops] Deb Cooley's No Objection on draft-ietf-sidrops-rpki-crl-numbers-04: (with COMMENT)
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/Vbtm1Sb0IcFSaGx9Nkp6aq7d4tU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

Deb Cooley has entered the following ballot position for
draft-ietf-sidrops-rpki-crl-numbers-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/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-sidrops-rpki-crl-numbers/



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

Thanks to Nancy Cam-Winget for their secdir reviews.

Section 5:  List RFC 9286 here. It appears that it is the RFC which requires
manifestNumber to be strictly increasing.

Section 5:  Can a short paragraph be added discussing the issues associated
with either the 'CRL Number' not matching the 'manifestNumber' (currently only
RECOMMENDED) and/or the issue of not ignoring a CRL Number if and when it
doesn't match the 'manifestNumber'.  Nothing too long, just a short note that
outlines the issues.  I can help with the words for this, if that would help.