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

Mark Nottingham <mnot@mnot.net> Sun, 09 January 2022 08:23 UTC

Return-Path: <mnot@mnot.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 2F8343A0D5D for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 00:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=mnot.net header.b=pR07qqSj; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=FTcRqb4J
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 wRrThec8VNqt for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 00:23:45 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 827F93A0D5A for <rfced-future@iab.org>; Sun, 9 Jan 2022 00:23:45 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id DCC683200D78; Sun, 9 Jan 2022 03:23:44 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 09 Jan 2022 03:23:45 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=2 JHgAyxHoFPrwRRijEbERSg0srBV+neN7N+MU1LfHxA=; b=pR07qqSj732EnfDxN iVqknT/QXBevy7NA3yn/Eyk6rBe2BrX0noIfmaYE5Q4lTM04ef5Jf6onhplFJ5DD JfZSi8DM0143ntfgPyCLgtFlMTyZ+rSsnGozAq5DYxgy0WleGxxHaOInpbCbGc07 kiclw/RHnmPqHi4hB7WcdgsXxRFen/rQng/OUjB3qaECsSReRjUu9PNQXN1Fa6vi A0peNdWdsRD8kPlMws/As6SBelDDdLRxaFcQmU7ie5zyqTraoG4IOSgkO2jOeb0w X7gS6haUHEz+XCcaNiK6AyT2mSD89Yes8AW6S/eOUbeihKBOsJiNytND7SprhJkC QhdiQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=2JHgAyxHoFPrwRRijEbERSg0srBV+neN7N+MU1LfH xA=; b=FTcRqb4JgVvyp8Rjug5VsdK/khec3EIRdWgQxtRkI/AHvEguVtEd5pS3L fNZJArhvr5lhxFfQvNxq+cGMA79Mc84l8yelVRjbiGvhSq7E0jAqajH9JxB1/XSv JOCflwPfr/+LUHe7EMUrARV6Jqu7lxsICZbXZ7rd7D6vxVsvF8ea38k6ZSScH/9Q Lt3hczGS6iMl+CDae/NcgkCOOl/J4L5i+g1ZN3FyCw7UXRRMeKI1ra9wXe2ihuvG gqmX40TFXENjOlMbvcpm4eMJvOJ/5Ffmdww6s1cLBftmfh/350AG0Duk0V6gIS12 WYeNiqZC1+gjCCTFO5vp+OeBi6KBA==
X-ME-Sender: <xms:kJvaYfYXMIsVtLbcrpHBq-5O6pbePU-m_u1pSUcnOrM0CeVIOQVxhQ> <xme:kJvaYeZTvyu4hypCst4bwqCuAepSYj7hSCq7ygOuaqkx6f09z5D6-r1wkHFjAoe8K DNUjz8Q-tg3SeZv6Q>
X-ME-Received: <xmr:kJvaYR-1P0lx3xW1TNQMtbeqmIZSxSGdwuMTnAbuQsjSt2B568dp2YP1iLgR7BQJceLUaGhk66pcT0hCIIVLs6n-Zikz3pRamPash9YP8RDYIlnMQb3LzMse>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudegjedgudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeeiteduuddvudfftedtuddvgeehtdeuheehjeegledtleekvefgffehfefffeff gfenucffohhmrghinhepihgvthhfrdhorhhgpdhirggsrdhorhhgpdhmnhhothdrnhgvth enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhho thesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:kJvaYVpkUYwnX_NhmicCg7FtW5ks5oD0k7kuN6j-aMjvRoRLY1kiPw> <xmx:kJvaYapaDKpN2hiTeqWcdqwgJnz2eEblOL3R5AnikU1aUSFi6Z07PA> <xmx:kJvaYbTyVQKfqgNosufYBoLEUAAgqp2HwnxX3PoHJmffc1UTmsWk5w> <xmx:kJvaYdV6fnSSEKZL5l7PqtPtrV1UdevoBak2biVKITutASn3JMJK0A>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 9 Jan 2022 03:23:43 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <1e6664f9-f19d-a226-e709-d03fe6968497@stpeter.im>
Date: Sun, 09 Jan 2022 19:23:40 +1100
Cc: "rfced-future@iab.org" <rfced-future@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <116833C8-6D7C-43B3-A91A-E63FCCE7C448@mnot.net>
References: <164159953944.5205.10517887235280838552@ietfa.amsl.com> <1e6664f9-f19d-a226-e709-d03fe6968497@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ewYYNum5t-foz0mde_GJqGUCw_w>
Subject: Re: [Rfced-future] New Version Notification for draft-iab-rfcefdp-rfced-model-08.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, 09 Jan 2022 08:23:50 -0000

Hi Peter,

Thanks. Looking through the diffs, I noticed a few things:

* "The RSWG is empowered to hold in-person or online-only meetings" -- this wording could be interpreted to prevent hybrid meetings, or online participation in in-person meetings.

* "The RSAB consists primarily of certain voting members.  As specified herein, the RSAB also includes certain non-voting members." -- this is quite wordy...

* "The RFC Series Consulting Editor, in effect representing the Editorial Stream" -- my understanding was that the RSCE's inclusion on the RSAB was not only for this purpose, so this could mislead. Also, it makes this text somewhat contradictory: "Note: this method of handling vacancies does not apply to a vacancy of the RSCE role, To ensure the smooth operation of the RFC Series, the RSAB shall only of the stream representatives enumerated above."

* "Email messages sent to the RSAB email discussion list or exchanged among all members of the RSAB shall be publicly archived..." -- I think the "or exchanged among all members of the RSAB" clause is impractical and ineffective, and it should be removed. I don't feel strongly about it to formally object, though.

Cheers,



> On 8 Jan 2022, at 10:53 am, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> 
> As promised...
> 
> 
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-iab-rfcefdp-rfced-model-08.txt
> Date: Fri, 07 Jan 2022 15:52: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-08.txt
> has been successfully submitted by Peter Saint-Andre and posted to the
> IETF repository.
> 
> Name:		draft-iab-rfcefdp-rfced-model
> Revision:	08
> Title:		RFC Editor Model (Version 3)
> Document date:	2022-01-07
> Group:		iab
> Pages:		31
> URL: https://www.ietf.org/archive/id/draft-iab-rfcefdp-rfced-model-08.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-08
> 
> 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

--
Mark Nottingham   https://www.mnot.net/