[Rfced-future] Welcome to the romp! A reminder of what I would like us to decide first...

Eliot Lear <lear@cisco.com> Wed, 01 April 2020 06:34 UTC

Return-Path: <lear@cisco.com>
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 5BB183A0D82 for <rfced-future@ietfa.amsl.com>; Tue, 31 Mar 2020 23:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 V5ZbCiQgxSje for <rfced-future@ietfa.amsl.com>; Tue, 31 Mar 2020 23:34:12 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DDDB3A0D7D for <rfced-future@iab.org>; Tue, 31 Mar 2020 23:34:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7838; q=dns/txt; s=iport; t=1585722852; x=1586932452; h=from:mime-version:subject:message-id:date:to; bh=B9iHEEL+wu9SGd/w7Pz3NJ/eiuZmdUt3q6v/Xgvks6A=; b=UK768i6KvSlTMm+33lAl+TCnZEm6KGaXw6RzSAZ9OccQ6Lsb+CiVOL8S fzoC+SYZqA29xw9BiFVdqpQhEdxdllT/CQByWmY9L7AismvOwni5MQ/pw kVy5ao9kF8xq+T8rceYKrMeOMcCHuLYiqtB85zifMtBgOC0E/gJ5AXDt3 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BPBABQNYRe/xbLJq1mHgELHIFwC4F4BYEYVAEgEiqEGokCm0+GD4F7CgEBAQwBASUKBAEBhyA1CA4CAwEBCwEBBQEBAQIBBQRthVYMhhqBMwKBBgeDCwGCfA+eco4RdYEyhUuEdQaBOIxLggCBOCCFcgKEdzKCLASOMaI8gkcEglKFC482FgeCTIgxhDKMP5gzjzmDNAIEBgUCFYFUAzSBWDMaCBsVOyoBgkE+EhgNj0QBDoI9ilc/AzCPDQEB
X-IronPort-AV: E=Sophos; i="5.72,330,1580774400"; d="scan'208,217"; a="24886877"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Apr 2020 06:34:10 +0000
Received: from [10.61.233.22] ([10.61.233.22]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 0316Y7MO020414 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <rfced-future@iab.org>; Wed, 1 Apr 2020 06:34:08 GMT
From: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FD9F2B3E-4A43-4D3B-BFB8-6A6436461AD1"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Message-Id: <E6A56B50-B397-4DD1-BBFB-B9019899C322@cisco.com>
Date: Wed, 01 Apr 2020 08:34:07 +0200
To: rfced-future@iab.org
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.233.22, [10.61.233.22]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/s4zKpD3o2EnMEYxkxXZNUk-2jE0>
Subject: [Rfced-future] Welcome to the romp! A reminder of what I would like us to decide first...
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, 01 Apr 2020 06:34:14 -0000

… though not necessarily fast.

Now that we seem to be getting things under way, I would like to thank those who have chimed in on both program scope and work program.  For those that haven’t, here is a convenient list of questions you may wish to answer (or not).

It is entirely fair for you to ask your own as well, but I would like us to discuss both scope and work plan so that we can focus our energies.  A big thank you to mnot, Joel, Jari, and Brian for focusing on the former in particular.  Thanks also to Andy and Larry for commenting on the latter, and to John K. for hitting on both a bit.

For scope:


Should the program worry about the structure of the series or should the program worry about putting in place someone who could lead the community in worrying about the structure of the series (among other things)?  

A related question:

Should we establish a process that addresses series evolution over time or should we leave that for later?

For work plan, here is the proposal:
Open up “the floor” for short problem statements that people think we need to address. We should be clear on what we see as problems and their scope.
See if we can get agreement on those.
Open up “the floor” for proposals on how to solve those problems.
See if we can get agreement on those.
For (1) and (3) we can provide some structure to facilitate comparison and discussion, if that is the wish of the group.  This in itself is a discussion point I invite you to address.  Let me add a bit of justification for this approach.  It is based precisely on what Andy Mallis alluded to: if it ain’t broke don’t fix it, and I am sure that we all agree that not everything is broken.  Without understanding what we want to fix, we run a very high risk of not finding consensus for solutions.

I am aware that there are other things going on this week.  I think it’s been a while since I’ve seen a thread as long as the NOMCOM thread, for instance.  I will ask that we discuss these questions now, with an eye toward coming to consensus next week.  Again, perfectly fine to offer an alternative for a workplan.  But please if you are going to do so, do so soon.

With regard to Larry’s request for how things work today, I would like to highlight Olaf Kolkman’s excellent presentation at the IETF Administrative Plenary in Montreal, as well as the reading list that you may conveniently find here <https://github.com/intarchboard/rfced-future/blob/master/SuggestedReading.md>.

Eliot