IETF Logo Mail Archive

[Sidrops] Re: Call for adoption: draft-spaghetti-sidrops-rpki-erik-protocol-04 (Ends 2025-11-29)

Martin Hoffmann <martin@nlnetlabs.nl> Mon, 10 November 2025 13:27 UTC

Return-Path: <martin@nlnetlabs.nl>
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 366B486E3A65; Mon, 10 Nov 2025 05:27:46 -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=nlnetlabs.nl
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 AYT3rrl9RlD7; Mon, 10 Nov 2025 05:27:45 -0800 (PST)
Received: from mout-b-201.mailbox.org (mout-b-201.mailbox.org [195.10.208.61]) (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 B3D6B86E3A60; Mon, 10 Nov 2025 05:27:45 -0800 (PST)
Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-201.mailbox.org (Postfix) with ESMTPS id 4d4r7X2r5GzDrlF; Mon, 10 Nov 2025 14:27:36 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nlnetlabs.nl; s=MBO0001; t=1762781256; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=eikOV4Aw7XQ8ZpMk5kONORiSZTHSIYl1OFRS0ETehrI=; b=sj17XJnU0dp5kAFpD/HeFfsJJZ82JI7EYJm8afEU3r3uRLm1obuGmIu+3jxVVCwxObPH3j 7bTgVKre1FK9HWAoQ1v3mQ1ufsXNP3tOn4ErcCRda9OeWGHflpMetrSmReaIP73D98bNx3 Z1LFIVphKUKERyOCr1CapI/v7CQ787DHa6xlIO7wG05vCi8fGJEVwOJcyb5lWkp5NruhnF VS8rcQTINy21CvWu3hgeUg/GE/XHJg6cGwMN69ordWk7f9hDm69u5tJ90bedJUjAGRGA5E EGhphUmR15nEpapghndzUvZw/AjlDbpwv3EqEISWY4cojmyM1FLisVYn01vR6w==
Authentication-Results: outgoing_mbo_mout; dkim=none; spf=pass (outgoing_mbo_mout: domain of martin@nlnetlabs.nl designates 2001:67c:2050:b231:465::202 as permitted sender) smtp.mailfrom=martin@nlnetlabs.nl
Date: Mon, 10 Nov 2025 14:27:30 +0100
From: Martin Hoffmann <martin@nlnetlabs.nl>
To: Russ Housley via Datatracker <noreply@ietf.org>
Message-ID: <20251110142730.5cf0e4e7@glaurung.nlnetlabs.nl>
In-Reply-To: <176261482720.1666229.7196331660629042612@dt-datatracker-5df8666cb-7l4w5>
References: <176261482720.1666229.7196331660629042612@dt-datatracker-5df8666cb-7l4w5>
Organization: NLnet Labs
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4d4r7X2r5GzDrlF
Message-ID-Hash: 4CDJFYWAWLQZGJI6SSLRULSR55PT536C
X-Message-ID-Hash: 4CDJFYWAWLQZGJI6SSLRULSR55PT536C
X-MailFrom: martin@nlnetlabs.nl
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: Russ Housley <housley@vigilsec.com>, draft-spaghetti-sidrops-rpki-erik-protocol@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sidrops] Re: Call for adoption: draft-spaghetti-sidrops-rpki-erik-protocol-04 (Ends 2025-11-29)
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/xBlHQ5WoyKFyaLcp3W22NfOSmjg>
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>

Russ Housley via Datatracker wrote:
> Subject: Call for adoption:
> draft-spaghetti-sidrops-rpki-erik-protocol-04 (Ends 2025-11-29)
> 
> This message starts a 3-week Call for Adoption for this document.

I want to support adoption of this document, but at this point I am
missing an indication -- both by the authors and the working group --
as to what the aim of defining a new RPKI transport protocol is.

Specifically, I want to avoid that at the end of the process we have
three protocols that all need to be implemented by publication server
and relying party.

Ideally, I would want the outcome to be that the new protocol is the
only required transport protocol and both rsync and RRDP will go away.
But at the very least, I feel that rsync needs to go.

  -- Martin

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