IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Wed, 02 March 2022 10:41 UTC

Return-Path: <lars@eggert.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 10C633A108B; Wed, 2 Mar 2022 02:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.227
X-Spam-Level: *
X-Spam-Status: No, score=1.227 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 gTRjjdx9WmTs; Wed, 2 Mar 2022 02:41:06 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 5BC7A3A1083; Wed, 2 Mar 2022 02:41:06 -0800 (PST)
Received: from smtpclient.apple (unknown [195.65.18.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 7FBB61D2F3F; Wed, 2 Mar 2022 12:40:58 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1646217658; bh=BmbPD8athWuhEg83TCHm43HTkT0yBUIb3DvsTrxChxg=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=uD/rZjbjjNhWAXZYLjiIdTp11SrjexLNFJ4IS1ctWU+MG+yyUJo5NglVcuhR2SjBG /p+cXexHyCbUy6h8/w1Ej/D+bSG5CN/NfRCE/3Vh0oagwQTBI4wPhZXYlaQoV/Kgz3 rAhzbkDrz7q4+CJexpBVNiKC9xs18D9v07yLJW+Y=
Content-Type: multipart/signed; boundary="Apple-Mail=_4C3A0F53-E8B0-4C10-9A88-EF30614BBE5D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <D72923A1-9C0B-4904-A3A9-C1983A8E3738@tzi.org>
Date: Wed, 02 Mar 2022 11:40:57 +0100
Cc: Mirja Kühlewind <ietf@kuehlewind.net>, "rfced-future@iab.org" <rfced-future@iab.org>, Paul Hoffman <paul.hoffman@icann.org>, "iab@iab.org" <iab@iab.org>, Peter Saint-Andre <stpeter@stpeter.im>, Eliot Lear <lear@lear.ch>
Message-Id: <42560AF8-8FCB-4137-AB8D-BDE365A0D6C2@eggert.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> <D72923A1-9C0B-4904-A3A9-C1983A8E3738@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-MailScanner-ID: 7FBB61D2F3F.A709A
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/oPsgU9rxQAEPU5HKA-dpBdWOgY0>
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:41:11 -0000

On 2022-3-2, at 11:35, Carsten Bormann <cabo@tzi.org> wrote:
> I’m also confused about the location of the RSWG.  Is this not an @rfc-editor.org list? Where is it then?

I just registered rswg.org and would be happy to transfer it to the IETF, if that could be a suitable home...

Lars

v2.23.0 | Report a Bug | By Email