Re: [Sidrops] proposal to update SIDROPS charter (requirement for multiple implementations before IESG/RFC publication)

Nick Hilliard <nick@foobar.org> Tue, 08 December 2020 14:49 UTC

Return-Path: <nick@foobar.org>
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 8B24B3A0F3A for <sidrops@ietfa.amsl.com>; Tue, 8 Dec 2020 06:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y-PTBed0BEqY for <sidrops@ietfa.amsl.com>; Tue, 8 Dec 2020 06:49:07 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C72C3A0F39 for <sidrops@ietf.org>; Tue, 8 Dec 2020 06:49:06 -0800 (PST)
X-Envelope-To: sidrops@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 0B8En3Bb044799 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Dec 2020 14:49:03 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
To: Job Snijders <job@ntt.net>
Cc: sidrops@ietf.org
References: <X8+NbXjEfH7Balvq@bench.sobornost.net>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <e7b09e7d-baa9-6d2e-e2e2-220026db4df8@foobar.org>
Date: Tue, 8 Dec 2020 14:49:02 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.40
MIME-Version: 1.0
In-Reply-To: <X8+NbXjEfH7Balvq@bench.sobornost.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/66Zeu3iWXnSMGkPQws9yYaj33I4>
Subject: Re: [Sidrops] proposal to update SIDROPS charter (requirement for multiple implementations before IESG/RFC publication)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 08 Dec 2020 14:49:10 -0000

Job Snijders wrote on 08/12/2020 14:27:
>      will indeed interoperate in intended ways. The SIDROPS working group
>      requires interopability reports from at least two different
>      implementations of a proposed specification, prior to publication as
>      RFC.

given the difficulties that have been seen in the RPKI recently, all of 
which related to subtle spec interpretations, this does not seem to be a 
completely dumb idea.

Nick