IETF Logo Mail Archive

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

Jay Borkenhagen <jayb@braeburn.org> Thu, 10 December 2020 23:30 UTC

Return-Path: <jayb@oz.mt.att.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 61F173A1341 for <sidrops@ietfa.amsl.com>; Thu, 10 Dec 2020 15:30:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 0PBTul8pwMa1 for <sidrops@ietfa.amsl.com>; Thu, 10 Dec 2020 15:30:54 -0800 (PST)
Received: from hrabosky.cbbtier3.att.net (braeburn.org [12.0.1.25]) by ietfa.amsl.com (Postfix) with ESMTP id 6671D3A133F for <sidrops@ietf.org>; Thu, 10 Dec 2020 15:30:54 -0800 (PST)
Received: from oz.mt.att.com (zoe.cbbtier3.att.net [12.0.1.45]) by hrabosky.cbbtier3.att.net (Postfix) with ESMTP id D22DA497EB; Thu, 10 Dec 2020 23:30:53 +0000 (UTC)
Received: by oz.mt.att.com (Postfix, from userid 1000) id A56FC5640A60; Thu, 10 Dec 2020 18:30:53 -0500 (EST)
X-Mailer: emacs 25.2.2 (via feedmail 11-beta-1 I); VM 8.2.0b under 25.2.2 (x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <24530.44968.720604.842924@oz.mt.att.com>
Date: Thu, 10 Dec 2020 18:30:48 -0500
From: Jay Borkenhagen <jayb@braeburn.org>
To: Job Snijders <job@ntt.net>
Cc: sidrops@ietf.org
In-Reply-To: <X8+NbXjEfH7Balvq@bench.sobornost.net>
References: <X8+NbXjEfH7Balvq@bench.sobornost.net>
Reply-To: Jay Borkenhagen <jayb@braeburn.org>
X-GPG-Fingerprint: DDDB 542E D988 94D0 82D3 D198 7DED 6648 2308 D3C0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/1YB8NzGGElGIJCztbIsc9IPjxMU>
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: Thu, 10 Dec 2020 23:30:56 -0000

Job Snijders writes:
 > Dear all,
 > 
 > I propose some following text detailing a requirement for multiple
 > implementations to exist prior to RFC publication will be beneficial to
 > the working group.
 > 

I support.  I believe this change will help improve the quality of 
RFCs produced here by requiring thorough and detailed understanding by
implementers before the drafts become RFCs.

Thanks.

						Jay B.

v2.23.0 | Report a Bug | By Email