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

Mark Nottingham <mnot@mnot.net> Sun, 09 January 2022 09:21 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 6001A3A1081 for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 01:21:58 -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=jHj3ouys; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IOs0q7/O
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 u9IW9DRzcFsS for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 01:21:53 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E3103A107F for <rfced-future@iab.org>; Sun, 9 Jan 2022 01:21:53 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 54E373201FCE; Sun, 9 Jan 2022 04:21:52 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 09 Jan 2022 04:21:52 -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=p 6r4Z/gD80qtoYjQBeggZ2gHtEBbiVggwxKcGy8iwPA=; b=jHj3ouys6GNFoTn7g UvgC87MGPVf8sA38DBpS7DR52/WpohMaMrSfL4HhNdv7+IBURflEQ2eVj5JbRniT uvP2asYHG6dyvTp1w0vdsxaWz5BtJp2wlX4iTDlnY/GWlT9rShOUGQmF4CJy8wQU N8zZ2ctbt5RtUNNMrlOQNI4RmBoi4k8TvY+G4q3VfNYGx54gSpV+v208yyKTS6Nz A44xzpMNzFLNq0EOWkp7UXeAePnTAxMlRVjfiN+r4Vpwh8ueG7P/aUrmx2mwfUNk TS2QoaYOl99gMm5r0EqwHTJLguTGNL7BDYywn9q6pT/XfZodwvEIikXALsKS4WTn tltuw==
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=p6r4Z/gD80qtoYjQBeggZ2gHtEBbiVggwxKcGy8iw PA=; b=IOs0q7/OoEgtaZlCvXSkEebJ01r7VcEv0jXLbCSLQ33+zpIKPbJ6HW3VD AcFV42DaK6IXaqW4y99VPcqNedOCRQiN5QnGNe6Yn1rNqvc9QW3VrGmtJ9/qEv6g g+pJIbSknqOyUPE6JLc0Smrfv/meRxzeRFKm1fdCySR2aLWhG5cElxf7aCBEYg0x 610Mgu0Trr933uK42EYUtgzD0bPI6HZm1uwRydIZWKLcEC83uXyAZ0J3O+Fw0+++ vnDSm1rp8e93Bnt5yCeOszWAe5xUxx2i1fUfO7XPyRjldmf2wB238UCUOnnkbLfv I7qBlOYn5wydcvOsjy6j/4A8A6Aww==
X-ME-Sender: <xms:L6naYXuoi7Ukm3FeTDoNJTjPH3qAL-8r-sWTRfXEb2uZrhfIxsUw9Q> <xme:L6naYYdaLwlIAxtdGCN_yBO9mfIl7bre3xWb0jfQGKk8ZeXEqMbdOXUOQi042z_HN af7pfgkJt3NIU1QZg>
X-ME-Received: <xmr:L6naYawtU_JH87zXUD1pXcZp1Cv9Jg2QIBP87tQk7YwReZQQXt-wsm3RURMVBQNQeJThnTN6kBhaFbsQBs-cMzQ2p-4jmcJ0S8Cn-hdIEgkCVkyxKlRfVOPd>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudegkedgtdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeevffffhfduteevvefhueffieegtdeutdehffeltefffedttdeggeejheeiueet teenucffohhmrghinhepmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:L6naYWNm5m_e0tYkWcuoyFzSIrIw9gqKP-t6jhqUvTgFPWxEVPsUtw> <xmx:L6naYX9Onh76tT7KIqeW_BgfrtpCVIlxe7FlwQWp9uqI1jf8T2msbw> <xmx:L6naYWUi6EPg1B7H4NA8YnVXYHunrj3ta4PBt1x9sFLZ2IgsdbX3Qg> <xmx:L6naYTbtqWyA0am6NhSSnmKqm2jgMRHdwJ8wAgFoJjq8uao3KY6dRw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 9 Jan 2022 04:21:50 -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: <756d6495-700f-04a2-da42-be730e4f3d5d@lear.ch>
Date: Sun, 09 Jan 2022 20:21:47 +1100
Cc: Peter Saint-Andre <stpeter@stpeter.im>, "rfced-future@iab.org" <rfced-future@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E200308A-316F-4A1B-A464-6B96E76B3349@mnot.net>
References: <164159953944.5205.10517887235280838552@ietfa.amsl.com> <1e6664f9-f19d-a226-e709-d03fe6968497@stpeter.im> <116833C8-6D7C-43B3-A91A-E63FCCE7C448@mnot.net> <756d6495-700f-04a2-da42-be730e4f3d5d@lear.ch>
To: Eliot Lear <lear@lear.ch>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/VTlpTpRhIRmBRgzSqr80cOaTN5U>
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 09:21:59 -0000

Not particularly. The previous text was fairly matter-of-fact, explaining the nature of meetings, whereas this (through use of "empowered" and the seemingly exclusive "or") seems more prohibitive. You are right to point out that it can be varied, so maybe it's isn't such a big deal.

Cheers,


> On 9 Jan 2022, at 7:59 pm, Eliot Lear <lear@lear.ch> wrote:
> 
> Hi Mark,
> 
> Just on one point:
> 
> On 09.01.22 09:23, Mark Nottingham wrote:
>> 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.
>> 
> Do you have a good wording suggestion for this, bearing in mind the text below?
> 
> 
>>    The RSWG may decide by rough consensus to use additional tooling
>>    (e.g., GitHub as specified in [
>> RFC8874
>> ]), forms of communication, and
>>    working methods (e.g., design teams) as long as they are consistent
>>    with [
>> RFC2418
>> ].
>> 
> 
> 
> Thanks,
> 
> Eliot
> 
> 

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