[Rfcplusplus] draft-klensin-rfcplusplus-alternatives-00

John C Klensin <john-ietf@jck.com> Sat, 14 July 2018 14:02 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: rfcplusplus@ietfa.amsl.com
Delivered-To: rfcplusplus@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7BFE130ED2 for <rfcplusplus@ietfa.amsl.com>; Sat, 14 Jul 2018 07:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 ZIxa-CUy7aHM for <rfcplusplus@ietfa.amsl.com>; Sat, 14 Jul 2018 07:02:36 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41D34130DBE for <Rfcplusplus@ietf.org>; Sat, 14 Jul 2018 07:02:36 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1feL86-000J6i-RF for Rfcplusplus@ietf.org; Sat, 14 Jul 2018 10:02:34 -0400
Date: Sat, 14 Jul 2018 10:02:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Rfcplusplus@ietf.org
Message-ID: <1986638168567223C132B119@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/2M0SCPOQ75mZ2OZcTVR7-80woqU>
Subject: [Rfcplusplus] draft-klensin-rfcplusplus-alternatives-00
X-BeenThere: rfcplusplus@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: For discussion of the RFC++ BoF proposal and related ideas <rfcplusplus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfcplusplus/>
List-Post: <mailto:rfcplusplus@ietf.org>
List-Help: <mailto:rfcplusplus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jul 2018 14:02:38 -0000

Hi.

As suggested by one of my comments to the list several days ago
and in the hope that it will help with the discussions, I've put
together an Internet Draft that attempts to summarize some major
categories of proposals so far.  The draft largely sets the
issues of problem statement and whether there is a problem work
solving aside and looks at possible solutions (including one
very radical one not explicitly proposed yet, at least in any
message I've seen).

Alissa agreed to allowing it to be posted between the cutoff and
Monday if I sent it to her.  I did that at around 19:48 UTC
yesterday.  It apparently has not been posted yet, I assume
because of the very busy schedule of the IETF Chair.  If she
continues to not have time, I'll post it to this list late
afternoon Montreal time today and then just go through the
normal procedure for the repository.

I hope at least a few people find it helpful.

best,
    john