Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model

Eliot Lear <lear@lear.ch> Thu, 10 March 2022 07:10 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 40E083A0898; Wed, 9 Mar 2022 23:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 D2sPlxAvAQQX; Wed, 9 Mar 2022 23:10:15 -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 206443A0848; Wed, 9 Mar 2022 23:10:14 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::b] ([IPv6:2001:420:c0c0:1011:0:0:0:b]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 22A7A9Kg657491 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 10 Mar 2022 08:10:10 +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=1646896210; bh=iMW9rEF5mGGT4N04CGl+j0oUWbF8cE+QZIFpkD7meMA=; h=Date:To:References:From:Subject:In-Reply-To:From; b=qlHND/5DD3L35zhtJ9GgP2w5gKn7/P6JXK6leHpJz3TfgyMD+8Gyf7CwcMNfmWAAk xfiljZwFIUoJyTOz0eRjatXNww8Ne8dMx0+fJW/0gK58r+DqURN2WdF9AadW11z/8N U6S6B7v2oEHDaG3A5fJ0BQNkePt/x6ftfS4qhfmY=
Message-ID: <e3e01de3-8b69-852a-7dca-cb0e9735ce4a@lear.ch>
Date: Thu, 10 Mar 2022 08:10:08 +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.2
Content-Language: en-US
To: "Murray S. Kucherawy" <superuser@gmail.com>, rfced-future@iab.org, IAB IAB <iab@iab.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
References: <CAL0qLwbHobErxtCxiMCtYtqByJJhWF79XAwtw2jV9DNte1OuUQ@mail.gmail.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <CAL0qLwbHobErxtCxiMCtYtqByJJhWF79XAwtw2jV9DNte1OuUQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------FrGokxA1LYueel51efce8ifq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/hzzUxVjlCyibNiB9QwacqG5Oj04>
Subject: Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model
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: Thu, 10 Mar 2022 07:10:21 -0000

Hi Murray,

On 10.03.22 07:33, Murray S. Kucherawy wrote:
>
> Bullet 9 also enumerates specific reasons one might use a "CONCERN" 
> position.  Notably absent from this list is the notion that some 
> aspect of the proposal under consideration is not written with 
> sufficient clarity that it can be understood or unambiguously 
> implemented.  I suggest that such a thing might be a valid reason to 
> hold progress for further discussion, or to return the item to the 
> RSWG for development.  Another possibility is an observation by an 
> RSAB member that the procedures described in this document prior to 
> consideration by the RSAB were not properly followed, which might also 
> be a reason to return the work to the RSWG for further development or 
> other handling.
>
The philosophy behind CONCERNs is that they should be rare, and that the 
community really should be taking responsibility for the content of a 
document.  Thus, unless something truly rises to a threat to a stream or 
the long term health of the series, the RSAB should stay out of the 
way.  Those two CONCERN criteria are sufficiently broad to permit 
members to act if the policy truly looks like it will cause harm in some 
way.

Eliot