IETF Logo Mail Archive

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

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 10 March 2022 15:38 UTC

Return-Path: <superuser@gmail.com>
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 20E283A11CF; Thu, 10 Mar 2022 07:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=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=gmail.com
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 2aNnt0_pUsI4; Thu, 10 Mar 2022 07:38:08 -0800 (PST)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 712033A11BB; Thu, 10 Mar 2022 07:38:08 -0800 (PST)
Received: by mail-vs1-xe35.google.com with SMTP id z85so6363784vsz.5; Thu, 10 Mar 2022 07:38:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+dgjAAtjppJlbyWiJwoK7KHnc629C2BPQyuBKKwIRtU=; b=A7QV7ChlWHR6cgJOVyVK8j0/rWTr1lFXMerYfP2mpSyyqwtyur5PQF3ykHtxPK1A1E PPUOQckVnLSJVGnML2VKGKDkMuPSZWV8R4fi4ka27HtRr5dUupI5OzHNZcUrb+YZYO88 rOB5M8E4b3UiMEuulo5SW4cZGNOedJ69aueJI4vcpVPrbqKp3k+ebkVMovU5p05nvUx8 UGpVJBW0y64s9yHRBwgNnhPBfbzv9tCwNMZ7wW+jsnYTWarINLucEywZflX95Mt1I2dk ajO3RdQplKC1VxlPDbMZT8yjD6UCI3dIbc+rjxaiVA9Lu2Xcl+CE8veSVcSW1ufwnutg A2Xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+dgjAAtjppJlbyWiJwoK7KHnc629C2BPQyuBKKwIRtU=; b=VHJ0WH0lOWUbwsO6dLiHKJUcv20+FRcKTzXRn22pGAaRzeCjuxs5whWcA3ZhkW9ImT HNvBe36pTWStSskKLVAsL+Jc1nMrlSRoOcUZ/bcnCzgQKhvVS5gGWGBfeUZ9QIhqqWBH 78XlRyFoXJEXO1T7CjAVoR3UZlwXbV4bkgPrM3GiUJAiUsS+Edu1DbFvQyWt8vfoaz3H M/wFloRwNKZI5E5TJRA+NboX2KlSNwPCECuSdbGHpkCns41RcWKYmgW8stFZ4NRWGvtt lRMbXa3E9NxU2PK8IwW6+cyX70OlxcfrhfqktiWJ1mZTqjvzG5IZ0XCoeJdMo0xPHApi 7xpQ==
X-Gm-Message-State: AOAM531Wei8zcT4k4MzQZ84UooNynzPRHHes9w0vYnIXQgATrwgwhp75 LhBu7jBPgjd86u9/XSQNeWWAo4bHeKN2sHpLC+s=
X-Google-Smtp-Source: ABdhPJzoB41H/jMSLSbnqx5lEAwrQJyHTE6Jupq1J0Kbj65GcnerlxfVRa9sjNIZvFjAykEewLoJ1ftHjYif30Ec6p8=
X-Received: by 2002:a67:b102:0:b0:320:7a21:f9a7 with SMTP id w2-20020a67b102000000b003207a21f9a7mr2362231vsl.79.1646926687096; Thu, 10 Mar 2022 07:38:07 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwbHobErxtCxiMCtYtqByJJhWF79XAwtw2jV9DNte1OuUQ@mail.gmail.com> <e3e01de3-8b69-852a-7dca-cb0e9735ce4a@lear.ch>
In-Reply-To: <e3e01de3-8b69-852a-7dca-cb0e9735ce4a@lear.ch>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 10 Mar 2022 07:37:55 -0800
Message-ID: <CAL0qLwZnaZ2J=7YnOS96h42135w6NrEdn-Obj7QOWwwRxDj1vg@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: rfced-future@iab.org, IAB IAB <iab@iab.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary="00000000000027d58105d9df00f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/EseUhG2UFGZ3kjs2qq88ymCssoE>
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 15:38:13 -0000

On Wed, Mar 9, 2022 at 11:10 PM Eliot Lear <lear@lear.ch> wrote:

> 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.
>

If we are to think of the RSWG as a typical working group (which the
document otherwise suggests is how we should think of it), then I can't
discount the possibility that something might be handed to the RSAB that is
not really ready for consideration, for whatever reason.  As I read what
you're saying here, this proposal presumes that can't (or won't) happen.
I'm thinking defensively here; what do we do when it does happen?  It seems
to me the RSAB needs a path to deal with such a situation, and they don't
with "CONCERN" constrained the way it is here.

-MSK

v2.23.0 | Report a Bug | By Email