[Sidrops] Re: Notification for draft-spaghetti-sidrops-rpki-ta-tiebreaker
Tim Bruijnzeels <tbruijnzeels@ripe.net> Thu, 20 June 2024 08:33 UTC
Return-Path: <tbruijnzeels@ripe.net>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC9AC15198D for <sidrops@ietfa.amsl.com>; Thu, 20 Jun 2024 01:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ripe.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qxoyUp_BVqwK for <sidrops@ietfa.amsl.com>; Thu, 20 Jun 2024 01:33:07 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10C12C151549 for <sidrops@ietf.org>; Thu, 20 Jun 2024 01:33:07 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-a63359aaacaso76918866b.1 for <sidrops@ietf.org>; Thu, 20 Jun 2024 01:33:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ripe.net; s=google1; t=1718872385; x=1719477185; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=A+S1Tv7lC3GtLcuOiS5D7ZqBZGvJuRaqk8sjzvrw4os=; b=Fa7FWmfp9RG7vB0xYJlByzwXMFEEr3U3zR4lO9EDVx61aPJObVBqNShMkNQ+BkHo15 W2meLrj0q3dbg5ZYi0LEzHNC6SOucy5L6Olr0PE1MXy14NEqufE0imxxZx5UVUsaqXqV iFLIOcqWDiFEsyAkFbmrZ0k/hGvKBVphO+vydlJ3lPKe+5+R3H6MZ/SNtYmQfnaDm8f9 6vV/KrOBlakwGi/yY0N9z0XEuD/0vNHCiyn0iFKqzmfWzCUSql9/HdV7M2q2oGFNIRiY /vX0nZs7i/4+rukHmzhe+hjSts7blP+5DJ7pzPsvTmpk3z1OXG8TmM9FBhPjVfX7eqJY k1qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718872385; x=1719477185; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=A+S1Tv7lC3GtLcuOiS5D7ZqBZGvJuRaqk8sjzvrw4os=; b=tjYTwPVTrg18PPnpCjoJc/jqXCdy4gfmFWttI/hT6CHj2u0SaZk+d4gcmYt4A85aVr Q8TjZtNh/38DXipHouRGvvrduVcHgoA62qPzPKHLQSTS6Vv3gJzKEYFu/We67ZHH8aR+ KKlK2OMhiaoXnKYAsDSmc5BgRa4q+UEzWPTrPqf7Z96H8aMwEuMlHdp+fc6vYLmoZS9k wliS31MCDN3XbVb8vyU+oGaP/y1//Sv2zjvUWDmu8nHOQepP+2R4O0Dz0NqJfr3WzwDi h3OZ3ZagDuB2l8WVM7U1PYE5FajLuDTh5We/SeTAGEL53I6Fbu4kL/O1HTCR5elUIjLN 3XPA==
X-Gm-Message-State: AOJu0Yw4UtSQa7/pHF5JZz3f/0PFJ4wxTbm8nYkKmrL3WQENScuFhI9l /gpmYt5LmqGfSFoqBMfc8D0rovTMehVhuKZ3NgwMHBoKeEXQSQn+rKuznLxyD3QDxVxHsZdSgwo C
X-Google-Smtp-Source: AGHT+IHMwAPePSEzJvFdcWtX8FE7E6ieKRfbOtbe8Qw7AwqZz8ant+5uTUBYIRbnlD48EQ1FXMDaaA==
X-Received: by 2002:a17:906:2b0e:b0:a69:67e3:57e6 with SMTP id a640c23a62f3a-a6fab77566bmr282444966b.49.1718872385311; Thu, 20 Jun 2024 01:33:05 -0700 (PDT)
Received: from smtpclient.apple ([109.37.128.68]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a6f8176eea5sm402199366b.88.2024.06.20.01.33.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jun 2024 01:33:05 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Tim Bruijnzeels <tbruijnzeels@ripe.net>
In-Reply-To: <ZnNtl9d7cnkMtK-1@snel>
Date: Thu, 20 Jun 2024 10:32:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <86AF7299-8541-4652-A699-33AED2F73A60@ripe.net>
References: <ZnNtl9d7cnkMtK-1@snel>
To: Job Snijders <job=40fastly.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: OFFJLKTL57PKNIZIKODFSTRJP42A2N56
X-Message-ID-Hash: OFFJLKTL57PKNIZIKODFSTRJP42A2N56
X-MailFrom: tbruijnzeels@ripe.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: sidrops@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Sidrops] Re: Notification for draft-spaghetti-sidrops-rpki-ta-tiebreaker
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/toBq9cJvM4yfGlveC2ARjo1rNrI>
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>
Hi Job, all, I am not convinced that this document should be written as a standards track update to RFC 8630, inserting additional steps in the way that it does. I believe that as written this is too implementation specific and if standardized imposes an implementation on other RPs that may not be optimal for them. That said, I agree with the goals that this document identifies. So please take the following as constructive feedback. I think this is better written as a separate document that explains how rpki-client applies a tie breaker between multiple candidate TA certificates that are each valid according to RFC 8630. This could be done as an informational draft describing rpki-client’s implementation of RFC 8630 section 3 step 4, or standards track - for the latter support from other RP implementers would be needed imo. For example, other RP implementation may choose to not only retrieve the TA certificates from the same URI over time, but pro-actively fetch them from any or all listed URIs on the TAL, perhaps once a hour/day/week/$time, or every validation run if they are really paranoid. Subject each of them to RFC 8630 validation as described, and *then* apply local tie breakers which may include this. Talking about tie breakers, what do you do in case you find multiple valid TA certificate with different sets of resources in the INR extension(s)? Union? Intersection? Pick one? I think, as written, rpki-client's implementation would pick the ‘most recent’ but what if there are multiple equally recent candidates? What do you do if equally recent TA certificates differ in their SIAs? I understand that you may consider these issues out of scope, but in that case I believe that calling them out as such would be useful. In short, I welcome discussion on tie breakers, but I think this could benefit from a broader discussion and only focussing on ‘most recent’ feels a bit arbitrary to me. As an informational draft that would still be okay - just document what you do - but for standards track I think we need that dicussion. Kind regards Tim > On 20 Jun 2024, at 01:45, Job Snijders <job=40fastly.com@dmarc.ietf.org> wrote: > > Dear SIDROPS, > > In context of Relying Parties maybe having acquired access to multiple > different valid issuances of a Trust Anchor certificate, Ties de Kock > pointed out potential issues relating to certification path validation. > > An implementation to demonstrate a tiebreaking scheme in the presence of > another TA certificate was instrumented in OpenBSD rpki-client, and we > documented our effort in this internet-draft. > > Your feedback is most welcome! > > Kind regards, > > Job > > ----- Forwarded message from internet-drafts@ietf.org ----- > > Date: Wed, 19 Jun 2024 16:11:54 -0700 > From: internet-drafts@ietf.org > To: Job Snijders <job@fastly.com>, Theo Buehler <tb@openbsd.org>, Ties de Kock > <tdekock@ripe.net> > Subject: New Version Notification for > draft-spaghetti-sidrops-rpki-ta-tiebreaker-00.txt > > A new version of Internet-Draft > draft-spaghetti-sidrops-rpki-ta-tiebreaker-00.txt has been successfully > submitted by Job Snijders and posted to the > IETF repository. > > Name: draft-spaghetti-sidrops-rpki-ta-tiebreaker > Revision: 00 > Title: Tiebreaking Resource Public Key Infrastructure (RPKI) Trust Anchors > Date: 2024-06-19 > Group: Individual Submission > Pages: 7 > URL: https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-ta-tiebreaker-00.txt > Status: https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rpki-ta-tiebreaker/ > HTML: https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-ta-tiebreaker-00.html > HTMLized: https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-rpki-ta-tiebreaker > > > Abstract: > > A Trust Anchor (TA) in the RPKI is represented by a self-signed X.509 > Certification Authority (CA) certificate. Over time, Relying Parties > (RP) may have acquired multiple different issuances of valid TA > certificates from the same TA operator. This document proposes a > tiebreaking scheme to be used by RPs to select one TA certificate for > certification path validation. This document updates RFC 8630. > > > > The IETF Secretariat > > > > ----- End forwarded message ----- > > _______________________________________________ > Sidrops mailing list -- sidrops@ietf.org > To unsubscribe send an email to sidrops-leave@ietf.org
- [Sidrops] Notification for draft-spaghetti-sidrop… Job Snijders
- [Sidrops] Re: Notification for draft-spaghetti-si… Tim Bruijnzeels
- [Sidrops] Re: Notification for draft-spaghetti-si… Job Snijders
- [Sidrops] Re: Notification for draft-spaghetti-si… Tim Bruijnzeels
- [Sidrops] Re: Notification for draft-spaghetti-si… Job Snijders
- [Sidrops] Re: Notification for draft-spaghetti-si… Tim Bruijnzeels
- [Sidrops] Re: Notification for draft-spaghetti-si… Dale W. Carder
- [Sidrops] Re: Notification for draft-spaghetti-si… Job Snijders
- [Sidrops] Re: Notification for draft-spaghetti-si… Martin Hoffmann
- [Sidrops] Re: Notification for draft-spaghetti-si… Ties de Kock
- [Sidrops] Re: Notification for draft-spaghetti-si… Martin Hoffmann
- [Sidrops] Re: Notification for draft-spaghetti-si… Job Snijders
- [Sidrops] Re: Notification for draft-spaghetti-si… Martin Hoffmann
- [Sidrops] Re: Notification for draft-spaghetti-si… Job Snijders
- [Sidrops] Re: Notification for draft-spaghetti-si… Ties de Kock
- [Sidrops] Re: Notification for draft-spaghetti-si… Russ Housley
- [Sidrops] Re: Notification for draft-spaghetti-si… Job Snijders
- [Sidrops] Re: Notification for draft-spaghetti-si… Russ Housley
- [Sidrops] Re: Notification for draft-spaghetti-si… Job Snijders