IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Wed, 02 March 2022 10:57 UTC

Return-Path: <lear@lear.ch>
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 39A223A1119; Wed, 2 Mar 2022 02:57:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level:
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 BbxJexh16noY; Wed, 2 Mar 2022 02:57:06 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 503CC3A0D58; Wed, 2 Mar 2022 02:57:03 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::6] ([IPv6:2001:420:c0c0:1011:0:0:0:6]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 222Auuwd594724 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 2 Mar 2022 11:56:57 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1646218618; bh=ovyukcYTXtuOUgiFM2UIzByH1+5+llJKW+SnMia+Cb4=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=c3Vf5q5mFtXZgt058d1/X78nkDIbiOeM4b6f5p23MSTzj7ebbpgwsxJ1eNFpb3RUX 42ZOcS5qEunYKjfVZMDeKhKFlSxgkuyCiqL3kd/2NB6O4SPrt/Lqabwlt9VaqKR0Z1 S++jHkyStEkCpYrURBNOXeOP64330WCJSPTcvrEY=
Message-ID: <3747057d-005d-55de-cf3a-c21c0305c33a@lear.ch>
Date: Wed, 02 Mar 2022 11:56:55 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Lars Eggert <lars@eggert.org>, Carsten Bormann <cabo@tzi.org>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Paul Hoffman <paul.hoffman@icann.org>, "iab@iab.org" <iab@iab.org>, Mirja Kühlewind <ietf@kuehlewind.net>, Peter Saint-Andre <stpeter@stpeter.im>
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> <42560AF8-8FCB-4137-AB8D-BDE365A0D6C2@eggert.org>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <42560AF8-8FCB-4137-AB8D-BDE365A0D6C2@eggert.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------5L500i3yEDS5nB4oBRZ5vm7E"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ACvvLAh3iRHCy3Ufp8S1B9px4hM>
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:57:12 -0000

Thanks, Lars.  My suggestion is that we start out on rfc-editor.org and 
leave it to the RSWG to decide next steps.

Eliot

On 02.03.22 11:40, Lars Eggert wrote:
> 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