[Rfced-future] Next Step - proposals?

Brian Rosen <br@brianrosen.net> Fri, 07 August 2020 14:55 UTC

Return-Path: <br@brianrosen.net>
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 5C2B33A0D3B for <rfced-future@ietfa.amsl.com>; Fri, 7 Aug 2020 07:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.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 eC5JSMTX_YSj for <rfced-future@ietfa.amsl.com>; Fri, 7 Aug 2020 07:55:15 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 7DD8E3A09D6 for <rfced-future@iab.org>; Fri, 7 Aug 2020 07:55:15 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id g14so2189749iom.0 for <rfced-future@iab.org>; Fri, 07 Aug 2020 07:55:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:message-id:date:to; bh=dlQVi5TblqHMk100yNM75rUNfECNZoX61RfESs3tCtw=; b=rlavc59X4hqV/9Ae1AIehXCllnEWEnSwkYRdW2hk4RTO2YFRyNkVAkJkyXhirz+gKg ghmIuGh/p0ljwQaeVGjRPWp3ADRGG8sAv/N0HO+WD799KdP5Wk1ky1IOLMV6u3aKiDx8 fDS1mobjPUftRUstOuDsz3vkqbbhaJd/zxm6vt3mMkGaQQ1UfxY/aVeLIR4F73zZuiF9 IV7VxDN1G8qrwivkwm9e18L7TZsGVvVeLkTatpIZsJWm9Y1yN2V51y5n5sNRB58bCWkh mamd4YvHbOO4pEb6w9dFN43Uo6ZCnZfEvIrWDTnRtdxcZF6pZ1m98iGYM2d+ZP+Egftq 2bCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=dlQVi5TblqHMk100yNM75rUNfECNZoX61RfESs3tCtw=; b=dUCRitYnhSV2NS+KGsBTVWkS2IrUcn+Oys7ElKZguPNJt2OgD8en0gYQvYilSfHDzj HlgpYYqYNviCV/NRN73ITiW/JAJhE1d6zLtdIV2jY3PzDkPOozO4UT6K375VD39nRJd9 1gO7EA7BdIrg9CR7pBDy9BY8kW0dAXJ8ns3rZVs+UGvKtKijf0LzvJT9M2dEn2FI0NXZ dTkSfXgbvo0XmCgaFJr8uk24JbD61k22NL43qESUHK77w5idJJdHrTSPLYsOk4XhG3j8 l8X55wFgUXgsY7Rypk5p5oFC5+79gGwuDSAuL6DuL0wxsInxYDFWF6HPCBGETQPBq0RI JXfw==
X-Gm-Message-State: AOAM532bjp5rzX1q+rxbskO4NShZ1a31NPErPHSvFjs0nhYm9KaTQ0Ee LHwvOH7MjhQduT9tUNDb+xBYgdFrizE=
X-Google-Smtp-Source: ABdhPJxuiH/qUEQwa/mMyqces2K1pjDu4F/2gyaszppqaWqOy/fEiDH+iVSIdZPx8nKvhLXpKxuMBw==
X-Received: by 2002:a5d:9d11:: with SMTP id j17mr4945580ioj.140.1596812114448; Fri, 07 Aug 2020 07:55:14 -0700 (PDT)
Received: from brians-mbp-2871.lan (dynamic-acs-24-154-119-158.zoominternet.net. [24.154.119.158]) by smtp.gmail.com with ESMTPSA id m2sm6551064iln.1.2020.08.07.07.55.13 for <rfced-future@iab.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Aug 2020 07:55:13 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_580A634A-168B-4CC8-94CE-4E7580A5DD1D"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Message-Id: <AFAC09A3-4242-4774-8765-45176290E9E3@brianrosen.net>
Date: Fri, 07 Aug 2020 10:55:12 -0400
To: rfced-future@iab.org
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Y_IAXkSVk8RZY65Vzj00ncbXe4I>
Subject: [Rfced-future] Next Step - proposals?
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: Fri, 07 Aug 2020 14:55:17 -0000

Dear colleagues,

The chairs would like to thank you for participating in the IETF 108 meeting of the RFC Editor Futures program.  We learned quite a bit at that meeting, not the least of which was that the group is not yet prepared to choose a direction.

Therefore, what we are thinking is that the next step should be for people to develop fleshed out proposals.  It would be good to have several alternatives that explore the different philosophies that have been expressed in the group.  Each proposal should be very clear on a few points:

Overall motivation and philosophy
What each proposed entity is responsible for
What the relationship of each entity is to other entities 
What accountability, selection, and transparency mechanisms are in play for each entity

The next step would be for us to discuss these proposals and see if we can find some common ground.  Our thinking is that we would appoint a neutral editor to document that common ground, which could come from any proposal.

The timing for any interim to discuss these depends very much on having proposals.  There are some drafts already of course, and we hope we can have more soon.

Thoughts?

Eliot and Brian