Re: [Rfced-future] Fwd: New Version Notification for draft-iab-rfcefdp-rfced-model-12.txt
Eliot Lear <lear@lear.ch> Sat, 05 March 2022 12:41 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 005933A16F2; Sat, 5 Mar 2022 04:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 mUMUYmUt8QHu; Sat, 5 Mar 2022 04:41:30 -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 2BEDD3A16F0; Sat, 5 Mar 2022 04:41:27 -0800 (PST)
Received: from [192.168.0.227] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 225CfN9J277766 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Sat, 5 Mar 2022 13:41:24 +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=1646484085; bh=q0m3mmrhoQG7mkOXVavhmctIXcUHkbHgPwKRsxqswPk=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=UQJ4GG6KP3EA5ApP1tsjaDk6c4Dqclyo7n9+pSHIC0x0nPUQ6krv1ONoWPDkbo1Rq ZybfLrfCI4qKaYSkeunZv8vn/zahkqXsB4sp3Qa5HfUGdP/Qe6GtahRZ52V52baSLy iLydYsGLekC4PtacSyHB51i0lfyFfD5F7T9WNRvs=
Message-ID: <96ed7529-82e0-090c-7763-48baef4fb2ab@lear.ch>
Date: Sat, 05 Mar 2022 13:41:20 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Peter Saint-Andre <stpeter@stpeter.im>, "rfced-future@iab.org" <rfced-future@iab.org>
Cc: Internet Architecture Board <iab@iab.org>
References: <164644951964.28345.3666686025373602366@ietfa.amsl.com> <81baa054-cc5b-8134-b0f6-d9671edc86e8@stpeter.im>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <81baa054-cc5b-8134-b0f6-d9671edc86e8@stpeter.im>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------b50jQcr0pvn50AQm9DC0kGxs"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/yJYrAGPhSy5nAiJlZ8dLe_57aQ8>
Subject: Re: [Rfced-future] Fwd: New Version Notification for draft-iab-rfcefdp-rfced-model-12.txt
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: Sat, 05 Mar 2022 12:41:35 -0000
Thank you Peter. Please note that there are a good number of changes made. I don't think these changes substantially change the consensus established within the group, but people should review them for themselves. Eliot On 05.03.22 04:09, Peter Saint-Andre wrote: > Hi all, this version is my attempt to incorporate all feedback > received during the IAB's community call for comments. If I have > missed anything, please post to the rfced-future@iab.org list and I > will make the appropriate fixes in the next version. > > Thanks! > > Peter > > > -------- Forwarded Message -------- > Subject: New Version Notification for > draft-iab-rfcefdp-rfced-model-12.txt > Date: Fri, 04 Mar 2022 19:05:19 -0800 > From: internet-drafts@ietf.org > To: Peter Saint-Andre <stpeter@stpeter.im> > > > A new version of I-D, draft-iab-rfcefdp-rfced-model-12.txt > has been successfully submitted by Peter Saint-Andre and posted to the > IETF repository. > > Name: draft-iab-rfcefdp-rfced-model > Revision: 12 > Title: RFC Editor Model (Version 3) > Document date: 2022-03-05 > Group: iab > Pages: 32 > URL: https://www.ietf.org/archive/id/draft-iab-rfcefdp-rfced-model-12.txt > Status: https://datatracker.ietf.org/doc/draft-iab-rfcefdp-rfced-model/ > Html: > https://www.ietf.org/archive/id/draft-iab-rfcefdp-rfced-model-12.html > Htmlized: > https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model > Diff: https://www.ietf.org/rfcdiff?url2=draft-iab-rfcefdp-rfced-model-12 > > 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). In addition, > various responsibilities of the "RFC Editor Function" are now > performed alone or in combination by the RSWG, RSAB, RPC, RFC Series > Consulting Editor (RSCE), and IETF LLC. Finally, this document > establishes the Editorial Stream for publication of future policy > definition documents produced through the processes defined herein. > > This document obsoletes RFC 8728. This document updates RFC 7841, > RFC 8729, and RFC 8730. > > > > > The IETF Secretariat > >
- [Rfced-future] Fwd: New Version Notification for … Peter Saint-Andre
- Re: [Rfced-future] Fwd: New Version Notification … Eliot Lear