[Sidrops] Re: Rechartering: implementation policy
Job Snijders <job@sobornost.net> Wed, 29 October 2025 17:42 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 D3FFB7E3459C for <sidrops@mail2.ietf.org>; Wed, 29 Oct 2025 10:42:06 -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=ham 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 E2o8qqRBFCy1 for <sidrops@mail2.ietf.org>; Wed, 29 Oct 2025 10:42:06 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 5444C7E34592 for <sidrops@ietf.org>; Wed, 29 Oct 2025 10:42:06 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-b3d196b7eeeso31291766b.0 for <sidrops@ietf.org>; Wed, 29 Oct 2025 10:42:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20230601.gappssmtp.com; s=20230601; t=1761759724; x=1762364524; darn=ietf.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=k4mn6sHaSIKzYzoKBrWgGFUyxihYsDRGttCV0x+DA/0=; b=SJJ0fR0NpzkZKezhzmck6BaK6muFfto0PkPma4V4p94890509poZWJzCorAojs71yk fnEWj7MVq4Occxzz3/tigvlxY/X7wkXfT/4oAjHA9YGNzgGSob0aVjQYw1GP+2BG8BZy 1Wd2z1HoPLRhnJB/oB9u8xaXgfa1Cpitn234AU3psegBI1egpSn+2AbDSrCp6WrxBcUq 4hTlkDXTs6II+N2PsySaquObcaWNciM8nRJ6OxwBbrZ/0HH6YmiQ+oNY9H2zJ0K7cAWP OfYFRDBUMAo8pwhBITpZKuh/v9B3gydGYSBaHi6IVSOKj2HHqNiT/+zTQuZWoDnmvXYh AkFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761759724; x=1762364524; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=k4mn6sHaSIKzYzoKBrWgGFUyxihYsDRGttCV0x+DA/0=; b=gJpQ5vtfxGFk2wsVcNpUkY5SkAX0SwyPifM9NVG66u4BqT/FpxW5nulWha5y4z3+aW oNhF0IDXYaNPJpU0Om0rwSQioxYc2QjTxV/vEo7jg3fwv2OxzjpKcv8HF9vS6/xyyo6j HoGbEB8AOmUv76Fy1pEQxv8+8pT9yTnBzVZc9YcZODUVAhJJJdVL3WcNSdFbMegq0KTv 0E7LdMguUDFaYvaem/SFD1c4Dqxl30l9RGRQm8AKh7z6FY5U0TUsP6mogInNeVtq/KdA vub127cYD7pnzdSWXHh3vMrrlVizHzDiqbnGZucqdYinPywpRsRY78IM0VY5L6EuCWvg IikQ==
X-Gm-Message-State: AOJu0YyVBrG43mWuQBNLwuWL5paDq8E+V94Q5QDRXTbYNSpPNmKb8Qd4 SDV21/WwtLLFI5BZaC/m+KUIaqgt+afsKCb3zPha6GthnSocTz1Qa/SgvXb5Q2WhWINfsa6tPwp AbhBeBa8=
X-Gm-Gg: ASbGncuGJTjmhXgHE3Gg8OosZQn1gs8NXpm19qfwqJaeIv7VRhZ2JBJlP4IMUf1ClED EF7FJ77vE2XmtBV7N3MeTHOnNhMuvjtR1Hzk8kYhVJXQMU5I8xsPi1yxNGNHcD7khjnwiTG4LFJ Q3MgEfijd3tIEBaFInIRlhZe7APO1JoYDFMv4U02el+GcWkjQ0+6MjBsND9Ax7TKvW4mx4/XsWq Pq7OWJt2/rf4LL85vyE8Z/qDlb5G0tUYoH0cU+vmzwIH8ep2DoflNjioAKGWYdc510y0uVDNA5L lPVL8cOCJo5fuQLg3KZfZ7N6NAUI6J+c5r8xiogXh887Udp5DphC5oO5gc6FMP7apkjAEOPOiEX d/bUkCvlOFQ/rxgU2fYzrqvLtWO9fm0+52cajx+ieC2CFVQnwQTHmnQpZq/36GdGvJn/vtVzNry EueOWMBZjRN43pwqLWMXg/mbIT3exbJaBjIuJAvjjFCcvhQ/LmGtfP/eIljtTnPFtwQb5qWRsmK efbv2enWPaUtxc=
X-Google-Smtp-Source: AGHT+IG26pQokyqHpxg2DRdxFk9I597pohfCOzU5gpQAuXuobTScAS0EBu10uLluf/MnpBiVfp1QVA==
X-Received: by 2002:a17:907:72c4:b0:b45:60ad:daf9 with SMTP id a640c23a62f3a-b7053b0cf7amr4939366b.3.1761759724449; Wed, 29 Oct 2025 10:42:04 -0700 (PDT)
Received: from feather.sobornost.net ([192.147.168.2]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-b6d85353ff7sm1503777766b.22.2025.10.29.10.42.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Oct 2025 10:42:03 -0700 (PDT)
Date: Wed, 29 Oct 2025 17:42:02 +0000
From: Job Snijders <job@sobornost.net>
To: sidrops@ietf.org
Message-ID: <aQJR6vxzaFfg6nV7@feather.sobornost.net>
References: <AA5D61DF-E7B0-47DD-A6E2-305C25F629E4@gigix.net> <cce754cf-10cf-bede-30dc-8403981cc438@foobar.org> <CA+eZshDT7yAknst7CNNcMaQ-1N0MwNw=Vvbq7TwhEwpvqmBzJQ@mail.gmail.com> <C32D24EE-AE16-407F-8D26-923B86476F8F@gigix.net> <aQIbIQhAo05GNOUW@feather.sobornost.net> <DB41BE12-27D3-4A74-83DD-75F493F9EB30@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DB41BE12-27D3-4A74-83DD-75F493F9EB30@vigilsec.com>
X-Clacks-Overhead: GNU Erik Bais
Message-ID-Hash: RQH33YISKAIYXMBKJEGCQV4GOT2QJ3RU
X-Message-ID-Hash: RQH33YISKAIYXMBKJEGCQV4GOT2QJ3RU
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sidrops] Re: Rechartering: implementation policy
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/e2DBfiJRh6u41xav2pIFb0TrtXI>
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 Wed, Oct 29, 2025 at 11:46:25AM -0400, Russ Housley wrote: > I suggested the text about a section in the Internet-Draft to document > implementation results. > > The point was to require the implementations be documented, but not > take all of the overhead associated with formal interoperability > reports; see BCP 9. I think it would be better to refer to BCP 9. I don't consider BCP 9's excellent guidance to be "overhead" - quite the opposite, quite often will the very act of writing an implementation report itself help shed light on gaps or conformity issues. In a recent WG history we have an example success story: the thorough reports from Tom Harrison's testsuite for draft-ietf-sidrops-manifest-numbers. It seems that over the years this WG has been quite good in testing/documenting implementations and their interopability. So, considering what Luigi & Russ sent earlier today, perhaps the following paragraph is clearer? """ Given the importance of routing security to the overall stability of the Internet, the Working Group will not submit protocol specifications for publication to the IESG before demonstrating at least two interoperable implementations. See RFC 5657 (part of BCP 9) for guidance on what implementation reports should contain and BCP 205 for guidance on how to raise awareness of running code. """ Kind regards, Job
- [Sidrops] Rechartering: implementation policy Luigi Iannone
- [Sidrops] Re: Rechartering: implementation policy Nick Hilliard
- [Sidrops] Re: Rechartering: implementation policy Job Snijders
- [Sidrops] Re: Rechartering: implementation policy Luigi Iannone
- [Sidrops] Re: Rechartering: implementation policy Nick Hilliard
- [Sidrops] Re: Rechartering: implementation policy Luigi Iannone
- [Sidrops] Re: Rechartering: implementation policy Dirk Doesburg
- [Sidrops] Re: Rechartering: implementation policy Luigi Iannone
- [Sidrops] Re: Rechartering: implementation policy William McCall
- [Sidrops] Re: Rechartering: implementation policy Luigi Iannone
- [Sidrops] Re: Rechartering: implementation policy Job Snijders
- [Sidrops] Re: Rechartering: implementation policy Luigi Iannone
- [Sidrops] Re: Rechartering: implementation policy Tim Bruijnzeels
- [Sidrops] Re: Rechartering: implementation policy Luigi Iannone
- [Sidrops] Re: Rechartering: implementation policy Russ Housley
- [Sidrops] Re: Rechartering: implementation policy Job Snijders
- [Sidrops] Re: Rechartering: implementation policy Luigi Iannone
- [Sidrops] Re: Rechartering: implementation policy Nick Hilliard
- [Sidrops] Re: Rechartering: implementation policy Luigi Iannone