Re: [Rfced-future] New Version Notification for draft-iab-rfcefdp-rfced-model-11.txt

Eliot Lear <lear@lear.ch> Sun, 13 February 2022 14:33 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 C2A923A0A8B for <rfced-future@ietfa.amsl.com>; Sun, 13 Feb 2022 06:33:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level:
X-Spam-Status: No, score=-2.803 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, 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 a8tT6gKRcNVJ for <rfced-future@ietfa.amsl.com>; Sun, 13 Feb 2022 06:33:46 -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 43B4B3A0A2D for <rfced-future@iab.org>; Sun, 13 Feb 2022 06:33:44 -0800 (PST)
Received: from [192.168.0.228] (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 21DEXaPm075636 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Sun, 13 Feb 2022 15:33:40 +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=1644762820; bh=HgsL40kGRjG3M1nWtLa+P76lWHlOOa4VDHpKjLz2LpM=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=o4qHLEPHs6Ie+632jSymlotphRDil50h5tj3Tp73P9AR3ZVBtHg7vLG1t2LGJYs7h 5T3i6p4qq39wxAWy7bL5CzfBnQtDyBS3nl5/8OJbQspVXKR2XGfppvyU8GkBBveBlv H1JDGDhZe6qAYAXVZmETb9iemgylSCsOmqxhRr9U=
Message-ID: <26755db2-c277-e867-2774-0685c483ebc4@lear.ch>
Date: Sun, 13 Feb 2022 15:33:34 +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.0
Content-Language: en-US
To: Colin Perkins <csp@csperkins.org>, Peter Saint-Andre <stpeter@stpeter.im>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>
References: <164372674609.19964.5179148622014680461@ietfa.amsl.com> <119208ad-0e6c-3613-bda6-862c25f344a5@stpeter.im> <26B8240B-1A29-4F0D-A92F-7BA4E4FC9EAD@csperkins.org>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <26B8240B-1A29-4F0D-A92F-7BA4E4FC9EAD@csperkins.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------JxOJzjkij0oSy39oqy05PDRt"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/PTcPpkOdewLLXHC4-sDDlOvYOao>
Subject: Re: [Rfced-future] New Version Notification for draft-iab-rfcefdp-rfced-model-11.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: Sun, 13 Feb 2022 14:33:52 -0000

Thanks for the read through and those points.  The chairs are capturing 
all proposed changes.

Eliot

On 13.02.22 15:22, Colin Perkins wrote:
> On re-reading this draft, I noticed the following two points:
>
> §3.1.1.4: "The intent is that the RSWG shall operate in a way similar to working groups in the IETF and research groups in the IRTF."
>
> §3.2.2: "the RSWG may adopt the proposal as a draft proposal of the RSWG, in much the same way a working group of the IETF or research group of the IRTF would"
>
> There are some significant differences in the way IRTF and IETF groups are permitted to operate. To avoid confusion, these sections might be better phrased by omitting the references to IRTF.
>
> Apologies that I didn’t catch these earlier.
>
> Colin
>
>
>
>
>> On 1 Feb 2022, at 14:47, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>>
>> FYI.
>>
>>
>> -------- Forwarded Message --------
>> Subject: New Version Notification for draft-iab-rfcefdp-rfced-model-11.txt
>> Date: Tue, 01 Feb 2022 06:45:46 -0800
>> From: internet-drafts@ietf.org
>> To: Peter Saint-Andre <stpeter@stpeter.im>
>>
>>
>> A new version of I-D, draft-iab-rfcefdp-rfced-model-11.txt
>> has been successfully submitted by Peter Saint-Andre and posted to the
>> IETF repository.
>>
>> Name:		draft-iab-rfcefdp-rfced-model
>> Revision:	11
>> Title:		RFC Editor Model (Version 3)
>> Document date:	2022-02-01
>> Group:		iab
>> Pages:		32
>> URL: https://www.ietf.org/archive/id/draft-iab-rfcefdp-rfced-model-11.txt
>> Status: https://datatracker.ietf.org/doc/draft-iab-rfcefdp-rfced-model/
>> Htmlized: https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model
>> Diff: https://www.ietf.org/rfcdiff?url2=draft-iab-rfcefdp-rfced-model-11
>>
>> 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.
>>
>>
>>
>> The IETF Secretariat
>>
>>
>> -- 
>> Rfced-future mailing list
>> Rfced-future@iab.org
>> https://www.iab.org/mailman/listinfo/rfced-future
>
>