Re: [Sidrops] Requiring Two Implementations - before exit of WGLC

Russ Housley <housley@vigilsec.com> Thu, 14 December 2023 18:21 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA7CAC14F68A; Thu, 14 Dec 2023 10:21:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qd1o3ipu1yFL; Thu, 14 Dec 2023 10:21:07 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19203C14F686; Thu, 14 Dec 2023 10:21:07 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 700581B7FE4; Thu, 14 Dec 2023 13:21:06 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 5D0C41B7E41; Thu, 14 Dec 2023 13:21:06 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <ZUzjYb-4cl33jFvy@feather.sobornost.net>
Date: Thu, 14 Dec 2023 13:20:56 -0500
Cc: Warren Kumari <warren@kumari.net>, SIDR Operations WG <sidrops@ietf.org>, sidrops-ads@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8474AA55-E0A0-4317-8839-7A86509A87E6@vigilsec.com>
References: <ZL8yOYPQL1z1HSPV@snel> <ZL95cRkffm65WL0c@dhcp-8bfa.meeting.ietf.org> <87pm1tvn2n.wl-morrowc@ops-netman.net> <CAAQiQRfLiRtL81beSVPxtm=5Wo4OhdS-J_1nVsqPc66GYB2baw@mail.gmail.com> <ZSALGNekRUzh9PaM@snel> <2F74A667-57B7-45BD-AB2F-0DAF877E54DC@amazon.com> <817DBADA-42AF-4CAC-B8FB-DDBDA564722D@nlnetlabs.nl> <21DDC19E-900E-4991-A484-9405C4FC014F@ripe.net> <CAAQiQRf6saTVLYOZLSz2V_ukYcHOm0rseqwJeZjuz5nRPaxS3g@mail.gmail.com> <CAHw9_iL6jr3kXFBKNWRjqAeUoF2ZZPb+_fUAMET5Q--reMmHjg@mail.gmail.com> <ZUzjYb-4cl33jFvy@feather.sobornost.net>
To: Job Snijders <job@fastly.com>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/54iqtt-Ug2lzMbr9KpQOnWsh2JM>
Subject: Re: [Sidrops] Requiring Two Implementations - before exit of WGLC
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2023 18:21:09 -0000

Job:

The SIDRops WG Chairs discussed this today.  We want to make it an informal policy for at least three documents.  Then, if there are no surprises, we will update the charter to reflect the requirement for two interoperable implementations before sending a document form the WG to the IESG.

For the SIDRops WG Chairs,
 Russ



> On Nov 9, 2023, at 8:49 AM, Job Snijders <job=40fastly.com@dmarc.ietf.org> wrote:
> 
> Dear Warren,
> 
> On Thu, Nov 09, 2023 at 05:31:30AM -0800, Warren Kumari wrote:
>> So, I had understood that all this was being modeled on IDR, so I want
>> to go see if we could just seal text from their charter / figure out
>> how they had navigated this… only to discover that it isn't actually
>> *in* their charter…
>> 
>> So, I asked the IESG, and John says that this is actually tradition,
>> not charter… seeing as everyone understands it in IDR (and I think
>> that many of us assumed that it was in the charter), perhaps that's
>> good enough?  Write it up and put it in the wiki?
>> 
>> This allows us to follow "Do the right thing" and not get wrapped
>> around the axle on process/charter language — can someone convince my
>> why I'm wrong here?
> 
> I strongly believe we need to write this down somewhere and the charter
> forms the essence of this working group; it's nice for newcomers to have
> something to base their participation on, or to point longerstanding
> participants to "remember, we agreed to this".
> 
> Updating the charter is not *that* much work, right?
> 
> Kind regards,
> 
> Job