IETF Logo Mail Archive

Re: [Rfced-future] Side idea

Carsten Bormann <cabo@tzi.org> Tue, 09 March 2021 08:23 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 3A1183A1727 for <rfced-future@ietfa.amsl.com>; Tue, 9 Mar 2021 00:23:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 tri_1uQXjpdF for <rfced-future@ietfa.amsl.com>; Tue, 9 Mar 2021 00:23:38 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 237863A1729 for <rfced-future@iab.org>; Tue, 9 Mar 2021 00:23:38 -0800 (PST)
Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DvpBc37zLzyTw; Tue, 9 Mar 2021 09:23:36 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <DE2E4740-B3A5-4E80-A9B9-2A9AA570E3CF@eggert.org>
Date: Tue, 09 Mar 2021 09:23:36 +0100
Cc: Michael StJohns <msj@nthpermutation.com>, rfced-future@iab.org
X-Mao-Original-Outgoing-Id: 636971015.911621-89ce8e1a7eb931389d02140c40a60fa8
Content-Transfer-Encoding: quoted-printable
Message-Id: <4882D61E-042B-477C-9DC3-FDD309ACC9E6@tzi.org>
References: <5d3e8031-2202-6a49-6bce-61c46bf0eb26@nthpermutation.com> <DE2E4740-B3A5-4E80-A9B9-2A9AA570E3CF@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ePvPhBe-5N3vjHu7URNTvkd_z8E>
Subject: Re: [Rfced-future] Side idea
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, 09 Mar 2021 08:23:41 -0000

On 2021-03-09, at 09:01, Lars Eggert <lars@eggert.org> wrote:
> 
> I'm not sure an RSE would be best qualified to author such a document. But a WG certainly can, like TCPM did for TCP: https://datatracker.ietf.org/doc/html/rfc7414

But they rarely do (*).

So I think it is an interesting question how this can be encouraged/helped with by providing/organizing additional resources; not sure the RSE would play a big role in such a process but they might have a coordinating one.
(Recently, the RPC has recruited some rather technically savvy copy editors…)

Grüße, Carsten

(*) yeah…

draft-bormann-6lo-6lowpan-roadmap-00
6LoWPAN Roadmap and Implementation Guide
2013-10-21
9 pages	Expired		

draft-bormann-core-roadmap-05
CoRE Roadmap and Implementation Guide
2013-10-21
22 pages	Expired

v2.23.0 | Report a Bug | By Email