IETF Logo Mail Archive

[Sidrops] Re: Call for WG Adoption of draft-snij-sidrops-constraining-rpki-trust-anchors

John Kristoff <jtk@dataplane.org> Tue, 20 January 2026 17:32 UTC

Return-Path: <jtk@dataplane.org>
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 92FB5AA84BF9 for <sidrops@mail2.ietf.org>; Tue, 20 Jan 2026 09:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=dataplane.org
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 lEnv6y7yOgDH for <sidrops@mail2.ietf.org>; Tue, 20 Jan 2026 09:32:07 -0800 (PST)
Received: from dataplane.org (dataplane.org [50.31.183.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4BE77AA84BF4 for <sidrops@ietf.org>; Tue, 20 Jan 2026 09:32:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dataplane.org; s=2025121200a; t=1768930321; bh=d1111CirlAF/Yx1KLecUicRdMa9XJQis/qsY3ZgYkG0=; h=Date:From:To:Subject:In-Reply-To:References:From; b=ZK3hTT/PagK2TyEcI8bhAbEQsC1G3ZShyQ1tIbMgsoYV6Fcja0kSYkPW9jA9d8Fzf lkgex/eQhdNZHMWbUNz2Lpx49y9qVTt18uWby1cG7rcXRZ1ycH5/f6Wm+KX1HhNOUz BuX53yjTyTKSBaQKdb1Ky01chtGjLW74PBRz9zR937WimMF4D3LYWZJkEBOeGf26Au i8Nk+F+e93zy7ChkC1DeS9CGtRDmmuCwS3fjGf/+dIL4hUoxof2sdixpjv5mmdgZVt ORX3U8CUT3pG9QQP49hmjdSCjDMdnDB82YGr1WNSMNiZ2LptYvj40zbOb2E9IA2hX4 GRWLehTe0CVgw==
Received: from localhost (localhost [127.0.0.1]) by dataplane.org (Postfix) with ESMTP id 27C92400D8 for <sidrops@ietf.org>; Tue, 20 Jan 2026 17:32:01 +0000 (UTC)
Date: Tue, 20 Jan 2026 11:32:00 -0600
From: John Kristoff <jtk@dataplane.org>
To: sidrops@ietf.org
Message-ID: <20260120113200.41fa116e@dataplane.org>
In-Reply-To: <5C5B8F40-6E19-4082-89C0-3DDC0AB6364A@gigix.net>
References: <5C5B8F40-6E19-4082-89C0-3DDC0AB6364A@gigix.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: AGYQBCCZBJOJYAC5T3DMFV56UYQ4CPPD
X-Message-ID-Hash: AGYQBCCZBJOJYAC5T3DMFV56UYQ4CPPD
X-MailFrom: jtk@dataplane.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sidrops] Re: Call for WG Adoption of draft-snij-sidrops-constraining-rpki-trust-anchors
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/cdzUVnG0XgFEm-aisvjb8rMkOCk>
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>

On Mon, 19 Jan 2026 13:46:55 +0100
Luigi Iannone <ggx@gigix.net> wrote:

> Title: Constraining RPKI Trust Anchors

Are there risks of stale or divergent, to the point of being
operationally problematic, constraints at the RPs? In other words,
could this lead to something akin to statically deployed bogon filters?
If I'm interpreting the text correctly, this depends on how and where
the EE certificates are maintained?

John

v2.39.1 | Report a Bug | By Email | System Status