[Sidrops] Re: SIDROps Rechartering

Tim Bruijnzeels <tbruijnzeels@ripe.net> Thu, 06 November 2025 22:44 UTC

Return-Path: <tbruijnzeels@ripe.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 96B4D84D709F for <sidrops@mail2.ietf.org>; Thu, 6 Nov 2025 14:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=ripe.net
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 Ri4UvN91VK_a for <sidrops@mail2.ietf.org>; Thu, 6 Nov 2025 14:44:24 -0800 (PST)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 D8E7984D7099 for <sidrops@ietf.org>; Thu, 6 Nov 2025 14:44:24 -0800 (PST)
Received: by mail-wm1-x331.google.com with SMTP id 5b1f17b1804b1-477632d45c9so738815e9.2 for <sidrops@ietf.org>; Thu, 06 Nov 2025 14:44:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ripe.net; s=google1; t=1762469064; x=1763073864; 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=pjTYlOntKbe783TB2/4EJGl55BRsQzv3wJ7TrO82C5A=; b=FAW3fZoolgM0zIUZo3cN79oB1JaLw4fXMEaonzwUBfMYXMHt1djbtKshfASChCGtX5 Gnbkk+AUvau1QR2fHipGeoD2pnQTV3WybwFaMLRzb1wVpAiK6mQ9k22jjp089BQ4/YSB sTwXf/NWgUflGoY7OUZmJ5yfHCQM+WmC3vnK+dEBkzOgZDNPp2/kn4PlAkmT96EIvz63 cHQFppR7Bl44sLotkOMGE/6JxhOz4DmsX/3Bk5QywmFK6ckKM44jtvlPzF7uNLeECM1j K+R/VctMc4dSENCe4K+fNUWn8481fS051Yf4U4q39m9zavYjBwGdlQfK6gDcIatP8Qsk GEAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762469064; x=1763073864; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-gg:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=pjTYlOntKbe783TB2/4EJGl55BRsQzv3wJ7TrO82C5A=; b=BaiHnRQ/gRmm7OvY2NDMQn8OgrcNlWyO/+tVd5KWUZYm3aAkQ/fYcVhteQU5eN+UzU 9xnLw8cE5wXKltqPsq+AYw/f44CIEleSH/3wsZ+VPxq7GSTW1MkwRZkWUdr3I3wIry3Z BKEY2Fu1sobW7NWULRZ5+HSvA6exbe5Jbnx+pg/cuEBFOIp+Koet/BpuYUzp7pTJNbwe ihFkYE8LNBa8isg33bDCLN9JRAoMCVc+pj68Xi09UcglNvwUqqALZxtsxdeIV+eNOKOg ebz7E/5e6GtF93eF6UmjBHrxqiBLyiEXARfS4/+nXLjsf1SMV0nbUzrSdKTfplOTnaM2 CC1Q==
X-Gm-Message-State: AOJu0Yw0sUcA56xdf9R1GQzT4Gd14CSXLlBL+cd9AyhKZEtZaZZfLTHZ ghVJ6R3klSiC2Rd8PVRZdjzDUxt7jZxk6uZTdruGkpcUKyHUfmrqY68iQSCKIpg+d1E=
X-Gm-Gg: ASbGncs2rcR5/pWOMllBzRTp3vre1OWYN/ljMA1NdagbAs/dbyc6Gbw+9WJzcC9GjwT DND6mUZtBXHwRexnuR9olC9JCo7kXZHCgHJjElqrebYlsTGbMb6rq7Y80H/Kk1tpsOxGYHOsgdk 37c58FO8xvkF/Dk/zkqo4RgPCqisHyp2jXmHKmyHcm3abZO9ab3EJO6GGjOak7yq/J2Labg+vPq 03ue/W8XZ186y3wwZFFmqbE/Yra16gw8oqlfyowjWrbx2gM5m5Qa3zcxg9+BOFoF9RnuGlVGzuo GwxjVpooE1gQkCdDLGdlcNZoO0szWVy7LsPW0e6Qc5dJ//ztvot5rQAIKwwARyopY3sn0I2Z5nJ 1JZdPC3Bw1PchzZ/0clMhYNDUq1xG46XN5phB0ylKvUMl2/0ztHmRf6AeGfBeat+NpsyDSoQTs4 KTliE3MP1YFgZqvFFhxBvzR0EUKXySury4uUdhqhdfokFjJBUY
X-Google-Smtp-Source: AGHT+IFbwXmsyTk5PyW9TwMNFSesqH3l7HxpLQmPPx2ZNhRFC08Bhkl8UeAq57+8h6h1gowCU0UmBw==
X-Received: by 2002:a05:600c:a43:b0:476:651d:27e6 with SMTP id 5b1f17b1804b1-4776bcc7167mr8740195e9.36.1762469063843; Thu, 06 Nov 2025 14:44:23 -0800 (PST)
Received: from smtpclient.apple ([2001:67c:1232:144:9596:72ad:25a6:6fec]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-88082a37b9esm27189806d6.52.2025.11.06.14.44.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Nov 2025 14:44:23 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
From: Tim Bruijnzeels <tbruijnzeels@ripe.net>
In-Reply-To: <DB594C7D-E196-4B71-B571-4150402BDF57@gigix.net>
Date: Thu, 06 Nov 2025 17:44:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <088390FB-EF0E-4B69-8BB3-7983E3E2498A@ripe.net>
References: <DB594C7D-E196-4B71-B571-4150402BDF57@gigix.net>
To: Luigi Iannone <ggx@gigix.net>
X-Mailer: Apple Mail (2.3826.700.81)
Message-ID-Hash: LVP5TX5CJMY276274QHNSMAPE5UODKX4
X-Message-ID-Hash: LVP5TX5CJMY276274QHNSMAPE5UODKX4
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 <sidrops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sidrops] Re: SIDROps Rechartering
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/_GiYPXBZC4LkmVA0fHf7Mvs3ltg>
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 Luigi,

Apologies, but it's not clear to me what I can do as a working group participant to help move the rechartering process forward.

I see that there are currently five open pull requests here:
https://github.com/ietf-wg-sidrops/charter/pulls

Do we need to comment on these, give thumbs up / down?

Thanks
Tim



> On 22 Oct 2025, at 11:01, Luigi Iannone <ggx@gigix.net> wrote:
> 
> Hi All,
> 
> Concerning the rechartering, there are 4 main points that need to be tackled in order to update in a meaningful way our charter:
> 
> 1. General language: Currently the charter talks more about SIDR as something that is about to be deployed. Today, the technology is much more mature and the charter should reflect this situation. 
> 
> 2. SIDROps goals:  The main goals are still about operators feedback and interoperability with non-SIDR Internet. While this are important goal, with the level of maturity reached today, the group may think about other interesting technical goals that may be important in the future.
> 
> 3. Implementation policy: The two-implementations policy is been part of the SIDROps modus operandi for a while and now we can put it officially in the charter, with some additional wordsmithing to avoid making it a blocking point during IESG review.
> 
> 4. Update the milestones according to the discussion.
> 
> 
> Points 1 and 4, look relatively simple to be done and we can deal with these later.
> 
> Points 2 and 3, may require more discussion compared to the others, hence, we can start with these two points, creating two separate threads to colect the advice of everyone.
> 
> Ideally using the two weeks leading to the IETF for discussion and summarize/refine during the first part of our face to face meeting in Montreal.
> 
> On behalf of the chairs
> Luigi 
> _______________________________________________
> Sidrops mailing list -- sidrops@ietf.org
> To unsubscribe send an email to sidrops-leave@ietf.org