IETF Logo Mail Archive

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

Colin Perkins <csp@csperkins.org> Sun, 13 February 2022 14:22 UTC

Return-Path: <csp@csperkins.org>
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 349C13A1361 for <rfced-future@ietfa.amsl.com>; Sun, 13 Feb 2022 06:22:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
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 AamRKEA7b3LJ for <rfced-future@ietfa.amsl.com>; Sun, 13 Feb 2022 06:22:51 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 16ADA3A09A5 for <rfced-future@iab.org>; Sun, 13 Feb 2022 06:22:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:From:Subject; bh=fK3RitVoOXsf7JVBo8/MGkBUNyV0YOW3r6CeidIgZWM=; b=SUVMGEcfpx76IsdgEw1JzEQWaV S3RdfJh9sXB+ToB5vzVqL1i3cBmk75FEVWFfU5nSc1hUiPmQlMMkhWsRqtIZfOw2CmfePwg8DL4dB QB32OdAM/su3DJQ8/y0hLub4K3nhhRgpEhs//LRzSXL4txAGKgcUTg054mX/m0mjLVf0nV5bA34nt GDaRXHPXEqUfsXXPqwp42MyDsF+LybdRiRrqVvImbJ2ScdHWKY79MqUAROATI6HrT4dbXtnNeCmoV UnK1OYg4jr+P3FeCwP70pDwMcOlJ/pN0nN2MTyiVk5Am5xeGia+fzEvcGZSIh+aWnPbAAl4Hh2gIQ FGn3bZBQ==;
Received: from [81.187.2.149] (port=46459 helo=[192.168.0.67]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1nJFly-0006k1-1B; Sun, 13 Feb 2022 14:22:46 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <119208ad-0e6c-3613-bda6-862c25f344a5@stpeter.im>
Date: Sun, 13 Feb 2022 14:22:36 +0000
Cc: "rfced-future@iab.org" <rfced-future@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <26B8240B-1A29-4F0D-A92F-7BA4E4FC9EAD@csperkins.org>
References: <164372674609.19964.5179148622014680461@ietfa.amsl.com> <119208ad-0e6c-3613-bda6-862c25f344a5@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.3445.104.21)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/rZdjnmORnwBuPzJB1j_m73GY5Do>
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:22:57 -0000

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



-- 
Colin Perkins
https://csperkins.org/

v2.23.0 | Report a Bug | By Email