[Sidrops] Re: SIDROps Charter update

Job Snijders <job@sobornost.net> Thu, 02 October 2025 07:58 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 390BA6C4D98A for <sidrops@mail2.ietf.org>; Thu, 2 Oct 2025 00:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level:
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.017, 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 G-qbSmpITEv5 for <sidrops@mail2.ietf.org>; Thu, 2 Oct 2025 00:58:41 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 020C46C4D984 for <sidrops@ietf.org>; Thu, 2 Oct 2025 00:58:41 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id 4fb4d7f45d1cf-634a3327ff7so1514461a12.1 for <sidrops@ietf.org>; Thu, 02 Oct 2025 00:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20230601.gappssmtp.com; s=20230601; t=1759391914; x=1759996714; darn=ietf.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=NwZeKl9LSL74G46ydAHImvBCbcZszo5e5fqbf67SohQ=; b=hkdwYyQd+wSCxHl/s96iZ54ZZOGT4DoYo5HvGQNwvKy4FnBIZIqj9gTBMOgRlgRFrX ReH+XciEtx7lRFEZrHDD5ZZtcRpLG6weMPWLqUyyjKPBBBoOl61chS6KWef/6kou6QqG xQjLiWCLWYq5PhkF3FtNCRrExONDJw6/p/ZxEYgO4ugb6rbs26DOBgXA0Z87c+OkbZWr sVr/y0SxxjBoo2XcQmZUYC9VymqZdZe0YvuglORo4rRwypnaxz8/a1xigDdQMd3ZAMGC pyAZ6eqlT2xK336w0BdazwQsZPhzdiCotSBe3go+Xx/rkw2yjSQi6R0sG1Inl/vKPey3 cXBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759391914; x=1759996714; h=in-reply-to: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=NwZeKl9LSL74G46ydAHImvBCbcZszo5e5fqbf67SohQ=; b=ZQ89eb+GQOjrckz/dZwth+lJ6gy+lMcfwtRSt2xS6th6XtqHZ+QhitgynphWCEbICd /dzQBo4cIhcYpdTMm7vjm8OE/9LhLhmrI4AQ3K1jVR+v/cdc7OqL49u/d17ztEWL+NwR DtSRweFwMTKjUSFjMCV3A4cfQJuUwWxCjRIhjCdSwmT5qEnHcGTtbW9i3smRPhUEKKKU CbNRALR1D/Mcd2J/33OeU19kRxVGh1F/HnruxHdQeqcRSGOyW4soKRp6vTpbBXvBqfqf EzeaCb3hgX7wyZ87AVr5rkJDiy5tVDvJLxws3/FjncMxSZDlFQPTvgdmu2kZJ9tjKbXT BYWw==
X-Forwarded-Encrypted: i=1; AJvYcCVPKvokI+bLHF8dFXBBJNCx3wmuZVGzrHtkxO+XSPvN1W1ZHT5pLzEwusl8Kz9UiOW04w7F6eWs@ietf.org
X-Gm-Message-State: AOJu0YyQexgB/Y1JiEH0CaqFuDo0M54saufrxm+mU6o7fBzAuFDRuODw Xms+150iOnie/i/vzqe5pP18nNA/IB0z5gT/H+FVh3uGcxEDs2/BkHERTZrRyXZ4Poc=
X-Gm-Gg: ASbGncvs7Cnl511sgLJXaSZFAkX5Q2rsWWpcwB5r9xrpo4jj+F3zG3ps28kUQ2gwW1r p5yTi0KRJrBC1j4NEj+ag8T+NAWjAWF/Z3D5tn4eSIpb91Br8Jtc1ho/BCl4oSUQOPepmVg38RW MuXFbG6tK4pH2mU31DM/9/woLNoOj6Lag9eYu4bIey8S8KGU0KmRJDjClYmHRQ0A3NKDOi+Srw8 TXszGdymoHVKewZtNUOMwd3c3Kroz42c97gBJQnti3u0nqUbE2ysBVfaFNUyHcGvkLZiYfXjHgY yToUInCMZIPlJ7yQlgzcYiwVpZBZ9SQRBxGm9avcOJ/YDOefriMA6dVDMLeojZFQznuc3BlQ0BB f7t7PmSQHKWZ2U4h/vCe+fflxPWgs2MYYAPJsdpab6CwwmWJ4ngUCmz0XG33SZ69EaIm7J+6Nil j7pv1kHDyV6JrGhZmUmPvVcfeEm4zMnLtV1Xr/aFwv6ohikPIHPht6nRQk76aAV/FpoahvfdcoD w==
X-Google-Smtp-Source: AGHT+IG6MPJUyBbt0K2TonlH+w4dgIlFQrvoIjuI1ZNDQIkWvHbrtZ2OppcXHw5Sx4K7Lj+aaWii+g==
X-Received: by 2002:aa7:d38c:0:b0:634:66c8:9e6d with SMTP id 4fb4d7f45d1cf-63678cdd2c6mr5479254a12.35.1759391913722; Thu, 02 Oct 2025 00:58:33 -0700 (PDT)
Received: from feather.sobornost.net (mieli.sobornost.net. [45.138.228.4]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-63788100129sm1342654a12.24.2025.10.02.00.58.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Oct 2025 00:58:32 -0700 (PDT)
Date: Thu, 02 Oct 2025 07:58:31 +0000
From: Job Snijders <job@sobornost.net>
To: mohamed.boucadair@orange.com
Message-ID: <aN4wp5B-N4kSxVbk@feather.sobornost.net>
References: <66D6278C-AD45-456A-8D8F-9E22DEF204AD@gigix.net> <PR0P264MB2885887E1B14E5BF96D2270888E7A@PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <PR0P264MB2885887E1B14E5BF96D2270888E7A@PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM>
X-Clacks-Overhead: GNU Erik Bais
Message-ID-Hash: FTTKTORX5NZVLS7UW3FNMHCZQZZQJH45
X-Message-ID-Hash: FTTKTORX5NZVLS7UW3FNMHCZQZZQJH45
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: Luigi Iannone <ggx@gigix.net>, IETF SIDRops Chairs <sidrops-chairs@ietf.org>, SIDRops IETF <sidrops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sidrops] Re: SIDROps Charter update
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/o4-EsekvhvP1b_GVZY4BloxP8yo>
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 Thu, Oct 02, 2025 at 06:18:03AM +0000, mohamed.boucadair@orange.com wrote:
> Hi Luigi, all,
> 
> Thank you all for the work put into this minor update to unlock manifest-number.

The majority of the authors of manifest-numbers indicated they'd like to
see a running code requirement in the charter. So if you are trying to
rush through this charter update it is NOT for the the benefit of the
manifest-numbers document.

Kind regards,

Job