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

Eric Rescorla <ekr@rtfm.com> Tue, 01 March 2022 18:46 UTC

Return-Path: <ekr@rtfm.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 9060D3A09D6 for <rfced-future@ietfa.amsl.com>; Tue, 1 Mar 2022 10:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.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 DneJ38B7dh8K for <rfced-future@ietfa.amsl.com>; Tue, 1 Mar 2022 10:46:23 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 47E1A3A09E3 for <rfced-future@iab.org>; Tue, 1 Mar 2022 10:46:23 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id w7so19545997ioj.5 for <rfced-future@iab.org>; Tue, 01 Mar 2022 10:46:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r+LAnlLfinTHDfjFNcls6zmHdb2ApxPeQWnRww6tcxo=; b=JcJGLEwKgOobyOJu/aWl6EmJuEaLqOtJU9qklcnhaV4vioGXb/zUB9iLkQApmzy5/M rZbK+CbnlyZKQfSfOR1Z1VJBbs8U8+/59BfU99m1d1obaqwfpfN/tlTZK+E1azV1sedJ StKaoNn7kDYReyIPwE3/1lQN9slnzUy9Ug43F7b3HbYSwQZCE9C5kQFoveYjhIq+aOZx dkc/K3ZHPd5xmWnsaGS/yHC2sMMDgY19+BsgtGGRaVvpetKA8EfJiX6hRQVdrl2j7Qgn jOCPSAfa4YB3dT7QIFzxH/S74VAZHbSnx//dDgSQr96DOqFsnJ+XgAxofnYvCFY0DegE FVmA==
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=r+LAnlLfinTHDfjFNcls6zmHdb2ApxPeQWnRww6tcxo=; b=svE91rBn9RJhsj9njFsj8QeULNIWewA59CuEglJfnJXJprqkIEh3k8BSOP/it3J8H0 1+G0Jiok4+/7eNv3Mr/3BvnNzjK7CaSWMmFW5bKkyi5Js9P/NcJhYohSL2HYH7BVOlWg rnF3GgPx6MX+o8IW92iniR989tfTLUSInd+E8aHZ7wfPIOvn/Fv5EhDf2rlih7eCdxkU +5i4fxXQSqH6Q79P3PZaCddFLqgWxnPCzehUAl0/iWkNOcK3JsYfMLn+SydwKMKRUShz f8asbTtC10yKrcrzFU4wBLASZO+3D/fXTy+jOWVsKbR5aIwSOmI94E9PCbJrmG1a0h4d A1QA==
X-Gm-Message-State: AOAM5338JCKDrJZxq2Xo/9pgMPjaNm8AB4TMwIVE11ABvquDaTcMp28V 37ZcvEnlKTW4g0TgE+vj/bgxgmrpH8QKMuXuyA10cw==
X-Google-Smtp-Source: ABdhPJwnocyJKWJE9lt/18E8BmF3BK57pW04MaWOCjY0A6G+UXWMPTcoP0BQMn89DPTfHMAJ++zP69USpqSLLIH7akk=
X-Received: by 2002:a02:a398:0:b0:314:ad84:75fd with SMTP id y24-20020a02a398000000b00314ad8475fdmr21572466jak.20.1646160382190; Tue, 01 Mar 2022 10:46:22 -0800 (PST)
MIME-Version: 1.0
References: <74AF211B-741E-46FC-9E35-8015D5254515@icann.org> <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch> <0c1711fe-bc05-e6b0-2f94-eb1c24ae3766@stpeter.im>
In-Reply-To: <0c1711fe-bc05-e6b0-2f94-eb1c24ae3766@stpeter.im>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 01 Mar 2022 10:45:46 -0800
Message-ID: <CABcZeBPqGHt0KD4tjQZFd7SVRwQHVa7fj7wJ_LYCn-3XQKjfjg@mail.gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Cc: Eliot Lear <lear@lear.ch>, Paul Hoffman <paul.hoffman@icann.org>, "rfced-future@iab.org" <rfced-future@iab.org>, "iab@iab.org" <iab@iab.org>
Content-Type: multipart/alternative; boundary="000000000000d2f83305d92c94fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/hvEjeEl1x773T-A847WZQi289JI>
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: Tue, 01 Mar 2022 18:46:29 -0000

On Tue, Mar 1, 2022 at 10:36 AM Peter Saint-Andre <stpeter@stpeter.im>
wrote:

> On 2/10/22 7:42 AM, Eliot Lear wrote:
> > Hi Paul,
> >
> >
> > On 09.02.22 17:46, Paul Hoffman wrote:
> >> Greetings again. The structures proposed in this document seem like a
> >> very good way forward. The level of detail about the expectations on
> >> each group is a good balance in prescriptiveness.
> >>
> >> Two small thoughts on the current draft:
> >>
> >> The future status of the rfc-interest mailing list is unclear; see
> >> Section 3.2.3. Given it s current contents, I could see that it would
> >> easily become a parallel track for discussions that should be on the
> >> RSWG mailing list. It might be good to close (and certainly archive!)
> >> rfc-interest unless it becomes more moderated by someone pointing
> >> discussions to the RSWG.
> >
> > I like the idea of at least having some RSWG participation to point
> > people to the right place, when necessary.
>
> Keeping the rfc-interest list and starting a new list for the RSWG might
> indeed lead to confusion.
>
> Here is a proposed change:
>
> OLD
>
>     The RSAB seeks
>     such input by, at a minimum, sending a notice to the rfc-interest
>     mailing list or to its successor or future equivalent.
>
> NEW
>
>     The RSAB seeks
>     such input by, at a minimum, sending a notice to the mailing list of
>     the RSWG (which should supersede the current rfc-interest list).
>

I actually don't agree with this. I think the WG should have a separate list
that is moderated by the chairs. The rfc-interest list can continue, but
I think the new model deserves a new list.

-Ekr


>
> >> Someone is going to have to tool the tracking for RSWG documents after
> >> they leave the RSWG, given that this is a new process. That might be
> >> informal (but public) tracking, but I suspect that formally tracking
> >> the various rfc799*-bis documents will prevent later issues from
> >> arising based on missed cross-dependencies. Maybe adding a sentence or
> >> two about this to the current draft will keep it in our minds as we
> >> move forward.
> >
> > Good idea.  Perhaps something along the lines, “The LLC is requested to
> > provide necessary tooling to support RSWG and RSAB decision processes
> > and policies.”
>
> WFM, although editorially I'll split up the RSWG and RSAB requests,
> placing them in the respective "Mode of Operation" sections.
>
> Peter
>
> --
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future
>