[Sidrops] Re: Mahesh Jethanandani's No Objection on draft-ietf-sidrops-rpki-crl-numbers-04: (with COMMENT)
Job Snijders <job@sobornost.net> Wed, 21 May 2025 08:06 UTC
Return-Path: <job@instituut.net>
X-Original-To: sidrops@mail2.ietf.org
Delivered-To: sidrops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id EE9A92B14B48 for <sidrops@mail2.ietf.org>; Wed, 21 May 2025 01:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5jzi3XvNVMF for <sidrops@mail2.ietf.org>; Wed, 21 May 2025 01:06:52 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id ABBC52B14B34 for <sidrops@ietf.org>; Wed, 21 May 2025 01:06:52 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id 98e67ed59e1d1-30e5430ed0bso6434396a91.3 for <sidrops@ietf.org>; Wed, 21 May 2025 01:06:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20230601.gappssmtp.com; s=20230601; t=1747814812; x=1748419612; darn=ietf.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=cV8LcPRroY4LUvXOiIr16PwUuKhHxh98gpqu7A2Mdmw=; b=P7OxWK0McwKq7pfVsxNnxj2qNAfX19JSUlAB7jg34e30an1p3eTwAqRtI+xKrPQjX9 CM56ecfF2o+UvDBdfbwwEH6XB0a1Bh+KhJtLKWJijFnc0nTJNxg58SP6lpGsr5M2L+Iq uNc/SFhLzkynbBM+wYqgRLAYv0S+AC2ENw2lzbvUNvbfA7Hn8PSEo9mZNH5xmETy3Aa9 CqcXarFwH0+nJg8+Ot7EVv9hTQKMp4xhPN6SyHs74lWXhu/IFm8XAYj3TDK5wiWoR4UI a9xFEH/Fy+AsouwXWP29e7p3VHquRP1mWR6Er7zmqiy5Srl8ZXeFThUMOFQlNuA9eXPg Ov3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747814812; x=1748419612; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=cV8LcPRroY4LUvXOiIr16PwUuKhHxh98gpqu7A2Mdmw=; b=WS1LZnhyGVp8L7LKtaf0sZF+eQG6kSmUXGK33xg5UsaXQQXdrgnUCgPzEUPuy3Tzlw 6RoKDiglgLUr2QX+nGJNDS4NTbgNrUCq49JROofwlX/flvag1WTm3eF96db9Uo9yiErf CcJ1i02HlabO4HZL1HcRO7SeTpzOe0kaTkQJzcuaaftUIrDL/wIeiMfvjkg31s8479py 5rCf+kB0J5ghPHUGjvf2BSkU9h15FIygLkoZaawx0V4kgIgrnpyQIXe6OYu4oVTJn/mG afhD3GbR1j+mtuo12kZtRLMqjV5LgVeoxJ1Eu869KOZjoMMIhCrpS9wRJe2PV7vYqfL1 LZkw==
X-Forwarded-Encrypted: i=1; AJvYcCVACn6qqwLmtDjlvSfha0w6s/WtmM5B1Ssmt8MUC1sJvqo3YFlYi+qH3eabOgZdSnfE9AUpfNeF@ietf.org
X-Gm-Message-State: AOJu0Yx+xnONa35Mq2MbrSBqxxeJzRU1sLhtYMrK8DDMgo0SNvLtJ9v0 a8KLsvuaBFAKmOyQJtk1y4pjyz1WKOijMxM1EWR9aN2Uvis8YBZmHBFPn5v3HIW3me0=
X-Gm-Gg: ASbGncsMEtFkT/vkm5CLsagRNCrq6/CIuy/Ly9zncy9/9gRpM3FrqlQj2B7kwD6B3sY YFI0BiMKaulREOUcrZNR/yG/VgPxU4QCZN8o6vHnCy9J6nR5XjT2w8sm2GdLTVKguQDYPzthaTw T3ZggmY0NV34yqxul9O2lzTTAthpPzxE+SHG2k+QMcwUqfI20MkgAc4ab6++7Pnc7RYpe/NJLXp uhwmic3AOb7r6o38WVH7AiW/XjNVv65SxxY5stiDTW64VK8NNZabXoWhoXBR1WlSxdaHXKw0HbV S636k4oPxZYPooYg6Y4I8XlkEcXc5hh+zNObTCvED7s0U5GJHobgHy6Uu7uoTnFw2WTaYqS+6Vh etV4bESkYCQ==
X-Google-Smtp-Source: AGHT+IGSubIbK5s7jU9/QTFJK4XwhVGMGjV6ovZde2j6H32ruj0jzz+xssQMbwivoa0eMWFMUgBu0g==
X-Received: by 2002:a17:90b:3d50:b0:2ee:db1a:2e3c with SMTP id 98e67ed59e1d1-30e830ca007mr25523758a91.1.1747814811543; Wed, 21 May 2025 01:06:51 -0700 (PDT)
Received: from feather.sobornost.net (fp5a95b782.narj007.ap.nuro.jp. [90.149.183.130]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-b26eaf6e609sm9184251a12.19.2025.05.21.01.06.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 May 2025 01:06:50 -0700 (PDT)
Date: Wed, 21 May 2025 08:06:46 +0000
From: Job Snijders <job@sobornost.net>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-ID: <aC2JliDt4mprTCW5@feather.sobornost.net>
References: <174770944105.485278.1618636493397390933@dt-datatracker-59b84fc74f-84jsl> <aCwGpx-5a28zP66h@theobuehler.org> <5068A297-DFC7-442F-B93D-6ADAD803088B@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5068A297-DFC7-442F-B93D-6ADAD803088B@gmail.com>
X-Clacks-Overhead: GNU Erik Bais
Message-ID-Hash: NK75XMYEJYCPAY65CQHUU5Q7WJP2XJXE
X-Message-ID-Hash: NK75XMYEJYCPAY65CQHUU5Q7WJP2XJXE
X-MailFrom: job@instituut.net
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: Theo Buehler <tb@theobuehler.org>, The IESG <iesg@ietf.org>, draft-ietf-sidrops-rpki-crl-numbers@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org, Russ Housley <housley@vigilsec.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sidrops] Re: Mahesh Jethanandani'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/ncoda29CQMDI0S1jHS21gfjvNro>
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>
Dear all, On Tue, May 20, 2025 at 09:51:57PM -0700, Mahesh Jethanandani wrote: > > On May 19, 2025, at 9:35 PM, Theo Buehler <tb@theobuehler.org> wrote: > > > >>> | Per Section 5.2.3 of [RFC5280], CAs issue new CRLs using a > >>> | monotonically increasing sequence number in the "CRL Number" > >>> | extension. It is RECOMMENDED that the "CRL Number" matches the > >>> | "manifestNumber" of the manifest that will include this CRL > >>> | (see Section 4.2.1 of [RFC9286]). > >> > >> Maybe this is covered somewhere else, but reading the last sentence of the NEW > >> I wonder what happens when the CRL Number does NOT match the manifestNumber. Is > >> the session aborted? Does it fall back to previous behavior, i.e., checking the > >> highest value of CRL Number. Some clarity would help. > > > > The I-D specifies that the crlNumber be ignored. Checking whether it > > matches the manifestNumber or not is not ignoring it :) > > I think Deb had a similar comment … > > The draft says “It is RECOMMENDED” that the ‘CRL Number’ matches the > ‘manifestNumber’. The question was, what happens when “CRL Number” > does not match the “manifestNumber”? Nothing happens. As this document attempts to clarify: Relying Parties ignore the CRL Number value. The RP discards the CRL Number value, the value does not impact the decision making process on the RP side, it simply is not considered (whether it matches the manifestNumber or not). (For historical reasons,) RPKI Issuers must include _some_ CRL Number (which can be any number); in turn Relying Parties merely check whether the extension is present and validly encoded, but otherwise ignore it. Seeing that multiple reasonable people now have gotten distracted by this particular sentence, I see two paths forward: Option 1) REMOVE this sentence: "It is RECOMMENDED that the "CRL Number" matches the "manifestNumber" of the manifest that will include this CRL (see Section 4.2.1 of [RFC9286])." Option 2) REPHRASE ... but how? Its just a recommendation. "You *have* to pick a color, we recommend picking the same color as this other thing over there because it's implementation-wise perhaps simpler." However - in attempting to rephrase, we risk that our continued rubbing makes this stain in the carpet worse and worse... My preference is option 1 - just remove it, but if people know of a sentence that conveys a recommendation what value to use without causing confusion I'm all ears! Let me know Kind regards, Job
- [Sidrops] Mahesh Jethanandani's No Objection on d… Mahesh Jethanandani via Datatracker
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Theo Buehler
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Mahesh Jethanandani
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Job Snijders
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Ketan Talaulikar
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Job Snijders
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Ketan Talaulikar
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Deb Cooley
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Job Snijders
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Deb Cooley
- [Sidrops] Re: Mahesh Jethanandani's No Objection … mohamed.boucadair
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Martin Hoffmann
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Tim Bruijnzeels
- [Sidrops] Re: Mahesh Jethanandani's No Objection … Job Snijders