IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 02 March 2022 10:36 UTC

Return-Path: <cabo@tzi.org>
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 5E68D3A1074; Wed, 2 Mar 2022 02:36:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=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
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 76KgyYpH80X8; Wed, 2 Mar 2022 02:36:06 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFA603A1072; Wed, 2 Mar 2022 02:36:05 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4K7rB25bcNzDCbx; Wed, 2 Mar 2022 11:35:53 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <F3E21454-F454-49BE-A506-FCFDFF0DF890@kuehlewind.net>
Date: Wed, 02 Mar 2022 11:35:43 +0100
Cc: Peter Saint-Andre <stpeter@stpeter.im>, "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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D72923A1-9C0B-4904-A3A9-C1983A8E3738@tzi.org>
References: <74AF211B-741E-46FC-9E35-8015D5254515@icann.org> <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch> <0c1711fe-bc05-e6b0-2f94-eb1c24ae3766@stpeter.im> <F3E21454-F454-49BE-A506-FCFDFF0DF890@kuehlewind.net>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/7K-y_6cgrWSR8qGl3yhQk6OMTyQ>
Subject: Re: [Rfced-future] [IAB] 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: Wed, 02 Mar 2022 10:36:11 -0000

On 1. Mar 2022, at 19:54, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
> 
> I was actually assuming we keep the rfc-interest list at least for now as this is also the list people are using to e.g. ask questions (to the RPC or the respective experts) about who to apply the xml or such.

Yes.

The RSWG list should be for business of the RSWG.
There is a lot of discussions about the RFC series that is not leading to RSWG activities (and v.v., if you count in the bureaucracy).

I’m also confused about the location of the RSWG.  Is this not an @rfc-editor.org list?  Where is it then?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email