Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model
Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 01 March 2022 21:44 UTC
Return-Path: <brian.e.carpenter@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 C51D43A0FE0; Tue, 1 Mar 2022 13:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, NICE_REPLY_A=-0.001, 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 xxHVbiMz7VG0; Tue, 1 Mar 2022 13:44:31 -0800 (PST)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (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 B3AAB3A0FF7; Tue, 1 Mar 2022 13:44:31 -0800 (PST)
Received: by mail-pl1-x62c.google.com with SMTP id e2so2159928pls.10; Tue, 01 Mar 2022 13:44:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Y5gdCxOoFKeNSwm85Jc1QlV/fWYLsac4rmkC5WYfpmA=; b=VcZdFShkBj8FIByLcn8JEEAN1DEtInJqFIKhlcb6LuDYhCzHNR5InGCRPcX4xRwX5G h/nATFRhXPDleHBvoD+0oLhyCoTHSPntNQmqg4kvCItvWRzooJRgPnuime6/JtNvwicJ JDmqFBrpq60AyXxjMYmzETklkOLM4HZaFpvjonz+hcHqM0Uj5Z8u6s25o4mm3DT3fvL6 ip6n5hTHE4sR9yCSGQRrmv/pU/umZ7l0R6tB83923p/0Vd43xRoudrGJ8CZYKcZdk04/ rkFI4zCX6t5mqBLmyQXdssq/zP5nAusjLS9WhKnbwWoLijRYvvP89jhwezZv4rlHJ1N1 zskQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Y5gdCxOoFKeNSwm85Jc1QlV/fWYLsac4rmkC5WYfpmA=; b=5hgoyecuaJznJKMu7XzXD/PD4LUrd+4TKjbGzgeHnje4WJBgqXw7l8WzNAdmfV8lfP ZpDs8fw6PlsowxwUpHh/hL/4brSedDJlSYz+WJ+mraGRyJiktUWx2FcYdIz7tUX6SIzd CjdV9PO9/mf9UG/MJEnE3QcXpJ1p3L/4yUAGPMzsh67WfssfTqTEC6uB2pmELB67/RB3 Ev+hZIqvbGR5D65unFYG3K8raA79coskRIhJFIGbKQ9by1fg11Bvd2n9W9wv1Z0aKn2o L4NVqcPvRloRyoguxWMX53P3WA7exYEU9ze4iJeIeY8D0kwu7X3ukzf1CPmwV9Vsd1cC 3N2Q==
X-Gm-Message-State: AOAM532hHxYc3+KHey6G9GfQTTRjkMChC4LuFkOa8d3uqvKycnb01Xz/ fnR0+37eYidqaRnVP7HxWL0=
X-Google-Smtp-Source: ABdhPJzz4t1uviHe0+iZ986jMqhZBV54tsjwknIMlZrEIn5AIvFMAJa3SG+EMaPEz4utjWd5N4y4rw==
X-Received: by 2002:a17:902:d4c6:b0:150:15ed:3cd9 with SMTP id o6-20020a170902d4c600b0015015ed3cd9mr26938070plg.2.1646171070886; Tue, 01 Mar 2022 13:44:30 -0800 (PST)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id q31-20020a17090a17a200b001bef4ea0377sm170723pja.10.2022.03.01.13.44.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Mar 2022 13:44:30 -0800 (PST)
To: Peter Saint-Andre <stpeter@stpeter.im>, Eric Rescorla <ekr@rtfm.com>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Paul Hoffman <paul.hoffman@icann.org>, "iab@iab.org" <iab@iab.org>, Eliot Lear <lear@lear.ch>
References: <74AF211B-741E-46FC-9E35-8015D5254515@icann.org> <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch> <0c1711fe-bc05-e6b0-2f94-eb1c24ae3766@stpeter.im> <CABcZeBPqGHt0KD4tjQZFd7SVRwQHVa7fj7wJ_LYCn-3XQKjfjg@mail.gmail.com> <de6c4153-ebed-47e2-7657-3ad7f917dd73@stpeter.im> <2b400d58-5985-016f-e722-2b61df64e146@gmail.com> <c75a8f66-3170-986d-7973-ff8758b4996b@stpeter.im>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <a1766e86-02e5-8c58-f089-2a0a1dbd1439@gmail.com>
Date: Wed, 02 Mar 2022 10:44:25 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <c75a8f66-3170-986d-7973-ff8758b4996b@stpeter.im>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/HyKVMnvgot_iNR_qSkrGm5KB11I>
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 21:44:37 -0000
On 02-Mar-22 10:04, Peter Saint-Andre wrote: > On 3/1/22 12:53 PM, Brian E Carpenter wrote: >> >> On 02-Mar-22 07:52, Peter Saint-Andre wrote: >>> On 3/1/22 11:45 AM, Eric Rescorla wrote: >>>> >>>> >>>> On Tue, Mar 1, 2022 at 10:36 AM Peter Saint-Andre <stpeter@stpeter.im >>>> <mailto: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. >>> >>> Can we specify (at a high level) what topics are appropriate for >>> rfc-interest as opposed to the RSWG list? Would we envision that rfc-i >>> is more for implementers? We already have a plethora of lists (rfc-i, >>> tools-discuss, xml2rfc-dev, etc.) and it's already unclear where certain >>> topics should be discussed. >> >> Please not. I don't think we should cover such operational details at all. >> (Do you realise that RFC2026 refers to anonymous FTP and gopher?) >> >> How about being *less* specific: >> >> The RSAB seeks >> such input by, at a minimum, sending a notice to relevant >> mailing lists. > > IIRC folks wanted to know that there was one place such announcements > were guaranteed to appear (kind of like the new-work list, I suppose). I want that too. It just doesn't seem like something we should bake into an RFC. Brian
- [Rfced-future] Comments on draft-iab-rfcefdp-rfce… Paul Hoffman
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Eliot Lear
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Brian E Carpenter
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Eric Rescorla
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre
- Re: [Rfced-future] [IAB] Comments on draft-iab-rf… Mirja Kuehlewind
- Re: [Rfced-future] [IAB] Comments on draft-iab-rf… Mirja Kuehlewind
- Re: [Rfced-future] [Ext] Comments on draft-iab-rf… Paul Hoffman
- Re: [Rfced-future] [Ext] Comments on draft-iab-rf… Peter Saint-Andre
- Re: [Rfced-future] [IAB] Comments on draft-iab-rf… Peter Saint-Andre
- Re: [Rfced-future] [IAB] Comments on draft-iab-rf… Mirja Kuehlewind
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Brian E Carpenter
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Brian E Carpenter
- Re: [Rfced-future] [Ext] Comments on draft-iab-rf… Eric Rescorla
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Peter Saint-Andre
- Re: [Rfced-future] Comments on draft-iab-rfcefdp-… Brian E Carpenter
- Re: [Rfced-future] [Ext] Comments on draft-iab-rf… Lars Eggert
- Re: [Rfced-future] [IAB] Comments on draft-iab-rf… Carsten Bormann
- Re: [Rfced-future] [IAB] Comments on draft-iab-rf… Mirja Kuehlewind
- Re: [Rfced-future] [IAB] Comments on draft-iab-rf… Lars Eggert
- Re: [Rfced-future] [IAB] Comments on draft-iab-rf… Eliot Lear