IETF Logo Mail Archive

Re: [Rfced-future] Fwd: Call for Comment: <draft-iab-rfcefdp-rfced-model-11> (RFC Editor Model (Version 3))

Eliot Lear <lear@lear.ch> Tue, 08 February 2022 20:23 UTC

Return-Path: <lear@lear.ch>
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 C4FF13A03F7 for <rfced-future@ietfa.amsl.com>; Tue, 8 Feb 2022 12:23:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.802
X-Spam-Level:
X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
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 mqyXKrHUj3vE for <rfced-future@ietfa.amsl.com>; Tue, 8 Feb 2022 12:22:56 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40CE03A0123 for <rfced-future@iab.org>; Tue, 8 Feb 2022 12:22:53 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::5] ([IPv6:2001:420:c0c0:1011:0:0:0:5]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 218KMli1650914 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 8 Feb 2022 21:22:48 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1644351768; bh=MW6jKgOiJa0npiKT9bttyvfTmLvKEuORZ/QoNywKyVI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=o1dIXDLv857xhMY1mjkcjYQmRBYbwPHyz49yUY1CTChepRIUkddd8hL2qFydboe5H xMbk41aA6shYz9veCJeshCWuLGoFtJxswBIO+/gpJ59Fr2YVM4tE36pG/Fv6moFYUv iXocc80X0QuuIltRCtJKzIZYLyV5hQkcCXoEa0P4=
Message-ID: <64dcc042-b119-ef90-3877-81a9335edad0@lear.ch>
Date: Tue, 08 Feb 2022 21:22:46 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1
Content-Language: en-US
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Cc: rfced-future@iab.org
References: <164425740397.25489.18392670988853927409@ietfa.amsl.com> <370a835f-6fec-1b63-0224-df583a4a43a9@lear.ch> <CANMZLAZXwogVdnZZFqAa7kkEJQL1phToXQWi9Qzkn4jegdHbsQ@mail.gmail.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <CANMZLAZXwogVdnZZFqAa7kkEJQL1phToXQWi9Qzkn4jegdHbsQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------GsrFE6LkJkNRX6bi0aEw00MJ"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/BMnBwqIJ6iR-T0zRlzShI1XZttQ>
Subject: Re: [Rfced-future] Fwd: Call for Comment: <draft-iab-rfcefdp-rfced-model-11> (RFC Editor Model (Version 3))
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
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: Tue, 08 Feb 2022 20:23:02 -0000

For information?  Why not?  But it might just be easier for people 
participating in those organizations to share the announcement.  I don't 
think we can reasonably expect many organizational responses in a 
month's time, tho.

Eliot

On 08.02.22 09:05, Brian Carpenter wrote:
> Should the IAB send it via liaisons to other SDOs?
>
> Regards,
>     Brian Carpenter
>     (via tiny screen & keyboard)
>
> On Tue, 8 Feb 2022, 20:03 Eliot Lear, <lear@lear.ch> wrote:
>
>     Hi everyone,
>
>     You may wish to forward this announcement widely to those who
>     might have
>     some interest or insight.
>
>     Eliot
>
>
>
>
>     ---------- Forwarded message ----------
>     From: IAB Executive Administrative Manager <execd@iab.org>
>     To: IETF Announcement List <ietf-announce@ietf.org>
>     Cc: last-call@ietf.org, irtf-announce@irtf.org,
>     rfc-interest@rfc-editor.org, architecture-discuss@ietf.org
>     Bcc:
>     Date: Mon, 07 Feb 2022 10:10:04 -0800
>     Subject: Call for Comment: <draft-iab-rfcefdp-rfced-model-11> (RFC
>     Editor Model (Version 3))
>     This is an announcement of a community-wide Call for Comment on
>     draft-iab-rfcefdp-rfced-model-11.
>
>     The document is being considered for publication as an
>     Informational RFC
>     within the IAB stream, and is available for inspection at:
>     <https://datatracker.ietf.org/doc/draft-iab-rfcefdp-rfced-model/>
>
>     The Call for Comment will last until 2022-03-07. Please send
>     comments to
>     rfced-future@iab.org and iab@iab.org.
>
>     Abstract:
>
>        This document specifies version 3 of the RFC Editor Model. The
>     model
>        defines two high-level tasks related to the RFC Series. First,
>        policy definition is the joint responsibility of the RFC Series
>        Working Group (RSWG), which produces policy proposals, and the RFC
>        Series Approval Board (RSAB), which approves such proposals. 
>     Second,
>        policy implementation is primarily the responsibility of the RFC
>        Production Center (RPC) as contractually overseen by the IETF
>        Administration Limited Liability Company (IETF LLC).
>
>        This document obsoletes RFC 8728.  This document updates RFC 7841,
>        RFC 8729, and RFC 8730.
>
>     This IAB Call for Comment is running concurrently with the IETF Last
>     Call for the following related IETF-stream documents:
>
>     https://datatracker.ietf.org/doc/draft-carpenter-rfced-iab-charter/
>     https://datatracker.ietf.org/doc/draft-rosen-rfcefdp-update-2026/
>     https://datatracker.ietf.org/doc/draft-rsalz-2028bis/
>
>     _______________________________________________
>     IETF-Announce mailing list
>     IETF-Announce@ietf.org
>     https://www.ietf.org/mailman/listinfo/ietf-announce
>     -- 
>     Rfced-future mailing list
>     Rfced-future@iab.org
>     https://www.iab.org/mailman/listinfo/rfced-future
>
>

v2.23.0 | Report a Bug | By Email