IETF Logo Mail Archive

Re: [Rfced-future] Fwd: RFC 9280 on RFC Editor Model (Version 3)

Wes Hardaker <wjhns1@hardakers.net> Fri, 01 July 2022 14:48 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7ABC159498 for <rfced-future@ietfa.amsl.com>; Fri, 1 Jul 2022 07:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 AzCJ1USAbbXW for <rfced-future@ietfa.amsl.com>; Fri, 1 Jul 2022 07:48:44 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (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 8D977C15A73F for <rfced-future@iab.org>; Fri, 1 Jul 2022 07:48:44 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) by mail.hardakers.net (Postfix) with ESMTPA id 676E320F4B; Fri, 1 Jul 2022 07:48:42 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Eliot Lear <lear@lear.ch>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>
References: <20220630185204.F0908289E0@rfcpa.amsl.com> <94872e69-aadc-c73a-db7b-728127451176@lear.ch>
Date: Fri, 01 Jul 2022 07:48:42 -0700
In-Reply-To: <94872e69-aadc-c73a-db7b-728127451176@lear.ch> (Eliot Lear's message of "Thu, 30 Jun 2022 21:35:09 +0200")
Message-ID: <yblpmioc2id.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/tJq2iABGga3tfZs_03gGqK7-zpk>
Subject: Re: [Rfced-future] Fwd: RFC 9280 on RFC Editor Model (Version 3)
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2022 14:48:45 -0000

Eliot Lear <lear@lear.ch> writes:

> I'd like to congratulate you on your hard work.  This wasn't easy-
> there was a lot of give and take by everyone.  Now the fun begins.  I
> hope to see you all in the RSWG!

I'll extend my personal congratulations to everyone as well.  It took
many view points, many compromises, and endless careful tracking prodding by
the chairs to achieve this milestone.  Thank you to everyone for all
your hard work, and most importantly, for proving that the IETF
consensus process can work even in the most trying of circumstances with
a very diverse set of starting opinions.

-- 
Wes Hardaker
USC/ISI

v2.23.0 | Report a Bug | By Email