IETF Logo Mail Archive

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

Peter Saint-Andre <stpeter@stpeter.im> Tue, 01 March 2022 18:40 UTC

Return-Path: <stpeter@stpeter.im>
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 098083A09AB for <rfced-future@ietfa.amsl.com>; Tue, 1 Mar 2022 10:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 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.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=q6kmli3C; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ksSgXmdu
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 99Gzlbkxu5CZ for <rfced-future@ietfa.amsl.com>; Tue, 1 Mar 2022 10:40:09 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D2593A0988 for <rfced-future@iab.org>; Tue, 1 Mar 2022 10:40:09 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 91ABE3201134; Tue, 1 Mar 2022 13:40:07 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 01 Mar 2022 13:40:07 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; bh=9EJYJcmV9jmnMr 9ADFPYrv8XFSwJUx14lxdoQY6tIIQ=; b=q6kmli3C8HhFbNt/KWpI8LIh24W57Z FeMzVq6MIeNsdKMalvk/bqa7x1D0khQn3Q63kxjNrIFaLN3nuV/3c0cpnVhMNCBt 5moYOpTAHpJ8NGReAZp5wDR/6abLZbUSNvLQWHwoP8a8ADqRbbzLG5KdqE3uX91X ZaVJLxsPutDEqwJ+kbVPPHd0Md98ufssrK2geCdRMVD2DXNLnbTvU2sDDUoXDbVy c5t/2uoPLoH5omdLgI5IcwG08tgIO9j2mfiOsfAsv5uGWMQ7ciec6wZ2SUCEF1Ul 5niogPFkXHG8SDFUH0GxWvXm3PwA3bHXzCflldeY9lR/jB9YQl5vuPBQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=9EJYJcmV9jmnMr9ADFPYrv8XFSwJUx14lxdoQY6tI IQ=; b=ksSgXmduDkvkohPx+dXp4Hv6YUrWmaU1qzgCql2lDvHBB7rOE9FxFfgk2 j227em2i03P0jwo/il31V3D8ZUZUUy91PwxrR9ncK/ROCkO4CXj5UEgr3PqF7m+R DMzDDzMHsd0Ir2C7mCzHOGsIZxzPx4HDvRcro5oDR+kSuyNcHDHkfx7vpDB2f5DE Um0veaUKLGVnjq9QOPCO7M0sL3XUE+GbvUgUi3B3rpIo3hZU9aIwXsTZ+q64Apo+ 0mCsm8QyTcmVMqRE1JNc+3b+quz/cgwKAVPwT+gVPdKMlEVx5sXgJOvd0nGmHpwQ 10qrwoNDN19iRpQd3dQYOhUq80xTg==
X-ME-Sender: <xms:hmgeYgGOuNvwX1cohXGprXUVLUDVLsyOGdbFoInEIaeuC7ilwXlIAg> <xme:hmgeYpV4C2zeyO47bKxrQCMlRNK5FIlKtSPBaIYeGzumD0tRPFc7Br_3h5jpI7BJr MHbllzcLUdiSiAiHQ>
X-ME-Received: <xmr:hmgeYqKN9KWbcyF4COg0fOvWDpb2Xt1iqrrW42gc10jMwEUpy9F4KsIA_q8A9IAipZGMJUW9d8migcWQAmdE53RV67IXVBUmSLKURVI>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddtvddgudduvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ekredttdefjeenucfhrhhomheprfgvthgvrhcuufgrihhnthdqtehnughrvgcuoehsthhp vghtvghrsehsthhpvghtvghrrdhimheqnecuggftrfgrthhtvghrnhepvedtgfettefgff evheetvddugedugfelveeftdelveetgfefgefggfefledukeehnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshhtphgvthgvrhesshhtphgvth gvrhdrihhm
X-ME-Proxy: <xmx:hmgeYiFGm7Ic5xCvFGmOQJEs90ctwy5SO03W1TBAqjxmo-FF27driQ> <xmx:hmgeYmVGzg3ZOya87KXD5pYap3unbzhhHdcQ1KAQppgK713aXw3zkw> <xmx:hmgeYlNTFTB8ZLtPVdQS8Apq7a7r2-Gbh__EVU-kl4JWtdh1EatcNg> <xmx:h2geYpeUrjO0uW0LS8-NS5l0HES94Cq0CjXfcI5CPo4X-4h7QWBA9g>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 1 Mar 2022 13:40:06 -0500 (EST)
Message-ID: <1318a9b8-8770-70c8-b593-5112744bc29b@stpeter.im>
Date: Tue, 01 Mar 2022 11:40:05 -0700
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: Colin Perkins <csp@csperkins.org>
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: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <26B8240B-1A29-4F0D-A92F-7BA4E4FC9EAD@csperkins.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Do8MG3iwEqPlOvHcyQYEVtpERe0>
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: Tue, 01 Mar 2022 18:40:14 -0000

On 2/13/22 7:22 AM, 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.

Noted. This change will be in version -12 of the document (more about 
that soon).

Peter

v2.23.0 | Report a Bug | By Email